Tripleo OSP with Red Hat Subscriptions¶

Undercloud¶

To deploy OSP, the Undercloud must be registered to Red Hat channels.

The value for pool can be obtained by executing the following command on an existing registered host:

subscription-manager list --available --matches='Red Hat OpenStack' --pool-only

Define the subscription details:

undercloud_cdn.yml¶

---
username: 'infrared.user@example.com'
password: '123456'
pool_ids: '1234567890abcdefghijklmnopqrstuv'

Warning

During run time, contents of the file are hidden from the logged output, to protect private account credentials.

For the full list of supported input, see the Ansible module documentation.

Note

Pre-registered undercloud is also supported if --cdn flag is missing.

Deploy your undercloud. It’s recommended to use --images-task rpm to fetch pre-packaged images that are only available via Red Hat channels:

infrared tripleo-undercloud --version 10 --cdn undercloud_cdn.yml --images-task rpm

Warning

--images-update is not supported with cdn.

Overcloud¶

Once the undercloud is registered, the overcloud can be deployed. However, the overcloud nodes will not be registered and cannot receive updates. While the nodes can be later registered manually, Tripleo provides a way to register them automatically on deployment.

According to the guide there are 2 heat-templates required. They can be included, and their defaults overridden, using a custom templates file. For registration to the customer portal, the minimum required fields are:

rhel_reg_method
rhel_reg_org
rhel_reg_user & rhel_reg_password
rhel_reg_pool_id
rhel_reg_repos

The value for rhel_reg_org can be obtained by issuing the following command on an existing registered host:

subscription-manager identity

The value for rhel_reg_pool_id can be obtained by executing the following command on an existing registered host:

subscription-manager list --available --matches='Red Hat OpenStack' --pool-only

overcloud_cdn.yml¶

---
tripleo_heat_templates:
    - /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml
    - /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/environment-rhel-registration.yaml

custom_templates:
    parameter_defaults:
        rhel_reg_activation_key: ""
        rhel_reg_org: "12345678"
        rhel_reg_pool_id: "1234567890abcdefghijklmnopqrstuv"
        rhel_reg_method: "portal"
        rhel_reg_sat_url: ""
        rhel_reg_sat_repo: ""
        rhel_reg_repos: "rhel-7-server-rpms,rhel-7-server-extras-rpms,rhel-7-server-rh-common-rpms,rhel-ha-for-rhel-7-server-rpms,rhel-7-server-openstack-10-rpms,rhel-7-server-rhceph-2-osd-rpms,rhel-7-server-rhceph-2-mon-rpms,rhel-7-server-rhceph-2-tools-rpms,rhel-7-server-satellite-tools-6.2-rpms"
        rhel_reg_auto_attach: ""
        rhel_reg_base_url: ""
        rhel_reg_environment: ""
        rhel_reg_force: ""
        rhel_reg_machine_name: ""
        rhel_reg_password: "123456"
        rhel_reg_release: ""
        rhel_reg_server_url: ""
        rhel_reg_service_level: ""
        rhel_reg_user: "infrared.user@example.com"
        rhel_reg_type: ""
        rhel_reg_http_proxy_host: ""
        rhel_reg_http_proxy_port: ""
        rhel_reg_http_proxy_username: ""
        rhel_reg_http_proxy_password: ""

Note

Please note that the rhel_reg_repos in the file above are for OSP 10.

Deploy the overcloud with the custom templates file:

infrared tripleo-overcloud --version=10 --deployment-files=virt --introspect=yes --tagging=yes --deploy=yes --overcloud-templates overcloud_cdn.yml