Chapter 18. Common administrative networking tasks

Procedure

1. Log in to the undercloud as the stack user, and source the stackrc file to enable the director command line tools.

   Example

   $ source ~/stackrc

   Copy to Clipboard

2. Create a custom YAML environment file.

   Example

   $ vi /home/stack/templates/my-neutron-environment.yaml

   Copy to Clipboard

   Tip

   The Red Hat OpenStack Platform Orchestration service (heat) uses a set of plans called templates to install and configure your environment. You can customize aspects of the overcloud with a custom environment file, which is a special type of template that provides customization for your heat templates.

3. In the YAML environment file, increase the VRRP advertisement interval using the ha_vrrp_advert_int argument with a value specific for your site. (The default is 2 seconds.)

   You can also set values for gratuitous ARP messages:

   ha_vrrp_garp_master_repeat

   The number of gratuitous ARP messages to send at one time after the transition to the master state. (The default is 5 messages.)

   ha_vrrp_garp_master_delay

   The delay for second set of gratuitous ARP messages after the lower priority advert is received in the master state. (The default is 5 seconds.)

   Example

   parameter_defaults:
     ControllerExtraConfig:
       neutron::agents::l3::ha_vrrp_advert_int: 7
       neutron::config::l3_agent_config:
         DEFAULT/ha_vrrp_garp_master_repeat:
           value: 5
         DEFAULT/ha_vrrp_garp_master_delay:
           value: 5

   Copy to Clipboard

4. Run the openstack overcloud deploy command and include the core heat templates, environment files, and this new custom environment file.

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   Example

   $ openstack overcloud deploy --templates \
   -e [your-environment-files] \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-neutron-environment.yaml

   Copy to Clipboard

Procedure

1. Log in to the undercloud as the stack user, and source the stackrc file to enable the director command line tools.

   Example

   $ source ~/stackrc

   Copy to Clipboard

2. Create a custom YAML environment file (my-neutron-environment.yaml).

   Note

   Values inside parentheses are sample values that are used in the example commands in this procedure. Substitute these sample values with ones that are appropriate for your site.

   Example

   $ vi /home/stack/templates/my-neutron-environment.yaml

   Copy to Clipboard

   Tip

   The undercloud includes a set of Orchestration service templates that form the plan for your overcloud creation. You can customize aspects of the overcloud with environment files, which are YAML-formatted files that override parameters and resources in the core Orchestration service template collection. You can include as many environment files as necessary.

3. In the environment file, add a parameter_defaults section. Under this section, add the dns_domain for ports extension, dns_domain_ports.

   Example

   parameter_defaults:
     NeutronPluginExtensions: "qos,port_security,dns_domain_ports"

   Copy to Clipboard

   Note

   If you set dns_domain_ports, ensure that the deployment does not also use dns_domain, the DNS Integration extension. These extensions are incompatible, and both extensions cannot be defined simultaneously.

4. Also in the parameter_defaults section, add your domain name (example.com) using the NeutronDnsDomain parameter.

   Example

   parameter_defaults:
       NeutronPluginExtensions: "qos,port_security,dns_domain_ports"
       NeutronDnsDomain: "example.com"

   Copy to Clipboard

5. Run the openstack overcloud deploy command and include the core Orchestration templates, environment files, and this new environment file.

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   Example

   $ openstack overcloud deploy --templates \
   -e [your-environment-files] \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-neutron-environment.yaml

   Copy to Clipboard

Verification

1. Log in to the overcloud, and create a new port (new_port) on a network (public). Assign a DNS name (my_port) to the port.

   Example

   $ source ~/overcloudrc
   $ openstack port create --network public --dns-name my_port new_port

   Copy to Clipboard

2. Display the details for your port (new_port).

   Example

   $ openstack port show -c dns_assignment -c dns_domain -c dns_name -c name new_port

   Copy to Clipboard

   Output

   +-------------------------+----------------------------------------------+
   | Field                   | Value                                        |
   +-------------------------+----------------------------------------------+
   | dns_assignment          | fqdn='my_port.example.com',                  |
   |                         | hostname='my_port',                          |
   |                         | ip_address='10.65.176.113'                   |
   | dns_domain              | example.com                                  |
   | dns_name                | my_port                                      |
   | name                    | new_port                                     |
   +-------------------------+----------------------------------------------+

   Copy to Clipboard

   Under dns_assignment, the fully qualified domain name (fqdn) value for the port contains a concatenation of the DNS name (my_port) and the domain name (example.com) that you set earlier with NeutronDnsDomain.

3. Create a new VM instance (my_vm) using the port (new_port) that you just created.

   Example

   $ openstack server create --image rhel --flavor m1.small --port new_port my_vm

   Copy to Clipboard

4. Display the details for your port (new_port).

   Example

   $ openstack port show -c dns_assignment -c dns_domain -c dns_name -c name new_port

   Copy to Clipboard

   Output

   +-------------------------+----------------------------------------------+
   | Field                   | Value                                        |
   +-------------------------+----------------------------------------------+
   | dns_assignment          | fqdn='my_vm.example.com',                    |
   |                         | hostname='my_vm',                            |
   |                         | ip_address='10.65.176.113'                   |
   | dns_domain              | example.com                                  |
   | dns_name                | my_vm                                        |
   | name                    | new_port                                     |
   +-------------------------+----------------------------------------------+

   Copy to Clipboard

   Note that the Compute service changes the dns_name attribute from its original value (my_port) to the name of the instance with which the port is associated (my_vm).

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the undercloud credentials file:

   $ source ~/stackrc

   Copy to Clipboard

3. Create a custom YAML environment file.

   Example

   $ vi /home/stack/templates/my-octavia-environment.yaml

   Copy to Clipboard

4. Your environment file must contain the keywords parameter_defaults. Under these keywords, add the extra DHCP option extension, extra_dhcp_opt.

   Example

   parameter_defaults:
     NeutronPluginExtensions: "qos,port_security,extra_dhcp_opt"

   Copy to Clipboard

5. Run the deployment command and include the core heat templates, environment files, and this new custom environment file.

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   Example

   $ openstack overcloud deploy --templates \
   -e <your_environment_files> \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \
   -e /home/stack/templates/my-octavia-environment.yaml

   Copy to Clipboard

Verification

1. Source your credentials file.

   Example

   $ source ~/overcloudrc

   Copy to Clipboard

2. Create a new port (new_port) on a network (public). Assign a valid attribute from the DHCP specification to the new port.

   Example

   $ openstack port create --extra-dhcp-option \
   name=domain-name,value=test.domain --extra-dhcp-option \
   name=ntp-server,value=192.0.2.123 --network public new_port

   Copy to Clipboard

3. Display the details for your port (new_port).

   Example

   $ openstack port show new_port -c extra_dhcp_opts

   Copy to Clipboard

   Sample output

   +-----------------+-----------------------------------------------------------------+
   | Field           | Value                                                           |
   +-----------------+-----------------------------------------------------------------+
   | extra_dhcp_opts | ip_version='4', opt_name='domain-name', opt_value='test.domain' |
   |                 | ip_version='4', opt_name='ntp-server', opt_value='192.0.2.123'  |
   +-----------------+-----------------------------------------------------------------+

   Copy to Clipboard

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the undercloud credentials file:

   $ source ~/stackrc

   Copy to Clipboard

3. To enable the port_numa_affinity_policy extension, open the environment file where the NeutronPluginExtensions parameter is defined, and add port_numa_affinity_policy to the list:

   parameter_defaults:
     NeutronPluginExtensions: "qos,port_numa_affinity_policy"

   Copy to Clipboard

4. Add the environment file that you modified to the stack with your other environment files, and redeploy the overcloud:

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   $ openstack overcloud deploy --templates \
   -e <your_environment_files> \
   -e /home/stack/templates/<custom_environment_file>.yaml

   Copy to Clipboard

Verification

1. Source your credentials file.

   Example

   $ source ~/overcloudrc

   Copy to Clipboard

2. Create a new port.

   When you create a port, use one of the following options to specify the NUMA affinity policy to apply to the port:

   • --numa-policy-required - NUMA affinity policy required to schedule this port.
   • --numa-policy-preferred - NUMA affinity policy preferred to schedule this port.

   • --numa-policy-legacy - NUMA affinity policy using legacy mode to schedule this port.

     Example

     $ openstack port create --network public \
       --numa-policy-legacy  myNUMAAffinityPort

     Copy to Clipboard

3. Display the details for your port.

   Example

   $ openstack port show myNUMAAffinityPort -c numa_affinity_policy

   Copy to Clipboard

   Sample output

   When the extension is loaded, the Value column should read, legacy, preferred or required. If the extension has failed to load, Value reads None:

   +----------------------+--------+
   | Field                | Value  |
   +----------------------+--------+
   | numa_affinity_policy | legacy |
   +----------------------+--------+

   Copy to Clipboard

Procedure

1. On the undercloud host, logged in as the stack user, create a custom YAML environment file.

   Example

   $ vi /home/stack/templates/my-modules-environment.yaml

   Copy to Clipboard

   Tip

   Heat uses a set of plans called templates to install and configure your environment. You can customize aspects of the overcloud with a custom environment file, which is a special type of template that provides customization for your heat templates.

2. In the YAML environment file under parameter_defaults, set ExtraKernelModules to the name of the module that you want to load.

   Example

   ComputeParameters:
     ExtraKernelModules:
       nf_conntrack_proto_gre: {}
   ControllerParameters:
     ExtraKernelModules:
       nf_conntrack_proto_gre: {}

   Copy to Clipboard

3. Run the openstack overcloud deploy command and include the core heat templates, environment files, and this new custom environment file.

   Important

   The order of the environment files is important as the parameters and resources defined in subsequent environment files take precedence.

   Example

   $ openstack overcloud deploy --templates \
   -e [your-environment-files] \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/my-modules-environment.yaml

   Copy to Clipboard

Procedure

1. Log in to the overcloud for the current project that contains the security group.

2. Obtain the name or ID of the target project.

   $ openstack project list

   Copy to Clipboard

3. Obtain the name or ID of the security group that you want to share between RHOSP projects.

   $ openstack security group list

   Copy to Clipboard

4. Using the identifiers from the previous steps, create an RBAC policy using the openstack network rbac create command.

   In this example, the ID of the target project is 32016615de5d43bb88de99e7f2e26a1e. The ID of the security group is 5ba835b7-22b0-4be6-bdbe-e0722d1b5f24:

   Example

   $ openstack network rbac create --target-project \
   32016615de5d43bb88de99e7f2e26a1e --action access_as_shared \
   --type security_group 5ba835b7-22b0-4be6-bdbe-e0722d1b5f24

   Copy to Clipboard

   --target-project

   specifies the project that requires access to the security group.

   Tip

   You can share data between all projects by using the --target-all-projects argument instead of --target-project <target-project>. By default, only the admin user has this privilege.

   --action access_as_shared

   specifies what the project is allowed to do.

   --type

   indicates that the target object is a security group.

   5ba835b7-22b0-4be6-bdbe-e0722d1b5f24

   is the ID of the particular security group which is being granted access to.