f76b9ee74b
Remove all tasks and variables related to toggling between installation of cloudkitty inside or outside of a Python virtual environment. Installing within a venv is now the only supported deployment. Additionally, a few changes have been made to make the creation of the venv more resistant to interruptions during a run of the role. * unarchiving a pre-built venv will now also occur when the venv directory is created, not only after being downloaded * virtualenv-tools is run against both pre-built and non pre-built venvs to account for interruptions during or prior to unarchiving Change-Id: I84dd86e4e8244de5a6ac55a302df0c9737d6388e Implements: blueprint only-install-venvs
OpenStack-Ansible CloudKitty
- tags
-
openstack, cloudkitty, cloud, ansible
- category
-
*nix
This Ansible role installs and configures OpenStack cloudkitty.
- This role will install the following Upstart services:
-
- cloudkitty-api
- cloudkitty-processor
Required Variables
cloudkitty_user_password
cloudkitty_rabbitmq_password
cloudkitty_galera_password
cloudkitty_galera_addressExample Playbook
- name: Install cloudkitty server
hosts: cloudkitty_all
user: root
roles:
- { role: "os_cloudkitty", tags: [ "os-cloudkitty" ] }
vars:
external_lb_vip_address: 172.16.24.1
internal_lb_vip_address: 192.168.0.1
cloudkitty_galera_address: "{{ internal_lb_vip_address }}"
cloudkitty_container_mysql_password: "SuperSecretePassword1"
cloudkitty_service_password: "SuperSecretePassword2"
cloudkitty_rabbitmq_password: "SuperSecretePassword3"