Hi Bertrand, that's indeed something I haven't thought about yet, but as you say, the ContainerManager could support multiple backends at once and schedule a container wherever it thinks it makes sense. From the ContainerRouter's PoV, a container is just an IP address + Port, so that concern is encapsulated in the ContainerManager.
Cheers, Markus Am Mi., 15. Aug. 2018 um 10:35 Uhr schrieb Bertrand Delacretaz < bdelacre...@apache.org>: > Hi, > > On Tue, Aug 14, 2018 at 4:07 PM Markus Thömmes > <markusthoem...@apache.org> wrote: > ... > > > https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+future+architecture > ... > > Very clear proposal, thank you! And thanks for bringing the discussion > here. > > Is the ContainerManager meant to support multiple underlying > orchestrators? I'm thinking of a use case where you want to segregate > actions of a specific set of namespaces to a dedicated orchestrator. > This can be useful for cases where people don't trust existing > container isolation mechanisms. > > From my understanding it looks like this is covered, just wanted to check. > > -Bertrand > > > -Bertrand >
