[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Commented] (MESOS-3688) Get Container Name information when launching a container task
From:       Sandor_Szücs_(JIRA) <jira () apache ! org>
Date:       2015-10-29 14:29:27
Message-ID: JIRA.12903693.1444387717000.96042.1446128967962 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=14980513#comment-14980513 ] 

Sandor Szücs commented on MESOS-3688:
-------------------------------------

From user point of view, the best case would be to get the current running \
containerid and name from docker, but such that Mesos knows about running containers, \
too. 

For example we plan to stream logs to files, cloud-log-providers and other \
log-consumers with that ID/name as SRC identification. Our deploy tool should know \
about this ID/name from a mesos framework (marathon).  Logfiles can easily written to \
files that are mapped to applications from logging services and can be found in a \
directory something like: path/to/logs/<dockername>/<dockerid>.log .

> Get Container Name information when launching a container task
> --------------------------------------------------------------
> 
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Affects Versions: 0.24.1
> Reporter: Raffaele Di Fazio
> Assignee: Kapil Arya
> Labels: mesosphere
> 
> We want to get the Docker Name (or Docker ID, or both) when launching a container \
> task with mesos. The container name is generated by mesos itself (i.e. \
> mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps") and it would \
> be nice to expose this information to frameworks so that this information can be \
> used, for example by Marathon to give this information to users via a REST API.  To \
> go a bit in depth with our use case, we have files created by fluentd logdriver \
> that are named with Docker Name or Docker ID (full or short) and we need a mapping \
> for the users of the REST API and thus the first step is to make this information \
> available from mesos. 



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


[prev in list] [next in list] [prev in thread] [next in thread]