Change VLAN tags in already deployed overcloud stack

Solution In Progress - Updated -

Issue

  • In order to improve the network channel between nodes, the networking team of our company is going to switch network ports of overcloud nodes into new VLANs. Therefore, we have to change VLAN tags on our nodes as well.

  • In our configuration, we have 4 internal networks:

VLAN10 - Internal API
VLAN20 - Tenant
VLAN30 - Storage
VLAN40 - Storage Mgmt
  • The following vlans are configured on the controllers:
[root@overcloud-controller0 ~]# ip a | grep vlan
9: vlan20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 172.16.13.10/24 brd 172.16.13.255 scope global vlan20
10: vlan30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 172.16.14.10/24 brd 172.16.14.255 scope global vlan30
    inet 172.16.14.20/32 brd 172.16.14.255 scope global vlan30
11: vlan10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 172.16.12.10/24 brd 172.16.12.255 scope global vlan10
    inet 172.16.12.101/32 brd 172.16.12.255 scope global vlan10
    inet 172.16.12.20/32 brd 172.16.12.255 scope global vlan10
12: vlan40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 172.16.15.10/24 brd 172.16.15.255 scope global vlan40
    inet 172.16.15.124/32 brd 172.16.15.255 scope global vlan40
  • We have deployed our overcloud via RHOSP Director.

  • Can we make changes in configuration without re-deploying the existing overcloud?

Environment

  • Red Hat OpenStack Platform 14.0 (RHOSP)
  • Red Hat OpenStack Platform 13.0 (RHOSP)
  • Red Hat OpenStack Platform 12.0 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In