Good Day,
I have just been testing the Slurm roll with the Rocks 6.2 beta and it appears the "var" group of commands (add/list/set/remove) has been removed so the following no longer work.
/opt/rocks/bin/rocks add var slurm_nodename DEFAULT value="State=UNKNOWN"
/opt/rocks/bin/rocks add var slurm_partition CLUSTER value="Default=yes State=UP"
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your error report.
I will install rocks 6.2 beta, to find another solution.
Best regards,
Werner
On 04/08/2015 03:31 PM, James wrote:
Good Day,
I have just been testing the Slurm roll with the Rocks 6.2 beta and it appears the "var" group of commands (add/list/set/remove) has been removed so the following no longer work.
/opt/rocks/bin/rocks add var slurm_nodename DEFAULT value="State=UNKNOWN"
/opt/rocks/bin/rocks add var slurm_partition CLUSTER value="Default=yes State=UP"
At first I will wait a short time for the answer of the rocks development team, why the var commands are removed.
I will install rocks 6.2 beta, and I will find another solution.
I think, that I can deliver a stable slurm-roll one week after rocks-62 has been released.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Werner.
The roll does seem to install OK on Rocks 6.2 beta. The only thing that generated warnings were the two rocks add var lines. I have attached the slurm roll install log.
Whether the lack of these two lines affects functionality I don't know.
One side suggestion, for the installation it assumes the /etc/yum.conf : assumeyes=1 is enabled. Often this is disabled on the Frontend. If disabled the installer fails with:
Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Exiting on user Command
sh: line 4: syntax error near unexpected token `|'
Could you please change the yum install lines to include a -y to set it to assume yes? That way it will work regardless of what the user has modified.
e.g. yum install -y hwloc
The lines in var are needed for rocks sync slurm, but I can also put
these lines
in a static file. The install file is not a static file, but is created
from rocks
on the fly from the node xml files.
I will see
Best regards
Werner
On 04/09/2015 12:25 AM, James wrote:
Thanks Werner.
The roll does seem to install OK on Rocks 6.2 beta. The only thing that generated warnings were the two rocks add var lines. I have attached the slurm roll install log.
Whether the lack of these two lines affects functionality I don't know.
One side suggestion, for the installation it assumes the /etc/yum.conf : assumeyes=1 is enabled. Often this is disabled on the Frontend. If disabled the installer fails with:
Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Exiting on user Command
sh: line 4: syntax error near unexpected token `|'
Could you please change the yum install lines to include a -y to set it to assume yes? That way it will work regardless of what the user has modified.
e.g. yum install -y hwloc
What is the staus with this? It seems pretty much none of the Rocks slurm management is working since "var" was removed. So anyone installing the roll and following the instructions will get very confused. I don't see any threads started about what do do with Rocks 6.2 and the slurm roll. It appears you have to abandon everything to do with rocks sync slurm or rocks add var slurm_partition. At the moment if you set up slurm the normal way and then rocks sync slurm, it will undo everything you did and return you to a single default CLUSTER queue with no QoS. I have no looked at 411 yet for slurm related stuff.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good Day,
I have just been testing the Slurm roll with the Rocks 6.2 beta and it appears the "var" group of commands (add/list/set/remove) has been removed so the following no longer work.
/opt/rocks/bin/rocks add var slurm_nodename DEFAULT value="State=UNKNOWN"
/opt/rocks/bin/rocks add var slurm_partition CLUSTER value="Default=yes State=UP"
Cheers
Hi,
Thank you for your error report.
I will install rocks 6.2 beta, to find another solution.
Best regards,
Werner
On 04/08/2015 03:31 PM, James wrote:
At first I will wait a short time for the answer of the rocks development team, why the var commands are removed.
I will install rocks 6.2 beta, and I will find another solution.
I think, that I can deliver a stable slurm-roll one week after rocks-62 has been released.
Thanks Werner.
The roll does seem to install OK on Rocks 6.2 beta. The only thing that generated warnings were the two rocks add var lines. I have attached the slurm roll install log.
Whether the lack of these two lines affects functionality I don't know.
One side suggestion, for the installation it assumes the /etc/yum.conf : assumeyes=1 is enabled. Often this is disabled on the Frontend. If disabled the installer fails with:
Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Exiting on user Command
sh: line 4: syntax error near unexpected token `|'
Could you please change the yum install lines to include a -y to set it to assume yes? That way it will work regardless of what the user has modified.
e.g. yum install -y hwloc
Thanks for this great roll,
James
Hi,
The lines in var are needed for rocks sync slurm, but I can also put
these lines
in a static file. The install file is not a static file, but is created
from rocks
on the fly from the node xml files.
I will see
Best regards
Werner
On 04/09/2015 12:25 AM, James wrote:
What is the staus with this? It seems pretty much none of the Rocks slurm management is working since "var" was removed. So anyone installing the roll and following the instructions will get very confused. I don't see any threads started about what do do with Rocks 6.2 and the slurm roll. It appears you have to abandon everything to do with rocks sync slurm or rocks add var slurm_partition. At the moment if you set up slurm the normal way and then rocks sync slurm, it will undo everything you did and return you to a single default CLUSTER queue with no QoS. I have no looked at 411 yet for slurm related stuff.