Deploying Cloud Infrastructure Automation

Before you start setting up the Cloud Infrastructure Automation module, make sure that CloudBlue Commerce Linux platform is deployed. For detailed deployment instructions, refer to CloudBlue Commerce Linux Platform Deployment Guide.

Note: HTML5 VNC console uses the modern web-socket based protocol. For a RHEL6-based UI/branding node there is an issue related to malfunctioning mod_rewrite module that is unable to pass such requests as a proxy. The issue has no solution for RHEL6. See for more details. You should ensure that UI/branding nodes have RHEL7 based OS and the installed Apache web server on the UI/branding node can process and proxy websocket URIs.

To deploy the Cloud Infrastructure Automation, do the following:

  1. Prepare the CI Endpoint node and register it in CloudBlue Commerce.
  2. Download the Cloud Infrastructure Automation package to the management node and run the installation.
  3. Install the Cloud Infrastructure Automation in CloudBlue Commerce.
  4. Update the c2u_settings in the OSS DB.
  5. Disable HW node management in service controller.
  6. Install the Cloud Infrastructure Automation APS package on the management node.
  7. Install the CI Endpoint ppm.
  8. Set up the Instance Manager and its database.
  9. Set up the network:
    • Create a public IP pool.
    • Create a private IP pool.
    • Create a network group.
  10. Add virtualization and backup nodes:
    • Add virtualization nodes.
    • (Optional) Add Virtuozzo storage high availability cluster.
    • (Optional) Add backup nodes.

Important: The time settings should be synchronized among all Cloud Infrastructure Automation nodes otherwise the IM outage can occur. For example, you can use the NTP protocol to synchronize the time on Cloud Infrastructure Automation nodes over a network. For more information about NTP, visit