Vagrant doesn't actually run manifests correctly

[benlangfeld]

Vagrant config added in ad010cb doesn't seem to actually trigger installing any openshift components. I'm not sure what I have to do other than instructing puppet to use the broker.pp manifest to actually get it to do anything. @bklang or @vindir, any ideas?

[bklang]

We had been testing this in a standalone VM, not using Vagrant, so that configuration is not tested. That said, it's probably a small tweak to make it work with Vagrant. I'll take a look.

[bklang]

Some more thoughts on this:

• I think we'll need to release this module to Puppet Forge so we can install it per Puppet instructions.
• I've looked at something like librarian-puppet to provide a single Puppetfile, but it seems unmaintained and broken. This problem is mostly solved by having the module itself list its own dependencies, and be installed as described above. The downside is that there does not appear to be a provision to install Puppet modules from Git or even a source directory without something like librarian-puppet.
• Because of module dependencies and Puppet module paths I'm not sure it makes sense to keep a Vagrantfile in this repo. It might make more sense to separate it out to a DevBox-style repo, but I'm open to other ideas.

[benlangfeld]

So the point is that there should be an easy way to test this setup. Tests for puppet-openshift should be in the puppet-openshift repo. The point is not to provide a simple way to bootstrap the released module, but to test the module while working on it directly. Chef can simply use cookbooks from local disk. I don't understand why Puppet would not allow using the module unpackaged; how are you doing it manually?

[bklang]

The need for puppet install was to satisfy this module's dependencies. Perhaps we can script around that with Vagrant. You can apply a module directly from disk once the dependencies are available to Puppet.

[anderssv]

Would be cool if this worked, but there is no solution yet? Just added some basic instantiation in broker.pp, but I always keep running into issues with templates and other stuff. Also tried using the module with other setup in Vagrant.

Am I correct to assume that the only way to get this working right now is by provisioning through a puppet-master?

[bklang]

It is possible to deploy this with a puppetmaster, but that is not how we were using it. We were simply creating a manifest on the node in question and using "puppet apply" to run the changes. It should work fine with Vagrant, it's just that no one has spent the time to document the integration or even to attempt it.

[anderssv]

Doh... Then I'm a bit lost... New to Puppet as well as OpenShift. :) Would you mind sketching up how you use it? Do you use puppet module install to install the module? What is the full apply command?

[anderssv]

I'm trying to get stuff working. You can see the Vagrant setup I'm running now at https://github.com/anderssv/puppet-vagrant-playground . It's far from ideal as I use two VMs (one puppetmaster) and so far have only looked into the broker. It should be as easy as doing a clone and running ./start.sh to get Vagrant running and testing on your computer.

I would really like to get this stuff working, but I had to add some requires to get it to do some stuff. Right now I seem to struggle with the MongoDB install. I disabled 10gen (which I havn't the faintest idea what is) because it seemed to conflict with dependencies specified in some of the packages of Openshift itself.

I hope creating a "out of the box" setup will help debugging and collaborating around the scripts, so if there's something I can help with or change let me know.

[anderssv]

The broker node now installs all the Puppet stuff. I still have some errors with selinux not beeing active, but I figured out a lot of other dependencies. Still not getting stuff working on the broker, but at least some progress. :)