Re: Mesos metrics -> influxdb

[Andreas Fritzler]

@Michael: Great tutorial on KairosDB & Cassandra!

On Thu, Feb 25, 2016 at 7:11 PM, vincent gromakowski <
vincent.gromakow...@gmail.com> wrote:

> +1 for Telegraph
> Le 25 févr. 2016 19:08, "Pradeep Chhetri"  a
> écrit :
>
>> Telegraf already has a input plugin to push mesos metrics to influxdb (
>> https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mesos)
>>
>>
>> On Thu, Feb 25, 2016 at 5:32 PM, Aaron Carey  wrote:
>>
>>> Has anyone had a good experience recording mesos metrics into influxdb?
>>>
>>> I've found a couple of options, a collectd plugin which doesn't appear
>>> to work with version 0.24.x and a more up to date containerised option
>>> which randomly crashes regularly and doesn't appear to actually post any
>>> stats.
>>>
>>> Anyone have any good solutions?
>>>
>>>
>>>
>>
>>
>> --
>> Pradeep Chhetri
>>
>> In the world of Linux, who needs Windows and Gates...
>>
>

Re: Question regarding docker containerizer

[Jojy Varghese]

Hi Pradeep,

The relevant code if you are interested is at :

https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3561 

 
https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L3672 


-jojy


> On Feb 25, 2016, at 4:10 PM, Pradeep Chhetri  
> wrote:
> 
> Hi Jie,
> 
> I see executor_id as empty. Does this means that it is running as task and 
> there is no executor for it ? Although, in the ps output, I see mesos-slave 
> is spawning a mesos-docker-executor which in turn spawning the docker 
> command. Here is the detail of one of the marathon task:
> 
> {
> "id": "logs_role_kibana.3b024b6e-dbf3-11e5-bc67-56847afe9799",
> "name": "kibana.role.logs",
> "framework_id": "20150904-093718-2198675372-5050-22379-",
> "executor_id": "",
> "slave_id": "a4f30c35-eee7-4110-a82f-cab5522c9b1b-S4",
> "state": "TASK_RUNNING",
> "resources": {
> "cpus": 0.5,
> "disk": 0,
> "mem": 1024,
> "ports": "[31050-31050]"
> },
> "statuses": [
> {
> "state": "TASK_RUNNING",
> "timestamp": 1456427344.63661,
> "labels": [
> {
> "key": "Docker.NetworkSettings.IPAddress",
> "value": "172.17.0.11"
> }
> ],
> "container_status": {
> "network_infos": [
> {
> "ip_address": "172.17.0.11",
> "ip_addresses": [
> {
> "ip_address": "172.17.0.11"
> }
> ]
> }
> ]
> }
> }
> ],
> "container": {
> "type": "DOCKER",
> "docker": {
> "image": "kibana:4.3.1",
> "network": "BRIDGE",
> "port_mappings": [
> {
> "host_port": 31050,
> "container_port": 5601,
> "protocol": "tcp"
> }
> ],
> "privileged": false,
> "parameters": [
> {
> "key": "publish-all",
> "value": "true"
> }
> ],
> "force_pull_image": true
> }
> }
> },
> 
> 
> 
> On Thu, Feb 25, 2016 at 11:59 PM, Jie Yu  > wrote:
> You can checkout the state.json endpoint on the master
> 
> On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri  > wrote:
> Hello Jie,
> 
> Thank you for the quick reply. Sorry for asking silly question. How can i 
> look for the taskinfo of a running container ? Can i see the TaskInfo details 
> in the mesos master UI for a task?
> 
> On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu  > wrote:
> You can take a look at the TaskInfo. If the TaskInfo does not have 
> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the executor 
> and send the task to the executor.
> 
> - Jie
> 
> On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri  > wrote:
> Hello,
> 
> From docker containerizer documentation 
> (http://mesos.apache.org/documentation/latest/docker-containerizer/ 
> ), 
> 
> "Users can either launch a Docker image as a Task, or as an Executor."
> 
> How can i identify whether a docker container started by lets say marathon is 
> running as a task or as an executor ?
> 
> 
> Thank you.
> 
> -Pradeep
> 
> 
> 
> 
> 
> 
> -- 
> Pradeep Chhetri
> 
> In the world of Linux, who needs Windows and Gates...
> 
> 
> 
> 
> -- 
> Pradeep Chhetri
> 
> In the world of Linux, who needs Windows and Gates...

Re: mesos agent not recovering after ZK init failure

[Benjamin Mahler]

Feel free to create one. I don't have enough information to know what the
issue is without doing some further investigation, but if the situation you
described is accurate it seems like a there are two strange bugs:

-the silent exit (do you not have the exit status?), and
-the flapping from ZK errors that needed the meta data directory to be
removed to resolve (are you convinced the removal of the meta directory is
what solved it?)

It would be good to track these issues in case they crop up again.

On Tue, Feb 23, 2016 at 2:51 PM, Sharma Podila  wrote:

> Hi Ben,
>
> Let me know if there is a new issue created for this, I would like to add
> myself to watch it.
> Thanks.
>
>
>
> On Wed, Feb 10, 2016 at 9:54 AM, Sharma Podila 
> wrote:
>
>> Hi Ben,
>>
>> That is accurate, with one additional line:
>>
>> -Agent running fine with 0.24.1
>> -Transient ZK issues, slave flapping with zookeeper_init failure
>> -ZK issue resolved
>> -Most agents stop flapping and function correctly
>> -Some agents continue flapping, but silent exit after printing the
>> detector.cpp:481 log line.
>> -The agents that continue to flap repaired with manual removal of
>> contents in mesos-slave's working dir
>>
>>
>>
>> On Wed, Feb 10, 2016 at 9:43 AM, Benjamin Mahler 
>> wrote:
>>
>>> Hey Sharma,
>>>
>>> I didn't quite follow the timeline of events here or how the agent logs
>>> you posted fit into the timeline of events. Here's how I interpreted:
>>>
>>> -Agent running fine with 0.24.1
>>> -Transient ZK issues, slave flapping with zookeeper_init failure
>>> -ZK issue resolved
>>> -Most agents stop flapping and function correctly
>>> -Some agents continue flapping, but silent exit after printing the
>>> detector.cpp:481 log line.
>>>
>>> Is this accurate? What is the exit code from the silent exit?
>>>
>>> On Tue, Feb 9, 2016 at 9:09 PM, Sharma Podila 
>>> wrote:
>>>
 Maybe related, but, maybe different since a new process seems to find
 the master leader and still aborts, never recovering with restarts until
 work dir data is removed.
 It is happening in 0.24.1.




 On Tue, Feb 9, 2016 at 11:53 AM, Vinod Kone 
 wrote:

> MESOS-1326 was fixed in 0.19.0 (set the fix version now). But I guess
> you are saying it is somehow related but not exactly the same issue?
>
> On Tue, Feb 9, 2016 at 11:46 AM, Raúl Gutiérrez Segalés <
> r...@itevenworks.net> wrote:
>
>> On 9 February 2016 at 11:04, Sharma Podila 
>> wrote:
>>
>>> We had a few mesos agents stuck in an unrecoverable state after a
>>> transient ZK init error. Is this a known problem? I wasn't able to find 
>>> an
>>> existing jira item for this. We are on 0.24.1 at this time.
>>>
>>> Most agents were fine, except a handful. These handful of agents had
>>> their mesos-slave process constantly restarting. The .INFO logfile had 
>>> the
>>> following contents below, before the process exited, with no error
>>> messages. The restarts were happening constantly due to an existing 
>>> service
>>> keep alive strategy.
>>>
>>> To fix it, we manually stopped the service, removed the data in the
>>> working dir, and then restarted it. The mesos-slave process was able to
>>> restart then. The manual intervention needed to resolve it is 
>>> problematic.
>>>
>>> Here's the contents of the various log files on the agent:
>>>
>>> The .INFO logfile for one of the restarts before mesos-slave process
>>> exited with no other error messages:
>>>
>>> Log file created at: 2016/02/09 02:12:48
>>> Running on machine: titusagent-main-i-7697a9c5
>>> Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg
>>> I0209 02:12:48.502403 97255 logging.cpp:172] INFO level logging
>>> started!
>>> I0209 02:12:48.502938 97255 main.cpp:185] Build: 2015-09-30 16:12:07
>>> by builds
>>> I0209 02:12:48.502974 97255 main.cpp:187] Version: 0.24.1
>>> I0209 02:12:48.503288 97255 containerizer.cpp:143] Using isolation:
>>> posix/cpu,posix/mem,filesystem/posix
>>> I0209 02:12:48.507961 97255 main.cpp:272] Starting Mesos slave
>>> I0209 02:12:48.509827 97296 slave.cpp:190] Slave started on 1)@
>>> 10.138.146.230:7101
>>> I0209 02:12:48.510074 97296 slave.cpp:191] Flags at startup:
>>> --appc_store_dir="/tmp/mesos/store/appc"
>>> --attributes="region:us-east-1;" --authenticatee=""
>>> --cgroups_cpu_enable_pids_and_tids_count="false"
>>> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
>>> --cgroups_limit_swap="false" --cgroups_root="mesos"
>>> --container_disk_watch_interval="15secs" --containerizers="mesos" 
>>> "
>>> I0209 02:12:48.511706 97296 slave.cpp:354] Slave resources:
>>> ports(*):[7150-7200]; 

Re: Question regarding docker containerizer

[Jie Yu]

Yeah, that's the command task. Mesos run all tasks using some executor. If
the user does not specify one (command task case), we will use the default
mesos executor.

On Thu, Feb 25, 2016 at 4:10 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hi Jie,
>
> I see executor_id as empty. Does this means that it is running as task and
> there is no executor for it ? Although, in the ps output, I see mesos-slave
> is spawning a mesos-docker-executor which in turn spawning the docker
> command. Here is the detail of one of the marathon task:
>
> {"id": "logs_role_kibana.3b024b6e-dbf3-11e5-bc67-56847afe9799","name": "
> kibana.role.logs","framework_id": "
> 20150904-093718-2198675372-5050-22379-","executor_id": "","slave_id":
> "a4f30c35-eee7-4110-a82f-cab5522c9b1b-S4","state": "TASK_RUNNING","
> resources": {"cpus": 0.5,"disk": 0,"mem": 1024,"ports": "[31050-31050]"},"
> statuses": [{"state": "TASK_RUNNING","timestamp": 1456427344.63661,"labels
> ": [{"key": "Docker.NetworkSettings.IPAddress","value": "172.17.0.11"}],"
> container_status": {"network_infos": [{"ip_address": "172.17.0.11","
> ip_addresses": [{"ip_address": "172.17.0.11"}]}]}}],"container": {"type":
> "DOCKER","docker": {"image": "kibana:4.3.1","network": "BRIDGE","
> port_mappings": [{"host_port": 31050,"container_port": 5601,"protocol": "
> tcp"}],"privileged": false,"parameters": [{"key": "publish-all","value": "
> true"}],"force_pull_image": true}}},
>
>
>
> On Thu, Feb 25, 2016 at 11:59 PM, Jie Yu  wrote:
>
>> You can checkout the state.json endpoint on the master
>>
>> On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri <
>> pradeep.chhetr...@gmail.com> wrote:
>>
>>> Hello Jie,
>>>
>>> Thank you for the quick reply. Sorry for asking silly question. How can
>>> i look for the taskinfo of a running container ? Can i see the TaskInfo
>>> details in the mesos master UI for a task?
>>>
>>> On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu  wrote:
>>>
 You can take a look at the TaskInfo. If the TaskInfo does not have
 ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
 executor and send the task to the executor.

 - Jie

 On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
 pradeep.chhetr...@gmail.com> wrote:

> Hello,
>
> From docker containerizer documentation (
> http://mesos.apache.org/documentation/latest/docker-containerizer/),
>
> *"Users can either launch a Docker image as a Task, or as an
> Executor."*
>
> How can i identify whether a docker container started by lets say
> marathon is running as a task or as an executor ?
>
>
> Thank you.
>
> -Pradeep
>
>
>

>>>
>>>
>>> --
>>> Pradeep Chhetri
>>>
>>> In the world of Linux, who needs Windows and Gates...
>>>
>>
>>
>
>
> --
> Pradeep Chhetri
>
> In the world of Linux, who needs Windows and Gates...
>

Re: "Chaos monkey" for mesos?

[Connor Doyle]

There's no way to kill a single task through the Mesos control
surfaces, but if you let the "chaos" framework launch tasks as a
privileged user, you can run wild.

On Thu, Feb 25, 2016 at 2:49 PM, Srikanth Viswanathan
 wrote:
> Sorry, ignore my first question. A framework can obviously kill tasks. I was
> just unsure as to whether it can kill foreign tasks, which leaves only my
> second question.
>
> On Thu, Feb 25, 2016 at 5:23 PM, Srikanth Viswanathan 
> wrote:
>>
>> Appreciate all the responses here. I'll look into `mesos-execute`.
>>
>> I was thinking about the framework idea in passing but my mesos knowledge
>> isn't up to scratch yet, so I haven't been able pursue it yet. There are
>> many questions in my mind w.r.t designing this as a framework:
>> * Doesn't a framework only receive offers from mesos and launch tasks? How
>> would a framework kill tasks? Can it also kill slaves?
>> * Is it legal in mesos for one framework to kill tasks belonging to
>> another framework?
>>
>> Thanks.
>> Srikanth
>>
>> On Thu, Feb 25, 2016 at 4:58 PM, Connor Doyle 
>> wrote:
>>>
>>> I think you could approximate that tool's behavior with some scripting
>>> plus `mesos-execute` (ships with the distribution) or by writing a
>>> really simple framework that just turns things off.
>>>
>>> On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
>>>  wrote:
>>> > Thanks. Craig and David. I'm curious about the design and use of that
>>> > tool.
>>> > Based on the video, it looks close to what I hope to do.
>>> >
>>> > A web search didn't yield any results about it, however. Does anyone
>>> > here
>>> > know more about the dcos chaos tool?
>>> >
>>> > Thanks again.
>>> > Srikanth
>>> >
>>> > On Thu, Feb 25, 2016 at 12:21 PM, craig w  wrote:
>>> >>
>>> >> here's a direct link in the video
>>> >> https://youtu.be/0I6qG9RQUnY?t=389
>>> >>
>>> >> On Thu, Feb 25, 2016 at 12:17 PM, David Wood 
>>> >> wrote:
>>> >>>
>>> >>> The DCOS tutorial mentions a chaos tool at the end of the video.  Not
>>> >>> sure if that's what your looking for, but it might be something to
>>> >>> follow up
>>> >>> on somehow.
>>> >>>
>>> >>> https://mesosphere.com/learn/
>>> >>>
>>> >>> David Wood
>>> >>> Computing Systems for Wireless Networks
>>> >>> IBM TJ Watson Research Center
>>> >>> daw...@us.ibm.com
>>> >>> 914-945-4923 (office), 914-396-6515 (mobile)
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> From:Srikanth Viswanathan 
>>> >>> To:user@mesos.apache.org
>>> >>> Date:02/25/2016 12:01 PM
>>> >>> Subject:"Chaos monkey" for mesos?
>>> >>> 
>>> >>>
>>> >>>
>>> >>>
>>> >>> Has there been any work done to develop a "chaos monkey" analogue for
>>> >>> Mesos? I have been researching on how to write one, but I wanted to
>>> >>> know if
>>> >>> there's any work already available that I can take a look at for
>>> >>> comparison,
>>> >>> and possibly re-use.
>>> >>>
>>> >>> The end goal would be something loaded into Mesos or separate from
>>> >>> Mesos
>>> >>> that randomly kills tasks. Could it be something as simple as an
>>> >>> application
>>> >>> that uses the KILL HTTP request from the scheduler API to kill tasks?
>>> >>>
>>> >>> Thanks.
>>> >>>
>>> >>> Srikanth
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> https://github.com/mindscratch
>>> >> https://www.google.com/+CraigWickesser
>>> >> https://twitter.com/mind_scratch
>>> >> https://twitter.com/craig_links
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> connor
>>
>>
>



-- 
connor

Re: Question regarding docker containerizer

[Pradeep Chhetri]

Hi Jie,

I see executor_id as empty. Does this means that it is running as task and
there is no executor for it ? Although, in the ps output, I see mesos-slave
is spawning a mesos-docker-executor which in turn spawning the docker
command. Here is the detail of one of the marathon task:

{"id": "logs_role_kibana.3b024b6e-dbf3-11e5-bc67-56847afe9799","name": "
kibana.role.logs","framework_id": "
20150904-093718-2198675372-5050-22379-","executor_id": "","slave_id": "
a4f30c35-eee7-4110-a82f-cab5522c9b1b-S4","state": "TASK_RUNNING","resources
": {"cpus": 0.5,"disk": 0,"mem": 1024,"ports": "[31050-31050]"},"statuses":
[{"state": "TASK_RUNNING","timestamp": 1456427344.63661,"labels": [{"key": "
Docker.NetworkSettings.IPAddress","value": "172.17.0.11"}],"container_status
": {"network_infos": [{"ip_address": "172.17.0.11","ip_addresses": [{"
ip_address": "172.17.0.11"}]}]}}],"container": {"type": "DOCKER","docker": {
"image": "kibana:4.3.1","network": "BRIDGE","port_mappings": [{"host_port":
31050,"container_port": 5601,"protocol": "tcp"}],"privileged": false,"
parameters": [{"key": "publish-all","value": "true"}],"force_pull_image":
true}}},



On Thu, Feb 25, 2016 at 11:59 PM, Jie Yu  wrote:

> You can checkout the state.json endpoint on the master
>
> On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri <
> pradeep.chhetr...@gmail.com> wrote:
>
>> Hello Jie,
>>
>> Thank you for the quick reply. Sorry for asking silly question. How can i
>> look for the taskinfo of a running container ? Can i see the TaskInfo
>> details in the mesos master UI for a task?
>>
>> On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu  wrote:
>>
>>> You can take a look at the TaskInfo. If the TaskInfo does not have
>>> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
>>> executor and send the task to the executor.
>>>
>>> - Jie
>>>
>>> On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
>>> pradeep.chhetr...@gmail.com> wrote:
>>>
 Hello,

 From docker containerizer documentation (
 http://mesos.apache.org/documentation/latest/docker-containerizer/),

 *"Users can either launch a Docker image as a Task, or as an Executor."*

 How can i identify whether a docker container started by lets say
 marathon is running as a task or as an executor ?


 Thank you.

 -Pradeep



>>>
>>
>>
>> --
>> Pradeep Chhetri
>>
>> In the world of Linux, who needs Windows and Gates...
>>
>
>


-- 
Pradeep Chhetri

In the world of Linux, who needs Windows and Gates...

Re: Question regarding docker containerizer

[Jie Yu]

You can checkout the state.json endpoint on the master

On Thu, Feb 25, 2016 at 3:53 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hello Jie,
>
> Thank you for the quick reply. Sorry for asking silly question. How can i
> look for the taskinfo of a running container ? Can i see the TaskInfo
> details in the mesos master UI for a task?
>
> On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu  wrote:
>
>> You can take a look at the TaskInfo. If the TaskInfo does not have
>> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
>> executor and send the task to the executor.
>>
>> - Jie
>>
>> On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
>> pradeep.chhetr...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> From docker containerizer documentation (
>>> http://mesos.apache.org/documentation/latest/docker-containerizer/),
>>>
>>> *"Users can either launch a Docker image as a Task, or as an Executor."*
>>>
>>> How can i identify whether a docker container started by lets say
>>> marathon is running as a task or as an executor ?
>>>
>>>
>>> Thank you.
>>>
>>> -Pradeep
>>>
>>>
>>>
>>
>
>
> --
> Pradeep Chhetri
>
> In the world of Linux, who needs Windows and Gates...
>

Re: Question regarding docker containerizer

[Pradeep Chhetri]

Hello Jie,

Thank you for the quick reply. Sorry for asking silly question. How can i
look for the taskinfo of a running container ? Can i see the TaskInfo
details in the mesos master UI for a task?

On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu  wrote:

> You can take a look at the TaskInfo. If the TaskInfo does not have
> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
> executor and send the task to the executor.
>
> - Jie
>
> On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
> pradeep.chhetr...@gmail.com> wrote:
>
>> Hello,
>>
>> From docker containerizer documentation (
>> http://mesos.apache.org/documentation/latest/docker-containerizer/),
>>
>> *"Users can either launch a Docker image as a Task, or as an Executor."*
>>
>> How can i identify whether a docker container started by lets say
>> marathon is running as a task or as an executor ?
>>
>>
>> Thank you.
>>
>> -Pradeep
>>
>>
>>
>


-- 
Pradeep Chhetri

In the world of Linux, who needs Windows and Gates...

Re: Question regarding docker containerizer

[Jie Yu]

You can take a look at the TaskInfo. If the TaskInfo does not have
ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the
executor and send the task to the executor.

- Jie

On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hello,
>
> From docker containerizer documentation (
> http://mesos.apache.org/documentation/latest/docker-containerizer/),
>
> *"Users can either launch a Docker image as a Task, or as an Executor."*
>
> How can i identify whether a docker container started by lets say marathon
> is running as a task or as an executor ?
>
>
> Thank you.
>
> -Pradeep
>
>
>

Question regarding docker containerizer

[Pradeep Chhetri]

Hello,

>From docker containerizer documentation (
http://mesos.apache.org/documentation/latest/docker-containerizer/),

*"Users can either launch a Docker image as a Task, or as an Executor."*

How can i identify whether a docker container started by lets say marathon
is running as a task or as an executor ?


Thank you.

-Pradeep

Re: "Chaos monkey" for mesos?

[Srikanth Viswanathan]

Sorry, ignore my first question. A framework can obviously kill tasks. I
was just unsure as to whether it can kill foreign tasks, which leaves only
my second question.

On Thu, Feb 25, 2016 at 5:23 PM, Srikanth Viswanathan 
wrote:

> Appreciate all the responses here. I'll look into `mesos-execute`.
>
> I was thinking about the framework idea in passing but my mesos knowledge
> isn't up to scratch yet, so I haven't been able pursue it yet. There are
> many questions in my mind w.r.t designing this as a framework:
> * Doesn't a framework only receive offers from mesos and launch tasks? How
> would a framework kill tasks? Can it also kill slaves?
> * Is it legal in mesos for one framework to kill tasks belonging to
> another framework?
>
> Thanks.
> Srikanth
>
> On Thu, Feb 25, 2016 at 4:58 PM, Connor Doyle 
> wrote:
>
>> I think you could approximate that tool's behavior with some scripting
>> plus `mesos-execute` (ships with the distribution) or by writing a
>> really simple framework that just turns things off.
>>
>> On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
>>  wrote:
>> > Thanks. Craig and David. I'm curious about the design and use of that
>> tool.
>> > Based on the video, it looks close to what I hope to do.
>> >
>> > A web search didn't yield any results about it, however. Does anyone
>> here
>> > know more about the dcos chaos tool?
>> >
>> > Thanks again.
>> > Srikanth
>> >
>> > On Thu, Feb 25, 2016 at 12:21 PM, craig w  wrote:
>> >>
>> >> here's a direct link in the video
>> >> https://youtu.be/0I6qG9RQUnY?t=389
>> >>
>> >> On Thu, Feb 25, 2016 at 12:17 PM, David Wood 
>> wrote:
>> >>>
>> >>> The DCOS tutorial mentions a chaos tool at the end of the video.  Not
>> >>> sure if that's what your looking for, but it might be something to
>> follow up
>> >>> on somehow.
>> >>>
>> >>> https://mesosphere.com/learn/
>> >>>
>> >>> David Wood
>> >>> Computing Systems for Wireless Networks
>> >>> IBM TJ Watson Research Center
>> >>> daw...@us.ibm.com
>> >>> 914-945-4923 (office), 914-396-6515 (mobile)
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> From:Srikanth Viswanathan 
>> >>> To:user@mesos.apache.org
>> >>> Date:02/25/2016 12:01 PM
>> >>> Subject:"Chaos monkey" for mesos?
>> >>> 
>> >>>
>> >>>
>> >>>
>> >>> Has there been any work done to develop a "chaos monkey" analogue for
>> >>> Mesos? I have been researching on how to write one, but I wanted to
>> know if
>> >>> there's any work already available that I can take a look at for
>> comparison,
>> >>> and possibly re-use.
>> >>>
>> >>> The end goal would be something loaded into Mesos or separate from
>> Mesos
>> >>> that randomly kills tasks. Could it be something as simple as an
>> application
>> >>> that uses the KILL HTTP request from the scheduler API to kill tasks?
>> >>>
>> >>> Thanks.
>> >>>
>> >>> Srikanth
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> https://github.com/mindscratch
>> >> https://www.google.com/+CraigWickesser
>> >> https://twitter.com/mind_scratch
>> >> https://twitter.com/craig_links
>> >
>> >
>>
>>
>>
>> --
>> connor
>>
>
>

Re: "Chaos monkey" for mesos?

[Srikanth Viswanathan]

Appreciate all the responses here. I'll look into `mesos-execute`.

I was thinking about the framework idea in passing but my mesos knowledge
isn't up to scratch yet, so I haven't been able pursue it yet. There are
many questions in my mind w.r.t designing this as a framework:
* Doesn't a framework only receive offers from mesos and launch tasks? How
would a framework kill tasks? Can it also kill slaves?
* Is it legal in mesos for one framework to kill tasks belonging to another
framework?

Thanks.
Srikanth

On Thu, Feb 25, 2016 at 4:58 PM, Connor Doyle  wrote:

> I think you could approximate that tool's behavior with some scripting
> plus `mesos-execute` (ships with the distribution) or by writing a
> really simple framework that just turns things off.
>
> On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
>  wrote:
> > Thanks. Craig and David. I'm curious about the design and use of that
> tool.
> > Based on the video, it looks close to what I hope to do.
> >
> > A web search didn't yield any results about it, however. Does anyone here
> > know more about the dcos chaos tool?
> >
> > Thanks again.
> > Srikanth
> >
> > On Thu, Feb 25, 2016 at 12:21 PM, craig w  wrote:
> >>
> >> here's a direct link in the video
> >> https://youtu.be/0I6qG9RQUnY?t=389
> >>
> >> On Thu, Feb 25, 2016 at 12:17 PM, David Wood  wrote:
> >>>
> >>> The DCOS tutorial mentions a chaos tool at the end of the video.  Not
> >>> sure if that's what your looking for, but it might be something to
> follow up
> >>> on somehow.
> >>>
> >>> https://mesosphere.com/learn/
> >>>
> >>> David Wood
> >>> Computing Systems for Wireless Networks
> >>> IBM TJ Watson Research Center
> >>> daw...@us.ibm.com
> >>> 914-945-4923 (office), 914-396-6515 (mobile)
> >>>
> >>>
> >>>
> >>>
> >>> From:Srikanth Viswanathan 
> >>> To:user@mesos.apache.org
> >>> Date:02/25/2016 12:01 PM
> >>> Subject:"Chaos monkey" for mesos?
> >>> 
> >>>
> >>>
> >>>
> >>> Has there been any work done to develop a "chaos monkey" analogue for
> >>> Mesos? I have been researching on how to write one, but I wanted to
> know if
> >>> there's any work already available that I can take a look at for
> comparison,
> >>> and possibly re-use.
> >>>
> >>> The end goal would be something loaded into Mesos or separate from
> Mesos
> >>> that randomly kills tasks. Could it be something as simple as an
> application
> >>> that uses the KILL HTTP request from the scheduler API to kill tasks?
> >>>
> >>> Thanks.
> >>>
> >>> Srikanth
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> https://github.com/mindscratch
> >> https://www.google.com/+CraigWickesser
> >> https://twitter.com/mind_scratch
> >> https://twitter.com/craig_links
> >
> >
>
>
>
> --
> connor
>

Re: "Chaos monkey" for mesos?

[Connor Doyle]

I think you could approximate that tool's behavior with some scripting
plus `mesos-execute` (ships with the distribution) or by writing a
really simple framework that just turns things off.

On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
 wrote:
> Thanks. Craig and David. I'm curious about the design and use of that tool.
> Based on the video, it looks close to what I hope to do.
>
> A web search didn't yield any results about it, however. Does anyone here
> know more about the dcos chaos tool?
>
> Thanks again.
> Srikanth
>
> On Thu, Feb 25, 2016 at 12:21 PM, craig w  wrote:
>>
>> here's a direct link in the video
>> https://youtu.be/0I6qG9RQUnY?t=389
>>
>> On Thu, Feb 25, 2016 at 12:17 PM, David Wood  wrote:
>>>
>>> The DCOS tutorial mentions a chaos tool at the end of the video.  Not
>>> sure if that's what your looking for, but it might be something to follow up
>>> on somehow.
>>>
>>> https://mesosphere.com/learn/
>>>
>>> David Wood
>>> Computing Systems for Wireless Networks
>>> IBM TJ Watson Research Center
>>> daw...@us.ibm.com
>>> 914-945-4923 (office), 914-396-6515 (mobile)
>>>
>>>
>>>
>>>
>>> From:Srikanth Viswanathan 
>>> To:user@mesos.apache.org
>>> Date:02/25/2016 12:01 PM
>>> Subject:"Chaos monkey" for mesos?
>>> 
>>>
>>>
>>>
>>> Has there been any work done to develop a "chaos monkey" analogue for
>>> Mesos? I have been researching on how to write one, but I wanted to know if
>>> there's any work already available that I can take a look at for comparison,
>>> and possibly re-use.
>>>
>>> The end goal would be something loaded into Mesos or separate from Mesos
>>> that randomly kills tasks. Could it be something as simple as an application
>>> that uses the KILL HTTP request from the scheduler API to kill tasks?
>>>
>>> Thanks.
>>>
>>> Srikanth
>>>
>>
>>
>>
>> --
>>
>> https://github.com/mindscratch
>> https://www.google.com/+CraigWickesser
>> https://twitter.com/mind_scratch
>> https://twitter.com/craig_links
>
>



-- 
connor

Re: "Chaos monkey" for mesos?

[Srikanth Viswanathan]

Thanks. Craig and David. I'm curious about the design and use of that tool.
Based on the video, it looks close to what I hope to do.

A web search didn't yield any results about it, however. Does anyone here
know more about the dcos chaos tool?

Thanks again.
Srikanth

On Thu, Feb 25, 2016 at 12:21 PM, craig w  wrote:

> here's a direct link in the video
> https://youtu.be/0I6qG9RQUnY?t=389
>
> On Thu, Feb 25, 2016 at 12:17 PM, David Wood  wrote:
>
>> The DCOS tutorial mentions a chaos tool at the end of the video.  Not
>> sure if that's what your looking for, but it might be something to follow
>> up on somehow.
>>
>> https://mesosphere.com/learn/
>>
>> David Wood
>> Computing Systems for Wireless Networks
>> IBM TJ Watson Research Center
>> daw...@us.ibm.com
>> 914-945-4923 (office), 914-396-6515 (mobile)
>>
>>
>>
>>
>> From:Srikanth Viswanathan 
>> To:user@mesos.apache.org
>> Date:02/25/2016 12:01 PM
>> Subject:"Chaos monkey" for mesos?
>> --
>>
>>
>>
>> Has there been any work done to develop a "*chaos monkey*
>> " analogue for
>> Mesos? I have been researching on how to write one, but I wanted to know if
>> there's any work already available that I can take a look at for
>> comparison, and possibly re-use.
>>
>> The end goal would be something loaded into Mesos or separate from Mesos
>> that randomly kills tasks. Could it be something as simple as an
>> application that uses the KILL HTTP request from the scheduler API to kill
>> tasks?
>>
>> Thanks.
>>
>> Srikanth
>>
>>
>
>
> --
>
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
> https://twitter.com/mind_scratch
> https://twitter.com/craig_links
>
>

Re: Recent UI enhancements & Managed Service Providers

[Paul Bell]

Hi Vinod,

Thank you for your reply.

I'm not sure that I can be more specific. MSPs are interested in a "view by
tenant", e.g., "show me all applications that are allotted to Tenant X".  I
suppose that the standard Mesos UI could, with properly named task IDs and
the UI's "Find" filter, accomplish part of "view by tenant". But in order
to see the resources consumed by Tenant X's tasks, you have to visit each
task individually and look at their "Resources" table (add them all up).

It'd be cool if when a filter is in effect, the Resources table was updated
to reflect only the resources consumed by the filter-selected tasks.

There's also the question of the units/meaning of Resources. Through
Marathon I give each of my Dockerized tasks .1 CPU. As I understand it,
Docker multiplies this value times 1024 which is Docker's representation of
all the cores on a host. So when I do "docker inspect " I will see
CpuShares of 102. But in the Mesos UI each of my 6 tasks shows .2 CPUs
allocated. I'm simply not sure what this means or how it's arrived at. I
suspect that an MSP will ask the same questions.

I will think about it some more, but I'd be interested to hear feedback on
these few points that I've raised.

Thanks again.

-Paul

On Thu, Feb 25, 2016 at 11:55 AM, Vinod Kone  wrote:

>
> > But an important MSP requirement is a unified view of their many
> tenants. So I am really trying to get a sense for how well the recent
> Mesos/Marathon releases address this requirement.
>
> Can you be more specific about what you mean by unified view and tenants?
> What's lacking currently?

Re: Mesos metrics -> influxdb

[vincent gromakowski]

+1 for Telegraph
Le 25 févr. 2016 19:08, "Pradeep Chhetri"  a
écrit :

> Telegraf already has a input plugin to push mesos metrics to influxdb (
> https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mesos)
>
>
> On Thu, Feb 25, 2016 at 5:32 PM, Aaron Carey  wrote:
>
>> Has anyone had a good experience recording mesos metrics into influxdb?
>>
>> I've found a couple of options, a collectd plugin which doesn't appear to
>> work with version 0.24.x and a more up to date containerised option which
>> randomly crashes regularly and doesn't appear to actually post any stats.
>>
>> Anyone have any good solutions?
>>
>>
>>
>
>
> --
> Pradeep Chhetri
>
> In the world of Linux, who needs Windows and Gates...
>

Re: Mesos metrics -> influxdb

[Pradeep Chhetri]

Telegraf already has a input plugin to push mesos metrics to influxdb (
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mesos)


On Thu, Feb 25, 2016 at 5:32 PM, Aaron Carey  wrote:

> Has anyone had a good experience recording mesos metrics into influxdb?
>
> I've found a couple of options, a collectd plugin which doesn't appear to
> work with version 0.24.x and a more up to date containerised option which
> randomly crashes regularly and doesn't appear to actually post any stats.
>
> Anyone have any good solutions?
>
>
>


-- 
Pradeep Chhetri

In the world of Linux, who needs Windows and Gates...

Re: Mesos metrics -> influxdb

[Michael Hausenblas]

Not Mesos metrics, but we've been using InfluxDB in this demo here: 
https://github.com/mesosphere/time-series-demo

Given the volume to be expected, I'd prolly be looking into something more 
scalable like KairosDB, see for example 
https://github.com/mesosphere/cassandra-kairosdb-tutorial

HTH!

Cheers,
Michael

--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/

> On 25 Feb 2016, at 17:32, Aaron Carey  wrote:
> 
> Has anyone had a good experience recording mesos metrics into influxdb?
> 
> I've found a couple of options, a collectd plugin which doesn't appear to 
> work with version 0.24.x and a more up to date containerised option which 
> randomly crashes regularly and doesn't appear to actually post any stats.
> 
> Anyone have any good solutions?

Mesos metrics -> influxdb

[Aaron Carey]

Has anyone had a good experience recording mesos metrics into influxdb?

I've found a couple of options, a collectd plugin which doesn't appear to work 
with version 0.24.x and a more up to date containerised option which randomly 
crashes regularly and doesn't appear to actually post any stats.

Anyone have any good solutions?

Re: "Chaos monkey" for mesos?

[craig w]

here's a direct link in the video
https://youtu.be/0I6qG9RQUnY?t=389

On Thu, Feb 25, 2016 at 12:17 PM, David Wood  wrote:

> The DCOS tutorial mentions a chaos tool at the end of the video.  Not sure
> if that's what your looking for, but it might be something to follow up on
> somehow.
>
> https://mesosphere.com/learn/
>
> David Wood
> Computing Systems for Wireless Networks
> IBM TJ Watson Research Center
> daw...@us.ibm.com
> 914-945-4923 (office), 914-396-6515 (mobile)
>
>
>
>
> From:Srikanth Viswanathan 
> To:user@mesos.apache.org
> Date:02/25/2016 12:01 PM
> Subject:"Chaos monkey" for mesos?
> --
>
>
>
> Has there been any work done to develop a "*chaos monkey*
> " analogue for
> Mesos? I have been researching on how to write one, but I wanted to know if
> there's any work already available that I can take a look at for
> comparison, and possibly re-use.
>
> The end goal would be something loaded into Mesos or separate from Mesos
> that randomly kills tasks. Could it be something as simple as an
> application that uses the KILL HTTP request from the scheduler API to kill
> tasks?
>
> Thanks.
>
> Srikanth
>
>


-- 

https://github.com/mindscratch
https://www.google.com/+CraigWickesser
https://twitter.com/mind_scratch
https://twitter.com/craig_links

Re: "Chaos monkey" for mesos?

[David Wood]

The DCOS tutorial mentions a chaos tool at the end of the video.  Not sure 
if that's what your looking for, but it might be something to follow up on 
somehow.

https://mesosphere.com/learn/

David Wood 
Computing Systems for Wireless Networks
IBM TJ Watson Research Center
daw...@us.ibm.com
914-945-4923 (office), 914-396-6515 (mobile)




From:   Srikanth Viswanathan 
To: user@mesos.apache.org
Date:   02/25/2016 12:01 PM
Subject:"Chaos monkey" for mesos?



Has there been any work done to develop a "chaos monkey" analogue for 
Mesos? I have been researching on how to write one, but I wanted to know 
if there's any work already available that I can take a look at for 
comparison, and possibly re-use.

The end goal would be something loaded into Mesos or separate from Mesos 
that randomly kills tasks. Could it be something as simple as an 
application that uses the KILL HTTP request from the scheduler API to kill 
tasks?

Thanks.

Srikanth

"Chaos monkey" for mesos?

[Srikanth Viswanathan]

Has there been any work done to develop a "chaos monkey
" analogue for
Mesos? I have been researching on how to write one, but I wanted to know if
there's any work already available that I can take a look at for
comparison, and possibly re-use.

The end goal would be something loaded into Mesos or separate from Mesos
that randomly kills tasks. Could it be something as simple as an
application that uses the KILL HTTP request from the scheduler API to kill
tasks?

Thanks.

Srikanth

Re: Recent UI enhancements & Managed Service Providers

[Vinod Kone]

> But an important MSP requirement is a unified view of their many tenants. So 
> I am really trying to get a sense for how well the recent Mesos/Marathon 
> releases address this requirement.

Can you be more specific about what you mean by unified view and tenants? 
What's lacking currently?

Recent UI enhancements & Managed Service Providers

[Paul Bell]

Hi All,

I am running older versions of Mesos & Marathon (0.23.0 and 0.10.0).

Over the course of the last several months I think I've seen several items
on this list about UI enhancements. Perhaps they were enhancements to the
data consumed by the Mesos & Marathon UIs. I've had very little time to dig
deeply into it.

So...I am wondering if someone can either point me to any discussions of
such enhancements or summarize them here.

There is a specific use case behind this request. The Mesos architecture
seems to be a real sweet spot for an MSP. But an important MSP requirement
is a unified view of their many tenants. So I am really trying to get a
sense for how well the recent Mesos/Marathon releases address this
requirement.

Thank you.

-Paul