Open Stack

i have tried MaaS+juju openstack deployment quite easy to deploy.


On Mon, Jun 26, 2017 at 3:38 AM, Satish Patel <satish.txt at gmail.com> wrote:

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