Switch to v2.1 API (charm deploys with old 2.0 API)

Bug #1794271 reported by James Page
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Fix Released
High
James Page

Bug Description

The nova-cloud-controller currently registers keystone endpoints using the v2.0 API; v2.1 is the current supported version so we need to switch the charm over to ensure compliance with tempest/refstack testing.

Revision history for this message
Nobuto Murata (nobuto) wrote :
James Page (james-page)
Changed in charm-nova-cloud-controller:
status: New → Triaged
importance: Undecided → High
assignee: nobody → James Page (james-page)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-cloud-controller (master)

Reviewed: https://review.openstack.org/605030
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=935d30571c7e813ccbfecb9cbbf980f7f2835b08
Submitter: Zuul
Branch: master

commit 935d30571c7e813ccbfecb9cbbf980f7f2835b08
Author: James Page <email address hidden>
Date: Tue Sep 25 11:08:23 2018 +0100

    Use v2.1 API for >= Queens

    Switch to using the v2.1 API endpoint for OpenStack Queens or later.

    Closes-Bug: 1794271

    Change-Id: Ia21b3a6782ab944b7c41564e889e6b12d264b731

Changed in charm-nova-cloud-controller:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-nova-cloud-controller (stable/18.08)

Fix proposed to branch: stable/18.08
Review: https://review.openstack.org/606914

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-cloud-controller (stable/18.08)

Reviewed: https://review.openstack.org/606914
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=76a0bf5acfeeefab4e8211fa653e571abf8c70a7
Submitter: Zuul
Branch: stable/18.08

commit 76a0bf5acfeeefab4e8211fa653e571abf8c70a7
Author: James Page <email address hidden>
Date: Tue Sep 25 11:08:23 2018 +0100

    Use v2.1 API for >= Queens

    Switch to using the v2.1 API endpoint for OpenStack Queens or later.

    Closes-Bug: 1794271

    Change-Id: Ia21b3a6782ab944b7c41564e889e6b12d264b731
    (cherry picked from commit 935d30571c7e813ccbfecb9cbbf980f7f2835b08)

David Ames (thedac)
Changed in charm-nova-cloud-controller:
milestone: none → 19.04
Revision history for this message
Felipe Reyes (freyes) wrote :

Hi James, is there any reason to set v2.1 only for >= Queens?, this exists since at least Mitaka.

The problem I'm chasing now is that "nova server-migration-list" exists in Mitaka, but it's only available when querying the v2.1 endpoint.

Revision history for this message
Drew Freiberger (afreiberger) wrote :

I recently ran across the need to access the v2.1 endpoint and did the following to workaround. If we could at least provide a forward-compatible endpoint like this, I think it would be a good start.

openstack endpoint create --region RegionOne --enable computev21 public 'https://nova.mycloud.foo:8774/v2.1/$(tenant_id)s'

I can then use this nova endpoint with my client specifying the arg '--service-type=computev21'.

I believe that we used to have computev3, but that got dropped as the API was deprecated.

This interface is required to support things such as nova live-migration-abort.

tags: added: canonical-bootstack
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Note: I forgot to mention, you have to register another service to have the additional endpoint for nova as mentioned in comment #6.

openstack service create computev21 --name novav21

David Ames (thedac)
Changed in charm-nova-cloud-controller:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.