Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

So the issue here was that the configuration files within the network-environment.yaml and controller.yaml where not being picked up correctly during the overcloud deploy. Within the relevant files i put the full paths and this then picked up the correct configuration files. Also I added the full path to the run-os-net-config.sh. To correctly setup the controller node to have the right details the interfaces were modified as the below. The external IP was set on the bridge as it is the native VLAN

params:
        $network_config:
          network_config:
          # NIC 2- Provisioning
          - type: interface
            name: nic2
            use_dhcp: false
            defroute: false
            addresses:
            - ip_netmask:
                list_join:
                - /
                - - get_param: ControlPlaneIp
                  - get_param: ControlPlaneSubnetCidr
            routes:
            - ip_netmask: 169.254.169.254/32
              next_hop:
                get_param: EC2MetadataIp


          - type: ovs_bridge
            name: bridge_name
            use_dhcp: false
            addresses:
            - ip_netmask:
                {get_param: ExternalIpSubnet}
            routes:
            - default: true
              ip_netmask: 0.0.0.0/0
              next_hop:
                get_param: ExternalInterfaceDefaultRoute
            dns_servers:
              get_param: DnsServers
            members:
            - type: interface
              name: nic1
              # force the MAC address of the bridge to this interface
              primary: true
            - type: vlan
              vlan_id:
                get_param: StorageNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageIpSubnet
            - type: vlan
              vlan_id:
                get_param: StorageMgmtNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageMgmtIpSubnet
            - type: vlan
              vlan_id:
                get_param: InternalApiNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: InternalApiIpSubnet
            - type: vlan
              vlan_id:
                get_param: TenantNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: TenantIpSubnet

This now works correct and the horizon dashboard and VMs are accessible on the external network.

So the issue here was that the configuration files within the network-environment.yaml and controller.yaml where not being picked up correctly during the overcloud deploy. Within the relevant files i put the full paths and this then picked up the correct configuration files. Also I added the full path to the run-os-net-config.sh. To correctly setup the controller node to have the right details the interfaces were modified as the below. The external IP was set on the bridge as it is the native VLAN

params:
        $network_config:
          network_config:
          # NIC 2- Provisioning
          - type: interface
            name: nic2
            use_dhcp: false
            defroute: false
            addresses:
            - ip_netmask:
                list_join:
                - /
                - - get_param: ControlPlaneIp
                  - get_param: ControlPlaneSubnetCidr
            routes:
            - ip_netmask: 169.254.169.254/32
              next_hop:
                get_param: EC2MetadataIp


          - type: ovs_bridge
            name: bridge_name
            use_dhcp: false
            addresses:
            - ip_netmask:
                {get_param: ExternalIpSubnet}
            routes:
            - default: true
              ip_netmask: 0.0.0.0/0
              next_hop:
                get_param: ExternalInterfaceDefaultRoute
            dns_servers:
              get_param: DnsServers
            members:
            - type: interface
              name: nic1
              # force the MAC address of the bridge to this interface
              primary: true
            - type: vlan
              vlan_id:
                get_param: StorageNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageIpSubnet
            - type: vlan
              vlan_id:
                get_param: StorageMgmtNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: StorageMgmtIpSubnet
            - type: vlan
              vlan_id:
                get_param: InternalApiNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: InternalApiIpSubnet
            - type: vlan
              vlan_id:
                get_param: TenantNetworkVlanID
              addresses:
              - ip_netmask:
                  get_param: TenantIpSubnet

This now works correct correctly and the horizon dashboard and VMs are accessible on the external network. network.