fcc4144692
In the kilo release the nova v2.1 API is tied to the v3 API, so v3 needs to be enabled for v2.1 to be enabled as well. This change adds a setting to control whether the v2.1 API should be enabled or disabled. If v2.1 is enabled then v3 will be enabled as well, but without registering it with the keystone catalog. Change-Id: I1e80189bbcbef1dd712cd6a527b5b59aa939e9e1 Closes-Bug: #1445524
OpenStack nova
- tags
-
openstack, nova, cloud, ansible
- category
-
*nix
Role for deployment, setup and installation of nova.
- This role will install the following:
-
- nova-consoleauth
- nova-conductor
- nova-compute
- nova-cert
- nova-api-metadata
- nova-spicehtml5proxy
- nova-api-ec2
- nova-api-os-compute
- nova-api-ec2
- name: Installation and setup of Nova
hosts: nova_all
user: root
roles:
- { role: "os_nova", tags: [ "os-nova" ] }
vars:
galera_address: "{{ internal_lb_vip_address }}"