Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

5.6. Updating the control plane for new edge sites

Update the control plane configuration to integrate newly deployed edge locations. This enables the control plane to manage storage and compute services at the new edge sites.

You can create additional node sets by using the OpenStackDataPlaneNodeSet custom resource (CR). Use a unique availability zone, and the VLANs, NIC mappings, and IP addresses specific to the site you are deploying. For more information about deploying an OpenStackDataPlaneNodeSet CR, see Creating the data plane.

When you deploy a DCN node set with storage, you must update two fields of the OpenStackControlPlane CR at the central location:

  • cinderVolumes
  • glanceAPIs
  • Neutron
  • OVN
참고

If you are using cells, you must also configure cells for the new DCN site.

Prerequisites

  • You have deployed the central location.
  • You have deployed an additional OpenStackDataPlane node set.

Procedure

  1. In the neutron service configuration, update the customServiceConfig field to add the new availability zone and network leaf: 

            customServiceConfig: |
    	[DEFAULT]
    	router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.AZLeastRoutersScheduler
    	network_scheduler_driver =  neutron.scheduler.dhcp_agent_scheduler.AZAwareWeightScheduler
    	default_availability_zones = az0,az1
    	[ml2_type_vlan]
    	network_vlan_ranges = datacentre:1:1000,leaf1:1:1000
    	[neutron]
    	physnets = datacentre,leaf

  2. In the OVN service configuration, update the availability zones: 

          ovnController:
        external-ids:
          availability-zones:
          - az0
          - az1
          enable-chassis-as-gateway: true
          ovn-bridge: br-int
          ovn-encap-type: geneve
          system-id: random
        networkAttachment: tenant
        nicMappings:
          datacentre: ospbr

  3. Update the cinderVolumes field in the OpenStackControlPlane CR to add the availability zones definitions of the remote location. Each cinder volume service in each availability zone uses the Glance API server for its availability zone. For example, glance_api_servers = https://glance-az1-internal.openstack.svc:9292: 

          cinderVolumes:
        az0:
          customServiceConfig: |
            [DEFAULT]
            ....
        az1:
          customServiceConfig: |
            [DEFAULT]
            enabled_backends = ceph
            glance_api_servers = https://glance-az1-internal.openstack.svc:9292
            [ceph]
            volume_backend_name = az1
            volume_driver = cinder.volume.drivers.rbd.RBDDriver
            rbd_ceph_conf = /etc/ceph/az1.conf
            rbd_user = openstack
            rbd_pool = volumes
            rbd_flatten_volume_from_snapshot = False
            rbd_secret_uuid = 19ccdd60-79a0-5f0f-aece-ece700e514f8
            rbd_cluster_name = az1
            backend_availability_zone = az1

  4. Register an Image service (glance) pod to the Identity service (keystone) catalog:

    In DCN, an Image service pod is deployed for each node set. A single Image service pod is registered to the Identity service catalog at any one time. For this reason, in the top-level Glance custom resource (CR), the keystoneEndpoint parameter is defined and exposed. Unless a single instance is deployed, the human operator can choose, before the main OpenStackControlPlane CR is applied, which instance should be registered. Because our default endpoint is the az0 Image service API, the keystoneEndpoint is set to az0: 

    spec:
   <...>
   glance:
      enabled: true
      keystoneEndpoint: az0
        glanceAPIs:
          az0:
            apiTimeout: 60

  5. Update the glanceAPIs field:

    For the node sets at az0, the glanceAPIs field configures the Image service pods for the central location. When you add an additional node set in AZ1, the OpenStackControlPlane CR is updated such that the glanceAPIs field contains the Image service (glance) pod definition for AZ0 and AZ1. Additionally, the Image service pod for AZ1 defines the ceph the backend for the central location, and the AZ0 Image service pod for the central location is updated so that it has the ceph backend definition for AZ1. 

          glanceAPIs:
        az1:
          customServiceConfig: |
            [DEFAULT]
            enabled_import_methods = [web-download,copy-image,glance-direct]
            enabled_backends = az0:rbd,az1:rbd
            [glance_store]
            default_backend = az1
            [az1]
            rbd_store_ceph_conf = /etc/ceph/az1.conf
            store_description = "az1 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az0]
            rbd_store_ceph_conf = /etc/ceph/az0.conf
            store_description = "az0 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
          networkAttachments:
          - storage
          override:
            service:
              internal:
                metadata:
                  annotations:
                    metallb.universe.tf/address-pool: internalapi
                    metallb.universe.tf/allow-shared-ip: internalapi
                    metallb.universe.tf/loadBalancerIPs: 172.17.0.81
                spec:
                  type: LoadBalancer
          replicas: 2
          type: edge
        az0:
          customServiceConfig: |
            [DEFAULT]
            enabled_import_methods = [web-download,copy-image,glance-direct]
            enabled_backends = az0:rbd,az1:rbd
            [glance_store]
            default_backend = az0
            [az0]
            rbd_store_ceph_conf = /etc/ceph/az0.conf
            store_description = "az0 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az1]
            rbd_store_ceph_conf = /etc/ceph/az1.conf
            store_description = "az1 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
          networkAttachments:
          - storage
          override:
            service:
              internal:
                metadata:
                  annotations:
                    metallb.universe.tf/address-pool: internalapi
                    metallb.universe.tf/allow-shared-ip: internalapi
                    metallb.universe.tf/loadBalancerIPs: 172.17.0.80
                spec:
                  type: LoadBalancer
          replicas: 3
          type: split
    참고

    Availability zone az0 is of type split, and all other availability zones are of type edge.

    The split type is for cloud users to use when uploading images. The edge type is created so that when Cinder or Nova interact with Glance they can be configured to whichever glance is local to them. Use at least 3 replicas for the default split glance pods and 2 replicas for the edge glance pods and increase replicas proportionally to the workload.

  6. Optional: Update the Cell configuration.

    By default, compute nodes across all availability zones (AZs) are placed in a common cell called cell1. You can increase the performance of large deployments by partitioning compute nodes into separate cells. For DCN deployments, place each availability zone into its own cell. For more information, see Adding Compute cells to the control plane.

  7. Apply the changes made to the OpenStackControlPlane CR: 

    oc apply -f openstack_control_plane.yaml

  8. Continue to update the control plane for each additional edge site that is added. Add Red Hat Storage Service (RHCS) to your OpenShift secrets as needed.

    1. In the neutron service configuration, update the customServiceConfig field to add the new availability zone and network leaf: 

              customServiceConfig: |
    	[DEFAULT]
    	router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.AZLeastRoutersScheduler
    	network_scheduler_driver =  neutron.scheduler.dhcp_agent_scheduler.AZAwareWeightScheduler
    	default_availability_zones = az0,az1,az2
    	[ml2_type_vlan]
    	network_vlan_ranges = datacentre:1:1000,leaf1:1:1000,leaf2:1:1000
    	[neutron]
    	physnets = datacentre,leaf1,leaf2

    2. In the OVN service configuration, update the availability zones 

            ovnController:
        external-ids:
          availability-zones:
          - az0
          - az1
          - az2
          enable-chassis-as-gateway: true
          ovn-bridge: br-int
          ovn-encap-type: geneve
          system-id: random
        networkAttachment: tenant
        nicMappings:
          datacentre: ospbr

    3. Add an additional availability zone the cinderVolumes service field: 

           cinderVolumes:
        az0:
          customServiceConfig: |
            [DEFAULT]
            ...
        az1:
          customServiceConfig: |
            [DEFAULT]
            ...
        az2:
          customServiceConfig: |
            [DEFAULT]
            enabled_backends = ceph
            glance_api_servers = https://glance-az2-internal.openstack.svc:9292
            [ceph]
            volume_backend_name = ceph
            volume_driver = cinder.volume.drivers.rbd.RBDDriver
            rbd_ceph_conf = /etc/ceph/az2.conf
            rbd_user = openstack
            rbd_pool = volumes
            rbd_flatten_volume_from_snapshot = False
            rbd_secret_uuid = 5c0c7a8e-55b1-5fa8-bc5c-9756b7862d2f
            rbd_cluster_name = az2
            backend_availability_zone = az2

    4. Add an additional availability zone to the glanceAPIs field:

      As you add additional AZs, you must ensure that each Image service pod definition contains the storage configuration of the central location (AZ0), and its own local ceph configuration. You must also ensure that the central location has the storage definition of all other sites. This creates a hub and spoke relationship between the central location Image service pod, and the Image service pods for geographically dispersed node sets: 

            glanceAPIs:
        az0:
          customServiceConfig: |
            [DEFAULT]
            enabled_import_methods = [web-download,copy-image,glance-direct]
            enabled_backends = az0:rbd,az1:rbd,az2:rbd
            [glance_store]
            default_backend = az0
            [az0]
            rbd_store_ceph_conf = /etc/ceph/az0.conf
            store_description = "az0 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az1]
            rbd_store_ceph_conf = /etc/ceph/az1.conf
            store_description = "az1 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az2]
            rbd_store_ceph_conf = /etc/ceph/az2.conf
            store_description = "az2 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
          networkAttachments:
          - storage
          override:
            service:
              internal:
                metadata:
                  annotations:
                    metallb.universe.tf/address-pool: internalapi
                    metallb.universe.tf/allow-shared-ip: internalapi
                    metallb.universe.tf/loadBalancerIPs: 172.17.0.80
                spec:
                  type: LoadBalancer
          replicas: 3
          type: split
        az1:
          customServiceConfig: |
            [DEFAULT]
            enabled_import_methods = [web-download,copy-image,glance-direct]
            enabled_backends = az0:rbd,az1:rbd
            [glance_store]
            default_backend = az1
            [az1]
            rbd_store_ceph_conf = /etc/ceph/az1.conf
            store_description = "az1 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az0]
            rbd_store_ceph_conf = /etc/ceph/az0.conf
            store_description = "az0 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
          networkAttachments:
          - storage
          override:
            service:
              internal:
                metadata:
                  annotations:
                    metallb.universe.tf/address-pool: internalapi
                    metallb.universe.tf/allow-shared-ip: internalapi
                    metallb.universe.tf/loadBalancerIPs: 172.17.0.81
                spec:
                  type: LoadBalancer
          replicas: 2
          type: edge
        az2:
          customServiceConfig: |
            [DEFAULT]
            enabled_import_methods = [web-download,copy-image,glance-direct]
            enabled_backends = az0:rbd,az2:rbd
            [glance_store]
            default_backend = az2
            [az2]
            rbd_store_ceph_conf = /etc/ceph/az2.conf
            store_description = "az2 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
            [az0]
            rbd_store_ceph_conf = /etc/ceph/az0.conf
            store_description = "az0 RBD backend"
            rbd_store_pool = images
            rbd_store_user = openstack
            rbd_thin_provisioning = True
          networkAttachments:
          - storage
          override:
            service:
              internal:
                metadata:
                  annotations:
                    metallb.universe.tf/address-pool: internalapi
                    metallb.universe.tf/allow-shared-ip: internalapi
                    metallb.universe.tf/loadBalancerIPs: 172.17.0.82
                spec:
                  type: LoadBalancer
          replicas: 2
          type: edge

  9. Apply the changes made to the OpenStackControlPlane CR: 

    oc apply -f openstack_control_plane.yaml

  10. Add the AZ to a host aggregate. This allows OpenStack administrators to schedule workloads to a geographical location by passing the --availability-zone argument:

    1. Open a terminal to the openstackclient pod: 

      # oc rsh openstackclient

    2. Create a new OpenStack aggregate: 

      $ openstack aggregate create <aggregate_name>

    3. Label the OpenStack aggregate with the name of the AZ: 

      $ openstack aggregate set --zone <availability_zone> <aggregate_name>

    4. Add each host in the AZ to the aggregate: 

      $ openstack aggregate add host <aggregate_name> <compute_node_1>
$ openstack aggregate add host <aggregate_name> <compute_node_2>
...
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

Legal Notice

Theme

© 2026 Red Hat맨 위로 이동