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 ("Re: [OSSTEST PATCH v8 0/3] Have OpenStack tested on top 
of xen's master and libvirt's master."):
> On Mon, Dec 12, 2016 at 04:51:47PM +0000, Ian Jackson wrote:
> > 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 ?
> 
> In a Xen dom0? Yes.

Right, OK, good.

> Well, OpenStack been all python, there is nothing to build. So devstack
> is mostly doing configuration and start services, I think.

Ah.  OK.

> > 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.
> 
> Will do.

Thanks.  Sorry for not noticing this sooner.

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

OK, fine.

> > Why no ARM jobs ?
> 
> I don't know if it is going to work, probably not. There probably going
> to be missing packages (dependencies) and it maybe not going to be able
> to start a guest, if devstart does not get the right guest image.

I'm not sure these are good reasons not to try to support ARM.

A failing test, with a promise that the system would detect
regressions if the test were made to pass, is a good incentive :-).

Ian.

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