Re: [gentoo-user] Custom ebuilds for CoreOS
Am Montag 01 Dezember 2014, 20:46:54 schrieb James: Anyone know anything about coreos? Lookie lookie, they have ebuilds? According to wikipedia, CoreOS is a fork of ChromeOS [1]. ChromeOS is most definitely a Gentoo derivative [2,3,4], even though that fact is not really well known (and not really publicised). [1] https://en.wikipedia.org/wiki/CoreOS [2] https://de.wikipedia.org/wiki/Google_Chrome_OS, see infobox [3] http://www.chromium.org/chromium-os [4] https://chromium.googlesource.com/chromiumos/overlays/portage/ -- Andreas K. Huettel Gentoo Linux developer kde, council
Re: [gentoo-user] Custom ebuilds for CoreOS
On Tue, Dec 2, 2014 at 7:36 AM, Andreas K. Huettel dilfri...@gentoo.org wrote: Am Montag 01 Dezember 2014, 20:46:54 schrieb James: Anyone know anything about coreos? Lookie lookie, they have ebuilds? According to wikipedia, CoreOS is a fork of ChromeOS [1]. ChromeOS is most definitely a Gentoo derivative [2,3,4], even though that fact is not really well known (and not really publicised). Interesting. Talk about a march of init systems. You have Gentoo which defaults to openrc and supports systemd, to ChromeOS which only supports upstart, to CoreOS which uses systemd. In any case, the whole point of both ChromeOS and CoreOS is that they're hosts for running applications completely outside of the usual unix-y approach of sticking stuff in /usr. Applications on ChromeOS are Chrome extensions and the like, and applications on CoreOS are containers. The whole point of both is to abstract away all the guts of how the OS operates, so the choice of init really shouldn't matter much to anybody using either. If you really want to stick stuff in /usr and interact with host processes directly, then you really should find a distro which isn't designed to be a black box in this regard. -- Rich
Re: [gentoo-user] Custom ebuilds for CoreOS
On Mon, 1 Dec 2014, Neil Bothwick wrote: On Mon, 1 Dec 2014 20:46:54 + (UTC), James wrote: Given that CoreOS have sponsored some systemd development (systemd-networkd), I think it is reasonable to assume they plan to stick with systemd for the foreseeable future. CoreOS a gentoo derived distro, had made a very elegant use of 'systemd'. systemd consists of 'unit' and 'target'. 'unit' is config file containing 'docker run' command. 'target' is the grouping mechanism (equiv to fig.yml and upcoming 'docker group' command) systemtd is exclusively used to manage the lifecycle of 'docker' containers ! thanks Saifi.
Re: [gentoo-user] Custom ebuilds for CoreOS
On Tue, 2 Dec 2014, Andreas K. Huettel wrote: Am Montag 01 Dezember 2014, 20:46:54 schrieb James: Anyone know anything about coreos? Lookie lookie, they have ebuilds? According to wikipedia, CoreOS is a fork of ChromeOS [1]. ChromeOS is most definitely a Gentoo derivative [2,3,4], even though that fact is not really well known (and not really publicised). i suppose, CoreOS uses the 'update mechanism' from ChromeOS to provide autoupdate service (a/b). for all practical purposes, CoreOS is a Gentoo derivative. thanks Saifi.
[gentoo-user] Custom ebuilds for CoreOS
Anyone know anything about coreos? Lookie lookie, they have ebuilds? python-oem-2.7.6-r1.ebuild [1] It clams to be 100% open source. It runs on bare metal, linux systems, clusters and clouds. It claims to have a much small footprint ~114 MB and boots very very fast via pxi(boot). Very interesting It does look commercial too?: https://coreos.com/ I guess my take is that eventually, linux will be very small, embedded and a cluster/cloud environment is where most systems will plug in, kinda like most modern cell phones. Hopefully, there'll be a systemd centric version so that enables individuals and small companies can remain in the game. Surely there will be a openrc version(s) that survives, adapts and remains relevant. To me, it appears that some forward looking folks have forked (stolen the best parts?) gentoo, made some fundamental (long overdue changes) and are all about creating a source_to_cluster platform. (h, vaguely sounds familiar...scratching head). It is a natural evilution for linux to take; or are we going to embrace some much needed change (new ideas) into gentoo? James [1] https://github.com/coreos/coreos-overlay/tree/master/dev-lang/python-oem [2] https://github.com/coreos/coreos-overlay/blob/master/eclass/git.eclass https://github.com/coreos https://coreos.com/products/ https://coreos.com/blog/rocket/ https://coreos.com/docs/
Re: [gentoo-user] Custom ebuilds for CoreOS
On Mon, Dec 1, 2014 at 3:46 PM, James wirel...@tampabay.rr.com wrote: It clams to be 100% open source. It runs on bare metal, linux systems, clusters and clouds. It claims to have a much small footprint ~114 MB and boots very very fast via pxi(boot). The whole idea of CoreOS is to be the host for a bunch of containers. The host is completely generic - other than maybe configuring things like the network or hardware or things actually related to hosting (what containers to run/how/etc) you aren't suppose to really touch it. You don't install packages on the host. All the stuff you care about goes into the containers. Think of it like VMWare on bare metal, except it is linux and you're running containers and not VMs (so much more efficient, and less secure). Surely there will be a openrc version(s) that survives, adapts and remains relevant. Again, the point of CoreOS is that you don't care how the host works. You won't add/remove services from the host. As such you won't care what init implementation it runs. The containers are a completely different beast. You might just run your application in the container as PID 1. Or, maybe you run something like sysvinit+openrc or systemd inside a container. You could have one of each running on the same host. To me, it appears that some forward looking folks have forked (stolen the best parts?) gentoo, made some fundamental (long overdue changes) and are all about creating a source_to_cluster platform. (h, vaguely sounds familiar...scratching head). It is a natural evilution for linux to take; or are we going to embrace some much needed change (new ideas) into gentoo? I have no idea if CoreOS is Gentoo-derived, but it is very much a special-purpose distro. The whole concept is that you put all the value-add in the containers, and then you just want a really standard and lightweight distro to host your containers in. Maybe you run CentOS in one container, and Gentoo in another container, and Debian in another container. -- Rich
Re: [gentoo-user] Custom ebuilds for CoreOS
On Mon, 1 Dec 2014 20:46:54 + (UTC), James wrote: I guess my take is that eventually, linux will be very small, embedded and a cluster/cloud environment is where most systems will plug in, kinda like most modern cell phones. Hopefully, there'll be a systemd centric version so that enables individuals and small companies can remain in the game. Given that CoreOS have sponsored some systemd development (systemd-networkd), I think it is reasonable to assume they plan to stick with systemd for the foreseeable future. -- Neil Bothwick Top Oxymorons Number 11: Terribly pleased pgpOg34vmPTR_.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Custom ebuilds for CoreOS
On Mon, Dec 1, 2014 at 3:56 PM, Neil Bothwick n...@digimed.co.uk wrote: On Mon, 1 Dec 2014 20:46:54 + (UTC), James wrote: I guess my take is that eventually, linux will be very small, embedded and a cluster/cloud environment is where most systems will plug in, kinda like most modern cell phones. Hopefully, there'll be a systemd centric version so that enables individuals and small companies can remain in the game. Given that CoreOS have sponsored some systemd development (systemd-networkd), I think it is reasonable to assume they plan to stick with systemd for the foreseeable future. More importantly, CoreOS uses systemd to monitor/control the instances inside containers like systemd-nspawn does, only in a more general and powerful way. I don't think you can currently run the CoreOS host with anything other than systemd, and to make it so it would be a lot of work. From [2]: Within the CoreOS world, you will almost exclusively use systemd to manage the lifecycle of your Docker containers. Regards. [2] https://coreos.com/docs/launching-containers/launching/getting-started-with-systemd/ -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
