Skip to content

Commit

Permalink
tox: use the vagrant-libvirt management network
Browse files Browse the repository at this point in the history
Instead of specifying the registry address for each ceph-ansible scenario
on the dedicated public network (which is different) we can use the
vagrant-libvirt management network that is common to all scenarios.

https://github.com/vagrant-libvirt/vagrant-libvirt#management-network

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit 072de56)
  • Loading branch information
dsavineau committed Oct 22, 2020
1 parent eb55440 commit 5406b6f
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions tox.ini
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,7 @@ setenv=
all_daemons: CEPH_ANSIBLE_SCENARIO_PATH = {toxinidir}/ceph-ansible/tests/functional/all_daemons/container
collocation: CEPH_ANSIBLE_SCENARIO_PATH = {toxinidir}/ceph-ansible/tests/functional/collocation/container
lvm_osds: CEPH_ANSIBLE_SCENARIO_PATH = {toxinidir}/ceph-ansible/tests/functional/lvm-osds/container
all_daemons: REGISTRY_ADDRESS = 192.168.17.1:5000
collocation: REGISTRY_ADDRESS = 192.168.15.1:5000
lvm_osds: REGISTRY_ADDRESS = 192.168.39.1:5000
REGISTRY_ADDRESS = 192.168.121.1:5000
CEPH_ANSIBLE_BRANCH = stable-3.2
VAGRANT_PROVIDER = {env:VAGRANT_PROVIDER:libvirt}
CEPH_ANSIBLE_VAGRANT_BOX = centos/atomic-host
Expand Down

0 comments on commit 5406b6f

Please sign in to comment.