Add peers_from_control_nodes to ReceptorAddress
- write_receptor_config peers to ReceptorAddress entries
that have peers_from_control_nodes enabled
- peers_from_control_nodes and listener_port removed from Instance model
- peers_from_control_nodes added to ReceptorAddress model
- ReceptorAddress is now unique by address and protocol combination
- Write receptor config task is dispatched upon ReceptorAddress creation
or deletion, and when control node is first created
- InstanceLinkSerializer adds a target_address field and has logic
to grab the instance hostname associated with the peered ReceptorAddress
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Showing
- awx/api/serializers.py 28 additions, 23 deletionsawx/api/serializers.py
- awx/main/management/commands/add_receptor_address.py 2 additions, 2 deletionsawx/main/management/commands/add_receptor_address.py
- awx/main/management/commands/provision_instance.py 3 additions, 8 deletionsawx/main/management/commands/provision_instance.py
- awx/main/managers.py 2 additions, 10 deletionsawx/main/managers.py
- awx/main/migrations/0188_inbound_hop_nodes.py 59 additions, 0 deletionsawx/main/migrations/0188_inbound_hop_nodes.py
- awx/main/models/ha.py 35 additions, 21 deletionsawx/main/models/ha.py
- awx/main/models/receptor_address.py 6 additions, 24 deletionsawx/main/models/receptor_address.py
- awx/main/tasks/receptor.py 24 additions, 30 deletionsawx/main/tasks/receptor.py
- awx/main/tasks/system.py 1 addition, 1 deletionawx/main/tasks/system.py
Loading
Please register or sign in to comment