Difference between revisions of "Meetings/Swift"
< Meetings
| Line 8: | Line 8: | ||
|} | |} | ||
| − | ''' | + | '''Next meeting:''' May 24, 2017 2100 UTC |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Follow-up from last week | * Follow-up from last week | ||
** TC goals | ** TC goals | ||
| Line 20: | Line 15: | ||
*** py3 -- https://governance.openstack.org/tc/goals/pike/python35.html | *** py3 -- https://governance.openstack.org/tc/goals/pike/python35.html | ||
*** we need to write down any plans or blockers and track any progress for this | *** we need to write down any plans or blockers and track any progress for this | ||
| − | * In the LOSF optimization, where do we store the meta data, K/V or volume? (rledisez) | + | ** In the LOSF optimization, where do we store the meta data, K/V or volume? (rledisez) |
| − | ** https://etherpad.openstack.org/p/swift-losf-meta-storage | + | *** https://etherpad.openstack.org/p/swift-losf-meta-storage |
| + | ** composite ring | ||
* Open Discussion | * Open Discussion | ||
Revision as of 22:26, 17 May 2017
| Meeting Time | Every Wednesday at 21:00 UTC in #openstack-meeting |
| Meeting Logs | http://eavesdrop.openstack.org/meetings/swift/2017/ |
| Chair | notmyname |
Next meeting: May 24, 2017 2100 UTC
- Follow-up from last week
- TC goals
- support wsgi -- https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
- py3 -- https://governance.openstack.org/tc/goals/pike/python35.html
- we need to write down any plans or blockers and track any progress for this
- In the LOSF optimization, where do we store the meta data, K/V or volume? (rledisez)
- composite ring
- TC goals
- Open Discussion
Notes left from earlier
- Things happening in Swift
- golang object server
- global ec
- composite rings
- policy migration
- policy auto tiering
- sync to elasticsearch
- container sharding
- symlinks
- increase part power
- container sharding
When adding an item, please include your IRC nickname with it.
