<HTML>
<HEAD>
<TITLE>Re: [Openstack] Canonical AWSOME</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>So if what u are talking about is anything RPC/MQ based, then I would say those are not internal API’s.<BR>
<BR>
Once a RPC/MQ mechanism is introduced they don’t really become internal API’s anymore (if we are talking about the same API’s, haha).<BR>
<BR>
Since other stuff can be reading those messages on the MQ its very useful to have a schema to know exactly what to read :-)<BR>
<BR>
On 4/24/12 11:46 AM, "Russell Bryant" <<a href="rbryant@redhat.com">rbryant@redhat.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>On 04/24/2012 01:25 PM, Joshua Harlow wrote:<BR>
> I’m more in favor of just having a schema, I don’t care if that compiles<BR>
> to protocol buffers, json, NEWAWESOMEhipsterMSGFORMAT.<BR>
><BR>
> That schema will force people to think a little more when they add<BR>
> messages, and it will automatically document the messages that are being<BR>
> sent around.<BR>
><BR>
> That’s a big win I think and is a step to getting those schemas<BR>
> versioned...<BR>
<BR>
I'm not sure a schema is really necessary aside from the Python classes<BR>
themselves. They're internal APIs, so they shouldn't be used from<BR>
outside of Nova. A schema would be useful if we had to define the<BR>
interfaces in some language neutral-format, but I don't think that<BR>
really matters here.<BR>
<BR>
I'm going to work on a proposal / prototype for how we can handle<BR>
versioning, though. The big goal here is making sure that we can<BR>
maintain compatibility with the previous release.<BR>
<BR>
--<BR>
Russell Bryant<BR>
<BR>
_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>