Repository navigation
Replies: 4 comments 4 replies
|
There is a relevant old discussion on the namespace/env/stack/environment concept: #94 I'm leaning now more towards a concept of an app/stack (1 compose file -> 1 app) with some reasonable defaults for isolation. I wouldn't like to replicate the k8s generic namespace concept that only complicates things. But this is not something I'd prioritise now. Regarding multi-tenancy, what specifically are we talking about (users, teams, services)? |
|
Thanks for your reply, I understand the complication with namesapces, amnd feature creep towards k8s.
I want to run (mostly) webservices for possibly 100s of users. Each user can log in into the uncloud nodes, but they should only be able to modify their own webservice. Reading between the lines, this should just work, as in the end it's a docker(-compose) per user, no? |
yes, and exactly that happened: fighting with docker-compose. So i like the route you took, seems much saner, also more secure because you don't have to chase docker-(-compose).
Understood. Yes this is complex, but it seems to me (still very new to uncloud) that the current simple(r) setup of it all should indeed allow for something like it. Also unsure how it should look; using unix users to separate things, is also how android sandboxes, so not entirely a dumb idea. Having namespaces == uid doesn't seem batch shit crazy, with the caveat that in our setup we have all user provisioing done for us, so that doesn't get pulled into uncloud. IOW: iff uid == namespaces in some future; does uncloud need to manage the accounts or do you just say: this is not our problem. This is what I had done in pgo - but then (due to docker-compose), you stil run into namespace collision of network names, services names etc. Became messy and how to understood, because the first services started would globber a namespace and then a second one could come along and don't start because of collossion. But threading through the login name as-if it's a namespace would certainly help here. Again, I'm also fuzzy on what the best way forward be. For us at $DAYJOB, this looks really promising, but before we can (also) give it to our users, some multi-tenant thing should be available |
another level of indirection :) Yes, I like that direction, making it all composable. This would fit our use-case well. As it stands we can totally use uncloud on a per-vm basis, the biggest win there is that each website + DB we have right now would become it's own uncloud deployment. |
Uh oh!
There was an error while loading. Please reload this page.
More of question, I guess. But the multi tenant story is basically multiple user accounts on the machines?
(couldn't find any docs explicitly saying this)
Namespaces (#208) are somehow related to this, I guess?
All reactions