{"id":2057,"date":"2017-06-01T09:50:50","date_gmt":"2017-06-01T13:50:50","guid":{"rendered":"http:\/\/blog.domb.net\/?p=2057"},"modified":"2017-06-01T14:23:29","modified_gmt":"2017-06-01T18:23:29","slug":"cloudforms-4-5-rhv-management-part-1","status":"publish","type":"post","link":"https:\/\/blog.domb.net\/?p=2057","title":{"rendered":"CloudForms 4.5 RHV 4.1 Management by Ansible Automation Inside (Part 1 Create Service Dialog)"},"content":{"rendered":"

This post will explain what steps you need to go through to enable the ansible management of RHV on the first release of CFME 4.5. I assume that you’ve already enabled the Embedded Ansible role in Configuration – Server Control (enabling ansible automation inside can take up to 7-10 minutes) .<\/p>\n

CloudForms 4.5 comes with the ansible version of 2.2.1. For the RHV \/ ovirt modules we need the 2.3 version. As both version run python 2.7 an upgrade of the package ansible will not pull in any dependency and will not add any harm to the system.<\/p>\n

[root@host204 ~]# rpm -ivh https:\/\/dl.fedoraproject.org\/pub\/epel\/7\/x86_64\/e\/epel-release-7-9.noarch.rpm<\/pre>\n
Then update ansible<\/p>\n
[root@host204 ~]# yum update ansible -y<\/pre>\n
Now\u00a0we need to get the\u00a0python-ovirt-engine-sdk4-4.1.3-1.el7ev.x86_64.rpm as this package is not on the cloudforms appliance yet for rhv 4.1. Please make sure you download it from the redhat portal.<\/p>\n
[root@host204 ~]# rpm -ivh python-ovirt-engine-sdk4-4.1.3-1.el7ev.x86_64.rpm<\/pre>\n
Once done you need to create a folder on the CFME 4.5 appliance so that ansible inside can read files on the filesystem. Open the file \/etc\/tower\/settings.py and add the following content<\/p>\n
AWX_PROOT_SHOW_PATHS = ['\/tmp\/readablebytower']<\/pre>\n
I need this directory for my playbooks as I\u00a0store the ovirt-ca.pem there which is needed for the authentication.<\/p>\n
Restart ansible automation inside to update the configs.<\/p>\n
[root@host204 ~]# ansible-tower-service restart<\/pre>\n
In CloudForms go to Automation – Ansible – Credentials and add the following machine credential. You only need to fill in the Name and Vault password as you will store the RHV creds in the vault. That is the power of ansible. Even if we don’t have the “credentials” in the UI you can pretty much use this\u00a0method for any provider until we added in the UI:<\/p>\n
\"\"Then go to Automation – Ansible – Repositories and git clone the following repo (this is for you to get some playbooks) or clone yours:<\/p>\n
\"\"<\/p>\n
If you are successful with adding the repo you now see all playbooks under Automation – Ansible – Playbooks:<\/p>\n
\"\"<\/p>\n
From there you can go to Services – \u00a0Catalogs and create a new catalog. Once done go to Catalog items where you can choose to create a new item from the ansible playbook. You can either let it generate a new service dialog or you can use one you’ve created.<\/p>\n
\"\"<\/p>\n
Now that we are done go order the item under Services – Service Catalogs – CatalogName – Item<\/p>\n
\"\"<\/p>\n
The job output\u00a0can either be checked in the self service portal or in \/var\/lib\/awx\/job_status\/…. on the appliance which runs ansbile.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
This post will explain what steps you need to go through to enable the ansible management of RHV on the first release of CFME 4.5. I assume that you’ve already enabled the Embedded Ansible role in Configuration – Server Control (enabling ansible automation inside can take up to 7-10 minutes) . CloudForms 4.5 comes with…<\/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,4],"tags":[67,111,110,29],"class_list":["post-2057","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ansible","category-cloudforms","category-virtualization","tag-ansible","tag-ansible-automation-inside","tag-ansible-inside","tag-cloudforms"],"_links":{"self":[{"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/2057","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=2057"}],"version-history":[{"count":15,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/2057\/revisions"}],"predecessor-version":[{"id":2087,"href":"https:\/\/blog.domb.net\/index.php?rest_route=\/wp\/v2\/posts\/2057\/revisions\/2087"}],"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=2057"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2057"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.domb.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2057"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}