31–40 of 41 posts
Earlier quoted context omitted.
Thank you kindly.
Here's what I've found out... We have some customers who are using this configuration (including nvidia-docker) with some scheduling limitations. That being said, we haven't expressly integrated this use case, so anything Kubernetes has done in 1.7 is available, but not completely surfaced/taken advantage of.
Any chance of some documentation/HOWTO on how that was done?
Thanks again!
That would be a shame because I decided to use Cattle because it seemed simpler and lighter that something like Kubernetes.
So does this mean Cattle is dead in 2.0 and Kubernetes is the only orchestrator available? That would be a shame because I decided to use Cattle because it seemed simpler and lighter that something like Kubernetes.
Earlier quoted context omitted.
The team did a good job integrating the simplicity of the cattle experience on top of Kubernetes. Part of the goal of the tech preview is to see if we've balanced the goal correctly.
Will you continue supporting mesos and swarm? Will you continue using haproxy for load balancing, or there will be other choices also with GUI support? Any plans to implement similar approach for other massively used containers, like let's encrypt certs provisioning? It would be great to have custom forms for configs and env variables with input validation for parametrizable containers. (Not only for provisioning new…
The built in balancer is still HAProxy. Let's Encrypt integration is certainly a possibility but no immediate plans.
Volume support is not fully there in the current preview release, but all those projects will continue to be supported.
Anyone had experience running a cross vendor cloud setup with Rancher? How was the experience and were you able to reduce operating costs?
Using rancher cluster on 4 different hosts in different regions. Sometimes I face different problems with networking, but they are mostly fixed restarting the containers. Its just hard to detect or diagnose them in time. Integrated network state monitoring could be such a great feature for Rancher!
Earlier quoted context omitted.
Awesome! And yeah I've found a few resources of people who've managed it. Last time I tried to compile it, it got stuck on some x86-specific dependencies in the base images you guys were using I think. A year later and I'm finally starting to look at it again. Official support would be fantastic if possible; I would very happily start using it on hundreds of devices in the near future :D
I soon will be working on this as a contribution. Starting with RancherOS’s kernel through, and adding GPU support. Please include me in your comms.
Earlier quoted context omitted.
I soon will be working on this as a contribution. Starting with RancherOS’s kernel through, and adding GPU support. Please include me in your comms.
FYI some of the contributions related to ARM are mentioned in this issue: https://github.com/rancher/rancher/issues/9751
So does this mean Cattle is dead in 2.0 and Kubernetes is the only orchestrator available? That would be a shame because I decided to use Cattle because it seemed simpler and lighter that something like Kubernetes.
[Rancher employee] it essentially means the same Cattle experience (ui, api, compose files) as you used before, but under the hood kubernetes launches the containers.
Thanks guys, you're doing awesome work
Does it do blue-green deployments yet?
One thing though, it is unclear how much RAM Rancher 2.0 requires.
http://rancher.com/rancher2-0/ states 2 GB, while the Getting Started Guide at http://rancher.com/docs/rancher/v2.0/en/quick-start-guide/ says minimum of 4 GB RAM.