Re: [openstack-dev] [nova] Outlook on Ocata blueprints
On 1/4/2017 12:07 AM, Shiina, Hironori wrote: Hi Matt, In Not started / blocked group in https://etherpad.openstack.org/p/nova-ocata-feature-freeze : https://blueprints.launchpad.net/nova/+spec/inject-nmi-ironic (Tang Chen) No Nova code changes yet, several Ironic patches outstanding, so probably not going to happen for Nova in Ocata. Nova code change for this blueprint was already posted. https://review.openstack.org/#/c/376548/ Thanks, Hironori Shiina Thanks for pointing that out, I've updated the status in the etherpad. The nova change is up, but is dependent on the python-ironicclient change which is dependent on the Ironic API change, and none of those are merged yet. The client change would have to be merged and released by January 19th so it's getting pretty tight for that series which is why I marked the nova blueprint as blocked. -- Thanks, Matt Riedemann __ 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] [nova] Outlook on Ocata blueprints
Hi Matt, In Not started / blocked group in https://etherpad.openstack.org/p/nova-ocata-feature-freeze : https://blueprints.launchpad.net/nova/+spec/inject-nmi-ironic (Tang Chen) No Nova code changes yet, several Ironic patches outstanding, so probably not going to happen for Nova in Ocata. Nova code change for this blueprint was already posted. https://review.openstack.org/#/c/376548/ Thanks, Hironori Shiina > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Thursday, December 29, 2016 10:19 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [nova] Outlook on Ocata blueprints > > Over the last couple of days I've gone over each blueprint targeted for > Ocata [1] which isn't yet implemented. I've categorized each based on > it's current status or what my outlook is for it getting done in this > release before the feature freeze on January 26th. The results are here: > > https://etherpad.openstack.org/p/nova-ocata-feature-freeze > > We have 69 blueprints targeted for Ocata of which only 14 are already > implemented (complete). That leaves 55 outstanding blueprints. > > I've broken them down as such: > > - Good progress: there are 16 of these which I'm fairly confident can > get merged before the feature freeze given enough focus. 5 of these are > priorities. > > - Slow progress / at risk: there are 19 of these which for one reason or > another are at risk of not getting completed before the feature freeze. > Some just haven't had enough (or any) core reviewer attention yet, or > they are wayward changes that look basically abandoned. 2 of these are > related to priorities. > > - Not started / blocked: there are 13 of these. Some don't have any code > proposed yet. Several are blocked because of dependencies on library > releases or other projects (some for os-vif or Ironic for example). 2 of > these are priorities. > > - On-going refactor / cleanup series: there are 7 of these. I consider > these lower priority as they are multi-release efforts and what doesn't > get done in Ocata can be worked on in Pike. > > -- > > As you'll see in the etherpad, I have notes on each one. If you own one > of these blueprints and there is a note about something that needs to > get done, please make that a priority if you want to see the blueprint > have a chance of landing in Ocata. > > Keep in mind that the non-client library release freeze for Ocata is > January 19th, so if you have dependencies on os-* or oslo libraries > those need to get released before the 19th, and then after that there is > only one week until feature freeze. With most people out until the 3rd, > that only leaves 3 weeks to get library changes released and 4 weeks > until feature freeze. > > If you know that you aren't going to have the time to work on something > please let me know and we can look for volunteers to pick up the > remaining work or I'll defer the blueprint out of tracking for Ocata so > reviewers can focus on what's planned to get done. > > If by January 12th we still have changes which haven't started I'll > probably just automatically defer them. > > Please let me know if there are any questions. > > [1] https://blueprints.launchpad.net/nova/ocata > > -- > > Thanks, > > Matt Riedemann > > > __ > 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] [nova] Outlook on Ocata blueprints
On 1/3/2017 6:03 PM, Takashi Natsume wrote: Hi Matt. The following blueprint has been approved for ocata, but it is not in "nova-ocata-feature-freeze" etherpad. * https://blueprints.launchpad.net/nova/+spec/cold-migration-with-target-ocata * https://review.openstack.org/#/c/334725/ (spec) The blueprint's definition is "Approved", but the series goal is still "Proposed for ocata". It should be "Accepted for ocata". Would you change it to "Accepted for ocata"? Thanks for pointing this one out Takashi. I don't think I've ever had to change the series on the blueprint to get it to switch from proposed to accepted, at least not that I remember. Anyway, that's fixed now and I've added an entry to the etherpad. I think later in the week I'm going to try and go through the etherpad again and start pulling things out which aren't started yet or otherwise don't really have a chance of getting in at this point. There are some others, like the one above, that are ready for review but just haven't gotten any serious review yet, and I'll start tagging those as needing review or somehow highlight those. We may also consider having a review day on things in that etherpad next week. I'll mention something along those lines in the team meeting this week. -- Thanks, Matt Riedemann __ 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] [nova] Outlook on Ocata blueprints
Hi Matt. The following blueprint has been approved for ocata, but it is not in "nova-ocata-feature-freeze" etherpad. * https://blueprints.launchpad.net/nova/+spec/cold-migration-with-target-ocata * https://review.openstack.org/#/c/334725/ (spec) The blueprint's definition is "Approved", but the series goal is still "Proposed for ocata". It should be "Accepted for ocata". Would you change it to "Accepted for ocata"? On 2016/12/29 10:19, Matt Riedemann wrote: Over the last couple of days I've gone over each blueprint targeted for Ocata [1] which isn't yet implemented. I've categorized each based on it's current status or what my outlook is for it getting done in this release before the feature freeze on January 26th. The results are here: https://etherpad.openstack.org/p/nova-ocata-feature-freeze We have 69 blueprints targeted for Ocata of which only 14 are already implemented (complete). That leaves 55 outstanding blueprints. I've broken them down as such: - Good progress: there are 16 of these which I'm fairly confident can get merged before the feature freeze given enough focus. 5 of these are priorities. - Slow progress / at risk: there are 19 of these which for one reason or another are at risk of not getting completed before the feature freeze. Some just haven't had enough (or any) core reviewer attention yet, or they are wayward changes that look basically abandoned. 2 of these are related to priorities. - Not started / blocked: there are 13 of these. Some don't have any code proposed yet. Several are blocked because of dependencies on library releases or other projects (some for os-vif or Ironic for example). 2 of these are priorities. - On-going refactor / cleanup series: there are 7 of these. I consider these lower priority as they are multi-release efforts and what doesn't get done in Ocata can be worked on in Pike. -- As you'll see in the etherpad, I have notes on each one. If you own one of these blueprints and there is a note about something that needs to get done, please make that a priority if you want to see the blueprint have a chance of landing in Ocata. Keep in mind that the non-client library release freeze for Ocata is January 19th, so if you have dependencies on os-* or oslo libraries those need to get released before the 19th, and then after that there is only one week until feature freeze. With most people out until the 3rd, that only leaves 3 weeks to get library changes released and 4 weeks until feature freeze. If you know that you aren't going to have the time to work on something please let me know and we can look for volunteers to pick up the remaining work or I'll defer the blueprint out of tracking for Ocata so reviewers can focus on what's planned to get done. If by January 12th we still have changes which haven't started I'll probably just automatically defer them. Please let me know if there are any questions. [1] https://blueprints.launchpad.net/nova/ocata Regards, Takashi Natsume NTT Software Innovation Center E-mail: natsume.taka...@lab.ntt.co.jp __ 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] [nova] Outlook on Ocata blueprints
Over the last couple of days I've gone over each blueprint targeted for Ocata [1] which isn't yet implemented. I've categorized each based on it's current status or what my outlook is for it getting done in this release before the feature freeze on January 26th. The results are here: https://etherpad.openstack.org/p/nova-ocata-feature-freeze We have 69 blueprints targeted for Ocata of which only 14 are already implemented (complete). That leaves 55 outstanding blueprints. I've broken them down as such: - Good progress: there are 16 of these which I'm fairly confident can get merged before the feature freeze given enough focus. 5 of these are priorities. - Slow progress / at risk: there are 19 of these which for one reason or another are at risk of not getting completed before the feature freeze. Some just haven't had enough (or any) core reviewer attention yet, or they are wayward changes that look basically abandoned. 2 of these are related to priorities. - Not started / blocked: there are 13 of these. Some don't have any code proposed yet. Several are blocked because of dependencies on library releases or other projects (some for os-vif or Ironic for example). 2 of these are priorities. - On-going refactor / cleanup series: there are 7 of these. I consider these lower priority as they are multi-release efforts and what doesn't get done in Ocata can be worked on in Pike. -- As you'll see in the etherpad, I have notes on each one. If you own one of these blueprints and there is a note about something that needs to get done, please make that a priority if you want to see the blueprint have a chance of landing in Ocata. Keep in mind that the non-client library release freeze for Ocata is January 19th, so if you have dependencies on os-* or oslo libraries those need to get released before the 19th, and then after that there is only one week until feature freeze. With most people out until the 3rd, that only leaves 3 weeks to get library changes released and 4 weeks until feature freeze. If you know that you aren't going to have the time to work on something please let me know and we can look for volunteers to pick up the remaining work or I'll defer the blueprint out of tracking for Ocata so reviewers can focus on what's planned to get done. If by January 12th we still have changes which haven't started I'll probably just automatically defer them. Please let me know if there are any questions. [1] https://blueprints.launchpad.net/nova/ocata -- Thanks, Matt Riedemann __ 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
