IBM Cloud Manager with OpenStack

https://www.ibm.com/docs/en/cmwo
Admin
IBM Cloud Manager with OpenStack is an enterprise cloud management solution that enables...
Tokens:437,309
Snippets:4,198
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Copy Example Cloud Topology File

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=nodes-prescribed-configuration

Copies a pre-defined example cloud topology YAML file from the IBM Cloud Manager installation path to the current deployment directory. Users should replace 'example-cloud.yml' with the specific topology file needed (e.g., example-controller-vmware-driver-cloud.yml) and 'your-cloud.yml' with their desired custom filename.

```bash
cp /opt/ibm/cmwo/cli/config/example-cloud.yml your-cloud.yml
```

--------------------------------

### Copy Example Cloud Configuration File (Bash)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=powervc-prescribed-configuration

This command copies a default example cloud configuration file to be used as a template for your specific cloud deployment. It assumes a default installation path for IBM Cloud Manager with OpenStack.

```Bash
$ cp /opt/ibm/cmwo/cli/config/example-controller-powervc-driver-cloud.yml your-cloud.yml
```

--------------------------------

### Swift Installation Script 1: Controller Node Setup

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=openstack-installing-object-storage-swift-manually

This shell script is designed to be run on the controller node as part of the Swift installation process. It sets up OpenStack environment variables, retrieves the admin token, and configures the service project and its ID. Key variables like KEYSTONE_IP and IP_ADDR need to be replaced with actual IP addresses.

```bash
#!/bin/sh
echo "Running $0"
set -x

function get_id {
    echo `"$@" | grep ' id ' | awk '{print $4}'`
}

KEYSTONE_IP={{controller.ip}}
# Get service token from keystone.conf, and decrypted the token
export OS_TOKEN=`grep "^[[:space:]]*admin_token" /etc/keystone/keystone.conf  |
awk -F'='  '{print $2}' | sed  's/^[[:space:]]*//' | xargs openstack-obfuscate  -u`

export OS_IDENTITY_API_VERSION=3
export OS_URL="http://$KEYSTONE_IP:35357/v3"
export OS_USER_DOMAIN_ID=default
export OS_PROJECT_DOMAIN_ID=default

IP_ADDR={{swift node ip}}
SERVICE_PROJECT_NAME=service
SWIFT_PWD=swift
REGION=RegionOne
#Change this port to other available port if Self-Service Portal(SSP) used 8080 port.
PORT=8080
VERSION_SWIFT=v1
ADMIN_ROLE_ID=$(get_id openstack role show admin)

# Setting up tenants.
echo "Setting up tenants..."
# Attempt to get the SERVICE_PROJECT_ID.
SERVICE_PROJECT_ID=$(get_id openstack project show $SERVICE_PROJECT_NAME)
if [ -z $SERVICE_PROJECT_ID ]; then
    # Create the tenant if none existed.
    SERVICE_PROJECT_ID=$(get_id openstack project create --name $SERVICE_PROJECT_NAME --description 'Service Tenant')
fi
echo "SERVICE_PROJECT_ID='$SERVICE_PROJECT_ID'"
if [ -z $SERVICE_PROJECT_ID ]; then
    echo "Unable to get the SERVICE_PROJECT_ID from $SERVICE_PROJECT_NAME."
    echo "The script can not continue without a valid id."
    echo "Fix the problem with keystone and run the script again."
    exit 1
fi

```

--------------------------------

### Start OpenStack Instance without Network Metadata (CLI)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=customizations-configuring-windows-guest-customization-specification

Starts a new virtual machine instance using the Nova CLI, specifying flavor, image, and basic administrator password metadata. This example omits detailed network device configurations, relying on default network configurations. It requires the OpenStack CLI client.

```bash
nova --flavor 3 --image 99504080-e08d-4cd2-a1b8-84725c1863d9 
--meta administrator.password=passw1rd --nic 
net-id=adc40cf9-528c-4a9e-b450-1fb90e384b01,v4-fixed-ip=10.9.7.113 yang113-w12-createImage
```

--------------------------------

### Shell Script: Executing Database Creation Commands

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=database-preparing

This section provides examples of how to execute the `create_dbs.sh` script to create databases. It shows commands for creating databases for a single region, multiple specified regions, or adding a database for an additional region. The script requires the DB2 instance to be started beforehand.

```shell
# Creates the database for a single region server only.
./create_dbs.sh region

# Creates the databases for three region servers.
./create_dbs.sh region=1,2,3

# Adds a database for a third region server.
./create_dbs.sh region=3
```

--------------------------------

### Enable NoSQL Service (Shell)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=database-preparing

This function enables the NoSQL service by configuring database credentials, setting up necessary directories, and starting the NoSQL listener. It determines various configuration parameters like host, port, user, and password from environment variables and helper functions. It utilizes `db2nosql.sh` for setup and `wplistener.sh` for managing the listener.

```shell
function enable_nosql()
{
    db_host=$(hostname -f)
    db_nosqlport=$(adjust_nosqlport ${OS_CEIL_DB_NOSQLPORT})
    db_user=$(adjust_user ${OS_CEIL_DB_USER})
    db_pwd=${OS_CEIL_DB_PWD}
    db_name=${OS_CEIL_DB_NAME}
    usermod -G `id -g $DB2_INSTANCE_USER` $db_user
    db2_dir=`db2ls | awk '{print $1}' | grep ^/`
    jdk_dir_name=`ls $db2_dir/java | grep jdk`
    java_home=$db2_dir/java/$jdk_dir_name
    json_log_path=/home/$DB2_INSTANCE_USER/json/logs
    db_port=$DB2_INSTANCE_PORT
    su - $DB2_INSTANCE_USER -c "mkdir -p $json_log_path"
    su - $DB2_INSTANCE_USER -c "export PATH=$PATH:$java_home/bin; cd $db2_dir/json/bin && ./db2nosql.sh -user $db_user -hostName $db_host -port $db_port -db $db_name -setup enable -password $db_pwd"
    su - $DB2_INSTANCE_USER -c "export JAVA_HOME=$java_home; cd $db2_dir/json/bin; ./wplistener.sh -shutdown -logPath $json_log_path -mongoPort $db_nosqlport -userid $db_user -password $db_pwd -dbName $db_name -noSQLHost $db_host </dev/null &> /dev/null"
    su - $DB2_INSTANCE_USER -c "export JAVA_HOME=$java_home; cd $db2_dir/json/bin; echo $db_pwd | nohup ./wplistener.sh -start -logPath $json_log_path -mongoPort $db_nosqlport -userid $db_user -dbName $db_name < /dev/null &> /dev/null &"
}
```

--------------------------------

### Validate IBM Spectrum Scale Cookbook Installation

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=integration-spectrum-scale-prerequisites

This command lists installed cookbooks on the Chef server and filters for 'ibm-spectrum-scale' to verify its presence after the IBM Cloud Manager with OpenStack installation.

```bash
[root@10-4-0-115 ~]# knife cookbook list|grep -i spectrum
```

--------------------------------

### Deploy Nova Instance with Network Metadata

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=customizations-customizing-network-settings-vmware-linux-guests

This example shows how to launch a virtual machine instance using the 'nova boot' command. It specifies the flavor, image, network ID, and various metadata parameters for network configuration, including DNS, IP address, netmask, gateway, DNS suffix, domain name, and hostname. This allows for detailed network customization during instance creation.

```bash
nova boot --flavor 10 --image  xiej-rh65-template 
--nic net-id=4ba1523c-2343-4368-bada-aed9beafdffa
--meta linux.dns1=10.9.0.14  --meta "networkdevice.Network adapter 1.ipaddress"=10.9.0.236 
--meta "networkdevice.Network adapter 1.netmask"=255.255.252.0 
--meta  "networkdevice.Network adapter 1.gateway1"=10.9.0.1 --meta dns.suffix=sce.cn.ibm.com 
--meta linux.domainname=xj-domainname test-cust-236 –meta linux.hostname test
```

--------------------------------

### Initialize Deployment Directory and Copy Environment

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=support-advanced-configuration-ha-controller-nodes

This code snippet demonstrates the initial steps for setting up a deployment. It involves creating a specific directory for deployment files, setting appropriate permissions, and then copying an example environment configuration file in JSON format using the `knife` command. The output is directed to a file named with the provided environment name.

```shell
$ mkdir your-deployment-name
$ chmod 600 your-deployment-name
$ cd your-deployment-name
$ knife environment show example-ibm-os-ha-controller-n-compute -d -F json > your-environment-name.json
```

--------------------------------

### Install EPEL Repository for Contrail Dependencies

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=cnpis-advanced-configuration-ha-controller-nodes

Installs the EPEL (Extra Packages for Enterprise Linux) repository, which provides additional RPM packages required for Contrail setup. This command installs the repository configuration file.

```bash
$> yum install epel-release-latest-7.noarch.rpm -Y
```

--------------------------------

### Install Required Tools (Yum)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=federation-configuring-keystone-identity-provider

Installs essential tools for Keystone federation setup using yum package manager. Dependencies include xmlsec1-openssl, python-pysaml2, and xmlsec1.

```bash
$ yum install xmlsec1-openssl
$ yum install python-pysaml2
$ yum install xmlsec1
```

--------------------------------

### Start Swift Services and Configure SELinux

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=openstack-installing-object-storage-swift-manually

This section outlines the process of enabling and starting all necessary Swift services, including account, container, and object related daemons, as well as the proxy service. It also includes a step to restore SELinux security contexts if SELinux is enabled, preventing potential permission issues.

```shell
#Start all Swift services
systemctl enable memcached.service rsyncd.service
SWIFT_ACCOUNT_SERVICES="account account-auditor account-reaper account-replicator"
for svc in $SWIFT_ACCOUNT_SERVICES; do
    systemctl enable openstack-swift-$svc;
    systemctl start openstack-swift-$svc;
done

SWIFT_CONTAINER_SERVICES="container container-replicator container-updater container-auditor"
for svc in $SWIFT_CONTAINER_SERVICES; do
    systemctl enable openstack-swift-$svc;
    systemctl start openstack-swift-$svc;
done

SWIFT_OBJECT_SERVICES="object object-replicator object-updater object-auditor"
for svc in $SWIFT_OBJECT_SERVICES; do
    systemctl enable openstack-swift-$svc;
    systemctl start openstack-swift-$svc;
done

systemctl enable openstack-swift-proxy
systemctl start openstack-swift-proxy

#If enabled selinux, it may need to run this to prevent permission issue in selinux 
restorecon -R /var/cache/swift 

echo "Swift script complete"
```

--------------------------------

### Help and Usage Information (Bash)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=database-preparing

This function displays the usage instructions and examples for running the database creation script. It explains how to specify single or multiple regions and reminds the user to set environment variables.

```bash
function show_help()
{
    echo -e "Usage:"
    echo -e "\t./create_dbs.sh region\t- create databases for single region server"
    echo -e "\t./create_dbs.sh region=1,2,3,...\t- create databases for multiple region servers"
    echo -e ""
    echo -e "Notice:"
    echo -e "\tBefore creating database, please set environment variables correctly:"
    echo -e ""
    echo -e "Examples:"
    echo -e "\tCreate databases for one region server on this machine:"
    echo -e "\t./create_dbs.sh region"
    echo -e ""
    echo -e "\tCreate databases for multiple region servers on this machine:"
    echo -e "\t./create_dbs.sh region=1,2,3"
}
```

--------------------------------

### Install EPEL Repository for Contrail

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=cnpis-advanced-configuration

Installs the EPEL (Extra Packages for Enterprise Linux) repository, which provides additional packages required for the Contrail setup. This command downloads and installs the `epel-release` RPM. The EPEL repository has a higher priority (90) to ensure its packages are preferred.

```shell
$> yum install epel-release-latest-7.noarch.rpm -Y

```

--------------------------------

### Create SSL Certificate Files (Keystone)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=federation-configuring-keystone-identity-provider

Sets up SSL certificate files for Keystone. This involves running the pki_setup command and adjusting file permissions for the private key directory and its contents.

```bash
$ keystone-manage pki_setup --keystone-user keystone --keystone-group keystone
$ chmod 755 /etc/keystone/ssl/private
$ chmod 644 /etc/keystone/ssl/private/*
```

--------------------------------

### JSON Topology Configuration Example

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=configuration-vmware-esxi-hosts

This JSON snippet shows a sample configuration for a topology, including run order and a list of roles or recipes to be executed. It is part of a larger deployment or configuration process.

```json
{
      "quit_on_error":true,
      "run_order_number":1,
      "runlist": [
              "role[ibm-os-single-controller-vmware-driver]",
              "role[ibm-os-prs-ego-master]",
              "role[ibm-os-prs-controller-node]",
              "role[ibm-os-prs-compute-node]",
              "recipe[ibm-openstack-vmware-driver::ceilometer]"
             ]
      }
      ]
}
```

--------------------------------

### HTTP GET Request for Filtering Cloud API Requests

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=services-get-requests

Demonstrates how to construct HTTP GET requests to filter cloud API requests. It shows examples of filtering by user and resolved status, and by parameters and state. No HTTP body is required for these requests.

```HTTP
GET http://host/cloud/api/requests?user=myuser&resolved=true
GET http://host/cloud/api/requests?parameters=deployment:10,12,22&state=PENDING,REJECTED
```

--------------------------------

### Copy Example Cloud Configuration File (Shell)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=environment-deploying-premises-region

This command copies the example cloud configuration file to a new file, which will be customized for the specific cloud environment. This is a prerequisite for configuring and deploying the cloud.

```shell
$ cp /opt/ibm/cmwo/cli/config/ example-icos-hybrid-controller-n-compute-kvm-cloud.yml 
your-icos-hybrid-cloud.yml
```

--------------------------------

### Configure Chef Server PostgreSQL Shared Buffers

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=integration-spectrum-scale-prerequisites

This configuration is necessary for controller nodes with a large amount of memory (e.g., above 64GB) to prevent installation issues. It modifies the PostgreSQL shared_buffers setting in the chef-server.rb file.

```ruby
postgresql['shared_buffers']='12288MB'
```

--------------------------------

### Generate SSH Key Pair and Distribute

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=integration-spectrum-scale-prerequisites

This section details the process of generating an SSH public key on a new node and distributing it to all other nodes to enable passwordless SSH communication. This is a prerequisite for Spectrum Scale installation.

```bash
ssh-keygen
```

```bash
for i in $NODE1 $NODE2 $NODE3 $NODE4 $NODE5 $NODE6 $NEWNODE; run ssh-copy-id root@$i; done
```

```bash
scp root@$NODE1:~/.ssh/authorized_keys ~/.ssh/
```

--------------------------------

### Boot Instance with Flavor (OpenStack Nova)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=customizations-configuring-ephemeral-disk-support-vmware

This command deploys a new virtual machine instance using a specified flavor and image. The flavor dictates the instance's resources, including whether it has an ephemeral disk. Ensure the flavor ID corresponds to the desired ephemeral disk configuration.

```bash
nova boot –flavor FLAVOR_ID –image IMAGE_ID INSTANCE_NAME
```

--------------------------------

### Copy Example Environment for Topology Deployment (Shell)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=configuration-vmware-ha-deployment

This command copies an example environment configuration file in JSON format, which is essential for defining the topology of your deployment. The '-d' flag includes default attributes, and '-Fjson' ensures JSON output.

```shell
$ knife environment show example-ibm-os-ha-controller-n-compute -d -Fjson > your-environment-name.json
```

--------------------------------

### Boot Instance with Block Device Info (OpenStack Nova)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=customizations-configuring-ephemeral-disk-support-vmware

This command boots a virtual machine instance and allows detailed specification of block device information, including ephemeral disks. It provides more granular control over storage than simply selecting a flavor, enabling the definition of source, destination, format, size, bus, and type for attached disks.

```bash
nova boot –flavor FALVOR_ID –image IMAGE -block-device source=blank, dest=local, format=ext4, size=2, bus=ide, type=disk INSTANCE_NAME
```

--------------------------------

### Configure YUM Repositories for RHEL

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=integration-spectrum-scale-prerequisites

This snippet shows how to configure YUM repositories on Red Hat Enterprise Linux nodes to access operating system and additional software packages required for installation. It includes settings for optional, update, and OS repositories.

```ini
[ftp3-optional]
   name=FTP3 Optional
   baseurl=ftp://<ftp3account>:<thepassword>@ftp3.linux.ibm.com/redhat/yum/7/server/optional/x86_64
   enabled=1
   gpgcheck=0
   priority=10
   sslverify=1
   
[ftp3-update]
   name=FTP3 update Optional
   baseurl=ftp://<ftp3account>:<thepassword>@ftp3.linux.ibm.com/redhat/yum/7/server/updates/x86_64
   enabled=1
   gpgcheck=0
   
[ftp3-os]
   name=FTP3 OS
   baseurl=ftp://<ftp3account>:<thepassword>@ftp3.linux.ibm.com/redhat/yum/7/server/os/x86_64
   enabled=1
   gpgcheck=0
   priority=10
   sslverify=1
```

--------------------------------

### Mount ISO Image for Package Installation

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=uninstalling-configuring-operating-system-yum-repositories

This section shows how to mount an ISO image to access its contents for copying packages. It involves creating a mount point and using the `mount` command with the loop option. Ensure the ISO file path is correct.

```bash
$ mkdir -p /mnt/iso
$ mount -o loop RHEL-7.2-20150219.1-Server-x86_64-dvd1.iso /mnt/iso
```

--------------------------------

### Enable Ceilometer Services for Boot (High Availability)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=support-how-disable-recover-ceilometer

Enables Ceilometer services to start automatically at boot time on controller nodes in a high availability setup.

```bash
systemctl enable openstack-ceilometer-api 
systemctl enable openstack-ceilometer-collector 
systemctl enable openstack-ceilometer-notification
systemctl enable openstack-ceilometer-central
systemctl enable openstack-ceilometer-alarm-evaluator 
systemctl enable openstack-ceilometer-alarm-notifier 
systemctl enable db2.nosql
```

--------------------------------

### Set Up NTP Server Synchronization on RHEL

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=integration-spectrum-scale-prerequisites

This section provides commands to set up and synchronize Network Time Protocol (NTP) on Red Hat Enterprise Linux nodes. Accurate time synchronization is crucial for distributed systems.

```bash
# yum install -y ntp
# ntpdate NTP server IP
# systemctl enable ntpd
# systemctl start ntpd
# timedatectl list-timezonesssh
# timedatectl set-timezone
# systemctl enable ntpd
```

--------------------------------

### Example Topology Run List with XIV/DS8000 Recipes

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=ccd-configuring-xiv-ds8000-cinder-driver-xiv-spectrum-accelerate

Illustrates a complete run list for a block storage node that includes the IBM OS block storage role and the necessary XIV / DS8000 Cinder driver recipes.

```json
"runlist": [
  "role[ibm-os-block-storage-node]",
  "recipe[xiv_ds8k::install]",
  "recipe[xiv_ds8k::configure]"
]
```

--------------------------------

### Copy Base Cloud Configuration File

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=qemu-prescribed-configuration

This command copies a base example cloud configuration file from the IBM Cloud Manager installation path to your deployment directory. You should rename the copied file to reflect your specific cloud environment. This file serves as the template for your deployment's cloud settings.

```bash
$ cp /opt/ibm/cmwo/cli/config/example-cloud.yml your-cloud.yml
```

--------------------------------

### Create Symbolic Links for Installation Media

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=uninstalling-configuring-operating-system-yum-repositories

This alternative method creates symbolic links to the 'Packages' and 'repodata' directories on the mounted installation media, instead of copying them. This saves disk space but requires ensuring the mount point persists across reboots.

```bash
$ cd /opt/ibm/cmwo/yum-repo/operatingsystem/redhat7.2/x86_64
$ ln -s /mnt/iso/Packages
$ ln -s /mnt/iso/repodata
```

--------------------------------

### Start OpenStack Instance with Full Network and Windows Metadata (CLI)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=customizations-configuring-windows-guest-customization-specification

Launches a virtual machine instance with extensive metadata, including Windows-specific settings (timezone, domain, workgroup, computer name, etc.) and detailed network device configurations for multiple adapters. This command utilizes the Nova CLI and requires proper OpenStack authentication.

```bash
nova boot --flavor 3 --image 99504080-e08d-4cd2-a1b8-84725c1863d9  
--meta change.sid=true --meta windows.workgroup=WORKGROUP 
--meta windows.computername=computerN --meta windows.organization=ibm.com 
--meta windows.username=ibm --meta windows.timezone=90 --meta dns.suffix=ibm.com 
--meta windows.admin.password=passw1rd --meta networkdevice.adapter1.dns1=10.9.6.12 
--meta networkdevice.adapter1.dns2=10.9.6.13 --meta networkdevice.adapter1.ipaddress=10.9.6.111 
--meta networkdevice.adapter1.netmask=255.255.255.0 
--meta networkdevice.adapter1.gateway1=10.9.6.1 --meta networkdevice.adapter1.gateway2=10.9.6.2  
--meta networkdevice.adapter1.primaryWINS=10.9.6.200  
--meta networkdevice.adapter1.secondaryWINS=10.9.6.201 --meta networkdevice.adapter2.dns1=10.9.7.22 
--meta networkdevice.adapter2.dns2=10.9.7.23 --meta networkdevice.adapter2.ipaddress=10.9.7.211 
--meta networkdevice.adapter2.netmask=255.255.255.0 --meta networkdevice.adapter2.gateway1=10.9.7.1 
--meta networkdevice.adapter2.gateway2=10.9.7.2  --meta networkdevice.adapter2.primaryWINS=10.9.7.200  
--meta networkdevice.adapter2.secondaryWINS=10.9.7.201 --nic net-id=46fd34b3-19c4-402b-b502-8e554f842960,v4-fixed-ip=10.9.6.111  
--nic net-id=adc40cf9-528c-4a9e-b450-1fb90e384b01,v4-fixed-ip=10.9.7.211 yang111-211-w12
```

--------------------------------

### Open vSwitch Bridge Mapping for Data Networks (JSON)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=powerkvm-advanced-configuration-ha-controller-nodes

Controls the creation of the data network OVS bridge. If Open vSwitch is installed and the data network bridge is pre-configured, this can be set to an empty string. For specific network configurations like bonding, set to an empty string and complete setup manually.

```json
{
  "openstack.network.openvswitch.bridge_mapping_interface": "br-eth1:eth1"
}
```

--------------------------------

### Mount DVD Device for Package Installation

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=uninstalling-configuring-operating-system-yum-repositories

This demonstrates mounting a physical DVD device containing installation media. It requires creating a mount point and using the `mount` command on the device node. The device name might vary.

```bash
$ mkdir -p /mnt/iso
$ mount /dev/cdrom /mnt/iso
```

--------------------------------

### Install Contrail Install Packages RPM

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=cnpis-advanced-configuration-ha-controller-nodes

Installs the primary Contrail installation package RPM. This action extracts the necessary Contrail RPMs into a tarball for further processing.

```bash
$> rpm –ivh \
/home/contrail3.0/contrail-install-packages-3.0.0.0-2723~kilo.el7.noarch.rpm
```

--------------------------------

### Configure Interfaces Template for Hyper-V Agent

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=agent-customizing-hyper

This snippet shows how to modify the 'interfaces.template' file for the IBM Cloud Manager with OpenStack Hyper-V Agent to enable config drive functionality when starting virtual machines. It details the default file path and provides an example of the template's structure.

```text
====================================================
# Injected by Nova on instance boot
#
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

{% for ifc in interfaces -%}
auto {{ ifc.name }}
iface {{ ifc.name }} inet static
        address {{ ifc.address }}
        netmask {{ ifc.netmask }}
        broadcast {{ ifc.broadcast }}
{%- if ifc.gateway %}
        gateway {{ ifc.gateway }}
{%- endif %}
{%- if ifc.dns %}
        dns-nameservers {{ ifc.dns }}
{%- endif %}

{% if use_ipv6 -%}
iface {{ ifc.name }} inet6 static
    address {{ ifc.address_v6 }}
    netmask {{ ifc.netmask_v6 }}
{%- if ifc.gateway_v6 %}
    gateway {{ ifc.gateway_v6 }}
{%- endif %}
{%- endif %}

{%- endfor %}
=====================================================
```

--------------------------------

### Install and Configure OpenStack Swift Proxy and Storage Nodes

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=openstack-installing-object-storage-swift-manually

This script installs and configures the OpenStack Swift proxy and storage packages on a Swift node. It creates a swift user and group, formats a disk image for Swift storage using XFS or ext4, and sets up the necessary configurations in /etc/swift/swift.conf and /etc/fstab.

```shell
#!/bin/sh
echo "Running $0"
set -x

KEYSTONE_IP={{controller.ip}}
IP_ADDR={{swift node ip}}
SERVICE_TENANT_NAME=service
SWIFT_PWD=swift
#Change this port to other available port if Self-Service Portal(SSP) used 8080 port.
PORT=8080

ARCH="NA"
archString=$(/bin/uname -a)
if [[ $archString == *ppc64* ]]; then
    ARCH="ppc64"
elif [[ $archString == *x86_64* ]];then
    ARCH="x86_64"
elif [[ $archString == *s390x* ]];then
    ARCH="s390x"
fi

# Add the swift user to the system
groupadd swift
useradd -g swift swift

#
# Installing and Configuring the Object Service
#
# Set the OS_USERNAME and OS_PASSWORD with Swift values for the setup scripts.
export OS_PASSWORD=swift
export OS_USERNAME=swift
export OS_USER_DOMAIN_ID=default
export OS_PROJECT_NAME=service
export OS_PROJECT_DOMAIN_ID=default
export OS_AUTH_URL="http://$KEYSTONE_IP:5000/v3"
export OS_IDENTITY_API_VERSION=3

# Install Openstack Swift storage packages
yum -y install openstack-swift-account openstack-swift-container openstack-swift-object
if [ $? -ne 0 ]; then
    echo "Could not install Swift storage packages."; exit 1;
fi
# Install Openstack Swift proxy packages
yum -y install openstack-swift-proxy
if [ $? -ne 0 ]; then
    echo "Could not install Swift proxy packages."; exit 1;
fi

# Set some random string of text as the suffix value.
RANDOM_STRING=$(cat /dev/urandom | head -n 15 | md5sum | head -c 15)
openstack-config --set /etc/swift/swift.conf swift-hash swift_hash_path_suffix $RANDOM_STRING

# Install xfs packages
yum -y install xfsdump xfsprogs-devel xfsprogs
XFS=1
if [ $? -ne 0 ]; then
    echo "Could not install XFS packages.";
    XFS=0
fi

# Create Swift backing disk
SWIFT_DATA_DIR=/srv/node
SWIFT_DISK_IMAGE=${SWIFT_DATA_DIR}/drives/images/swift.img
SWIFT_MOUNT_POINT=${SWIFT_DATA_DIR}/sdb1
mkdir -p ${SWIFT_MOUNT_POINT}
mkdir -p ${SWIFT_DATA_DIR}/drives
SWIFT_DRIVES_DIR=${SWIFT_DATA_DIR}/drives

# Create a loopback disk and format it to XFS
if [[ -e ${SWIFT_DISK_IMAGE} ]]; then
    if egrep -q ${SWIFT_MOUNT_POINT} /proc/mounts;
     then
        umount ${SWIFT_MOUNT_POINT}
        rm -f ${SWIFT_DISK_IMAGE}
    fi
fi

function write_to {
    # RTC 178288 : Checking the duplicated entries
    # Pass "check" as the 3rd argument to only write if the value isn't there already.
    if [ -f $2 ] && [[ $# -eq 3 ]] && [[ "$3" == 'check' ]]; then
        grep -q $1 $2
        if [ $? -eq 0 ]; then
            # do nothing
            return
        fi
    fi
    echo $1 >> $2
}

# create the file for the loopback device, modify size  specified in the truncate command to 
make a larger or smaller partition as needed.  In our example, we set it 1G.
mkdir -p ${SWIFT_DATA_DIR}/drives/images
touch ${SWIFT_DISK_IMAGE}
truncate -s 1G ${SWIFT_DISK_IMAGE}


# Mount the disk with mount options to make it as efficient as possible
mkdir -p ${SWIFT_MOUNT_POINT}
if [ $XFS -ne 0 ]; then
    # Make a fresh XFS filesystem
    mkfs.xfs -f -i size=1024 ${SWIFT_DISK_IMAGE}
    write_to "${SWIFT_DISK_IMAGE} ${SWIFT_MOUNT_POINT} xfs loop,noatime,nodiratime,nobarrier,logbufs=8 0 0" /etc/fstab
    mount ${SWIFT_MOUNT_POINT}
else
    # Make a fresh ext4 filesystem
    mkfs.ext4 -F -I 1024 ${SWIFT_DISK_IMAGE}
    mount -t ext4 -o loop ${SWIFT_DISK_IMAGE} ${SWIFT_MOUNT_POINT}
fi
#Change swift owner and groups
chown -R swift:swift ${SWIFT_DATA_DIR}

#If enabled selinux, it may need to run this to prevent permission issue in selinux 
restorecon -R  ${SWIFT_DATA_DIR}
```

--------------------------------

### Create and Secure Deployment Directory (Bash)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=cloud-multiple-hypervisor-types

This snippet demonstrates how to create a directory for your deployment, set restrictive permissions (only owner can read/write), and then navigate into that directory. This is the initial step to organize deployment-specific files.

```Bash
$ mkdir your-deployment-name
$ chmod 600 your-deployment-name
$ cd your-deployment-name
```

--------------------------------

### Install DB2 Fix Pack (Shell)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=updates-db2

This command initiates the installation of the DB2 fix pack. It requires the path to the installation directory as an argument. The command prompts the user to confirm or change the installation directory.

```shell
$ ./installFixPack -b /opt/ibm/db2/V10.5/
Do you want to choose a different installation directory for the fix pack? [yes/no]
------------------------------------------------------------------------------------
no
```

--------------------------------

### Linux on Power Silent Installation for IBM Cloud Manager

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=server-silent-installation

This command installs IBM Cloud Manager silently on a Linux on Power system. It makes the installer executable, creates a response file with the license accepted, and initiates the silent installation. The installer directory path must not contain spaces.

```shell
chmod +x ./cmwo430_plinux_install.bin

echo LICENSE_ACCEPTED=true > 
./installer.rsp; ./cmwo430_plinux_install.bin -i silent -f 
./installer.rsp
```

--------------------------------

### z/VM Compute Node Topology Example (JSON)

Source: https://www.ibm.com/docs/en/cmwo/4.3.0_topic=controller-deploying-new

An example snippet showing how to include z/VM compute nodes in a topology file. It illustrates the structure for defining z/VM specific roles and node details.

```json
{
  .....
    {
      "fqdn":"compute-juno.fqdn.com",
      "password":"password-juno",
      "quit_on_error":true,
      "run_order_number":2,
      "runlist": [
        "role[ibm-os-zvm-driver-node]",
        "role[ibm-os-prs-compute-node]"
      ]
    }  
  ]
}
```

```json
{
  ......
  "fqdn":"compute-kilo.fqdn.com",
  "password":"password-kilo",

```
Tokens:
Raw