<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* 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;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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">Thank you, Sheryl!<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">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Rhonda<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<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"> Sheryl Sick [mailto:sheryls@redapt.com]
<br>
<b>Sent:</b> Tuesday, April 05, 2016 2:51 PM<br>
<b>To:</b> Rochelle Grober <rochelle.grober@huawei.com>; Gema Gomez <gema@ggomez.me>; women-of-openstack@lists.openstack.org; Rhonda Eldridge <reldridge@technicacorp.com><br>
<b>Subject:</b> Re: [Women-of-openstack] Technica Inquiries on the List<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hello ladies and looking forward to meeting everyone in a few weeks! <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Redapt has deployed several RA variations of OpenStack. We have worked pretty closely with Mirantis on multiple projects. I can send over details of an RA later this afternoon. <o:p></o:p></p>
<div>
<p class="MsoNormal">Sheryl Sick | SAE Technology Solutions<br>
Redapt, Inc. <a href="tel:206.218.6690">206.218.6690</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">On Tue, Apr 5, 2016 at 11:26 AM -0700, "Rhonda Eldridge" <<a href="mailto:reldridge@technicacorp.com" target="_blank">reldridge@technicacorp.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">Thank you, all! I commit to putting the question out on the other forums and I just found another tool from Mirantis. Has anyone used it? Do you agree with the recommendations or results?<br>
<br>
<a href="https://docs.mirantis.com/openstack/fuel/fuel-8.0/pdf/Mirantis-OpenStack-8.0-PlanningGuide.pdf">https://docs.mirantis.com/openstack/fuel/fuel-8.0/pdf/Mirantis-OpenStack-8.0-PlanningGuide.pdf</a><br>
<br>
<a href="https://www.mirantis.com/blog/hardware-bom-calculator-controllers-switches-bells-and-whistles/">https://www.mirantis.com/blog/hardware-bom-calculator-controllers-switches-bells-and-whistles/</a><br>
<br>
<a href="https://software.mirantis.com/reference-documentation-on-fuel-folsom-2-1/sizing-hardware/">https://software.mirantis.com/reference-documentation-on-fuel-folsom-2-1/sizing-hardware/</a><br>
<br>
<br>
<br>
Looking forward to meeting some of you in Austin,<br>
Rhonda<br>
<br>
<br>
-----Original Message-----<br>
From: Rochelle Grober [<a href="mailto:rochelle.grober@huawei.com">mailto:rochelle.grober@huawei.com</a>]
<br>
Sent: Tuesday, April 05, 2016 2:05 PM<br>
To: Gema Gomez <<a href="mailto:gema@ggomez.me">gema@ggomez.me</a>>; <a href="mailto:women-of-openstack@lists.openstack.org">
women-of-openstack@lists.openstack.org</a><br>
Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
<br>
Great advice, Gema and Amy.<br>
<br>
Three node is definitely the smallest size anyone should consider for a working setup as opposed to test/R&D. I've been trying to get "reference architecture" for a three node and a five node HA cloud, as this is tribal knowledge within the Ops community,
but getting it defined and documented has not really gone anywhere. Maybe we can get this going through a collaboration with this group, Ops and somd specific Docs folks.<br>
<br>
--Rocky<br>
<br>
-----Original Message-----<br>
From: Gema Gomez [<a href="mailto:gema@ggomez.me">mailto:gema@ggomez.me</a>]<br>
Sent: Tuesday, April 05, 2016 10:58 AM<br>
To: <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</a><br>
Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
<br>
I totally agree with Amy.<br>
<br>
It very much depends on how chunky your single node is compared to the amount of resources your VMs are going to require. Decide what kind of flavors you are going to use (i.e. how much memory, CPU and HD you will need per VM) and then do the math to see how
many of those you can fit on your node. It all depends very much on your workload. If you are going to have many small VMs, you'll be able to get more out of your HW than if you have one big VM eating all the resources.<br>
<br>
Also, simple maintenance tasks like upgrading packages/kernel will cause a disruption to your service.<br>
<br>
I wouldn't go to production with less than 3 nodes for a small and cozy cloud.<br>
<br>
Cheers,<br>
Gema<br>
<br>
On 05/04/16 18:47, Amy Marrich wrote:<br>
> Rhonda,<br>
><br>
> Well main disadvantage would be single point of failure, we do <br>
> something very similar with the OpenStack-Ansible project's AIO <br>
> installs but those are generally fro PoC and development. My guess <br>
> from experience is compute and network will grow before storage but it <br>
> depends on your use case.<br>
><br>
> I think you'd get the best response probably over in the #openstack <br>
> channel on freenode, lots of folks over there to answer questions.<br>
><br>
> Amy<br>
><br>
> From: Rhonda Eldridge <<a href="mailto:reldridge@technicacorp.com%20%0b">reldridge@technicacorp.com
<br>
</a>> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> Date: Tuesday, April 5, 2016 at 12:36 PM<br>
> To: Amy Marrich <<a href="mailto:amy.marrich@rackspace.com%20%0b">amy.marrich@rackspace.com
<br>
</a>> <<a href="mailto:amy.marrich@rackspace.com">mailto:amy.marrich@rackspace.com</a>>>,<br>
> "women-of-openstack@lists.openstack.org<br>
> <<a href="mailto:women-of-openstack@lists.openstack.org">mailto:women-of-openstack@lists.openstack.org</a>>"<br>
> <<a href="mailto:women-of-openstack@lists.openstack.org%0b">women-of-openstack@lists.openstack.org<br>
</a>> <<a href="mailto:women-of-openstack@lists.openstack.org">mailto:women-of-openstack@lists.openstack.org</a>>><br>
> Subject: RE: [Women-of-openstack] Technica Inquiries on the List<br>
><br>
> Thank you, Amy! Here goes:<br>
><br>
> We have a Contrail Cloud Platform Configuration. We are considering a<br>
> single node reference that is then extended to additional nodes based on<br>
> the growth. It is unknown if compute, storage, or networking<br>
> requirements will grow first. What are the advantages and <br>
> disadvantages of this approach?<br>
><br>
> I appreciate the encouragement.<br>
><br>
> Rhonda<br>
><br>
> *From:* Amy Marrich [<a href="mailto:Amy.Marrich@rackspace.com">mailto:Amy.Marrich@rackspace.com</a>]<br>
> *Sent:* Tuesday, April 05, 2016 1:21 PM<br>
> *To:* Rhonda Eldridge <<a href="mailto:reldridge@technicacorp.com%20%0b">reldridge@technicacorp.com
<br>
</a>> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>>;<br>
> <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</a><br>
> <<a href="mailto:women-of-openstack@lists.openstack.org">mailto:women-of-openstack@lists.openstack.org</a>><br>
> *Subject:* Re: [Women-of-openstack] Technica Inquiries on the List<br>
><br>
> Rhonda,<br>
><br>
> Go for it, if we can't answer we can probably point you in the right <br>
> direction.<br>
><br>
> Amy<br>
><br>
> *From: *Rhonda Eldridge <<a href="mailto:reldridge@technicacorp.com%20%0b">reldridge@technicacorp.com
<br>
</a>> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> *Date: *Tuesday, April 5, 2016 at 12:18 PM<br>
> *To: *"women-of-openstack@lists.openstack.org<br>
> <<a href="mailto:women-of-openstack@lists.openstack.org">mailto:women-of-openstack@lists.openstack.org</a>>"<br>
> <<a href="mailto:women-of-openstack@lists.openstack.org%0b">women-of-openstack@lists.openstack.org<br>
</a>> <<a href="mailto:women-of-openstack@lists.openstack.org">mailto:women-of-openstack@lists.openstack.org</a>>><br>
> *Subject: *[Women-of-openstack] Technica Inquiries on the List<br>
><br>
> Hello -<br>
><br>
> I am a new member of this list. I would like to post a technical <br>
> question and get the opinion of this community, but I also want to <br>
> respect the intention of the topics on this list.<br>
><br>
> Can someone let me know if a technical inquiry would be welcomed?<br>
><br>
> Sincerely,<br>
><br>
> Rhonda Eldridge<br>
><br>
> Director of Engineering<br>
><br>
> Technica Corporation<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Women-of-openstack mailing list<br>
> <a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack">
http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack</a><br>
><br>
<br>
_______________________________________________<br>
Women-of-openstack mailing list<br>
<a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack</a><br>
<br>
_______________________________________________<br>
Women-of-openstack mailing list<br>
<a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack</a><br>
<br>
_______________________________________________<br>
Women-of-openstack mailing list<br>
<a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>