Ensure that your OpenStack environment meets the software prerequisites for your IBM® Cloud Orchestrator installation. You can either install IBM Cloud Manager with OpenStack that is part of the IBM Cloud Orchestrator product or you can install an OpenStack distribution of another vendor (Bring your own OpenStack). Note that you can connect IBM Cloud Orchestrator only to a single OpenStack instance (one-to-one mapping).
Ensure that IBM Cloud Manager with OpenStack V4.3 Fix Pack 2 is installed (OpenStack Kilo release). For information about IBM Cloud Manager with OpenStack prerequisites, see the IBM Cloud Manager with OpenStack documentation.
The IBM Cloud Manager with OpenStack installation uses a single Keystone service. In a multi-region installation, the Keystone service must run on the OpenStack Controller of the first region that is installed. OpenStack's Identity Federation is not supported by IBM Cloud Orchestrator.
The IBM Cloud Manager with OpenStack installation is a fresh installation. No users, projects, or domains are defined other than those that are created during the basic OpenStack installation.
A parallel usage of the IBM Cloud Manager with OpenStack installation through IBM Cloud Orchestrator and standard OpenStack is not supported. If an IBM Cloud Manager with OpenStack installation is configured to be used by IBM Cloud Orchestrator, all user activities must be done through the IBM Cloud Orchestrator interface, and not through the OpenStack interfaces. The OpenStack Self-Service interface must only be used as described in the IBM Cloud Orchestrator documentation.
Each region must have only one hypervisor type. IBM Cloud Orchestrator does not support using multiple types of hypervisor within a region.
The IBM Cloud Manager with OpenStack distribution provides the simple token enhancement that is required and used by IBM Cloud Orchestrator. For more information about how to set up the simple token, see Customizing passwords and secrets and Data bags in the IBM Cloud Manager with OpenStack documentation.
The self-service user interface extension of IBM Cloud Manager with OpenStack does not work with IBM Cloud Orchestrator and it must not be installed. If it is installed, see Uninstalling the self-service user interface on Linux to uninstall it.
force_config_drive=always
customization_enabled = false
the sections where to insert
them is for force_config_drive:[DEFAULT]
while
for customization_enabled is:[vmware]
then
restart the compute service. The file name is customized from the
cluster name that is specified instead of reporting the default value.For general OpenStack requirements, see the documentation for your chosen OpenStack product.
OpenStack Kilo release is installed. Refer to the documentation of your OpenStack product.
The OpenStack installation uses a single Keystone service. Federation is not supported. For more information, see your OpenStack documentation.
The OpenStack installation is a fresh installation. No users, projects, or domains are defined other than those that are created during the basic OpenStack installation.
A parallel usage of the OpenStack installation through IBM Cloud Orchestrator and standard OpenStack is not supported. If an OpenStack installation is configured to be used by IBM Cloud Orchestrator, all user activities must be done through the IBM Cloud Orchestrator interface, and not through the OpenStack interfaces. The OpenStack interfaces must only be used as described in the IBM Cloud Orchestrator documentation.
You must install Horizon extensions, as described in Installing the IBM Cloud Orchestrator extensions for Horizon.
You must reconfigure Keystone, as described in Configuring V3 API endpoints for Keystone.
You must create IBM Cloud Orchestrator specific roles, projects, and users, as described in Adding roles, users, and projects to Keystone.
The Cinder V1 API must be enabled and V1 endpoints must be defined, as described in Enabling the Cinder V1 API.
Multiple regions are allowed, but they must use one shared Keystone. Each region must have only one hypervisor type. IBM Cloud Orchestrator does not support using multiple types of hypervisor within a region.
Extensions to Keystone must be installed. IBM Cloud Orchestrator needs a simple token security provider to be installed on Keystone.
In certain situations vendor-specific OpenStack distribution extensions might not work with IBM Cloud Orchestrator. A vendor-specific distribution must comply the IBM Cloud Orchestrator’s prerequisites. In addition, the OpenStack distribution must be reconfigured and enhanced to the needs of IBM Cloud Orchestrator. Otherwise, the OpenStack distribution of this vendor is not supported by IBM Cloud Orchestrator.
Depending on the database backend, OpenStack might be case-sensitive.