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

AWS instance updates #3041

Merged
merged 2 commits into from
Mar 10, 2020
Merged

AWS instance updates #3041

merged 2 commits into from
Mar 10, 2020

Conversation

jaymalasinha
Copy link

@jaymalasinha jaymalasinha commented Mar 5, 2020

πŸ”© Description: What code changed, and why?

Re-size and remove AWS instances

⛓️ Related Resources

πŸ‘ Definition of Done

πŸ‘Ÿ How to Build and Test the Change

βœ… Checklist

πŸ“· Screenshots, if applicable

@jaymalasinha jaymalasinha requested a review from a team as a code owner March 5, 2020 14:39
@jaymalasinha jaymalasinha changed the title Jsinha/instance updates AWS instance updates Mar 5, 2020
@@ -18,7 +18,7 @@ module "single_local_inplace_upgrade" {
vpc = "${var.environment}"
platform = "ubuntu-16.04"
key_name = "cd-infrastructure"
instance_type = "m4.large"
instance_type = "m5.large"
Copy link
Contributor

Choose a reason for hiding this comment

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

does this mean we will lose the data that is currently on these instances?

Copy link
Author

Choose a reason for hiding this comment

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

No, I already resized them to m5.large this morning during the maintenance window. During the update I just restarted the instance, so you did not loose any data

@@ -70475,6 +70475,24 @@ const (
// InstanceTypeT22xlarge is a InstanceType enum value
InstanceTypeT22xlarge = "t2.2xlarge"

// InstanceTypeT3Micro is a InstanceType enum value
InstanceTypeT3Micro = "t3.micro"
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these changes you made yourself or are they from the upstream aws/aws-sdk-go package? If the former, we need to chat about how we are going to manage these patches as we typically do not change code in the vendor directory. If the latter, we will mant to make sure we get go.mod and go.sum updated to account for what version these are in.

Copy link
Author

Choose a reason for hiding this comment

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

I made those manually since I was changing the type to t3.micro. I will revert this file.

Copy link
Contributor

@stevendanna stevendanna left a comment

Choose a reason for hiding this comment

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

We need to sort out the changes to vendor before merging this.

@jaymalasinha jaymalasinha force-pushed the jsinha/instance_updates branch 2 times, most recently from b067948 to 11bafd6 Compare March 5, 2020 20:56
Jaymala Sinha added 2 commits March 10, 2020 09:23
…inplace_upgrade senarios

As requested in https://github.com/chef/release-engineering/issues/962

Signed-off-by: Jaymala Sinha <jsinha@chef.io>
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
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.

4 participants