starlingx/docs
Code Issues Proposed changes
docs/doc/source/node_management/kubernetes/node_interfaces/interface-provisioning.rst
Adil ac4d8fea44 Node Management and Distributed cloud Guide updates 
Global Pass Upgrades

Added content from emails attached to ticket and sharepoint

Pacth 01: inputs from email by Greg

Patch 03: Created new section for subcloud group
          updated table 1 shared system configurations

Patch 04: corrected typos (Mary's comments)

Patch 05: solved merged conflict

patch 06: removed broken link

Story: TBD
Task: TBD



Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I60b0a40a60a44d30429cd3a4dd8374c16345951a
2021-05-27 16:31:17 -03:00

3.0 KiB
Raw Blame History

Interface Provisioning

Before you can unlock and use the additional controller, worker, or storage nodes, you must configure their interfaces to attach them to networks.

Some interfaces require manual provisioning before the nodes can be unlocked.

  • For the second controller node, you must attach an interface to the network, and to the cluster-host network if used, before you can unlock the node.

  • For a storage node, you must attach an interface to the cluster-host network before you can unlock the node.

  • For a worker node, you must attach an interface to the cluster-host network before you can unlock the node.

    Note

    For the application and an openstack-compute labeled worker node, you must also attach at least one 'data' class data networks before you can unlock the node. The data networks must be set up beforehand. For more information, see Interface Settings <interface-settings>.

  • On a network that uses static addressing, you must assign an IP address to the interface. For more information, see Interface IP Address Provisioning Using the CLI <interface-ip-address-provisioning-using-the-cli>.

    ~(keystone_admin)$ system host-addr-add <node> <ifname> <ip_address> <prefix>

    where the following options can be used:

    node

    The name or UUID of the worker node.

    ifname

    The name of the interface.

    ip_address

    An IPv4 or IPv6 address.

    prefix

    The netmask length for the address.

supports three types of interfaces:

Ethernet interfaces

These are created automatically for each port on the host. You must configure Ethernet interfaces by specifying the interface class.

Aggregated Ethernet interfaces

For link protection, you can create an aggregated Ethernet interface with two or more ports, and configure it with the interface class.

VLAN interfaces

To support multiple interfaces on the same physical Ethernet or aggregated Ethernet interface, you can create interfaces and configure them with the interface class.

The procedure for attaching an interface depends on the interface type.

Logical interfaces of network types oam and mgmt cannot be deleted. They can only be modified to use different physical ports when required.

Note

On all nodes, except for the initial controller, the Ethernet interface for the internal management network is attached automatically to support installation using booting. On the initial controller node, the interface for the internal management network is attached according to the settings specified during the Ansible bootstrapping of the system.