# Cloudstack Swift River

**URL:** <https://discuss.elastic.co/t/cloudstack-swift-river/10297>\
**Category:** Elasticsearch\
**Created:** [January 10, 2013, 4:31pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297 "2013-01-10T16:31:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![chenry12](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@chenry12](https://discuss.elastic.co/u/chenry12)\
**Post date:** [January 10, 2013, 4:31pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/1 "2013-01-10T16:31:23Z")

</div>

Hello,

Before developping a CloudStack Swift river  
[http://docs.openstack.org/trunk/openstack-compute/starter/content/ch05s01s02.html](http://docs.openstack.org/trunk/openstack-compute/starter/content/ch05s01s02.html)  
Do you know if this solution exists ?

It seems that is close to the "dropbox river" solution developed by david ?  
I have never developped plugins for ES, only used this search.

Is it possible to develop a plugin based on river CloudStack Swift River  
and how difficult and time expected to develop this kind of solution?

Thanks,

--

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 10, 2013, 4:41pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/2 "2013-01-10T16:41:50Z")

</div>

If cloudstack has a nice API and is easy to use, the elasticsearch river side is  
quite easy to understand.  
Just fork any river project (RSS, FS, Twitter...) and go for it.

BTW, I wrote something about it (french content):  
[http://dev.david.pilato.fr/?p=171](http://dev.david.pilato.fr/?p=171) [http://dev.david.pilato.fr/?p=171](http://dev.david.pilato.fr/?p=171)

Feel free to ask any question about it.

HTH  
David.

Le 10 janvier 2013 à 17:31, Christophe HENRY [chrispub12@free.fr](mailto:chrispub12@free.fr) a écrit :

> Hello,
> 
> Before developping a CloudStack Swift river
> 
> [Admin Documentation — nova 28.1.0.dev108 documentation](http://docs.openstack.org/trunk/openstack-compute/starter/content/ch05s01s02.html)  
> Do you know if this solution exists ?
> 
> It seems that is close to the "dropbox river" solution developed by david ?  
> I have never developped plugins for ES, only used this search.
> 
> Is it possible to develop a plugin based on river CloudStack Swift River and  
> how difficult and time expected to develop this kind of solution?
> 
> Thanks,
> 
> --

--  
David Pilato  
[http://www.scrutmydocs.org/](http://www.scrutmydocs.org/)  
[http://dev.david.pilato.fr/](http://dev.david.pilato.fr/)  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

--

---

<div class="post-metadata">

**Author:** ![chenry12](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@chenry12](https://discuss.elastic.co/u/chenry12)\
**Post date:** [January 10, 2013, 6:04pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/3 "2013-01-10T18:04:25Z")

</div>

Oups, There is a mistake : not read CloudStack but _OpenStack._  
But the link is good.

Hi David,  
If you base your answer with the web link with api , that's good for me 🙂

--

---

<div class="post-metadata">

**Author:** ![chenry12](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@chenry12](https://discuss.elastic.co/u/chenry12)\
**Post date:** [January 10, 2013, 6:05pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/4 "2013-01-10T18:05:47Z")

</div>

Oups there is a mistake, read OpenStack instead of Cloudstack.

Hi David,  
If you base your answer with the web link with api , that's good for me 🙂

Thanks for your answer and the tuto.

--

---

<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:** [January 13, 2013, 9:47am UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/5 "2013-01-13T09:47:57Z")

</div>

Can you explain why a river?

From what I understand, OpenStack is a cloud service like Amazon AWS, not  
really a source for a river.

There is a cloud-aws plugin, which supersedes the zen discovery (and and  
obsoleted S3 shared storage) but that is all I know about ES cloud support  
yet.

I'm very enthusiastic about JClouds [http://www.jclouds.org](http://www.jclouds.org)

"jclouds tests support of 30 cloud providers and cloud software stacks  
including Amazon, GoGrid, Ninefold, vCloud, OpenStack, and Azure."

By managing compute nodes and blob stores, JClouds could be the starting  
point for an ES launch tool and a discovery plugin (maybe based on the  
zookeeper plugin at [https://github.com/sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper)) for  
more than 30 cloud infrastructures!

If someone would like to start work on this, it would be very, very  
exciting.

My favorite is also OpenStack since everybody can build OpenStack private  
clouds because it is open source.

Cheers,

Jörg

--

---

<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:** [January 13, 2013, 9:55am UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/6 "2013-01-13T09:55:18Z")

</div>

Sorry, I forgot Apache Whirr [http://whirr.apache.org/](http://whirr.apache.org/) where Elasticsearch  
deployment on AWS and Rackspace is supported, but it is not clear to me how  
JClouds is used.

Jörg

--

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 13, 2013, 10:00am UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/7 "2013-01-13T10:00:09Z")

</div>

Hello Jörg,

I think he stores files (oOo, Office, pdf...) on openstack swift space (a dropbox like feature) and want to index them.  
He did not say that he wants to run ES on a openstack cloud.

So, I suppose that a river makes sense here.

My 2 cents.

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 janv. 2013 à 10:47, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) a écrit :

Can you explain why a river?

From what I understand, OpenStack is a cloud service like Amazon AWS, not really a source for a river.

There is a cloud-aws plugin, which supersedes the zen discovery (and and obsoleted S3 shared storage) but that is all I know about ES cloud support yet.

I'm very enthusiastic about JClouds [http://www.jclouds.org](http://www.jclouds.org)

"jclouds tests support of 30 cloud providers and cloud software stacks including Amazon, GoGrid, Ninefold, vCloud, OpenStack, and Azure."

By managing compute nodes and blob stores, JClouds could be the starting point for an ES launch tool and a discovery plugin (maybe based on the zookeeper plugin at [https://github.com/sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper)) for more than 30 cloud infrastructures!

If someone would like to start work on this, it would be very, very exciting.

My favorite is also OpenStack since everybody can build OpenStack private clouds because it is open source.

Cheers,

## Jörg

--

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 13, 2013, 11:35am UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/8 "2013-01-13T11:35:59Z")

</div>

Hey Christophe,

Have a look at this nice blog post from Luca: [http://blog.trifork.nl/2013/01/10/how-to-write-an-elasticsearch-river-plugin/](http://blog.trifork.nl/2013/01/10/how-to-write-an-elasticsearch-river-plugin/)

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 janv. 2013 à 11:00, David Pilato [david@pilato.fr](mailto:david@pilato.fr) a écrit :

> Hello Jörg,
> 
> I think he stores files (oOo, Office, pdf...) on openstack swift space (a dropbox like feature) and want to index them.  
> He did not say that he wants to run ES on a openstack cloud.
> 
> So, I suppose that a river makes sense here.
> 
> My 2 cents.
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 13 janv. 2013 à 10:47, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) a écrit :
> 
> Can you explain why a river?
> 
> From what I understand, OpenStack is a cloud service like Amazon AWS, not really a source for a river.
> 
> There is a cloud-aws plugin, which supersedes the zen discovery (and and obsoleted S3 shared storage) but that is all I know about ES cloud support yet.
> 
> I'm very enthusiastic about JClouds [http://www.jclouds.org](http://www.jclouds.org)
> 
> "jclouds tests support of 30 cloud providers and cloud software stacks including Amazon, GoGrid, Ninefold, vCloud, OpenStack, and Azure."
> 
> By managing compute nodes and blob stores, JClouds could be the starting point for an ES launch tool and a discovery plugin (maybe based on the zookeeper plugin at [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper)) for more than 30 cloud infrastructures!
> 
> If someone would like to start work on this, it would be very, very exciting.
> 
> My favorite is also OpenStack since everybody can build OpenStack private clouds because it is open source.
> 
> Cheers,
> 
> ## Jörg
> 
> --

--

---

<div class="post-metadata">

**Author:** ![chenry12](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@chenry12](https://discuss.elastic.co/u/chenry12)\
**Post date:** [January 14, 2013, 2:56pm UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/9 "2013-01-14T14:56:33Z")

</div>

Thanks Jörg and David for your contribution.

This is exactly what explains David.  
My need is to collect the documents (pdf, office, ...) stored in containers  
swift and index content in Elasticsearch.

Indeed, it does not seem very complicated to write a river. Thank you for  
this link.

--

---

<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:56am UTC](https://discuss.elastic.co/t/cloudstack-swift-river/10297/10 "2017-07-06T02:56:37Z")

</div>


