Red Hat Satellite 6.3 introduces integration with Ansible Tower. One of the key enhancements is the ability to add a snippet to provisioning templates that allows administrators to configure hosts provisioned through Satellite using Ansible Tower. An example must be added to the Provisioning Guide that outlines how to create this snippet, and referenced in the new section created in BZ#1454562.
*** Bug 1527206 has been marked as a duplicate of this bug. ***
Assigning to Clifton for review.
Correct, Following snippets have been added to Satellite 6.3 for Ansible tower integration with satellite6.3 a) ansible_provisioning_callback b) ansible_tower_callback_script c) ansible_tower_callback_service Please note that these snippets are being used by Satellite Kikcstart default and Satellite kickstart default Finish templates. In case of network-based provisioning, "Satellite kickstart default template" is updated w/ a call to "ansible_provisioning_callback" which internally calls "ansible_tower_callback_service: snippet for all hosts based on systemd( for rhel7 hosts). For other hosts(rhel6) and image based provisioning, "Satellite Kickstart Default Finish" template is updated with "ansible_tower_callback_script" and that copies the script on hosts under "/root/ansible_provisioning_call.sh" and performs the provisioning callback. For a successful Integration user needs to define following Parameters in Satellite6.3 at host/hostgroup level. ansible_tower_provisioning => true ansible_tower_fqdn => TOWER_FQDN ansible_job_template_id => TEMPLATE_ID(get it from Tower) ansible_host_config_key => CONFIG_KEY(get it from Tower Job template) Referenced BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1468717#c19
(In reply to Sachin Ghai from comment #5) > Correct, Following snippets have been added to Satellite 6.3 for Ansible > tower integration with satellite6.3 > > a) ansible_provisioning_callback > b) ansible_tower_callback_script > c) ansible_tower_callback_service > > > Please note that these snippets are being used by Satellite Kikcstart > default and Satellite kickstart default Finish templates. > > In case of network-based provisioning, "Satellite kickstart default > template" is updated w/ a call to "ansible_provisioning_callback" which > internally calls "ansible_tower_callback_service: snippet for all hosts > based on systemd( for rhel7 hosts). > > For other hosts(rhel6) and image based provisioning, "Satellite Kickstart > Default Finish" template is updated with "ansible_tower_callback_script" and > that copies the script on hosts under "/root/ansible_provisioning_call.sh" > and performs the provisioning callback. > > For a successful Integration user needs to define following Parameters in > Satellite6.3 at host/hostgroup level. > > ansible_tower_provisioning => true > ansible_tower_fqdn => TOWER_FQDN > ansible_job_template_id => TEMPLATE_ID(get it from Tower) > ansible_host_config_key => CONFIG_KEY(get it from Tower Job template) > > Referenced BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1468717#c19 Hi Sachin, Thank you for the detailed information and link to BZ#1468717. Regards,
Resetting the assignee and QA contact.
Agreed. I retract my attempts to push this forward. We have a published version, let's step back and complete QA properly, and we'll republish when we have Sachin's comments and a clean bill of QA-health. Apologies for the confusion - I got GA-fever. Thanks, Steve
These changes are live on the customer portal, see https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/managing_hosts/chap-red_hat_satellite-managing_hosts-integrating_satellite_and_ansible_tower