Open Stack

Rhonda,

Here is an example Mirantis/RA that has been vetted and deployed. Redapt is agnostic solutions team and we have deployed multiple customized solutions depending on preferences and needs. We can certainly chat further in Austin or before.

Looking forward to meeting more of the ladies at OpenStack!

Sheryl Sick | SAE Technology Solutions
Redapt, Inc. 206.218.6690

From: Rhonda Eldridge
Date: Tuesday, April 5, 2016 at 11:59 AM
To: Sheryl Sick, Rochelle Grober, Gema Gomez, "women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>"
Subject: RE: [Women-of-openstack] Technica Inquiries on the List

Thank you, Sheryl!

Sincerely,
Rhonda

From: Sheryl Sick [mailto:sheryls at redapt.com]
Sent: Tuesday, April 05, 2016 2:51 PM
To: Rochelle Grober <rochelle.grober at huawei.com<mailto:rochelle.grober at huawei.com>>; Gema Gomez <gema at ggomez.me<mailto:gema at ggomez.me>>; women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>; Rhonda Eldridge <reldridge at technicacorp.com<mailto:reldridge at technicacorp.com>>
Subject: Re: [Women-of-openstack] Technica Inquiries on the List

Hello ladies and looking forward to meeting everyone in a few weeks!

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.
Sheryl Sick | SAE Technology Solutions
Redapt, Inc. 206.218.6690<tel:206.218.6690>



On Tue, Apr 5, 2016 at 11:26 AM -0700, "Rhonda Eldridge" <reldridge at technicacorp.com<mailto:reldridge at technicacorp.com>> wrote:
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?

https://docs.mirantis.com/openstack/fuel/fuel-8.0/pdf/Mirantis-OpenStack-8.0-PlanningGuide.pdf

https://www.mirantis.com/blog/hardware-bom-calculator-controllers-switches-bells-and-whistles/

https://software.mirantis.com/reference-documentation-on-fuel-folsom-2-1/sizing-hardware/



Looking forward to meeting some of you in Austin,
Rhonda


-----Original Message-----
From: Rochelle Grober [mailto:rochelle.grober at huawei.com]
Sent: Tuesday, April 05, 2016 2:05 PM
To: Gema Gomez <gema at ggomez.me<mailto:gema at ggomez.me>>; women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>
Subject: Re: [Women-of-openstack] Technica Inquiries on the List

Great advice, Gema and Amy.

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.

--Rocky

-----Original Message-----
From: Gema Gomez [mailto:gema at ggomez.me]
Sent: Tuesday, April 05, 2016 10:58 AM
To: women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>
Subject: Re: [Women-of-openstack] Technica Inquiries on the List

I totally agree with Amy.

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.

Also, simple maintenance tasks like upgrading packages/kernel will cause a disruption to your service.

I wouldn't go to production with less than 3 nodes for a small and cozy cloud.

Cheers,
Gema

On 05/04/16 18:47, Amy Marrich wrote:
> Rhonda,
>
> Well main disadvantage would be single point of failure, we do
> something very similar with the OpenStack-Ansible project's AIO
> installs but those are generally fro PoC and development. My guess
> from experience is compute and network will grow before storage but it
> depends on your use case.
>
> I think you'd get the best response probably over in the #openstack
> channel on freenode, lots of folks over there to answer questions.
>
> Amy
>
> From: Rhonda Eldridge <reldridge at technicacorp.com
<mailto:reldridge at technicacorp.com%20%0b>> <mailto:reldridge at technicacorp.com>>
> Date: Tuesday, April 5, 2016 at 12:36 PM
> To: Amy Marrich <amy.marrich at rackspace.com
<mailto:amy.marrich at rackspace.com%20%0b>> <mailto:amy.marrich at rackspace.com>>,
> "women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>
> <mailto:women-of-openstack at lists.openstack.org>"
> <women-of-openstack at lists.openstack.org
<mailto:women-of-openstack at lists.openstack.org%0b>> <mailto:women-of-openstack at lists.openstack.org>>
> Subject: RE: [Women-of-openstack] Technica Inquiries on the List
>
> Thank you, Amy!  Here goes:
>
> We have a Contrail Cloud Platform Configuration.   We are considering a
> single node reference that is then extended to additional nodes based on
> the growth.   It is unknown if compute, storage, or networking
> requirements will grow first. What are the advantages and
> disadvantages of this approach?
>
> I appreciate the encouragement.
>
> Rhonda
>
> *From:* Amy Marrich [mailto:Amy.Marrich at rackspace.com]
> *Sent:* Tuesday, April 05, 2016 1:21 PM
> *To:* Rhonda Eldridge <reldridge at technicacorp.com
<mailto:reldridge at technicacorp.com%20%0b>> <mailto:reldridge at technicacorp.com>>;
> women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>
> <mailto:women-of-openstack at lists.openstack.org>
> *Subject:* Re: [Women-of-openstack] Technica Inquiries on the List
>
> Rhonda,
>
> Go for it, if we can't answer we can probably point you in the right
> direction.
>
> Amy
>
> *From: *Rhonda Eldridge <reldridge at technicacorp.com
<mailto:reldridge at technicacorp.com%20%0b>> <mailto:reldridge at technicacorp.com>>
> *Date: *Tuesday, April 5, 2016 at 12:18 PM
> *To: *"women-of-openstack at lists.openstack.org<mailto:women-of-openstack at lists.openstack.org>
> <mailto:women-of-openstack at lists.openstack.org>"
> <women-of-openstack at lists.openstack.org
<mailto:women-of-openstack at lists.openstack.org%0b>> <mailto:women-of-openstack at lists.openstack.org>>
> *Subject: *[Women-of-openstack] Technica Inquiries on the List
>
> Hello -
>
> I am a new member of this list.  I would like to post a technical
> question and get the opinion of this community, but I also want to
> respect the intention of the topics on this list.
>
> Can someone let me know if a technical inquiry would be welcomed?
>
> Sincerely,
>
> Rhonda Eldridge
>
> Director of Engineering
>
> Technica Corporation
>
>
>
> _______________________________________________
> Women-of-openstack mailing list
> Women-of-openstack at lists.openstack.org<mailto:Women-of-openstack at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack
>

_______________________________________________
Women-of-openstack mailing list
Women-of-openstack at lists.openstack.org<mailto:Women-of-openstack at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack

_______________________________________________
Women-of-openstack mailing list
Women-of-openstack at lists.openstack.org<mailto:Women-of-openstack at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack

_______________________________________________
Women-of-openstack mailing list
Women-of-openstack at lists.openstack.org<mailto:Women-of-openstack at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/3b936a63/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MirantisUnlockedAppliance-Openstack.pdf
Type: application/pdf
Size: 1295232 bytes
Desc: MirantisUnlockedAppliance-Openstack.pdf
URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20160405/3b936a63/attachment-0001.pdf>