You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@marcelmamula I don't think this is a good idea, for a handful of reasons:
Homogeneity objective, means appending code for Spot across all Cloud Service Providers. That's a lot of work, re-testing, further bloats the input vars, and would need to be factored into long-term validation testing upon each new release.
Spot are not SAP Certified, so we're adding code that will only ever be applicable to temporary sandboxes (not that I disagree with that for cost-saving). If I recall, AWS AMI are relatively flexible and can be applied to any AWS EC2 VS Instance Type (Profile) - but the other CSPs (if I recall correctly) all place a restriction on x OS Image applied to y Profile, therefore I doubt SLES4SAP / RHEL4SAP OS Images will work with other Spot compute.
Spot may not be fully comprehended by end-users, they may use it by accident or misunderstand - then lose their work.
Primarily No.1 is my reason for this apprehension. I don't have personal time available to code for each platform and re-test.
amazon.aws.ec2_instance
module does not support creation of Spot instanceshttps://docs.ansible.com/ansible/latest/collections/amazon/aws/ec2_instance_module.html
This module does not support creating EC2 Spot instances.
It would be good to add support for Spot instances by using module
amazon.aws.ec2_spot_instance
based on user specified variable with extra inputs for Spot specific inputs like Launch Group. https://docs.ansible.com/ansible/latest/collections/amazon/aws/ec2_spot_instance_module.htmlThe text was updated successfully, but these errors were encountered: