<div dir="ltr">I didn't realize this was off-list. The discussion here is certainly applicable to the broader community.<br clear="all"><div><div><br></div>-Dolph</div>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Miller, Mark M (EB SW Cloud - R&D - Corvallis)</b> <span dir="ltr"><<a href="mailto:mark.m.miller@hp.com">mark.m.miller@hp.com</a>></span><br>
Date: Fri, Apr 12, 2013 at 2:01 PM<br>Subject: RE: Keystone Ugly<br>To: "Yee, Guang" <<a href="mailto:guang.yee@hp.com">guang.yee@hp.com</a>>, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>><br>
Cc: "Brownell, Jonathan C (Corvallis)" <<a href="mailto:brownell@hp.com">brownell@hp.com</a>><br><br><br>
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Yee, Guang
<br>
<b>Sent:</b> Friday, April 12, 2013 11:47 AM<br>
<b>To:</b> Dolph Mathews; Miller, Mark M (EB SW Cloud - R&D - Corvallis)<br>
<b>Cc:</b> Brownell, Jonathan C (Corvallis)<br>
<b>Subject:</b> RE: Keystone Ugly<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Sounds reasonable. But what about the standard interfaces like ‘admin’ and ‘public’, should those be interchangeably?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Guang<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Dolph Mathews [mailto:<a href="mailto:dolph.mathews@gmail.com" target="_blank">dolph.mathews@gmail.com</a>]
<br>
<b>Sent:</b> Friday, April 12, 2013 11:42 AM<br>
<b>To:</b> Miller, Mark M (EB SW Cloud - R&D - Corvallis)<br>
<b>Cc:</b> Yee, Guang; Brownell, Jonathan C (Corvallis)<br>
<b>Subject:</b> Re: Keystone Ugly<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-Dolph<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Fri, Apr 12, 2013 at 1:28 PM, Miller, Mark M (EB SW Cloud - R&D - Corvallis) <<a href="mailto:mark.m.miller@hp.com" target="_blank">mark.m.miller@hp.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">POST Enpoints GET Endpoints Result<u></u><u></u></p>
<p class="MsoNormal">------------------- -------------------- --------------<u></u><u></u></p>
<p class="MsoNormal">V3 v3 Pass<u></u><u></u></p>
<p class="MsoNormal">V3 v2.0
<span style="background:yellow">Fails</span> (does not return them)<u></u><u></u></p>
<p class="MsoNormal">V2.0 v3 Pass<u></u><u></u></p>
<p class="MsoNormal">V2.0 v2.0 Pass<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Mark<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><img border="0" width="1880" height="720" src="cid:image001.png@01CE3775.76795ED0"><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</div><br></div>