fix column name for relationship between chef_cmdb and conn_info
add description & order for servers in the proposal
more progress towards talking to an off server chef server
1) cmdb chef & conn info created in the db when proposal committed
2) start working on (WIP) attempts to monkeypatch the REST chef api to feed it the key from the db.
chef makes it hard... each access path (query, node and databag) seems to be doing something slightly different w/ regards to the way they interact with the REST api client)
fix typo
better monkeypatch for REST, replace the authenticator for all cases, as long as we've been initialized
preliminary docs
new layout
Merge pull request #8 from cloudedge/pull-req-master-8fd3f586f8e29b7bf0af886ccc15be0e9c3290e1

Merged by devtool for cloudedge
Epic rename of cmdb to jig
Merge pull request #9 from VictorLowther/pull-req-master-ca715c91ecfe7b42a192c575f9a6289aeb4c9007

Merged by devtool for VictorLowther
merge with jig rename
add install_action directive
move default chef client key to test/fixtures
Use expand_path to allow paths to be specified with ~.
(couldn't find something that allows allows ENV variables to be used, which would have been nicer)
updates to have jig_spec test working with latest code:

 * bit more jig rename changes
 * clean up the replace authenticator - just call a simple method.

still working on creating the default chef proposal automatically in dev env.
jigchef test working both  with and without conn info
Merge pull request #11 from aabes/pull-req-master-9945cd360a8663f448c4e229cf377825801a3f6d

Chef barclamp - install key, conn info and friends [2/2]
update to install actions
Merge pull request #12 from aabes/pull-req-master-62e31e1f5aff1d3c82c9d2a90e03538aab1f148c

update to new layout for install actions [1/1]
Make sure we don't get confused by someone else having created /opt/dell.

Instead, check to be certian that we are in fact an admin node before creating
a new client for ourselves.