![Bartosz Zurkowski](/assets/img/avatar_default.png)
Trove implies strict network requirements. All Trove instances must be launched in a network that is connected to the management network so that Guest Agents residing in the data plane could communicate with control plane services, e.g. RabbitMQ and Trove Conductor. Trove Devstack plugin creates a management network bound to management physnet (trove-mgmt), as well as tenant network (alt-private) connected to it via a router. Consequently, Trove instances deployed in the tenant network can easily access the management services mentioned above. However, these networks are visible only from the perspective of the tenant that created the networks. Since Tempest does not provide an easy way to create a similar management network, and as such does not enable creating tenant network for Trove instances automatically, this change adds --share flag to networks created by Devstack so that Tempest could reuse them. Change-Id: I8c642ab6150858478c48291a51675ef9d15dafaa Signed-off-by: Bartosz Zurkowski <b.zurkowski@samsung.com>
Enabling Trove in DevStack
To enable Trove in DevStack, perform the following steps:
Note: The python-troveclient is automatically installed. If you need to
control how the client gets installed, set the TROVECLIENT_REPO,
TROVECLIENT_DIR and TROVECLIENT_BRANCH environment variables appropriately.
Download DevStack
export DEVSTACK_DIR=~/devstack
git clone git://git.openstack.org/openstack-dev/devstack.git $DEVSTACK_DIR
Enable the Trove plugin
Enable the plugin by adding the following section to
$DEVSTACK_DIR/local.conf
[[local|localrc]]
enable_plugin trove git://git.openstack.org/openstack/trove
Optionally, a git refspec (branch or tag or commit) may be provided as follows:
[[local|localrc]]
enable_plugin trove git://git.openstack.org/openstack/trove <refspec>
Run the DevStack utility
cd $DEVSTACK_DIR
./stack.sh