Open Stack

On Tue, May 27, 2014 at 10:02 AM, Hua ZZ Zhang <zhuadl at cn.ibm.com> wrote:

> Do it make sense to support storage policy work in devstack so that it can
> be more easily tested?
>
> -Edward Zhang
>
> I don't think storage policy on one VM  (which has other OpenStack
services)  like usually setup for devstack is very practical, but I may be
wrong.

Chmouel.




>
> [image: Inactive hide details for John Dickinson ---2014-05-24 上午
> 06:27:13---John Dickinson <me at not.mn>]John Dickinson ---2014-05-24 上午
> 06:27:13---John Dickinson <me at not.mn>
>
>
>    *John Dickinson <me at not.mn <me at not.mn>>*
>
>    2014-05-24 上午 06:27
>    Please respond to
>    "OpenStack Development Mailing List \(not for usage questions\)" <
>    openstack-dev at lists.openstack.org>
>
>
>
> To
>
>
>    "OpenStack Development Mailing List (not for usage questions)" <
>    openstack-dev at lists.openstack.org>,
>    openstack-operators at lists.openstack.org
>
>
> cc
>
>
> Subject
>
>
>    [openstack-dev] [Swift] storage policies merge plan
>
>
> We've been working for a long time on the feature/ec branch in the swift
> repo. It's now "done" and needs to be merged into master to be generally
> available.
>
> Here's how the integration is going to work:
>
> 1) The feature/ec branch will be refactored into a series of dependent
> reviewable patches
> 2) The patch chain will be proposed to master, and master will enter a
> freeze until the storage policy patches land
> 3) The first patch in the chain will be marked as -2 to "plug" the chain
> 4) The Swift community will review and approve all patches in the chain.
> 5) When all patches in the chain are approved, the first -2 will be
> removed and the whole chain will be sent to the CI system
>
>
> There are two things that I'll ask of you during this time. First, please
> commit time to reviewing the storage policy patches. Second, please do not
> deploy a version of Swift that is midway through the storage policy patch
> chain. I don't expect it to break anything, but it's a complicating factor
> best to be avoided.
>
> I will send out another email when the patch chain has been proposed to
> master and to announce the freeze.
>
> --John
>
>
>
> *(See attached file: signature.asc)*
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/4ae61578/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/4ae61578/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic11382.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/4ae61578/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/4ae61578/attachment-0002.gif>