[
https://issues.apache.org/jira/browse/AURORA-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615730#comment-14615730
]
Renan DelValle commented on AURORA-1376:
----------------------------------------
[~wfarner], thanks for the input. I'll go with JSON in that case. I researched
different libraries to use for parsing and settled upon gson due to ease of use
and performance (not that it makes a huge difference but it's a +).
Here's what the schema is looking like right now for JSON, any input would be
appreciated. Not all fields will be required and this will be determined
between the use of custom executors (thermos included) and the mesos command
executor.
{code:title=JSON|borderStyle=solid}
{
"thermos":{
"executorPath":"/home/vagrant/aurora/dist/thermos_executor.pex",
"executorResources":[
"testURI"
],
"thermosObserverRoot":"/var/run/thermos",
"executorFlags":"--announcer-enable --announcer-ensemble localhost:2181",
"executorOverhead":{
"numCpus":0.25,
"disk_mb":0,
"ram_mb":128,
"numPorts":0
},
"globalContainerMounts":[
"/host:/container:ro"
]
},
"mesos-command":{
"executorResources":[
],
"executorOverhead":{
"numCpus":.25,
"disk_mb":0,
"ram_mb":2,
"numPorts":0
},
"globalContainerMounts":[
],
"commandValue":"test"
}
}
{code}
As side note, the commandValue field is only there temporarily to be able to
show that the mesos command executor works. Right now there's currently no way
to get that info to the executor (AFAIK) until the client is modified to
support custom executors and are able to pass that info the command line
executor.
> Create support for custom executors in Scheduler
> ------------------------------------------------
>
> Key: AURORA-1376
> URL: https://issues.apache.org/jira/browse/AURORA-1376
> Project: Aurora
> Issue Type: Sub-task
> Components: Scheduler
> Reporter: Renan DelValle
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
