Jump to: navigation, search

Difference between revisions of "Cloudpulse/OperatorTests"

 
Line 1: Line 1:
 
== Operator Tests ==
 
== Operator Tests ==
  
=== Ubuntu OS Packages ===
+
Perform the following steps to use cloudpulse to run operator tests. For Operator tests, only containerized environments are supported.
The following required packages are to be installed in ubuntu
 
  
* sudo apt-get update
+
=== Install RPM Packages ===
* sudo apt-get install ansible
+
The following RPM packages need to be installed.
  
=== SSH Keys ===
+
yum install -y ansible
  
The Operator Tests run an ansible playbook on the Target nodes and get the required information for the operator Tests.
+
=== Setup SSH Keys ===
  
To enable cloudpulse do operator tests the ssh keys have to be created and added to the authorized keys in all the target systems from the host running cloudpulse.
+
Operator test runs an ansible playbook on the target nodes and gets the required information.
 +
To enable cloudpulse to do operator tests the ssh keys have to be created and added to the authorized keys in all the target systems from the host running cloudpulse.
  
* ssh-keygen  
+
ssh-keygen
* ssh-copy-id -i ~/.ssh/id_rsa.pub "controllernode"
+
ssh-copy-id -i ~/.ssh/id_rsa.pub "<target_node_ip>"
  
=== Configuration File Changes ===
+
=== Create node configuration file ===
  
The following configurations are needed in /etc/cloudpulse/cloudpulse.conf for testing operator tests.
+
Location of node configuration file needs to be provided to cloudpulse.conf to do operator tests:
  
[operator_test]
+
[operator_test]
operator_setup_file = /etc/cloudpulse/openstack_config.yaml
+
operator_setup_file = <path_nodes_config.yaml>
containerized = True
 
rabbit_container = rabbitmq_v1
 
galera_container = mariadb_v1
 
  
The operator setup file contains the information in the following format
+
The node configuration file contains the information in the following format:
  
control-1:
+
## nodes_config.yaml
    ip: 172.22.191.164
+
## Modify and place this file in any location <path_nodes_config.yaml>.
    user: root
+
    role: controller
+
# Format
    galerauser: wsrepuser
+
#<node-name>:
    galerapassword: 12345677
+
#    ip: <IP-address>
 
+
#    user: root
The "containerized" keyword tells us if the operator tests have to be done inside a container or on the controller itself.If the services are running inside a container then the name of the containers should be given in rabbit_container and galera_container.
+
#    role: <compute, control, storage>
 +
 +
#E.g:
 +
gg31-1-compute-1:
 +
    ip: <compute_node_1_ip>
 +
    user: root
 +
    role: compute
 +
gg31-1-controller-1:
 +
    ip: <controller_node_1_ip>
 +
    user: root
 +
    role: control compute
 +
    galerauser: <galera_user_name>
 +
    galerapassword: <galera_password>
 +
gg31-1-controller-2:
 +
    ip: <controller_node_2_ip>
 +
    user: root
 +
    role: control
 +
    galerauser: <galera_user_name>
 +
    galerapassword: <galera_password>
 +
gg31-1-controller-3:
 +
    ip: <controller_node_3_ip>
 +
    user: root
 +
    role: control
 +
    galerauser: <galera_user_name>
 +
    galerapassword: <galera_password>
 +
 +
=== Run Operator Tests ===
 +
cloudpulse-server --config-file <path_cloudpulse.conf>

Latest revision as of 15:27, 6 July 2017

Operator Tests

Perform the following steps to use cloudpulse to run operator tests. For Operator tests, only containerized environments are supported.

Install RPM Packages

The following RPM packages need to be installed.

yum install -y ansible

Setup SSH Keys

Operator test runs an ansible playbook on the target nodes and gets the required information. To enable cloudpulse to do operator tests the ssh keys have to be created and added to the authorized keys in all the target systems from the host running cloudpulse.

ssh-keygen
ssh-copy-id -i ~/.ssh/id_rsa.pub "<target_node_ip>"

Create node configuration file

Location of node configuration file needs to be provided to cloudpulse.conf to do operator tests:

[operator_test]
operator_setup_file = <path_nodes_config.yaml>

The node configuration file contains the information in the following format:

## nodes_config.yaml
## Modify and place this file in any location <path_nodes_config.yaml>.

# Format
#<node-name>:
#    ip: <IP-address>
#    user: root
#    role: <compute, control, storage>

#E.g:
gg31-1-compute-1:
    ip: <compute_node_1_ip>
    user: root
    role: compute
gg31-1-controller-1:
    ip: <controller_node_1_ip>
    user: root
    role: control compute
    galerauser: <galera_user_name>
    galerapassword: <galera_password>
gg31-1-controller-2:
    ip: <controller_node_2_ip>
    user: root
    role: control
    galerauser: <galera_user_name>
    galerapassword: <galera_password>
gg31-1-controller-3:
    ip: <controller_node_3_ip>
    user: root
    role: control
    galerauser: <galera_user_name>
    galerapassword: <galera_password>

Run Operator Tests

cloudpulse-server --config-file <path_cloudpulse.conf>