- Get the Dell Telecom Infrastructure Automation Suite install bundle from Dell Digital Locker. You can initiate the installer from any Linux host that supports Docker runtime.
- You require three VMs for the three high availability (HA) nodes with the following user credentials:
- The username of an admin user with sudo privileges
- The sudo password for the management cloud VMs
- The packages that are required for Longhorn must be installed on all HA controller nodes. See Software requirements
Perform this procedure on the VM where you are installing the Dell Telecom Infrastructure Automation Suite cloud. This procedure installs and configures Dell Telecom Infrastructure Automation Suite with ansible and helm plug-ins. After the management cloud installation completes, you can install the Dell Telecom Infrastructure Automation Suite applications. Installation can take up to 45 minutes (depending on network conditions).
- Copy the installer bundle to the server.
scp DTIAS-bundle-v2.0.1.tar.gz <user>@<IP_ADDRESS>
- Log in as a user with sudo privileges to the server where you are installing Dell Telecom Infrastructure Automation Suite.
- Run the following command to untar the install bundle.
tar -xzvf DTIAS-bundle-v2.0.1.tar.gz
- Change directory to install bundle.
cd DTIAS-bundle-v2.0.1
- Edit the dtias_config.yaml file and update the required attributes using Vim or a similar editor. Save the file and quit the editor.
The following is an example dtias_config.yaml file:
ha:
enabled: true
vip: 192.168.207.45
storage_path: "/longhorn/"
# Set to true to restore DTIAF core services from a backup
restore_enabled: false
# Default timeout in seconds for the restore to finish
restore_timeout: 3600
# Region where the backup bucket is located. Optional
backup_storage_region: minio
# Name of the backup from which the restore will be.
backup_name: "replace-backup-name"
# Name the bucket where the backup is stored
backup_bucket_name: "replace-bucket"
# Url of where the backup is located. e.g. http://localhost:9000
backup_storage_url:
# Your AWS access key
opensearch_username: "admin"
opensearch_password: "admin"
velero_aws_access_key: "replace-access-key"
# Your AWS secret key
velero_aws_secret_key: "external_secretkey"
# Base64 encoded content of ca cert file
velero_ca_string: ""
# KMS Configuration
# Set to true to enable storage of secrets in a Key Management Service (KMS).
enable_kms: false
# Specify the KMS provider's name (e.g., "vault"). Leave empty if not using a KMS.
kms_provider: ""
# Define the IP address of the Key Management Service (KMS) host. e.g "http://1.2.3.8:8200"
kms_address: ""
# Provide the day-0 token required for communication with the Key Management Service (KMS).
kms_token: ""
# Provide the dedicated DTIAS namespace to use in the KMS
kms_namespace: ""
# Base64 encoded content of ca cert file for vault server
kms_ca_string: ""
# password for keycloak
keycloak_user_password: <PASSWORD>
keycloak_hostname: "flcm-oc-ha-envd"
license_file: ""
# Set to true to enable migration from source to current destination cluster
enable_migration: false
resources:
# Controller node (exactly 1 required regardless of ha enable)
- id: "CP1"
username: "dell"
ipaddress: "192.168.207.41"
password: <PASSWORD>
role: controller
# ha nodes (exactly 2 required in case of ha enabled set to true, 0 required in case of ha enabled set to false)
- id: "CP2"
username: "dell"
ipaddress: "192.168.207.42"
password: <PASSWORD>
role: ha
- id: "CP3"
username: "dell"
ipaddress: "192.168.207.43"
password: <PASSWORD>
role: ha
add worker node, optional
- id: "John-Doe-2-RG"
username: "user"
ipaddress: "1.2.3.4"
password: <PASSWORD>
role: worker
remove worker node, optional
- id: "John-Doe-3-RG"
username: "user"
ipaddress: "1.2.3.5"
password: <PASSWORD>
role: worker_remove
bmp_config:
bmpnode_id: bmonode_dp #bmp node resourece
# location - id and name fields must have the same value
Location:
Id: gc
Name: gc
Address:
City: Round Rock
Country: United States of America
State: Texas
Street: 501 Dell Way
Coordinates:
Latitude: '30.48421164465075'
Longitude: '-97.66330717434248'
Description: Dell Headquarters
GlobalLocationId: gc # should be same as bmo node resource
site:
id: gc-site # this will be the global site name for bmp
description: office site
res:
visibility: tenant
isPrivate: false
bmoSiteAttributes:
# DHCP Enable is work in progress
# Uncomment the below lines to enable DHCP
# dhcpConfig:
# defaultLeaseTime: 0
# dhcpSubnets: []
# dns: ""
# domain: ""
# interfaces: ""
# maxLeaseTime: 0
# vendorClassIds: []
# dhcpRelayConfig:
# dhcpForwardAddress: "" # Forwarding address
# interfaces: "" # Interface names
dhcpDeployMode: none
nodeName: ha-env-d-cp1 # node name of first controller
address:
street: 5450 Great America Pkwy
city: Malibu
state: California
country: USA
coordinates:
latitude: 37.404882
longitude: -121.978486
Labels: []
resourcePool:
Description: This is resource pool
Id: rp_dp
Name: rp_dp
dualstack: false
# Optional CIDR configuration for ipv4 only cluster
# If cluster_cidr and service_cidr are not set explicitly, they should use the default settings. i.e 10.42.0.0/16 and 10.43.0.0/16
# Uncomment the below lines to enable custom CIDR configuration with updated values. (Currently only /16 subnet is tested in this installer)
# cluster_cidr: "172.27.0.0/16"
# service_cidr: "172.28.0.0/16"For more information about the field definitions, see Dell Telecom Infrastructure Automation Suite fields.
Note:The
location - ID
andName
fields must have the same value in thedtias_config.yaml file
.
Note: You must remove the installer input file or remove all passwords from the installer input file after a successful Dell Telecom Infrastructure Automation Suite installation.
- Ensure that the servers hosting the cloud nodes meet the prerequisites that are mentioned above.
After making the required changes in
dtias_config.yaml
, run the following command in the DTIAS bundle to validate that all the prerequisites for the installation are met.INSTALL_TARGET=PREREQUISITE make install
- Perform one of the following steps:
- Run
make install
to install DTIAS. To upload and activate a license, see Dell Telecom Infrastructure Automation Suite licensing overview. - Run
INSTALL_TARGET=DTIB-RH make install
to install DTIAS and DTIB-RH on Day-0. Ensure to procure the license, place it in the bundle under the license directory, update the license file indtias_config.yaml
, and then run this command to install DTIB RH. For more information about license management, see Dell Telecom Infrastructure Automation Suite licensing overview.
Note: When DTIAS installation fails in a Red Hat Enterprise Linux 9.2 HA setup with security agents running, run this command to stop the service:sudo systemctl stop mfetpd
. After the installation is completed, run this command to start the service:sudo systemctl start mfetpd
.
Note: When installing DTIAS in an air-gapped environment (disconnected mode), be sure to add a default mock gateway. For air-gapped environments, use 127.0.0.1 as the nameserver IP address.
- Run