Remove the step to manually add a route on compute nodes to access ldap (dsr8MR3)
Change-Id: If415a2cdab2788bb9a437cc9b809bfd4574b03d3 Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili
parent
548fcc5003
commit
17b936366d
|
|
@ -72,9 +72,9 @@ subcloud, the subcloud installation has these phases:
|
|||
patch level as the system controller. This ensures that the subcloud
|
||||
boot image aligns with the patch level of the load to be installed on
|
||||
the subcloud.
|
||||
|
||||
|
||||
.. warning::
|
||||
|
||||
|
||||
If the patch level of load-imported ISO does not match the system controller
|
||||
patch level, the subcloud patch state may not align with the system
|
||||
controller patch state.
|
||||
|
|
@ -126,11 +126,11 @@ Controlling the RVMC debug level and automatic serial console log capture
|
|||
|
||||
The optional parameter, ``rvmc_debug_level``, in the subcloud install_values
|
||||
YAML file, controls the generation of debug logs during |RVMC| installation,
|
||||
which are then stored in the ansible log files for each subcloud.
|
||||
which are then stored in the ansible log files for each subcloud.
|
||||
|
||||
**Valid rvmc_debug_levels**
|
||||
|
||||
The available ``rvmc_debug_level`` values control the log content as follows.
|
||||
The available ``rvmc_debug_level`` values control the log content as follows.
|
||||
|
||||
Note that the log levels increase in verbosity as they increase:
|
||||
|
||||
|
|
@ -152,7 +152,7 @@ logs.
|
|||
|
||||
When the ``rvmc_debug_level`` is enabled (``rvmc_debug_level`` > 0), the full serial
|
||||
console output can be automatically captured, provided the serial console is
|
||||
configured in the 'install_type' install value.
|
||||
configured in the 'install_type' install value.
|
||||
|
||||
.. note:: Capturing graphical console output is not supported.
|
||||
|
||||
|
|
@ -566,29 +566,31 @@ subcloud ansible log files: ``/var/log/dcmanager/ansible``, and named as
|
|||
|
||||
- Add static route for nodes in subcloud to access openldap service.
|
||||
|
||||
In a Distributed Cloud system, openldap service is running on Central
|
||||
Cloud. In order for the nodes in the subclouds to access openldap service,
|
||||
such as ssh to the nodes as openldap users, a static route to the System
|
||||
Controller is required to be added in these nodes. This applies to
|
||||
controller nodes, worker nodes and storage nodes (nodes that have sssd
|
||||
running).
|
||||
In a |DC| system, openldap service is running on Central Cloud. In order
|
||||
for the nodes in the subclouds to access openldap service, such as ssh to
|
||||
the nodes as openldap users, a static route to the System Controller is
|
||||
required to be added in controller nodes of the subcloud.
|
||||
|
||||
The static route can be added on each of the nodes in the subcloud using system
|
||||
.. note::
|
||||
|
||||
LDAP traffic from worker and storage nodes of the subcloud is sent
|
||||
with |SNAT| via the controller nodes. Thus, static routes do not need to be
|
||||
configured on these nodes.
|
||||
|
||||
The static route can be added to the controller nodes in the subcloud using system
|
||||
CLI.
|
||||
|
||||
The following examples show how to add the static route in controller node and
|
||||
worker node:
|
||||
The following example shows how to add the static route in controller node:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
[sysadmin@controller-0 ~(keystone_admin)]$ system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
[sysadmin@controller-0 ~(keystone_admin)]$ system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
|
||||
The static route can also be added using Deployment Manager by adding the
|
||||
route in its configuration file.
|
||||
|
||||
The following examples show adding the route configuration in controller
|
||||
and worker host profiles of the deployment manager's configuration file:
|
||||
The following example shows adding the route configuration in controller
|
||||
profile of the deployment manager's configuration file:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
|
@ -613,31 +615,3 @@ subcloud ansible log files: ``/var/log/dcmanager/ansible``, and named as
|
|||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
||||
Worker node:
|
||||
---
|
||||
apiVersion: starlingx.windriver.com/v1
|
||||
kind: HostProfile
|
||||
metadata:
|
||||
labels:
|
||||
controller-tools.k8s.io: "1.0"
|
||||
name: compute-0-profile
|
||||
namespace: deployment
|
||||
spec:
|
||||
administrativeState: unlocked
|
||||
boardManagement:
|
||||
credentials:
|
||||
password:
|
||||
secret: bmc-secret
|
||||
type: dynamic
|
||||
bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
|
||||
clockSynchronization: ntp
|
||||
console: ttyS0,115200n8
|
||||
installOutput: text
|
||||
......
|
||||
routes:
|
||||
- gateway: <Gateway IP address>
|
||||
interface: mgmt0
|
||||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
|
|
|||
|
|
@ -251,7 +251,7 @@ subcloud, the subcloud installation process has two phases:
|
|||
between the subcloud and system controller, then the
|
||||
``management_gateway_address`` parameter should be replaced with admin
|
||||
subnet information.
|
||||
|
||||
|
||||
For example:
|
||||
|
||||
.. code-block:: none
|
||||
|
|
@ -361,28 +361,31 @@ subcloud, the subcloud installation process has two phases:
|
|||
|
||||
- Add static route for nodes in subcloud to access openldap service.
|
||||
|
||||
In DC system, openldap service is running on Central Cloud. In order for the nodes
|
||||
in the subclouds to access openldap service, such as ssh to the nodes as openldap
|
||||
users, a static route to the system controller is required to be added in these
|
||||
nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
|
||||
that have sssd running).
|
||||
In |DC| system, openldap service is running on Central Cloud. In order for
|
||||
the nodes in the subclouds to access openldap service, such as ssh to the
|
||||
nodes as openldap users, a static route to the System Controller is
|
||||
required to be added in the controller nodes of the subcloud.
|
||||
|
||||
The static route can be added on each of the nodes in the subcloud using system
|
||||
.. note::
|
||||
|
||||
LDAP traffic from worker and storage nodes of the subcloud is sent
|
||||
with |SNAT| via the controller nodes. Thus, static routes do not need to be
|
||||
configured on these nodes.
|
||||
|
||||
The static route can be added to the controller nodes in the subcloud using system
|
||||
CLI.
|
||||
|
||||
The following examples show how to add the static route in controller node and
|
||||
worker node:
|
||||
The following example shows how to add the static route in controller node:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
|
||||
The static route can also be added using Deployment Manager by adding the route
|
||||
in its configuration file.
|
||||
|
||||
The following examples show adding the route configuration in controller and
|
||||
worker host profiles of the deployment manager's configuration file:
|
||||
The following example shows adding the route configuration in controller
|
||||
profile of the deployment manager's configuration file:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
|
@ -407,31 +410,3 @@ subcloud, the subcloud installation process has two phases:
|
|||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
||||
Worker node:
|
||||
---
|
||||
apiVersion: starlingx.windriver.com/v1
|
||||
kind: HostProfile
|
||||
metadata:
|
||||
labels:
|
||||
controller-tools.k8s.io: "1.0"
|
||||
name: compute-0-profile
|
||||
namespace: deployment
|
||||
spec:
|
||||
administrativeState: unlocked
|
||||
boardManagement:
|
||||
credentials:
|
||||
password:
|
||||
secret: bmc-secret
|
||||
type: dynamic
|
||||
bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
|
||||
clockSynchronization: ntp
|
||||
console: ttyS0,115200n8
|
||||
installOutput: text
|
||||
......
|
||||
routes:
|
||||
- gateway: <Gateway IP address>
|
||||
interface: mgmt0
|
||||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
|
|
|||
|
|
@ -212,28 +212,31 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
|
|||
|
||||
- Add static route for nodes in subcloud to access openldap service.
|
||||
|
||||
In DC system, openldap service is running on Central Cloud. In order for the nodes
|
||||
in the subclouds to access openldap service, such as ssh to the nodes as openldap
|
||||
users, a static route to the System Controller is required to be added in these
|
||||
nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
|
||||
that have sssd running).
|
||||
In a |DC| system, openldap service is running on Central Cloud. In order
|
||||
for the nodes in the subclouds to access openldap service, such as ssh to
|
||||
the nodes as openldap users, a static route to the System Controller is
|
||||
required to be added in controller nodes of the subcloud.
|
||||
|
||||
The static route can be added on each of the nodes in the subcloud using system
|
||||
.. note::
|
||||
|
||||
LDAP traffic from worker and storage nodes of the subcloud is sent
|
||||
with |SNAT| via the controller nodes. Thus, static routes do not need to be
|
||||
configured on these nodes.
|
||||
|
||||
The static route can be added to the controller nodes in the subcloud using system
|
||||
CLI.
|
||||
|
||||
The following examples show how to add the static route in controller node and
|
||||
worker node:
|
||||
The following example shows how to add the static route in controller node:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
|
||||
The static route can also be added using Deployment Manager by adding the route
|
||||
in its configuration file.
|
||||
|
||||
The following examples show adding the route configuration in controller and
|
||||
worker host profiles of the deployment manager's configuration file:
|
||||
The following example shows adding the route configuration in controller
|
||||
profile of the deployment manager's configuration file:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
|
@ -258,31 +261,3 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
|
|||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
||||
Worker node:
|
||||
---
|
||||
apiVersion: starlingx.windriver.com/v1
|
||||
kind: HostProfile
|
||||
metadata:
|
||||
labels:
|
||||
controller-tools.k8s.io: "1.0"
|
||||
name: compute-0-profile
|
||||
namespace: deployment
|
||||
spec:
|
||||
administrativeState: unlocked
|
||||
boardManagement:
|
||||
credentials:
|
||||
password:
|
||||
secret: bmc-secret
|
||||
type: dynamic
|
||||
bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
|
||||
clockSynchronization: ntp
|
||||
console: ttyS0,115200n8
|
||||
installOutput: text
|
||||
......
|
||||
routes:
|
||||
- gateway: <Gateway IP address>
|
||||
interface: mgmt0
|
||||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
|
@ -84,28 +84,31 @@ components and produces a 'Prestaging ISO'.
|
|||
|
||||
- Add static route for nodes in subcloud to access openldap service.
|
||||
|
||||
In DC system, openldap service is running on Central Cloud. In order for the nodes
|
||||
in the subclouds to access openldap service, such as ssh to the nodes as openldap
|
||||
users, a static route to the System Controller is required to be added in these
|
||||
nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
|
||||
that have sssd running).
|
||||
In a |DC| system, openldap service is running on Central Cloud. In order
|
||||
for the nodes in the subclouds to access openldap service, such as ssh to
|
||||
the nodes as openldap users, a static route to the System Controller is
|
||||
required to be added in controller nodes of the subcloud.
|
||||
|
||||
The static route can be added on each of the nodes in the subcloud using system
|
||||
.. note::
|
||||
|
||||
LDAP traffic from worker and storage nodes of the subcloud is sent
|
||||
with |SNAT| via the controller nodes. Thus, static routes do not need to be
|
||||
configured on these nodes.
|
||||
|
||||
TThe static route can be added to the controller nodes in the subcloud using system
|
||||
CLI.
|
||||
|
||||
The following examples show how to add the static route in controller node and
|
||||
worker node:
|
||||
The following example shows how to add the static route in controller node:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
|
||||
|
||||
The static route can also be added using Deployment Manager by adding the route
|
||||
in its configuration file.
|
||||
|
||||
The following examples show adding the route configuration in controller and
|
||||
worker host profiles of the deployment manager's configuration file:
|
||||
The following example shows adding the route configuration in controller
|
||||
profile of the deployment manager's configuration file:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
|
|
@ -131,34 +134,6 @@ components and produces a 'Prestaging ISO'.
|
|||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
||||
Worker node:
|
||||
---
|
||||
apiVersion: starlingx.windriver.com/v1
|
||||
kind: HostProfile
|
||||
metadata:
|
||||
labels:
|
||||
controller-tools.k8s.io: "1.0"
|
||||
name: compute-0-profile
|
||||
namespace: deployment
|
||||
spec:
|
||||
administrativeState: unlocked
|
||||
boardManagement:
|
||||
credentials:
|
||||
password:
|
||||
secret: bmc-secret
|
||||
type: dynamic
|
||||
bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
|
||||
clockSynchronization: ntp
|
||||
console: ttyS0,115200n8
|
||||
installOutput: text
|
||||
......
|
||||
routes:
|
||||
- gateway: <Gateway IP address>
|
||||
interface: mgmt0
|
||||
metric: 1
|
||||
prefix: 64
|
||||
subnet: <Central Cloud mgmt subnet>
|
||||
|
||||
.. _local-install-bundle-section:
|
||||
|
||||
--------------------
|
||||
|
|
|
|||
Loading…
Reference in New Issue