-
If you have no VM and the host doesn't have a pool name, then you have everything loaded
-
@olivierlambert
How to start setup infrastructure (assume it was the main reason to develop lite) if there is nothing available at start? -
Because it's a first alpha release and not a v1.0?
-
@olivierlambert
Got some output from chrome:Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced. To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData. Note that for performance reasons, only the first access to one of the properties is shown. 1 source index.cb584bcd.js:1But got the answer already "first Alpha"
Good practice is to add comment to content f.ex. "Network - Not ready yet" or something similar to prevent stupid questions like mine -
High level overview feedback:
So a bit of feedback from me too.- The layout looks great!
- I believe it has just enough to get one started with using the hypervisor (taking into account the existing labels and the placeholder buttons) or to help you in a pinch.
Current issue found that I assume should work at this time based on other messages is that the console seems to have been implemented but is not working. Chrome inspector console shows: WebSocket connection to 'wss://<my local ip address>/console?uuid=e4cd9c61-d399-a3fa-33f7-5699c920d523&session_id=OpaqueRef%3A927fa4fe-74c2-456a-bfd8-d84e98c3bf42' failed. After that there is a line with "Failed when connecting: Connection closed (code: 1006)".
The interface looks very clean and oriented on functionality. Congratulations and keep up the good work!
-
What version of XCP-ng are you using @bogdantomasciuc ? The console should work on 8.2.1
-
@bogdantomasciuc This is probably due to the browser rejecting self-signed SSL certificates when it tries to connect to the console (the console connections go directly to the slave hosts instead of going through the master). To fix that, go to each of your slave hosts' landing pages with HTTPS (https://<slave host IP>/). The browser should ask you if you want to accept self-signed certificates. Click on Accept. Once you've done that for all your hosts, go back to XO Lite, refresh and the consoles should work.
In the next releases, XO Lite will be able to detect when the self-signed certificates haven't been accepted and give clear instructions on what to do
-
@redy Thanks for the feedback, we've added a "coming soon" message on pages that aren't implemented yet, to avoid confusion.
-
@olivierlambert I am currently on 8.2. I will upgrade and try later. Thank you!
@pdonias The certificates are already accepted. I will check back after I update to 8.2.1 as suggested by @olivierlambert but thank you very much for your suggestion!
-
The console doesn't work for me either.
XCP-ng is 8.2.1
My workstation is Fedora 36 and I have tried both Firefox and Chrome.
I am connecting to XO-Lite over https so the cert has been accepted.
I am using the navigation panel on the left to navigate down through the pool -> host -> vm and clicking on the vm. There is no response at all. The main window where I assume the console is supposed to be remains blank.
Also the link to change the theme that was towards the top left has disappeared so I am stuck in dark mode.
-
The link is on the right now (moon/sun for dark/light theme).
-
@mjtbrady Could you open your browser console (F12 > Console tab) and check if there's an error message when you open a VM console?
-
Firefox can’t establish a connection to the server at wss://10.42.27.25/console?ref=OpaqueRef%3A96c12e00-b160-48c1-8c44-bc06be4af8af&session_id=OpaqueRef%3A5be27bec-a910-4ee6-8beb-f6951a7d7ccc. index.e1f7b30e.js:60:128685 WebSocket on-error event index.e1f7b30e.js:60:154603 Failed when connecting: Connection closed (code: 1006) index.e1f7b30e.js:60:157567 _fail https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 _socketClose https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 onclose https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 (Async: EventHandlerNonNull) attach https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 open https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 _connect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 _updateConnectionState https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 ut https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:60 setup https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:64 qi https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 wr https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 d https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 run https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 A https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Hc https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _x https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _x https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 (Async: promise callback) fx https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 cx https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 effect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _g https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Td https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 ax https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 effect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _g https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Td https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 ax https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 effect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _g https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Td https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 ax https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 effect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _g https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Td https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 ax https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 effect https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 _g https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Td https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 ax https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 set value https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 Oe https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:9 q https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:9 (Async: promise callback) q https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:9 T https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:9 l https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:9 qi https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 wr https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 n https://lite.xen-orchestra.com/dist/assets/index.e1f7b30e.js:1 -
I took that to be an icon associated with the logout. I think that the theme and logout either need to both be text or both be icons or more obviously be separate buttons. Or maybe it is just me.
-
@mjtbrady Did you accept the self-signed certificates by navigating to https://10.42.27.25/ and clicking on Accept? It's important to accept them for all the slave hosts, not only for the master host.
-
That was the problem, but I do not think that it should be.
I am browsing to XO Lite using the FQDN of the XCP-ng host and the certificate had been accepted for that. But the console connection being made by XO Lite is to the XCP-ng host IP address.
-
Yes, Xen API (XAPI) is returning IP addresses only.
-
Indeed, @olivierlambert, that was the issue and it works now. So for whoever has the same issue. First go to the local IP address of the host (NOT to the domain name), accept the certificate and then go to /xolite.html and it will work both with the ip address and the domain name in the address field.
Thanx again for clearing things up! -
Hi Guys.
Just a note for dumb bums like me... I tried out XO Lite (coming along nicely) but it took be a bit to work out that it needed to be installed on the pool master.
I put it onto one of the slaves, and tried to log in, but got no feedback at all, just nothing changed.
I eventually looked in the xo logs and found it was complaining about being on the slave not the master.. duh.. when you think about it.. but some feedback in the gui would help
-
That will be easier when it will be released officially, meaning bundled directly inside all hosts. So the slave will redirect you to the master.
