phildougherty

Sorry, I think I misunderstood what you were saying there. Could you clarify a bit more about what kind of functionality you'd prefer we support in the scenario you described? A large influx of traffic hits your application while you are unavailable to handle it. If you do not have autoscaling enabled, your application performance could suffer, if you do have it enabled your bill could grow out of bounds. We do plan to let you set min and max bounds for autoscaling once it is implemented. Thanks for your help!

Thanks, that is valuable feedback. We definitely recognize that there are other options out there that offer unlimited static sites. We feel that the additional features and capabilities offered by the platform including running scaled our dynamic workloads, workers, jobs, and databases - at a price point that is very competitive will provide you with value to make up for it - having these features just results in a different economic model for us.

Thanks for the feedback! Autoscaling is not yet supported on the platform (but is coming soon). Before autoscaling lands as a feature, insights based alerting will also land. You'll be able to setup alerts for scaling events, bandwidth, cpu, memory, and more that can be sent via email or slack.

Thanks for the feedback! I will be sure to address your points with the team as we continue to develop our roadmap. One thing to point out is that there is now console access available in the product.

We certainly took a lot of inspiration and leaned on the awesome experience of the nanobox team, but this is largely a completely different architecture.

A complex combination of factors that touch on timing, investment, strategy, people, mistakes, and way too many other factors to fit in a HN comment.

Hey there! DO Kubernetes PM here.

I just added you so you have access to the product. I will reach out to the PM on DBaaS as well.

Interesting to see where things head for sure. It's also very impactful to me to realize that some of the most iconic things in NYC have already surpassed the 70 year mark or much more (empire state building, BK bridge, statue of liberty, city hall, grand central, countless others). Makes me excited about how much longer structures can exist utilizing the tactics we have learned as humans.

managed to get a broken nose there my first week in NYC. way to go me. cool to see some good shows there before it became condos.

just had a lot of fun with this. thanks for making it.

Hey there! I'm the product manager working on the DigitalOcean Kubernetes product and early access program. We have updated our announcement blog post with some new information (at the bottom). We will be opening up early access phase 1 on July 10th. https://blog.digitalocean.com/introducing-digitalocean-kuber...

Perhaps the right wording would have been "not making you want to tear your hair out"

There may be some chances for an improvement at Pittsburgh airport with the announcement of $1.1bn in major renovations being funded: http://www.post-gazette.com/business/development/2017/09/12/...

I could see Southwest adding a PIT -> Seattle non-stop in a hurry if needed.

Disclosure, i work at containership.

We have a SaaS based product that can stand up a Kubernetes cluster for you, and it really does only take 10-15 minutes from signup to being live. https://containership.io

Pretty neat how nicely this integrates into an existing docker host setup. Definitely going to give it a try and see about integrating into containership.

edit: typo

I wrote a quick post discussing this outage. I figured I should share here https://blog.containership.io/aws-got-you-down

Must be related to AWS S3 issues.

https://status.aws.amazon.com/

Thanks!

How is this doing discovery of other nodes? Says it is fully decentralized but just doing a `meshbird new` to get a key and then running `MESHBIRD_KEY="key" meshbird join` doesn't explain the discovery mechanism to me. Haven't dug into it much though.

Great suggestion. I updated the post with that. Thanks!

Thanks for the appreciation :) I may just nuke the social share thing altogether, but I think I'll sleep on that decision.

Fixed! Thank you!

Yep we have a lot of similarities to Docker Cloud/Tutum. Per-seat pricing, unlimited servers/clusters. We have a free tier you can try out.

We changed the size of the social share widget to be smaller, hope it helps.

Thanks for the heads up, I'll look into making that less annoying.

Whoops! Good catch.

Performance comparison is coming in part 2. Sorry! Editing.

I guess that's true if you're treating containers and the environment they run in as "another layer" of stuff that you use configuration management to deploy on top of your existing automation you maybe already had prior to adopting them. I do suppose that is probably true of many users still today. There is also the use case of updating your base image or AMI and then replacing slaves/followers/your servers that run the containers, more or less eliminating the need for a job that is constantly running, or running on a schedule to keep the host system up to date. It's true that in the case of container hosting systems, that is mostly being abstracted away from you, and this post was written with that mindset as we do just that. Good comment and point of view though, I think it's still something a lot of folks struggle to wrap their heads around!

That's fair. This was definitely written with deployments in mind so I can't disagree with your assessment. With that said, I think the real downside of config management, and the real upside of containers really comes down to deployments. There is definitely still a use case for system level changes and patching that are best served by config management. How long until the container based config management? :serious_question:

Not sure of the approach Nomad takes, if any, but generally speaking bind mounting from the host system into the container is the common approach. That allows you to attach network storage, or EBS, or whatever you're used to using, and having access to it from your containers pretty transparently.

ContainerShip, has CodexD (https://github.com/containership/codexd) which creates subvolumes for your containers on the fly using ephemeral/host storage, and can stream the data around to other servers in the cluster if containers are relocated.

(Disclosure: I'm a founder of ContainerShip)

I am in complete agreement. I don't think it's a question of if, and more a question of WHEN everything in the data center is containerized. The benefits far outweigh the negatives (like educating your whole staff on a new workflow or set of tools), and it seems that ease of use when it comes to the ecosystem/tools/orchestration is really the only hurdle keeping it from getting there. We're working on making those "non-custom" software packages easy to stand up and use via http://containership.io/#marketplace