neutron network and availability zone information cannot be provided in cluster create call

[Saurabh Surana]

While creating a single instance in trove user can specify:
1. Neutron network - to be associated with an instance, so that a port form that network is attached to the instance
2. Availability zone - which can be used to provision an instance in a particular availability zone

Both these parameters cannot be provided on a cluster create API call

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/179443

[Saurabh Surana (saurabh-surana)]

Instances in cluster should be allowed to be :
1. provisioned in multiple different availability zones (provides the fail over/HA capabilities for the clusters)
2. provisioned with multiple different neutron network (provides ability to provision cluster instances in application specific networks)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/179443
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=c4946145cc75fe4eb540afba02d2ab2d78be2b87
Submitter: Jenkins
Branch: master

commit c4946145cc75fe4eb540afba02d2ab2d78be2b87
Author: Saurabh Surana <email address hidden>
Date: Fri May 1 10:39:22 2015 -0700

    accepting network and availability zone for instances in cluster

    Standalone instance create call in trove already accepts neutron networks
    and availability zone information.

    In the similar manner, instances which are part of the cluster can
    now be supplied with a specific neutron network information and
    availability zone.

    This review is addressing the fix only for vertica datastore.

    Partial-Bug: #1447350
    Change-Id: I5a1e9300dd0a16395769acda672943899f9ad0ad