<HTML>
<HEAD>
<TITLE>Re: [Openstack] EC2 compat.</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Sweet,<BR>
<BR>
Ideas and thoughts are welcome.<BR>
<BR>
There is a lot of cleanup/testing/validation that needs to happen, but someones got to do it :-P<BR>
<BR>
On 4/11/12 8:06 AM, "Duncan McGreggor" <<a href="duncan@dreamhost.com">duncan@dreamhost.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Lurking on the thread, but love what I'm seeing :-)<BR>
<BR>
Nice work, guys!<BR>
<BR>
d<BR>
<BR>
On Tue, Apr 10, 2012 at 10:43 PM, Joshua Harlow <<a href="harlowja@yahoo-inc.com">harlowja@yahoo-inc.com</a>> wrote:<BR>
> Very cool, glad to see that is being worked on, it looks pretty similar to<BR>
> what I was thinking of.<BR>
> I’m all for open dialogues.<BR>
> In fact.<BR>
> I was thinking of what is needed to make this work better.<BR>
><BR>
> Open questions/thoughts/brainstorm (at least that I was thinking of):<BR>
><BR>
> How strict do we want to be with the XSD? (there aren’t a lot of tolerant<BR>
> xsd validators out there, which sux)<BR>
><BR>
> Should we use something like jaxb for python, that should be more tolerant<BR>
> (unsure as what the best solution here is)<BR>
><BR>
> How do we continuously measure the compatibility level?<BR>
><BR>
> # of test cases passing, # of xml differences, # of xsd issues<BR>
><BR>
> Should we use boto as a intermediate layer? (it is very tolerant)<BR>
><BR>
> From what I understand there XML code is basically selecting certain<BR>
> attributes out of the XML using SAX, then adding any unknown attributes<BR>
> dynamically on to a object<BR>
><BR>
> How do we make it repeatable?<BR>
><BR>
> For a given test X, if there is a problem with test X and its response Y,<BR>
> how do we easily recreate that test X and response Y (so that dev’s can fix<BR>
> it)?<BR>
> Do we have a “golden set” of responses that when test X is called it should<BR>
> match golden response Z (otherwise there is an issue)<BR>
><BR>
> This is where the mock server maybe useful, in that we can point test X at<BR>
> the mock server; get the expected responses Z,<BR>
> Then point the test X at the real openstack server and get responses Y that<BR>
> should match Z (exactly, minus the request id?)<BR>
> EC2 seems to also already have some type of mocking, but I haven’t used<BR>
> it... (<a href="http://bit.ly/HJkdh7">http://bit.ly/HJkdh7</a>)<BR>
><BR>
><BR>
> I like how there is a tests folder that u guys have, that seems like it<BR>
> could be a good location for the “content checking tests” which actually<BR>
> require code/logic to dig into the XML response. It might make sense to use<BR>
> another tool to verify the XSD’s (how tolerant we want to be is an open<BR>
> question) and another tool that will show u the xml differences (some of<BR>
> which might be ok, some not). I have used in java xmlunit to do those kind<BR>
> of xml difference comparisons, it provides some nifty ways of ignoring<BR>
> certain differences and such. If say we had 3 levels of tests I think that<BR>
> would make sense (starting say from XSD validation, to difference<BR>
> comparisons to content comparisons), and would make a hell of a EC2 cool<BR>
> validation toolkit.<BR>
><BR>
> The other usage of the site I was making was to list all the known error<BR>
> conditions, and any other incompatibilities that I am noticing with EC2<BR>
> (error conditions, features, parameters...). That seems really needed to<BR>
> allow for anyone to actually use the EC2 apis and handle all the cases which<BR>
> could be thrown at them.<BR>
><BR>
> -Josh<BR>
><BR>
><BR>
><BR>
><BR>
> On 4/10/12 7:02 PM, "Eric Windisch" <<a href="eric@cloudscaling.com">eric@cloudscaling.com</a>> wrote:<BR>
><BR>
><BR>
> Josh, as a follow-up, it would be good to keep an open dialogue on this.<BR>
> When/if you get a chance to review the aws-compat branch, I'd like to get<BR>
> your feedback as well.<BR>
><BR>
> PS I meant to write "assess", not "access". I only noticed when I read back<BR>
> my email. I'm too pedantic to not correct myself.<BR>
><BR>
><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>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>