Nicely done sir. I have a similar project called Q2, still unpublished. I would be happy to talk to you about our projects and share ideas. Congratulations, you beat me to the punch!
I have had the very same keyboard shown in the article for more than ten years and it still works perfectly, although I was a bit disappointed at the time because it didn't feel quite the ones in the laptops. Lately though, I went all nostalgic and undusted an old IBM 1391405, that clicks like a charm while I am typing this.
Clear evidence that I am getting old and being left behind: of the four technologies named in that title I only have heard of one and have never actually used it.
You're still better than I am. I've heard of the latter three, I've never used a single one, and I still find it very difficult to understand what the core of the second one (Mesos) actually is because it's so shrouded in buzzwords and vague descriptions.
All I got was that it's some sort of userspace microkernel geared around abstracting the computing resources of machines (nodes) in categories like CPU/RAM/disk and expose them programmatically through a cluster-wide API. The master daemon makes resource offers to a slave daemon, which in turn runs ported applications (be it Hadoop, Jenkins, ElasticSearch or whatever) called Mesos frameworks that have to be ported to this Scheduler/Executor paradigm (sort of like a cluster resource-level MapReduce, I presume?) in order to perform Tasks.
Mesosphere is the whole stack as an integrated OS. Marathon is pretty easy to understand - it's an init system/framework supervisor that operates on a higher level of abstraction than simple OS processes.
Mesos is a generic cluster manager. Its job is to keep track of available resources (RAM/CPU/Disk space) on a group of machines, and to share these resources between "Frameworks", which are more or less specialized distributed applications.
Available framework include existing applications that have been ported to Mesos (Jenkins, Hadoop, Elasticsearch, ...), along with some that have been developed specifically for Mesos (Chronos for running cron-like tasks, Marathon for running long-running tasks).
For example, you can tell Marathon "I want to run 10 instances of ./my_code, with 512MB of RAM and 2 cores each", and the framework and Mesos will collaborate to figure out where to run them. As a bonus, Mesos has some Docker integration, so you can natively do things like "Start 20 instances of container my_organization/my_app".
The datacenter OS thing is a bit of a shaky metaphor, but the idea is that, like the OS does for a single computer, the role of Mesos is to view your cluster resources as a single pool, and to try to fairly allocate these resources between multiple (distributed) applications.
"From the investigation of the coordinated anarchyst groups, it is derived that their members might be the alleged authors of several attacks with home made explosive artifacts in all the national territory"
Whether they are guilty of those charges or not, is of course a completely different matter.
The thing is, to use a 'secure email' or having a book named 'against democracy' is not proof of enough to relate them to those attacks.
at this point, to use a secure email and having that book was enough reason to put them in jail because of those attacks.
in chile the same thing happened, 14 people were arrested under similar charges (possessions of books and even a guns and roses posters). they spent years in prison while the trial was setted up and investigated. they were found not guilty 3 times...
they are currently in jail because they have the book against democracy and they use a secure email. if they are guilty or not, it will be resolved later on a trial. but they can spend years in prison without the trial be made.
