@olivierlambert Thanks Olivier, perfect explanation and also good that there is a way back by switching the channel. Will live the "latest" life from here on out

For anybody that ends up on this old discussion regarding the Xenica WHMCS addon. It might be interesting to know that they charge $30 per month and it seems not to have been maintained in a very long time.
For vmware there is a suite of scripts with working examples, for Xen Orchestra we have the API set, but it would still be very beneficial to get the original plan of @olivierlambert in this blog post, back on track.

I could provide a WHMCS test setup, people for testing (agents of hosting companies), and participate as much as my limited programming skills allow

@olivierlambert Thanks Olivier, perfect explanation and also good that there is a way back by switching the channel. Will live the "latest" life from here on out

In XOA Enterprise XOA > Updates > Release channels

Re: Stable channel update date

Hi, is the "latest" channel tested or more of a beta? ...or to ask differently: is it safe to assume "latest" will not take down a productive server farm, or would we have to stay on stable to get maximum protection from heart attacks?

@stormi thanks, will look forward to try this out when the update drops.

@Danp these hosts are running:

Version 8.2.1 ()
Build number release/yangtze/master/58

@Andrew thanks for the hint. Didn't even think of -or look much- into the shell commands, but you're absolutely right, they would be faster and easier than getting a XCP-ng Center running on some virtual Windows, when I can simply open the shell (even from within XOA) and do it this way.

Re: Can't figure out how to configure a separate NFS network on the hosts via XO

Reading the above topic, I was able to do network changes right in XOA instead of having to go into XCP-ng Center. However, I see that mode column twice (seems to be an exact copy) in the PIFs list of all hosts and I can't find a way to change the MTU listed. For MTU changes I still need to go into XCP-ng Center, remove the IP settings at the bottom, change MTU, then add them again. Is this the intended way of handling such changes ?

Running an XCP-ng host for a few hours results in the local console being unreadable and plastered with these errors:

fcoe_driver CRITICAL: ['Traceback (most recent call last):\n', '  File "/opt/xensource/libexec/fcoe_driver", line 34, in execute\n    output = subprocess.check_output(cmd)\n', '  File "/usr/lib64/python2.7/subprocess.py", line 575, in check_output\n    raise CalledProcessError(retcode, cmd, output=output)\n', "CalledProcessError: Command '['fipvlan', '-c', '-s', 'eth1']' returned non-zero exit status 19\n"]

I have actually two questions:

• what or how can these above errors be prevented? ..not using any FCOE

• is there a key combo or other simple way to re-draw the console menu so text becomes readable and the navigation usable again?

For anybody that ends up on this old discussion regarding the Xenica WHMCS addon. It might be interesting to know that they charge $30 per month and it seems not to have been maintained in a very long time.
For vmware there is a suite of scripts with working examples, for Xen Orchestra we have the API set, but it would still be very beneficial to get the original plan of @olivierlambert in this blog post, back on track.

I could provide a WHMCS test setup, people for testing (agents of hosting companies), and participate as much as my limited programming skills allow