| j_king | I think I might've fixed it. pebkac. | 00:57 |
|---|---|---|
| j_king | https://code.launchpad.net/~james-agentultra/charms/precise/mongodb/join-replicaset-test/+merge/296497 | 00:57 |
| === Zetas_ is now known as Zetas | ||
| === FourDollars_ is now known as FourDollars | ||
| === Tribaal_ is now known as Tribaal | ||
| === med_ is now known as Guest47242 | ||
| bodie_ | how does Juju compare to Kubernetes? | 11:56 |
| jrwren | bodie_: something still needs to deploy all of your systems that are going to run k8s and juju is excellent at that. | 14:10 |
| jrwren | bodie_: https://jujucharms.com/kubernetes/trusty/ | 14:10 |
| bodie_ | jrwren, I see, so Juju is more of a PaaS orchestrator and then actually scheduling containers on the platform might be the role of something like Kube? Can't Juju also handle container scheduling? I might have misunderstood a bit | 15:14 |
| magicaltrout | hey bodie_ I don't use k8s so you're talking to the uneducated here, but what you write is my understanding of it | 15:16 |
| bodie_ | magicaltrout, do you use a different container scheduler on top of juju, or just juju? My understanding was that Juju can also handle container scheduling via lxd on units | 15:18 |
| bodie_ | I think that's where my confusion is: do you even need kube if you're running juju? | 15:18 |
| magicaltrout | sorry bodie_ you caught me watching youtube instead of monitoring IRC ;) | 15:24 |
| magicaltrout | personally in production deployments I just use plain Juju, that said I am working on DC/OS support for Juju for one client | 15:24 |
| magicaltrout | for development and testing I often use LXD & Juju because it provides a pretty good simulation on my development server | 15:25 |
| magicaltrout | but LXD support is currently LXD local not LXD remote, so you cant do it in a cluster or anything like that | 15:25 |
| magicaltrout | that said of cause plenty of people do use Juju and K8S just as it underpins a large number of openstack deployments | 15:26 |
| bodie_ | Ah, I see | 15:34 |
| bodie_ | Thanks magicaltrout | 15:35 |
| jrwren | bodie_: I think it is definitely true that for many workloads you don't need k8s if you are running juju. | 15:35 |
| jrwren | bodie_: That said, they are different things. Juju is an universal modeling system for software application workflows. K8s is a management control system for docker. | 15:36 |
| jrwren | bodie_: e.g. k8s self-healing, service disco and load balancing features, afaik, juju has no such equivalent. A charm might provide it, but juju itself does not. | 15:38 |
| bodie_ | I think that makes sense | 15:38 |
| bodie_ | Juju is more for modeling a specific arrangement of services where Kube is more for scheduling containers on some platform | 15:39 |
| jrwren | *whew* good. I do not feel confident in my ability to explain the differences, so I'm happy it makes some sense. | 15:39 |
| bodie_ | I think it's a complicated topic, lol | 15:39 |
| === Salty is now known as SaltySolomon | ||
| === flip214_ is now known as flip214 | ||
| magicaltrout | you know when you're on the road with work and the your partner isn't replying to texts probably cause the kids are being really annoying, so you ask how her day has been and tell her to call whenever if she wants a chat. But secretly you hope she doesn't because its going to involve a lot of complaining and you're sat 1000's of miles away....... | 18:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!