8e96db0739
In order to enable and deploy federated Keystone, we need to use version 3 of the Keystone API and the v3 Keystone Client. This work begins that transition by having a set of backwards compatible library commands. Specifically, this commit updates the keystone library to use v3 Keystone Client and the usage of ensure_tenant in the os_keystone tasks to use the v3 admin url. In version 3 of Keystone's Endpoints (Catalog) API each endpoint only has one URL and has separate interface types (public, internal, admin). This change updates all uses of ensure_endpoint to structure the endpoint data in a better way for the ensure_endpoint command in the keystone module. As a result, some incidents where internalurl and adminurl were swapped have been fixed. Note: In new deployments the endpoints will be created using the v3 API and will therefore not be available via the v2 API. This will be a breaking change to legacy CLI clients. The openstack CLI should be used instead. DocImpact Related-Bug: #1470635 Partially-implements: blueprint keystone-federation Change-Id: I2cd4f505e850b4b113452abc25ee00d486b1637d
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:
nova_galera_address: "{{ internal_lb_vip_address }}"