a bit of an aside, but i am under the impression that containers are not another OS, but the same as the underlying host. So you cant have an Ubuntu container on a CoreOS host.. unless you use a hypervisor.. the container is coreos too.
mike On 18 January 2015 at 20:56, Diego Medina <[email protected]> wrote: > One other thing I'd like to point out, many people say CoreOS is great > because it autoupdates on its own, but you need to realize that the > containers that run on top of CoreOS don't run coreos, they run Ubuntu, > Fedora, etc, and if there is a security issue (think openssl, etc), you > have to rebuild all your containers again to apply the missing updates. > > Thanks > > On Sun, Jan 18, 2015 at 2:28 PM, Jason Giedymin <[email protected]> > wrote: > >> Coreos places focus on the OS to deploy services as containers. It’s >> distributed key store is meant to share config in a cluster and to aid in >> basic scheduling via fleet, which is like cluster wide systemd. >> >> It’s scheduler is basic (but can be made to be more complex if you were >> to use these base tools). On the other hand, Mesos has a more complex >> featureful scheduler, works as-an application, and has more first class >> controls over managing jobs (cgroups, etc…) >> >> There is not complete overlap between these two systems. They do not >> necessarily compete with each other. But they do have features which try to >> address distributed application design/deployment. >> >> - J >> >> On Jan 18, 2015, at 1:29 PM, Victor L <[email protected]> wrote: >> >> Hope this helps some >> It doesn't as it doesn't even try to answer my question. Let me re- >> phrase it: what does mesos on the coreos cluster do that coreos itself >> doesn't do already? >> >> On Sun, Jan 18, 2015 at 10:00 AM, Jason Giedymin < >> [email protected]> wrote: >> >>> The value of coreos that immediately comes to mind since I do much work >>> with these tools: >>> >>> - the small foot print, it is a minimal os, meant to run containers. So >>> it throws everything not needed for that out. >>> - containers are the launch vehicle, thus deps are in container land. I >>> can run and test containers with ease, not having to worry about multiple >>> OSes. >>> - with etcd and fleet, coordinating the launch and modification of both >>> machines and cluster make it a breeze. Allowing you to do dynamic mesos >>> scaling up or down. I add nodes at will, across multiple cloud platforms, >>> ready to launch multitude of containers or just mesos. >>> - security. There is a defined write strategy. You cannot write willy >>> nilly to any location. >>> - all the above further allow auto OS updates, which is supported today >>> on all platforms that deploy coreos. This means more frequent updates since >>> the os is minimal, which should increase the security effectiveness when >>> compared to big box superstore OSes like Redhat or Ubuntu. Some platforms >>> charge quite a bit for managed updates of this frequency and level of >>> testing. >>> >>> Coreos allows me to keep apps in a configured container that I trust, >>> tested, and works time and time again. >>> >>> I see coreos as a compliment. >>> >>> As a fyi I'm available for questions, debugging, and client work in this >>> area. >>> >>> Hope this helps some, from real world usage. >>> >>> Sent from my iPad >>> >>> > On Jan 18, 2015, at 9:16 AM, Victor L <[email protected]> wrote: >>> > >>> > I am confused: what's the value of mesos on the top of coreos cluster? >>> Mesos provides distributed resource management, fault tolerance, etc., but >>> doesn't coreos provides the same things already? >>> > Thanks >>> >> >> >> > > > -- > Diego Medina > Lift/Scala consultant > [email protected] > http://fmpwizard.telegr.am >
