<html><body>
<p><font size="2" face="sans-serif">+1 - this is important for both incubated projects and vendor implementations. I seem to recall one of the sessions talking about gating commits to passing an upgrade test from the previous stable release and these interfaces are an obvious candidate. Identifying the specific interfaces will take some work, but the plugin points (e.g. scheduler, rpc, etc) are a good starting point.</font><br>
<font size="2" face="sans-serif"><br>
Michael<br>
<br>
-------------------------------------------------<br>
Michael Fork<br>
Cloud Architect, Emerging Solutions<br>
IBM Systems & Technology Group</font><br>
<br>
<img width="16" height="16" src="cid:1__=0ABBF379DF9D6A028f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Justin Santa Barbara ---04/23/2012 05:43:58 PM---On Mon, Apr 23, 2012 at 12:31 PM, Eric Windisch <eri"><font size="2" color="#424282" face="sans-serif">Justin Santa Barbara ---04/23/2012 05:43:58 PM---On Mon, Apr 23, 2012 at 12:31 PM, Eric Windisch <eric@cloudscaling.com>wrote: > There seemed to be a</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Justin Santa Barbara <justin@fathomdb.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">Eric Windisch <eric@cloudscaling.com>, </font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Cc: </font><font size="1" face="sans-serif">openstack <openstack@lists.launchpad.net></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">04/23/2012 05:43 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [Openstack] Canonical AWSOME</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Sent by: </font><font size="1" face="sans-serif">openstack-bounces+mjfork=us.ibm.com@lists.launchpad.net</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<br>
<font size="3" face="serif">On Mon, Apr 23, 2012 at 12:31 PM, Eric Windisch <</font><a href="mailto:eric@cloudscaling.com"><font size="3" color="#0000FF" face="serif"><u>eric@cloudscaling.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left: 9pt"><font size="1" face="serif">There seemed to be a strong agreement at the summit regarding the need for contracts on those "private" apis. This is because those APIs are no longer really private, they're shared amongst incubated projects. Furthermore, it seems this may be required to support version heterogeneity during upgrades with versioned RPC calls.</font><br>
<br>
<font size="1" face="serif">The incubated projects could use REST APIs, but we're talking of introducing artificial scaling and reliability constraints to do that. It seems far better to me, if we can have contracts on those internal APIs and use them between the incubated projects. There is a strong enough push to maintain these versions *anyway*.</font></ul>
<br>
<font size="3" face="serif">Ah - thanks for explaining that. I'm all for locking down these internal interfaces. I didn't realize people were willing to do so.</font><br>
<tt><font size="2">_______________________________________________<br>
Mailing list: </font></tt><tt><font size="2"><a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></font></tt><tt><font size="2"><br>
Post to : openstack@lists.launchpad.net<br>
Unsubscribe : </font></tt><tt><font size="2"><a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></font></tt><tt><font size="2"><br>
More help : </font></tt><tt><font size="2"><a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</body></html>