# Gateway for openstack/swift

**URL:** <https://discuss.elastic.co/t/gateway-for-openstack-swift/11237>\
**Category:** Elasticsearch\
**Created:** [March 21, 2013, 1:10pm UTC](https://discuss.elastic.co/t/gateway-for-openstack-swift/11237 "2013-03-21T13:10:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![david\_ventura](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@david\_ventura](https://discuss.elastic.co/u/david_ventura)\
**Post date:** [March 21, 2013, 1:10pm UTC](https://discuss.elastic.co/t/gateway-for-openstack-swift/11237/1 "2013-03-21T13:10:41Z")

</div>

Hi all,

I would like to make a gateway to use OpenStack / swift as storage space.

If I'm not mistaken, I can take the reference claud-awd plugin as a  
starting point, and more precisely the part of the S3 storage.

Is this the right way to go?

Another small question,

Elasticsearch documentation on the S3 gateway is marked as 'deprecated' and  
removed in the future.

Does this mean that ES API will be changed and make the code S3 gateway  
obsolete?

David

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [March 21, 2013, 3:59pm UTC](https://discuss.elastic.co/t/gateway-for-openstack-swift/11237/2 "2013-03-21T15:59:54Z")

</div>

Yes, you should be prepared that NFS/S3/HDFS gateways will disappear in  
favor of a backup/restore mechanism with snapshots etc.

As far as I understand most people got a misconception of the gateway as  
a backup tool. But the gateway must scale over many hundreds and  
thousands of nodes so it will be local filesystem only in the future.

After a backup/restore framework will be added I assume there will be  
the possibility to address NFS/S3/HDFS again, and also Swift, but not as  
a gateway.

Jörg

Am 21.03.13 14:10, schrieb david ventura:

> Does this mean that ES API will be changed and make the code S3  
> gateway obsolete?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![david\_ventura](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@david\_ventura](https://discuss.elastic.co/u/david_ventura)\
**Post date:** [March 22, 2013, 8:25am UTC](https://discuss.elastic.co/t/gateway-for-openstack-swift/11237/3 "2013-03-22T08:25:30Z")

</div>

OK, thanks very much Jörg.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:45am UTC](https://discuss.elastic.co/t/gateway-for-openstack-swift/11237/4 "2017-07-06T02:45:10Z")

</div>


