-
Notifications
You must be signed in to change notification settings - Fork 63
WIP PvC Prereqs and Control Plane merge #89
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion-based infrastructure Signed-off-by: Webster Mudge <[email protected]>
…lative imports are difficult in Ansible, but FQCN imports are always good WIP migrating example definitions to separate repo Removed most uses of push-down Ansible tags as they confuse even the most experienced Ansible user Renamed several playbooks to be more explanatory of what service they work on Started splitting out playbooks into separate deployment areas to allow users to pick and choose, or run the whole thing from main.yml Updated private cloud cluster deployment to include necessary steps for ECS deployment, still WIP Refactored main to simplify some pathways for better readability, still WIP Signed-off-by: Daniel Chaffelson <[email protected]>
Deploying a cluster requires facts to be gathered for ansible version, this Play now gathers facts Updated pvc_cp_setup.yml so it'll run independently of main.yml Signed-off-by: Daniel Chaffelson <[email protected]>
…llow independent execution remove separate pvc-ds playbook as tags and switches better control functionality structured within the main deployment process Signed-off-by: Daniel Chaffelson <[email protected]>
Signed-off-by: Daniel Chaffelson <[email protected]>
|
Please note this PR contains breaking changes as we begin development on the 2.x release. |
wmudge
added a commit
to wmudge/cloudera-deploy
that referenced
this pull request
Mar 8, 2023
* Initial version for CDP Public Cloud setup and teardown using definition-based infrastructure * Migrate roles from cloudera-deploy to cloudera.exe collection, as relative imports are difficult in Ansible, but FQCN imports are always good * Migrate WIP example definitions to separate repo * Remove most uses of push-down Ansible tags as they confuse even the most experienced Ansible user * Rename several playbooks to be more explanatory of what service they work on * Split playbooks into separate deployment areas to allow users to run adhoc or in sequence via main.yml * Update private cloud cluster deployment to include necessary steps for ECS deployment * Refactor main to simplify some pathways for better readability * Rename iptables role to be generic prereqs for pvc_ecs * Gather facts necessary for cluster deployment * Update pvc_cp_setup.yml so it runs independent of main.yml * Break pvc playbooks out into groups according to functional area to allow independent execution * Remove separate pvc-ds playbook as tags and switches better control functionality structured within the main deployment process * Add teardown play for ECS clusters Signed-off-by: Daniel Chaffelson <[email protected]> Co-authored-by: Webster Mudge <[email protected]> Signed-off-by: Webster Mudge <[email protected]>
wmudge
added a commit
that referenced
this pull request
Mar 8, 2023
* Update PvC prerequisites and Control Plane (#89) * Initial version for CDP Public Cloud setup and teardown using definition-based infrastructure * Migrate roles from cloudera-deploy to cloudera.exe collection, as relative imports are difficult in Ansible, but FQCN imports are always good * Migrate WIP example definitions to separate repo * Remove most uses of push-down Ansible tags as they confuse even the most experienced Ansible user * Rename several playbooks to be more explanatory of what service they work on * Split playbooks into separate deployment areas to allow users to run adhoc or in sequence via main.yml * Update private cloud cluster deployment to include necessary steps for ECS deployment * Refactor main to simplify some pathways for better readability * Rename iptables role to be generic prereqs for pvc_ecs * Gather facts necessary for cluster deployment * Update pvc_cp_setup.yml so it runs independent of main.yml * Break pvc playbooks out into groups according to functional area to allow independent execution * Remove separate pvc-ds playbook as tags and switches better control functionality structured within the main deployment process * Add teardown play for ECS clusters * Update installation order and targeted hosts (#97) * Move RDBMS role after TLS cert distribution role * Update hosts for CM configuration and deployment * Update conditionals for installation of Kerberos * Add gather_facts to the definition verification play * Fix teardown when dynamic infra not reachable (#93) * Remove Infra availability checks during teardown as Infra may not actually be reachable * Add 'pvc' tag to cluster deployment for the scenario where ECS is being added to an existing CDP Base cluster * Remove duplicate call to deploy local OS user accounts for ECS * Remove legacy centos7-init.sh script (#98) Signed-off-by: Daniel Chaffelson <[email protected]> Signed-off-by: Webster Mudge <[email protected]> Co-authored-by: Dan Chaffelson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.