XO Lite: building an embedded UI in XCP-ng

ChromeShavings

@olivierlambert - This build is awesome! I just needed something simple and web-based to view the status of my VM's and this met that need. Loving XCP-ng 8.2. Cannot wait for 8.3!

ajpri1998

I see I'm running commit "0d127" of XO Lite, from December 28th. Is there a faster "channel" I can get on, to test some of the latest commits?

Also I like how on XO you can click on the commit # to be taken to the github page for it, can that be added to xo lite?

olivierlambert

XO Lite release process is a bit different. If you want the "latest" build, you can use the "SaaS" version and point it toward your host. Otherwise, you'll need to wait for the RPM to be updated in your XCP-ng.

CptHyper

Hi, just installed 8.3 on my testbox to play around with it and figured out XO Lite is not working when you select dualstack (ipv4 and ipv6) during installation. I reinstalled the machine only with ipv4 and XO Lite was up and running immediately.

olivierlambert

Yes, it's not XO Lite related but IPv6 dual stack related. Adding @BenjiReis in the loop

john.c

@CptHyper said in XO Lite: building an embedded UI in XCP-ng:

Hi, just installed 8.3 on my testbox to play around with it and figured out XO Lite is not working when you select dualstack (ipv4 and ipv6) during installation. I reinstalled the machine only with ipv4 and XO Lite was up and running immediately.

Thanks for further confirming my past experience with the IPv6 dual stack and IPv6 only issue. You experienced the in-ability to connect to XO Lite because of the issue with the IPv6 dual stack management network not coming up on start up.

DustinB

Love the platform already, great work, even with just the limited abilities that are baked in.

olivierlambert

Yes, it takes a bit of time now because we validated the concept and now merging all components in a clean fashion in the code base. Now, we have a core component library we could you for both XO 6 and XO Lite \o/

saneece

I've tried to put get this working on both of my hosts but I get the same output when I go to it in Edge and Chrome

Microsoft Edge
Version 121.0.2277.106 (Official build) (64-bit)

Google Chrome
Version 121.0.6167.185 (Official Build) (64-bit)

Both hosts are on XCP-NG 8.2

olivierlambert

Have you tried with the special URL?

saneece

@olivierlambert

Not sure what that is honestly. Very new to xcp-ng

olivierlambert

Visit your host/pool master URL (like https://<master-ip-address>) and validate the self-signed certificate
Then enter this URL in your browser: https://lite.xen-orchestra.com/#/?master=<master-ip-address>
Profit

saneece

@olivierlambert

Closer. I at least get a login page but when I try to log in, I get "An error has occurred" I have confirmed the password. I just logged in to the host directly on the machine to confirm.

saneece

Pause, I am an idiot.. I left the <> around my IP lol..

Can you explain why the calling on HOST_URL/xolite.html did not work and why I needed your special URL to make that work? I think you have a very interesting way to accessing XO Lite while it's in beta.

HeMaN

@saneece said in XO Lite: building an embedded UI in XCP-ng:

I've tried to put get this working on both of my hosts but I get the same output when I go to it in Edge and Chrome

Microsoft Edge
Version 121.0.2277.106 (Official build) (64-bit)

Google Chrome
Version 121.0.6167.185 (Official Build) (64-bit)

Both hosts are on XCP-NG 8.2

Output is of the wget command that should be executed from a shell on the host, but you are talking about edge and chrome.
You did do the wget command in a shell (should save a xolite.html file and not an index.html file) and then with a browser open the xo-lite url on the host it was downloaded on?

Otherwise it looks like a typo in the command that made you redirect the screen output of the wget command to a file called xolite.html

peder

@saneece The XO Lite installing instructions say that you should run this command on your xcp-ng server

wget https://lite.xen-orchestra.com/ -O /opt/xensource/www/xolite.html

You seem to have omitted the -O /opt/xensource/www/xolite.html part, since your screenshot talks about "Saving as index.html", and that's why you can't go to HOST_URL/xolite.html

saneece

@peder and @HeMaN I copied and pasted the command from the post into SSH on both my hosts.

Read my follow up posts though and youll see I can access it with https://lite.xen-orchestra.com/#/?master=<master-ip-address> so I am good now. Thanks though.

peder

@saneece said in XO Lite: building an embedded UI in XCP-ng:

Can you explain why the calling on HOST_URL/xolite.html did not work and why I needed your special URL

Yeah, I was just explaining why HOST_URL/xolite.html didn't work for you.
You only ran wget https://lite.xen-orchestra.com/
and that's why your log screenshots says that it's saving to index.html.

If you had run the entire command it would have said "Saving to /opt/xensource/www/xolite.html " and you would have been able to access it the "normal" way.

saneece

@peder Gotcha. I actually checked my command history and I did include the "-O /opt/xensource/www/xolite.html" portion of the command. It does look like the -O was lowercase though which ended up being the problem so you were right. Apparently I DIDN'T copy and paste it like I thought I did, so I apologize. Thanks friends!

HeMaN

@saneece

Wget options say
-o logfile,
--output-file=logfile
Log all messages to logfile. The messages are normally reported to standard error.

-O file, --output-document=file
The documents are not written to the appropriate files, but all are concatenated together and written to file.

So the output of your first wget download was indeed redirected to the xolite.html file you saw in your browser in stead of downloading the file.

The location where you were when you typed the command will have the index.html file that is downloaded as seen in the 'log' file you created