adding BDD file first because that the most awesome thing to do
add route (change from nodes/ to dashboard/)
basic getready page working WITH BDD passing
add placeholder form fields for deployment and network
POST working to create deployment and add nodes
add title
add no ISOs info
complete node grid options
add missing doc model material
add network and range create from POST
refactor network constants into model
change to given so that BDD will automatically use given OR when
refactor to remove config
BDD test validates getready POST adds deployment
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