-
Notifications
You must be signed in to change notification settings - Fork 38
Cortx monitor 3 Node VM provisioning manual
Run below steps in all 3 nodes
-
Setup yum repo (Required only for installing build specific RPMS)
$yum-config-manager --add-repo http://cortx-storage.colo.seagate.com/releases/cortx/github/integration-custom-ci/centos-7.8.2003/custom-build-399/cortx_iso/
-
Install 3rd party packages
curl -s http://cortx-storage.colo.seagate.com/releases/cortx/third-party-deps/rpm/install-cortx-prereq.sh | bash
Ensure below 3rd party packages are installed.
-
RPMs
Package Version hdparm 9.43 ipmitool 1.8.18 lshw B.02.18 python3 3.6.8 python36-dbus 1.2.4 python36-gobject 3.22.0 python36-paramiko 2.1.1 python36-psutil 5.6.7 shadow-utils 4.6 smartmontools 7.0 systemd-python36 1.0.0 udisks2 2.8.4 -
Python
Package Version cryptography 2.8 jsonschema 3.2.0 pika 1.1.0 pyinotify 0.9.6 python-daemon 2.2.4 requests 2.25.1 zope.component 4.6.2 zope.event 4.5.0 zope.interface 5.2.0
-
-
Run cortx-py-utils pre-requisites
-
Install cortx-py-utils
-
Install SSPL RPMs
Find description, example and usage of config used across mini provisioner stages here
Note
-
Mini provisioner interfaces are supposed to be executed in following order
- post-install, prepare, config, init
- And when needed, remaining stages has no order dependency to execute, i.e for test, reset, cleanup
-
Config required at each mini provisioner stage is a super set of current plus previous stage config
-
Post Install
-
Run Utils post_install on all 3 nodes
-
Edit this template and store the file with filled in value at /tmp/sspl.post-install.tmpl.3-node on all 3 nodes
-
Run SSPL post_install on all 3 nodes
/opt/seagate/cortx/sspl/bin/sspl_setup post_install --config yaml:///tmp/sspl.post-install.tmpl.3-node
-
-
Prepare
-
Edit this template and store the file with filled in value at /tmp/sspl.prepare.tmpl.3-node on all 3 nodes
-
Run SSPL prepare on all 3 nodes
/opt/seagate/cortx/sspl/bin/sspl_setup prepare --config yaml:///tmp/sspl.prepare.tmpl.3-node
-
-
Config
-
Edit this template and store the file with filled in value at /tmp/sspl.config.tmpl.3-node on all 3 nodes
-
Run SSPL config on all 3 nodes
/opt/seagate/cortx/sspl/bin/sspl_setup config --config yaml:///tmp/sspl.config.tmpl.3-node
-
Init
-
Edit this template and store the file with filled in value at /tmp/sspl.init.tmpl.3-node on all 3 nodes
-
Run SSPL init on all 3 nodes
/opt/seagate/cortx/sspl/bin/sspl_setup init --config yaml:///tmp/sspl.init.tmpl.3-node
-
Run below stpes in all 3 nodes
-
Start SSPL service
systemctl start sspl-ll
-
Check service status
systemctl status sspl-ll
Note: Starting service using systemctl is recommended only when HA framework is not in place, otherwise service is supposed to be started in Cortx cluster automatically by HA
Run below step in all 3 node to execute tests
Note: Test check features on single node alone(on one which its executed)
-
Start SSPL tests with plan
/opt/seagate/cortx/sspl/bin/sspl_setup test --config <config_url> --plan [sanity|alerts|self_primary|self_secondary]
Ex. '
/opt/seagate/cortx/sspl/bin/sspl_setup test --config <config_url> --plan sanity