diff options
author | Bartosz Zurkowski <b.zurkowski@samsung.com> | 2019-03-21 08:57:59 +0100 |
---|---|---|
committer | Bartosz Zurkowski <b.zurkowski@samsung.com> | 2019-03-21 13:07:09 +0100 |
commit | ddafb0e40dc1c2491df35b4eca604309e185351e (patch) | |
tree | 4e7c8ac9815c27a1b42808e051994c10a8ec88ba /playbooks | |
parent | 7a7a08e41ac8038f9c5df187a0421d46f416abc0 (diff) | |
download | trove-ddafb0e40dc1c2491df35b4eca604309e185351e.tar.gz |
Share networks created by Trove Devstack plugin
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>
Diffstat (limited to 'playbooks')
0 files changed, 0 insertions, 0 deletions