vagrant talk discussion

vagrant.md

Discussion below in comments

Hi 💋

Hi.

I had the talk I gave for the Mongodb usergroup in mind, with minor changes: https://speakerdeck.com/sgoettschkes/va-short-intro-to-vagrant

After Thomas comment I was more on cutting the theory in half and going right into practice setting up a new vagrant vm, installing node and then getting ghost (blogging plattform written in node) running.

Regarding splitting up: I agree that we could handle it that way that I'm doing the introduction and theory and you show how to do stuff in practice. I think the audience would benefit from 15 mins. of theory to get the background right and then another 15 mins. of seeing how it works in practice.

What do you think?

If you think you could introduce and get something running on it in 15 mins, I think you should just do your talk without my demo.
If you don't - though I would be very impressed if you could and would love to see that - I would do a short demo afterward.

What sounds the most interesting to me is you giving an intro and booting up a box and giving a short SSH exploration, that way my demo could be just me showing my Vagrantfile and tiny application then vagrant up and showing the different Linuxes hitting eachother.

The thing I find most interesting about vagrant is how easy it is to set up a distributed system on your dev machine. I did a demo at vienna.rb last summer where I built a little distributed logger with 4 VMs running rails and one as my logging box. I would probably shoot for something similar.

Back to you.
@Sgoettschkes

Here's the link to the demo I was talking about
https://github.com/pferdefleisch/vagrant-drb-demo

Your talk looks like it could be perfect. I think it gets boring when all talks at a X meetup are about exactly X. And tools are awesome. Especially awesome tools like vagrant. I don't know who would say "Hey, this isn't about Javascript, WTF?!"

I was actually planning on using mongo or http://rethinkdb.com/ in my demo

Yeah, I think 15 mins. are to short for both theory and a demo. What I could do is: Cut the theory by a few minutes, then do a demo with vagrant init, vagrant up and vagrant ssh.
From their you could take over, showing a more complex setup with provisioning going on, distributed systems or whatever you like. I'd love to see distribution especially as I only work with one box at a time and never tried setting up a more complex system.

that sounds great.
FYI, I was going to use http://www.ansible.com/home to provision the boxes.
Maybe I will spend a couple minutes of my demo with an intro to that.
Or maybe we need a third person to do an ansible talk :P

Ansible is great, but I don't use it for vagrant. I like it for setup of cloud machines because I don't need anything than my local ansible to get startet (Actually, I had a vagrant box with ansible installed and the playbooks to set up my boxes at hetzner and Digital Ocean). With chef, I'd need a server or get the cookbooks in there or whatever.

For vagrant, I use chef as it combines easy setup for most things and the possibility to do even the most complex things without workarounds.

I moved from chef to ansible because ansible just feels right to me. Lots of ceremony with chef (and chef server - yikes!) way more features than I need for one to a few servers.
I also don't like to have vagrant provision for me because their provisioning API was another level of confusion between me and chef.
I will send you a link when i have my repo up so you can see what I mean. The only thing I miss in ansible is a way to specify a non-standard ssh-config file. Being able to keep my ssh config in my ansible repo would be awesome.