<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Joe,</div>
<div><br>
</div>
<div>Thanks for the notes.</div>
<div><br>
</div>
<div>We had a productive discussion with the Glance folk on how to share images across clouds (<a href="https://libertydesignsummit.sched.org/event/6b4a5dbd177cde2aad7a9927a82534d0#.VWDLPpOqqko">https://libertydesignsummit.sched.org/event/6b4a5dbd177cde2aad7a9927a82534d0#.VWDLPpOqqko</a>)
and we’ll be working on that spec.</div>
<div><br>
</div>
<div>We also had some forward looking discussions with the Keystone team on how to manage multi-cloud nested projects. </div>
<div><br>
</div>
<div>As joe said, Federated identity is needed but giving users a transparent exprience will take much, much more. </div>
<div><br>
</div>
<div>Are there blueprints created for this gap ?</div>
<div><br>
</div>
<div>Tim</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>joe <<a href="mailto:joe@topjian.net">joe@topjian.net</a>><br>
<span style="font-weight:bold">Date: </span>Friday 22 May 2015 23:26<br>
<span style="font-weight:bold">To: </span>openstack-operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Openstack-operators] Ops Keystone / Federation Session<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hello,
<div><br>
</div>
<div>Better late than never, here's a summary of the Ops Keystone / Federation Session from this past Tuesday:</div>
<div><br>
</div>
<div>First, I want to thank everyone from the Keystone team for attending the session -- it was very cool to have you guys on-hand to directly answer questions and give input and insight into the various items being discussed.</div>
<div><br>
</div>
<div>This was the first time we had a discussion session dedicated to this topic and we could have easily spent entire sessions on each of the main items listed in the
<a href="https://etherpad.openstack.org/p/YVR-ops-federation">Etherpad</a>. I think that shows there's a lot to be discussed with regard to federated clouds.</div>
<div><br>
</div>
<div>The biggest discussion item to come out of the session was that a federated cloud means so much more than just "Keystone". Allocating, restricting, automatic provisioning, reporting, and cleanup of any type of OpenStack-enabled resource in a federated
cloud are all areas Operators are interested in learning about, but those areas are either not well defined (perhaps because what works for one federation won't work for another), are not possible to do yet, or are possible but Operators aren't sure how to
implement them.</div>
<div><br>
</div>
<div>I encourage operators who are interested in this area to keep the discussion going on this list by sharing your questions, concerns, and trials. As well, I hope to see this topic in future Ops meetups and tracks as a more formal way to touch base on this
area.</div>
<div><br>
</div>
<div>Etherpad: <a href="https://etherpad.openstack.org/p/YVR-ops-federation">https://etherpad.openstack.org/p/YVR-ops-federation</a></div>
<div><br>
</div>
<div>Thanks,</div>
<div>Joe</div>
</div>
</div>
</div>
</span>
</body>
</html>