novarc provides link to the specific version of OS API

Bug #776679 reported by Eldar Nugaev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Undecided
Eldar Nugaev

Bug Description

novarc provides link to the specific version OS API.

But without version of API nova provides xml like this with information about available API and addresses.
I suppose we shouldn't define specific version of api and give user link to url without predefined version.

<versions>
<version id="v1.1" status="CURRENT">
<links>
<link href="http://10.0.0.1:8774/v1.1" rel="self"/>
</links>
</version>
<version id="v1.0" status="DEPRECATED">
<links>
<link href="http://10.0.0.1:8774/v1.0" rel="self"/>
</links>
</version>
</versions>

Related branches

Eldar Nugaev (reldan)
Changed in nova:
assignee: nobody → Eldar Nugaev (reldan)
status: New → In Progress
Revision history for this message
Thierry Carrez (ttx) wrote :

From Devin on the merge prop:
"I don't see the need for this. If a client requires a specific version of an API, then it should manage that itself. I also don't see the need for an additional parameter. Can you explain your use case?"

Changed in nova:
status: In Progress → Incomplete
Revision history for this message
Eldar Nugaev (reldan) wrote :

Hi Thierry.

I suppose we can't just drop this bug.
Nova gives response that v1.0 is DEPRECATED.
So I see inconsistency. I need link to information about versions and their status. At this time I have to get link to DEPRECATED (As we can see in nova) version, remova path from the link and change to CURRENT state.

version_objs = [
            {
                "id": "v1.1",
                "status": "CURRENT",
            },
            {
                "id": "v1.0",
                "status": "DEPRECATED",
            },
        ]

Revision history for this message
Brian Waldon (bcwaldon) wrote :

In response to the CURRENT/DEPRECATED comment:

v1.0 was set to deprecated earlier in the cactus dev cycle when the expectation was to still have full v1.1 support. I suppose now we should change the status of v1.0 to current and v1.1 to EXPERIMENTAL, or BETA.

Revision history for this message
Eldar Nugaev (reldan) wrote :

Absolutely agree with Brain.

But if we have the feature to provide information about versions of API, why we should not provide the link to this information?
Yes, there are no complexity to get link, then delete path, then get information about allowed API's, then chose the needed on.
But I suppose it hack.

Revision history for this message
Eldar Nugaev (reldan) wrote :

 Brian sorry for typo :(

Revision history for this message
Thierry Carrez (ttx) wrote :

If you change the NOVA_URL in novarc, it will break the nova cmdline (which relies on a fully defined NOVA_URL)...

Revision history for this message
Thierry Carrez (ttx) wrote :

Closing as WontFix since this is probably a bad idea. Feel free to reopen if you want to continue discussion on this.

Changed in nova:
status: Incomplete → Won't Fix
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.