# Design practices for hosting multiple clusters/on-demand cluster creation? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 8, 2014, 1:01am UTC](https://discuss.elastic.co/t/design-practices-for-hosting-multiple-clusters-on-demand-cluster-creation/15133 "2014-01-08T01:01:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Josh\_Harrison](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@Josh\_Harrison](https://discuss.elastic.co/u/Josh_Harrison)\ **Post date:** [January 8, 2014, 1:01am UTC](https://discuss.elastic.co/t/design-practices-for-hosting-multiple-clusters-on-demand-cluster-creation/15133/1 "2014-01-08T01:01:29Z")
While ES is still in a pre deployment stage at my job, there is growing interest in it. For various reasons, a monster cluster holding everyone's stuff is simply not possible. Individual projects require complete control over their data and the culture and security requirements here are such that doing something like always naming project 1's indexes PROJECT\_1\_ will not fly. We have a fairly beefy hadoop cluster hosting our content currently, along with a separate head node acting as the master. In this situation, is it simply a matter of starting up new processes on each node pointed at different configuration profiles and tying specific ports to specific projects/clusters? Basically, is there an established way to build on-demand clusters, given a set of resources? We'll layer something in front of it to deal with access control/etc. Thanks! -Josh -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ad2695f7-d1a2-4036-82b2-58bddf349681%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ad2695f7-d1a2-4036-82b2-58bddf349681%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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 8, 2014, 7:23am UTC](https://discuss.elastic.co/t/design-practices-for-hosting-multiple-clusters-on-demand-cluster-creation/15133/2 "2014-01-08T07:23:51Z")
You could look at chef cookbook: > **[elastic/cookbook-elasticsearch](https://github.com/elastic/cookbook-elasticsearch)** > > cookbook-elasticsearch - Chef cookbook for Elasticsearch [http://www.elasticsearch.org/tutorials/deploying-elasticsearch-with-chef-solo/](http://www.elasticsearch.org/tutorials/deploying-elasticsearch-with-chef-solo/) Does it help? -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 8 janv. 2014 à 02:01, Josh Harrison [hijakk@gmail.com](mailto:hijakk@gmail.com) a écrit : While ES is still in a pre deployment stage at my job, there is growing interest in it. For various reasons, a monster cluster holding everyone's stuff is simply not possible. Individual projects require complete control over their data and the culture and security requirements here are such that doing something like always naming project 1's indexes PROJECT\_1\_ will not fly. We have a fairly beefy hadoop cluster hosting our content currently, along with a separate head node acting as the master. In this situation, is it simply a matter of starting up new processes on each node pointed at different configuration profiles and tying specific ports to specific projects/clusters? Basically, is there an established way to build on-demand clusters, given a set of resources? We'll layer something in front of it to deal with access control/etc. ## Thanks! -Josh 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ad2695f7-d1a2-4036-82b2-58bddf349681%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ad2695f7-d1a2-4036-82b2-58bddf349681%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/535D6769-0469-4BF8-9840-C67FA81CFD89%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/535D6769-0469-4BF8-9840-C67FA81CFD89%40pilato.fr). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 1:57am UTC](https://discuss.elastic.co/t/design-practices-for-hosting-multiple-clusters-on-demand-cluster-creation/15133/3 "2017-07-06T01:57:59Z")
Closed on July 6, 2017, 1:57am UTC