<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 4:25 PM, Jamie Lennox <span dir="ltr"><<a href="mailto:jamielennox@redhat.com" target="_blank">jamielennox@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">To most of your questions i don't know the answer as the format was in place before i started with the project. I know that it is similar (though not exactly the same) as nova's but not where they are documented (as they are version independent)<br>
<br>
I can tell you it looks like:<br>
<br>
{<br>
"versions": {<br>
"values": [<br>
{<br>
"status": "stable",<br>
"updated": "2013-03-06T00:00:00Z",<br>
"media-types": [<br>
{<br>
"base": "application\/json",<br>
"type": "application\/vnd.openstack.identity-v3+json"<br>
},<br>
{<br>
"base": "application\/xml",<br>
"type": "application\/vnd.openstack.identity-v3+xml"<br>
}<br>
],<br>
"id": "v3.0",<br>
"links": [<br>
{<br>
"href": "http:\/\/localhost:5000\/v3\/",<br>
"rel": "self"<br>
}<br>
]<br>
},<br>
{<br>
"status": "stable",<br>
"updated": "2013-03-06T00:00:00Z",<br>
"media-types": [<br>
{<br>
"base": "application\/json",<br>
"type": "application\/vnd.openstack.identity-v2.0+json"<br>
},<br>
{<br>
"base": "application\/xml",<br>
"type": "application\/vnd.openstack.identity-v2.0+xml"<br>
}<br>
],<br>
"id": "v2.0",<br>
"links": [<br>
{<br>
"href": "http:\/\/localhost:5000\/v2.0\/",<br>
"rel": "self"<br>
},<br>
{<br>
"href": "http:\/\/<a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a>\/api\/openstack-identity-service\/2.0\/content\/",<br>
"type": "text\/html",<br>
"rel": "describedby"<br>
},<br>
{<br>
"href": "http:\/\/<a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a>\/api\/openstack-identity-service\/2.0\/identity-dev-guide-2.0.pdf",<br>
"type": "application\/pdf",<br>
"rel": "describedby"<br>
}<br>
]<br>
}<br>
]<br>
<div><div class="h5"> }<br>
}<br></div></div></blockquote><div><br></div><div>The above is keystone's unversioned multiple choice response. I just wrote docs for v3's existing version description response, which is closely based on the above:</div>
<div><br></div><div> <a href="https://review.openstack.org/#/c/60576/">https://review.openstack.org/#/c/60576/</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><div class="h5">
<br>
----- Original Message -----<br>
> From: "Flavio Percoco" <<a href="mailto:flavio@redhat.com">flavio@redhat.com</a>><br>
> To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Sent: Monday, 25 November, 2013 6:41:42 PM<br>
> Subject: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance]<br>
> Support of v1 and v2 glance APIs in Nova)<br>
><br>
> On 25/11/13 09:28 +1000, Jamie Lennox wrote:<br>
> >So the way we have this in keystone at least is that querying GET / will<br>
> >return all available API versions and querying /v2.0 for example is a<br>
> >similar result with just the v2 endpoint. So you can hard pin a version<br>
> >by using the versioned URL.<br>
> ><br>
> >I spoke to somebody the other day about the discovery process in<br>
> >services. The long term goal should be that the service catalog contains<br>
> >unversioned endpoints and that all clients should do discovery. For<br>
> >keystone the review has been underway for a while now:<br>
> ><a href="https://review.openstack.org/#/c/38414/" target="_blank">https://review.openstack.org/#/c/38414/</a> the basics of this should be<br>
> >able to be moved into OSLO for other projects if required.<br>
><br>
> Did you guys create your own 'home document' language? or did you base<br>
> it on some existing format? Is it documented somewhere? IIRC, there's<br>
> a thread where part of this was discussed, it was related to horizon.<br>
><br>
> I'm curious to know what you guys did and if you knew about<br>
> JSON-Home[0] when you started working on this.<br>
><br>
> We used json-home for Marconi v1 and we'd want the client to work in a<br>
> 'follow your nose' way. Since, I'd prefer OpenStack modules to use the<br>
> same language for this, I'm curious to know why - if so - you<br>
> created your own spec, what are the benefits and if it's documented<br>
> somewhere.<br>
><br>
> Cheers,<br>
> FF<br>
><br>
> [0] <a href="http://tools.ietf.org/html/draft-nottingham-json-home-02" target="_blank">http://tools.ietf.org/html/draft-nottingham-json-home-02</a><br>
><br>
> --<br>
> @flaper87<br>
> Flavio Percoco<br>
><br>
</div></div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div>-Dolph
</div></div>