Difference between revisions of "Meetings/Swift"
< Meetings
| Line 8: | Line 8: | ||
** Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?] | ** Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?] | ||
*** 2 big questions in the review comments | *** 2 big questions in the review comments | ||
| + | **** Does setting ionice actually improve anything? Swift's processes are rather interconnected, so it's very difficult to isolate a logical API operation by process. eg nice'ing the container server would impact object PUTs since the container is updated as part of the object write. | ||
**** Should we even be doing this in Swift itself instead of distro init scripts. On the one hand, the ionice priority "code" has to be rewritten for every distro. On the other, ops know ionice and how/when to use it and does that actually belong in Swift? If it does, why not other ops/management tools? | **** Should we even be doing this in Swift itself instead of distro init scripts. On the one hand, the ionice priority "code" has to be rewritten for every distro. On the other, ops know ionice and how/when to use it and does that actually belong in Swift? If it does, why not other ops/management tools? | ||
| − | |||
** Make object-auditor storage-policy-aware - https://review.openstack.org/#/c/266599/ [notmyname] | ** Make object-auditor storage-policy-aware - https://review.openstack.org/#/c/266599/ [notmyname] | ||
*** critical bug that needs to be closed for a release | *** critical bug that needs to be closed for a release | ||
Revision as of 18:33, 13 January 2016
Meeting Time: Every Wednesday at 21:00 UTC in #openstack-meeting Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2016/ Meeting Chair: notmyname
Agenda: January 13, 2016 2100 UTC
- Patches
- Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?]
- 2 big questions in the review comments
- Does setting ionice actually improve anything? Swift's processes are rather interconnected, so it's very difficult to isolate a logical API operation by process. eg nice'ing the container server would impact object PUTs since the container is updated as part of the object write.
- Should we even be doing this in Swift itself instead of distro init scripts. On the one hand, the ionice priority "code" has to be rewritten for every distro. On the other, ops know ionice and how/when to use it and does that actually belong in Swift? If it does, why not other ops/management tools?
- 2 big questions in the review comments
- Make object-auditor storage-policy-aware - https://review.openstack.org/#/c/266599/ [notmyname]
- critical bug that needs to be closed for a release
- Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?]
- What's going on? [notmyname]
When adding an item, please include your IRC nickname with it.
