Hehe, alright :) Well, as their documentation says: http://www.rackspace.com/blog/rackspace-cloud-files-how-to-use-expiring-objects-api-functionality/
It should "just work" :) If it doesn't it's not an openstack issue but a rackspace issue ;) Mvh / Best regards Morten Møller Riis Gigahost ApS m...@gigahost.dk On Oct 10, 2013, at 2:48 PM, Shrinand Javadekar <shrin...@maginatics.com> wrote: > I am using Rackspace Cloudfiles-US. I don't have access to the actual storage > servers to find out if the expirer is running. > > But given that it is a publicly available object store, I would hope so :-). > > -Shri > > > On Wed, Oct 9, 2013 at 8:46 PM, Morten Møller Riis <m...@gigahost.dk> wrote: > Is the swift-object-expirer daemon running? > > Mvh / Best regards > Morten Møller Riis > Gigahost ApS > m...@gigahost.dk > > > > > On Oct 10, 2013, at 2:28 PM, Shrinand Javadekar <shrin...@maginatics.com> > wrote: > >> Hi, >> >> Objects in a swift container can be deleted by either explicitly deleting >> them or by setting a expiry timestamp on them. Is there a performance >> difference between the two? For example, when I want to delete an object, >> instead of deleting it, can I simply set the X-Delete-After attribute of >> that object to 0? Is one faster than the other? >> >> My guess is that setting the object expiry timestamp may be faster since >> that would only involve changing the xattrs of the object inode. Delete will >> require creation of a new version of the object, truncating it to a 0 byte >> file and renaming it to change the extension to ".ts". Seems like less work >> is done when object expiration is set. >> >> To try this out, I tried setting the X-Delete-After attribute using the >> swift command line client: >> >> $ swift post -m X-Delete-After: 1 <container-name> <object-name> >> >> After I did this, when I stat the object, I see the attribute "Meta >> X-Delete-After: 1". However, the object never got deleted. Any idea what I'm >> doing wrong? >> >> -Shri >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack@lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
