5장. Deploying a DCN node set

Procedure

1. Create a file on your workstation named dcn-data-plane-networks.yaml to define the OpenStackDataPlaneNodeSet CR that configures the data plane node networks:

   apiVersion: dataplane.openstack.org/v1beta1
   kind: OpenStackDataPlaneNodeSet
   metadata:
     name: dcn-data-plane-networks
     namespace: openstack
   spec:
     env:
       - name: ANSIBLE_FORCE_COLOR
         value: "True"

2. Specify the services to apply to the nodes:

   spec:
     ...
     services:
       - bootstrap
       - configure-network
       - validate-network
       - install-os
       - ceph-hci-pre
       - configure-os
       - ssh-known-hosts
       - run-os
       - reboot-os

3. Set the edpm_enable_chassis_gw and edpm_ovn_availability_zones fields on the data plane:

   spec:
     env:
     - name: ANSIBLE_FORCE_COLOR
       value: "True"
     networkAttachments:
     - ctlplane
     nodeTemplate:
       ansible:
         ansiblePort: 22
         ansibleUser: cloud-admin
         ansibleVars:
           edpm_enable_chassis_gw: true
           edpm_ovn_availability_zones:
             - az0

4. Optional: The ceph-hci-pre service prepares data plane nodes to host Red Hat Ceph Storage services after network configuration using the edpm_ceph_hci_pre edpm-ansible role. By default, the edpm_ceph_hci_pre_enabled_services parameter of this role only contains RBD, RGW, and NFS services. DCN only supports RBD services at DCN sites. If you are deploying HCI, disable the RGW and NFS services by adding the edpm_ceph_hci_pre_enabled_services parameter, and adding only ceph RBD services.

   apiVersion: dataplane.openstack.org/v1beta1
   kind: OpenStackDataPlaneNodeSet
   metadata:
     name: openstack-edpm
     namespace: openstack
   spec:
     env:
     - name: ANSIBLE_FORCE_COLOR
   	value: "True"
     networkAttachments:
     - ctlplane
     nodeTemplate:
   	ansible:
     	ansiblePort: 22
     	ansibleUser: cloud-admin
     	ansibleVars:
       	edpm_ceph_hci_pre_enabled_services:
       	- ceph_mon
       	- ceph_mgr
       	- ceph_osd
   ...

   참고

   If other services, such as the Dashboard, are deployed with HCI nodes, they must be added to the edpm_ceph_hci_pre_enabled_services parameter list. For more information about this role, see edpm_ceph_hci_pre role.

5. Configure the Red Hat Ceph Storage cluster network for storage management.

   The following example has 3 nodes. It assumes the storage management is on VLAN23:

   apiVersion: dataplane.openstack.org/v1beta1
   kind: OpenStackDataPlaneNodeSet
   metadata:
     name: openstack-edpm
     namespace: openstack
   spec:
     env:
     - name: ANSIBLE_FORCE_COLOR
       value: "True"
     networkAttachments:
     - ctlplane
     nodeTemplate:
       ansible:
         ansiblePort: 22
         ansibleUser: cloud-admin
         ansibleVars:
           edpm_ceph_hci_pre_enabled_services:
           - ceph_mon
           - ceph_mgr
           - ceph_osd
           edpm_fips_mode: check
           edpm_iscsid_image: {{ registry_url }}/openstack-iscsid:{{ image_tag }}
           edpm_logrotate_crond_image: {{ registry_url }}/openstack-cron:{{ image_tag }}
           edpm_network_config_hide_sensitive_logs: false
           edpm_network_config_os_net_config_mappings:
             edpm-compute-0:
               nic1: 52:54:00:1e:af:6b
               nic2: 52:54:00:d9:cb:f4
             edpm-compute-1:
               nic1: 52:54:00:f2:bc:af
               nic2: 52:54:00:f1:c7:dd
             edpm-compute-2:
               nic1: 52:54:00:dd:33:14
               nic2: 52:54:00:50:fb:c3
           edpm_network_config_template: |
             ---
             {% set mtu_list = [ctlplane_mtu] %}
             {% for network in nodeset_networks %}
             {{ mtu_list.append(lookup(vars, networks_lower[network] ~ _mtu)) }}
             {%- endfor %}
             {% set min_viable_mtu = mtu_list | max %}
             network_config:
             - type: ovs_bridge
               name: {{ neutron_physical_bridge_name }}
               mtu: {{ min_viable_mtu }}
               use_dhcp: false
               dns_servers: {{ ctlplane_dns_nameservers }}
               domain: {{ dns_search_domains }}
               addresses:
               - ip_netmask: {{ ctlplane_ip }}/{{ ctlplane_cidr }}
               routes: {{ ctlplane_host_routes }}
               members:
               - type: interface
                 name: nic2
                 mtu: {{ min_viable_mtu }}
                 # force the MAC address of the bridge to this interface
                 primary: true
             {% for network in nodeset_networks %}
               - type: vlan
                 mtu: {{ lookup(vars, networks_lower[network] ~ _mtu) }}
                 vlan_id: {{ lookup(vars, networks_lower[network] ~ _vlan_id) }}
                 addresses:
                 - ip_netmask:
                     {{ lookup(vars, networks_lower[network] ~ _ip) }}/{{ lookup(vars, networks_lower[network] ~ _cidr) }}
                 routes: {{ lookup(vars, networks_lower[network] ~ _host_routes) }}
             {% endfor %}
           edpm_neutron_metadata_agent_image: {{ registry_url }}/openstack-neutron-metadata-agent-ovn:{{ image_tag }}
           edpm_nodes_validation_validate_controllers_icmp: false
           edpm_nodes_validation_validate_gateway_icmp: false
           edpm_selinux_mode: enforcing
           edpm_sshd_allowed_ranges:
           - 192.168.111.0/24
           - 192.168.122.0/24
           - 192.168.133.0/24
           - 192.168.144.0/24
           edpm_sshd_configure_firewall: true
           enable_debug: false
           gather_facts: false
           image_tag: current-podified
           neutron_physical_bridge_name: br-ex
           neutron_public_interface_name: eth0
           service_net_map:
             nova_api_network: internalapi
             nova_libvirt_network: internalapi
           storage_mgmt_cidr: "24"
           storage_mgmt_host_routes: []
           storage_mgmt_mtu: 9000
           storage_mgmt_vlan_id: 23
           storage_mtu: 9000
           timesync_ntp_servers:
           - hostname: pool.ntp.org
       ansibleSSHPrivateKeySecret: dataplane-ansible-ssh-private-key-secret
       managementNetwork: ctlplane
       networks:
       - defaultRoute: true
         name: ctlplane
         subnetName: subnet1
       - name: internalapi
         subnetName: subnet1
       - name: storage
         subnetName: subnet1
       - name: tenant
         subnetName: subnet1
     nodes:
       edpm-compute-0:
         ansible:
           host: 192.168.122.100
         hostName: compute-0
         networks:
         - defaultRoute: true
           fixedIP: 192.168.122.100
           name: ctlplane
           subnetName: subnet1
         - name: internalapi
           subnetName: subnet1
         - name: storage
           subnetName: subnet1
         - name: storagemgmt
           subnetName: subnet1
         - name: tenant
           subnetName: subnet1
       edpm-compute-1:
         ansible:
           host: 192.168.122.101
         hostName: compute-1
         networks:
         - defaultRoute: true
           fixedIP: 192.168.122.101
           name: ctlplane
           subnetName: subnet1
         - name: internalapi
           subnetName: subnet1
         - name: storage
           subnetName: subnet1
         - name: storagemgmt
           subnetName: subnet1
         - name: tenant
           subnetName: subnet1
       edpm-compute-2:
         ansible:
           host: 192.168.122.102
         hostName: compute-2
         networks:
         - defaultRoute: true
           fixedIP: 192.168.122.102
           name: ctlplane
           subnetName: subnet1
         - name: internalapi
           subnetName: subnet1
         - name: storage
           subnetName: subnet1
         - name: storagemgmt
           subnetName: subnet1
         - name: tenant
           subnetName: subnet1
     preProvisioned: true
     services:
     - bootstrap
     - configure-network
     - validate-network
     - install-os
     - ceph-hci-pre
     - configure-os
     - ssh-known-hosts
     - run-os
     - reboot-os

6. Apply the CR:

   $ oc apply -f <dataplane_cr_file>

   • Replace <dataplane_cr_file> with the name of your file.

     참고

     Ansible does not configure or validate the networks until the OpenStackDataPlaneDeployment CRD is created.

7. Create an OpenStackDataPlaneDeployment CRD, as described in Creating the data plane in the Deploying Red Hat OpenStack Services on OpenShift guide, which has the OpenStackDataPlaneNodeSet CRD file defined above to have Ansible configure the services on the data plane nodes.

8. To confirm the network is configured, complete the following steps:

   1. SSH into a data plane node.
   2. Use the ip a command to display configured networks.
   3. Confirm the storage networks are in the list of configured networks.