Skip to content
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

[FEATURE] ec2 to ec2_instance #129

Merged
merged 14 commits into from
Feb 24, 2023
Merged

[FEATURE] ec2 to ec2_instance #129

merged 14 commits into from
Feb 24, 2023

Conversation

FredButler
Copy link
Contributor

Move from ec2 to amazon.aws.ec2_instance module.
volumes structure changed for ec2_instance; maintain old syntax in cluster_defs.
Spot instances no longer supported

Chrony changes showing although already merged

Copy link
Contributor

@JamalSky JamalSky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

Copy link
Collaborator

@dipiazzg dipiazzg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@antoineserrano antoineserrano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sad to see support for Spot instances going away...

@dseeley
Copy link
Contributor

dseeley commented Feb 23, 2023

Looks familiar (c.f. dseeley@e832c5f)!!

There are a few other changes & fixes in there that might be useful, e.g.

  • amazon.aws.ec2_instance doesn't return the tagged_instances structure if the instances already exist, so the playbook would not be idempotent (& I think this kills one or two of the redeploy schemes).
  • You need Ansible core >=2.12.4 (or pypi v5.6.0) now, so the preflight assertions should change (they actually get a bit simpler).
  • I found that the route53 rescue mechanism (create_dns_a.yml) wasn't working, as the module_args were not present anymore, hence these values are acquired from elsewhere.

@FredButler
Copy link
Contributor Author

Looks familiar (c.f. dseeley@e832c5f)!!

There are a few other changes & fixes in there that might be useful, e.g.

  • amazon.aws.ec2_instance doesn't return the tagged_instances structure if the instances already exist, so the playbook would not be idempotent (& I think this kills one or two of the redeploy schemes).
  • You need Ansible core >=2.12.4 (or pypi v5.6.0) now, so the preflight assertions should change (they actually get a bit simpler).
  • I found that the route53 rescue mechanism (create_dns_a.yml) wasn't working, as the module_args were not present anymore, hence these values are acquired from elsewhere.

Thanks for having a look @dseeley, I did find your PR albeit a good time after struggling without it, defiantly helped. create_dns_a.yml was an issue. I'll look into this.

I'd need to test the redeploy schemes, if we still use those that is.

Thanks for the hint of the preflight assertions also.

@dipiazzg dipiazzg merged commit 2fb0cd1 into master Feb 24, 2023
@dipiazzg dipiazzg deleted the 729-ec2-deprecation-3 branch February 24, 2023 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants