Re: [Xen-devel] [OSSTEST PATCH v8 0/3] Have OpenStack tested on top of xen's master and libvirt's master.

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Anthony PERARD writes ("[OSSTEST PATCH v8 0/3] Have OpenStack tested on top of 
xen's master and libvirt's master."):
> I have looked into getting OpenStack been tested on the latest Xen via
> osstest.
> Run of AP_FETCH_PLACEHOLDERS=y ./standalone-generate-dump-flight-runvars on
> master (5d88d6299618f6bce204d82579392a76028fb8cd) vs this patch series:

Thanks.  I'm afraid that has prompted some nontrivial questions and
comments:

The way you have done things, the test-amd64-amd64-devstack job will
run on a Xen dom0 installed by osstest.  Does this devstack test
expect to be run in such a context ?

It's quite anomalous that your test-* job is doing all the cloning and
building of things.  This is not a huge problem; there are only a
handful of places in osstest that have any "improper" knowledge of job
names, and for their purposes I think this is probably a "test" rather
than a "build".  (In particular, ts-hosts-allocate-Executive has some
different ideas about what would be a good host for a build.)

Most software, though, has a separate build and execute.  Maybe
tempest doesn't do that, in which case fine.  (Sorry if I have asked
this question before...)

+openstack-nova             test-amd64-amd64-devstack     all_host_suite        
  jessie
+openstack-nova             test-amd64-amd64-devstack     all_hostflags         
  arch-amd64,arch-xen-amd64,suite-jessie,purpose-test

This does not request a host capable of HVM.  Is that right ?
(In practice all our x86 hosts are capable of HVM so this may not
matter.)

+openstack-nova             test-amd64-amd64-devstack     revision_cinder
+openstack-nova             test-amd64-amd64-devstack     revision_devstack
+openstack-nova             test-amd64-amd64-devstack     revision_glance
+openstack-nova             test-amd64-amd64-devstack     revision_keystone
+openstack-nova             test-amd64-amd64-devstack     revision_nova         
  ap-fetch-version:openstack-nova
+openstack-nova             test-amd64-amd64-devstack     revision_requirements
+openstack-nova             test-amd64-amd64-devstack     revision_tempest

These openstack components ought not to live in the global namespace.
I would like you to prefix all of these runvars with `openstack'.  So,
revision_openstack_cinder etc.  Cf revison_rumprun_something.

Thinking about it, I think you should probably do the same with the
corresponding shell environment variables.

+openstack-nova             test-amd64-amd64-devstack     toolstack             
  libvirt
+openstack-nova             test-amd64-amd64-devstack     tree_cinder           
  git://git.openstack.org/openstack/cinder.git
+openstack-nova             test-amd64-amd64-devstack     tree_devstack         
  git://git.openstack.org/openstack-dev/devstack.git
+openstack-nova             test-amd64-amd64-devstack     tree_glance           
  git://git.openstack.org/openstack/glance.git
+openstack-nova             test-amd64-amd64-devstack     tree_keystone         
  git://git.openstack.org/openstack/keystone.git
+openstack-nova             test-amd64-amd64-devstack     tree_nova             
  git://git.openstack.org/openstack/nova.git
+openstack-nova             test-amd64-amd64-devstack     tree_requirements     
  git://git.openstack.org/openstack/requirements.git
+openstack-nova             test-amd64-amd64-devstack     tree_tempest          
  git://git.openstack.org/openstack/tempest.git

I notice that you have not created an openstack job in the other
branches.  Is that deliberate ?

Why no ARM jobs ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel