Blox – Open Source Tools for Amazon ECS
blox.github.io
Blox – Open Source Tools for Amazon ECS
1–10 of 30 posts
Re: Blox – Open Source Tools for Amazon ECS
#2[deleted]
Re: Blox – Open Source Tools for Amazon ECS
#3In case it wasn't clear to anyone else, this is by the Amazon ECS team. An introductory blog post is here: https://aws.amazon.com/blogs/compute/introducing-blox-from-a...
Re: Blox – Open Source Tools for Amazon ECS
#4One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud.
Pluggable schedulers is one of the best features that is missing from kubernetes, swarm, and nomad. All the scheduling/lifecycle algorithms are pretty naive when it comes to any stateful (DBs, kafka) or batch (hadoop, spark) services. But even for typical webapps, pluggable schedulers give you a nice place to hook into a lot of the lifecycle that makes things like pre-warming or cleanly killing sockets at scale down a lot simpler.
So this is pretty cool... and makes ECS more attractive... but I wish it was just mesos which is built around the idea of providing a framework for building schedulers and would be way more portable.
Re: Blox – Open Source Tools for Amazon ECS
#5One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
I think you might be a bit misinformed and referring to a much older version of kubernetes. I say this as someone who has used (and deployed) Mesos for the past few years and is currently working on Kubernetes. Kubernetes has pluggable schedulers[1], but unlike Mesos, which requires a scheduler as part of a framework, there is a default Kubernetes scheduler[2]
A kubernetes scheduler is akin to a mesos framework sans the executor and how you interact with them. There is a single way to interact with schedulers in k8s (via the apiserver) and there is a default "executor" which is the containerizer (docker/rkt/oci-d/etc). For proof of this, see the etcd[3] operator or prometheus[4] operators. Both etcd and prometheus are stateful services.
[1] http://kubernetes.io/docs/admin/multiple-schedulers/
[2] http://kubernetes.io/docs/admin/kube-scheduler/
[3] https://coreos.com/blog/introducing-the-etcd-operator.html
[4] https://coreos.com/blog/the-prometheus-operator.htmlRe: Blox – Open Source Tools for Amazon ECS
#6One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
What other features are you missing from ECS?
Re: Blox – Open Source Tools for Amazon ECS
#7One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
Kubernetes supports pluggable schedulers:
http://kubernetes.io/docs/admin/multiple-schedulers/
It also supports pluggable "controllers," which manage the lifecycle of containers.
(So a Kubernetes scheduler + controller is roughly equivalent to a Mesos framework scheduler; see this doc for more details: https://github.com/kubernetes/community/blob/master/contribu... )
Another recent development in this area is CoreOS operators, which leverages pluggable controllers + Third Party Resources and was previously discussed on HN: https://news.ycombinator.com/item?id=12868594
[Disclosure: I work on Kubernetes at Google.]
Re: Blox – Open Source Tools for Amazon ECS
#8One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
Kubernetes supports pluggable schedulers: http://kubernetes.io/docs/admin/multiple-schedulers/ It also supports pluggable "controllers," which manage the lifecycle of containers. (So a Kubernetes scheduler + controller is roughly equivalent to a Mesos framework scheduler; see this doc for more details: https://github.com/kubernetes/community/blob/master/contribu... ) Another recent development in this area is CoreOS…
I knew that was on the roadmap, but didn't know that it was supported yet. Very cool :)
Re: Blox – Open Source Tools for Amazon ECS
#9One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
I think you might be a bit misinformed and referring to a much older version of kubernetes. I say this as someone who has used (and deployed) Mesos for the past few years and is currently working on Kubernetes. Kubernetes has pluggable schedulers[1], but unlike Mesos, which requires a scheduler as part of a framework, there is a default Kubernetes scheduler[2] A kubernetes scheduler is akin to a mesos framework sans…
I haven't been following kubernetes as closely for the last 6 months, cool to see that its also being supported...
A lot of our decision to go with mesos was that our first use case is running big data tools (spark, etc) which have a good bit of integration with mesos. Will be interesting to see the level of adoption of projects implementing operators
Re: Blox – Open Source Tools for Amazon ECS
#10One of the more interesting announcements. ECS has seemed like a non starter for any "serious" project for a while, but as someone who has been implementing mesos for the last few months, its pretty interesting that they would prioritize pluggable schedulers rather than getting better feature parity with kubernetes on google cloud. Pluggable schedulers is one of the best features that is missing from kubernetes, swar…
What other features are you missing from ECS?
Not the OP, but I'm missing in no particular order(and some of these may be on offer now):
* Secret storage
* Pet sets(coming along in k8s)
* Leader election
* Persistent volumes
It looks like Blox can address some of this stuff, but kubernetes is providing this stuff OOTB.. It's also locked to vendor-specific service offerings. This isn't to say Kubernetes doesn't have room for improvement; its AWS integrations could use some work(Application Load Balancer support, etc).