change from Dell email to ongoing email
Merge pull request #164 from cloudedge/emailfix

change from Dell email to ongoing email
add title
add no ISOs info
Zap the local copy of the IPMI cookbook
Let network ranges have their own conduits.

We want to be able to create a BMC network that has an admin range to
let the admin node be issued an IP in the same subnet that the BMCs will
live on.  The easiest way to facilitate that is to make the BMC network
live on the BMC conduit by default, but have the admin range in that
network live on one of the host interfaces.
Have production.sh create the BMC network
Add ability to grab addresses by range as well as by net.

Since it is possible for address ranges to have their own conduit
settings, it is a good idea for us to let the nethelper code we inject
into the Chef node object be able to use it.
Add special-case logic to node to handle "admin".

It is rather useful to be able to refer to the admin node using an
easy-to-remember name.  "admin" is nice.

This lets API calls to use "admin" to refer to the admin node without
hardcoding a name or a node ID.
Fix typo in api_helper.rb
Fix up nethelper.rb to add exact address fetching.
Add ubuntu 14.04 support
Add squid to the list of required packages
Merge pull request #162 from VictorLowther/let-network-ranges-have-conduits

Let network ranges have conduits
Merge pull request #165 from cloudedge/issue160

Base function for "Get Ready" UI screen from #163 WIP
Add a Power framework for Nodes.

Now that the hardware workload can detect and configure IPMI
controllers, we need a little framework to use them.

* Add a Power class that anything that can control power states on a
  node should subclass and use. This class (and not its subclasses!) is
  the only one that the framework interacts with.
* Add a Power::SSH class to the core, it will be in charge of handling
  OS level reboots.
* Add a power method to the Node object, and arrange for it to use the
  Power class.
* Remove the dedicated reboot method from the Node class.
* Add API and CLI support for the Power methods.
Redirect when we retry a noderole in the UI
Merge pull request #168 from VictorLowther/fix-retry-in-ui

+2 Redirect when we retry a noderole in the UI
Fix how we were creating repo data.

The Chef recipes that were creating the repository information that the
rest of Crowbar was using to install packages was making some nasty
assumptions:

* It assumed that the recipe was running on the same node that the admin
  node was on.
* It assumed that it could find barclamp metadata by looking at the
  right location on the filesystem.

Both of these assumptions violated a pretty strict seperation of
concerns between the Crowbar framework and the Chef recipes.  To resolve
that, we now save all the barclamp metadata in the database at barclamp
information time, and pass that information to the provisioner via the
appropriate role sysdata.
Update docker-admin.md