Bug 1748036

Summary: [RFE] Reduce the deployment time of hosted-engine on a remote host
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Ido Rosenzwig <irosenzw>
Component: RFEsAssignee: Nobody <nobody>
Status: CLOSED DEFERRED QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: low    
Version: 2.3.12CC: bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
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: 2021-09-29 11:33:06 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:

Description Ido Rosenzwig 2019-09-02 14:08:29 UTC
Description of problem:

When running hosted-engine deployment on a remote host using 
hosted-engine ansible role directly, the deployment time can be significantly reduced when adding the following lines to /etc/ansible/ansible.cfg under [ssh] section:

ssh_args = -C -o ControlMaster=auto -o ControlPersist=30m
control_path_dir = /root/cp
control_path = %(directory)s/%%h-%%r
pipelining = True

In every task in ansible on a remote host a new ssh connection is 
being established. because we have numerous tasks on the hosted-engine Ansible role we create many ssh connections.
Adding these 4 lines in ansbile.cfg configuration file will ensure opening  only one ssh connection to the remote host, thus reducing the time of open and close ssh connection every single task.

These lines should be added to /etc/ansible/ansible.cfg when installing the hosted-engine package.

Steps to verfiy:
1. Deploy hosted-engine on a local host 
2. Deploy hosted-engine on a remote host
(it doesn't matter if it's command-line or with cockpit)

Comment 1 Michal Skrivanek 2021-08-20 11:01:59 UTC
This bug/RFE is more than a year old and it didn't get enough attention so far, and is now flagged as pending close. 
Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.

Comment 2 Michal Skrivanek 2021-09-29 11:33:06 UTC
This bug didn't get any attention in a long time, and it's not planned in foreseeable future. oVirt development team has no plans to work on it.
Please feel free to reopen if you have a plan how to contribute this feature/bug fix.