<div dir="ltr">i have tried MaaS+juju openstack deployment quite easy to deploy.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 26, 2017 at 3:38 AM, Satish Patel <span dir="ltr"><<a href="mailto:satish.txt@gmail.com" target="_blank">satish.txt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you folks!<br>
<br>
I have 5 node so following role i am planning to implement, I am<br>
little confused related network component, should i use DVR<br>
(distributed virtual router ) but problem is every single node need<br>
public IP address in that case, first time building production style<br>
openstack so don't know what would be the best option?<br>
<br>
1 controller + network<br>
4 compute node<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Jun 21, 2017 at 10:22 PM, Mike Smith <<a href="mailto:mismith@overstock.com">mismith@overstock.com</a>> wrote:<br>
> Agree you should definitely check out what is already out there in community<br>
> if you are starting from scratch. In our specific case, we do our puppet<br>
> configs manually because 1) we are still on puppet v3 for everything else<br>
> and 2) we have been doing it this way since Folsom and it’s worked well.<br>
><br>
> We are about to build another new cluster on Ocata and I think for that one<br>
> I will try and leverage more of the community puppet stuff if possible.<br>
><br>
> On Jun 21, 2017, at 1:49 PM, John van Ommen <<a href="mailto:john.vanommen@gmail.com">john.vanommen@gmail.com</a>> wrote:<br>
><br>
> I couldn't agree more. OpenStack deployment is not a trivial task. Do not<br>
> reinvent the wheel.<br>
><br>
> John<br>
><br>
> On Jun 21, 2017 12:04 PM, "Erik McCormick" <<a href="mailto:emccormick@cirrusseven.com">emccormick@cirrusseven.com</a>><br>
> wrote:<br>
>><br>
>> If you are a Puppet shop you should check out the Puppet community<br>
>> modules. You will get familiar with all the inner goo as you'll need your<br>
>> own composition layer (in my case a series of hiera files). There's no<br>
>> reason to reinvent the wheel unless you really want to.<br>
>><br>
>> -Erik<br>
>><br>
>> On Jun 21, 2017 2:19 PM, "Satish Patel" <<a href="mailto:satish.txt@gmail.com">satish.txt@gmail.com</a>> wrote:<br>
>>><br>
>>> Thank you all of you for your opinion, As mike suggested i am also<br>
>>> planning to brew home grown puppet module to understand each and every<br>
>>> component and their role instead of grabbing third party tool, I am<br>
>>> sure OOO is best for 100 deploying 100 compute node but in my setup we<br>
>>> have only 5 servers and its not worth it to manage undercloud server.<br>
>>><br>
>>> We are puppet shop so it would be easy to write own code and go from<br>
>>> there.<br>
>>><br>
>>> On Wed, Jun 21, 2017 at 1:25 AM, Remo Mattei <<a href="mailto:remo@italy1.com">remo@italy1.com</a>> wrote:<br>
>>> > I did a deployment with cs9 hp it was pretty bad. I hope the new one<br>
>>> > does<br>
>>> > better.<br>
>>> ><br>
>>> > Nevertheless I do not see many using hp out there. Maybe different<br>
>>> > regions<br>
>>> > like emea do better with that.<br>
>>> ><br>
>>> > Inviato da iPhone<br>
>>> ><br>
>>> > Il giorno 20 giu 2017, alle ore 21:10, John van Ommen<br>
>>> > <<a href="mailto:john.vanommen@gmail.com">john.vanommen@gmail.com</a>> ha scritto:<br>
>>> ><br>
>>> > At HPE we originally used TripleO but switched to a 'flat' model.<br>
>>> ><br>
>>> > I personally didn't see any advantage to Triple O. In theory, it should<br>
>>> > be<br>
>>> > easier to manage and upgrade. In the real world, Helion 3.0 and 4.0 are<br>
>>> > superior in every respect.<br>
>>> ><br>
>>> > John<br>
>>> ><br>
>>> > On Jun 20, 2017 9:02 PM, "Remo Mattei" <<a href="mailto:remo@italy1.com">remo@italy1.com</a>> wrote:<br>
>>> >><br>
>>> >> I worked for Red Hat and they really want to get ooo going because the<br>
>>> >> installation tools did never work as everyone was hoping. Before Red<br>
>>> >> Hat I<br>
>>> >> was at Mirantis and the fuel installation was nice now dead. I know<br>
>>> >> ooo will<br>
>>> >> go into containers next couple of release but kolla–Ansible is one of<br>
>>> >> the<br>
>>> >> emerging solutions now to get it out fast.<br>
>>> >><br>
>>> >> I am doing a project now where I am working on deploying ooo just<br>
>>> >> finished<br>
>>> >> the doc for Ocata undercloud.<br>
>>> >><br>
>>> >> Just my two cents to concord with Mike’s statement.<br>
>>> >><br>
>>> >> Remo<br>
>>> >><br>
>>> >> Inviato da iPhone<br>
>>> >><br>
>>> >> Il giorno 20 giu 2017, alle ore 20:51, Mike Smith<br>
>>> >> <<a href="mailto:mismith@overstock.com">mismith@overstock.com</a>><br>
>>> >> ha scritto:<br>
>>> >><br>
>>> >> There are definitely 1,001 opinions on what is “best”. We use RDO at<br>
>>> >> Overstock and we use home-grown puppet modules because we do our own<br>
>>> >> puppet<br>
>>> >> modules for everything else we do here. We based everything around<br>
>>> >> the<br>
>>> >> official Openstack install documents and we do it because we want to<br>
>>> >> *fully*<br>
>>> >> understand everything we can instead of treating it like a black box<br>
>>> >> that<br>
>>> >> knows how to do the magic.<br>
>>> >><br>
>>> >> However, there are lots of options out there - ansible, kolla, puppet<br>
>>> >> plus<br>
>>> >> vendor-specific options too like those provided by Mirantis. If there<br>
>>> >> are<br>
>>> >> config management tools (ansible, puppet, etc) that you already use,<br>
>>> >> you may<br>
>>> >> want to check out the Openstack options for those. You are correct<br>
>>> >> that<br>
>>> >> that packstack is more of a ‘all-in-one-server’ installer for a quick<br>
>>> >> POC.<br>
>>> >> It can to more, but I think RDO recommends “Triple-O” (which stands<br>
>>> >> for<br>
>>> >> Openstack-on-Openstack) for production RDO deploys. Since they are<br>
>>> >> affiliated with RedHat, they would also lean heavily towards the<br>
>>> >> Ansible<br>
>>> >> option as well.<br>
>>> >><br>
>>> >> Good luck!<br>
>>> >><br>
>>> >><br>
>>> >> Mike Smith<br>
>>> >> Overstock Cloud Team<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> On Jun 20, 2017, at 5:49 PM, Erik McCormick<br>
>>> >> <<a href="mailto:emccormick@cirrusseven.com">emccormick@cirrusseven.com</a>><br>
>>> >> wrote:<br>
>>> >><br>
>>> >> This is a religious discussion for most, but I would suggest Kolla. It<br>
>>> >> takes out a lot of the guess work, has a good upgrade mechanism, and<br>
>>> >> is well<br>
>>> >> supported by the community via mailing list and ORC. Take a look.<br>
>>> >><br>
>>> >> -Erik<br>
>>> >><br>
>>> >><br>
>>> >> On Jun 20, 2017 7:15 PM, "Satish Patel" <<a href="mailto:satish.txt@gmail.com">satish.txt@gmail.com</a>> wrote:<br>
>>> >>><br>
>>> >>> We are deploying 5 node openstack cloud for internal use and<br>
>>> >>> wondering<br>
>>> >>> what method we should use, initial test was on RDO packstack but i<br>
>>> >>> heard packstack isn't good for production, some people on google<br>
>>> >>> suggesting using triplo. I found its little complicated because you<br>
>>> >>> need one more extra server run undercloud openstack to deploy<br>
>>> >>> overcloud openstack, should i really use triplo or is there any other<br>
>>> >>> and easy method which can allow us to upgrade in future also.<br>
>>> >>><br>
>>> >>> ______________________________<wbr>_________________<br>
>>> >>> Mailing list:<br>
>>> >>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> >>> Unsubscribe :<br>
>>> >>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >><br>
>>> >> ______________________________<wbr>_________________<br>
>>> >> Mailing list:<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> >> Unsubscribe :<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >><br>
>>> >><br>
>>> >> wbr>5949ed75173232896912281!<br>
>>> >><br>
>>> >> ______________________________<wbr>_________________<br>
>>> >> Mailing list:<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> >> Unsubscribe :<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >><br>
>>> >> !DSPAM:1,<wbr>5949ed75173232896912281!<br>
>>> >><br>
>>> >><br>
>>> >> ______________________________<wbr>_________________<br>
>>> >> Mailing list:<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> >> Unsubscribe :<br>
>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> >><br>
>>> > !DSPAM:1,<wbr>5949f395185901832122137!<br>
>>> ><br>
>>> ><br>
>>> > ______________________________<wbr>_________________<br>
>>> > Mailing list:<br>
>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> > Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> > Unsubscribe :<br>
>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> ><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Mailing list:<br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>>> Unsubscribe :<br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Mailing list:<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> Unsubscribe :<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
>><br>
> ______________________________<wbr>_________________<br>
> Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
> Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
> Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
> Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
><br>
<br>
______________________________<wbr>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
</div></div></blockquote></div><br></div>