Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On Tue, Apr 15, 2014 at 04:30:53PM EDT, Joe Gordon wrote: > One of my biggest issues with running devstack in vagrant is how slow > it is The vagrant_devstack project (github.com/bcwaldon/vagrant_devstack) has some Chef recipes to cache pip and apt - so it's only the first run that is slow, and rebuilds are sped up. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On Fri, Apr 11, 2014 at 11:24 AM, Sean Dague wrote: > On 04/11/2014 11:38 AM, Greg Lucas wrote: > > Sean Dague wrote: > >> Maybe it would be good to get an ad-hoc IRC meeting together to figure > >> out what the must have features are that inspired everyone to write > >> these. If we can come up with a way to overlap those all sanely, moving > >> to stackforge and doing this via gerrit would be something I'd be into. > > > > This is a good idea, I've definitely stumbled across lots of GitHub > > projects, blog posts, etc that overlap here. > > > > Folks seem to have a strong preference for provisioner so it may makes > > sense to support several. We can put together a Vagrantfile that allows > > you to choose a provisioner while maintaining a common machine > > configuration (using --provision-with or using env variables and loading > > in additional rb files, etc). > > Honestly, multi provisioner support is something I think shouldn't be > done. That's realistically where I become uninterested in spending > effort here. Puppet is needed if we want to be able to replicate > devstack-gate locally (which is one of the reasons I started writing this). > > Being opinionated is good when it comes to providing tools to make > things easy to onboard people. The provisioner in infra is puppet. > Learning puppet lets you contribute to the rest of the openstack infra, > and I expect to consume some piece of that in this process. I get that > leaves other efforts out in the cold, but the tradeoff in the other > direction I don't think is worth it. > > The place I think plugability makes sense is in virt backends. I'd > honestly love to be able to do nested kvm for performance reasons, or an > openstack cloud for dogfooding reasons. > I originally cobbled together https://github.com/jogo/DevstackUp to run devstack locally as there were no good alternatives at the time. I would be really happy to see a vagrant devstack runner that looks more like how infra does it. One of my biggest issues with running devstack in vagrant is how slow it is to set everything up, there are a lot of packages to install. Hopefully with one consolidated devstack vagrant we can address this. On a related note, I have stopped using vagrant and just use nova on a public cloud. > -Sean > > -- > Sean Dague > Samsung Research America > s...@dague.net / sean.da...@samsung.com > http://dague.net > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On Fri, Apr 11, 2014 at 8:40 AM, Anne Gentle wrote: > I'd love to see consolidation as I've tried to keep up nova dev docs for > example, and with all the options it's tough to test and maintain one for > docs. Go for it. > Nova isn't the only project that uses devstack, so shouldn't docs on how to set up devstack live at http://devstack.org/ or where ever the official docs for devstack are? > > > On Fri, Apr 11, 2014 at 9:34 AM, Collins, Sean < > sean_colli...@cable.comcast.com> wrote: > >> Hi, >> >> I've noticed a proliferation of Vagrant projects that are popping up, is >> there any interest from other authors in trying to consolidate? >> >> https://github.com/bcwaldon/vagrant_devstack >> >> https://github.com/sdague/devstack-vagrant >> >> http://openstack.prov12n.com/how-to-make-a-lot-of-devstack-with-vagrant/ >> >> https://github.com/jogo/DevstackUp >> >> https://github.com/search?q=vagrant+devstack&ref=cmdform >> >> -- >> Sean M. Collins >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
> Honestly, multi provisioner support is something I think shouldn't be > done. > if there's already a provisioner that is used for infra, > let's re-use some of that knowledge and expertise. OK, I'm convinced. :-) I was thinking one reason there is a proliferation of devstack vagrantfiles is that when people find one with a provisioner they aren't already familiar with, they tend to build from scratch with something they know. But agreed that the efforts of the community would be better focused on a single configuration, particularly one that aligns with the existing infrastructure. > The place I think plugability makes sense is in virt backends. I'd > honestly love to be able to do nested kvm for performance reasons, or an > openstack cloud for dogfooding reasons. +1 for nested virt support. ~Greg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On Fri, Apr 11, 2014 at 02:24:10PM EDT, Sean Dague wrote: > Honestly, multi provisioner support is something I think shouldn't be > done. Agreed - in addition let's keep this in perspective - we're just adding a little bit of glue to prep the VM for the running of DevStack, which does the heavy lifting. > Being opinionated is good when it comes to providing tools to make > things easy to onboard people. The provisioner in infra is puppet. > Learning puppet lets you contribute to the rest of the openstack infra, > and I expect to consume some piece of that in this process. +1000 on this - if there's already a provisioner that is used for infra, let's re-use some of that knowledge and expertise. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On 04/11/2014 11:38 AM, Greg Lucas wrote: > Sean Dague wrote: >> Maybe it would be good to get an ad-hoc IRC meeting together to figure >> out what the must have features are that inspired everyone to write >> these. If we can come up with a way to overlap those all sanely, moving >> to stackforge and doing this via gerrit would be something I'd be into. > > This is a good idea, I've definitely stumbled across lots of GitHub > projects, blog posts, etc that overlap here. > > Folks seem to have a strong preference for provisioner so it may makes > sense to support several. We can put together a Vagrantfile that allows > you to choose a provisioner while maintaining a common machine > configuration (using --provision-with or using env variables and loading > in additional rb files, etc). Honestly, multi provisioner support is something I think shouldn't be done. That's realistically where I become uninterested in spending effort here. Puppet is needed if we want to be able to replicate devstack-gate locally (which is one of the reasons I started writing this). Being opinionated is good when it comes to providing tools to make things easy to onboard people. The provisioner in infra is puppet. Learning puppet lets you contribute to the rest of the openstack infra, and I expect to consume some piece of that in this process. I get that leaves other efforts out in the cold, but the tradeoff in the other direction I don't think is worth it. The place I think plugability makes sense is in virt backends. I'd honestly love to be able to do nested kvm for performance reasons, or an openstack cloud for dogfooding reasons. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
Sean Dague wrote: > Maybe it would be good to get an ad-hoc IRC meeting together to figure > out what the must have features are that inspired everyone to write > these. If we can come up with a way to overlap those all sanely, moving > to stackforge and doing this via gerrit would be something I'd be into. This is a good idea, I've definitely stumbled across lots of GitHub projects, blog posts, etc that overlap here. Folks seem to have a strong preference for provisioner so it may makes sense to support several. We can put together a Vagrantfile that allows you to choose a provisioner while maintaining a common machine configuration (using --provision-with or using env variables and loading in additional rb files, etc). ~Greg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
I'd love to see consolidation as I've tried to keep up nova dev docs for example, and with all the options it's tough to test and maintain one for docs. Go for it. On Fri, Apr 11, 2014 at 9:34 AM, Collins, Sean < sean_colli...@cable.comcast.com> wrote: > Hi, > > I've noticed a proliferation of Vagrant projects that are popping up, is > there any interest from other authors in trying to consolidate? > > https://github.com/bcwaldon/vagrant_devstack > > https://github.com/sdague/devstack-vagrant > > http://openstack.prov12n.com/how-to-make-a-lot-of-devstack-with-vagrant/ > > https://github.com/jogo/DevstackUp > > https://github.com/search?q=vagrant+devstack&ref=cmdform > > -- > Sean M. Collins > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
> Maybe it would be good to get an ad-hoc IRC meeting together to figure > out what the must have features are that inspired everyone to write > these. If we can come up with a way to overlap those all sanely, moving > to stackforge and doing this via gerrit would be something I'd be into. > > -Sean +1 to this idea. I found vagrant_devstack a while ago and started using it and then started documenting it for our development team at Comcast, it has been very helpful for getting new developers started. Having something in Stackforge would be great, so that we can consolidate all our knowledge and energy. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
On 04/11/2014 10:34 AM, Collins, Sean wrote: > Hi, > > I've noticed a proliferation of Vagrant projects that are popping up, is > there any interest from other authors in trying to consolidate? > > https://github.com/bcwaldon/vagrant_devstack > > https://github.com/sdague/devstack-vagrant > > http://openstack.prov12n.com/how-to-make-a-lot-of-devstack-with-vagrant/ > > https://github.com/jogo/DevstackUp > > https://github.com/search?q=vagrant+devstack&ref=cmdform That's definitely an option. As I look at the differences across the projects I mostly see that there are differences with the provisioning engine. My personal end game was to get to a point where it would be simple to replicate the devstack gate, which means reusing that puppet policy (which is why I started with puppet). I see https://github.com/bcwaldon/vagrant_devstack is based on chef. And https://github.com/jogo/DevstackUp is just shell. Maybe it would be good to get an ad-hoc IRC meeting together to figure out what the must have features are that inspired everyone to write these. If we can come up with a way to overlap those all sanely, moving to stackforge and doing this via gerrit would be something I'd be into. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Vagrant Devstack projects - time to consolidate?
Hi, I've noticed a proliferation of Vagrant projects that are popping up, is there any interest from other authors in trying to consolidate? https://github.com/bcwaldon/vagrant_devstack https://github.com/sdague/devstack-vagrant http://openstack.prov12n.com/how-to-make-a-lot-of-devstack-with-vagrant/ https://github.com/jogo/DevstackUp https://github.com/search?q=vagrant+devstack&ref=cmdform -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
