Deploying the Inception Server
To deploy the Inception Server, use the following configuration:
-
Login to the host, which has the Base OS installed.
-
Create a temporary folder to store the downloaded offline SMI Cluster Manager products tarball.
mkdir /data/offline-cm
Example:user1@testaio:~$ mkdir /data/offline-cm user1@testaio:~$ cd /data/offline-cm/ user1@testaio:/data/offline-cm$
-
Fetch the desired tarball to the newly created temporary folder. You can fetch the tarball either from the artifactory or copy it securely through the scp command.
/data/offline-cm$ wget --user [user] --ask-password [password] <repository_url>
In the following example, the tarball is fetched from the artifactory using basic authentication:
Example:
user1-cloud@testaio-cmts-control-plane:/data/offline-cm$ wget --user [user1] --password [user@123] <http://<repo_url>/cluster-deployer-2020-04-12.tar>
-
Untar the offline Cluster Manager tarball.
/data/offline-cm$ tar xvf <filename>
Example:
user1@testaio-cmts-control-plane:/data/offline-cm$ tar xvf cluster-deployer-2020-04-12.tar
-
Navigate to the deployer-inception folder which has the required charts and docker files.
/data/offline-cm/data$ cd deployer-inception/
Example:user1@testaio-cmts-control-plane:/data/offline-cm/data$ cd deployer-inception/
-
Run the following command to deploy the Inception Server.
sudo ./deploy --external-ip <external_ipaddress> --first-boot-password "<first_boot_password>"
Note-
During a fresh installation of the Inception Server, you can load the first boot configuration automatically through the deploy command. The first boot configuration is a YAML file which contains all the original passwords. Loading the first boot configuration is a one-time operation.
./deploy --external-ip <external_ipaddress> --first-boot-password '<first_boot_password>' --first-boot-config /var/tmp/cluster-config.conf
Example:user1@testaio-cmts-control-plane:/data/offline-cm/data/deployer-inception$./deploy --external-ip <ipv4address> --first-boot-password '<first_boot_password>' --first-boot-config /var/tmp/cluster-config.conf
-
For security reasons, ensure that the first boot configuration YAML file is not stored anywhere in the system after you bring up the Inception server.
Example:user1@testaio-cmts-control-plane:/data/offline-cm/data/deployer-inception$ ./deploy --external-ip <ipv4address> --first-boot-password '<first_boot_password>'
The following examples displays the connection details on the console when the Inception Server setup completes:
Connection Information ---------------------- SSH (cli): ssh admin@127.0.0.1 -p 2022 Files: https://files-offline.smi-deployer.10.85.109.252.nip.io API: https://restconf.smi-deployer.10.85.109.252.nip.io
-
-
Verify the list of the containers after the Inception Server is installed.
sudo docker ps
Example:
user@u20-inception-252:~/data/deployer-inception$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES de5dac28c575 //cluster_synchronizer:1.2.0-f000c25 "/usr/bin/npm run st…" 4 days ago Up 4 days smi-cluster-deployer_cluster_sync_1 f043cd13abaa //nginx:1.2.0-ff992e0 "/usr/local/bin/run-…" 4 days ago Up 4 days smi-cluster-deployer_ingress_1 0dee8eed93ef //metrics:1.2.0-9ae401f "python3 /usr/local/…" 4 days ago Up 4 days smi-cluster-deployer_metrics_1 eb1e13cf34e7 //confd_notifications:1.2.0-fe37e9e "/usr/local/bin/run-…" 4 days ago Up 4 days smi-cluster-deployer_confd_notifications_1 6a2a73827f38 //config_mgmt:1.2.0-61bfe40 "/usr/local/bin/run-…" 4 days ago Up 4 days smi-cluster-deployer_config_mgmt_1 079905616eba //cluster_offline_files:1.2.0-f42a431 "/usr/bin/supervisord" 4 days ago Up 4 days smi-cluster-deployer_cluster-offline-files_1 6453ec01a39f //confd:1.2.0-cc7013e "/usr/local/bin/uid_…" 4 days ago Up 4 days 0.0.0.0:443->443/tcp, :::443->443/tcp smi-cluster-deployer_confd_1 c3b45608d664 registry:2 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp
NoteFor upgrading the Inception server, see Upgrading the Inception Server section.
NOTES:
-
external_ipaddress —Specify the interface IP address that points to your Converged Interconnect Network (CIN) setup. It hosts the ISO and offline tars to be downloaded to the remote hosts.
-
first_boot_password —Specify the first boot password. The first boot password is a user-defined value.