-
Notifications
You must be signed in to change notification settings - Fork 22
Add crc-cloud Ansible role #195
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
Conversation
fe40ace to
858d3dd
Compare
|
Ansible is not able to programmatically set infra and then provision which pulumi provides. ( cc @adrianriobo for more info around using pulumi over ansible) |
|
@danpawlik do you mean the steps insde the VM to set and ensure the cluster is running or the provisioning? |
|
So there can be a basic way to run the ansible to setup the cluster. With that way, there is no need to use crc-cloud binary to spawn instance (check issue: #192). The CI would be able to take crc.qcow2 image to the cloud provider, connect to it , then run the ansible playbook. |
e1021fc to
0af05e5
Compare
|
So in the README file is early how-to deploy crc cloud using the Ansible role that will be running inside the container. With that way, we don't need to wait #192 that propably it is not a priority for you. |
0af05e5 to
79cd913
Compare
|
@sourcery-ai review |
Reviewer's Guide by SourceryThis pull request introduces an Ansible-based deployment solution for CRC cloud, offering an alternative to the existing crc-cloud tool. It includes roles for bootstrapping the environment and deploying the cloud, along with comprehensive documentation and playbooks to automate the process. Sequence diagram for CRC Cloud BootstrapsequenceDiagram
participant Ansible Playbook
participant crc-bootstrap Role
participant Podman Container
Ansible Playbook->>crc-bootstrap Role: Execute role
crc-bootstrap Role->>Podman Container: Build container
crc-bootstrap Role->>Podman Container: Create container
crc-bootstrap Role->>Podman Container: Start container
Podman Container->>Podman Container: Runs start.yaml playbook
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @danpawlik - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider using Ansible modules instead of shell commands where possible for better idempotency and readability.
- It would be helpful to add some comments to the tasks in
main.yamlto explain what each task is doing.
Here's what I looked at during the review
- 🟡 General issues: 7 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @danpawlik - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider using Ansible modules instead of shell commands where possible for better idempotency and readability.
- It would be helpful to add some comments to the tasks in
main.yamlto explain what each task is doing.
Here's what I looked at during the review
- 🟡 General issues: 7 issues found
- 🟡 Security: 1 issue found
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
79cd913 to
b2134f6
Compare
|
@sourcery-ai dismiss |
|
@sourcery-ai review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @danpawlik - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider using Ansible modules instead of shell commands where possible for better idempotency and error handling.
- It might be helpful to add tags to the tasks, so it would be easier to run specific parts of the playbook.
Here's what I looked at during the review
- 🟡 General issues: 2 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
ed83c0e to
766237c
Compare
The Ansible tool might handle in better way how to deploy the CRC cloud. NOTE: The Ansible role can be optimized and it would be done in next pull requests. This commit just adds same functionality as it is done in clustersetup.sh script. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
766237c to
9ee0499
Compare
After merging change [1], we are able to stop using shell script and start using dedicated Ansible role that brings better output what is done and better control on starting the service. [1] crc-org/crc-cloud#195 Change-Id: I41dfb356806f9c97b64102f5f612607026d55b9b Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
The Ansible tool might handle in better way how to deploy the CRC cloud.
Summary by Sourcery
Add Ansible roles to bootstrap and deploy CRC (CodeReady Containers) cloud directly on the host
New Features:
Enhancements:
Documentation: