[WARNING] XCP-ng Center shows wrong CITRIX updates for XCP-ng Servers - DO NOT APPLY - Fix released
@Biggen I think the same, but until there is no tree in XO, I get not used to XO(A).
And I didn't catch anything, this was my entire fault (did you notice the XCP-NG CENTER TEAM badge near my username?)
Yeah I get that the layout of xcp-ng Center is friendlier on the eyes.
Fix is available: https://github.com/xcp-ng/xenadmin/releases/tag/20.03.01.31
Sorry for the trouble
I just endet up to remove all URLs with "citrix." in them, except for XML-Namespaces which are not executed as download.
I have big hopes for a new major XO(A) release to replace XCP-ng Center with a hopefull spectecular good way of a tree view
@borzel only who do nothing can't do wrong. keep up with the good work and make treasure of your mistakes!
Pretty please do not abandon XCP-ng Center! There are BASIC things XCP-ng Center does that XOA free does not. For example, cloning a VM cannot be done with free XOA.
I don't have any insider knowledge, but I gotta believe Vates will have to pull the plug on xcp-ng Center at some point. Its another source of bug entry (as we just witnessed) and requires extra manpower. I'd rather them throw more of their time into XOA since that is their "official" management software.
Why not just built XO for yourself from sources if you need to do more than the free version of XOA allows?
I understand they will have to pull the plug on xcp-ng Center at some point and I will have build XO from sources. I do hope XO's views improve and work better, because they can be quite frustrating now. Its the nature of a web interface, and I understand there are challenges there, but if there is no choice but to use XO then the challenge is even greater.
However, I say XO(A) is a fantastic product and I have tried to make the math work for us and pay for it. I still can't swing it, partly because you need Enterprise Edition to make a simple clone.
I am exceedingly grateful any of this exists at all, and I thank everyone who have made it possible!!!
- Why not using XO from the sources?
- Fast clone shouldn't be restricted to Enterprise, sounds more like a bug than anything else. In short, XOA Free should cover all features of XCP-ng Center.
- We also have possible plans for XO lite, a "XCP-ng Center" like embed in the host UI directly.
- While I am capable of using XO from sources, I value the work that has gone into XOA and feel guilty running from source
- I am glad to hear you say this, as I found it odd to require Enterprise. Should I file a bug report?
- +1 for an XO lite!
I will also repeat, THANK YOU to you and your team for your work. It pains me to read posts questioning your reasons to charge A,B,C for X,Y,Z, and I am on your camp. You need to make it viable... Hence my apprehension to use XO from sources.
No worries @hvilches and thanks for your support and feedback!
Please open an issue on XO GH bug tracker regarding clone feature, it should be available in XOA Free. If you spot other "basic" features like that restricted, please report
The tree-view in Center is far better than any overview I can find in XO.
Starting, stopping, restarting a VM is fast and natural to do in that tree view.
That makes Center useful for occasional users, that have to find a way to solve a problem, where XO is targetted at the pro user, who knows how to solve his problem before he starts.
Just to join a new server I get confused every time, and end at a place, where I have to enter its password permanently, which seems wrong.
With Windows on the workstation you have the chicken/egg problem. I run XOce in Virtualbox on my laptop. Not simple compared to Center.
XO is not cheap, and if that forces you into XOce there is confusion between the 3 versions XO, XOA and XOce, dubbed up with different ways to install XOce.
XOlite embedded in the Xcp-ng-host might change things.
- XO6 will be the next UI for XO, using a tree view among other things
- I don't understand about adding the host password?
- No chicken egg problem: you can deploy XOA from Xen Orchestra website. Why not doing that?
- Anyway, XOlite will solve all of this
@olivierlambert Oliver - do you guys have a feature request tracking page for XO6? I would really like to give some real-world (production) viewpoints to your next tool. Like other people, I have to switch between both tools (XO and XO Center) to get my job done, thus, I am hoping the version will help avoid that problem.
@olivierlambert Thanks Oliver! Let me know if you are interested in any BETA testers. I would be happy to join your beta user's group...
As soon we got something usable, we'll have probably another extra "route" in XO URL, like
I hope that the next XO UI includes way to handle large amount of VMs easily.
Currently, we have hundreds of VMs running. If for example, I want to start, stop, migrate or w/e large amount of them with a single command, that is only possible from the Center. XO only shows 20 VMs at once.
For us, there is also second problem with using XO only, because XO is hosted on the Xen server itself, so if Xen server is in maintenance then we cannot access XO interface - of course that could be avoided by adding isolated machine running XO, but up until now we have been to lazy to do it - mainly because of the problem described above
Otherwise XO is a great product, and we use it for everything else.
@Zaiban that's not true! The UI is made to handle thousands of VMs!
It's just that you think to change your mind and use filters Filters are life, filters are THE way to handles tons of objects. Not displayed infinite number of them. Note that you can now even display 100 objects in recent XO release.
So please reconsider your workflow before telling you can't do something
Okay sorry, maybe I have been lazy at something else too like skipping the documentation. I'll do more research and learn to use properly.
Thanks for pointing it out
And another for making such a great product. We have been using from sources until now, because in our University its a hard process of getting any licenses approved for purchase. Maybe in the future I can do something about that.