Hi Chmouel, Storage policies can be fully tested and exercised on an SAIO; the docs that were recently merged to the feature/ec branch also include a second example policy using 2x replication to show this. No reason why devstack can’t be used but I’d propose it doesn’t make anything easier and/or more testable.
Thx Paul From: Chmouel Boudjnah [mailto:chmo...@enovance.com] Sent: Tuesday, May 27, 2014 2:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Swift] storage policies merge plan On Tue, May 27, 2014 at 10:02 AM, Hua ZZ Zhang <zhu...@cn.ibm.com<mailto:zhu...@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. [Inactive hide details for John Dickinson ---2014-05-24 上午 06:27:13---John Dickinson <m...@not.mn>]John Dickinson ---2014-05-24 上午 06:27:13---John Dickinson <m...@not.mn<mailto:m...@not.mn>> John Dickinson <m...@not.mn<mailto:m...@not.mn>> 2014-05-24 上午 06:27 Please respond to "OpenStack Development Mailing List \(not for usage questions\)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> To "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, openstack-operat...@lists.openstack.org<mailto:openstack-operat...@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@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto: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
