Bug 1636919

Summary:	[RFE] Support Hosted-Engine deploy from remote server
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Ido Rosenzwig <irosenzw>
Component:	hosted-engine-setup	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:	Tahlia Richardson <trichard>
Priority:	high
Version:	unspecified	CC:	bugs, mgoldboi
Target Milestone:	ovirt-4.3.2	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	sbonazzo: ovirt-4.3? rule-engine: planning_ack? sbonazzo: devel_ack+ rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-19 10:03:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1676542
Bug Blocks:

Description Ido Rosenzwig 2018-10-08 09:28:17 UTC

Description of problem:

Currently the hosted-engine role can be executed only from the host it will be installed on. We should have the option to execute the role remotely, from another machine.

Version-Release number of selected component (if applicable):
1.0.0

Comment 1 Moran Goldboim 2018-10-08 10:19:00 UTC

Raising priority here, since this is an enabler for Ansible Tower (AWX)/ Satellite(Foreman)/ CloudForms (ManageIQ)

Comment 2 Sandro Bonazzola 2019-01-23 09:41:00 UTC

This is already available if you are using directly the role.

Comment 3 Nikolai Sednev 2019-02-12 14:09:08 UTC

I've tried to remotely deploy HE using these components:
ovirt-ansible-hosted-engine-setup-1.0.11-0.1.master.20190206102238.el7.noarch
ovirt-ansible-repositories-1.1.4-2.el7ev.noarch
ovirt-ansible-engine-setup-1.1.7-1.el7ev.noarch
ansible-2.7.7-1.el7ae.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.3-1.el7ev.noarch
Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)

Tried deploy from remote server puma19 using the same components and this yml:

hosted_engine_deploy_remotehost.yml---
- name: Deploy oVirt hosted engine
  hosts: alma03.qa.lab.tlv.redhat.com
  vars:
    he_bridge_if: enp5s0f0
    he_fqdn: nsednev-he-1.qa.lab.tlv.redhat.com
    he_vm_mac_addr: 00:16:3e:7b:b8:53
    he_domain_type: nfs
    he_storage_domain_addr: yellow-vdsb.qa.lab.tlv.redhat.com
    he_storage_domain_path: /Compute_NFS/nsednev_he_1/
  roles:
    - role: ovirt.hosted_engine_setup
    he_appliance_password: somepassword
    he_admin_password: anotherpassword


puma19 ~]# ansible-playbook -i alma03.qa.lab.tlv.redhat.com, /root/hosted_engine_deploy_remotehost.yml 

Deployment failed with:
fatal: [alma03.qa.lab.tlv.redhat.com -> nsednev-he-1.qa.lab.tlv.redhat.com]: FAILED! => {"changed": false, "elapsed": 195, "msg": "timed out waiting for ping module test success: Failed to connect to the host via ssh: ssh: connect to host nsednev-he-1.qa.lab.tlv.redhat.com port 22: Connection timed out"}

Moving back to assigned.
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1676542 for more details.

Comment 4 Simone Tiraboschi 2019-03-11 12:48:34 UTC

Please try it with something like:

cat he_deployment.json
{
    "he_bridge_if": "enp5s0f0",
    "he_fqdn": "nsednev-he-1.qa.lab.tlv.redhat.com",
    "he_vm_mac_addr": "00:16:3e:7b:b8:53",
    "he_domain_type": "nfs",
    "he_storage_domain_addr": "yellow-vdsb.qa.lab.tlv.redhat.com",
    "he_storage_domain_path": "/Compute_NFS/nsednev_he_1/",
    "he_mem_size_MB": "4096",
    "he_ansible_host_name": "alma03.qa.lab.tlv.redhat.com"
}

cat passwords.yml
he_appliance_password: 123456
he_admin_password: 123456


cat hosted_engine_deploy.yml
---
- name: Deploy oVirt hosted engine
  hosts: alma03.qa.lab.tlv.redhat.com
  roles:
    - role: ovirt.hosted_engine_setup


ansible-vault encrypt passwords.yml
ansible-playbook -i alma03.qa.lab.tlv.redhat.com, hosted_engine_deploy.yml --extra-vars='@he_deployment.json' --extra-vars='@passwords.yml' --ask-vault-pass

Comment 5 Nikolai Sednev 2019-03-11 14:55:53 UTC

puma18 ~]# ansible-playbook -i alma03.qa.lab.tlv.redhat.com, /root/hosted_engine_deploy.yml
Deployment was successful over nfs with the following contents of yml:
---
- name: Deploy oVirt hosted engine
  hosts: alma03.qa.lab.tlv.redhat.com
  vars:
    he_bridge_if: enp5s0f0
    he_fqdn: nsednev-he-1.qa.lab.tlv.redhat.com
    he_vm_mac_addr: 00:16:3e:7b:b8:53
    he_domain_type: nfs
    he_storage_domain_addr: yellow-vdsb.qa.lab.tlv.redhat.com
    he_storage_domain_path: /Compute_NFS/nsednev_he_1/
    he_mem_size_MB: 4096
    he_ansible_host_name: alma03.qa.lab.tlv.redhat.com
    he_appliance_password: somepassword
    he_admin_password: someanotherpassword
  roles:
    - role: ovirt.hosted_engine_setup

Tested on:
ovirt-hosted-engine-setup-2.3.6-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
rhvm-appliance-4.3-20190305.1.el7.x86_64
ansible-2.7.8-1.el7ae.noarch
ovirt-ansible-hosted-engine-setup-1.0.12-1.el7ev.noarch
Linux 3.10.0-957.10.1.el7.x86_64 #1 SMP Thu Feb 7 07:12:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)

Moving to verified.

Comment 6 Nikolai Sednev 2019-03-11 15:11:30 UTC

I've opened a doc bug to cover this RFE https://bugzilla.redhat.com/show_bug.cgi?id=1636919#c5

Comment 7 Sandro Bonazzola 2019-03-19 10:03:20 UTC

This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.