starlingx/docs
Code Issues Proposed changes

Updated "no-proxy" service parameter using Horizon/CLI

Browse Source 
Updated Patchset 2 comments
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I5f7079d5b43b50ac4528c6707a1a9e42e9c27670
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
(cherry picked from commit 96331cf427)
This commit is contained in:
Juanita-Balaraj
2021-11-23 10:23:55 -05:00
parent c588eac620
commit 0373e9f6c5
2 changed files with 55 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -27,6 +27,12 @@ interface or the CLI. You can use IPv4 or IPv6 addresses.
addresses in their |SANs| must be updated with new certificates reflecting
the new addresses.
.. note::
If you are running docker proxy on your system, you need to change the
``no_proxy`` service parameter using the CLI to append the new |OAM| IP
address. For more information, see :ref:`Change the OAM IP Configuration
Using the CLI <changing-the-oam-ip-configuration-using-the-cli>`.
.. rubric:: |prereq|
Before changing the |OAM| IP configuration, review the Fault Management page

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

@@ -8,6 +8,28 @@ Change the OAM IP Configuration Using the CLI
If you prefer, you can use the CLI to view or change the |OAM| IP Configuration.
.. rubric:: |context|
During installation, |prod-long| is configured with an |OAM| network subnet and
related IP addresses. You can change these addresses using the the CLI or the
Horizon Web Interface. You can use IPv4 or IPv6 addresses.
.. caution::
Access to the |OAM| network is interrupted during this procedure. When a
:command:`swact` is performed on the controllers, the newly active
controller uses the changed |OAM| IP addresses. The existing |OAM| IP
addresses are no longer valid, and you must use the new OAM IP addresses
to reconnect to the controller. Changes to external |OAM| access routing
settings may also be required. In addition, |VNC| console access to
worker-node hosts is interrupted until the hosts are locked and unlocked.
Once the |OAM| IP addresses are changed, any existing server certificates
(ssl, docker_registry, OpenStack etc.) that have the old |OAM| IP addresses
in their |SANs| must be updated with new certificates reflecting the new
addresses. For more information, see :ref:`Install/Update Local Registry
Certificates <installing-updating-the-docker-registry-certificate>`.
To view the existing |OAM| IP configuration, use the following command.
.. code-block:: none
@@ -78,3 +100,30 @@ For more information about the default firewall rules, see
For more information about modifying the firewall options, see
:ref:`Modify Firewall Options <security-firewall-options>`.
(Optional) If you are running Docker proxy on your system, you need to
change the **no_proxy** service parameter using the CLI to append the new
OAM IP, using the following steps:
#. To list the service parameters, use the :command:`system service-parameter-list`
command. Note the old **no_proxy** values.
#. To append the new OAM IP to the no_proxy parameter, use the
:command:`system serviceparameter-modify docker proxy no_proxy=old_value, new_oam_ip(s)`
command.
Where, *<new_oam_ip(s)>* is the new OAM IP(s) that needs to be appended
to the **no_proxy** parameter. Ensure you include new values for the
floating OAM, controller-0 OAM, and controller-1 if they are changed.
#. To apply the changes, use the :command:`system service-parameter-apply docker`
command.
#. Lock and unlock the controller(s).
.. seealso::
:ref:`Default Firewall Rules <security-default-firewall-rules>`
:ref:`Modify Firewall Options <security-firewall-options>`