1,437 karma · joined March 4, 2011
For more info, checkout the following links:
Blog : http://KenCochrane.com
Github : http://github.com/kencochrane
Linkedin: http://www.linkedin.com/in/kencochrane
Stack overflow: http://stackoverflow.com/users/356788/
Kargo has native support for Argo CD today, but one of it's goals is to be agnostic and could probably work with Dagger or other tools in the future.
Do you have more than one, and DNS load balance, or do you just live with the risk?
One of the main reasons why I use an ALB/ELB is so that I don’t have that SPOF. If you found a way around that, please share, I would love to know, so I can save some money :)
What is the tech stack?
Does it cost much to keep it running?
It will setup your swarm, which uses auto scaling groups for the worker nodes. You can then configure the auto scaling groups how ever you want, to scale based on your cloudwatch metrics, etc.
There is also a Docker for GCP product in beta. https://beta.docker.com but I don't know how auto scaling works for it.
Disclaimer: I work at Docker on the Docker for AWS product.
How do you know that is the extension and not a directory with a .jpg in the name? It is too complicated to convert to your URL scheme.
For me the URL based solution isn't quicker to type since I have to think too much. Also, how often is this going to be typed by hand verse scripted anyway? It will be easier to script if the URL is the same and only the GET Params change.
I prefer the get parameters, it is more obvious.
Another option that isn't as clean, but I have seen before is to Base64 encode the image URL. You wouldn't be able to easily type but you could keep your URL scheme, and still possible to script.
http://www.businessinsider.com/jet-insiders-referral-program...
Not sure what you mean about no message telling me to go get the bits today. There was no email saying that docker for mac/windows was made public, it was announced during the keynote at DockerCon (this morning), and a blog post went out.
Before we made it public, everyone who had signed up for the beta had an invite sent to them, and there was no one left in the queue.
Our goal for this project was to keep it as simple as possible. We tried to only use standard AWS features (CloudFormation, EC2, Autoscaling groups, VPC, ELB, etc) and we are using Docker 1.12 out of the box, with no changes.
All of the scheduling is handled in the docker engine itself, so we didn't need to add anything outside of that.
This version is pretty much an MVP, and we hope that the beta testers will help us test it out, and guide the future direction of the project.
Here is another youtube video: Getting Started with Tutum https://www.youtube.com/watch?v=fnV92aHLmyE
Any chance this might get added to the mainline kernel? aufs was never able to get merged in. OverlayFS was merged in, but IMHO isn't as good as aufs.
"Hello, We have just become aware of EC2 network connectivity issues in the US-EAST-1 region. The impact of this issue is loss of network connectivity to EC2 instances in US-EAST-1. The AWS support and engineering teams are actively working on bringing closure to this issue. I will share additional information as soon as I learn more about this issue."