[Container-tools] Recommendations for bootstrapping a local k8s cluster?

Aaron Weitekamp aweiteka at redhat.com
Thu May 28 13:46:23 UTC 2015



----- Original Message -----
> On Tue, 2015-05-26 at 09:27 -0400, Aaron Weitekamp wrote:
> > Top-posting since I'm not following all of this thread.
> replying inline to your top post ;)
> 
> > 
> > omv breaks the typical Vagrant model in that I can't have a different
> > Vagrantfile per project that each do different things. I have to keep
> > changing my omv.yaml file.
> Actually this is not true. You can have multiple clones of the
> Oh-My-Vagrant project, and put one in each project dir where you want a
> vagrant env.

Sure, but omv is software that needs updating and now I have to manage updates in multiple places. Also I don't want to put clones of omv in each of my projects. A single Vagrantfile (or omv.yaml) is acceptable, even desirable, to include in each project but I don't want a sub-repo nested in each of my projects that are under version control. That's a mess.

> 
> >  So I *must* run vagrant from the omv dir to get all of its
> > functionality. This also means the common "rsync from current working
> > directory" model has to change. It's a bit awkward and I feel like I'm
> > always "managing" my dev environment.
> If you want to run OMV from *any* dir (I think this is what you're
> asking) there is a VAGRANT_CWD option which you can use and set per
> project. rbarlow (bowlofeggs) is looking into this and making sure it's
> seamless with OMV.
> 
> > 
> > As I work to containerize my desktop I really like the "run from
> > current working directory" model where the container bindmounts
> > whatever git repo I'm working in. This fits with Vagrant and
> > containers and I think it can work with omv as well. It's a pattern
> > that is beginning to emerge with development environment containers.
> > 
> > * super-priv container with git, ansible and omv (not vagrant)
> > * rely on host-installed vagrant
> > * each development project repo has a customized omv.yaml file for
> > that project
> > * bindmount `pwd` into container
> 
> 
> 




More information about the Container-tools mailing list