All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH OSSTEST v2 6/6] Create a flight to test OpenStack with xen-unstable and libvirt
Date: Tue, 8 Sep 2015 14:14:27 +0100	[thread overview]
Message-ID: <1441718067.24450.94.camel@citrix.com> (raw)
In-Reply-To: <1438880611-13244-7-git-send-email-anthony.perard@citrix.com>

On Thu, 2015-08-06 at 18:03 +0100, Anthony PERARD wrote:
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> ---
>  ap-common            |  9 +++++++++
>  ap-fetch-version     |  4 ++++
>  ap-fetch-version-old |  5 +++++
>  ap-print-url         |  3 +++
>  cri-common           |  1 +
>  make-flight          | 42 +++++++++++++++++++++++++++++++++++++++++-
>  mfi-common           |  5 +++++
>  7 files changed, 68 insertions(+), 1 deletion(-)
> 
> diff --git a/ap-common b/ap-common
> index dfeab9e..40eda02 100644
> --- a/ap-common
> +++ b/ap-common
> @@ -57,6 +57,14 @@
>  : ${PUSH_TREE_OVMF:=$XENBITS:/home/xen/git/osstest/ovmf.git}
>  : ${BASE_TREE_OVMF:=git://xenbits.xen.org/osstest/ovmf.git}
>  
> +: ${TREE_DEVSTACK:=git://git.openstack.org/openstack-dev/devstack.git}
> +:
> ${TREE_OPENSTACK_REQUIREMENTS:=git://git.openstack.org/openstack/requirem
> ents.git}
> +: ${TREE_KEYSTONE:=git://git.openstack.org/openstack/keystone.git}
> +: ${TREE_GLANCE:=git://git.openstack.org/openstack/glance.git}
> +: ${TREE_CINDER:=git://git.openstack.org/openstack/cinder.git}
> +: ${TREE_NOVA:=git://git.openstack.org/openstack/nova.git}
> +: ${TREE_TEMPEST:=git://git.openstack.org/openstack/tempest.git}

Maybe these should all be TREE_OPENSTACK_FOO? And perhaps put git
://git.openstack.org/openstack/ into a variable (like $XENBITS or
$GIT_KERNEL_ORG)

> +
>  : ${TREE_LINUXFIRMWARE:=git://xenbits.xen.org/osstest/linux
> -firmware.git}
>  : ${PUSH_TREE_LINUXFIRMWARE:=$XENBITS:/home/osstest/ext/linux
> -firmware.git}
>  :
> ${UPSTREAM_TREE_LINUXFIRMWARE:=$GIT_KERNEL_ORG/pub/scm/linux/kernel/git/f
> irmware/linux-firmware.git}
> @@ -84,6 +92,7 @@ fi
>  : ${LOCALREV_RUMPUSERXEN:=daily-cron.$branch}
>  : ${LOCALREV_SEABIOS:=daily-cron.$branch}
>  : ${LOCALREV_OVMF:=daily-cron.$branch}
> +: ${LOCALREV_DEVSTACK:=daily-cron.$branch}
>  
>  : ${TREEBASE_LINUX_XCP:=
> http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27}
>  
> diff --git a/ap-fetch-version b/ap-fetch-version
> index 8b41acf..9aba511 100755
> --- a/ap-fetch-version
> +++ b/ap-fetch-version
> @@ -89,6 +89,10 @@ ovmf)
>  	repo_tree_rev_fetch_git ovmf \
>  		$TREE_OVMF_UPSTREAM master $LOCALREV_OVMF
>  	;;
> +openstack)
> +	repo_tree_rev_fetch_git devstack \
> +		$TREE_DEVSTACK master $LOCALREV_DEVSTACK
> +	;;
>  osstest)
>          if [ "x$OSSTEST_USE_HEAD" = "xy" ] ; then
>  	    git update-ref -m "Arranging to test HEAD" \
> diff --git a/ap-fetch-version-old b/ap-fetch-version-old
> index 0b4739b..d12c753 100755
> --- a/ap-fetch-version-old
> +++ b/ap-fetch-version-old
> @@ -31,6 +31,7 @@ select_xenbranch
>  : ${BASE_LOCALREV_RUMPUSERXEN:=daily-cron.$branch.old}
>  : ${BASE_LOCALREV_SEABIOS:=daily-cron.$branch.old}
>  : ${BASE_LOCALREV_OVMF:=daily-cron.$branch.old}
> +: ${BASE_LOCALREV_DEVSTACK:=daily-cron.$branch.old}
>  
>  : ${BASE_TREE_QEMU_UPSTREAM:=${TREE_QEMU_UPSTREAM/\/staging\//\/}}
>  
> @@ -97,6 +98,10 @@ ovmf)
>  	repo_tree_rev_fetch_git ovmf \
>  		$BASE_TREE_OVMF xen-tested-master $BASE_LOCALREV_OVMF
>  	;;
> +openstack)
> +	repo_tree_rev_fetch_git devstack \
> +		$TREE_DEVSTACK master $BASE_LOCALREV_DEVSTACK

This one should be pulling from the gate output on xenbits not from
upstream. See e.g. BASE_TREE_OVMF.

Actually, I think you've missed the ap-push changes needed to populate that
tree, you need this in order to have a baseline.
 
>  if [ x$buildflight = x ]; then
> @@ -101,6 +108,20 @@ job_create_test_filter_callback () {
>          *) return 1;;
>        esac
>        ;;
> +    openstack)
> +      if [ x$toolstack != xlibvirt ] ; then return 1; fi
> +      case "$job" in
> +        test-*-libvirt*) return 1;;
> +      esac
> +      case $xenarch in
> +          amd64) ;;
> +          *) return 1;;
> +      esac
> +      case $dom0arch in
> +          amd64) ;;
> +          *) return 1;;
> +      esac
> +      ;;


Do you not want to only accept *-devstack here and reject everything else?

Otherwise don't you end up with various xl and HVM tests?

Ian.

  reply	other threads:[~2015-09-08 13:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 17:03 [PATCH OSSTEST v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2015-08-06 17:03 ` [PATCH OSSTEST v2 1/6] ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM Anthony PERARD
2015-08-06 17:03 ` [PATCH OSSTEST v2 2/6] ts-kernel-build: Compile CONFIG_CRYPTO_XTS in Anthony PERARD
2015-09-08 11:45   ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 3/6] ts-xen-install: Add dom0_mem runvar to control dom0 memory Anthony PERARD
2015-09-08 11:48   ` Ian Campbell
2015-09-08 12:52     ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 4/6] ts-openstack-devstack: Deploy OpenStack on a host Anthony PERARD
2015-09-08 13:03   ` Ian Campbell
2015-09-08 14:36     ` Ian Jackson
2015-09-25 12:36       ` Anthony PERARD
2015-09-25 12:35     ` Anthony PERARD
2015-09-25 12:45       ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 5/6] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2015-09-08 13:06   ` Ian Campbell
2015-09-25 13:04     ` Anthony PERARD
2015-09-25 13:17       ` Ian Campbell
2015-09-25 13:54         ` Ian Jackson
2015-08-06 17:03 ` [PATCH OSSTEST v2 6/6] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-09-08 13:14   ` Ian Campbell [this message]
2015-09-25 13:10     ` Anthony PERARD
2015-09-09 16:13 ` [PATCH OSSTEST v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master 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=1441718067.24450.94.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@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.