Xen Orchestra is the management tool to administrate a XenServer and/or XCP-ng hypervisor infrastructure environment. This content capsule will integrate HCMX/CSA with your XO management stack, in order to easily consume XenServer/XCP-ng resources using HCMX/CSA.
Create a Xen Orchestra provider
Once this capsule has been imported into HCMX/CSA, create the Xen Orchestra provider.
Go to the provider definition page in HCMX/CSA, select the new Xen Orchestra provider type and click "create". Give the new provider a relevant name and description. The Service Access Point should be the FQDN or ip address of your Xen Orchestra (Appliance) instance. Because we will be connecting directly to the XO(A) host with SSH on port 22, you can use the following notation:
HCMX/CSA will complain that it cannot verify the Service Access Point but you can just ignore that message and carry on.
The credentials to use are the root credentials to the XO(A) instance. For instance:
Make sure the "Enabled" box is checked. Save the new provider by clicking on the "Create" button and again, ignore the HCMX/CSA verification message. The provider will be saved and active regardless.
Modify the Xen Orchestra Compute published offering
After the provider has been created, you can modify the associated offering. Go to published offerings, select the Xen Orchestra Compute offering and modify the options to reflect your Xen Orchestra environment. Change the template names to the proper ones in your XO(A) environment. Also modify the value of the network uuid property. To retrieve the network uuid, go into the XO(A) management web interface, select the pool you are using, select networks and copy the uuid from the appropriate network.
A note on templates
In order to successfully deploy new VMs using this Xen Orchestra content, you will need to use/create clone-able OS templates that already have the XE-guest utilities installed. To create a template in XO(A), use the XO(A) web interface and manually create a new VM, install the desired OS and install the XE-guest utilities on the system. Once satisfied with the system, shut it down and convert it to a template.
A note on XO/XOA
This content uses the XO-CLI command line tool on the XO/XOA server. Make sure to install the tool (as rot) using npm install --global xo-cli and make sure the user configured in the HCMX/CSA provider configuration is able to run the xo-cli command line tool
If you are using the latest XOA appliance, make sure to modify or disable the firewall. This content will open several sessions to the XOA server to provision resources and to get back information. The default XOA firewall configuration prevents access after the 5th connection withing 30 seconds. The command to disable the firewall is ufw disable or change the firewall to allow more connections per time-unit (consult your debian documentation for details on how to do that)
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
This release of the Xen Orchestra content capsule is updated to work with HCMX as well as CSA. Use the Content Management tab in HCMX to upload the capsule to into your HCMX environment. Once uploaded, create a resource provider for yout XO(A) server and adjust the Xen Orchestra Service Design to fit your environment, then publish it into a catalog and let your users consume Xen compute resources.
This release contains the capsule for integrating HCM/CSA with the Xen Orchestra (Appliance) management system, as well as the OO Studio project files (source code) for additional development.
This code is has been tested in a lab environment only, running CSA 4.92, CSA 4.93 together with XO Community 5.38.1 and XCP-ng version 7.6.0.
The capsule should be compatible with all latest versions of CSA, HCM, XCP-ng, WenServer, XO and XOA.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox