Installation and configuration¶

Installation¶

sudo -i

1. Save the list of previously installed packages before starting the installation, this will allow you to painlessly restore the system in case of damage. Run following commands to do this:

   mkdir -p /tmp/rollback/cloud_manager
   pip3 freeze > /tmp/rollback/cloud_manager/
   

   After that, directory /tmp/rollback/cloud_manager will contain file pip_before.txt with list of installed applications.

2. Also save migration versions:

   openstack aos db list -n cloud_manager > /tmp/rollback/cloud_manager/migrations.txt
   

   Where:

   • /tmp/rollback/cloud_manager/ is file directory;
   • migrations.txt is name of file with migration versions.

3. Install the package CloudManager:

   • from Python package repository:

     pip3 install cloud-manager
     

4. Save the list of installed packages after installation to be able to roll back changes:

   pip3 freeze > /tmp/rollback/cloud_manager/pip_after.txt
   

5. Add user:

   useradd -m aos
   passwd aos
   

Configuration¶

1. Perform initial configuration of the module:

   openstack aos configure -n cloud_manager
   

2. Create directory for logs with the required permissions:

   mkdir -p /var/log/aos/cloud-manager
   chown -R aos:aos /var/log/aos/cloud-manager
   

3. Copy sample configuration file, if using non-standard parameters, edit them (for details, see Configuration file):

   cp /etc/aos/aos.conf.example /etc/aos/aos.conf
   cp /etc/aos/cloud_manager.conf.example /etc/aos/cloud_manager.conf
   

4. Create database using MySQL as an example, set rights, database type and other parameters:

   # Login to the database using the root password
   mysql -uroot -p
   # Create cloud_manager database
   CREATE DATABASE cloud_manager;
   # Give permission to read, edit, perform any actions on all tables in cloud_manager database
   GRANT ALL PRIVILEGES ON cloud_manager.* TO 'aos'@'localhost' IDENTIFIED BY 'password';
   GRANT ALL PRIVILEGES ON cloud_manager.* TO 'aos'@'%' IDENTIFIED BY 'password';
   # Exit the database
   

5. Edit section [database] of the configuration file etc/aos/cloud_manager.conf, for example:

   [database]
   url = mysql+pymysql://aos:password@tst.stand.loc:3306/cloud_manager?charset=utf8
   

6. Migrate database:

   openstack aos db migrate -n cloud_manager
   

7. Configure RabbitMQ Server message broker:

   rabbitmqctl add_user aos password
   rabbitmqctl add_vhost aos
   rabbitmqctl set_permissions -p aos aos ".*" ".*" ".*"
   rabbitmqctl set_permissions aos ".*" ".*" ".*"
   

8. Create user in OpenStack for API services:

   openstack user create --domain default --project service --project-domain default --password password --or-show aos
   

9. Assign user service role:

   openstack role add --user aos --user-domain default --project service --project-domain default service
   

10. Enable and start systemd services:

    systemctl daemon-reload
    systemctl enable aos-cloud-manager-agent.service
    systemctl start aos-cloud-manager-agent.service
    systemctl enable aos-cloud-manager-api.service
    systemctl start aos-cloud-manager-api.service
    systemctl enable aos-cloud-manager-listener.service
    systemctl start aos-cloud-manager-listener.service
    systemctl enable aos-cloud-manager-beat.service
    systemctl start aos-cloud-manager-beat.service
    systemctl enable aos-cloud-manager-worker.service
    systemctl start aos-cloud-manager-worker.service
    

11. Create CloudManager API service:

    openstack service create --name cloud-manager --description "Cloud Manager Service" cloud-manager
    

12. Create endpoints:

    openstack endpoint create --region RegionOne cloud-manager internal http://controller:9362
    openstack endpoint create --region RegionOne cloud-manager admin http://controller:9362
    openstack endpoint create --region RegionOne cloud-manager public http://controller:9362
    

Configuration file¶

Configuration file is presented in ini format and consists of the following sections and parameters:

Possibilities of using the module¶

• Initialization of compute nodes;
• Filling in information about compute nodes;
• PXE image creating;
• Initialization of power control devices;
• Compute node power management;
• Synchronization of compute nodes;
• Monitoring and control of compute nodes;
• Hypervisors reserving management.

Recovery plan¶

Roll back if CloudManager fails to install or update:

1. Compare the versions of the migrations in the file /tmp/rollback/cloud_manager/migrations.txt with the current ones. If there are differences migrate to the previous version. Migration example:

   openstack aos db list -n cloud_manager
   openstack aos db migrate -n cloud_manager --migration 27
   

2. Revert to the previous state of the packages:

   cd /tmp/rollback/cloud_manager
   diff --changed-group-format='%>' --unchanged-group-format='' pip_before.txt pip_after.txt > pip_uninstall.txt
   diff --changed-group-format='%<' --unchanged-group-format='' pip_before.txt pip_after.txt > pip_install.txt
   pip3 uninstall -r pip_uninstall.txt
   pip3 install -r pip_install.txt