cortx py utils multi node manual provisioning

Pre-Requisites

Kafka Server (on all the nodes)

• Kafka server has been installed at path /opt/kafka. Kafka configuration is complete and it is running. For more details refer Kafka setup. Note that kafka may not be installed on all the nodes in CORTX cluster.

Required python packages

Refer Required python packages to get the list of required python packages.

Install cortx-py-utils rpm (on all nodes in the CORTX cluster)

Get the rpm.
#yum install -y cortx-py-utils-2.0.0-90_8b3c613.noarch.rpm <== RPM name would be different

Mini Provisioning steps

Post Install (on all nodes)

• Edit this template and store the filled in value /tmp/utils.post_install.tmpl.3-node
• Run config command
  /opt/seagate/cortx/utils/bin/utils_setup post_install --config yaml:///tmp/utils.post_install.tmpl.3-node

Config (on all nodes)

• Edit this template and store the filled in value /tmp/utils.config.tmpl.3-node

• cortx>software>common>message_bus_type ==> This indicates message bus type. Currently only "kafka" is supported.
• cortx>software>kafka>servers ==> This key holds an array of values. Each value is of type "server-FQDN":"port". Port is optional.

• Run config command
  /opt/seagate/cortx/utils/bin/utils_setup config --config yaml:///tmp/utils.config.tmpl.3-node
  NOTE: Config creates /etc/cortx/message_bus.conf

Validation and Test

Test (on a single node only - on a node where kafka is installed)

• Edit this template and store the filled in value /tmp/utils.test.tmpl.3-node

• Run the test command
  /opt/seagate/cortx/utils/bin/utils_setup test --config yaml:///tmp/utils.test.tmpl.3-node

• In test phase, it validates that message bus is working fine by below actions:

• create a message_type
• Send a test message using producer class
• Get that message using consumer class.
• If the received message matches with the sent one, return success.

Reset and Cleanup

Reset

• Run the reset command
  /opt/seagate/cortx/utils/bin/utils_setup reset

• In reset phase:

• It deletes all created message_types from all clustered nodes

Cleanup

• Run the cleanup command
  /opt/seagate/cortx/utils/bin/utils_setup cleanup

• In cleanup phase:

• It deletes config file /etc/cortx/message_bus.conf created by config phase