Re: [openstack-dev] [nova] Austin summit priorities session recap

[Bias, Randy]

We understand.  We¹re willing, ready, and able to assist with all of the
upstream items that need to happen in order to get our submission in and
more.  We just need to know so we can help.

Best,


‹Randy




On 6/8/16, 6:09 PM, "Matt Riedemann"  wrote:

>That blueprint is high priority for a single vendor but low
>priority when compared to the very large backlog of items that Nova has
>for the release as a whole.
>


__
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] Austin summit priorities session recap

[Dan Smith]

> According to the state of this review:
> https://review.openstack.org/#/c/317689/ the works aren't going to be
> done in this cycle.

This is a procedural -2 waiting for all the following patches to be
reviewed and passing 3rd party CI before we land them. We certainly
expect to get this work into the tree in newton.

This refactor work _is_ a priority for nova in newton, which is why we
said in Austin that it was important to get it done before we add more
drivers. Reviewing that code will help accelerate the process --
hopefully you're helping in that area :)

--Dan

__
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] Austin summit priorities session recap

[Diana Clarke]

Hi Alex:

We still hope to land this patch series during this cycle. If you're
referring to the -2 on the patch you mentioned [1], it was just a
procedural -2 until we stopped using the old methods in the driver and
cutover completely to the new methods. I'll ping Dan Smith on IRC
later today, and see if he's ready to revisit his -2.

The cutover to the new methods is in this patch [2], and then there is
a big delete of all the old methods and tests in this patch [3].
Yesterday, the entire patch series was green as far as CI was
concerned, including the experimental job Matt Riedemann kindly added
for LVM (thanks!!!). There are now a few merge conflicts, but it's
still otherwise ready for review.

Feodor has been an excellent reviewer, and it would be great to
continue to get his feedback on this patch series. We hope to be able
to reciprocate when the ScaleIO patches are up for review since we'll
be familiar with that area of the code. The entire patch series can be
found here [4] if anyone else is interested in jumping in on reviews
too.

Thanks folks!

--diana

[1] https://review.openstack.org/#/c/317689/
[2] https://review.openstack.org/#/c/282580/
[3] https://review.openstack.org/#/c/322974/
[4] 
https://review.openstack.org/#/q/openstack/nova+topic:libvirt-instance-storage

On Wed, Jun 8, 2016 at 1:05 PM, Alexandre Levine
 wrote:
> Hi Matt,
>
> According to the state of this review:
> https://review.openstack.org/#/c/317689/ the works aren't going to be done
> in this cycle.
>
> Do you think it'd be possible for our driver to cut in now?
>
> Feodor participated in reviewing and helped as much as possible with current
> efforts and if needed we can spare even more resources to help with the
> refactoring in the next cycle.
>
> Best regards,
>
>   Alex Levine
>
>
> On 5/10/16 7:40 PM, Matt Riedemann wrote:
>>
>> On 5/10/2016 11:24 AM, Alexandre Levine wrote:
>>>
>>> Hi Matt,
>>>
>>> Sorry I couldn't reply earlier - was away.
>>> I'm worrying about ScaleIO ephemeral storage backend
>>>
>>> (https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend)
>>> which is not in this list but various clients are very interested in
>>> having it working along with or instead of Ceph. Especially I'm worrying
>>> in view of the global libvirt storage pools refactoring which looks like
>>> a quite global effort to me judging by a number of preliminary reviews.
>>> It seems to me that we wouldn't be able to squeeze ScaleIO additions
>>> after this refactoring.
>>> What can be done about it?
>>> We could've contribute our initial changes to current code (which would
>>> potentially allow easy backporting to previous versions as a benefit
>>> afterwards) and promise to update our parts along with the refactoring
>>> reviews or something like this.
>>>
>>> Best regards,
>>>   Alex Levine
>>>
>>>
>>> On 5/6/16 3:34 AM, Matt Riedemann wrote:

 There are still a few design summit sessions from the summit that I'll
 recap but I wanted to get the priorities session recap out as early as
 possible. We held that session in the last slot on Thursday. The full
 etherpad is here [1].

 The first part of the session was mostly going over schedule milestones.

 We already started Newton with a freeze on spec approvals for new
 things since we already have a sizable backlog [2]. Now that we're
 past the summit we can approve specs for new things again.

 The full Newton release schedule for Nova is in this wiki [3].

 These are the major dates from here on out:

 * June 2: newton-1, non-priority spec approval freeze
 * June 30: non-priority feature freeze
 * July 15: newton-2
 * July 19-21: Nova Midcycle
 * Aug 4: priority spec approval freeze
 * Sept 2: newton-3, final python-novaclient release, FeatureFreeze,
 Soft StringFreeze
 * Sept 16: RC1 and Hard StringFreeze
 * Oct 7, 2016: Newton Release

 The important thing for most people right now is we have exactly four
 weeks until the non-priority spec approval freeze. We then have about
 one month after that to land all non-priority blueprints.

 Keep in mind that we've already got 52 approved blueprints and most of
 those were re-approved from Mitaka, so have been approved for several
 weeks already.

 The non-priority blueprint cycle is intentionally restricted in Newton
 because of all of the backlog work we've had spilling over into this
 release. We really need to focus on getting as much of that done as
 possible before taking on more new work.

 For the rest of the priorities session we talked about what our actual
 review priorities are for Newton. The list with details and owners is
 already available here [4].

 In no particular order, these are the review priorities:

 * Cells v2
 * Scheduler
 * API Improvements
 * os-vif integration
 * libvirt storage pool

Re: [openstack-dev] [nova] Austin summit priorities session recap

[Matt Riedemann]

On 6/8/2016 7:19 PM, Bias, Randy wrote:

I just want to point out that this appears to imply that open source
storage backends for OpenStack would be prioritized over closed-source
ones and I think that runs counter to the general inclusivity in the
community.  I assume it¹s just a turn of phrase, but I suspect it could be
easily misinterpreted to mean that open source storage projects (external
to OpenStack) could be prioritized over open source ones, creating a very
uneven playing field, which would potentially be very bad from a
perception point of view.

Thanks,


--Randy

VP, Technology, EMC Corporation
Top 10 OpenStack & Cloud Pioneer
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
EXEC ADMIN: inna.k...@emc.com, +1 (415) 601-1168




On 5/10/16, 9:40 AM, "Matt Riedemann"  wrote:


A closed-source vendor-specific ephemeral backend for a single virt
driver in Nova isn't a review priority for the release.



__
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



The implication has to do more with the ability to test and develop on 
closed-source vendor specific backends. So there is a smaller group of 
people that can work on these things and we can't/don't test them in the 
community CI system, which is what third party CI requirements are for.


As a data point, it took me about 4 releases to get DB2 support into 
Nova (landed in Liberty) and we ripped that out a couple of weeks ago. 
It wasn't maintained (no CI) and very few people knew how DB2 worked and 
didn't have access to setting up an environment to test it out.


So, no, the ScaleIO backend spec is not being intentionally blocked 
because it's a closed-source vendor solution. I didn't mean it that way. 
I was just trying to point out the matter of priorities for Nova in this 
release. That blueprint is high priority for a single vendor but low 
priority when compared to the very large backlog of items that Nova has 
for the release as a whole.


--

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] Austin summit priorities session recap

[Bias, Randy]

I just want to point out that this appears to imply that open source
storage backends for OpenStack would be prioritized over closed-source
ones and I think that runs counter to the general inclusivity in the
community.  I assume it¹s just a turn of phrase, but I suspect it could be
easily misinterpreted to mean that open source storage projects (external
to OpenStack) could be prioritized over open source ones, creating a very
uneven playing field, which would potentially be very bad from a
perception point of view.

Thanks,


--Randy

VP, Technology, EMC Corporation
Top 10 OpenStack & Cloud Pioneer
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
EXEC ADMIN: inna.k...@emc.com, +1 (415) 601-1168




On 5/10/16, 9:40 AM, "Matt Riedemann"  wrote:

>A closed-source vendor-specific ephemeral backend for a single virt
>driver in Nova isn't a review priority for the release. 


__
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] Austin summit priorities session recap

[Matt Riedemann]

On 6/8/2016 12:05 PM, Alexandre Levine wrote:

Hi Matt,

According to the state of this review:
https://review.openstack.org/#/c/317689/ the works aren't going to be
done in this cycle.

Do you think it'd be possible for our driver to cut in now?

Feodor participated in reviewing and helped as much as possible with
current efforts and if needed we can spare even more resources to help
with the refactoring in the next cycle.

Best regards,

  Alex Levine




Alex,

Unfortunately the spec for the scaleio image backend wasn't approved 
before the non-priority spec approval freeze so it's going to have to 
wait for Ocata.


I realize this is frustrating. We do already have 85 approved blueprints 
for Newton though including the libvirt imagebackend refactor which the 
scaleio change is going to be dependent on, so I still urge helping out 
with that in any way possible to move it along and make sure that 
dependency gets completed in Newton.


--

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] Austin summit priorities session recap

[Alexandre Levine]

Hi Matt,

According to the state of this review: 
https://review.openstack.org/#/c/317689/ the works aren't going to be 
done in this cycle.


Do you think it'd be possible for our driver to cut in now?

Feodor participated in reviewing and helped as much as possible with 
current efforts and if needed we can spare even more resources to help 
with the refactoring in the next cycle.


Best regards,

  Alex Levine


On 5/10/16 7:40 PM, Matt Riedemann wrote:

On 5/10/2016 11:24 AM, Alexandre Levine wrote:

Hi Matt,

Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage backend
(https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend) 


which is not in this list but various clients are very interested in
having it working along with or instead of Ceph. Especially I'm worrying
in view of the global libvirt storage pools refactoring which looks like
a quite global effort to me judging by a number of preliminary reviews.
It seems to me that we wouldn't be able to squeeze ScaleIO additions
after this refactoring.
What can be done about it?
We could've contribute our initial changes to current code (which would
potentially allow easy backporting to previous versions as a benefit
afterwards) and promise to update our parts along with the refactoring
reviews or something like this.

Best regards,
  Alex Levine


On 5/6/16 3:34 AM, Matt Riedemann wrote:

There are still a few design summit sessions from the summit that I'll
recap but I wanted to get the priorities session recap out as early as
possible. We held that session in the last slot on Thursday. The full
etherpad is here [1].

The first part of the session was mostly going over schedule 
milestones.


We already started Newton with a freeze on spec approvals for new
things since we already have a sizable backlog [2]. Now that we're
past the summit we can approve specs for new things again.

The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze,
Soft StringFreeze
* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly four
weeks until the non-priority spec approval freeze. We then have about
one month after that to land all non-priority blueprints.

Keep in mind that we've already got 52 approved blueprints and most of
those were re-approved from Mitaka, so have been approved for several
weeks already.

The non-priority blueprint cycle is intentionally restricted in Newton
because of all of the backlog work we've had spilling over into this
release. We really need to focus on getting as much of that done as
possible before taking on more new work.

For the rest of the priorities session we talked about what our actual
review priorities are for Newton. The list with details and owners is
already available here [4].

In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration

We *should* be able to knock out glance v2, get-me-a-network and
os-vif relatively soon (I'm thinking sometime in June).

Not listed in [4] but something we talked about was volume
multi-attach with Cinder. We said this was going to be a 'stretch
goal' contingent on making decent progress on that item by
non-priority feature freeze *and* we get the above three smaller
priority items completed.

Another thing we talked about but isn't going to be a priority is
NFV-related work. We talked about cleaning up technical debt and
additional testing for NFV but had no one in the session signed up to
own that work or with concrete proposals on how to make improvements
in that area. Since we can't assign review priorities to something
that nebulous it was left out. Having said that, Moshe Levi has
volunteered to restart and lead the SR-IOV/PCI bi-weekly meeting [5]
(thanks again, Moshe!). So if you (or your employer, or your vendor)
are interested in working on NFV in Nova please attend that meeting
and get involved in helping out that subteam.

[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html 


[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4]
https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html 



[5]
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html 






__ 


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subjec

Re: [openstack-dev] [nova] Austin summit priorities session recap

[Alexandre Levine]

Thank you Matt.
We'll think how we can help here.

Best regards,
  Alex Levine

On 5/10/16 7:40 PM, Matt Riedemann wrote:

On 5/10/2016 11:24 AM, Alexandre Levine wrote:

Hi Matt,

Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage backend
(https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend) 


which is not in this list but various clients are very interested in
having it working along with or instead of Ceph. Especially I'm worrying
in view of the global libvirt storage pools refactoring which looks like
a quite global effort to me judging by a number of preliminary reviews.
It seems to me that we wouldn't be able to squeeze ScaleIO additions
after this refactoring.
What can be done about it?
We could've contribute our initial changes to current code (which would
potentially allow easy backporting to previous versions as a benefit
afterwards) and promise to update our parts along with the refactoring
reviews or something like this.

Best regards,
  Alex Levine


On 5/6/16 3:34 AM, Matt Riedemann wrote:

There are still a few design summit sessions from the summit that I'll
recap but I wanted to get the priorities session recap out as early as
possible. We held that session in the last slot on Thursday. The full
etherpad is here [1].

The first part of the session was mostly going over schedule 
milestones.


We already started Newton with a freeze on spec approvals for new
things since we already have a sizable backlog [2]. Now that we're
past the summit we can approve specs for new things again.

The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze,
Soft StringFreeze
* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly four
weeks until the non-priority spec approval freeze. We then have about
one month after that to land all non-priority blueprints.

Keep in mind that we've already got 52 approved blueprints and most of
those were re-approved from Mitaka, so have been approved for several
weeks already.

The non-priority blueprint cycle is intentionally restricted in Newton
because of all of the backlog work we've had spilling over into this
release. We really need to focus on getting as much of that done as
possible before taking on more new work.

For the rest of the priorities session we talked about what our actual
review priorities are for Newton. The list with details and owners is
already available here [4].

In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration

We *should* be able to knock out glance v2, get-me-a-network and
os-vif relatively soon (I'm thinking sometime in June).

Not listed in [4] but something we talked about was volume
multi-attach with Cinder. We said this was going to be a 'stretch
goal' contingent on making decent progress on that item by
non-priority feature freeze *and* we get the above three smaller
priority items completed.

Another thing we talked about but isn't going to be a priority is
NFV-related work. We talked about cleaning up technical debt and
additional testing for NFV but had no one in the session signed up to
own that work or with concrete proposals on how to make improvements
in that area. Since we can't assign review priorities to something
that nebulous it was left out. Having said that, Moshe Levi has
volunteered to restart and lead the SR-IOV/PCI bi-weekly meeting [5]
(thanks again, Moshe!). So if you (or your employer, or your vendor)
are interested in working on NFV in Nova please attend that meeting
and get involved in helping out that subteam.

[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html 


[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4]
https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html 



[5]
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html 






__ 


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



Alexandre,

A closed-source vendor-specific ephemeral backend for a single virt 
driver in Nova isn't a review priority for the release. The review 
priorities we have for Newton are really broad multi-release efforts 
that we need to focus on.


This doe

Re: [openstack-dev] [nova] Austin summit priorities session recap

[Matt Riedemann]

On 5/10/2016 11:24 AM, Alexandre Levine wrote:

Hi Matt,

Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage backend
(https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend)
which is not in this list but various clients are very interested in
having it working along with or instead of Ceph. Especially I'm worrying
in view of the global libvirt storage pools refactoring which looks like
a quite global effort to me judging by a number of preliminary reviews.
It seems to me that we wouldn't be able to squeeze ScaleIO additions
after this refactoring.
What can be done about it?
We could've contribute our initial changes to current code (which would
potentially allow easy backporting to previous versions as a benefit
afterwards) and promise to update our parts along with the refactoring
reviews or something like this.

Best regards,
  Alex Levine


On 5/6/16 3:34 AM, Matt Riedemann wrote:

There are still a few design summit sessions from the summit that I'll
recap but I wanted to get the priorities session recap out as early as
possible. We held that session in the last slot on Thursday. The full
etherpad is here [1].

The first part of the session was mostly going over schedule milestones.

We already started Newton with a freeze on spec approvals for new
things since we already have a sizable backlog [2]. Now that we're
past the summit we can approve specs for new things again.

The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze,
Soft StringFreeze
* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly four
weeks until the non-priority spec approval freeze. We then have about
one month after that to land all non-priority blueprints.

Keep in mind that we've already got 52 approved blueprints and most of
those were re-approved from Mitaka, so have been approved for several
weeks already.

The non-priority blueprint cycle is intentionally restricted in Newton
because of all of the backlog work we've had spilling over into this
release. We really need to focus on getting as much of that done as
possible before taking on more new work.

For the rest of the priorities session we talked about what our actual
review priorities are for Newton. The list with details and owners is
already available here [4].

In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration

We *should* be able to knock out glance v2, get-me-a-network and
os-vif relatively soon (I'm thinking sometime in June).

Not listed in [4] but something we talked about was volume
multi-attach with Cinder. We said this was going to be a 'stretch
goal' contingent on making decent progress on that item by
non-priority feature freeze *and* we get the above three smaller
priority items completed.

Another thing we talked about but isn't going to be a priority is
NFV-related work. We talked about cleaning up technical debt and
additional testing for NFV but had no one in the session signed up to
own that work or with concrete proposals on how to make improvements
in that area. Since we can't assign review priorities to something
that nebulous it was left out. Having said that, Moshe Levi has
volunteered to restart and lead the SR-IOV/PCI bi-weekly meeting [5]
(thanks again, Moshe!). So if you (or your employer, or your vendor)
are interested in working on NFV in Nova please attend that meeting
and get involved in helping out that subteam.

[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html
[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4]
https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html

[5]
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html




__
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



Alexandre,

A closed-source vendor-specific ephemeral backend for a single virt 
driver in Nova isn't a review priority for the release. The review 
priorities we have for Newton are really broad multi-release efforts 
that we need to focus on.


This doesn't mean we aren't approving other specs/blueprints. We already 
have 53 approved blueprints for Newton and only 6 of those are 
implemented,

Re: [openstack-dev] [nova] Austin summit priorities session recap

[Alexandre Levine]

Hi Matt,

Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage backend 
(https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend) 
which is not in this list but various clients are very interested in 
having it working along with or instead of Ceph. Especially I'm worrying 
in view of the global libvirt storage pools refactoring which looks like 
a quite global effort to me judging by a number of preliminary reviews. 
It seems to me that we wouldn't be able to squeeze ScaleIO additions 
after this refactoring.

What can be done about it?
We could've contribute our initial changes to current code (which would 
potentially allow easy backporting to previous versions as a benefit 
afterwards) and promise to update our parts along with the refactoring 
reviews or something like this.


Best regards,
  Alex Levine


On 5/6/16 3:34 AM, Matt Riedemann wrote:
There are still a few design summit sessions from the summit that I'll 
recap but I wanted to get the priorities session recap out as early as 
possible. We held that session in the last slot on Thursday. The full 
etherpad is here [1].


The first part of the session was mostly going over schedule milestones.

We already started Newton with a freeze on spec approvals for new 
things since we already have a sizable backlog [2]. Now that we're 
past the summit we can approve specs for new things again.


The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze, 
Soft StringFreeze

* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly four 
weeks until the non-priority spec approval freeze. We then have about 
one month after that to land all non-priority blueprints.


Keep in mind that we've already got 52 approved blueprints and most of 
those were re-approved from Mitaka, so have been approved for several 
weeks already.


The non-priority blueprint cycle is intentionally restricted in Newton 
because of all of the backlog work we've had spilling over into this 
release. We really need to focus on getting as much of that done as 
possible before taking on more new work.


For the rest of the priorities session we talked about what our actual 
review priorities are for Newton. The list with details and owners is 
already available here [4].


In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration

We *should* be able to knock out glance v2, get-me-a-network and 
os-vif relatively soon (I'm thinking sometime in June).


Not listed in [4] but something we talked about was volume 
multi-attach with Cinder. We said this was going to be a 'stretch 
goal' contingent on making decent progress on that item by 
non-priority feature freeze *and* we get the above three smaller 
priority items completed.


Another thing we talked about but isn't going to be a priority is 
NFV-related work. We talked about cleaning up technical debt and 
additional testing for NFV but had no one in the session signed up to 
own that work or with concrete proposals on how to make improvements 
in that area. Since we can't assign review priorities to something 
that nebulous it was left out. Having said that, Moshe Levi has 
volunteered to restart and lead the SR-IOV/PCI bi-weekly meeting [5] 
(thanks again, Moshe!). So if you (or your employer, or your vendor) 
are interested in working on NFV in Nova please attend that meeting 
and get involved in helping out that subteam.


[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2] 
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html

[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4] 
https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html
[5] 
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html





__
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] Austin summit priorities session recap

[Matt Riedemann]

On 5/6/2016 1:37 PM, Nikhil Komawar wrote:

Thanks for sending this out Matt. I added a inline comment here.

On Thu, May 5, 2016 at 8:34 PM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:

There are still a few design summit sessions from the summit that
I'll recap but I wanted to get the priorities session recap out as
early as possible. We held that session in the last slot on
Thursday. The full etherpad is here [1].

The first part of the session was mostly going over schedule milestones.

We already started Newton with a freeze on spec approvals for new
things since we already have a sizable backlog [2]. Now that we're
past the summit we can approve specs for new things again.

The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze,
Soft StringFreeze
* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly
four weeks until the non-priority spec approval freeze. We then have
about one month after that to land all non-priority blueprints.

Keep in mind that we've already got 52 approved blueprints and most
of those were re-approved from Mitaka, so have been approved for
several weeks already.

The non-priority blueprint cycle is intentionally restricted in
Newton because of all of the backlog work we've had spilling over
into this release. We really need to focus on getting as much of
that done as possible before taking on more new work.

For the rest of the priorities session we talked about what our
actual review priorities are for Newton. The list with details and
owners is already available here [4].

In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration


I saw the priorities review ( https://review.openstack.org/#/c/312217/ )
has been merged so wanted to point that out here. I know Nova team cares
about history section of the specs so the dates are more clear from the
links posted on the comment. To be more explicit: Glance v2 work
(BP+code) was initially proposed in Icehouse, the co-located mid-cycle
was in Kilo where we had a brief session on Glance v2 work (& thanks to
all the Nova members who have been giving their input). Also, the reason
for my comments/questions in the etherpad.



We *should* be able to knock out glance v2, get-me-a-network and
os-vif relatively soon (I'm thinking sometime in June).

Not listed in [4] but something we talked about was volume
multi-attach with Cinder. We said this was going to be a 'stretch
goal' contingent on making decent progress on that item by
non-priority feature freeze *and* we get the above three smaller
priority items completed.

Another thing we talked about but isn't going to be a priority is
NFV-related work. We talked about cleaning up technical debt and
additional testing for NFV but had no one in the session signed up
to own that work or with concrete proposals on how to make
improvements in that area. Since we can't assign review priorities
to something that nebulous it was left out. Having said that, Moshe
Levi has volunteered to restart and lead the SR-IOV/PCI bi-weekly
meeting [5] (thanks again, Moshe!). So if you (or your employer, or
your vendor) are interested in working on NFV in Nova please attend
that meeting and get involved in helping out that subteam.

[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html
[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4]

https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html
[5]
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html

--

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
ht

Re: [openstack-dev] [nova] Austin summit priorities session recap

[Nikhil Komawar]

Thanks for sending this out Matt. I added a inline comment here.

On Thu, May 5, 2016 at 8:34 PM, Matt Riedemann 
wrote:

> There are still a few design summit sessions from the summit that I'll
> recap but I wanted to get the priorities session recap out as early as
> possible. We held that session in the last slot on Thursday. The full
> etherpad is here [1].
>
> The first part of the session was mostly going over schedule milestones.
>
> We already started Newton with a freeze on spec approvals for new things
> since we already have a sizable backlog [2]. Now that we're past the summit
> we can approve specs for new things again.
>
> The full Newton release schedule for Nova is in this wiki [3].
>
> These are the major dates from here on out:
>
> * June 2: newton-1, non-priority spec approval freeze
> * June 30: non-priority feature freeze
> * July 15: newton-2
> * July 19-21: Nova Midcycle
> * Aug 4: priority spec approval freeze
> * Sept 2: newton-3, final python-novaclient release, FeatureFreeze, Soft
> StringFreeze
> * Sept 16: RC1 and Hard StringFreeze
> * Oct 7, 2016: Newton Release
>
> The important thing for most people right now is we have exactly four
> weeks until the non-priority spec approval freeze. We then have about one
> month after that to land all non-priority blueprints.
>
> Keep in mind that we've already got 52 approved blueprints and most of
> those were re-approved from Mitaka, so have been approved for several weeks
> already.
>
> The non-priority blueprint cycle is intentionally restricted in Newton
> because of all of the backlog work we've had spilling over into this
> release. We really need to focus on getting as much of that done as
> possible before taking on more new work.
>
> For the rest of the priorities session we talked about what our actual
> review priorities are for Newton. The list with details and owners is
> already available here [4].
>
> In no particular order, these are the review priorities:
>
> * Cells v2
> * Scheduler
> * API Improvements
> * os-vif integration
> * libvirt storage pools (for live migration)
> * Get Me a Network
> * Glance v2 Integration
>

I saw the priorities review ( https://review.openstack.org/#/c/312217/ )
has been merged so wanted to point that out here. I know Nova team cares
about history section of the specs so the dates are more clear from the
links posted on the comment. To be more explicit: Glance v2 work (BP+code)
was initially proposed in Icehouse, the co-located mid-cycle was in Kilo
where we had a brief session on Glance v2 work (& thanks to all the Nova
members who have been giving their input). Also, the reason for my
comments/questions in the etherpad.


>
> We *should* be able to knock out glance v2, get-me-a-network and os-vif
> relatively soon (I'm thinking sometime in June).
>
> Not listed in [4] but something we talked about was volume multi-attach
> with Cinder. We said this was going to be a 'stretch goal' contingent on
> making decent progress on that item by non-priority feature freeze *and* we
> get the above three smaller priority items completed.
>
> Another thing we talked about but isn't going to be a priority is
> NFV-related work. We talked about cleaning up technical debt and additional
> testing for NFV but had no one in the session signed up to own that work or
> with concrete proposals on how to make improvements in that area. Since we
> can't assign review priorities to something that nebulous it was left out.
> Having said that, Moshe Levi has volunteered to restart and lead the
> SR-IOV/PCI bi-weekly meeting [5] (thanks again, Moshe!). So if you (or your
> employer, or your vendor) are interested in working on NFV in Nova please
> attend that meeting and get involved in helping out that subteam.
>
> [1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
> [2]
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html
> [3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
> [4]
> https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html
> [5]
> http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html
>
> --
>
> 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

[openstack-dev] [nova] Austin summit priorities session recap

[Matt Riedemann]

There are still a few design summit sessions from the summit that I'll 
recap but I wanted to get the priorities session recap out as early as 
possible. We held that session in the last slot on Thursday. The full 
etherpad is here [1].


The first part of the session was mostly going over schedule milestones.

We already started Newton with a freeze on spec approvals for new things 
since we already have a sizable backlog [2]. Now that we're past the 
summit we can approve specs for new things again.


The full Newton release schedule for Nova is in this wiki [3].

These are the major dates from here on out:

* June 2: newton-1, non-priority spec approval freeze
* June 30: non-priority feature freeze
* July 15: newton-2
* July 19-21: Nova Midcycle
* Aug 4: priority spec approval freeze
* Sept 2: newton-3, final python-novaclient release, FeatureFreeze, Soft 
StringFreeze

* Sept 16: RC1 and Hard StringFreeze
* Oct 7, 2016: Newton Release

The important thing for most people right now is we have exactly four 
weeks until the non-priority spec approval freeze. We then have about 
one month after that to land all non-priority blueprints.


Keep in mind that we've already got 52 approved blueprints and most of 
those were re-approved from Mitaka, so have been approved for several 
weeks already.


The non-priority blueprint cycle is intentionally restricted in Newton 
because of all of the backlog work we've had spilling over into this 
release. We really need to focus on getting as much of that done as 
possible before taking on more new work.


For the rest of the priorities session we talked about what our actual 
review priorities are for Newton. The list with details and owners is 
already available here [4].


In no particular order, these are the review priorities:

* Cells v2
* Scheduler
* API Improvements
* os-vif integration
* libvirt storage pools (for live migration)
* Get Me a Network
* Glance v2 Integration

We *should* be able to knock out glance v2, get-me-a-network and os-vif 
relatively soon (I'm thinking sometime in June).


Not listed in [4] but something we talked about was volume multi-attach 
with Cinder. We said this was going to be a 'stretch goal' contingent on 
making decent progress on that item by non-priority feature freeze *and* 
we get the above three smaller priority items completed.


Another thing we talked about but isn't going to be a priority is 
NFV-related work. We talked about cleaning up technical debt and 
additional testing for NFV but had no one in the session signed up to 
own that work or with concrete proposals on how to make improvements in 
that area. Since we can't assign review priorities to something that 
nebulous it was left out. Having said that, Moshe Levi has volunteered 
to restart and lead the SR-IOV/PCI bi-weekly meeting [5] (thanks again, 
Moshe!). So if you (or your employer, or your vendor) are interested in 
working on NFV in Nova please attend that meeting and get involved in 
helping out that subteam.


[1] https://etherpad.openstack.org/p/newton-nova-summit-priorities
[2] 
http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html

[3] https://wiki.openstack.org/wiki/Nova/Newton_Release_Schedule
[4] 
https://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html
[5] 
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093541.html


--

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