Great. I never noticed that example on github. Thank you, Champak.
On Tuesday, December 18, 2018 at 9:59:27 AM UTC-5, Champak Reddy wrote: > > Hi, > > I had asked a slightly different but pertinent question earlier this year: > https://groups.google.com/forum/#!topic/elasticluster/Oi5ECP7DgOA > > Cheers, > Champak > > > > On Tue, 18 Dec 2018 at 15:43, Manuele Simi <[email protected] > <javascript:>> wrote: > >> With a second thought I realized that your requirement makes sense. You >> may have different parts of your jobs that have different requirements on >> the execution worker. >> >> Let's wait for a reply from people @ elasticluster. >> >> On Tuesday, December 18, 2018 at 9:34:43 AM UTC-5, Manuele Simi wrote: >>> >>> >>> It is unusual to have different flavors for the compute nodes. They are >>> workers for the same cluster and I expect they are interchangeable. Or at >>> least that's the rationale I use to create my clusters on the cloud. >>> >>> But probably the authors of elasticluster (and I'm not) have a better >>> answer. >>> >>> On Tuesday, December 18, 2018 at 9:23:25 AM UTC-5, Orxan Shibliyev wrote: >>>> >>>> Thanks for the reply. I just realized submitting a job with 1 node with >>>> slurm, launches compute001 although I did not specify the node. Seems like >>>> elasticluster does not intend to use frontend for computations. I don't >>>> know if should I ask this question in separate post but is it possible to >>>> launch the high-memory requiring job on frontend instead of compute node? >>>> If this is not possible, then how can I make two sections for compute >>>> nodes >>>> instead of sectioning compute and frontend? >>>> >>>> On Tue, Dec 18, 2018 at 1:13 PM Manuele Simi <[email protected]> >>>> wrote: >>>> >>>>> Yes, it is possible. >>>>> >>>>> You need to define a cluster/<name>/<group> sections that override the >>>>> cluster/<name> section. >>>>> >>>>> In the following example I create specific configurations (with their >>>>> own flavor) for the nodes in the compute and frontend groups of a cluster >>>>> named "gridengine". >>>>> >>>>> # Cluster Section >>>>> *[cluster/gridengine]* >>>>> ... >>>>> *frontend_nodes=1* >>>>> *compute_nodes=3* >>>>> >>>>> # Compute node section >>>>> *[cluster/gridengine/compute]* >>>>> *flavor=n1-highcpu-2* >>>>> ... >>>>> >>>>> # Frontend node section >>>>> *[cluster/gridengine/frontend]* >>>>> *flavor=n1-standard-64* >>>>> ... >>>>> >>>>> On Tue, Dec 18, 2018 at 8:46 AM Orxan Shibliyev <[email protected]> >>>>> wrote: >>>>> >>>>>> Is it possible to take different flavors for frontend and compute >>>>>> nodes? I want high memory machine for frontend and lower memory for >>>>>> computes. I use GCE machines. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "elasticluster" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >> You received this message because you are subscribed to the Google Groups >> "elasticluster" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
