Open Stack

If I understand correctly, you must be referring to the "Back-end API for Object Server REST APIs":

"DiskFile.delete(timestamp)
Delete the object."

"This implementation creates a tombstone file using the given timestamp, and removes any older versions of the object file. Any file that has an older timestamp than timestamp will be deleted."

So I will override these methods.  One question, is there a REST API that sits on every ObjectServer?  I am having a hard time figuring out the architecture from the perspective of multiple servers / VMs.  I get the up-front API is REST, but when you start to build a distributed back-end there are naturally many servers.  Those servers need files to be uploaded/downloaded, so they need an http REST API as well (unless NFS or some other transport is assumed).  In my configuration I plan on 10 Object Servers and 2 servers for account / container / proxy.  There is not a great deal of information on the interaction of these servers.  I looked at http://docs.openstack.org/developer/swift/howto_installmultinode.html but it still does not speak to efficiencies and transports between nodes.


-----Original Message-----
From: Pete Zaitcev [mailto:zaitcev at redhat.com]
Sent: Wednesday, November 13, 2013 1:09 PM
To: Perez, Daniel - ES
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] WORM support

On Wed, 13 Nov 2013 16:47:29 +0000
"Perez, Daniel - ES" <daniel.perez at exelisinc.com> wrote:

> I am wondering if I can circumvent the use of tombstone files?

Not without writing some code, but you can write your own Pluggable Back-end like Gluster does. In that case you're free to implement any delete mechanism you like. Note, however, that current PBEs do not support our normal replication. This is not a concern for Gluster, since it is itself distributed, but something you might need for WORM.

--Pete

________________________________

This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Exelis Inc. The recipient should check this e-mail and any attachments for the presence of viruses. Exelis Inc. accepts no liability for any damage caused by any virus transmitted by this e-mail.