Added parallel light compose config

[BrianSipos]

This refactors all ION to outside of ANMS project, with a volume mount on the host to share transport proxy socket between the ANMS and testenv projects.

Closes #169

[d-linko]

After deploying the light-compose file the amp-manager's refdm-proxy.service fails with error:

Jul 09 18:39:11 amp-manager refdm-proxy[79]: 2025-07-09T18:39:11.858449 T:203002B3FFFF0000 <ERROR> [proxy_cli.c:82:cace_amp_proxy_cli_real_connect] Failed to connect socket /var/tmp/nm/proxy.sock with errno 111
Jul 09 18:39:21 amp-manager refdm-proxy[79]: 2025-07-09T18:39:21.862803 T:203002B3FFFF0000 <INFO> [proxy_cli.c:78:cace_amp_proxy_cli_real_connect] Connecting to socket /var/tmp/nm/proxy.sock
Jul 09 18:39:21 amp-manager refdm-proxy[79]: 2025-07-09T18:39:21.862940 T:203002B3FFFF0000 <ERROR> [proxy_cli.c:82:cace_amp_proxy_cli_real_connect] Failed to connect socket /var/tmp/nm/proxy.sock with errno 111
Jul 09 18:39:32 amp-manager refdm-proxy[79]: 2025-07-09T18:39:32.864997 T:203002B3FFFF0000 <INFO> [proxy_cli.c:78:cace_amp_proxy_cli_real_connect] Connecting to socket /var/tmp/nm/proxy.sock
Jul 09 18:39:32 amp-manager refdm-proxy[79]: 2025-07-09T18:39:32.865047 T:203002B3FFFF0000 <ERROR> [proxy_cli.c:82:cace_amp_proxy_cli_real_connect] Failed to connect socket /var/tmp/nm/proxy.sock with errno 111
Jul 09 18:39:44 amp-manager refdm-proxy[79]: 2025-07-09T18:39:44.870152 T:203002B3FFFF0000 <INFO> [proxy_cli.c:78:cace_amp_proxy_cli_real_connect] Connecting to socket /var/tmp/nm/proxy.sock
Jul 09 18:39:44 amp-manager refdm-proxy[79]: 2025-07-09T18:39:44.870236 T:203002B3FFFF0000 <ERROR> [proxy_cli.c:82:cace_amp_proxy_cli_real_connect] Failed to connect socket /var/tmp/nm/proxy.sock with errno 111
Jul 09 18:39:56 amp-manager systemd[1]: refdm-proxy.service: start operation timed out. Terminating.
Jul 09 18:39:56 amp-manager systemd[1]: refdm-proxy.service: Failed with result 'timeout'.
Jul 09 18:39:56 amp-manager systemd[1]: Failed to start refdm-proxy.service - REFDM with proxy SEQPACKET socket transport.

and the core is unable to communicate with the amp-manager.

I think this might be due not having the shared sockdir volume but not 100% sure that that is the fix

[d-linko]

I just pushed changes that updated the sockdir to an external volume. Doing that fixed the proxy.service error and I was able to roundtrip sending a command to an agent from core and receive the report back

[BrianSipos]

I just pushed changes that updated the sockdir to an external volume. Doing that fixed the proxy.service error and I was able to roundtrip sending a command to an agent from core and receive the report back

Unfortunately doing this only works if the BP node is also running in a container to access the volume. The filesystem mount is needed to isolate the ANMS from whatever provides the socket, in a container or not. I will add an env variable to set the FS path with a default for system and override for test operation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud