0e4a0d726b
* Updated the JSON client to be consistent with the library. The JSON client requires two JSONs, 1. JOB json -- contains job description. 2. Config json -- contains configuration information such as username, password, schedulerUrl, zookeeper cluster configuration etc. * Job json using docker-compose executor. Used https://github.com/paypal/dce-go/blob/develop/examples/client.go#L50 to create a json file for a job that uses the docker-compose executor. The current job json file (examples/job.json) uses an outdated version of docker-compose executor. Once examples/client.go has been modified to use examples/job_dce.json, it should be okay to get rid of examples/job.json. * Run thermos jobs using json client. Added an extra field to JobJson, ExecutorDataFile, that holds the path to the json file representing the executor configuration data. Added a new example job json file (examples/job_thermos.json) that is to be passed to the json client along with the config file to run a thermos job. * Using scheduler URL instead of leader from zk. The endpoints returned by ZKEndpoints(...) is not reachable from outside the vagrant box. Hence, using the scheduler URL directly. * Added docs for using dce-go and json client. * Place json client docs in separate subsection. * Config now embeds realis.Cluster to be backwards compatible with the python client cluster.json file. Changed the type of Transport to string to stay flexible if new transport types come up. JSON is used as the default transport option is not transport is provided with the config.
21 lines
No EOL
393 B
JSON
21 lines
No EOL
393 B
JSON
{
|
|
"name": "sampleapp",
|
|
"cpu": 0.25,
|
|
"ram_mb": 256,
|
|
"disk_mb": 100,
|
|
"executor": "docker-compose-executor",
|
|
"service": true,
|
|
"ports": 4,
|
|
"instances": 1,
|
|
"uris": [
|
|
{
|
|
"uri": "http://192.168.33.8/app.tar.gz",
|
|
"extract": true,
|
|
"cache": false
|
|
}
|
|
],
|
|
"labels":{
|
|
"fileName":"sampleapp/docker-compose.yml,sampleapp/docker-compose-healthcheck.yml"
|
|
}
|
|
|
|
} |