Skip to content

Latest commit

 

History

History
254 lines (195 loc) · 7.6 KB

ProvisionReleaseBuild.md

File metadata and controls

254 lines (195 loc) · 7.6 KB
Raw

Deploy Cortx Build Stack

You will need to complete this guide before moving onto the steps below.

Before You Start

Checklist:

Single-Node VM Deployment

  • Please create VM(s) with at least 4 CPUs and 4 GB of RAM
  • For single-node VM deployment, ensure the VM is created with 2+ attached disks, in addition to at least 1 ide storage for OS.
    2+ disks is basic configuration that doesn't allow configuration of erasure coding. If one wishes to enable erasure coding, 8+ attached disks would be required.
  • Do you see the devices on execution of this command: lsblk ?
  • Do the systems on your setup have valid hostnames, are the hostnames accessible: ping ?
  • Do you have IPs' assigned to all NICs ensxx, ensxx and ensxx? 
    ip a
  • Identify primary node and run below commands on primary node
    NOTE: For single-node VM, the VM node itself is treated as primary node.

Pre-requisite

  • Change Hostname by running, 
    sudo hostnamectl set-hostname --static --transient --pretty deploy-test.cortx.com
    • Please use this hostname to avoid issues further in the bootstrap process.
    • Make sure the hostname is changed by running:
      hostname -f

Note: You can change the hostname as per your requirement

  • Disable SElinux by running, 
    sed -i 's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config

Note: Reboot the VM by running reboot command after disabling SElinux

  • Set repository URL 
    export CORTX_RELEASE_REPO="file:///var/artifacts/0"

Procedure for VM Deployment Steps

1. Install Provisioner API and requisite packages

yum install -y yum-utils
yum-config-manager --add-repo "${CORTX_RELEASE_REPO}/3rd_party/"
yum-config-manager --add-repo "${CORTX_RELEASE_REPO}/cortx_iso/"

cat <<EOF >/etc/pip.conf
[global]
timeout: 60
index-url: $CORTX_RELEASE_REPO/python_deps/
trusted-host: $(echo $CORTX_RELEASE_REPO | awk -F '/' '{print $3}')
EOF

# Cortx Pre-requisites
yum install --nogpgcheck -y java-1.8.0-openjdk-headless
yum install --nogpgcheck -y python3 cortx-prereq sshpass

# Pre-reqs for Provisioner
yum install --nogpgcheck -y python36-m2crypto salt salt-master salt-minion

# Provisioner API
yum install --nogpgcheck -y python36-cortx-prvsnr

# Verify provisioner version (0.36.0 and above)
provisioner --version

2. Cleanup temporary repos

rm -rf /etc/yum.repos.d/*3rd_party*.repo
rm -rf /etc/yum.repos.d/*cortx_iso*.repo
yum clean all
rm -rf /var/cache/yum/
rm -rf /etc/pip.conf

3. Create the config.ini file

Note: You can find the devices on your node by running below command to update in config.ini

device_list=$(lsblk -nd -o NAME -e 11|grep -v sda|sed 's|sd|/dev/sd|g'|paste -s -d, -)
  • Values for storage.cvg.0.metadata_devices: 
    echo ${device_list%%,*}
  • Values for storage.cvg.0.data_devices:
 echo ${device_list#*,}
  • You can find the interfaces as per zones defined in your setup by running,
 firewall-cmd --get-active-zones
  • Firewall must be disabled to connect to GUI and do IO operations
systemctl stop firewalld
systemctl disable firewalld
  • Configure config.ini file:

    • Find disks:

      device_list=\$(lsblk -nd -o NAME -e 11|grep -v sda|sed 's|sd|/dev/sd|g'|paste -s -d, -)

    • Open file:

      vi ~/config.ini

      Paste the code below into the config file replacing your network interface names with ens33,..ens35 and storage disks with /dev/sdb, /dev/sdc, ...

      Without erasure coding (2+ attached storage LUNs/disks)

      [srvnode_default]
network.data.private_interfaces=ens35
network.data.public_interfaces=ens34
network.mgmt.interfaces=ens33
storage.cvg.0.data_devices=/dev/sdc, /dev/sdd, /dev/sde, /dev/sdf, /dev/sdg, /dev/sdh, /dev/sdi
storage.cvg.0.metadata_devices=/dev/sdb
network.data.private_ip=192.254.254.254
storage.durability.sns.data=1
storage.durability.sns.parity=0
storage.durability.sns.spare=0
bmc.user=None
bmc.secret=None

[srvnode-1]
hostname=deploy-test.cortx.com
roles=primary,openldap_server

[enclosure_default]
type=other

[enclosure-1]

      With erasure coding enabled (8+ attached storage LUNs/disks)

      [srvnode_default]
network.data.private_interfaces=ens35
network.data.public_interfaces=ens34
network.mgmt.interfaces=ens33
storage.cvg.0.data_devices=/dev/sdc, /dev/sdd, /dev/sde, /dev/sdf, /dev/sdg, /dev/sdh, /dev/sdi
storage.cvg.0.metadata_devices=/dev/sdb
network.data.private_ip=192.254.254.254
storage.durability.sns.data=4
storage.durability.sns.parity=2
storage.durability.sns.spare=2
bmc.user=None
bmc.secret=None

[srvnode-1]
hostname=deploy-test.cortx.com
roles=primary,openldap_server

[enclosure_default]
type=other

[enclosure-1]

4. Bootstrap Node

 provisioner setup_provisioner srvnode-1:$(hostname -f) \
 --logfile --logfile-filename /var/log/seagate/provisioner/setup.log --source rpm \
 --config-path ~/config.ini \
 --dist-type bundle --target-build ${CORTX_RELEASE_REPO}

5. Prepare Pillar Data

Update data from config.ini into Salt pillar. Export pillar data to provisioner_cluster.json

 provisioner configure_setup ./config.ini 1
 salt-call state.apply components.system.config.pillar_encrypt
 provisioner confstore_export

Non-Cortx Group: System & 3rd-Party Softwares

  • System components:

    provisioner deploy_vm --setup-type single --states system

  • 3rd-Party components:

    provisioner deploy_vm --setup-type single --states prereq

Cortx Group: Utils, IO Path & Control Path

  • Utils component:

    provisioner deploy_vm --setup-type single --states utils

  • IO Path components:

    provisioner deploy_vm --setup-type single --states iopath

  • Control Path components:

    provisioner deploy_vm --setup-type single --states controlpath

Cortx Group: HA

  • HA components:

    provisioner deploy_vm --setup-type single --states ha

Start cortx cluster (irrespective of number of nodes):

  • Execute the following command on primary node to start the cluster:

    cortx cluster start

  • Verify cortx cluster status:

    hctl status

Usage:

Follow this guide to setup the GUI. Then to test your system upload data using this guide

Tested by:

  • May 24 2021: Mukul Malhotra ([email protected]) on a Windows laptop running VMWare Workstation 16 Pro.
  • May 12, 2021: Christina Ku ([email protected]) on VM "LDRr2 - CentOS 7.8-20210511-221524" with 2 disks.
  • May 11, 2021: Patrick Hession ([email protected]) on a Windows laptop running VMWare Workstation 16 Pro.
  • Jan 6, 2021: Patrick Hession ([email protected]) on a Windows laptop running VMWare Workstation 16 Pro.