Provides automated setup of RDO with various deployment scenarios. The deployment scenarios mainly focus on Keystone and integration with external identity sources.

Automation typically covers creation of VMs created from cloud images, installation and configuration of RDO, and installation and configuration of other software that is needed for the particular scenario (such as Active Directory or FreeIPA).

These scripts have been tested on Fedora 20 and RHEL 7. The scripts will attempt to set up your environment for you the first time they are run, which includes cloning required git repos and installing required packages.

Global configuration is defined in global.conf. This mainly consists of virtual network settings that will be used by the VMs that are created by the individual scenarios.

Scenario specific configuration is defined in individual .conf files. Each VM has it's own conf file, which defines things such as the OS image and package repositories that should be used, packages to install, and user and password information. The actual configuration steps that are used to set up software after VM creation are in cloud-init user-data scripts, which are prefixed with 'vm-post-cloud-init-'.

To deploy a particular scenario, you should just be able to run 'setup.sh' in the scenario directory that you want to deploy. This needs to be run as a user with passwordless sudo abilities. The first time a particular scenario is run, the OS images used to install the VMs will be downloaded. The downloaded images will be reused on subsequent runs.

Once a VM is initially created, you can ssh into it and follow the progress by tailing the following log files:

• /var/log/cloud-init.log - initial VM creation and package installtion

• /var/log/vm-post-cloud-init-*.sh.log - user-data script execution

When you are finished with the VMs, you can just run cleanup.sh in the scenario directory to clean everything up.

This scenario sets up Active Directory on one VM and RDO on a second. Deployment details include:

• Keystone depolyed in eventlet (keystone-all)
• Active Directory set up as LDAP identity backend
• Service users created in Active Directory (no Keystone domains)

The Windows 2008 Server evaluation image will be automatically downloaded from Microsoft the first time that this scenario is set up, which will take some time to complete. On subsequent runs, a converted qcow2 image will be reused without requiring another download process.

A v3 keystonerc file is created in addition to the standard keystonerc files that are created by packstack.

This scenario sets up FreeIPA and Ipsilon on one VM and RDO on a second. Deployment details include:

• Keystone running in httpd
• SQL identity backend
• OS-FEDERATION extension configured for SAML authentication
• Ipsilon configured for Kerberos authentication

There are a few manual steps that need to be completed before SAML authentication to Keystone will work. Ipsilon doesn't currently have a way for us to set up Keystone as a SP in an automated way. The following steps are needed to complete the registration in Ipsilon:

• The SP metadata for Keystone needs to be copied from the RDO vm to the Ipsilon VM. This can be copied over by running:

  scp /etc/http/mellon/http_rdo.rdodom.test_keystone.xml [email protected]:~

• Connect to the Ipsilon VM using 'ssh -X' to allow a browser to be used.

• Obtain a Kerberos ticket for the admin user with 'kinit admin'.

• Run firefox and configure it for IPA by connecting to ipa.rdodom.test and run through the setup wizard.

• Connect to https://ipa.rdodom.test/idp with the browser, login as the admin user via Kerberos, then add the SP by navigating to:

  Identity Providers->saml2->Manage->Add New

• Name the Service Provider, select the metadata xml that was copied over via the browse dialog, then click 'Save'.

At this point, the SP is registered. You can attempt to obtain a Keystone token via SAML federation by going to the following URL in the browser:

http://rdo.rdodom.test:5000/v3/OS-FEDERATION/identity_providers/ipsilon/protocols/saml2/auth

The token body should be displayed if you have a valid Kerberos ticket that is used to authenticate to the Ipsilon IdP.

This scenario sets up FreeIPA on one VM and RDO on a second. Deployment details include:

• Keystone running in httpd
• v3 cloud sample policy is used for a multi-domain deployment
• cloud_admin administers the overall cloud (admin_domain)
• Service users live in the 'default' domain
• FreeIPA set up as a separate Keystone domain using LDAP identity
• FreeIPA 'admin' user administers the FreeIPA domain
• Kerberos authentication is configured for Keystone at /krb

When the deployment is complete, you should be able to do the following to test Kerberos authentication:

[rdouser@rdo]$ source ~/keystonerc_kerberos 
[rdouser@rdo ~(keystone_kerberos)]$ kinit admin
Password for [email protected]: 
[rdouser@rdo ~(keystone_kerberos)]$ openstack role list
+----------------------------------+---------------+
| ID                               | Name          |
+----------------------------------+---------------+
| 22b79d81c9ed48dda625bf7de6df7645 | admin         |
| 45ec68348ee84917a992d4e401d253d8 | ResellerAdmin |
| 89ac3797a4ef46d89c0a9f69a1de6851 | SwiftOperator |
| 9fe2ff9ee4384b1894a90878d3e92bab | _member_      |
+----------------------------------+---------------+
[rdouser@rdo ~(keystone_kerberos)]$

Other keystonerc files are supplied to perform tasks as the cloud admin, or for non-kerberized FreeIPA admin tasks.