fahclient 7.6.x ignore <power value="*"/>
Posted: Mon May 11, 2020 8:36 am
Hi all,
I saw many discussion about cpu control on fahclient 7.6.x but the argument is still not clear for me.
I work for a service provider and we are planning to automate deploy some hundreds Centos7/Fedora32 4 core VM instances on our cloud infrastructure (KVM based) but seems that the tag <power> on /etc/fahclient/config.xml is ignored from the client and this can be a probem for us.
I opened also one issue on github with all the details of the problem: "fahclient 7.6.x ignore <power value="*"/> - fahcontrol overwrite item on config.xml" but they closed the item and redirected me to this forum.
Someone can explain to me if:
- is possible to assign a power value (light/medium/high) to fahclient?
- is possible to avoid that the client take the full control of one Cpu and distribute the load to all available cpu?
For the moment we found a workaround for that (we define the number of CPU slots on config.xml to use 1 to 4 vCpu of the VM instance ( then we can set resource usage to 25%, 50%, 75%,100% ...) but is not the best and the job are always linked to a vCpu used at 100%
Any suggestion is welcome
Thanks in advance
Peter
I saw many discussion about cpu control on fahclient 7.6.x but the argument is still not clear for me.
I work for a service provider and we are planning to automate deploy some hundreds Centos7/Fedora32 4 core VM instances on our cloud infrastructure (KVM based) but seems that the tag <power> on /etc/fahclient/config.xml is ignored from the client and this can be a probem for us.
I opened also one issue on github with all the details of the problem: "fahclient 7.6.x ignore <power value="*"/> - fahcontrol overwrite item on config.xml" but they closed the item and redirected me to this forum.
Someone can explain to me if:
- is possible to assign a power value (light/medium/high) to fahclient?
- is possible to avoid that the client take the full control of one Cpu and distribute the load to all available cpu?
For the moment we found a workaround for that (we define the number of CPU slots on config.xml to use 1 to 4 vCpu of the VM instance ( then we can set resource usage to 25%, 50%, 75%,100% ...) but is not the best and the job are always linked to a vCpu used at 100%
Any suggestion is welcome
Thanks in advance
Peter