131–140 of 154 posts
Earlier quoted context omitted.
One more good experience. I created an cluster of dedicated servers ( 64 cores, 6TB of SSD storage and 256 GB of RAM, 1 GPU) using Rancher, for about 250 Euros/Month. This would cost at least 2k in a cloud such as AWS. There is a post about how I did with persistent storage here ( https://medium.com/@bratao/state-of-persistent-storage-in-k8... ) It really transformed my company DevOps. I´m VERY happy. If you can, use…
Where did you rent dedicated servers?
Earlier quoted context omitted.
One more good experience. I created an cluster of dedicated servers ( 64 cores, 6TB of SSD storage and 256 GB of RAM, 1 GPU) using Rancher, for about 250 Euros/Month. This would cost at least 2k in a cloud such as AWS. There is a post about how I did with persistent storage here ( https://medium.com/@bratao/state-of-persistent-storage-in-k8... ) It really transformed my company DevOps. I´m VERY happy. If you can, use…
Longhorn synchronously replicates the volume across multiple replicas stored on multiple nodes https://github.com/longhorn/longhorn At first look the numbers in the colourful table near the end, Piraeus/Linstor/DRBD seems 10x faster than Longhorn 0.8. The article goes into great depth of the (a)synchronous replication options of Piraeus, but doesn't mention that Longhorn always does synchronous replication. I wonder…
I´m really rooting for Longhorn. I´m a sucker for GUIs. But in my tests the performance is not there yet.
However, they opened a new epic ticket to focus on performance, and hopefully they will keep improving Longhorn after the acquisition.
Earlier quoted context omitted.
TL;DR: https://www.eqtgroup.com/Investments/Current-Portfolio/suse/ But we are mostly independent now. I.e we choose the directions.
> mostly independent Sounds like something Red Hat could say too...
There was also CoreOS, which has since been bought by RedHat, and Deis, since bought by Microsoft.
So now it's been turned back into an OS war. RedHat, SuSE, and Microsoft.This is fitting because kubernetes feels like an operating system for container clusters. After all, operating systems are just resource managers and schedulers like kubernetes is.
(For those interested, there are several kubernetes distributions that are not company backed and open source. Two of my favorites are Kubespray[1] and Typhoon[2].)
1: https://github.com/kubernetes-sigs/kubespray 2: https://typhoon.psdn.io/
Rancher was the last independent kubernetes distribution (that was company backed) as far as I can tell. There was also CoreOS, which has since been bought by RedHat, and Deis, since bought by Microsoft. So now it's been turned back into an OS war. RedHat, SuSE, and Microsoft.This is fitting because kubernetes feels like an operating system for container clusters. After all, operating systems are just resource manage…
Earlier quoted context omitted.
Why did you keep your TURN relays out of k8s?
Because we needed geographic distribution so that we don't end up hairpinning our users, and they only run a single service so the value prop is much lower. We use route 53 to do geodns across a number of cheap instances around the world (which is also nice, let's you pick regions with cheap bandwidth but good latency to major metro areas). We currently have TURN relays in Las Vegas, New York, and Amsterdam and that…
Earlier quoted context omitted.
They recently when through a Series D round for $75 million, but yet you believe they have half a billion in the bank? They were on their last leg begging for seed money to keep them afloat.
That's a lower estimate of the acquisition based on the info about this deal linked elsewhere in the thread and on the net.
Why?!? Why the worst enterprise distro out there had to?!? Canonical would have been perfect -________-
I was talking to both of them about on-prem solutions, and found the Rancher support covered Ubuntu hosts, and Canonical support covered Rancher. Was trying to understand which support contract we would need.
But something happened between the companies and they parted ways. And neither party would comment.
In the end, we ditched Rancher support. The price almost doubled from one year to another and covered very little. I was also unimpressed by the technical chops of the Rancher solutions architect they gave us, which didn't seem to know anything beyond the basic documentation on their site.
But we are using Rancher 2 and Rancher 1.6 in production and have been happy with the solution itself.
We are migrating our on-prem from VMware to OpenStack and may stick with Rancher as k8s provisioner if charmed k8s doesn't live up to the sales pitch.
We are a team of 4 people doing on-prem datacenters on 10+ sites around the world, so we need a little bit of plug and play.
The real news for me here is that SUSE still exists.
Every now and then I try a Linux distro other than SUSE (currently, openSUSE) and am left disappointed. Mostly it is the size of the repo. openSUSE has everything . I guess that shouldn't be too surprising, the Build Service also builds packages for distributions not their own: https://build.opensuse.org And of course there's really nothing as good as YaST for system configuration. They also provide a full aarch64 OS…
I've been through a number of distros; SUSE as mentioned, Mandrake, Debian, Gentoo, Arch, Mint, KDE Neon, probably others that I've forgotten. I installed openSUSE Leap 15.2 on my laptop last week and immediately I felt right at home. KDE as the default desktop with no weird modifications nor excessive vendor branding, plus a well thought out default Btrfs partitioning scheme with good use of subvolumes (and CoW disabled on /var, nice detail) and snapshots for easy backups and rollback in case of botched upgrades or config changes.
The only minor gripe I have is their choice to ship Firefox ESR, but I understand why they do it, and it was easy to add the official repo for the latest release version.