This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.Chapter 18. Configuring for OpenStack
18.1. Overview Copy linkLink copied to clipboard!
When deployed on OpenStack, OpenShift Container Platform can be configured to access OpenStack infrastructure, including using OpenStack Cinder volumes as persistent storage for application data.
18.2. Configuring OpenStack Variables Copy linkLink copied to clipboard!
To set the required OpenStack variables, create a /etc/cloud.conf file with the following contents on all of your OpenShift Container Platform hosts, both masters and nodes:
Consult your OpenStack administrators for values of the OS_
variables, which are commonly used in OpenStack configuration.
18.3. Configuring OpenShift Container Platform Masters for OpenStack Copy linkLink copied to clipboard!
You can set an OpenStack configuration on your OpenShift Container Platform master and node hosts in two different ways:
- Using Ansible and the advanced installation tool
- Manually, by modifying the master-config.yaml and node-config.yaml files.
18.3.1. Configuring OpenShift Container Platform for OpenStack with Ansible Copy linkLink copied to clipboard!
During advanced installations, OpenStack can be configured using the following parameters, which are configurable in the inventory file:
-
openshift_cloudprovider_kind
-
openshift_cloudprovider_openstack_auth_url
-
openshift_cloudprovider_openstack_username
-
openshift_cloudprovider_openstack_password
-
openshift_cloudprovider_openstack_domain_id
-
openshift_cloudprovider_openstack_domain_name
-
openshift_cloudprovider_openstack_tenant_id
-
openshift_cloudprovider_openstack_tenant_name
-
openshift_cloudprovider_openstack_region
-
openshift_cloudprovider_openstack_lb_subnet_id
Example 18.1. Example OpenStack Configuration with Ansible
18.3.2. Manually Configuring OpenShift Container Platform Masters for OpenStack Copy linkLink copied to clipboard!
Edit or create the master configuration file on all masters (/etc/origin/master/master-config.yaml by default) and update the contents of the apiServerArguments
and controllerArguments
sections:
When triggering a containerized installation, only the directories of /etc/origin and /var/lib/origin are mounted to the master and node container. Therefore, cloud.conf should be in /etc/origin/ instead of /etc/.
18.3.3. Manually Configuring OpenShift Container Platform Nodes for OpenStack Copy linkLink copied to clipboard!
Edit or create the node configuration file on all nodes (/etc/origin/node/node-config.yaml by default) and update the contents of the kubeletArguments
and nodeName
sections:
- 1
- Name of the OpenStack instance where the node runs (i.e., name of the virtual machine)
When triggering a containerized installation, only the directories of /etc/origin and /var/lib/origin are mounted to the master and node container. Therefore, cloud.conf should be in /etc/origin/ instead of /etc/.