JioCloud/jiocloud_puppet_builder — pull request #25 by hkumarmk (2014-08-27 10:19:20+00:00)
Title: Added fabric.yaml to send configurations to fab

The idea is to separate resource spawner (using spawn_resources.sh)
and deployment (fab) completely so both of them can run
independantly if required.

1. Changed spawn_resources.sh
1a. SetupHiera function has changed
Added more hiera configurations
changed the yaml file to fabric.yaml
this file will be configuration to fab
1b. Added all puppet code under $tmp/jiocloud_puppet_builder
this was there before, but somewhere this got reverted
2. Changed fabfile.py
2a. Added decorator @task so that only subset of functions
are set as fab tasks
2b. Replaced the code to define fab roles to use fabric.yaml
instead of argument
2c. Added fabConfig task to read fabric.yaml and configure fabric
It also generate user.yaml using genUserHiera fucntion
2d. added genUserHiera function to generate user.yaml
2e. Changed initiateSetup function
copy fabric.yaml to cloud lb node,
use env.hosts instead of env.host - env.hosts is used
as hosts variable in fab.
changed inner fab call to use fabconfig