All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hu <robert.hu@vmm.sh.intel.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Hu, Robert" <robert.hu@intel.com>,
	"Pang, LongtaoX" <longtaox.pang@intel.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [OSSTEST Nested PATCH v8 6/7] Compose the main recipe of nested test job
Date: Fri, 24 Apr 2015 14:31:48 +0800	[thread overview]
Message-ID: <1429857108.31307.53.camel@localhost> (raw)
In-Reply-To: <21816.53761.60014.705124@mariner.uk.xensource.com>

On Thu, 2015-04-23 at 12:05 +0100, Ian Jackson wrote:
> Pang, LongtaoX writes ("RE: [Xen-devel] [OSSTEST Nested PATCH v8 6/7] Compose the main recipe of nested test job"):
> > Ian Campbell [mailto:ian.campbell@citrix.com]:
> > > The arguments passed to ts-* in sg-run-job should _always_ be just a
> > > bare indent. The ident=foo thing is a special case for standalone mode.
> > > 
> > Do you means that the parameter passed to ts-* in sg-run-job should _always_ be just a bare ident?
> 
> Yes, that's what Ian means.
> 
> > If yes. I think it needs to pass l1's '$gn' which is not a bare ident to 'ts-debian-hvm-install' for installing L1 guest VM, since the default '$gn ||= 'debianhvm' if no other '$gn' was passed to this script, but for nested job we expect a different '$gn' from 'debianhvm', such as 'nestedl1'. So it need to pass 'host' and 'nestedl1' to  'ts-debian-hvm-install' script. 
> > +    run-ts . = ts-debian-hvm-install + host + nestedl1
> 
> Indeed.
> 
> > For 'ts-nested-setup' script, it need to call 'ts_get_host_guest'
> > which need two parameters 'host' and 'nestedl1' to get $l0 and $l1
> > scope, so it also need to pass 'nestedl1' to this script.
> 
> Yes.
> 
> > For ' ts-guest-destroy', it also need two parameters of 'host' and 'nestedl1' which is L1's '$gn'.
> 
> If you're intending to destroy the l1, then yes.  If you want to
> destroy theh l2 then you need to pass `nestedl1' and whatever the L2
> guest name/ident is.
Here comes a common issue we need to settle down:
To not break the principle that we shall only pass in ident in recipe,
we shall either
1. for l1 and l2, identical their ident/name/hostname, make this a
principle as well. This shall avoid much complex design but adding one
additional rule to bear in mind.
2. setup $ident --> $name mapping somewhere at the beginning (either
alloc host or make flight, you name it, but somewhere).

I prefer Ian C's suggestion, option 1, that why should we differ the
ident and name for l1 and l2.
> 
> Ian.

  reply	other threads:[~2015-04-24  6:31 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 21:19 [OSSTEST Nested PATCH v8 0/7] Introduction of netsted HVM test job longtao.pang
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 1/7] parsing grub which has 'submenu' primitive longtao.pang
2015-04-21 10:12   ` Ian Campbell
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 2/7] Changes to support '/boot' leading paths of kernel, xen, in grub longtao.pang
2015-04-21 10:13   ` Ian Campbell
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 3/7] Edit some APIs in TestSupport.pm for nested test longtao.pang
2015-04-21 10:19   ` Ian Campbell
2015-04-21 12:33     ` Ian Jackson
2015-04-21 12:53       ` Ian Campbell
2015-04-21 13:28         ` Ian Jackson
2015-04-21 13:41           ` Ian Campbell
2015-04-21 14:30             ` Ian Jackson
2015-04-21 14:43               ` Ian Campbell
2015-04-22  8:25                 ` Pang, LongtaoX
2015-04-22  9:48                   ` Ian Campbell
2015-04-22 12:50                     ` Ian Jackson
2015-04-23  0:34                       ` Hu, Robert
2015-04-27  9:36                         ` Robert Hu
2015-04-28  7:41                           ` Ian Campbell
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 4/7] Changes on test step of Debian hvm guest install longtao.pang
2015-04-21 10:28   ` Ian Campbell
2015-04-23  5:59     ` Robert Hu
2015-04-23  6:52       ` Ian Campbell
2015-04-23 10:43         ` Hu, Robert
2015-04-23 12:04           ` Ian Campbell
2015-04-23 11:07         ` Ian Jackson
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 5/7] Add new script to customize nested test configuration longtao.pang
2015-04-21 10:40   ` Ian Campbell
2015-04-22  8:35     ` Pang, LongtaoX
2015-04-22  9:56       ` Ian Campbell
2015-04-23  9:38         ` Robert Hu
2015-04-23 11:30           ` Ian Campbell
2015-04-23 13:05             ` Ian Campbell
2015-04-24  8:45             ` Pang, LongtaoX
2015-04-28  7:39               ` Ian Campbell
2015-04-23  7:27     ` Pang, LongtaoX
2015-04-23 11:35       ` Ian Campbell
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 6/7] Compose the main recipe of nested test job longtao.pang
2015-04-21 10:48   ` Ian Campbell
2015-04-22  8:38     ` Pang, LongtaoX
2015-04-22 11:04       ` Ian Campbell
2015-04-22 11:23         ` Ian Campbell
2015-04-23  8:08           ` Pang, LongtaoX
2015-04-23 11:05             ` Ian Jackson
2015-04-24  6:31               ` Robert Hu [this message]
2015-04-23 10:49           ` Robert Hu
2015-04-13 21:19 ` [OSSTEST Nested PATCH v8 7/7] Add test job for nest test case longtao.pang
2015-04-21 10:51   ` 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=1429857108.31307.53.camel@localhost \
    --to=robert.hu@vmm.sh.intel.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=longtaox.pang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.