<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.emailstyle17
{mso-style-name:emailstyle17;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{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;}
/* List Definitions */
@list l0
{mso-list-id:213468642;
mso-list-type:hybrid;
mso-list-template-ids:-2039417962 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#000000" vlink="#000000">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Kathy,<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">The proposal here is to improve the content creation/contribution process.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Given that if the content is ready/released in github, any OpenStack user architects can still refer to these material for their workload (even before the content
is published/promoted by the Marketing team).<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">We will follow the Docs process and show on docs.openstack.org, but I believe we still need our own git repo for the artifacts?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Or are you suggesting to use the docs git repo such as openstack-manuals [1].<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">Docs has the writing style [2] and diagram guidelines [3], I believe we can follow that.<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">The proposal is to extend the “creation” as well as the “review” to wider community. Once the content is made available/developing on github, anyone from the
community can help with the review.<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">[1]
</span><a href="https://github.com/openstack/openstack-manuals"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://github.com/openstack/openstack-manuals</span></a><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">[2]
</span><a href="http://docs.openstack.org/contributor-guide/writing-style.html"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://docs.openstack.org/contributor-guide/writing-style.html</span></a><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">[3]
</span><a href="http://docs.openstack.org/contributor-guide/diagram-guidelines.html"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://docs.openstack.org/contributor-guide/diagram-guidelines.html</span></a><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Leong.<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Kathy Cacciatore [mailto:kathyc@openstack.org]
<br>
<b>Sent:</b> Friday, December 2, 2016 7:17 AM<br>
<b>To:</b> Sun, Yih Leong <yih.leong.sun@intel.com><br>
<b>Cc:</b> enterprise-wg@lists.openstack.org<br>
<b>Subject:</b> RE: [Enterprise] EWG Workload Reference Architecture - Git Repo<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif">Leong, this is all good, thank you. However, it does not address the back end to get them published and promoted to the intended audience - prospective OpenStack user architects
for their PoCs.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif">I suggested using Docs (docs.openstack.org) as a place to show them on OpenStack.org. And use the Docs process for reviews by community writers. Once they
are complete, I can write up the page needed for openstack.org/software/sample-configs and link to the doc in the respoitory or docs.openstack.org. We'd still need a place to store the Heat templates too. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif">And, the teams developing these should use a consistent design for all graphics. In a little while, we hope to provide a set of images for servers,
disks, network storage, routers, etc., so the team can use them to put together their diagrams. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif">I'm asking to please take this one step further and provide for outside (of the creation team) review of the created docs for language, provide consistent
graphics, and consider placement and promotion options in your plan. Than you.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in;word-wrap: break-word">
<span style="font-family:"Arial",sans-serif">On Thursday, December 1, 2016 11:44pm, "Sun, Yih Leong" <<a href="mailto:yih.leong.sun@intel.com">yih.leong.sun@intel.com</a>> said:<o:p></o:p></span></p>
<div id="SafeStyles1480691378">
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">In the last Enterprise WG meeting, I proposed to move the development of workload reference architecture into OpenStack github and review system/process.<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Most agreed and support this approach. I just want to bring this up to this maillist in case of anyone who missed the last meeting.<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">As most are aware, in the previous Newton cycle, we have published two Workload Reference Architecture (Web Application & Big Data) which are now available at
<a href="https://www.openstack.org/software/sample-configs">https://www.openstack.org/software/sample-configs</a>. (eCommerce is in the final stage of publication).<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">With this, we can:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Create a more scalable process for on-going enhancement/development/creation of existing or new workload reference architecture (e.g. container, media transcoding, enterprise database, PaaS,
etc).<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reach out to wider community and encourage more people to contribute.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Mitigate EWG resources bottleneck on developing workload reference architecture.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Allow parallel development of multiple reference architectures at any release cycle.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">5.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Embrace OpenStack 4 Open principles.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">To achieve this, few things needs to be done:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Create a github repo to host EWG Workload Reference Architecture. (I have submitted the github request)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Develop a common template or format for the content writing. (pending)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Decide a directory structure for hosting each individual workload reference architecture (documents, diagram, sample code such as heat or murano), potentially with multiple "version" or
"release". (pending)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4.</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Form initial team of core-reviewer for this repo to validate/approve content. (pending)<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Let me know if you have any questions.<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">---<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Yih
<strong><u><span style="font-family:"Arial",sans-serif">Leong</span></u></strong> Sun, PhD<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif">Senior Software Cloud Architect | Open Source Technology Center | Intel Corporation<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"><a href="mailto:yih.leong.sun@intel.com"><u><span style="color:#0563C1">yih.leong.sun@intel.com</span></u></a> | +1 503 264 0610<o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal" style="word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in;word-wrap: break-word">
<span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif">--
<br>
Regards, <br>
<br>
Kathy Cacciatore<br>
Consulting Marketing Manager<br>
OpenStack Foundation<br>
1-512-970-2807 (mobile)<br>
Part time: Monday - Thursday, 9am - 2pm US CT<br>
<a href="mailto:kathyc@openstack.org">kathyc@openstack.org</a><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;word-wrap: break-word"><span style="font-family:"Arial",sans-serif"> <o:p></o:p></span></p>
</div>
</body>
</html>