AWX 19.4.0 how data is copied between receptor workers

riadh hamdi

unread,

Nov 5, 2021, 4:40:52 AM11/5/21

to awx-p...@googlegroups.com, riadh hamdi

Hello ,

I have installed the latest version of AWX and I see that when launching a job a work is detected on receptor nodes (here my execution node is tools_receptor_1).

After launching the job template from the UI

On control plane when launching the command receptorctl work list I am getting the following output

#docker exec -it tools_awx_1 receptorctl work list

{'lsTyGQyh': {'Detail': 'Running: PID 255',
'ExtraData': {'Expiration': '0001-01-01T00:00:00Z',
'LocalCancelled': False,
'LocalReleased': False,
'RemoteNode': 'receptor-1',
'RemoteParams': {'params': '--private-data-dir=/tmp/awx_43_8xmv19jd '
'--delete'},
'RemoteStarted': True,
'RemoteUnitID': 'SOWTu5xR',
'RemoteWorkType': 'ansible-runner',
'SignWork': True,
'TLSClient': ''},
'State': 1,
'StateName': 'Running',
'StdoutSize': 0,
'WorkType': 'remote'}}

#docker exec -it tools_receptor_1 receptorctl work list

{'SOWTu5xR': {'Detail': 'Running: PID 255',
'ExtraData': {'Params': 'worker '
'--private-data-dir=/tmp/awx_43_8xmv19jd '
'--delete',
'Pid': 249},
'State': 1,
'StateName': 'Running',
'StdoutSize': 0,
'WorkType': 'ansible-runner'}}

I can see that the directory /tmp/awx_43_8xmv19jd was created on both the control plane (tools_awx_1) and the worker (tools_receptor_1).

So my question is how the directory content is copied between the two nodes ?

Do receptor copy the directory content before submitting the work ?

Many thanks.

RH

Vincent Rubiolo

unread,

Nov 8, 2021, 6:36:30 AM11/8/21

to AWX Project

Hi RH,

Interesting to see that Receptor is used by AWX for job distribution ...

I have not dived into the subject but could it be that the temp dir is actually a shared volume between the containers? That would allow the data transfer ...

HTH,

Vincent

Stefan Coussens

unread,

Nov 10, 2021, 10:26:42 AM11/10/21

to Vincent Rubiolo, AWX Project

I believe this is setting up what will eventually be the ansible automation mesh they talked about at ansiblefest

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/c4d77262-1fab-49e3-8d68-5d66e3f88ca8n%40googlegroups.com.

Vincent Rubiolo

unread,

Nov 12, 2021, 8:01:31 AM11/12/21

to AWX Project

On Wednesday, November 10, 2021 at 4:26:42 PM UTC+1 stefan....@gmail.com wrote:

I believe this is setting up what will eventually be the ansible automation mesh they talked about at ansiblefest

Oh interesting indeed. I need to watch those sessions. Is it the talk titled "Automation at Large: Managing Ansible Tower on a Massive Scale" that you were referring to?

Vincent

Stefan Coussens

unread,

Nov 12, 2021, 9:57:14 AM11/12/21

to Vincent Rubiolo, AWX Project

I don't know the exact talk but it was something about a banana stand and separating the control and execution planes (and a replacement for isolated nodes)

--

You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/ed34b764-6435-49f0-b86f-0e28101dd3dbn%40googlegroups.com.

Vincent Rubiolo

unread,

Nov 16, 2021, 6:01:57 AM11/16/21

to AWX Project

On Friday, November 12, 2021 at 3:57:14 PM UTC+1 stefan....@gmail.com wrote:

I don't know the exact talk but it was something about a banana stand and separating the control and execution planes (and a replacement for isolated nodes)