weka / tools

GNU General Public License v3.0
20 stars 8 forks source link

wekaconfig "resources_generator.py" --net parameter is blank #262

Open Mars-weka opened 9 months ago

Mars-weka commented 9 months ago

In the config.sh generated by wekaconfig, in the Resources generator section, only the first few nodes have the correct NIC information after --net, while the rest of the nodes are blank.

For example, in a setup of 296 machines, only the first ten have the correct --net information, and the rest are blank.

wait echo Running Resources generator on host obj-x0x-01.dpe-a para ${PARA} ssh obj-x0x-01.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.4/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-03.dpe-a para ${PARA} ssh obj-x0x-03.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.5/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-05.dpe-a para ${PARA} ssh obj-x0x-05.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.6/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-07.dpe-a para ${PARA} ssh obj-x0x-07.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.7/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-09.dpe-a para ${PARA} ssh obj-x0x-09.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.8/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-11.dpe-a para ${PARA} ssh obj-x0x-11.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.9/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-13.dpe-a para ${PARA} ssh obj-x0x-13.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.10/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-15.dpe-a para ${PARA} ssh obj-x0x-15.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.11/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-17.dpe-a para ${PARA} ssh obj-x0x-17.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.12/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-19.dpe-a para ${PARA} ssh obj-x0x-19.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.13/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x0x-21.dpe-a para ${PARA} ssh obj-x0x-21.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net bond0/1.1.1.14/27/1.1.1.1 --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-01.dpe-a para ${PARA} ssh obj-x3x-01.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-05.dpe-a para ${PARA} ssh obj-x3x-05.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-07.dpe-a para ${PARA} ssh obj-x3x-07.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-09.dpe-a para ${PARA} ssh obj-x3x-09.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-11.dpe-a para ${PARA} ssh obj-x3x-11.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB echo Running Resources generator on host obj-x3x-13.dpe-a para ${PARA} ssh obj-x3x-13.dpe-a sudo /tmp/resources_generator.py -f --path /tmp --net --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB

Mars-weka commented 9 months ago

my workaround: a file that lists containing hostname, IP, subnet, and gateway. e.g. hosts_.list.txt

cat host_.list.txt

obj-x0x-01.dpe-a 1.1.1.4 27 1.1.1.1 obj-x0x-03.dpe-a 1.1.1.5 27 1.1.1.1 obj-x0x-05.dpe-a 1.1.1.6 27 1.1.1.1 obj-x0x-07.dpe-a 1.1.1.7 27 1.1.1.1 obj-x0x-09.dpe-a 1.1.1.8 27 1.1.1.1 obj-x0x-11.dpe-a 1.1.1.9 27 1.1.1.1

Then regenerate a new list

cat host_list.txt |awk '{printf "echo Running Resources generator on host %s\n", $1; printf "para %s ssh %s /tmp/resources_generator.py -f --path /tmp --net bond0/%s/%s/%s --compute-dedicated-cores 13 --drive-dedicated-cores 8 --frontend-dedicated-cores 2 --compute-memory 90GB\n", "${PARA}", $1, $2, $3, $4}'