i found the answer by my self sorry if i disturbed you.

2016-04-26 15:19 GMT+02:00 Stefano Bianchi <[email protected]>:

> Now that it is running, how can i check the User Interface?
>
>
> 2016-04-26 15:18 GMT+02:00 Stefano Bianchi <[email protected]>:
>
>> Yes, now it's running!!! June you are awesome!!!
>>
>> 2016-04-26 15:16 GMT+02:00 Stefano Bianchi <[email protected]>:
>>
>>> i have done these 2 commands, now jupyter is in deploying in marathon,
>>> staging in mesos.
>>> Is there some additional configuration needed?
>>>
>>> 2016-04-26 15:13 GMT+02:00 Stefano Bianchi <[email protected]>:
>>>
>>>> June i tried to run your json, but the task is waiting, and if starts
>>>> it failed immediately.
>>>>
>>>> I guess because i did not type this commands:
>>>>
>>>>
>>>>    1.
>>>>
>>>>    echo 'docker,mesos' > /etc/mesos-slave/containerizers
>>>>
>>>>    2.
>>>>
>>>>    $ echo '5mins' > /etc/mesos-slave/executor_registration_timeout
>>>>
>>>>
>>>> Could it be the problem?
>>>>
>>>> 2016-04-26 15:02 GMT+02:00 Stefano Bianchi <[email protected]>:
>>>>
>>>>> Thank you June taylor, it is axactly what i was intending.
>>>>> if it is not disturbing you, i try jupyter notebook as well, just to
>>>>> make some tests on how to launch marathon.
>>>>> stay tuned :)
>>>>>
>>>>> 2016-04-26 14:58 GMT+02:00 Stefano Bianchi <[email protected]>:
>>>>>
>>>>>> thanks haosdent.
>>>>>> actually i have run this kind of apps through rest api.
>>>>>> Now i want learn how to laung docker files. I found this exaple:
>>>>>>
>>>>>> {
>>>>>>   "container": {
>>>>>>     "type": "DOCKER",
>>>>>>     "docker": {
>>>>>>       "network": "HOST",
>>>>>>       "image": "group/image"
>>>>>>     },
>>>>>>     "volumes": [
>>>>>>       {
>>>>>>         "containerPath": "/etc/a",
>>>>>>         "hostPath": "/var/data/a",
>>>>>>         "mode": "RO"
>>>>>>       },
>>>>>>       {
>>>>>>         "containerPath": "/etc/b",
>>>>>>         "hostPath": "/var/data/b",
>>>>>>         "mode": "RW"
>>>>>>       }
>>>>>>     ]
>>>>>>   }}
>>>>>>
>>>>>>
>>>>>> I am able to link the correspondent field in the marathon UI with
>>>>>> what is written in this json.
>>>>>> What i need to understand is, what i should write in:
>>>>>>
>>>>>>  "image": "group/image"
>>>>>>
>>>>>> i mean, with what i have to replace group and image?
>>>>>> For instance, if i would run wordpress container on docker hub what i
>>>>>> should put replacing "group/image" ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2016-04-26 14:30 GMT+02:00 haosdent <[email protected]>:
>>>>>>
>>>>>>> This is marathon REST API document:
>>>>>>> https://mesosphere.github.io/marathon/docs/rest-api.html#post-v2-apps
>>>>>>> . Usually we define a task json file and call the rest api.
>>>>>>>
>>>>>>> For example, create tasks.json which content is
>>>>>>>
>>>>>>> ```
>>>>>>> {
>>>>>>> "id": "/test-sleep",
>>>>>>> "cmd": "sleep 200"
>>>>>>> }
>>>>>>> ```
>>>>>>>
>>>>>>> And
>>>>>>>
>>>>>>> ```
>>>>>>> curl -X POST -H "Content-type: application/json" 
>>>>>>> http://${YOUR_MARATHON_ADDR}:8080/v2/apps
>>>>>>> -d @tasks.json
>>>>>>> ```
>>>>>>>
>>>>>>> You could find more field definitions in their document.
>>>>>>>
>>>>>>> On Tue, Apr 26, 2016 at 8:24 PM, Stefano Bianchi <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Hi guys
>>>>>>>>
>>>>>>>> i'm trying to follow the instructions on mesosphere documentation,
>>>>>>>> but it is a little bit unlear for me that i am new to this world.
>>>>>>>> i' would like to launch a wordpress container, present on docker
>>>>>>>> hub here https://hub.docker.com/_/wordpress/ , from marathon UI
>>>>>>>> but i don't understand the mechanism.
>>>>>>>> I understood that i don't have to specify a command in "Command"
>>>>>>>> field, but i don't know how to fill the dockers fields in marathon UI 
>>>>>>>> to
>>>>>>>> launch wordpress container.
>>>>>>>> Could you please help me or tell me where i can find a clearer
>>>>>>>> documentation?
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Haosdent Huang
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to