Comment 9 for bug 1470635

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/202242
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=117db2be5d26063bd21fc62170e183a7473b30c3
Submitter: Jenkins
Branch: kilo

commit 117db2be5d26063bd21fc62170e183a7473b30c3
Author: Ian Cordasco <email address hidden>
Date: Mon Jun 29 23:23:08 2015 -0500

    Upgrade the Keystone library to use v3

    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
    (cherry picked from commit c1fdbab4de2dc69790eb95f6ad9ce9515b8ce9fa)