Microsoft recently announced upcoming native container support in Windows.
http://blogs.technet.com/b/server-cloud/archive/2015/04/08/microsoft-announces-new-container-technologies-for-the-next-generation-cloud.aspx
On Fri, Mar 6, 2015 at 1:01 PM, Alex Rukletsov a...@mesosphere.io wrote:
Hi
Hi Alexandre,
sorry for a tardy reply. Mesos master and slaves (or workers, as per
MESOS-1478) communicate via protobuf messages. Any agent that understands
these messages can be (or pretend) a Mesos slave. So the answer to your
question is yes, it is possible to provide an alternative slave
Hi Tim,
if we're operating in a cloud base environment (OpenStack), would that mean
we could run this containerizer on the hypervisor host, or anywhere else,
and manage remotely the executors inside Windows cloud instances?
On Fri, Feb 20, 2015 at 3:14 PM, Tim Chen t...@mesosphere.io wrote:
Hi
I stumbled across Spoon: https://spoon.net/docs/getting-started
It doesn't look very open, but perhaps it provides a lighter footprint for
containerization vs. Windows-based VMs. If they provide the right
integration API's, perhaps one could write a Spoon containerizer?
On Fri, Feb 20, 2015 at
In that case, is it possible to make a stripped down Slave implementation
that only does the minimum to interact with the Master to relay the
resources and tasks?
I'm not sure I understand fully the complete responsibilities of the Slave
and how the Master sees it.
On Fri, Feb 20, 2015 at 3:49
Hi James,
I agree this is a compelling feature, but it might not be an absolute
requirement for many use cases.
We're evaluating Mesos to build custom frameworks for distributed
computation that needs to be cross-platform (Windows mainly), where some
tasks would be oriented for video rendering
6 matches
Mail list logo
