<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I completely agree with Salvatore about the support in both formats. They both must have the same consideration from our side.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So, is there any rush on having XML support for Folsom? I would say NO. I think we should carefully review what we are supporting for Folsom because it’s going
to be our “debut” as core project and the last thing that we want is a service that offers a lot of features but with bugs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Just my .02<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Edgar
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<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""> Salvatore Orlando [mailto:sorlando@nicira.com]
<br>
<b>Sent:</b> Thursday, August 16, 2012 9:29 AM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> [openstack-dev] [Quantum] About XML support in Quantum v2 API<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the last Quantum Meeting on IRC [1], it was decided to finalize a decision on XML support for Quantum during this week.<o:p></o:p></p>
<div>
<p class="MsoNormal">There is already a patch from Andrews Medina [2] that addresses XML support (probably not yet thoroughly).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would like to use this email thread to continue the discussion, and possibly finalize a decision before the end of this week, so that we can ask for a FFE if needed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">You can read the meeting logs and previous email threads concerning XML support in Openstack projects.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As you might already know, this is the first version of Quantum with a truly publicly accessible API.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The Quantum v2 API that we are releasing for Folsom [3], comes from a merge between the v1 Quantum API and the Melange API. The API currently support json only.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Here's something we might want to consider before deciding on XML support<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- There should be no "preferred" format. If we decide to support XML as well, it must receive the same attention as JSON, in terms of i) development, ii) testing, and iii) documentation. For instance, JSON-only capabilities will be totally
unacceptable; a documentation with JSON-only examples would look bad too.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- Once the API is released backward compatibility must be ensured for every format supported.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- Adding support for more format during the v2 lifecycle should be acceptable; Dropping support for a specific format during the v2 API lifecycle would be very very bad.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Salvatore<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-13-21.00.log.html">http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-13-21.00.log.html</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">[2] <a href="https://review.openstack.org/#/c/10856/">https://review.openstack.org/#/c/10856/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[3] <a href="http://wiki.openstack.org/Quantum/APIv2-specification">http://wiki.openstack.org/Quantum/APIv2-specification</a><o:p></o:p></p>
</div>
</div>
</body>
</html>