wangwei created SINGA-36:
----------------------------
Summary: Clean ModelProto, ClusterProto and JobProto
Key: SINGA-36
URL: https://issues.apache.org/jira/browse/SINGA-36
Project: Singa
Issue Type: Improvement
Reporter: wangwei
Currently, we use the google protocol buffer to generate ClusterProto and
ModelProto classes for cluster (i.e., worker, server, group, etc) configuration
and model (i.e., neuralnet, updater, etc) configuration respectively. Theses
classes provide functions to load/parse plain text configuration files.
To make the naming more representative and simplify the configuration process,
this ticket will:
* move worker, server and group configuration into JobProto, i.e., these
configurations are job/application specific.
* move ModelProto as a field of JobProto, because the neuralnet configuration
is also job specific.
* move zookeeper, hostfile, etc configuration into ClusterProto, because these
fields are shared by all jobs.
The configuration for ClusterProto is done when installing SINGA and is done
for only once. The configuration file is fixed at $SINGA/conf/singa.conf.
The configuration for JobProto is done every time a new job is submitted. The
conf file is $workspace/job.conf. Users submit the job by passing
-conf=$workspace to ./bin/singa-run.sh
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
