diff mbox

[OSSTEST,v11,10/20] ts-openstack-deploy: Switch to Neutron for network

Message ID 20170616175704.7832-11-anthony.perard@citrix.com (mailing list archive)
State New, archived
Headers show

Commit Message

Anthony PERARD June 16, 2017, 5:56 p.m. UTC
nova-network is not supported anymore and Neutron is the default.

Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
 ap-common           | 3 ++-
 make-flight         | 2 +-
 ts-openstack-deploy | 8 +-------
 3 files changed, 4 insertions(+), 9 deletions(-)

Comments

Ian Jackson June 23, 2017, 1:41 p.m. UTC | #1
Anthony PERARD writes ("[OSSTEST PATCH v11 10/20] ts-openstack-deploy: Switch to Neutron for network"):
> nova-network is not supported anymore and Neutron is the default.

Is this kind of thing going to be common ?  If so then it will be a
constant maintenance burden in osstest.

Is there some way we can get the list of components out of the
top-level tree ?

Ian.
Anthony PERARD June 23, 2017, 2:10 p.m. UTC | #2
On Fri, Jun 23, 2017 at 02:41:02PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[OSSTEST PATCH v11 10/20] ts-openstack-deploy: Switch to Neutron for network"):
> > nova-network is not supported anymore and Neutron is the default.
> 
> Is this kind of thing going to be common ?  If so then it will be a
> constant maintenance burden in osstest.

No, that's not common. I don't think it's going to happen again anytime
soon.

> Is there some way we can get the list of components out of the
> top-level tree ?

I don't know if there is a simple way to get this list. And if we start
looking at the list of all OpenStack git trees, there are hundreds of
them.
Ian Jackson June 23, 2017, 2:18 p.m. UTC | #3
Anthony PERARD writes ("Re: [OSSTEST PATCH v11 10/20] ts-openstack-deploy: Switch to Neutron for network"):
> On Fri, Jun 23, 2017 at 02:41:02PM +0100, Ian Jackson wrote:
> > Is this kind of thing going to be common ?  If so then it will be a
> > constant maintenance burden in osstest.
> 
> No, that's not common. I don't think it's going to happen again anytime
> soon.

OK, fine.

> > Is there some way we can get the list of components out of the
> > top-level tree ?
> 
> I don't know if there is a simple way to get this list. And if we start
> looking at the list of all OpenStack git trees, there are hundreds of
> them.

Yow.  Let's not.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
diff mbox

Patch

diff --git a/ap-common b/ap-common
index 7e84f15..adfdc11 100644
--- a/ap-common
+++ b/ap-common
@@ -55,7 +55,8 @@ 
 : ${BASE_TREE_OVMF:=git://xenbits.xen.org/osstest/ovmf.git}
 
 define_openstack_trees() {
-    local openstack_trees=(cinder glance keystone nova requirements tempest)
+    local openstack_trees=(cinder glance keystone neutron nova requirements
+        tempest)
     local tree
     local url
 
diff --git a/make-flight b/make-flight
index 3235cca..ff4f17e 100755
--- a/make-flight
+++ b/make-flight
@@ -696,7 +696,7 @@  do_examine_one () {
 
 do_openstack_tests () {
     local xsms=$(xenbranch_xsm_variants)
-    local openstack_trees=(cinder devstack glance keystone nova
+    local openstack_trees=(cinder devstack glance keystone neutron nova
         requirements tempest)
 
     if [ $branch != openstack-nova ]; then
diff --git a/ts-openstack-deploy b/ts-openstack-deploy
index 1349009..2107760 100755
--- a/ts-openstack-deploy
+++ b/ts-openstack-deploy
@@ -35,6 +35,7 @@  sub checkout () {
     build_clone($ho, 'openstack_devstack',     $builddir, 'devstack');
     build_clone($ho, 'openstack_glance',       $builddir, 'glance');
     build_clone($ho, 'openstack_keystone',     $builddir, 'keystone');
+    build_clone($ho, 'openstack_neutron',      $builddir, 'neutron');
     build_clone($ho, 'openstack_nova',         $builddir, 'nova');
     build_clone($ho, 'openstack_requirements', $builddir, 'requirements');
     build_clone($ho, 'openstack_tempest',      $builddir, 'tempest');
@@ -63,13 +64,6 @@  LIBVIRT_TYPE=xen
 disable_service horizon
 disable_service n-novnc
 disable_service dstat
-# Disable neutron and switch back to nova-network
-disable_service q-svc
-disable_service q-dhcp
-disable_service q-meta
-disable_service q-agt
-disable_service q-l3
-enable_service n-net
 USE_SYSTEMD=False
 # To keep systemd off, we need to enable use of screen
 USE_SCREEN=True