131–140 of 203 posts
Is this a good technical fit? Is this good for the tech community as a whole? I am a bit disheartened to see discussions often going in the direction of big corporation politics / power play, rather than how it benefits the community.
Is this a good technical fit? Is this good for the tech community as a whole? I am a bit disheartened to see discussions often going in the direction of big corporation politics / power play, rather than how it benefits the community.
The only thing positive I can say is I MUCH rather have Redhat buy them than Oracle. I think Redhat has been a positive community member and well I will invoke the mom rule for Oracle.
Earlier quoted context omitted.
> this is a good move by Red Hat to position themselves with rkt Red Hat does not give a damn about rkt. They care about Kubernetes, specifically establishing and consolidating a dominant position in upstream kubernetes development. CoreOS helps them do that. rkt on the other hand is a dead project and completely useless to Red Hat. > Google, on the other hand, doesn't need Docker to plug any holes in their go to mar…
Frankly, I'm not sure why Google would acquire RedHat, SAP or Oracle. I'm not sure what will be gain from that. Google probably doesn't care about the softwares these companies provides as it has its own internal alternatives/derivative and Google is not really a software vendor, so it's a bit outside of their core business. What would make more sense in my opinion would be for Google to have a partnership with a big…
They do: they have a Cisco partnership for Google Cloud.
Earlier quoted context omitted.
Because it does the rest for you, magically. You mount a config file into the system, but CoreOS on it (or boot per PXE), and coreOS does the entire rest for you. You never have to install or reinstall, never have to deal with updates. If you put that config file on any system with coreOS, it'll be exactly like yours. This means I can create a config to tell a server to join a kubernetes cluster, and then whenever I…
Ah, I see. So it's basically integrated Puppet, but with first class support from the configured system
And it automatically handles updates across the cluster - only a certain amount of servers restarts at a time, allowing you to stay constantly up while handling updates automatically, and potentially scaling out in seconds.
It's sad RedHat EOL'd it immediately.
Earlier quoted context omitted.
I agree that this is a good move by Red Hat to position themselves with rkt and Quay ahead of Docker going to Microsoft (who will pay a premium to try to put this genie back into the bottle) Given their self-inflicted XHR debacle that dethroned Office, I just don't see Microsoft passing up this opportunity. Google, on the other hand, doesn't need Docker to plug any holes in their go to market unless it's a blocking p…
> this is a good move by Red Hat to position themselves with rkt Red Hat does not give a damn about rkt. They care about Kubernetes, specifically establishing and consolidating a dominant position in upstream kubernetes development. CoreOS helps them do that. rkt on the other hand is a dead project and completely useless to Red Hat. > Google, on the other hand, doesn't need Docker to plug any holes in their go to mar…
Interesting thought, although these merger/acquisitions play out over quarters and years. Not really conducive to a 12 episode season every year. And seems Silicon Valley has already had a touch of this type of narrative :)
Earlier quoted context omitted.
Fedora / CentOS Atomic, which is Redhat's "clone" of container linux.
Atomic (or at least OStree) predates ContainerLinux by quite a bit. Also Atomic is more than just an OS; it's a system of reliable upgrades / versions switching. So it's got something in common with NixOS.
I used to be a gnome foundation member (I trained Andrea Veri on the sysadmin team who trained Patrick Uiterwijk, the current lead sysadmin for GNOME) when Colin Watson wrote OSTree. He was talking about it and some of the ideas from it at the KDE/GNOME desktop summit in Berlin (2011ish) in some of the comments after https://desktopsummit.org/program/sessions/improving-how-we-...
At the following Boston (GNOME) developer summit one of the big conversational points sans Ubuntu pulling away from GNOME to build Unity was the idea of GNOME OS because Linux was hard then. He built rpm-ostree after that, and it was after CoreOS as a distro was a thing.
rpm-ostree's first commit was Dec 21, 2013: https://github.com/projectatomic/rpm-ostree/commit/958dfa435...
https://coreos.com/blog/coreos-fourth-birthday CoreOS as a company was created on July 13th, 2013.
TL;DNR: It's complicated, but Atomic as a distro most definitely does not predate ContainerLinux as rpm-ostree didn't exist when CoreOS the company was founded.
Earlier quoted context omitted.
Atomic doesn't predate CoreOS. CoreOS = 2013 Atomic host = 2014
OSTree (the foundation for it) was built as part of GNOME Continuous in 2011.
A quick D&B search on CoreOS, Inc. shows revenues of ~$550,000 [1], which means at $250m acquisition price, RH paid ~454X revenues..! [1] http://www.hoovers.com/company-information/company-search.ht...
I have personally seen checks cut to CoreOS that were larger than the D&B number you quote. The set of similar corporate customers we'd run into was surprisingly vast and diverse. Redhat's made a brilliant move here.
My point was not to imply this is a bad deal for any of the involved parties, but simply to add a data point to the discussion, one which other entrepreneurs looking for areas to add value should find highly interesting.
Earlier quoted context omitted.
Because it does the rest for you, magically. You mount a config file into the system, but CoreOS on it (or boot per PXE), and coreOS does the entire rest for you. You never have to install or reinstall, never have to deal with updates. If you put that config file on any system with coreOS, it'll be exactly like yours. This means I can create a config to tell a server to join a kubernetes cluster, and then whenever I…
Ah, I see. So it's basically integrated Puppet, but with first class support from the configured system
No package management or bloated softwares distributed.
It's immutable infrastructure. You configure your host once during provisioning, then it can accept container workloads in your cluster.