<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>I am definitely enjoying sharing with you all.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Sincerely,</div>
<div id="AppleMailSignature">Rhonda</div>
<div id="AppleMailSignature"><br>
<br>
Sent from my iPad</div>
<div><br>
On Apr 5, 2016, at 4:08 PM, Kathy Cacciatore <<a href="mailto:kathyc@openstack.org">kathyc@openstack.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><font face="arial" size="3">
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
Rhonda, All the resources mentioned in this thread are terrific. You may also try "Ask OpenStack", the community-supported Q&A site for OpenStack users and developers. It's accessible here [1]. </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
[1] <a href="https://ask.openstack.org/">https://ask.openstack.org/</a></p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
On Tuesday, April 5, 2016 1:59pm, <a href="mailto:women-of-openstack-request@lists.openstack.org">
women-of-openstack-request@lists.openstack.org</a> said:<br>
<br>
</p>
<div id="SafeStyles1459885903">
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
> Send Women-of-openstack mailing list submissions to<br>
> <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</a><br>
> <br>
> To subscribe or unsubscribe via the World Wide Web, visit<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>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:women-of-openstack-request@lists.openstack.org">women-of-openstack-request@lists.openstack.org</a><br>
> <br>
> You can reach the person managing the list at<br>
> <a href="mailto:women-of-openstack-owner@lists.openstack.org">women-of-openstack-owner@lists.openstack.org</a><br>
> <br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Women-of-openstack digest..."<br>
> <br>
> <br>
> Today's Topics:<br>
> <br>
> 1. Re: Technica Inquiries on the List (Amy Marrich)<br>
> 2. Re: Technica Inquiries on the List (Sheryl Sick)<br>
> 3. Re: Technica Inquiries on the List (Rhonda Eldridge)<br>
> <br>
> <br>
> ----------------------------------------------------------------------<br>
> <br>
> Message: 1<br>
> Date: Tue, 5 Apr 2016 18:35:43 +0000<br>
> From: Amy Marrich <<a href="mailto:Amy.Marrich@rackspace.com">Amy.Marrich@rackspace.com</a>><br>
> To: Rhonda Eldridge <<a href="mailto:reldridge@technicacorp.com">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">women-of-openstack@lists.openstack.org</a>><br>
> Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
> Message-ID: <D3296D8A.1B067%<a href="mailto:amy.marrich@rackspace.com">amy.marrich@rackspace.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
> <br>
> Rhonda,<br>
> <br>
> When I looked at fuel for an icehouse deployment at a former company the<br>
> concern was that is was proprietary but that is no longer the case.<br>
> There?s at least 4 options available that I can think of offhand within<br>
> the OpenStack projects OSA (ansible), puppet, kolla and fuel and that?s<br>
> not even taking into consideration projects such as heat which can be tied<br>
> into a chef server.<br>
> <br>
> Between the IRC channels and mailing lists you?ll get a lot of<br>
> information, suggestions as well as opinions.:)<br>
> <br>
> Look forward to meeting you in Austin!<br>
> <br>
> Amy<br>
> <br>
> On 4/5/16, 1:23 PM, "Rhonda Eldridge" <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a>> wrote:<br>
> <br>
> >Thank you, all! I commit to putting the question out on the other forums<br>
> >and I just found another tool from Mirantis. Has anyone used it? Do you<br>
> >agree with the recommendations or results?<br>
> ><br>
> ><a href="https://docs.mirantis.com/openstack/fuel/fuel-8.0/pdf/Mirantis-OpenStack-8">https://docs.mirantis.com/openstack/fuel/fuel-8.0/pdf/Mirantis-OpenStack-8</a><br>
> >.0-PlanningGuide.pdf<br>
> ><br>
> ><a href="https://www.mirantis.com/blog/hardware-bom-calculator-controllers-switches">https://www.mirantis.com/blog/hardware-bom-calculator-controllers-switches</a><br>
> >-bells-and-whistles/<br>
> ><br>
> ><a href="https://software.mirantis.com/reference-documentation-on-fuel-folsom-2-1/s">https://software.mirantis.com/reference-documentation-on-fuel-folsom-2-1/s</a><br>
> >izing-hardware/<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<br>
> >working setup as opposed to test/R&D. I've been trying to get "reference<br>
> >architecture" for a three node and a five node HA cloud, as this is<br>
> >tribal knowledge within the Ops community, but getting it defined and<br>
> >documented has not really gone anywhere. Maybe we can get this going<br>
> >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<br>
> >amount of resources your VMs are going to require. Decide what kind of<br>
> >flavors you are going to use (i.e. how much memory, CPU and HD you will<br>
> >need per VM) and then do the math to see how many of those you can fit on<br>
> >your node. It all depends very much on your workload. If you are going to<br>
> >have many small VMs, you'll be able to get more out of your HW than if<br>
> >you have one big VM eating all the resources.<br>
> ><br>
> >Also, simple maintenance tasks like upgrading packages/kernel will cause<br>
> >a disruption to your service.<br>
> ><br>
> >I wouldn't go to production with less than 3 nodes for a small and cozy<br>
> >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">reldridge@technicacorp.com</a><br>
> >> <<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">amy.marrich@rackspace.com</a><br>
> >> <<a href="mailto:amy.marrich@rackspace.com">mailto:amy.marrich@rackspace.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>
> >> <<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>
> >> 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">reldridge@technicacorp.com</a><br>
> >> <<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">reldridge@technicacorp.com</a><br>
> >> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> >> *Date: *Tuesday, April 5, 2016 at 12:18 PM<br>
> >> *To: *"<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>
> >> <<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: *[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><br>
> <br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> Message: 2<br>
> Date: Tue, 5 Apr 2016 18:51:11 +0000<br>
> From: Sheryl Sick <<a href="mailto:sheryls@redapt.com">sheryls@redapt.com</a>><br>
> To: Rochelle Grober <<a href="mailto:rochelle.grober@huawei.com">rochelle.grober@huawei.com</a>>, Gema Gomez<br>
> <<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>
> <<a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</a>>, Rhonda Eldridge<br>
> <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a>><br>
> Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
> Message-ID:<br>
> <<a href="mailto:B2E5F366C8C1E3E5.144EFC1E-6FA6-43D9-83BA-833769264140@mail.outlook.com">B2E5F366C8C1E3E5.144EFC1E-6FA6-43D9-83BA-833769264140@mail.outlook.com</a>><br>
> <br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Hello ladies and looking forward to meeting everyone in a few weeks!<br>
> <br>
> Redapt has deployed several RA variations of OpenStack. We have worked pretty<br>
> closely with Mirantis on multiple projects. I can send over details of an RA later<br>
> this afternoon.<br>
> <br>
> Sheryl Sick | SAE Technology Solutions<br>
> Redapt, Inc. 206.218.6690<<a href="tel:206.218.6690">tel:206.218.6690</a>><br>
> <br>
> <br>
> <br>
> <br>
> On Tue, Apr 5, 2016 at 11:26 AM -0700, "Rhonda Eldridge"<br>
> <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a><<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> wrote:<br>
> <br>
> Thank you, all! I commit to putting the question out on the other forums and I<br>
> just found another tool from Mirantis. Has anyone used it? Do you agree with the<br>
> 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<br>
> setup as opposed to test/R&D. I've been trying to get "reference architecture"<br>
> for a three node and a five node HA cloud, as this is tribal knowledge within the<br>
> Ops community, but getting it defined and documented has not really gone anywhere.<br>
> Maybe we can get this going through a collaboration with this group, Ops and somd<br>
> 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<br>
> resources your VMs are going to require. Decide what kind of flavors you are going<br>
> to use (i.e. how much memory, CPU and HD you will need per VM) and then do the<br>
> math to see how many of those you can fit on your node. It all depends very much<br>
> on your workload. If you are going to have many small VMs, you'll be able to get<br>
> 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<br>
> 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">reldridge@technicacorp.com</a><br>
> > <<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">amy.marrich@rackspace.com</a><br>
> > <<a href="mailto:amy.marrich@rackspace.com">mailto:amy.marrich@rackspace.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>
> > <<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>
> > 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">reldridge@technicacorp.com</a><br>
> > <<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">reldridge@technicacorp.com</a><br>
> > <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> > *Date: *Tuesday, April 5, 2016 at 12:18 PM<br>
> > *To: *"<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>
> > <<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: *[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><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/227564a1/attachment-0001.html">http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/227564a1/attachment-0001.html</a>><br>
> <br>
> ------------------------------<br>
> <br>
> Message: 3<br>
> Date: Tue, 5 Apr 2016 18:59:27 +0000<br>
> From: Rhonda Eldridge <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a>><br>
> To: Sheryl Sick <<a href="mailto:sheryls@redapt.com">sheryls@redapt.com</a>>, Rochelle Grober<br>
> <<a href="mailto:rochelle.grober@huawei.com">rochelle.grober@huawei.com</a>>, Gema Gomez <<a href="mailto:gema@ggomez.me">gema@ggomez.me</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">women-of-openstack@lists.openstack.org</a>><br>
> Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
> Message-ID:<br>
> <<a href="mailto:A0F6E7845F0C7D4FA2A6EE51E50D83F0258944FF@mail-hq3.technica1.com">A0F6E7845F0C7D4FA2A6EE51E50D83F0258944FF@Mail-HQ3.Technica1.com</a>><br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Thank you, Sheryl!<br>
> <br>
> Sincerely,<br>
> Rhonda<br>
> <br>
> From: Sheryl Sick [<a href="mailto:sheryls@redapt.com">mailto:sheryls@redapt.com</a>]<br>
> Sent: Tuesday, April 05, 2016 2:51 PM<br>
> To: Rochelle Grober <<a href="mailto:rochelle.grober@huawei.com">rochelle.grober@huawei.com</a>>; Gema Gomez<br>
> <<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>; Rhonda Eldridge<br>
> <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a>><br>
> Subject: Re: [Women-of-openstack] Technica Inquiries on the List<br>
> <br>
> Hello ladies and looking forward to meeting everyone in a few weeks!<br>
> <br>
> Redapt has deployed several RA variations of OpenStack. We have worked pretty<br>
> closely with Mirantis on multiple projects. I can send over details of an RA later<br>
> this afternoon.<br>
> Sheryl Sick | SAE Technology Solutions<br>
> Redapt, Inc. 206.218.6690<<a href="tel:206.218.6690">tel:206.218.6690</a>><br>
> <br>
> <br>
> <br>
> On Tue, Apr 5, 2016 at 11:26 AM -0700, "Rhonda Eldridge"<br>
> <<a href="mailto:reldridge@technicacorp.com">reldridge@technicacorp.com</a><<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> wrote:<br>
> Thank you, all! I commit to putting the question out on the other forums and I<br>
> just found another tool from Mirantis. Has anyone used it? Do you agree with the<br>
> 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:gema@ggomez.me">mailto:gema@ggomez.me</a>>>;<br>
> <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</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>
> Great advice, Gema and Amy.<br>
> <br>
> Three node is definitely the smallest size anyone should consider for a working<br>
> setup as opposed to test/R&D. I've been trying to get "reference architecture"<br>
> for a three node and a five node HA cloud, as this is tribal knowledge within the<br>
> Ops community, but getting it defined and documented has not really gone anywhere.<br>
> Maybe we can get this going through a collaboration with this group, Ops and somd<br>
> 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:<br>
> <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</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>
> I totally agree with Amy.<br>
> <br>
> It very much depends on how chunky your single node is compared to the amount of<br>
> resources your VMs are going to require. Decide what kind of flavors you are going<br>
> to use (i.e. how much memory, CPU and HD you will need per VM) and then do the<br>
> math to see how many of those you can fit on your node. It all depends very much<br>
> on your workload. If you are going to have many small VMs, you'll be able to get<br>
> 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<br>
> 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">reldridge@technicacorp.com</a><br>
> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>%20%0b>><br>
> <<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">amy.marrich@rackspace.com</a><br>
> <<a href="mailto:amy.marrich@rackspace.com">mailto:amy.marrich@rackspace.com</a>%20%0b>><br>
> <<a href="mailto:amy.marrich@rackspace.com">mailto:amy.marrich@rackspace.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>
> > <<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>%0b>><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>
> > 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">reldridge@technicacorp.com</a><br>
> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>%20%0b>><br>
> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>>;<br>
> ><br>
> <a href="mailto:women-of-openstack@lists.openstack.org">women-of-openstack@lists.openstack.org</a><<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">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">reldridge@technicacorp.com</a><br>
> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>%20%0b>><br>
> <<a href="mailto:reldridge@technicacorp.com">mailto:reldridge@technicacorp.com</a>>><br>
> > *Date: *Tuesday, April 5, 2016 at 12:18 PM<br>
> > *To: *"<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>
> > <<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>%0b>><br>
> <<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>
> ><br>
> <a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a><<a href="mailto:Women-of-openstack@lists.openstack.org">mailto: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><<a href="mailto:Women-of-openstack@lists.openstack.org">mailto: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><<a href="mailto:Women-of-openstack@lists.openstack.org">mailto: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><<a href="mailto:Women-of-openstack@lists.openstack.org">mailto: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>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/1d2d7e33/attachment.html">http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/1d2d7e33/attachment.html</a>><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>
> End of Women-of-openstack Digest, Vol 18, Issue 11<br>
> **************************************************<br>
> </p>
</div>
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
<br>
<br>
</p>
<!--WM_COMPOSE_SIGNATURE_START-->
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
-- <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></p>
<!--WM_COMPOSE_SIGNATURE_END-->
<p style="margin:0;padding:0;font-family: arial; font-size: 12pt; word-wrap: break-word;">
</p>
</font></div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Women-of-openstack mailing list</span><br>
<span><a href="mailto:Women-of-openstack@lists.openstack.org">Women-of-openstack@lists.openstack.org</a></span><br>
<span><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></span><br>
</div>
</blockquote>
</body>
</html>