Host provisioning

host-provision.sh takes a newly-delivered BMS host to a state where install-oracle.sh can be run, including:

Creating a user on the BMS host to run automation code, including SSH authentication and sudo access
Optionally configure Internet access through a proxy server
If running Red Hat Enterprise Linux, register the BMS host using Red Hat’s subscription manager
Optionally use Linux LVM to create a volume for local Oracle software

For a RAC cluster, run host-provision.sh on each cluster node.

Pre-requisities

Follow BMS planning and implementation steps, including testing ssh connectivity as the customeradmin user.
Obtain the customeradmin password, which will be prompted for in the host-provision.sh run.
If running Red Hat Enterprise Linux, obtain Red Hat credentials to request licenses.
Choose or create a host to run bms-toolkit from; this is typically the same jump host as created as part of BMS implementation. It will act as the ansible control node.
On the control node, download and extract bms-toolkit; in this example we take a zip file of the master branch:

curl -LO https://github.com/google/bms-toolkit/archive/refs/heads/master.zip
unzip master.zip
cd bms-toolkit-master

Parameters

--instance-ip-addr: IP address of the BMS host to provision.
--instance-ssh-user: username on the BMS host to run bms-toolkit commands as. The default is ansible.
--proxy-setup: configure a proxy server on the control node to provide BMS host Internet access; by default no proxy server will be configured.
--u01-lun: optionally configure Linux LVM for the software mount in Oracle RAC installs, for use in install-oracle.sh’s --ora-data-mounts option.

Sample invocations

To provision BMS host 172.16.30.1 to run as user ansible9 and to configure a proxy server:

./host-provision.sh --instance-ip-addr 172.16.30.1  --instance-ssh-user ansible9 --proxy-setup true

To provision BMS host 172.16.30.1 to run as user ansible9 without a proxy server, and also to configure Linux LVM on device /dev/mapper/3600a098038314473792b51456555712f:
```
./host-provision.sh --instance-ip-addr 172.16.30.1  --instance-ssh-user ansible9 \
--u01-lun /dev/mapper/3600a098038314344372b4f75392d3850
```

Proxy server

If the BMS host requires outgoing Internet access (to access Red Hat license servers, for example), there are several options. host-provision.sh can optionally configure Internet access through a proxy server on the control node. A proxy server can improve network security by restricting which Internet sites can be accessed, as well as auditing such access.

Linux LVM

BMS disk devices are presented as multipathed device nodes with the full world-wide name (WWN) of the device, such as /dev/mapper/3600a098038314344372b4f75392d3850. This presents an issue when configuring the data mount configuration file when running install-oracle.sh for RAC clusters, as each nodes will have separate software mounts with their own WWNs. The --u01-lun parameter addresses this issue by creating a Linux LVM volume with a consistent name /dev/mapper/db-sw that can be included in the data mount configuration file.

Schematic

With the caveat that code structure can quickly go out of date, the following represents the host-provision utility as it existed when this document was created.

Shows codeflow from host-utility.sh command line to the host-provision.yml entry point and on to the leaf scripts.

The aim of publishing the above code flow is not accuracy or up-to-date codemap, but rather function as a helpful start so the user can gain the basic understanding of the layout.