murano is registerd in keystone without API version

Bug #1476716 reported by noa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Invalid
High
Unassigned

Bug Description

when murano registers to keystone the endpoint should be "http://135.248.18.124:8082/v1" instead of
"http://135.248.18.124:8082".

this will make it compatible with the other services.
this means a change to the python-client will also be necessary in order to remove the hardcoded version from the urls.

Changed in murano:
status: New → Confirmed
importance: Undecided → High
milestone: none → liberty-3
Changed in murano:
assignee: nobody → Nikolay Starodubtsev (starodubcevna)
Changed in murano:
status: Confirmed → Invalid
Revision history for this message
noa (noa-koffman) wrote :

Hi,
can you please comment why you say this bug is invalid?
thanks

Revision history for this message
Nikolay Starodubtsev (starodubcevna) wrote :

Hi all,
I mark this bug as invalid because OpenStack projects is on their way to skip versioning in keystone-catalog. here is the link: https://wiki.openstack.org/wiki/VersionDiscovery

Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

Thanks Nikolay, does look invalid. =) Do we need to add an additional bug, to accommodate VersionDiscovery then?

Revision history for this message
Nikolay Starodubtsev (starodubcevna) wrote :

Kirill, I think that we should make a bp for it. and marked it as 'future' as soon as we don't have many API versions right now. But it's only IMHO.

Changed in murano:
assignee: Nikolay Starodubtsev (starodubcevna) → nobody
Revision history for this message
Serg Melikyan (smelikyan) wrote :

We need to investigate this bug more and dive to our way working with versions deeper

Changed in murano:
status: Invalid → Won't Fix
status: Won't Fix → New
milestone: liberty-3 → next
Revision history for this message
Nikolay Starodubtsev (starodubcevna) wrote :

Serg, we need a bp about versions. It wasn't something what we looking at before, but the reason I marked it as invalid that OpenStack project skips version in catalog.

Changed in murano:
milestone: next → liberty-rc1
Changed in murano:
status: New → Triaged
Changed in murano:
assignee: nobody → Kirill Zaitsev (kzaitsev)
Changed in murano:
status: Triaged → Confirmed
Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

This is not a bug. It is up to the service to include or not include version information into the endpoint url itself. Openstack services do both (some include, some don't)

Examples of OS services, that do not include version info in it's endpoints are: Neutron, Glance, Ceilometer (and Murano). For those services client is responsible for choosing a version, but a single endpoint might be capable of serving multiple API versions.

Examples of OS services, that include version info in their endpoints are: Heat, Nova, Keystone. For those services clients do not concatenate the version with the path, but rather just take the endpoint as is. Therefore 1 endpoint is capable of serving only 1 version of API

Murano choses the former option, to be able to allow serving several API version from a single endpoint.
Furthermore this means, that Murano's approach is indeed compatible with other OS services (though it is obviously impossible to be compatible with all of them, since there is no single approach among OS services.)

Thus I'm closing the bug as invalid

Changed in murano:
status: Confirmed → Invalid
Changed in murano:
assignee: Kirill Zaitsev (kzaitsev) → nobody
Revision history for this message
Robert Duncan (rduncan-t) wrote :

Murano seems to use a hardcoded keystone auth url - at least as deployed by Fuel. it should use the http 300 on the unversioned keystone endpoint. murano only supports keystone version 2

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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