Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs
Thanks for giving this review Michal. On Thu, Jan 19, 2017 at 8:29 AM, Andreas Jaegerwrote: > On 2017-01-19 11:10, Michal Dulko wrote: > > Hi all, > > > > I've seen some confusion around new Cinder CI jobs being proposed to > > project-config in yesterday's IRC scrollback. This email aims to sum > > this up and explain purposes of what's being proposed. > > > Thanks a lot, Michal! That helps me seeing the big picture with all > these changes, > > Andreas > > > [...] > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >GF: Felix Imendörffer, Jane Smithard, Graham Norton, >HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs
On 2017-01-19 11:10, Michal Dulko wrote: > Hi all, > > I've seen some confusion around new Cinder CI jobs being proposed to > project-config in yesterday's IRC scrollback. This email aims to sum > this up and explain purposes of what's being proposed. Thanks a lot, Michal! That helps me seeing the big picture with all these changes, Andreas > [...] -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs
Hi all, I've seen some confusion around new Cinder CI jobs being proposed to project-config in yesterday's IRC scrollback. This email aims to sum this up and explain purposes of what's being proposed. Background == For a few releases we're aiming to increase our functional and integration tests coverage. This was manifested by adding new Tempest tests, enabling functional tests, providing CIs for open source volume drivers and enabling multinode grenade testing of rolling upgrade. We're continuing the efforts with various new jobs: Multinode grenade = In Newton we've introduced a job that tests master c-api and c-sch with stable c-vol and c-bak. We would like to be able to test other combinations as well. Currently Grenade doesn't support upgrading services on a node one-by-one, while running tests in-between, so that's why we've decided to create multiple jobs. This is being developed in [1]. I understand that two more multinode jobs put a lot of burden on gate's resources and that's why we plan to keep these jobs in experimental queue. We can fire them up on potentially breaking changes like RPC API modifications and DB migrations. Zero downtime = This was triggered by introduction of assert:supports-zero-downtime- upgrade tag [2] and Cinder's implementation is being worked on in [3]. The exact testing solution is currently evaluated in Nova and Cinder's implementation is following that. I think adding this job for Cinder is future work - we'll let Nova team spearhead this. Note that at first patch [3] was to introduce 3 more multinode jobs. I don't think this will be necessary and we will require only a single job. Anyway - that's future. Volume migration This is being worked on in [4] and is Cinder's equivalent of gate- tempest-dsvm-multinode-live-migration-ubuntu-xenial in Nova. Run in-tree tests = This effort aims to increase Cinder's community control over what Tempest tests are run in Cinder jobs. It's gathered under run-intree- tests topic [5]. ZeroMQ (merged) === This case is pretty simple, gate-tempest-dsvm-zeromq-multibackend- ubuntu-xenial in experimental queue aims to test multibackend scenario with ZeroMQ. Such scenario wasn't functional until [6] was merged. I believe that we can pretty easily identify patches that can potentially break ZeroMQ support, so this will stay in experimental for now and be run only on demand. I hope this helps to clear out some doubts. As you can see some of the jobs with the highest demand for gate resources are intended to only stay in experimental queue to be run by Cinder reviewers on demand. [1] https://review.openstack.org/#/c/384836/ [2] https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html [3] https://review.openstack.org/#/c/420375/ [4] https://review.openstack.org/#/c/381737 [5] https://review.openstack.org/#/q/topic:run-intree-tests [6] https://review.openstack.org/#/c/398452/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev