singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SINGA-11) Start SINGA on Apache Mesos
Date Wed, 21 Oct 2015 05:38:27 GMT


ASF subversion and git services commented on SINGA-11:

Commit d6c3963541ed2b639e5193906bf3ec38d8bd3d54 in incubator-singa's branch refs/heads/master
from [~ug93tad]
[;h=d6c3963 ]

SINGA-89 Add Docker support

Changed the Dockerfile for building Mesos to compile the scheduler directly from the main
brach (after SINGA-11 is merged).

> Start SINGA on Apache Mesos
> ---------------------------
>                 Key: SINGA-11
>                 URL:
>             Project: Singa
>          Issue Type: New Feature
>            Reporter: wangwei
>            Assignee: Anh Dinh
> Apache Mesos is a fine-grained cluster management framework which enables resource sharing
in the same cluster. Mesos abstracts out the physical configurations of cluster nodes, and
presents resources to the users in the form of "offers". SINGA uses Mesos for two purposes:
> # To acquire necessary resources for training the model.
> # To launch and monitor progress of the training task.
> To these ends, we implement a {{SINGA Scheduler}} which interacts with Mesos master.
The scheduler is called when the user wants to start a new SINGA job, and it performs the
following steps:
> # Read the job configuration file to determine necessary resources in terms of CPUs,
memory and storage.
> # Wait for resource offers from the Mesos master.
> # Determine if the offers meet the requirement of resources.
> # Prepare the task to launch at each slave:
> #* Deliver the job configuration file to the slave node.
> #* Specify the command to run on the slave:
> {code}
> singa -conf ./job.conf
> {code}
> #* Launch and monitor the progress
> For step 3, we currently implement a simple scheme: the number of CPUs offered by each
Mesos slave exceed the total number of SINGA worker and SINGA server per process. In other
words, each selected slave must be able to run the entire worker group or server group.
> For step 4, we currently relies on HDFS to deliver the configuration file to each slave.
Particularly, we write the file to a known directory (different for each job) on HDFS and
ask the
> slave to use its Fetcher utility to download the file before executing the task.
> The development and testing environment for this ticket are created from [SINGA-89|]
> We will create a {{}} file explaining the steps.
> h5. Important
> We assume that SINGA, Mesos and Hadoop are running at every node. 

This message was sent by Atlassian JIRA

View raw message