Generalize deployment tests

I generalized the deployment tests by removing all of the hard coded node names, ports, and nics, and instead imported them from a JSON file.  The JSON file's name is defined in deployment.cfg, and the file is used to populate information about the environment that the deployment tests will be run in.
The idea was that depending on the setup, there will be a varying number of nodes.  If a particular setup does not have enough nodes, then don't perform tests that require that many nodes. Thoughts?