| *** mikecmpbll has quit IRC | 00:43 | |
| *** baojg has quit IRC | 00:50 | |
| *** NM has joined #openstack-swift | 02:04 | |
| *** idlemind has joined #openstack-swift | 02:57 | |
| idlemind | Is it possible to have a ring where objects automatically expire x (90?) days after creation? Would this be a policy or handled by the expiration service strictly? | 02:58 |
|---|---|---|
| *** zaitcev has quit IRC | 04:14 | |
| timburke | idlemind, we don't have a way to have that be tied to a ring or storage policy, at least not at the moment. currently, you'd have to specify x-delete-after: 7776000 (that is, 90 days' worth of seconds) for each object as it's uploaded (or POST it after uploading) | 05:12 |
| timburke | fwiw, i had an idea a while ago to add a "defaulter" middleware that would let you specify something like x-default-object-x-delete-after: 7776000 at the container level to have all uploads automatically get such a header if it wasn't already specified | 05:14 |
| *** pcaruana has quit IRC | 07:14 | |
| *** pcaruana has joined #openstack-swift | 07:24 | |
| *** mikecmpbll has joined #openstack-swift | 08:27 | |
| *** e0ne has joined #openstack-swift | 08:36 | |
| *** e0ne has quit IRC | 08:43 | |
| *** mikecmpbll has quit IRC | 10:35 | |
| *** mvkr has joined #openstack-swift | 14:28 | |
| idlemind | @timburke when they are back - as long as I could do something scheduled that added the policy at least for now that'd be ok | 17:23 |
| *** mvkr has quit IRC | 18:09 | |
| *** sorrison has quit IRC | 22:11 | |
| *** sorrison has joined #openstack-swift | 22:14 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!