Re: [Xen-devel] [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [OSSTEST Nested PATCH v11 6/7] Compose the main 
recipe of nested test job"):
> I'll leave it to Ian to suggest a solution since it will no doubt
> involve some tcl plumbing (I'd be inclined to record 'hosts which are
> actually guests' somewhere and have the infra clean them up
> automatically after doing leak check and log collection).

Thinking "aloud":

The things we want to happen at the end of the job are:
  * leak check on the l1
 !* logs capture on the l1 (might involve "power cycle")
  * destruction of the l1 on l0
  * leak check on l0
 !* logs capture on l0

The items marked ! should happen even in case of failure.

This is going to be quite fiddly to do in a generic way.  But on the
other hand, doing it in a generic way would avoid writing an explicit
error handler in the l1 test case code, and replicating the "per-host
operations".

> I was thinking more along the lines of creating Osstest/PDU/guest.pm
> with the appropriate methods calling out to toolstack($l0)->foo, setting
> $ho->{Power} = 'guest $l1guestname' somewhere and allowing
> power_cycle_host_setup to do it's thing.

Yes, that's what I meant.

Ian.

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