4138: Prepare Node Manager GCE driver for production.
authorBrett Smith <brett@curoverse.com>
Mon, 16 Feb 2015 16:06:41 +0000 (11:06 -0500)
committerBrett Smith <brett@curoverse.com>
Tue, 17 Feb 2015 22:49:24 +0000 (17:49 -0500)
commitd6d290bfc01d90d160cecf72d86aff40d7f63f3f
tree350322be90128536e5125fb047edc7693d1f7a7d
parentd32bbed004b76333c3e72e6c1f97dcde88e11edd
4138: Prepare Node Manager GCE driver for production.

* Set node metadata in more appropriate places.
* Bridge more differences between GCE and EC2, like the fact that
  sizes are listed for each location they're available, and GCE
  doesn't provide node boot times.
* Use more infrastructure from BaseComputeNodeDriver to reduce code
  duplication.
* Load as many objects as possible at initialization time, to reduce
  API overhead of creating nodes.
services/nodemanager/arvnodeman/computenode/__init__.py
services/nodemanager/arvnodeman/computenode/driver/gce.py
services/nodemanager/doc/gce.example.cfg
services/nodemanager/tests/test_computenode_driver_gce.py
services/nodemanager/tests/testutil.py