@@ -276,6 +276,57 @@ Sometimes it's necessary to find out why a stack was not deployed as expected.
276276link:README_debugging.adoc[Debugging] helps you find the root cause of the
277277issue.
278278
279+ == OpenStack Integration
280+
281+ OpenShift on OpenStack takes advantage of the cloud provider to offer
282+ features such as dymaic storage to the OpenShift users. Auto scaling
283+ also requires communication with the OpenStack service. You must
284+ provide a set of OpenStack credentials so that OpenShift and the heat
285+ scaling mechanism can work correctly.
286+
287+ These are the same values used to create the Heat stack.
288+
289+ .Sample OSP Credentials - `osp_credentials.yaml`
290+ ----
291+ ---
292+ parameters:
293+ os_auth_url: http://10.0.x.x:5000/v2.0
294+ os_username: <username>
295+ os_password: <password>
296+ os_region_name: regionOne
297+ os_tenant_name: <tenant name>
298+ ----
299+
300+ When invoking the stack creation, include this by adding `-e
301+ osp_credentials.yaml` to the command.
302+
303+ == [[ca-certificates]]OpenStack with SSL/TLS
304+
305+ If your OpenStack service is encrypted with SSL/TLS, you will need to
306+ provide the CA certificate so that the communication channel can be
307+ validated.
308+
309+ The CA certificate is provided as a literal string copy of contents of
310+ the CA certificate file, and can be included in an additional
311+ environment file:
312+
313+ .CA Certificate Parameter File `ca_certificates.yaml`
314+ ----
315+ ---
316+ parameters:
317+ ca_cert: |
318+ -----BEGIN CERTIFICATE-----
319+ ...
320+ -----END CERTIFICATE-----
321+ ----
322+
323+ When invoking the stack creation, includ this by adding `-e
324+ ca_certificates.yaml`.
325+
326+ You can include multiple CA certificate strings and all will be imported
327+ into the CA list on all instances.
328+
329+
279330== Multiple Master Nodes
280331
281332You can deploy OpenShift with multiple master hosts using the 'native'
@@ -385,15 +436,15 @@ when you create the stack.
385436
386437Example of `env_ldap.yaml` using an Active Directory server:
387438
388- ```yaml
439+ .LDAP parameter file `env_ldap.yaml
440+ ----
389441parameter_defaults:
390442 ldap_hostname: <ldap hostname>
391443 ldap_ip: <ip of ldap server>
392444 ldap_url: ldap://<ldap hostname>:389/CN=Users,DC=example,DC=openshift,DC=com?sAMAccountName
393445 ldap_bind_dn: CN=Administrator,CN=Users,DC=example,DC=openshift,DC=com?sAMAccountName
394446 ldap_bind_password: <admin password>
395- ```
396-
447+ ----
397448
398449```bash
399450heat stack-create my-openshift \
@@ -402,6 +453,8 @@ heat stack-create my-openshift \
402453 -f openshift-on-openstack/openshift.yaml
403454```
404455
456+ If your LDAP service uses SSL, you will also need to add a link:#ca-certificates[CA Certficate] for the LDAP communications.
457+
405458== Using Custom Yum Repositories
406459
407460You can set additional Yum repositories on deployed nodes by passing `extra_repository_urls`
@@ -513,7 +566,7 @@ the `dns_nameserver` list.
513566You will still need to set the API and wildcard entries, though.
514567
515568
516- == Retrieving the CA certificate
569+ == Retrieving the OpenShift CA certificate
517570
518571You can retrieve the CA certificate that was generated during the OpenShift
519572installation by running
0 commit comments