thanks for replying.
I really wish I don’t have to manually configure an SGE or SLURM scheduler my onw. That’s why I was looking for a configured scheduler!
Anyway, I did not create an Alces Flight cluster through CloudFormation: I launched one alces flight instance, configured as “master” node. Then I planned to add more Alces flight nodes in an autoscaling group, configure them as slaves, and orchestrate this small cluster using the grid scheduler shipped with Alces Flight. But that service (gridscheduler) is not actually installed: when I type
alces services avail, the
base/gridscheduler entry is not marked as available.
I tried to install and enable it: installation went ok, but when I tried to enable it, i got error messages like:
`$ alces service enable base/gridscheduler`
`alces service enable: serviceware not installed: base`
$ alces service enable gridscheduler
alces service enable: service does not provide component: gridscheduler/base
Searching in the proper directory, I found that the executables were installed, but the scheduler isn’t configured and a
qsub command gives:
Unable to initialize environment because of error: Please set the environment
I suspect this is all related to the fact that creating a single instance without a proper CloudFormation design impairs some functionalities, such as job scheduler configuration: might it be the case?