The last version available is far more complete than the OP. You can start/stop VMs, snapshot etc. VM creation is in the pipes with network creation too. But still, you can have far more interactions today than even 6 months ago.

@pdonias said in Wrong colours in dashboard:

Thanks for the feedback, we'll take care of that.

To get more of an idea about the HDR technology checkout these links:-

https://www.viewsonic.com/library/photography/what-is-hdr-hdr-vs-sdr/ https://en.wikipedia.org/wiki/High_dynamic_range https://www.dolby.com/technologies/dolby-vision/

Some of the links refer to videos though the graphics technology applies outside of videos, these will help you get an idea of how the technology will affect the user interface of XOA and XO Lite.

In this case it's the colours part of HDR which is relevant as the user interface, doesn't have photos or videos in it but does still have other forms of imagery. Though the client devices may be used with other usage which the full HDR is appropriate for, so thus have compatible hardware and have the feature active.

@ph7 If your interested in finding out more about HDR you can also check out the links above. I also added my input about your issue, as I knew that HDR can play a part in the reproduction of colour etc in an image, or user interface.

So can have an impact on what colours are used on the dashboard, as well as other parts of the user interface.

Hi @mattnj

I think it's possible deploy took some time and as long as you have a XAPI task running, remove can't be done Yes rebooting will "cancel" the task and destroy can work then 🙂

@tcorp8310 yes yum update should do the trick

Hi @Houbsi, good question. This is how it works:

any XO instance that is connected to a pool will add some information about itself to the pool's metadata XO Lite reads that information to know the URL of XO's UI

In xo-server's config, you can force XO to report a custom URL instead of raw network information:

[http] publicUrl = 'http://example.com'

However, at the moment, XO Lite doesn't support it, but it's coming soon: https://github.com/vatesfr/xen-orchestra/pull/7849 🙂

And @olivierlambert, yes, for now, any XO instance, whether it's an XOA or not, reports itself on the pool and we simply pick the latest one. But we can definitely implement something smarter in the future if necessary.

pdonias opened this pull request in vatesfr/xen-orchestra closed feat(lite/XoaButton): support `xo-server`'s setting `http.publicUrl` #7849

@Tristis-Oris said in XOLite - Which URL?:

@itpartner it already builtin at xen 8.3, so guide will not requried.

This, XCP-ng 8.3 isn't released yet, so you're running 8.2 which doesn't include the package.

@hellst0rm I don't see why it wouldn't work as long as everything is set to trust your internal CA root. It's pretty trivial to create a CA. I did it years ago because I can't stand cert errors and as a learning exercise. The only annoying part is it's just one more thing to keep track of and update, but if you're running a homelab it just becomes another part of the exercise.

@borzel With my PWA manifest merged you can do further development work around it if you wish. However don't add to much extra Java script if you do so, as it can seriously affect performance and security.

Also too many abstractions can affect the ability to understand how Xen Orchestra, as well as XCP-ng works and fix any issues, by thus limiting the number of people who can understand the code and its workings in order to fix them. As read any code from libraries and frameworks used in order to understand them and avoid any vulnerabilities in the code.

Not to mention that people who wish to use it may not have Java script enabled browsers or have Java script disabled (maybe even blocked). If the software can't work at all without Java script in the browsers currently support available at the moment now, then they will boycott using the software or website.

I'm not waiting for your suggestion to do it, it's already in the backlog 😉