Chapter 8. Performing overcloud post-installation tasks

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the deployment status command:

   $ openstack overcloud status

   Copy to Clipboard Toggle word wrap

   The output of this command displays the status of the overcloud:

   +-----------+---------------------+---------------------+-------------------+
   | Plan Name |       Created       |       Updated       | Deployment Status |
   +-----------+---------------------+---------------------+-------------------+
   | overcloud | 2018-05-03 21:24:50 | 2018-05-03 21:27:59 |   DEPLOY_SUCCESS  |
   +-----------+---------------------+---------------------+-------------------+

   Copy to Clipboard Toggle word wrap

   If your overcloud uses a different name, use the --stack argument to select an overcloud with a different name:

   $ openstack overcloud status --stack <overcloud_name>

   Copy to Clipboard Toggle word wrap
   • Replace <overcloud_name> with the name of your overcloud.

Procedure

1. Source the overcloudrc file:

   $ source ~/overcloudrc

   Copy to Clipboard Toggle word wrap

2. Run the openstack flavor create command to create a flavor. Use the following options to specify the hardware requirements for each flavor:

   --disk

   Defines the hard disk space for a virtual machine volume.

   --ram

   Defines the RAM required for a virtual machine.

   --vcpus

   Defines the quantity of virtual CPUs for a virtual machine.

3. The following example creates the default overcloud flavors:

   $ openstack flavor create m1.tiny --ram 512 --disk 0 --vcpus 1
   $ openstack flavor create m1.smaller --ram 1024 --disk 0 --vcpus 1
   $ openstack flavor create m1.small --ram 2048 --disk 10 --vcpus 1
   $ openstack flavor create m1.medium --ram 3072 --disk 10 --vcpus 2
   $ openstack flavor create m1.large --ram 8192 --disk 10 --vcpus 4
   $ openstack flavor create m1.xlarge --ram 8192 --disk 10 --vcpus 8

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the overcloudrc file:

   $ source ~/overcloudrc

   Copy to Clipboard Toggle word wrap

2. Create the default Tenant network:

   (overcloud) $ openstack network create default

   Copy to Clipboard Toggle word wrap

3. Create a subnet on the network:

   (overcloud) $ openstack subnet create default --network default --gateway 172.20.1.1 --subnet-range 172.20.0.0/16

   Copy to Clipboard Toggle word wrap

4. Confirm the created network:

   (overcloud) $ openstack network list
   +-----------------------+-------------+--------------------------------------+
   | id                    | name        | subnets                              |
   +-----------------------+-------------+--------------------------------------+
   | 95fadaa1-5dda-4777... | default     | 7e060813-35c5-462c-a56a-1c6f8f4f332f |
   +-----------------------+-------------+--------------------------------------+

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the overcloudrc file:

   $ source ~/overcloudrc

   Copy to Clipboard Toggle word wrap

2. Create the public network:

   • Create a flat network for a native VLAN connection:

     (overcloud) $ openstack network create public --external --provider-network-type flat --provider-physical-network datacentre

     Copy to Clipboard Toggle word wrap

   • Create a vlan network for non-native VLAN connections:

     (overcloud) $ openstack network create public --external --provider-network-type vlan --provider-physical-network datacentre --provider-segment 201

     Copy to Clipboard Toggle word wrap

     Use the --provider-segment option to define the VLAN that you want to use. In this example, the VLAN is 201.

3. Create a subnet with an allocation pool for floating IP addresses. In this example, the IP range is 10.1.1.51 to 10.1.1.250:

   (overcloud) $ openstack subnet create public --network public --dhcp --allocation-pool start=10.1.1.51,end=10.1.1.250 --gateway 10.1.1.1 --subnet-range 10.1.1.0/24

   Copy to Clipboard Toggle word wrap

   Ensure that this range does not conflict with other IP addresses in your external network.

Procedure

1. Source the overcloudrc file:

   $ source ~/overcloudrc

   Copy to Clipboard Toggle word wrap

2. Create the provider network:

   • Create a flat network for a native VLAN connection:

     (overcloud) $ openstack network create provider --external --provider-network-type flat --provider-physical-network datacentre --share

     Copy to Clipboard Toggle word wrap

   • Create a vlan network for non-native VLAN connections:

     (overcloud) $ openstack network create provider --external --provider-network-type vlan --provider-physical-network datacentre --provider-segment 201 --share

     Copy to Clipboard Toggle word wrap
     • Use the --provider-segment option to define the VLAN that you want to use. In this example, the VLAN is 201.
     • Use the --share option to create a shared network. Alternatively, specify a tenant instead of specifying --share, so that only the tenant has access to the new network.
     • Use the --external option to mark a provider network as external. Only the operator can create ports on an external network.

3. Add a subnet to the provider network to provide DHCP services:

   (overcloud) $ openstack subnet create provider-subnet --network  provider --dhcp --allocation-pool start=10.9.101.50,end=10.9.101.100 --gateway 10.9.101.254 --subnet-range 10.9.101.0/24

   Copy to Clipboard Toggle word wrap

4. Create a router so that other networks can route traffic through the provider network:

   (overcloud) $ openstack router create external

   Copy to Clipboard Toggle word wrap

5. Set the external gateway for the router to the provider network:

   (overcloud) $ openstack router set --external-gateway provider external

   Copy to Clipboard Toggle word wrap

6. Attach other networks to this router. For example, run the following command to attach a subnet subnet1 to the router:

   (overcloud) $ openstack router add subnet external subnet1

   Copy to Clipboard Toggle word wrap

   This command adds subnet1 to the routing table and allows traffic from virtual machines using subnet1 to route to the provider network.

Procedure

1. To map a new bridge called br-floating to the floating physical network, include the NeutronBridgeMappings parameter in an environment file:

   parameter_defaults:
     NeutronBridgeMappings: "datacentre:br-ex,floating:br-floating"

   Copy to Clipboard Toggle word wrap

2. With this method, you can create separate external networks after creating the overcloud. For example, to create a floating IP network that maps to the floating physical network, run the following commands:

   $ source ~/overcloudrc
   (overcloud) $ openstack network create public --external --provider-physical-network floating --provider-network-type vlan --provider-segment 105
   (overcloud) $ openstack subnet create public --network public --dhcp --allocation-pool start=10.1.2.51,end=10.1.2.250 --gateway 10.1.2.1 --subnet-range 10.1.2.0/24

   Copy to Clipboard Toggle word wrap

Procedure

1. If you run this test from the undercloud, ensure that the undercloud host has access to the Internal API network on the overcloud. For example, add a temporary VLAN on the undercloud host to access the Internal API network (ID: 201) using the 172.16.0.201/24 address:

   $ source ~/stackrc
   (undercloud) $ sudo ovs-vsctl add-port br-ctlplane vlan201 tag=201 -- set interface vlan201 type=internal
   (undercloud) $ sudo ip l set dev vlan201 up; sudo ip addr add 172.16.0.201/24 dev vlan201

   Copy to Clipboard Toggle word wrap
2. Run the integration tests as described in the Validating your cloud with the Red Hat OpenStack Platform Integration Test Suite.

3. After completing the validation, remove any temporary connections to the overcloud Internal API. In this example, use the following commands to remove the previously created VLAN on the undercloud:

   $ source ~/stackrc
   (undercloud) $ sudo ovs-vsctl del-port vlan201

   Copy to Clipboard Toggle word wrap

Procedure

1. Create an environment file named prevent-stack-delete.yaml.

2. Set the HeatApiPolicies parameter:

   parameter_defaults:
     HeatApiPolicies:
       heat-deny-action:
         key: 'actions:action'
         value: 'rule:deny_everybody'
       heat-protect-overcloud:
         key: 'stacks:delete'
         value: 'rule:deny_everybody'

   Copy to Clipboard Toggle word wrap
   • The heat-deny-action is a default policy that you must include in your undercloud installation.

   • Set the heat-protect-overcloud policy to rule:deny_everybody to prevent anyone from deleting any stacks in the overcloud.

     Note

     Setting the overcloud protection to rule:deny_everybody means that you cannot perform any of the following functions:

     • Delete the overcloud.
     • Remove individual Compute or Storage nodes.
     • Replace Controller nodes.

3. Add the prevent-stack-delete.yaml environment file to the custom_env_files parameter in the undercloud.conf file:

   custom_env_files = prevent-stack-delete.yaml

   Copy to Clipboard Toggle word wrap

4. Run the undercloud installation command to refresh the configuration:

   $ openstack undercloud install

   Copy to Clipboard Toggle word wrap