On Thu, Sep 28, 2017 at 12:32 PM, Emilien Macchi <[email protected]> wrote:
> On Thu, Sep 28, 2017 at 9:22 AM, Wesley Hayutin <[email protected]> > wrote: > [...] > > OK.. I think the solution is to start migrating these jobs to RDO > Software > > Factory third party testing. > > > > Here is what I propose: > > 1. Start with an experiment check job > > https://review.rdoproject.org/r/#/c/9823/ > > This will help us confirm that everything works or fails as we expect. > We > > are > > also afforded a configurable timeout \0/. It's currently set to 360 > minutes > > for the overcloud upgrade jobs. > > > > 2. Once this is proven out, we can run upgrade jobs as third party on any > > review upstream > > > > 3. New coverage should be prototyped in RDO Software Factory > > > > 4. If jobs prove to be reliable and consistent and run under 170 minutes > we > > move what > > we can back upstream. > > > > WDYT? > > I think this is mega cool, although your work is related to *Upgrades* > and not minor updates but still super cool. > > Note: FTR we discussed on IRC that we would probably do the same kind > of thing for minor updates testing. > > Thanks Wes, > -- > Emilien Macchi > Right, I'm going to first attempt to get what we *have* running, and then get the new jobs we need in there as well. :)) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
