How to add new add-on software to elasticluster?  #687

Activity

1. riccardomurri commented on Nov 18, 2020

   

   riccardomurri

   on Nov 18, 2020

   Contributor

   More actions

   Hello @weizhu365 and thanks for your interest in ElastiCluster!

   I think there are two options to add new roles to be used by ElastiCluster:

   1. Create your own .yml file with the playbook, then use it with elasticluster setup my-cluster -- myplaybook.yml

      Note that, to save time, this requires that you create a cluster in two stages:

      • first create the cluster but do not configure it:

        elasticluster start --no-setup my-cluster

      • then set it up with the additional playbook(s):

        elasticluster setup my-cluster -- myplaybook.yml

      Note that:

      • You can have more than one additional playbook file; they will be run in the order given.
      • Nothing bad will happen if you do a normal elasticluster start my-cluster (i.e., without the --no-setup option) and then a elasticluster setup -- myplaybook.yml; it's just that the standard ElastiCluster playbooks will run twice.

   2. Install ElastiCluster from sources, navigate to the source directory, then cd elasticluster/share/playbooks and add your own roles in the roles directory. You can then call them from the gridengine.yml file (shortcut), or:

      • add a new .yml file for your new role (like the rstudio.yml file); the purpose of this file is to just call the additional role or roles for hosts in a specific group (let's say, group mysoftware);
      • add an include: statement for this new .yml file in main.yml
      • in the [setup/...] section of the config file, add the group mysoftware to all hosts where you want the software installed.

   Whichever way you choose, if the software can be freely installed, I would be happy to work on a PR for making it available to other users of ElastiCluster!
2. weizhu365 commented on Nov 18, 2020

   

   weizhu365

   on Nov 18, 2020 via email

   Last edited by weizhu365

   Author

   More actions

   Riccardo; Thank you for the reply, which is very helpful. Actually, I had figured out to use the solution two, following the Rstudio example. Nevertheless, your reply makes me more confident. :-) The solution 1 is new to me. The software to be installed are all open-source, and I believe that a general solution like this is useful to all ElastiCluster users. Best, Wei

   …

   On Nov 18, 2020, at 3:25 PM, Riccardo Murri ***@***.***> wrote: Hello @weizhu365 and thanks for your interest in ElastiCluster! I think there are two options to add new roles to be used by ElastiCluster: • Create your own .yml file with the playbook, then use it with elasticluster setup my-cluster -- myplaybook.yml Note that, to save time, this requires that you create a cluster in two stages: • first create the cluster but do not configure it: elasticluster start --no-setup my-cluster • then set it up with the additional playbook(s): elasticluster setup my-cluster -- myplaybook.yml Note that: • You can have more than one additional playbook file; they will be run in the order given. • Nothing bad will happen if you do a normal elasticluster start my-cluster (i.e., without the --no-setup option) and then a elasticluster setup -- myplaybook.yml; it's just that the standard ElastiCluster playbooks will run twice. • Install ElastiCluster from sources, navigate to the source directory, then cd elasticluster/share/playbooks and add your own roles in the roles directory. You can then call them from the gridengine.yml file (shortcut), or: • add a new .yml file for your new role (like the rstudio.yml file); the purpose of this file is to just call the additional role or roles for hosts in a specific group (let's say, group mysoftware); • add an include: statement for this new .yml file in main.yml • in the [setup/...] section of the config file, add the group mysoftware to all hosts where you want the software installed. Whichever way you choose, if the software can be freely installed, I would be happy to work on a PR for making it available to other users of ElastiCluster! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.