Skip to content
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.

bunch of updates #139

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

bunch of updates #139

wants to merge 4 commits into from

Conversation

Brzhk
Copy link

@Brzhk Brzhk commented Jul 24, 2017

so far:

  • couple of typos fixed
  • packer images bumped to the latest xenial release
  • terraform syntax changes
  • amazon/amazon-ecs-agent docker image uses the latest tag now
  • segment/ecs-logs from 0.1.1 to 0.1.5
  • ixgbevf from 3.1.2 to 3.4.3
  • terraform 0.7.2 to 0.9.11
  • packer 0.10.1 to 1.0.3
  • dumb-init from 1.1.3 to 1.2.0
  • some bash syntax best practices here or there.
  • the image kernel is not bumped anymore
  • removed now unnecessary dependency to linux-image-extra
  • patched ixgbevf compilation for x.x.x-255+ aws kernel images.
  • adds necessary lib for EFS usage (nfs-common)
  • adds some tools (curl, unzip, jq)

 - latest xenial ubuntu release base
 - amazon/amazon-ecs-agent docker image uses the latest tag now
 - segment/ecs-logs from 0.1.1 to 0.1.5
 - ixgbevf from 3.1.2 to 3.4.3
 - terraform 0.7.2 to 0.9.11
 - packer 0.10.1 to 1.0.3
 - dumb-init from 1.1.3 to 1.2.0
 - some bash syntax best practices here or there.
Copy link
Contributor

@achille-roussel achille-roussel left a comment

Choose a reason for hiding this comment

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

Those are great changes, thanks a lot for your contributions!

I left a couple of comments inline, once addressed I'll be happy to merge this.

@@ -23,6 +23,7 @@ variable "cidr" {
}

variable "default_ecs_ami" {
type = "map"
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you mind running terraform fmt, I think the formatting is incorrect here.

Copy link
Author

Choose a reason for hiding this comment

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

done!

Copy link
Author

Choose a reason for hiding this comment

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

Also please run a final check beforehand, just to make sure.

# https://www.packer.io/docs/builders/amazon-ebs.html
ami:
source_ami: ami-e6d5d2f1
source_ami: ami-d15a75c7
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this the ID of an official image? Do you mind giving a link to it so we can verify how it was built?

Copy link
Author

Choose a reason for hiding this comment

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

Choose a reason for hiding this comment

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

If your making updates to leverage handy new terraform features, why not throw in the AMI data resource? https://www.terraform.io/docs/providers/aws/d/ami.html

Copy link
Author

@Brzhk Brzhk Aug 4, 2017

Choose a reason for hiding this comment

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

Maybe in the next one? Although Im wary of unrepeatable builds. You could.argue that I have sent the ECS agent to the latest docker tag. Your call.

EDIT: @gjohnson did you mean at the ecs-cluster module level aiming for "^myami-\d{3}" of the self account ?

@Brzhk
Copy link
Author

Brzhk commented Jul 27, 2017

Sorry for bothering you @achille-roussel,
Has anyone looked into the DNS/DHCP/network configuration of the containers and/or host instances to ease up service discovery? I had some troubles in my first experiments with the stack, I'll soon have to look into this.

Is there a gitter/slack/IRC room we can discuss the stack so I can avoid hijacking the pull requests?

@raja
Copy link

raja commented Aug 15, 2017

Can this be merged?

@martinkoch-geniebelt
Copy link

Would be really nice if this could be merged :)

@raja
Copy link

raja commented Sep 8, 2017

I assume this repository has largely been abandoned and also ecs has changed significantly in the last year. I've used Segment's stack as guide and built a new stack module from scratch with the following key differences:

If it is of interest to anyone, I'd be happy to publish it publicly.

@martinkoch-geniebelt
Copy link

@raja That would be really cool, thanks. In my local version, I have also created a web-service-alb, so we can compare notes on that one :)

@jalessio
Copy link
Contributor

jalessio commented Sep 9, 2017

@raja and @martinkoch-geniebelt I've come to the similar conclusion that I should just use this repo as a template (which is a great start!) and modify to suit my own needs, but it would still be great to keep "the template" up to date somewhere. Please publish your fork if you're able to.

@raja and @martinkoch-geniebelt -- @slajax also has added ALB support in PR #134

@pikeas
Copy link

pikeas commented Dec 14, 2017

Is there a reason this hasn't been merged?

@kc-dot-io
Copy link

kc-dot-io commented Dec 15, 2017

Most large PRs don’t end up merging here because doing so would impact all the downstream environments the next time a source is pulled. The approach it seems many of us are using is to maintain a fork that you can point all your sources to and just PR to this repo to share with others - If they want the change they can add your fork as a remote and diff / patch as needed. We’re maintaining our fork actively and have rolled out ALB support on internal services as well for example. Anyone who wants this change is welcome to it but ultimately it would be risky for the segment team to merge it here. It would require a lot of community engagement to do these changes right since terraform doesn’t yet have a robust way to deal with semantic versioning of external modules - just refs, which is insufficient for managing the roll out of breaking changes in a stable way. No one wants downtime because of upstream infra changes. Tread carefully.

@pikeas
Copy link

pikeas commented Dec 15, 2017

@slajax Is your fork public?

@kc-dot-io
Copy link

Yes. See open pull requests.

@@ -27,7 +27,7 @@ ExecStart=/usr/bin/docker run \
--publish=127.0.0.1:51679:51679 \
--env-file=/etc/ecs/ecs.config \
--env=ECS_CLUSTER=${SERVER_GROUP} \
amazon/amazon-ecs-agent:v1.14.1
amazon/amazon-ecs-agent:latest
Copy link

Choose a reason for hiding this comment

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

Dont know if this is a great idea. It happened to me twice that they introduce a critical bug in the latest version and screwed up all my cluster. Personally I would prefer to have that stuck to a fixed version

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants