Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/12/14 14:22, Alan Pevec wrote: Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z Ceilometer (all proposed by Ceilo PTL) https://review.openstack.org/138315 https://review.openstack.org/138317 https://review.openstack.org/138320 https://review.openstack.org/138321 https://review.openstack.org/138322 Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver Glance https://review.openstack.org/137704 - glance_store is backward compatible, but not sure about forcing version bump on stable https://review.openstack.org/137862 - Disable osprofiler by default to prevent upgrade issues, disabled by default in other services Horizon standing-after-freeze translation update, coming on Dec 3 https://review.openstack.org/138018 - visible issue, no translation string changes https://review.openstack.org/138313 - low risk patch for a highly problematic issue Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments I'd like to request another exception for Neutron to avoid introducing regression in hostname validation for DNS nameservers: https://review.openstack.org/#/c/139061/ Nova https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno+topic:1386236/juno,n,z - - soaked more than a week in master, makes numa actually work in Juno Sahara https://review.openstack.org/135549 - fix for auto security groups, there were some concerns, see review for details ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUgG3pAAoJEC5aWaUY1u57E7gH/Ry5zrN5/1bA8M2NkkhmJ1D4 ks9sX4ivZYjSeV5/4qfLsrHAnO2+R5H3CmVHmS2Us3s5ZTU4CTiKCt9TAmWDy5pd f6YmpjzOnszusXMMibi1K7sWZGmC0P5zOSxyPZh1W3rljy7WZSeR/P3NtAqqBw3M eMb0gEDBDkyn8JNWSxM5mjYHYsYnfU6CddZWT/EoOQExttFKRyAd35ugOJnvbQoR F3Cu3k/BgsxSPYZIuLzf+W1YQBsnGpH9AK7LwTzVfsYJgX1ggiVGU8Rdh3FvccIx hV84PKMwNccIgwIMxqK83QHtV4p1FJ/TN4UmActXSgR1J+QUEFgH32zAolIMLlw= =n/d7 -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
I'd like to request another exception for Neutron to avoid introducing regression in hostname validation for DNS nameservers: https://review.openstack.org/#/c/139061/ Nice solution for this regression, I think it's worthy last-minute exception. Should VMT also send this officially to the vendors as a followup to OSSA 2014-039 ? Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On 12/04/2014 09:29 AM, Alan Pevec wrote: I'd like to request another exception for Neutron to avoid introducing regression in hostname validation for DNS nameservers: https://review.openstack.org/#/c/139061/ Nice solution for this regression, I think it's worthy last-minute exception. Should VMT also send this officially to the vendors as a followup to OSSA 2014-039 ? Cheers, Alan Thanks Alan for bringing this up, Well the security fix did cause a regression so this fix should warrant an OSSA ERRATA. However, I now wonder what use-case requires an hostname as nameserver, considering this will cause an extra lookup for name resolution... Tristan signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On 12/03/2014 01:17 PM, Alan Pevec wrote: 2014-12-02 17:15 GMT+01:00 Jay S. Bryant jsbry...@electronicjungle.net: Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver +1 I think this is fine to make an exception for. one more Cinder exception proposal was added in StableJuno etherpad * https://review.openstack.org/#/c/138526/ (This is currently the master version but I will be proposing to stable/juno as soon as it is approved in Master) The Brocade FS San Lookup facility is currently broken and this revert is necessary to get it working again. Jay, what's the status there, I see master change failed in gate? Cheers, Alan Finally was able to get the master version through the gate and cherry-picked it here: https://review.openstack.org/#/c/139194/ That one has made it through the check. So, if it isn't too late, it could use a +2/+A. Thanks! Jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
2014-12-04 23:00 GMT+01:00 Jay S. Bryant jsbry...@electronicjungle.net: Finally was able to get the master version through the gate and cherry-picked it here: https://review.openstack.org/#/c/139194/ That one has made it through the check. So, if it isn't too late, it could use a +2/+A. Looks good and is exception worthy, approved. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On 12/04/2014 05:01 PM, Alan Pevec wrote: 2014-12-04 23:00 GMT+01:00 Jay S. Bryant jsbry...@electronicjungle.net: Finally was able to get the master version through the gate and cherry-picked it here: https://review.openstack.org/#/c/139194/ That one has made it through the check. So, if it isn't too late, it could use a +2/+A. Looks good and is exception worthy, approved. Thanks so much Alan! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
Alan Pevec wrote: General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z So it looks like we should hold on that, and revert the recent capping before release (see further down on this thread). Ceilometer (all proposed by Ceilo PTL) https://review.openstack.org/138315 Already in https://review.openstack.org/138317 +1 https://review.openstack.org/138320 +1 https://review.openstack.org/138321 Impact a bit unclear, but then the fix is basic https://review.openstack.org/138322 +1 Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver +1 Glance https://review.openstack.org/137704 - glance_store is backward compatible, but not sure about forcing version bump on stable -1 for 2014.2.1 exception, also needs to be revisited in light of recent capping revert proposal https://review.openstack.org/137862 - Disable osprofiler by default to prevent upgrade issues, disabled by default in other services Sounds like something we'd rather have in the point release than after. I don't think it's aversion incompatibility issue, but more of an upgrade potential pain. Horizon standing-after-freeze translation update, coming on Dec 3 https://review.openstack.org/138018 - visible issue, no translation string changes +1 https://review.openstack.org/138313 - low risk patch for a highly problematic issue Already in Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) -1: I would rather fix the doc to match behavior, than change behavior to match the doc and lose people that were relying on it. https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments +0: Feels a bit large for a last-minute exception. Nova https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno+topic:1386236/juno,n,z - soaked more than a week in master, makes numa actually work in Juno +0: Also feels a bit large for a last-minute exception Sahara https://review.openstack.org/135549 - fix for auto security groups, there were some concerns, see review for details Already in -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
Doug Hellmann wrote: On Dec 2, 2014, at 5:41 PM, Alan Pevec ape...@gmail.com wrote: General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z +2, let's keep all deps in sync. Those updates do not break anything for existing users. Just spotted it, there is now proposal to revert caps in Juno: https://review.openstack.org/138546 Doug, shall we stop merging caps to projects in Juno? Today we found that when we have caps in place that do not overlap with the versions used in master, we can’t upgrade services one at a time on a host running multiple services. We didn’t have this problem between icehouse and juno because I used the same cap values for both releases, so we didn’t trigger any problems with grenade. One solution is to undo the caps and then add caps when we discover issues in new versions of libraries and stable branches. Another is to require applications to work with “old” versions of libraries and degrade their feature set, so that we can keep the lower bounds overlapping. In retrospect, this issue with caps was obvious, but I don’t remember it being raise in the planning. As Sean pointed out on IRC today, we should have someone write a spec for changing the way we deal with requirements so we can think about it before deciding what to do. After the releases today, the “no more alpha versions for Oslo” ship has sailed. Removing the caps will at least let us move ahead while we figure out what to do for stable branches. Yes, looks like we need to think a bit deeper about it, and at the very least not ship them in the point release. +2 on the requirements revert. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
2014-12-02 17:15 GMT+01:00 Jay S. Bryant jsbry...@electronicjungle.net: Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver +1 I think this is fine to make an exception for. one more Cinder exception proposal was added in StableJuno etherpad * https://review.openstack.org/#/c/138526/ (This is currently the master version but I will be proposing to stable/juno as soon as it is approved in Master) The Brocade FS San Lookup facility is currently broken and this revert is necessary to get it working again. Jay, what's the status there, I see master change failed in gate? Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
Horizon standing-after-freeze translation update, coming on Dec 3 This is now posted https://review.openstack.org/138798 David, Matthias, I'd appreciate one of you to have a quick look before approving. Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) -1: I would rather fix the doc to match behavior, than change behavior to match the doc and lose people that were relying on it. Consensus is not to merge this and keep behavior. https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments +0: Feels a bit large for a last-minute exception. Kyle, Ihar, I'd like to see +2 from Neutron stable-maint before approving exception. Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On 03/12/14 20:22, Alan Pevec wrote: Horizon standing-after-freeze translation update, coming on Dec 3 This is now posted https://review.openstack.org/138798 David, Matthias, I'd appreciate one of you to have a quick look before approving. Cheers, Alan Alan, thanks for the heads-up here. Approved. Matthias ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [stable] Exception proposals for 2014.2.1
Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z Ceilometer (all proposed by Ceilo PTL) https://review.openstack.org/138315 https://review.openstack.org/138317 https://review.openstack.org/138320 https://review.openstack.org/138321 https://review.openstack.org/138322 Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver Glance https://review.openstack.org/137704 - glance_store is backward compatible, but not sure about forcing version bump on stable https://review.openstack.org/137862 - Disable osprofiler by default to prevent upgrade issues, disabled by default in other services Horizon standing-after-freeze translation update, coming on Dec 3 https://review.openstack.org/138018 - visible issue, no translation string changes https://review.openstack.org/138313 - low risk patch for a highly problematic issue Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments Nova https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno+topic:1386236/juno,n,z - soaked more than a week in master, makes numa actually work in Juno Sahara https://review.openstack.org/135549 - fix for auto security groups, there were some concerns, see review for details ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/12/14 14:22, Alan Pevec wrote: Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z +2, let's keep all deps in sync. Those updates do not break anything for existing users. Ceilometer (all proposed by Ceilo PTL) https://review.openstack.org/138315 Already pushed to gate (why?) https://review.openstack.org/138317 https://review.openstack.org/138320 https://review.openstack.org/138321 https://review.openstack.org/138322 Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver Glance https://review.openstack.org/137704 - glance_store is backward compatible, but not sure about forcing version bump on stable I think this one should not go in. For stable releases in downstream, it's quite common to backport fixes for bugs. We don't fix bugs by bumping versions. https://review.openstack.org/137862 - Disable osprofiler by default to prevent upgrade issues, disabled by default in other services Hm, looks more like a version incompatibility. Should we instead set glance and osprofiler versions in line? I'm probably ok with disabling debug features even in stable releases, but this one seems like a wrong fix for a rightful issue. Comments? Horizon standing-after-freeze translation update, coming on Dec 3 https://review.openstack.org/138018 - visible issue, no translation string changes https://review.openstack.org/138313 - low risk patch for a highly problematic issue Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) As I told in comments, this one seems to me making the code in line with official documentation, so can be considered as a bug fix. Though the change in behaviour is pretty significant to be cautious. https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments +2. Nova https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno+topic:1386236/juno,n,z - - soaked more than a week in master, makes numa actually work in Juno Sahara https://review.openstack.org/135549 - fix for auto security groups, there were some concerns, see review for details ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUfdT4AAoJEC5aWaUY1u574hoIAJtE6dIAtCPcJw4H83EsFoEh pNDHiHTBmjMCJVFtEKtBUgKT/pRZw5zyvRXYHQSk99Lqw7StcYn2gyW9sDQJSclv ak8wm5KCDtZMnkzfisDtTILx2AQj8RHw1UWVrsjqkoS0vyjUW6dfOpiyxd7o6s9n zJYgGi5uO1EZO+oLDk5NkKl6pDu4OZNbx1iLk+0EPmpjPD9ZT6AdacvtW5oM3+4c udA4CCsiAkHXvUutM0GNeftuOk4TBj6evnnzOai5mZC4QoT3/vhd1or+AEjLtEqO QhM8MT8u+mSDhhlbfblNqIf/bBHOkgZcEX4DMdPtz9R/LtqvBDhDjtyOjJ8cG6w= =bcTW -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On 12/02/2014 07:22 AM, Alan Pevec wrote: Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z Ceilometer (all proposed by Ceilo PTL) https://review.openstack.org/138315 https://review.openstack.org/138317 https://review.openstack.org/138320 https://review.openstack.org/138321 https://review.openstack.org/138322 Cinder https://review.openstack.org/137537 - small change and limited to the VMWare driver +1 I think this is fine to make an exception for. Glance https://review.openstack.org/137704 - glance_store is backward compatible, but not sure about forcing version bump on stable https://review.openstack.org/137862 - Disable osprofiler by default to prevent upgrade issues, disabled by default in other services Horizon standing-after-freeze translation update, coming on Dec 3 https://review.openstack.org/138018 - visible issue, no translation string changes https://review.openstack.org/138313 - low risk patch for a highly problematic issue Neutron https://review.openstack.org/136294 - default SNAT, see review for details, I cannot distil 1liner :) https://review.openstack.org/136275 - self-contained to the vendor code, extensively tested in several deployments Nova https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno+topic:1386236/juno,n,z - soaked more than a week in master, makes numa actually work in Juno Sahara https://review.openstack.org/135549 - fix for auto security groups, there were some concerns, see review for details ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z +2, let's keep all deps in sync. Those updates do not break anything for existing users. Just spotted it, there is now proposal to revert caps in Juno: https://review.openstack.org/138546 Doug, shall we stop merging caps to projects in Juno? Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [stable] Exception proposals for 2014.2.1
On Dec 2, 2014, at 5:41 PM, Alan Pevec ape...@gmail.com wrote: General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.org/#/q/status:open+branch:stable/juno+topic:openstack/requirements,n,z +2, let's keep all deps in sync. Those updates do not break anything for existing users. Just spotted it, there is now proposal to revert caps in Juno: https://review.openstack.org/138546 Doug, shall we stop merging caps to projects in Juno? Today we found that when we have caps in place that do not overlap with the versions used in master, we can’t upgrade services one at a time on a host running multiple services. We didn’t have this problem between icehouse and juno because I used the same cap values for both releases, so we didn’t trigger any problems with grenade. One solution is to undo the caps and then add caps when we discover issues in new versions of libraries and stable branches. Another is to require applications to work with “old” versions of libraries and degrade their feature set, so that we can keep the lower bounds overlapping. In retrospect, this issue with caps was obvious, but I don’t remember it being raise in the planning. As Sean pointed out on IRC today, we should have someone write a spec for changing the way we deal with requirements so we can think about it before deciding what to do. After the releases today, the “no more alpha versions for Oslo” ship has sailed. Removing the caps will at least let us move ahead while we figure out what to do for stable branches. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
