{"id":1571,"date":"2016-09-20T12:15:27","date_gmt":"2016-09-20T16:15:27","guid":{"rendered":"http:\/\/blog.domb.net\/?p=1571"},"modified":"2017-05-18T11:45:28","modified_gmt":"2017-05-18T15:45:28","slug":"register-hosts-to-satellite6-via-cloudforms-and-ansible-tower-part-1","status":"publish","type":"post","link":"https:\/\/blog.domb.net\/?p=1571","title":{"rendered":"Register hosts to Satellite6 via CloudForms and Ansible Tower part 1"},"content":{"rendered":"

CloudForms is the single pane of glass for virtual machines, cloud instances, and baremetal servers provisioned via Satellite 6. Since we added support for Ansible Tower we can do a lot of magic as we can now call Ansible Tower via CloudForms. What does that mean for operations and orchestration?<\/p>\n

Let\u2019s say we have the following use case:<\/p>\n

We have a host or multiple hosts which need to be registered to Red Hat Satellite 6 and update to the latest errata. We also want to be able to choose if puppet should be used as a configuration management tool or if the host will be managed by Ansible Tower. <\/p>\n

CloudForms gives you endless possibilities on how you could achieve this registration. The blog series will walk you through the steps on how to build the above use case through the out of the box integration with Ansible Tower by Red Hat and Red Hat Satellite 6.<\/p>\n

Part 1<\/strong> Will walk you through how to enable the inventory synchronization between CloudForms and Ansible Tower and how to create the sat6register job which will be executed from CloudForms.
\nPart 2<\/strong> Will walk you through how to auto generate a service dialog in CloudForms from an Ansible Tower Job and expose it as a self service catalog item which can be ordered via self service portal.
\nPart 3 <\/strong>Will walk you through the creation of a custom button sat6register under the VM section which enable you to register a host from the administration ui.
\nPart 4<\/strong> Will walk you through the customization of the service dialog to make it dynamic and grab information via api from Red Hat Satellite 6.<\/p>\n

Step 1<\/strong> Login to Ansible Tower with an admin user
\n\"towerlogin\"<\/p>\n

Step 2 <\/strong> Click on the project tab on the top left
\n\"project\"
\nStep 3<\/strong> Then click +ADD
\n\"add\"<\/p>\n

Step 4<\/strong> Fill in the following information
\nNAME:<\/em> Can be arbitrary
\nDESCRIPTION: <\/em>I like to see the giturl of the project there so https:\/\/github.com\/ldomb\/ansible_tower_roles
\nSCM TYPE:<\/em>git
\nSCM URL:<\/em>https:\/\/github.com\/ldomb\/ansible_tower_roles
\nORGANIZATION: <\/em>In my case default
\n\"project1\"
\nStep 5<\/strong> Once done hit save
\n\"save\"
\nand go back to the project tab
\n\"project\"
\nwhere you will see the following
\n\"projecttower\"<\/p>\n

Step 6<\/strong> Create machine credentials for the hosts you would like to access via ssh. Click on settings
\n\"settings\"
\ncredentials
\n\"credentials\"
\n+ADD
\n\"add\"<\/p>\n

Fill in the information for your host. In my case I did use username password. In your case it could be an ssh-key. The vault password is used to decrypt the admin_pass password for the Red Hat Satellite 6 connection. You can learn how to set the initial vault password it here:
\nhttp:\/\/docs.ansible.com\/ansible\/playbooks_vault.html<\/a>
\n\"selection_020\"
\nclick +ADD
\n\"add\"<\/p>\n

Step 7<\/strong> Create the credential to connect to your Red Hat CloudForms appliance. We will need those when we setup the inventory sync between Ansible Tower and Red Hat CloudForms. Repeat Step 6 (You won’t need a vault password here). As a type choose CloudForms
\n\"cfmetower\"
\nand hit +ADD
\n\"add\"
\nStep 8<\/strong> Now we are ready to go and create an inventory for the hosts which are in CloudForms. We need this as ansible is going to ask us about the inventory if we create the job template. Click on the inventory tab
\n\"inventoryscripts\"
\nand click the +ADD button.
\n\"add\"
\nFill in the following values
\n\"cfmeinventory\"
\nand hit save. You will get redirected to the groups page. Here is where you could add group variables for the CloudForms inventory. <\/p>\n

\"save\"
\nClick the ADD Group button and
\n\"addgroup\"
\nfill in the following values
\n\"cfmegroup\"
\nand hit save
\n\"save\"<\/p>\n

Step 9 <\/strong>Now Sync the inventory on the bottom left corner of the page
\n\"sync\"
\nYou will get redirected to the following page. Once the sync is finished you should see a screen similar to this if you have hosts within CloudForms.
\n\"syncsuccessfull\"<\/p>\n

Step 10<\/strong> We are finally ready to create the job in Ansible Tower. Click on the Job Template tab
\n\"jobtemplate\"
\nclick +ADD
\n\"add\"
\nand enter the following values for the job template
\n\"jobtemplatesat6\"<\/p>\n

Step 11. Add the following values to the EXTRA VARIABLE field
\nsat6_ip: <\/em> $HOST_IP_ADDR
\nsat6_fqdn: <\/em> $HOST_FQDN
\nadmin_user:<\/em> admin
\norg:<\/em> redhat
\nloc:<\/em> nyc
\nhostgroup:<\/em> false
\nactivationkey:<\/em> ak-Reg_To_Library_soe_no_puppet<\/p>\n

Make sure you create a password in the \/roles\/sat6register\/group_vars\/all\/vault file as it will be looked up by \/roles\/sat6register\/group_vars\/all\/vars file containing admin_pass: \u201c{{ vault_admin_pass}}\u201d.
\nYou also find instructions on how to do this here:
\nhttps:\/\/galaxy.ansible.com\/ldomb\/sat6register\/<\/a>
\n\"selection_022\"<\/p>\n

Make sure that the box Prompt on launch is checked<\/strong>. This is very important as if you don\u2019t do this right you will NOT be able to override any extra_vars from CloudForms when executing the job template.
\n. We are now done with the Ansible Tower setup. Let’s go to part 2 which will explain howto setup CloudForms to execute this Job Template.<\/p>\n","protected":false},"excerpt":{"rendered":"

CloudForms is the single pane of glass for virtual machines, cloud instances, and baremetal servers provisioned via Satellite 6. Since we added support for Ansible Tower we can do a lot of magic as we can now call Ansible Tower via CloudForms. What does that mean for operations and orchestration? Let\u2019s say we have the…<\/p>\n","protected":false},"author":2,"featured_media":2048,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[64,37,6],"tags":[71,29,68],"class_list":["post-1571","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ansible","category-cloudforms","category-puppet","tag-ansible-tower","tag-cloudforms","tag-satellite6"],"_links":{"self":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1571"}],"version-history":[{"count":46,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1571\/revisions"}],"predecessor-version":[{"id":1788,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1571\/revisions\/1788"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/media\/2048"}],"wp:attachment":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}