Hi, Matt,

Thank you for the clarification.

Best Regards
Chaoyi Huang ( Joe Huang )


-----Original Message-----
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] 
Sent: Monday, June 13, 2016 9:07 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Let me know if you have an approved spec 
but unapproved blueprint

On 6/12/2016 7:48 PM, joehuang wrote:
> Hello,
>
> This spec is not approved yet: 
> https://review.openstack.org/#/c/295595/
>
> But the BP is approved: 
> https://blueprints.launchpad.net/nova/+spec/expose-quiesce-unquiesce-a
> pi
>
> Don't know how to deal with the spec now. Is this spec killed? Should Nova 
> support application level consistency snapshot for disaster recovery purpose 
> or not?
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
> -----Original Message-----
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Sunday, June 12, 2016 9:08 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [nova] Let me know if you have an approved 
> spec but unapproved blueprint
>
> I've come across several changes up for review that are tied to Newton 
> blueprints which have specs approved but the blueprints in launchpad are not 
> yet approved.
>
> If you have a spec that was approved for Newton but your blueprint in 
> launchpad isn't approved yet, please ping me (mriedem) in IRC or reply to 
> this thread to get it approved and tracked for the Newton release.
> It's important (at least to me) that we have an accurate representation of 
> how much work we're trying to get done this release, especially with 
> non-priority feature freeze coming up in three weeks.
>

Neither the spec nor the blueprint is approved. The blueprint was previously 
approved in mitaka but is not for newton, with reasons in the spec review for 
newton.

At this point we're past non-priority spec approval freeze so this isn't going 
to get in for newton. There are a lot of concerns about this one so it's going 
to be tabled for at least this release, we can revisit in ocata, but it adds a 
lot of complexity and it's more than we're willing to take on right now given 
everything else planned for this release.

-- 

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

Reply via email to