13 KiB

Raw Blame History

Install a Subcloud Without Redfish Platform Management Service

For subclouds with servers that do not support Redfish Virtual Media Service, the ISO is installed locally at the subcloud. You can use the Central Cloud's CLI to bootstrap subclouds from the Central Cloud.

After physically installing the hardware and network connectivity of a subcloud, the subcloud installation process has two phases:

Installing the ISO on controller-0; this is done locally at the subcloud by using either, a bootable USB device, or a local boot server
Executing the dcmanager subcloud add command in the Central Cloud that uses Ansible to bootstrap on controller-0 in the subcloud

Note

After a successful remote installation of a subcloud in a Distributed Cloud system, a subsequent remote reinstallation fails because of an existing ssh key entry in the /root/.ssh/known_hosts on the system controller. In this case, delete the host key entry, if present, from /root/.ssh/known_hosts on the system controller before doing reinstallations.

partner

You must have downloaded update-iso.sh from .
In order to deploy subclouds from either controller, all local files that are referenced in the subcloud-bootstrap-values.yaml file must exist on both controllers (for example, /home/sysadmin/docker-registry-ca-cert.pem).

At the subcloud location, physically install the servers and network connectivity required for the subcloud.

Note

The servers require connectivity to a gateway router that provides IP routing between the subcloud management or admin subnet and the system controller management subnet, and between the subcloud subnet and the system controller subnet.

Update the ISO image to modify installation boot parameters (if required), automatically select boot menu options and add a kickstart file to automatically perform configurations such as configuring the initial IP Interface for bootstrapping.

For subclouds, the initial IP Interface should be the planned IP Interface for the subcloud.

Use the update-iso.sh script from . The script is used as follows:

update-iso.sh --initial-password <password> -i <input bootimage.iso> -o <output bootimage.iso>
                [ -a <ks-addon.cfg> ] [ -p param=value ]
                [ -d <default menu option> ] [ -t <menu timeout> ]
     -i <file>: Specify input ISO file
     -o <file>: Specify output ISO file
     -a <file>: Specify ks-addon.cfg file
     --initial-password <password>: Specify the initial login password for sysadmin user
     --no-force-password: Do not force password change on initial login (insecure)

     -p <p=v>:  Specify boot parameter
                Examples:
                -p instdev=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0

     -d <default menu option>:
                Specify default boot menu option:
                0 - Standard Controller, Serial Console
                1 - Standard Controller, Graphical Console
                2 - AIO, Serial Console
                3 - AIO, Graphical Console
                4 - AIO Low-latency, Serial Console
                5 - AIO Low-latency, Graphical Console
                NULL - Clear default selection
     -t <menu timeout>:
                Specify boot menu timeout, in seconds

The following example ks-addon.cfg file, used with the -a option, sets up an initial IP interface at boot time by defining a on an Ethernet interface and has it use to request an IP address.

In Debian, by default the ks-addon.cfg script is executed outside of the installing subcloud runtime (outside the chroot environment). As a result, the script does not have access to the kernel runtime command shell. Instead, the file system must be accessed via the provided $IMAGE_ROOTFS environment variable.

If required, a chroot can be manually entered, allowing full access to the installing subcloud's execution environment. See the ks-addon.cfg given below for an example.

#### start ks-addon.cfg

DEVICE=enp0s3
OAM_VLAN=1234
OAM_ADDR="xxxx:xxxx:x:xxxx:xx:x:x:x"

# This section is run outside of the subcloud target runtime.
# The IMAGE_ROOTFS environment variable is set to the root of the target filesystem

cat << EOF > ${IMAGE_ROOTFS}/etc/network/interfaces.d/ifcfg-${DEVICE}
auto ${DEVICE}
iface ${DEVICE} inet6 manual
mtu 9000
post-up echo 0 > /proc/sys/net/ipv6/conf/${DEVICE}/autoconf;\
echo 0 > /proc/sys/net/ipv6/conf/${DEVICE}/accept_ra;\
echo 0 > /proc/sys/net/ipv6/conf/${DEVICE}/accept_redirects
EOF

cat << EOF > ${IMAGE_ROOTFS}/etc/network/interfaces.d/ifcfg-vlan${OAM_VLAN}
auto vlan${OAM_VLAN}
iface vlan${OAM_VLAN} inet6 static
vlan-raw-device ${DEVICE}
address ${OAM_ADDR}
netmask 64
gateway ${OAM_GW_ADDR}
mtu 1500
post-up /usr/sbin/ip link set dev vlan${OAM_VLAN} mtu 1500;\
echo 0 > /proc/sys/net/ipv6/conf/vlan${OAM_VLAN}/autoconf;\
echo 0 > /proc/sys/net/ipv6/conf/vlan${OAM_VLAN}/accept_ra;\
echo 0 > /proc/sys/net/ipv6/conf/vlan${OAM_VLAN}/accept_redirects
EOF

# If execution is required inside the chroot environment, you can manually enter the
# chroot and run commands. Note: quotes around EOF are required:
cat << "EOF" | chroot "${IMAGE_ROOTFS}" /bin/bash -s
  echo "ks-addon.cfg: inside chroot"

  # chrooted commands go here.
  # Commands are executed in the context of the installing subcloud.

EOF

#### end ks-addon.cfg

After updating the ISO image, create a bootable USB with the ISO or put the ISO on a PXEBOOT server.

At the subcloud location, install the software from a USB device or a Boot Server on the server designated as controller-0.
At the subcloud location, verify that the interface on the subcloud controller has been properly configured by the kickstart file added to the ISO.
Log in to the subcloud's controller-0 and ping the Central Cloud's floating IP Address.

At the system controller, create a /home/sysadmin/subcloud1-bootstrap-values.yaml overrides file for the subcloud.

For example:

system_mode: simplex
name: "subcloud1"

description: "test"
location: "loc"

management_subnet: 192.168.101.0/24
management_start_address: 192.168.101.2
management_end_address: 192.168.101.50
management_gateway_address: 192.168.101.1

external_oam_subnet: 10.10.10.0/24
external_oam_gateway_address: 10.10.10.1
external_oam_floating_address: 10.10.10.12

systemcontroller_gateway_address: 192.168.204.101

docker_registries:
  k8s.gcr.io:
    url: registry.central:9001/k8s.gcr.io
  gcr.io:
    url: registry.central:9001/gcr.io
  ghcr.io:
    url: registry.central:9001/ghcr.io
  quay.io:
    url: registry.central:9001/quay.io
  docker.io:
    url: registry.central:9001/docker.io
  docker.elastic.co:
    url: registry.central:9001/docker.elastic.co
  registry.k8s.io:
    url: registry.central:9001/registry.k8s.io
  icr.io:
    url: registry.central:9001/icr.io
  defaults:
    username: sysinv
    password: <sysinv_password>
    type: docker

Where <sysinv_password> can be found by running the following command as 'sysadmin' on the Central Cloud:

$ keyring get sysinv services

In the above example, if the admin network is used for communication between the subcloud and system controller, then the management_gateway_address parameter should be replaced with admin subnet information.

For example:

management_subnet: 192.168.101.0/24
management_start_address: 192.168.101.2
management_end_address: 192.168.101.50
admin_subnet: 192.168.102.0/24
admin_start_address: 192.168.102.2
admin_end_address: 192.168.102.50
admin_gateway_address: 192.168.102.1

This configuration uses the local registry on your central cloud. If you prefer to use the default external registries, make the following substitutions for the docker_registries and additional_local_registry_images sections of the file.

docker_registries:
  defaults:
   username: <your_wrs-aws.io_username>
   password: <your_wrs-aws.io_password>

Note

If you have a reason not to use the Central Cloud's local registry you can pull the images from another local private docker registry.

You can use the Central Cloud's local registry to pull images on subclouds. The Central Cloud's local registry's HTTPS certificate must have the Central Cloud's IP, registry.local and registry.central in the certificate's list. For example, a valid certificate contains a list "DNS.1: registry.local DNS.2: registry.central IP.1: <floating management\> IP.2: <floating OAM\>".

If required, run the following command on the Central Cloud prior to bootstrapping the subcloud to install the new certificate for the Central Cloud with the updated list:
```
~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
```
At the Central Cloud / system controller, monitor the progress of the subcloud bootstraping and deployment by using the deploy status field of the dcmanager subcloud list command.

You can also monitor detailed logging of the subcloud bootstrapping and deployment by monitoring the following log files on the active controller in the Central Cloud.

/var/log/dcmanager/ansible/<subcloud_name>_playbook.output.log

For example:

controller-0:/home/sysadmin# tail /var/log/dcmanager/ansible/subcloud1_playbook.output.log
k8s.gcr.io: {password: secret, url: null}
quay.io: {password: secret, url: null}
)

TASK [bootstrap/bringup-essential-services : Mark the bootstrap as completed] ***
changed: [subcloud1]

PLAY RECAP *********************************************************************
subcloud1                  : ok=230  changed=137  unreachable=0    failed=0

Provision the newly installed and bootstrapped subcloud. For detailed deployment procedures for the desired deployment configuration of the subcloud, see the post-bootstrap steps of the .
Check and update docker registry credentials on the subcloud:
```
REGISTRY="docker-registry"
SECRET_UUID='system service-parameter-list | fgrep
$REGISTRY | fgrep auth-secret | awk '{print $10}''
SECRET_REF='openstack secret list | fgrep $
{SECRET_UUID} | awk '{print $2}''
openstack secret get ${SECRET_REF} --payload -f value
```
The secret payload should be username: sysinv password:<password>. If the secret payload is username: admin password:<password>, see, Updating Docker Registry Credentials on a Subcloud <updating-docker-registry-credentials-on-a-subcloud> for more information.
For more information on bootstrapping and deploying, see the procedures listed under install-a-subcloud.

13 KiB Raw Blame History

Install a Subcloud Without Redfish Platform Management Service

13 KiB

Raw Blame History