mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaston, Dan" <>
Subject RE: "Cluster of Workstations" type design for a Mesos cluster
Date Tue, 21 Jul 2015 16:02:19 GMT
Its not so much a matter of want to isolate them, I may not be able to due to limitations outside
of my control which may require them to be on their own private network.

From: Marco Massenzio []
Sent: Tuesday, July 21, 2015 12:47 PM
Subject: Re: "Cluster of Workstations" type design for a Mesos cluster

You're not crazy :)

This will work just fine, the Master takes up very little CPU/RAM, and, as you plan to have
it on your desktop you could even "wrap" with some send-notify script so that should it fail
or something, you could get an alert.
I'm not sure why you want to "segment" out the Agent Nodes and isolate them from (outbound)
web connectivity, the one thing to bear in mind is that you won't be able to install packages
directly (apt-get) and anything you want to run off them you will need to instead fuffle around
with binary installers and the like - then again, you may just install the smallest footprint
OS (CoreOS springs to mind) and maximize resources for tasks.

Keep us posted on how you progress, I may eventually go down the same path :)

Marco Massenzio
Distributed Systems Engineer

On Tue, Jul 21, 2015 at 6:44 AM, Gaston, Dan <<>>
Is there likely to be any issues with the Master? Given it would be an active desktop it would
be running all of the typical mesos master stuff, plus say an active Ubuntu desktop environment.
It would also need to host things like a local Docker registry and the like as well, since
the compute nodes wouldn’t have direct access to the wider internet.

From:<> [<>]
On Behalf Of Jeff Schroeder
Sent: Tuesday, July 21, 2015 10:42 AM
Subject: Re: "Cluster of Workstations" type design for a Mesos cluster

As far as mesos is concerned, compute is a commodity. This should work just fine. Put Aurora
or Marathon ontop of mesos if you need a general purpose scheduler and you're good to go.
The nice thing is that you can add additional slaves as you need. I believe heterogeneous
clusters are best if possible, but absolutely not a requirement of any sort.

On Tuesday, July 21, 2015, Gaston, Dan <<>>
Let’s say I had 2 high-performance workstations kicking around (dual 6-core, 2.4GHz, xeon
processors; 128 GB RAM each; etc) and a smaller workstation (single Xeon 4-core, 3.5GHz and
16 GB RAM) available and I wanted to cluster them together with Mesos. What is the best way
of doing this? My thought was that the smaller workstation would be at my desk (the other
two would be in the same office) because it would be used for development work and some general
tasks but would also be the master node of the mesos cluster (note that HA isn’t a requirement
here). This workstation would have two NICs, one connected to our institutional network and
the other making up the private network between the clusters.

Is this even doable? Normally you would have some sort of client submitting to the Master
but in this case the Master node would be serving up multiple roles. The other workstations
would probably not have access to the institutional network, so all software updates and the
like would have to be piped through the master workstation. There would also be a relatively
large NAS device connected into this network as well.

Thoughts and suggestions welcome, even if it is to tell me I’m crazy. I’m building a small
scale compute “cluster” that is fairly limited by budget (and the needs aren’t high
either) and it may not be able to be located in a datacenter, hence the cluster of workstations
type setup.


Dan Gaston, PhD
Clinical Laboratory Bioinformatician
Department of Pathology and Laboratory Medicine
Division of Hematopathology
Rm 511, 5788 University Ave.
Halifax, NS B3H 1V8

Text by Jeff, typos by iPhone

View raw message