All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH v11 20/20] Introduce flight for stable branches of OpenStack
Date: Fri, 23 Jun 2017 17:26:26 +0100	[thread overview]
Message-ID: <20170623162626.GI1702@perard.uk.xensource.com> (raw)
In-Reply-To: <22861.7809.24331.372938@mariner.uk.xensource.com>

On Fri, Jun 23, 2017 at 02:58:25PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[OSSTEST PATCH v11 20/20] Introduce flight for stable branches of OpenStack"):
> > OpenStack have many different repo which should be in sync, so this
> > patch should grab the revisions of the stable branch of every OpenStack
> > tree. Tempest does not have stable branch and should be able to test any
> > OpenStack version.
> 
> I'm afraid I don't understand this patch.
> 
> Partly, I think it needs to be squashed with the original patch
> introducing `openstack-nova' as a branch.  While your series has a
> number of things where a thing is introduced and then later patched,
> and this is largely OK, I think it is too confusing to have a whole
> branch appear and disappear like this (without ever having been
> run for real).

Yes, I can do that.

> > -openstack-nova)
> > +openstack-tempest*)
> > +        # OpenStack Tempest does not have stable branches and should work with any
> 
> Your comment lines need wrapping to ~70-75 (here and later).
> 
> > +        # version of OpenStack
> >  	repo_tree_rev_fetch_git openstack-nova \
> >  		$TREE_OPENSTACK_NOVA master $LOCALREV_OPENSTACK_NOVA
> >  	;;
> > +openstack-*-*)
> 
> I think you need to document what your openstack-*-* branch names are
> going to be.
> 
> And, you make provision here for branches openstack-tempest* but you
> don't add any such branches to cr-for-branches.
> 
> I forget what decisions we made about the push gate logic for the
> various openstack branches.  I think it would be worth explicitly
> writing this down in tree (in a comment in ap-fetch-* perhaps).

We decided to track only nova.git, and let osstest clone other trees and
checkout the HEAD (by having REVISION_* empty). That is fine if we track
"master" of nova.git.

The issue now is if we want to track a branch of OpenStack, like
"stable/ocata" (which is the latest release), we need to have all trees
(nova.git, devstack.git, ...) checkout the same branch. (tempest.git
does not have release specific branch.)

I think this patch is confusing because I originally try to use osstest
scripts to find which commit to use for every trees and so have add the
necessary into ./ap-fetch-version. But I could not make that works
without duplicating some functions and so went with writing
'origin/stable/ocata' into REVISION_*.


In term of osstest branches, in cr-for-branches, I would like only one
branch. 'openstack-nova-ocata' would be a the branch that test the
OpenStack release named 'Ocata'. Later, once this branch run smoothly,
we can add a branch to test 'master', the development branch of
OpenStack, it was called 'openstack-nova' in the original 3 patch of
this patch series.

-- 
Anthony PERARD

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

  reply	other threads:[~2017-06-23 16:26 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 17:56 [OSSTEST PATCH v11 00/20] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 01/20] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 02/20] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 03/20] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 04/20] ts-openstack-deploy: Set http proxy Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 05/20] TestSupport: provide target_https_mitm_proxy_cert_path Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 06/20] ts-openstack-deploy: set CURL_CA_BUNDLE Anthony PERARD
2017-06-16 17:56 ` [OSSTEST PATCH v11 07/20] ts-openstack-deploy: Keep CURL_CA_BUNDLE when sudo is called Anthony PERARD
2017-06-23 13:37   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 08/20] ts-openstack-deploy: Try to disable use of SYSTEMD Anthony PERARD
2017-06-23 13:38   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 09/20] ts-kernel-build: Enable network related modules for Neutron Anthony PERARD
2017-06-23 13:39   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 10/20] ts-openstack-deploy: Switch to Neutron for network Anthony PERARD
2017-06-23 13:41   ` Ian Jackson
2017-06-23 14:10     ` Anthony PERARD
2017-06-23 14:18       ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 11/20] ts-openstack-deploy: Increase fd and memory limits for rabbitmq Anthony PERARD
2017-06-23 13:41   ` Ian Jackson
2017-06-23 14:35     ` Anthony PERARD
2017-06-23 15:34       ` Ian Jackson
2017-06-23 16:50         ` Anthony PERARD
2017-06-23 17:16           ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 12/20] make-flight: Increase dom0_mem for openstack flight Anthony PERARD
2017-06-23 13:42   ` Ian Jackson
2017-06-23 14:40     ` Anthony PERARD
2017-06-23 15:35       ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 13/20] ts-openstack-deploy: Apply a Tempest patch Anthony PERARD
2017-06-23 13:43   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 14/20] ts-openstack-deploy: Ignore libvirt-python version and use latest Anthony PERARD
2017-06-23 13:44   ` Ian Jackson
2017-06-16 17:56 ` [OSSTEST PATCH v11 15/20] ts-openstack-tempest: Fix tempest invocation Anthony PERARD
2017-06-23 13:45   ` Ian Jackson
2017-06-23 14:49     ` Anthony PERARD
2017-06-16 17:57 ` [OSSTEST PATCH v11 16/20] ts-openstack-tempest: Update list of skipped tests Anthony PERARD
2017-06-23 13:47   ` Ian Jackson
2017-06-23 15:16     ` Anthony PERARD
2017-06-23 15:38       ` Ian Jackson
2017-06-30 16:11         ` Anthony PERARD
2017-06-30 16:32           ` Ian Jackson
2017-06-30 17:58             ` Anthony PERARD
2017-07-05 14:33               ` Anthony PERARD
2017-06-16 17:57 ` [OSSTEST PATCH v11 17/20] ts-openstack-deploy: Move logs to /var/log/openstack Anthony PERARD
2017-06-23 13:48   ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 18/20] ts-logs-capture: Capture OpenStack logs Anthony PERARD
2017-06-23 13:49   ` Ian Jackson
2017-06-23 15:31     ` Anthony PERARD
2017-06-23 15:42       ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 19/20] ts-openstack-deploy: Increase devstack timeout Anthony PERARD
2017-06-23 13:49   ` Ian Jackson
2017-06-16 17:57 ` [OSSTEST PATCH v11 20/20] Introduce flight for stable branches of OpenStack Anthony PERARD
2017-06-23 13:58   ` Ian Jackson
2017-06-23 16:26     ` Anthony PERARD [this message]
2017-06-23 16:47       ` Ian Jackson
2017-06-23 17:00   ` Ian Jackson
2017-06-30 16:51     ` Anthony PERARD
2017-07-03 11:00       ` Ian Jackson
2017-06-19 11:02 ` [OSSTEST PATCH v11 00/20] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD

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=20170623162626.GI1702@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.