xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Hu, Robert" <robert.hu@intel.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job
Date: Tue, 1 Sep 2015 15:58:51 +0100	[thread overview]
Message-ID: <1441119531.26292.48.camel@citrix.com> (raw)
In-Reply-To: <21989.47387.157970.104150@mariner.uk.xensource.com>

On Tue, 2015-09-01 at 15:41 +0100, Ian Jackson wrote:
> Hi Robert.  Sorry I haven't had a chance to look at your whole v11
> series properly yet.  But I will reply here:
> 
> Ian Campbell writes ("Re: [OSSTEST Nested PATCH v11 6/7] Compose the main 
> recipe of nested test job"):
> > Then on power operation the appropriate method each object is called in
> > turn (so you can call multiple modules if needed by the host).
> 
> Ian's explanation is right.
> 
> > > So how shall I assign $ho->{Power} method? by statically through 
> > > config
> > > file?
> > > or some generic way automatically identify $host is some guest, 
> > > therefore
> > > assign 'guest' to $ho->{Power}?
> > > Would you give me some idea? thanks.
> > 
> > I'm not sure. Something in selecthost would need to know somehow that 
> > the
> > host being requested was actually an L1 guest.
> 
> I think this would be correct.
> 
> > Ian, any ideas?
> 
> I was expecting there to be a runvar which would for an L1 guest give
> the ident of its host.  ts-nested-setup would set this runvar and
> selecthost would look at it.
> 
> There are various possible exact syntaxes but I think the best one is
> probably that the runvar which ordinarily gives the name of a real
> host instead contains the containing host name and the L1 guest name.
> 
> So if you do
>   ./ts-nested-setup l0_host l1
> then you get a runvar `l1' with value `l0_host:l1'.
> 
> selecthost would see the colon, and set $ho->{Host} to `l0_host', so
> that get_target_property's recursion into containing hosts works
> properly.
> 
> selecthost would also be able to see that $ho->{Host} being set meant
> it was a nested guest, and that therefore power operations should be
> done by running toolstack operations on the host.  (Rather than
> looking up a host property.)
> 
> It also needs to arrange that for an L1 (well, anything with
> $ho->{Host} aka the _nestedhost runvar),

ITYM:         aka a host runvar containing a colon),

Ian.

  reply	other threads:[~2015-09-01 14:58 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  9:08 [OSSTEST Nested PATCH v11 0/7] Introduction of netsted HVM test job longtao.pang
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 1/7] grub: remove patch to disable submenu from 20_linux_xen overlay longtao.pang
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 2/7] Parsing grub which has 'submenu' primitive longtao.pang
2015-06-10 13:30   ` Ian Jackson
2015-06-11  3:17     ` Robert Hu
2015-06-11  8:37       ` Ian Campbell
2015-06-11  9:01         ` Robert Hu
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 3/7] Changes to support '/boot' leading paths of kernel, xen, in grub longtao.pang
2015-06-10 13:31   ` Ian Jackson
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 4/7] Changes on test step of Debian hvm guest install longtao.pang
2015-06-08 10:31   ` Ian Campbell
2015-06-09  5:29     ` Pang, LongtaoX
2015-06-09  8:07       ` Ian Campbell
2015-06-09  9:10         ` Pang, LongtaoX
2015-06-10 13:41   ` Ian Jackson
2015-06-11  6:15     ` Pang, LongtaoX
2015-06-11 15:08       ` Ian Jackson
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 5/7] Add new script to customize nested test configuration longtao.pang
2015-06-10 13:58   ` Ian Jackson
2015-06-11  6:19     ` Pang, LongtaoX
2015-06-11 15:14       ` Ian Jackson
2015-06-12  3:46         ` Pang, LongtaoX
2015-06-12  8:42           ` Ian Campbell
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job longtao.pang
2015-06-10 15:42   ` Ian Jackson
2015-06-11  7:41     ` Pang, LongtaoX
2015-06-11  8:40       ` Ian Campbell
2015-06-11  9:52         ` Pang, LongtaoX
2015-06-11 10:37           ` Ian Campbell
2015-06-11 15:19       ` Ian Jackson
2015-06-12  3:42         ` Robert Hu
2015-06-12  8:44           ` Ian Campbell
2015-06-12  9:00             ` Robert Hu
2015-06-12  9:15               ` Ian Campbell
2015-06-12  3:58         ` Pang, LongtaoX
2015-06-12 15:27           ` Ian Jackson
2015-06-12 15:28             ` Ian Jackson
2015-06-14 12:52               ` Robert Hu
2015-06-14 12:51             ` Robert Hu
2015-06-15  9:08               ` Ian Campbell
2015-06-17  8:54                 ` Pang, LongtaoX
2015-06-17  9:35                   ` Ian Campbell
2015-06-17 11:00                     ` Pang, LongtaoX
2015-06-17 11:48                       ` Ian Campbell
2015-06-18  9:16                         ` Pang, LongtaoX
2015-06-18  9:22                           ` Ian Campbell
2015-06-18  9:26                             ` Pang, LongtaoX
2015-06-17 11:31                     ` Ian Jackson
2015-06-25  8:21                     ` Pang, LongtaoX
2015-06-25  9:33                       ` Ian Campbell
2015-06-25 10:21                       ` Ian Jackson
2015-08-18  6:46                         ` Hu, Robert
2015-09-01 13:51                           ` Ian Campbell
2015-09-01 14:41                             ` Ian Jackson
2015-09-01 14:58                               ` Ian Campbell [this message]
2015-09-11  1:39                               ` Hu, Robert
2015-09-11 14:03                                 ` Ian Jackson
2015-09-11  1:39                             ` Hu, Robert
2015-06-17  9:08                 ` Pang, LongtaoX
2015-06-19  3:03             ` Pang, LongtaoX
2015-06-19 12:16               ` Ian Jackson
2015-06-19 12:17                 ` Ian Jackson
2015-06-30 16:36                   ` [OSSTEST RFC PATCH 0/4] Nested job execution infrastructure Ian Jackson
2015-06-30 16:36                     ` [OSSTEST PATCH 1/4] Tcl: Provide lunappend Ian Jackson
2015-06-30 16:36                     ` [OSSTEST PATCH 2/4] sg-run-job: Declare Tcl (for the benefit of Emacs) Ian Jackson
2015-06-30 16:36                     ` [OSSTEST PATCH 3/4] sg-run-job: Break out per-host-prep and per-host-finish Ian Jackson
2015-07-28  5:39                       ` Robert Hu
2015-07-28 15:15                         ` Ian Jackson
2015-07-29  8:13                           ` Robert Hu
2015-06-30 16:36                     ` [OSSTEST PATCH 4/4] sg-run-job: Provide infrastructure for layers of nesting Ian Jackson
2015-07-28  6:47                       ` Robert Hu
2015-07-28 15:13                         ` Ian Jackson
2015-06-30 16:56                     ` [OSSTEST RFC PATCH 0/4] Nested job execution infrastructure Ian Jackson
2015-07-01  1:56                     ` Robert Hu
2015-07-02 17:14                       ` Ian Jackson
2015-07-28  5:36                     ` Robert Hu
2015-05-26  9:08 ` [OSSTEST Nested PATCH v11 7/7] Add test job for nest test case longtao.pang
2015-06-10 15:46   ` Ian Jackson
2015-06-11  6:28     ` Pang, LongtaoX
2015-06-11 15:16       ` Ian Jackson
2015-05-26 11:34 ` [OSSTEST Nested PATCH v11 0/7] Introduction of netsted HVM test job Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1441119531.26292.48.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=robert.hu@intel.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).