Allow deployed nodes to run chef-client once and stop. [2/3]

This pull request series does the following:

 * Have the node create and destroy actions in the nodes controller also create and destroy the appropriate Chef nodes and clients. This code should vanish and be replaced by the appropriate jig interactions the moment they are written.
 * Fix up the test framework to use a selection of different host names for the admin node it deploys, rather than just using admin.smoke.test.  This will help catch any hardcoded dependencies on specific hostnames in the future.
 * Have the freshly-booted compute node create its node object if it did not get passed its fqdn.  This code will not function properly until we have working IP address allocation and enough of the jig in place to rerun the provisioner recipes when the node is detected.


 chef/cookbooks/nfs-server/recipes/default.rb       |    3 +-
 .../nfs-server/templates/default/exports.erb       |    4 +--
 chef/cookbooks/provisioner/recipes/update_nodes.rb |    5 +--
 .../provisioner/templates/default/control.sh.erb   |   38 +++++++++++++++-----
 4 files changed, 36 insertions(+), 14 deletions(-)

Crowbar-Pull-ID: d0402aca3e2d655006401ce1f098566477fa0a97

Crowbar-Release: development