<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi everyone,<br>
</p>
<p>Just an update on the draft Architecture Design Guide. <br>
</p>
<p>For Ocata, we reorganized some migrated content from the current
Arch Guide and Ops Guide, and updated the compute and networking
sections in the Design chapter. It is currently published at
<a class="moz-txt-link-freetext" href="http://docs.openstack.org/draft/arch-design-draft/">http://docs.openstack.org/draft/arch-design-draft/</a>.
<br>
<br>
As discussed at the PTG (1), our plan for Pike:<br>
</p>
<ol>
<li>Writing the Design chapter is the highest priority. The goal
to complete the networking and storage sections first, then work
on the remaining sections and chapters.</li>
<li>Create a bug report for each task, describing what information
should be covered to complete the task.</li>
<li>Develop a use case template which will be applied to all
architecture use cases in the guide. <br>
</li>
<li>Remove the architecture content from the Ops Guide since it
has been migrated and integrated into the draft Arch Guide.</li>
<li>Remove the current Arch Guide and publish the draft Arch Guide
to docs.openstack.org. </li>
</ol>
<p>Our plans are also documented in the spec:
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/436747/">https://review.openstack.org/#/c/436747/</a>. I would really
appreciate some reviews and comments.<br>
</p>
<p>Overhauling the guide has been ongoing for a few release cycles
due to lack of contributors. We would like to make good progress
for Pike, so if you are interested in getting involved, please
reach out to me or Ben Silverman.</p>
<p>Thanks!</p>
<p>Darren<br>
</p>
<p> (1) <a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/docs-i18n-ptg-pike">https://etherpad.openstack.org/p/docs-i18n-ptg-pike</a><br>
<br>
</p>
</body>
</html>