August 2014 - Openstack-stable-maint

[all][oslo] official recommendations to handle oslo-incubator sync requests
by Ihar Hrachyshka 12 Sep '14

12 Sep '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, I've found out there are no clear public instructions on how to handle oslo-incubator synchronizations in master and stable branches neither at [1] nor at [2]. Though my observations show that there is some oral tradition around community on how we handle those review, as follows: 1. For master oslo-incubator sync requests, we tend to sync the whole modules or even all the modules that a project uses (unless some specific obstacles to do so). This is to use the latest and greatest code from Oslo subproject, fetch all possible bug fixes and goodies, and make the synchronized copy of it as similar to upstream (=oslo-incubator) as possible. 2. For stable branches, the process is a bit different. For those branches, we don't generally want to introduce changes that are not related to specific issues in a project. So in case of backports, we tend to do per-patch consideration when synchronizing from incubator. 3. Backporting for stable branches is a bit complicated process. When reviewing synchronization requests for those branches, we should not only check that the code is present in all consequent branches of the appropriate project (f.e. for Havana, in both Juno and Icehouse), but also that the patches being synchronized were successfully backported to corresponding stable branches of oslo-incubator. So the usual way of oslo-incubator bug fix is (in case of e.g. Neutron): oslo-incubator (master) -> neutron (master) -> oslo-incubator (stable/icehouse) -> neutron (stable/icehouse). [For Havana, it's even more complicated, introducing more elements in the backporting chain.] I hope I've described the existing oral tradition correctly. Please comment on that, and if we're ok with the way it's written above, I'd like to update our wiki pages ([1] and [2]) with that. [1]: https://wiki.openstack.org/wiki/ReviewChecklist#Oslo_Syncing_Checklist [2]: https://wiki.openstack.org/wiki/StableBranch Cheers, /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJT81aRAAoJEC5aWaUY1u57PmgIAIJzzOUHMRe4oDJ0slj5DwjW FpXY6ce/awnFBpG7PR/qlMWXrbGHwesDZ3oihVHA4hbGOkjG7trK35uP07A9IQDI fptLQZ0CXIjgQghoHUtM2BUUjJ19jwKaMdX14BNAAIO6C0hJMElpl/ZTY7zGwa9S pBotxelpMHr4fE06BqDU5hfradBPJOjn0dg2xcqchYU67B8DqTYaLHwQh9XL1r8s 16IvcDlrpJf9N2f9G/V6SlgJlgZzVUfyeKIKQ47/AP+FsSv2rPpH6UgtDdIy8yqj IMyyXUNbvBNwZTC4bLd6NlrNIuLBLmUX7Ao96wldFbAc84uFc6iAoRrtPNdj2ec= =B7+E -----END PGP SIGNATURE-----

3 4

Stable check of openstack/ceilometer failed
by jenkins＠openstack.org 30 Aug '14

30 Aug '14

1 0

Stable check of openstack/ceilometer failed
by jenkins＠openstack.org 29 Aug '14

29 Aug '14

Build failed. - periodic-ceilometer-docs-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-havana/3… : SUCCESS in 8m 16s - periodic-ceilometer-python26-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python26-hava… : SUCCESS in 10m 41s - periodic-ceilometer-python27-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-hava… : SUCCESS in 7m 53s - periodic-ceilometer-docs-icehouse http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-icehouse… : SUCCESS in 4m 30s - periodic-ceilometer-python26-icehouse http://logs.openstack.org/periodic-stable/periodic-ceilometer-python26-iceh… : FAILURE in 3m 41s - periodic-ceilometer-python27-icehouse http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-iceh… : FAILURE in 5m 42s

1 0

[openstack-dev][Neutron][stable] How to backport database schema fixes
by Yaguang Tang 29 Aug '14

29 Aug '14

Hi, all It seems that currently it's hard to backport any database schema fix to Neutron [1] which uses alembic to manage db schema version. Nova has the same issue before and a workaround is to put some placeholder files before each release. So first do we allow db schema fixes to be backport to stable for Neutron ? If we do, then how about put some placeholder files similar to Nova at the end of each release cycle? or we have some better solution for alembic. From the stable maintainer side, we have a policy for stable backport https://wiki.openstack.org/wiki/StableBranch - DB schema changes is forbidden If we allow db schema backports for more than one project, I think we need to update the wiki. [1] https://review.openstack.org/#/c/110642/ <https://review.openstack.org/#/c/110642/> -- Tang Yaguang Canonical Ltd. | www.ubuntu.com | www.canonical.com gpg key: 0x187F664F

5 4

Stable check of openstack/ceilometer failed
by jenkins＠openstack.org 28 Aug '14

28 Aug '14

1 0

Stable check of openstack/trove failed
by jenkins＠openstack.org 28 Aug '14

28 Aug '14

Build failed. - periodic-trove-docs-icehouse http://logs.openstack.org/periodic-stable/periodic-trove-docs-icehouse/ea18… : SUCCESS in 3m 11s - periodic-trove-python26-icehouse http://logs.openstack.org/periodic-stable/periodic-trove-python26-icehouse/… : FAILURE in 4m 58s - periodic-trove-python27-icehouse http://logs.openstack.org/periodic-stable/periodic-trove-python27-icehouse/… : SUCCESS in 4m 35s

2 1

Stable check of openstack/tempest failed
by jenkins＠openstack.org 28 Aug '14

28 Aug '14

Build failed. - periodic-tempest-dsvm-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-havana… : SUCCESS in 36m 11s - periodic-tempest-dsvm-neutron-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-hav… : FAILURE in 38m 08s - periodic-tempest-dsvm-postgres-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : SUCCESS in 35m 15s - periodic-tempest-dsvm-full-icehouse http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-icehou… : SUCCESS in 1h 01m 10s - periodic-tempest-dsvm-neutron-icehouse http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-ice… : SUCCESS in 58m 28s - periodic-tempest-dsvm-postgres-full-icehouse http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : SUCCESS in 47m 58s

1 0

Stable check of openstack/neutron failed
by jenkins＠openstack.org 26 Aug '14

26 Aug '14

1 0

Icehouse bitrot jobs
by Alan Pevec 26 Aug '14

26 Aug '14

2014-08-18 0:51 GMT+02:00 Alan Pevec <apevec(a)gmail.com>: > BTW are Icehouse periodic jobs running? I don't see them listed in > "Stable check of openstack/keystone failed" reports... Also no mention of icehouse under http://logs.openstack.org/periodic-stable/ so I went ahead and copy/pasted: https://review.openstack.org/115933 Is that all needed to enable Icehouse bitrot jobs or I missed something? Cheers, Alan

3 3

Stable check of openstack/neutron failed
by jenkins＠openstack.org 25 Aug '14

25 Aug '14

1 0