starlingx/docs
Code Issues Proposed changes

OAM address change for DC subclouds information missing

Browse Source 
Change-Id: I4853c64febaf75f394d8f09185c68b1e57ccc18e
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2024-09-30 06:18:08 +00:00
parent a9b2f72816
commit 66aca4d058
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst
View File

@ -95,6 +95,21 @@ resources are available to migrate any running instances.
On AIO Simplex systems you do not need to lock and unlock the host. The
changes are applied automatically.
In the |prod-dc| system, if the system controller |OAM| address is changed
(the network itself or the floating address), subclouds need to update the
address pool ``system-controller-oam-subnet`` so that the registry.central domain
points to the new value. Run the following command on all subclouds:
.. code-block::
~(keystone_admin)]$ system addrpool-modify [system-controller-oam-subnet's uuid] \
--network [new system-controller OAM network address] \
--prefix [new system-controller OAM network prefix] \
--ranges [new system-controller OAM network address range] \
--floating-address [new system-controller OAM floating address]
Adjust the necessary parameters based on the altered values in the system controller.
.. rubric:: |postreq|
(Optional) If you are running Docker proxy on your system, you need to
@ -121,4 +136,4 @@ OAM IP, using the following steps:
:ref:`Default Firewall Rules <security-default-firewall-rules>`
:ref:`Modify Firewall Options <security-firewall-options>`
:ref:`Modify Firewall Options <security-firewall-options>`