On 02/22/2015 06:35 AM, [email protected] wrote:
Last friday i put some Ansible scripts on github for provisoning a multi
AZ cluster on AWS.
You could have a look at it
https://github.com/roybos/aws-mesos-marathon-cluster and maybe it helps you.
It basically creates a VPC within an AWS region and setups 1 node in 3 AZ's.
All nodes are currently equal(mesos master and slave are on the same
machine) which is fine for smaller clusters for let's say 3 to 30 nodes.
Roy Bos
Very cool. I'm new to ansible, but I like what I've learns so far.
What would be cool is if some thing like this ansible example was for
just 3 (generic linux ) system that are installed from sources. No
binaries, no distro specific packages, just pure, raw sources. That
way it would provide a baseline for installation on all sorts of linux
(embedded, vm, container, uncommon_distro, different architectures like
arm64 etc etc) based systems.
Any ansible guides for generic mesos installs from sources would be
of keen interests to many folks.
After that in-house from sources methodology is viable, I'm quite
certain companies will want to augment their local (in-house) cluster
resources, with resources from vendors, particularly in a dynamic mode
of utilization. Therefore, within the in-house resources mixed
(supplemented) with vendor resources is the future of cluster computing.
ymmv.
Sadly, I see little progress on this open systems approach, and that
concerns me greatly for the viability of the mesos cluster. Is it indeed
going to be limited to large corporations trying to sell something
nobody wants; or are there going to be open source methodologies
developed that streamline the installation of mesos
inside of a medium size company with modest resources.
Ansible is the key technology here combined with building up a mesos
cluster FROM 100% SOURCES.
Put that in your presentation at mesos con(artists?)
James
