Bootstrapping the Admin Node, Part n of m [4/5]

This pull request series allows Crowbar to get further along with
bootstrapping the admin node.

  * The chef barclamp has been refactored to build run lists that
    include all the node-local prerequisites for any given node.  More
    thought is needed here -- we will probably wind up having to
    maintain a real fully-fleshed out run list per node.
  * Attrib handling per node role has been made a little more
    fine-grained.  Specifically, we now have two outbound data
    locations, one for user-defined data and another for data that the
    framework manages.  The former is only editable when a noderole is
    in proposed state, while the latter can be changed by the Crowbar
    framework at any time and should not be editable by the user at
    all.  Wall data still exists as the only inbound data path from a
    Jig run.
  * The logic used to decide what roles need to be populated on a
  freshly-discovered node has been made more accurate.
  * The admin node now deploys a DNS server as part of its initial
    bootstrap.  The DNS server is not properly configured as of yet.



 chef/cookbooks/utils/README.rdoc                   |    8 --
 chef/cookbooks/utils/metadata.rb                   |    6 --
 chef/cookbooks/utils/providers/line.rb             |  106 --------------------
 chef/cookbooks/utils/recipes/default.rb            |   28 ------
 chef/cookbooks/utils/resources/line.rb             |   23 -----
 .../barclamp_chef/app/models/barclamp_chef/jig.rb  |   18 +++-
 crowbar_engine/barclamp_chef/lib/barclamp_chef.rb  |    5 +-
 7 files changed, 19 insertions(+), 175 deletions(-)

Crowbar-Pull-ID: dda46b22e196800cd48f79a273d87621c71cbbfe

Crowbar-Release: development