singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SINGA-89) SINGA-89 Add Docker support
Date Wed, 21 Oct 2015 05:38:27 GMT

    [ https://issues.apache.org/jira/browse/SINGA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966278#comment-14966278
] 

ASF subversion and git services commented on SINGA-89:
------------------------------------------------------

Commit 1f513ec1e6ea75c8b1dcd0582022a7669bab595e in incubator-singa's branch refs/heads/master
from [~ug93tad]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=1f513ec ]

SINGA-89  Add Docker support

Docker is a Linux container which is fast to deploy and incurs small overhead. A Docker container
functions like a light-weight virtual machine and runs in its own isolated environment. There
are at least two benefits in building adding Docker support for SINGA:

+ Out of the box deployment of SINGA: the image, once built, contains the complete environment
necessary to start SINGA.

+ Light-weight development and testing environment for distributed features. The image can
be used to set up a test-bed consisting of many independent nodes (each node has its own IP
address), without the need for cluster hardware.

We add to Github a Dockerfile specifying how to build SINGA image, from which the user can
construct the image by executing:

sudo docker build -t singa/base .

The user can choose another name beside singa/base . The build process can take a long time,
but it needs to be done only at one host and the result image can then be copied to other
hosts.

We also add another Dockerfile which adds Mesos and Hadoop ontop of SINGA. This is closely
related to SINGA-11. The image created from this Dockerfile is used to set up the distributed
test bed.

See the README.md for more details of the images and how to use them.

IMPORTANT We assume that every host has Docker running. Two nodes on the epiC cluster (`ciidaa-c18`
and `ciidaa-c19`) are set up with Docker and the pre-built images.

IMPORTANT For now, the Dockerfile for building Mesos+Hadoop+SINGA will pull the latest from
ug93tad's (Anh's) SINGA-11 branch. This pull step is removed after SINGA-11 is merged to the
project's master branch.


> SINGA-89 Add Docker support
> ---------------------------
>
>                 Key: SINGA-89
>                 URL: https://issues.apache.org/jira/browse/SINGA-89
>             Project: Singa
>          Issue Type: New Feature
>            Reporter: Anh Dinh
>            Assignee: Anh Dinh
>
> Docker is a Linux container which is fast to deploy and incurs small  overhead. A Docker
container functions like a light-weight virtual machine and runs in its own isolated environment.
There are at least two benefits in building adding Docker support for SINGA:
> # Out of the box deployment of SINGA: the image, once built, contains the complete environment
necessary to start SINGA.
> # Light-weight development and testing environment for distributed features. The image
can be used to set up a test-bed consisting of many  independent nodes (each node has its
own IP address), without the need for cluster hardware.
> We add to Github a {{Dockerfile}} specifying how to build SINGA image, from which the
user can construct the image by executing:
> {code}
> sudo docker build -t singa/base .
> {code}
> The user can choose another name beside {{singa/base}} . The build process can take a
long time, but it needs to be done only at one host and the result image can then be copied
to other hosts. 
> We also add another {{Dockerfile}} which adds Mesos and Hadoop ontop of SINGA. This is
closely related to [SINGA-11|https://issues.apache.org/jira/browse/SINGA-11]. The image created
from this Dockerfile is used to set up the distributed test bed. 
> See the {{README.md}} for more details of the images and how to use them. 
> h5. Important
> We assume that every host has Docker running. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message