{"id":1594,"date":"2016-09-20T22:39:42","date_gmt":"2016-09-21T02:39:42","guid":{"rendered":"http:\/\/blog.domb.net\/?p=1594"},"modified":"2017-05-18T11:45:54","modified_gmt":"2017-05-18T15:45:54","slug":"register-hosts-to-satellite6-via-cloudforms-and-ansible-tower-part-2","status":"publish","type":"post","link":"https:\/\/blog.domb.net\/?p=1594","title":{"rendered":"Register hosts to Satellite6 via CloudForms and Ansible Tower part 2"},"content":{"rendered":"

This post will show you how to add Ansible Tower as a provider in CloudForms, discover and create a catalog item out of a job template we\u2019ve created and order the catalog item via self service portal.<\/p>\n

If you followed part 1 you now have a fully functional Ansible Tower which we can add as a provider to Red Hat CloudForms.<\/p>\n

Step 1<\/strong> Login to CloudForms
\n\"logincfme\"<\/p>\n

Step 2<\/strong> Go to Configuration -> Configuration Management
\n\"configurationmanagement\"<\/p>\n

Step 3<\/strong> Click on Configuration and add a new provider
\n\"addnewprovider\"<\/p>\n

Step 4<\/strong> Fill in the following values (of course it needs to match your environment)
\n\"addtowerprov\"
\nNow validate your credentials
\n\"validate\"
\nand hit add
\n\"addcfme\"<\/p>\n

Step 5 <\/strong> After Adding the provider you will see that CloudForms will discover the created job template from Ansible Tower
\n\"towerjobs\"<\/p>\n

Step 6<\/strong> Click on the sat6register job template
\n\"screen-shot-2016-09-20-at-5-23-34-pm\"
\nThen click configuration -> Create Service Dialog from this Job Template
\n\"createdialogfromtemplate\"<\/p>\n

In my case I did name the template reghosts_to_sat6<\/strong>
\n\"screen-shot-2016-09-20-at-5-29-05-pm\"
\nClick the save button on the bottom right
\n\"screen-shot-2016-09-20-at-5-30-44-pm\"<\/p>\n

Step 7<\/strong> Now its time to look at the actual service dialog which got created from the Ansible Job Template
\nGot to Automate -> Customization -> Service Dialogs and click on your service dialog. You will see a dialog which pretty much looks like this
\n\"selection_025\"
\nIf you want to be able to edit the fields you have to uncheck<\/strong> the readonly box for each field. Per default they are set readonly!<\/p>\n

Step 8 <\/strong> Believe it or not but this is a fully functional service dialog which can be added to a catalog in CloudForms. Part 4<\/strong> of the series which I will release next week will show you how you can make some of these fields dynamic<\/strong>. <\/p>\n

Step 9 <\/strong> Create a catalog. Go to Services -> Catalogs -> Catalogs and click on Configuration -> Create new catalog
\n\"screen-shot-2016-09-20-at-5-39-52-pm\"
\nName the catalog however you like and add it
\n\"screen-shot-2016-09-20-at-5-40-50-pm\"<\/p>\n

Step 10<\/strong> Lets add the service dialog to the ansible catalog. Click on Services -> Catalogs -> Catalog items -> ansible -> Configuration -> Create new catalog item
\n\"screen-shot-2016-09-20-at-5-43-01-pm\"
\nAs a catalog item type choose AnsibleTower
\n\"screen-shot-2016-09-20-at-5-43-59-pm\"
\nAdd the following values to the catalog item and click add
\n\"screen-shot-2016-09-20-at-5-45-32-pm\"<\/p>\n

Step 11<\/strong> Lets add some color to the catalog item and add an ansible logo<\/a>. Click on the newly created catalog item and upload the ansible logo.
\n\"selection_044\"<\/p>\n

Step 12 <\/strong>login to the self service ui, you will find that under https:\/\/cloudformsfqdn\/self_service
\n\"logincfme\"
\nOnce logged in click on Service Catalog and you will see your ansible catalog item
\n\"screen-shot-2016-09-20-at-5-54-49-pm\"<\/p>\n

Step 13<\/strong> Click on the ansible catalog item and fill out the values. The limit is the host or hosts separated by “:” which you would like to register to Satellite6. The limit cannot be left empty and the host must exist in the Ansible Tower inventory unless you chose the tower inventory to update on launch of a job.
\n\"screen-shot-2016-09-20-at-5-55-54-pm\"
\nIf you have entered all the correct values you can go ahead, add the item to the shopping cart
\n\"screen-shot-2016-09-20-at-5-59-20-pm\"
\nYou can now click on the shopping cart on the top right and order the item
\n\"screen-shot-2016-09-20-at-5-59-31-pm\"<\/p>\n

As this item was launched as a service you can follow the work flow under Services->Requests. Once the statemachine steps gets to launch_job you will see the job popping up in the Ansible Tower Console. <\/p>\n

\"selection_024\"<\/p>\n

After few second, the job is executed and registers the host with the Red Hat Satellite 6 server. The completion of the job can be validated in CloudForms under Services -> Requests or in the Satellite 6 UI. <\/p>\n

The next part (part 3) of the blog series which I will release next week will show you how you can add that dialog as a button under vm instances.<\/p>\n","protected":false},"excerpt":{"rendered":"

This post will show you how to add Ansible Tower as a provider in CloudForms, discover and create a catalog item out of a job template we\u2019ve created and order the catalog item via self service portal. If you followed part 1 you now have a fully functional Ansible Tower which we can add as…<\/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":[67,29,8,68],"class_list":["post-1594","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ansible","category-cloudforms","category-puppet","tag-ansible","tag-cloudforms","tag-puppet-2","tag-satellite6"],"_links":{"self":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1594","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=1594"}],"version-history":[{"count":30,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1594\/revisions"}],"predecessor-version":[{"id":1792,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/1594\/revisions\/1792"}],"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=1594"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1594"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}