Earlier quoted context omitted.
The use case I described - Skyport's cloud managed secure servers - needs super high quality, self-recovering embedded code that made no assumptions about the network being high quality or reliable. I think the thing people - and especially the OpenStack guys - don't appreciate is how terrible it is to (a) lose a workload or (b) require someone visit the datacenter (which may actually be a colo in another state or ho…
I find your expectations to be unreasonably high. The self correcting system is a fiction and will always be a fiction. The indefatigable infrastructure that corrects the errant member system with 5 9s is a fiction and will always be a fiction.
Intel Pulls Out of OpenStack Effort It Founded with Rackspace
111–118 of 118 posts
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#112Earlier quoted context omitted.
You missed Red Hat, who seem to be the only company having major success with OpenStack [1] Most of IBM, Intel, HPE etc have thrown in the towel and now offer their own services on top of Red Hat OpenStack. OpenStack has now found itself beyond enterprise, and now being the de-facto platform for NFV running mobile networks, and I guess Red Hat are becoming the winner here as they are so used to supporting an OpenStac…
Canonical also have a strongly growing OpenStack business with no signs of pulling out from it.
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#113Earlier quoted context omitted.
Canonical also have a strongly growing OpenStack business with no signs of pulling out from it.
(Disclaimer: I work on Red Hat in the virtualization team). Canonical seriously lacks expertise in KVM (+QEMU+libvirt), and you cannot take that for granted when you have a customer with VMs crashing that is asking for a fix.
FWIW, I recently had to explicitly inform the Canonical Virt maintainers (of which there seem to be very few) about which patches that ought to be backported to fix a bug in one of their libvirt packages that was seriously affecting (i.e. preventing from patches being merged) OpenStack upstream CI environment.
The said bug had fixes already available upstream, and are straight backports with no conflicts. No one bothered to do the "unsexy" work of backporting & cutting a quick stable build.
Only after pointing out the commits (with help from one of the lead upstream libvirt maintainers), and posting them on a LaunchPad bug, did the Ubuntu maintainers stepped in to backport the said fixes.
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#114Earlier quoted context omitted.
The "a while back" qualifier here is important. Both Mesos and Kubernetes are relatively new projects in a rapidly moving space. FWIW we are running Kubernetes 1.4x with multiple redundant masters in production with no problems. We are also running Mesos/Marathon internally. These projects did have major issues early on but now they are becoming much more robust. For control we are using CoreOS with kube-aws. It actu…
Kubernetes and the push for it is religious. Get out of here with that. Not all of us have been industry < 10 years
In other news: http://i0.kym-cdn.com/photos/images/facebook/001/044/247/297...
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#115Earlier quoted context omitted.
Kubernetes and the push for it is religious. Get out of here with that. Not all of us have been industry < 10 years
I've been in "the industry" professionally since ~2005, and with Linux since 1998 or so. I have a business need for kubernetes and there is nothing at all religious about it. It is simply that we have lots of new applications that need to be spun up and deployed. They might need to scale up or scale down, and we have gobs and gobs of on-premise (read 0 cloud) new hardware. "API Driven" infrastructure is the best way…
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#116Earlier quoted context omitted.
Is Joyent's documentation less than three years old yet? I wanted to dive into Joyent but their wiki was skeletal. To make my comment more useful: I'm hearing good things about Proxmox and will likely lab it up soon. r/homelab has some feedback on it as well.
Their docs site has always been decent enough for us. https://docs.joyent.com/private-cloud Anything missing or questionable could usually be resolved by looking in the docs folder of the corresponding service's github repo.
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#117Earlier quoted context omitted.
I've been in "the industry" professionally since ~2005, and with Linux since 1998 or so. I have a business need for kubernetes and there is nothing at all religious about it. It is simply that we have lots of new applications that need to be spun up and deployed. They might need to scale up or scale down, and we have gobs and gobs of on-premise (read 0 cloud) new hardware. "API Driven" infrastructure is the best way…
A better 'story'? This is terrible jargon as is the entire storied approach. There are dozens of ways to achieve the technical outcome you aim at and docker is one. Docker is the less toil|overhead, less flexible|performant, vendor lock-in, learn a new toolset approach. Save your indignation for someone who doesn't know better.
Spare the drama dude. Just because something doesn't work for you doesn't mean it doesn't work very well for others.
Re: Intel Pulls Out of OpenStack Effort It Founded with Rackspace
#118the article mentions other big players pulling out or cutting jobs/funding related to OpenStack in recent months in addition to this latest move by Intel. Is this related to some endemic problem with the technology, big egos within the project, dominance by another outside player or what? Cursory searching doesn't reveal any "big thing". Maybe it's just dying a death by a thousand cuts.
I figure Intel's participation was hinged on supporting a growing fleet of competitors to AWS, who would bid up chip prices. I guess that isn't happening. IMO, OpenStack was sort of a consortium effort to compete with VMWare, AWS and Salesforce, but it's operational model is closest to AWS. Nearly all the big enterprise IT companies tied their rafts together hoping to stave the flow of customers. It doesn't appear to…