bluechi icon indicating copy to clipboard operation
bluechi copied to clipboard

Minimize number of nodes in integration tests by having bluechi-agent running on controller node

Open mwperina opened this issue 11 months ago • 2 comments

Please describe what you would like to see

Currently we use one node only for bluechi-controller and one or more other nodes for bluechi-agents. But that increases the number of nodes required for each test and make test suite more resource hungry. So having bluechi-agent configured on controller node would decrease the number of required nodes and thus making the suite faster and less resource hungry.

Please describe the solution you'd like

  • Configure bluechi-agent on the controller node and use local socket connection between them
  • Go over all existing tests and try to move the functionality of a bluechi-agent on a separate node to the bluechi-agent on controller node

Please describe your use case

Minimizing the number of required nodes would make the suite less resource hungry and hopefully will also increase the chances to be able to reserve enough of real nodes in multi-host testing scenario

mwperina avatar Feb 07 '25 07:02 mwperina

will try to working on this one

dracher avatar Feb 07 '25 08:02 dracher

@dracher The controller accepts UDS and TCP connections by default. The agent connects via TCP by default, so you'd need to change the bluechi-agent config to:

[bluechi-agent]
ControllerAddress=unix:path=/run/bluechi/bluechi.sock

engelmi avatar Feb 07 '25 09:02 engelmi