Experimental fabric/cuisine support

[Sef Kloninger]

Hi everyone -

A large and important contribution from David Glance at UWA just landed on master, see PR #2415.  David has written an alternative set of setup scripts.  Instead of Chef, he's using fabric and cuisine.  In addition it has some support for local development using vagrant.  He has written written up Fabric/Cuisine and Vagrant instructions on the wiki.

It's important that everyone here knows that THIS IS AN EXPERIMENTAL FEATURE.  It hasn't been tested by the Class2Go core team.  Our production repo still is configured and installed via the chef scripts.  Fabric is part of the main repo so other developers can try it out, test, contribute, and evaluate.  It's good to experiment with such things, and it's convenient that we can do so in the main repo when something doesn't interfere with the rest of the project.

Will Class2Go overall move from Chef to Fabric/Cuisine?  I don't know.  It seems that there is pretty good support for chef-solo in the wider PAAS space.  But I do like that this is all Python, and it seems clean.  I'd love to hear what people think.

If you have comments or feedback this forum is a good place to post your thoughts.  

Thanks David!

- Sef

[Johannes Tynes]

excellent, will test this out as part of setting up recovery / redundancy procedures

also vagrant will definitely make it easier to do dev on multiple boxes

[Anurag Sahay]

Fabric Support is relatively simpler and more straightforward to use than Chef.
Was able to use and check out most of it and it works pretty well straight out of the box.
Thanks David.