From e03f06c081edc82e5d4ad614cce9a093fc2d1863 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rados=C5=82aw=20Piliszek?= Date: Fri, 20 Mar 2020 14:51:02 +0100 Subject: [PATCH] Do not enforce vxlan in init-runonce The affected command was meant to create a tenant network, so let us really test it this way. Not marking CI, because someone may be using this script. Change-Id: I5abe46948992121a11a36f941d4f8fac1caa92b1 --- tools/init-runonce | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/init-runonce b/tools/init-runonce index 0cb06d6889..dcbb13ae09 100755 --- a/tools/init-runonce +++ b/tools/init-runonce @@ -85,7 +85,7 @@ if [[ $ENABLE_EXT_NET -eq 1 ]]; then --subnet-range ${EXT_NET_CIDR} --gateway ${EXT_NET_GATEWAY} public1-subnet fi -$KOLLA_OPENSTACK_COMMAND network create --provider-network-type vxlan demo-net +$KOLLA_OPENSTACK_COMMAND network create demo-net $KOLLA_OPENSTACK_COMMAND subnet create --subnet-range 10.0.0.0/24 --network demo-net \ --gateway 10.0.0.1 --dns-nameserver 8.8.8.8 demo-subnet