Difference between revisions of "Cloudpulse/OperatorTests"

Revision as of 23:45, 23 September 2015

Operator Tests

Ubuntu OS Packages

The following required packages are to be installed in ubuntu

sudo apt-get update
sudo apt-get install ansible

SSH Keys

The Operator Tests run an ansible playbook on the Target nodes and get the required information for the operator Tests.

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.

ssh-keygen
ssh-copy-id -i ~/.ssh/id_rsa.pub "controllernode"

Configuration File Changes

The following configurations are needed in /etc/cloudpulse/cloudpulse.conf for testing operator tests.

[operator_test] operator_setup_file = /etc/cloudpulse/openstack_config.yaml containerized = True rabbit_container = rabbitmq_v1 galera_container = mariadb_v1

The operator setup file contains the information in the following format

control-1:

   ip: 172.22.191.164
   user: root
   role: controller
   galerauser: wsrepuser
   galerapassword: 12345677

The "containerized" keyword tells us if the openrator 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.

@@ Line 1: / Line 1: @@
-== To Install CloudPulse Server ==
+== Operator Tests ==
 === Ubuntu OS Packages ===
@@ Line 5: / Line 5: @@
 * sudo apt-get update
-* sudo apt-get install python-pip python-dev libmysqlclient-dev
+* sudo apt-get install ansible
-=== PIP required packages ===
+=== SSH Keys ===
-The required pip modules to be installed
-pip install pbr oslo.config pecan keystonemiddleware wsme oslo.concurrency paramiko eventlet oslo.messaging oslo.versionedobjects oslo.db netifaces MySQL-python
+The Operator Tests run an ansible playbook on the Target nodes and get the required information for the operator Tests.
-=== Mysql commands ===
+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.
-The Mysql commands required for setting up the database .(To be run in the controller)
+* ssh-keygen
+* ssh-copy-id -i ~/.ssh/id_rsa.pub "controllernode"
-* CREATE DATABASE cloudpulse;
-* GRANT ALL PRIVILEGES ON cloudpulse.* TO 'cloudpulse'@'localhost' IDENTIFIED BY 'password';
-* GRANT ALL PRIVILEGES ON cloudpulse.* TO 'cloudpulse'@'%' IDENTIFIED BY 'password';
-* create table `cpulse` ( id int NOT NULL AUTO_INCREMENT, uuid VARBINARY(128), name VARCHAR(128), state VARCHAR(128), created_at timestamp default current_timestamp, updated_at  timestamp default 0,testtype VARBINARY(128),result TEXT ,primary key (id));>
-=== Openstack commands ===
-The following services have to be setup to make cloudpulse as a service.
-* openstack user create --password-prompt cloudpulse  [prompt will appear asking for password]
-* openstack role add --project  service --user cloudpulse admin
-*  openstack service create  cloudpulse --description "Openstack Health service" --type health
-* openstack endpoint create --publicurl http://controller:9999 --internalurl http://controller:9999 --adminurl http://controller:9999 --region RegionOne cloudpulse
 === Configuration File Changes ===
-[database]
-connection = mysql://cloudpulse:password@controller/cpulse?charset=utf8<br />
-[keystone_authtoken]<br />
-...<br />
-auth_uri = http://controller:5000/v2.0<br />
-project_domain_id = default<br />
-project_name = service<br />
-user_domain_id = default<br />
+The following configurations are needed in /etc/cloudpulse/cloudpulse.conf for testing operator tests.
-password = password<br />
+[operator_test]
+operator_setup_file = /etc/cloudpulse/openstack_config.yaml
+containerized = True
+rabbit_container = rabbitmq_v1
+galera_container = mariadb_v1
-username = cloudpulse<br />
+The operator setup file contains the information in the following format
-auth_url = http://controller:35357<br />
+control-1:
+    ip: 172.22.191.164
+    user: root
+    role: controller
+    galerauser: wsrepuser
+    galerapassword: 12345677
-auth_plugin = password</nowiki><br />
+The "containerized" keyword tells us if the openrator 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.