-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Platform] Enable SSH pipelining during universe provisioning #7995
Comments
artem-mindrov
added a commit
that referenced
this issue
Apr 19, 2021
Summary: 1. Enable SSH pipelining in ansible.cfg 2. Add a task to disable requiretty in /etc/sudoers. Make sure pipelining is disabled for this task specifically (since it requires sudo and may fail). Also make sure required pre-provisioning tasks are run regardless of the disable_custom_ssh setting (run them in a separate playbook) as this violates the SRP. 3. AnsibleProcess#run changed to allow idempotent invocations with the same extra vars. Test Plan: Provision a single node universe on - AWS - GCP Do the same with ANSIBLE_SSH_PIPELINING=False in the YW environment, check that 'disable requiretty in /etc/sudoers' task is skipped Reviewers: daniel, rtsisyk, wesley, dskorobogaty Reviewed By: dskorobogaty Subscribers: jenkins-bot, devops Differential Revision: https://phabricator.dev.yugabyte.com/D11218
artem-mindrov
added a commit
that referenced
this issue
Apr 21, 2021
Summary: the new playbook added under #7995 was missing in the release manifest Test Plan: make sure the playbook is included in the release Reviewers: wesley Reviewed By: wesley Differential Revision: https://phabricator.dev.yugabyte.com/D11313
YintongMa
pushed a commit
to YintongMa/yugabyte-db
that referenced
this issue
May 26, 2021
Summary: 1. Enable SSH pipelining in ansible.cfg 2. Add a task to disable requiretty in /etc/sudoers. Make sure pipelining is disabled for this task specifically (since it requires sudo and may fail). Also make sure required pre-provisioning tasks are run regardless of the disable_custom_ssh setting (run them in a separate playbook) as this violates the SRP. 3. AnsibleProcess#run changed to allow idempotent invocations with the same extra vars. Test Plan: Provision a single node universe on - AWS - GCP Do the same with ANSIBLE_SSH_PIPELINING=False in the YW environment, check that 'disable requiretty in /etc/sudoers' task is skipped Reviewers: daniel, rtsisyk, wesley, dskorobogaty Reviewed By: dskorobogaty Subscribers: jenkins-bot, devops Differential Revision: https://phabricator.dev.yugabyte.com/D11218
YintongMa
pushed a commit
to YintongMa/yugabyte-db
that referenced
this issue
May 26, 2021
Summary: the new playbook added under yugabyte#7995 was missing in the release manifest Test Plan: make sure the playbook is included in the release Reviewers: wesley Reviewed By: wesley Differential Revision: https://phabricator.dev.yugabyte.com/D11313
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current setting in ansible.cfg is to disable SSH pipelining:
This was most likely related to having to disable requiretty in /etc/sudoers, but
There is more room for runtime optimization:
install_backup_util
role along withansible-prometheus
, subtasks ininstall-s3cmd
configure-cluster-server.yml
is run first for master then tserver, but tserver tasks are run twice because the first run is missing an explicit server type argument so the playbook executes both master and tserver tasks due to how conditional execution is written, the same applies to install_package)configure-cluster-server
do not depend onyb_process_type
, they should probably be extracted out of this playbookThe text was updated successfully, but these errors were encountered: