Difference between revisions of "Meetings/Swift"
< Meetings
David Hadas (talk | contribs) |
|||
| Line 14: | Line 14: | ||
** Make sure any code approaching the device go via a central function (e.g. storage_directory() in utils) allowing monkey patching it or offering other ways to extend it | ** Make sure any code approaching the device go via a central function (e.g. storage_directory() in utils) allowing monkey patching it or offering other ways to extend it | ||
** While we do it , we can extend storage_directory() to also append the basedir and device since this seem to be required by all its users. | ** While we do it , we can extend storage_directory() to also append the basedir and device since this seem to be required by all its users. | ||
| + | * Next release June 27? | ||
Revision as of 14:42, 12 June 2013
Meeting Time: Every other Wednesday at 19:00 UTC
Next Meeting: Wednesday, June 12
Agenda items:
- API
- hong kong summit
- How backwards compatible do we need to be with internal (i.e. non-user-facing) interfaces? This question was inspired by https://review.openstack.org/22820, which changes the format of a data structure in the WSGI environment that other middlewares may use, though none in the Swift codebase do.
- Path Control: Create an open interface to control the path used by Swift within devices (where within the device a/c/o/tmp/qurentined/async are placed).
- Make sure any code approaching the device go via a central function (e.g. storage_directory() in utils) allowing monkey patching it or offering other ways to extend it
- While we do it , we can extend storage_directory() to also append the basedir and device since this seem to be required by all its users.
- Next release June 27?
