Yes Inviato da iPhone
> Il giorno 16 gen 2017, alle ore 16:26, Manuel Sopena Ballesteros > <manuel...@garvan.org.au> ha scritto: > > Some people has mentioned packstack as a deployment tool for production, > however as far as I know packstack does not provide HA. > > Would tripleO be a better fit for production instead of packstack? > > thanks > > Manuel > > > -----Original Message----- > From: Juris M. [mailto:jm...@gmx.com] > Sent: Tuesday, January 17, 2017 9:22 AM > To: Remo Mattei; Melvin Hillsman > Cc: openstack@lists.openstack.org > Subject: Re: [Openstack] recommended way to install openstack today > > Hi, > > I missed the initial mail that started this thread, as I wasn't signed up to > the mailing list at the time, so I'm replying to this (I apologize if this is > frowned upon). > > I would like to add my two cents to the ones suggesting to use a deployment > tool, like Puppet, Ansible or Packstack (whichever you prefer, really, or > depending on any dependencies you may have) if for nothing else but the fact > that you'll end up with some sort of reusable instruction file. This is > preferable for a few reasons. You can inspect the file to see what are the > various things the deployment system accounted for to perform the deployment. > You can then add or change variables to experiment and using some version > control system save your configurations to return to a known or interesting > configuration. > > If you're interested in how the actual configuration of the services looks > like, you can always connect to your nodes and inspect them that way, or > collect them and compare to the answer file to see which option affected > what. Also, this will primarily save you time, as your experimentation may > break the environment for some reason, and it will simply become tedious to > do it by hand over and over. > > I do, however, suggest that you try to repeat the deployment of a service or > few by hand in different configurations, just to get the hang of it and walk > through the process manually and see what all the moving pieces are - this > will come in handy in situation when something breaks and you want to be able > to fix it rather than redeploy. > > I wish you the best of luck :) > > -- > Juris M. > > >> On Mon, 2017-01-16 at 12:35 -0800, Remo Mattei wrote: >> The main point is what you are trying to get out. In the enterprise >> space you will never install it from source now. Too complex too hard >> not upgrades etc etc. We did a deployment after the initial config of >> the yaml file the ha 3 controllers 3 computes and ceph servers took >> 37 min no way you can do that in any other ways. >> >> >> >> Inviato da iPhone >> >>> Il giorno 16 gen 2017, alle ore 08:30, Melvin Hillsman <mrhillsman@ >>> gmail.com> ha scritto: >>> >>> When I originally starting deploying OpenStack I did it by hand with >>> multiple VMs just to get the hang of it and highly recommend this >>> method for any newcomer because it gives you an idea of the >>> configurations and interdependencies. Being employed to work on >>> OpenStack led me to use openstack-ansible and to be honest if it >>> were not a “requirement” for the team I work with I would probably >>> still use it though some other options are worth considering; like >>> those you mentioned. >>> >>> Deployment Guide: http://docs.openstack.org/project-deploy-guide/op >>> enstack-ansible/newton/ >>> Developer Documentation: http://docs.openstack.org/developer/openst >>> ack-ansible/ >>> >>> Kind regards, >>> -- >>> Melvin Hillsman >>> Ops Technical Lead >>> OpenStack Innovation Center >>> >>> mrhills...@gmail.com >>> phone: (210) 312-1267 >>> mobile: (210) 413-1659 >>> Learner | Ideation | Belief | Responsibility | Command >>> http://osic.org >>> >>> >>> On 1/16/17, 8:44 AM, "Remo Mattei" <r...@italy1.com> wrote: >>> >>> I would not suggest devstack depending on what you want to learn >>> but devstack is tailored for dev. If you want a system closer to >>> production look into packstack and you can reboot without having to >>> deal with the devstack issue and then you have to learn screen etc. >>> >>> Also look into trystack if you are just want to learn it and not >>> install it. >>> Have a good day! >>> >>> Remo >>> >>> Inviato da iPhone >>> >>>> Il giorno 15 gen 2017, alle ore 23:51, i...@bjoern-stuebe.de ha >>>> scritto: >>>> >>>> Hey, >>>> >>>> i used it for study purposes, too. >>>> >>>> I implemented an OpenStack environment with DevStack. This is a >>>> easy way to deploy OpenStack on your System. You will find a good >>>> documentation on openstack.org. >>>> >>>> http://docs.openstack.org/developer/devstack/guides/single-machin >>>> e.html >>>> http://docs.openstack.org/developer/devstack/ >>>> >>>> greetings, >>>> bjoern >>>> >>>> >>>> >>>> Zitat von Manuel Sopena Ballesteros <manuel...@garvan.org.au>: >>>> >>>>> Hi, >>>>> >>>>> We have been testing openstack for a few days in a all-in-one >>>>> flavor. Now we would like to have an openstack HA production >>>>> environment. I see there are multiple ways to do this... >>>>> TripleO, fuel, kolla... my question is what would be your >>>>> preferred way to deploy openstack today? >>>>> >>>>> Thank you very much >>>>> >>>>> Manuel Sopena Ballesteros | Big data Engineer Garvan Institute >>>>> of Medical Research The Kinghorn Cancer Centre, 370 Victoria >>>>> Street, Darlinghurst, NSW 2010 >>>>> T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel.sb@g >>>>> arvan.org.au<mailto:manuel...@garvan.org.au> >>>>> >>>>> NOTICE >>>>> Please consider the environment before printing this email. >>>>> This message and any attachments are intended for the addressee >>>>> named and may contain legally privileged/confidential/copyright >>>>> information. If you are not the intended recipient, you should >>>>> not read, use, disclose, copy or distribute this communication. >>>>> If you have received this message in error please notify us at >>>>> once by return email and then delete both messages. We accept no >>>>> liability for the distribution of viruses or similar in >>>>> electronic communications. This notice should not be removed. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo >>>> /openstack >>>> Post to : openstack@lists.openstack.org Unsubscribe : >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo >>>> /openstack >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinf >>> o/openstack >>> Post to : openstack@lists.openstack.org >>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinf >>> o/openstack >>> >>> >>> >>> >>> >>> >> >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ope >> nstack >> Post to : openstack@lists.openstack.org Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/ope >> nstack > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > NOTICE > Please consider the environment before printing this email. This message and > any attachments are intended for the addressee named and may contain legally > privileged/confidential/copyright information. If you are not the intended > recipient, you should not read, use, disclose, copy or distribute this > communication. If you have received this message in error please notify us at > once by return email and then delete both messages. We accept no liability > for the distribution of viruses or similar in electronic communications. This > notice should not be removed. > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > !DSPAM:1,587d661779432060110563! > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
