4 ms·
This was my take, FWIW. https://www.theregister.com/2023/11/16/canonical_microcloud/ https://www.theregister.com/2023/11/16/canonical_microcloud/
by lproven 3y ago
This was my take, FWIW.
https://www.theregister.com/2023/11/16/canonical_microcloud/ https://www.theregister.com/2023/11/16/canonical_microcloud/
- linuxftw 3y agoThis demo is very hard to follow indeed. They are just jumping around, demoing features, but not talking about how it all fits together.
- lproven 3y agoI agree, but as I said in the article, the first stage of the demo failed, and after some frantic attempts to tear down and rebuild the cluster, they gave up, moved on to later stage of the demo, and then came back to it. Which is why it's incoherent and doesn't fit together.
- dilyevsky 3y agoThis is why you always prepare videos
- cloudbonsai 3y agoMmm. So is MicroCloud essentially a glue between LXD + Ceph? It's not really clear what the problem MicroCloud is trying to solve, though. Considering that LXD already supports multi-node clustering, why does anyone want another cluster manager on top of LXD?
- tyingq 3y agoParaphrased, they are saying LXD is more suited to running VMs or containers and not specifically microservices. It's missing sophisticated cross-container networking, centralized storage management, etc. So they are pitching a "simpler than K8S, more complicated than LXD" layer on top of LXD for that purpose. I suppose it also would compete with Proxmox, which is a somewhat different space than K8S. But other things it adds, like the web ui, RBAC, etc...put it in that space also.
- SoftTalker 3y agoI got Proxmox running in an on-prem cluster fairly easily. I was never able to figure out k8s. If MicroCloud is comparably easy to set up and manage as Proxmox, I'll definitely check it out.
- deleted 3y ago[deleted]
- 0xbadcafebee 3y agoSo basically it's VMware but with more nodes required