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.
I think two nodes is a sensible thing to require. At the very least the
user should get prominent warning that the test isn't being run -- we
don't want to make that kind of thing easy to miss -- but I think the
right behavior is just to fail. The point of the deployment tests is
that you need an actual deployment to run them, assuming at least too
nodes is more than reasonable.

-Ian

Quoting Ryan Abouzahra (2014-08-26 17:19:13)
>    In tests/deployment/deployment.py:
> >                      return network
> >              return []
> >
> > -        def create_networks():
> > -            api.group_create('acme-code')
> > -            api.project_create('anvil-nextgen', 'acme-code')
> > +        def create_networks(nodes):
> > +            # At least 2 nodes with 1 nic each are required for this test
> > +            if len(nodes) < 2:
> > +                return
> 
>    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?
> 
>    --
>    Reply to this email directly or [1]view it on GitHub.
> 
> References
> 
>    1. https://github.com/CCI-MOC/haas/pull/222/files#r16743303