openstack team mailing list archive

[Dolph Mathews <dolph.mathews@xxxxxxxxx>]

I didn't realize this was off-list. The discussion here is certainly
applicable to the broader community.

-Dolph


---------- Forwarded message ----------
From: Miller, Mark M (EB SW Cloud - R&D - Corvallis) <mark.m.miller@xxxxxx>
Date: Fri, Apr 12, 2013 at 2:01 PM
Subject: RE: Keystone Ugly
To: "Yee, Guang" <guang.yee@xxxxxx>, Dolph Mathews <dolph.mathews@xxxxxxxxx>
Cc: "Brownell, Jonathan C (Corvallis)" <brownell@xxxxxx>


 You might be thinking why we just don’t switch over to using v3 and be
done with the inconsistencies. Bottom line, we are migrating our services
over but we don’t have time to change all of them before our next release
and thus the problem. I am really glad that the latest Keystone release is
backwards compatible with v2.0.****

** **

Mark****

** **

*From:* Yee, Guang
*Sent:* Friday, April 12, 2013 11:47 AM
*To:* Dolph Mathews; Miller, Mark M (EB SW Cloud - R&D - Corvallis)
*Cc:* Brownell, Jonathan C (Corvallis)
*Subject:* RE: Keystone Ugly****

** **

Sounds reasonable. But what about the standard interfaces like ‘admin’ and
‘public’, should those be interchangeably?****

** **

** **

Guang****

** **

** **

*From:* Dolph Mathews [mailto:dolph.mathews@xxxxxxxxx]
*Sent:* Friday, April 12, 2013 11:42 AM
*To:* Miller, Mark M (EB SW Cloud - R&D - Corvallis)
*Cc:* Yee, Guang; Brownell, Jonathan C (Corvallis)
*Subject:* Re: Keystone Ugly****

** **

Correct- v3 endpoints represent a slightly different concept than v2
endpoints (which are really a set of 3 static urls), so endpoints created
on v3 are explicitly excluded from v2.0. With v3, you could create a fourth
interface type (say, local) or, down the road, a domain-specific endpoint,
neither of which would make any sense on v2.0.****


****

** **

-Dolph****

** **

On Fri, Apr 12, 2013 at 1:28 PM, Miller, Mark M (EB SW Cloud - R&D -
Corvallis) <mark.m.miller@xxxxxx> wrote:****

Hi,****

 ****

I have a Keystone Grizzly server up and just noticed that after adding
endpoints with the v3 APIs, you cannot read them back with the v2.0 APIs.***
*

 ****

 ****

POST Enpoints                   GET Endpoints                 Result****

-------------------                --------------------
--------------****

V3
v3                           Pass****

V3
v2.0                        Fails (does not return them)****

V2.0                                                       v3
                Pass****

V2.0
v2.0                        Pass****

 ****

Mark****

 ****

****

** **