OpenStack Meeting Summary

Agenda: June 17, 2015 2100 UTC

1Meeting summary
https://wiki.openstack.org/wiki/Meetings/Swift (notmyname, 21:03:15)

2 general (notmyname, 21:03:48) 

21:04:07 <notmyname> as mentioned in -swift and on the mailing list, we've slightly change the core team structure
21:04:18 <notmyname> we now have swift-core and swiftclient-core
21:04:37 <notmyname> swiftclient-core can merge code for python-swiftclient

团队分swift-core and swiftclient-core，主要是为了让更多的人选择swift，需要改善client使用。目前移植到swift上需要适配甚多接口，工作量大。后面社区的工作会相对侧重swiftclient。

3 container sync (notmyname, 21:14:50)
https://bugs.launchpad.net/swift/+bug/1464022 (notmyname, 21:17:50)

目前container的同步接口没有包括对metadata的同步。编码基本完成，可以发布一个patch测试。

4 next release (notmyname, 21:26:52) 

21:29:13 <notmyname> if the EC stuff lands soon, then I'm inclined to revert the six dependency, release 2.3.1, then reapply the new dependency
21:29:40 <notmyname> however, if there's more "big" stuff that lands, then we've got a 2.4 release no matter what and the new dependency will stay in

5 hummingbird update (notmyname, 21:32:23) 

21:34:20 <dfg_> we've also seen an increase in performance of GET calls

21:35:23 <dfg_> um- not sure about specific numbers but the # read timeotus has decreased by like x30

6 oslo.config (notmyname, 21:42:22)
https://review.openstack.org/#/c/192094/ (notmyname, 21:43:36)
http://paste.openstack.org/show/297679/ (notmyname, 21:43:48)
https://review.openstack.org/#/c/149930/ this one is the patch. the other was the spec (notmyname, 21:56:53)

关于oslo.config的使用。有些人不建议使用全局配置文件，但目前的机制还没有一个好的解决方案。

7 other (notmyname, 21:59:39)
https://review.openstack.org/#/c/191970/ and https://review.openstack.org/#/c/184189/ need reviewed (notmyname, 22:00:21)

Agenda: June 3, 2015 2100 UTC

• priority reviews [notmyname]
• py3 script-generated patches. what are we doing here?

Agenda: May 27, 2015 2100 UTC

#info py26 is no longer supported in swift

#info specs take way too long to land, tech details up front cause it to slow down, discoverability of landed specs may be an issue.
so where there is a landed spec, link to it from priority review page section