[jira] [Commented] (MESOS-4427) Ensure ip_address in state.json (from NetworkInfo) is valid
[
https://issues.apache.org/jira/browse/MESOS-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15181855#comment-15181855
]
Martin Evgeniev commented on MESOS-4427:
Oops sry...
> Ensure ip_address in state.json (from NetworkInfo) is valid
> ---
>
> Key: MESOS-4427
> URL: https://issues.apache.org/jira/browse/MESOS-4427
> Project: Mesos
> Issue Type: Bug
>Reporter: Sargun Dhillon
>Priority: Critical
> Labels: mesosphere
> Fix For: 0.28.0
>
>
> We have seen a master state.json where the state.json has a field that looks
> similar to:
> ---REDACTED---
> {code:json}
> {
> "container": {
> "docker": {
> "force_pull_image": false,
> "image": "REDACTED",
> "network": "HOST",
> "privileged": false
> },
> "type": "DOCKER"
> },
> "executor_id": "",
> "framework_id": "9f0e50ea-54b0-44e3-a451-c69e0c1a58fb-",
> "id": "ping-as-a-service.c2d1c17a-be22-11e5-b053-002590e56e25",
> "name": "ping-as-a-service",
> "resources": {
> "cpus": 0.1,
> "disk": 0,
> "mem": 64,
> "ports": "[7907-7907]"
> },
> "slave_id": "9f0e50ea-54b0-44e3-a451-c69e0c1a58fb-S76043",
> "state": "TASK_RUNNING",
> "statuses": [
> {
> "container_status": {
> "network_infos": [
> {
> "ip_address": "",
> "ip_addresses": [
> {
> "ip_address": ""
> }
> ]
> }
> ]
> },
> "labels": [
> {
> "key": "Docker.NetworkSettings.IPAddress",
> "value": ""
> }
> ],
> "state": "TASK_RUNNING",
> "timestamp": 1453149270.95511
> }
> ]
> }
> {code}
> ---REDACTED---
> This is invalid, and it mesos-core should filter it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4427) Ensure ip_address in state.json (from NetworkInfo) is valid
[
https://issues.apache.org/jira/browse/MESOS-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15180581#comment-15180581
]
Martin Evgeniev commented on MESOS-4427:
Are you using Docker libnetwork plugin with custom network (overlay etc..)?
> Ensure ip_address in state.json (from NetworkInfo) is valid
> ---
>
> Key: MESOS-4427
> URL: https://issues.apache.org/jira/browse/MESOS-4427
> Project: Mesos
> Issue Type: Bug
>Reporter: Sargun Dhillon
>Priority: Critical
> Labels: mesosphere
>
> We have seen a master state.json where the state.json has a field that looks
> similar to:
> ---REDACTED---
> {code:json}
> {
> "container": {
> "docker": {
> "force_pull_image": false,
> "image": "REDACTED",
> "network": "HOST",
> "privileged": false
> },
> "type": "DOCKER"
> },
> "executor_id": "",
> "framework_id": "9f0e50ea-54b0-44e3-a451-c69e0c1a58fb-",
> "id": "ping-as-a-service.c2d1c17a-be22-11e5-b053-002590e56e25",
> "name": "ping-as-a-service",
> "resources": {
> "cpus": 0.1,
> "disk": 0,
> "mem": 64,
> "ports": "[7907-7907]"
> },
> "slave_id": "9f0e50ea-54b0-44e3-a451-c69e0c1a58fb-S76043",
> "state": "TASK_RUNNING",
> "statuses": [
> {
> "container_status": {
> "network_infos": [
> {
> "ip_address": "",
> "ip_addresses": [
> {
> "ip_address": ""
> }
> ]
> }
> ]
> },
> "labels": [
> {
> "key": "Docker.NetworkSettings.IPAddress",
> "value": ""
> }
> ],
> "state": "TASK_RUNNING",
> "timestamp": 1453149270.95511
> }
> ]
> }
> {code}
> ---REDACTED---
> This is invalid, and it mesos-core should filter it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4446) Set Docker labels based on TaskInfo labels.
[ https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141647#comment-15141647 ] Martin Evgeniev commented on MESOS-4446: Many thanks for the info [~gyliu]. I'll open a JIRA to request some docs.. > Set Docker labels based on TaskInfo labels. > --- > > Key: MESOS-4446 > URL: https://issues.apache.org/jira/browse/MESOS-4446 > Project: Mesos > Issue Type: Story > Components: docker >Reporter: Gennady Feldman >Assignee: Abhishek Dasgupta > > So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be > possible to pass those onto the docker container? > This would really help with doing "docker inspect" on the mesos-slave nodes > as well as allow us to better collect docker metrics about the > tasks/containers that are currently running on the slave. > docker supports labels out of the box. See here: > https://docs.docker.com/engine/userguide/labels-custom-metadata/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4446) Set Docker labels based on TaskInfo labels.
[
https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137627#comment-15137627
]
Martin Evgeniev commented on MESOS-4446:
HI guys,
First of all i want to ask if any of this Mesos labels stuff is documented? I
cant find anything :(
The second think i want to know if there is anyway to make Mesos expose any
custom value form the docker inspect command. The main problem is that right
now it only looks for the container IPAddr by this
"Docker.NetworkSettings.IPAddress" and the docker overlay network this changes
a bit and if you have custom network the json looks like this:
{code}
"NetworkSettings": {
"Bridge": "",
"SandboxID":
"102744ffe3f07313c0c00e5880fe825d0791a04cecd88d807f8bb40b9cc043ef",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"443/tcp": null,
"80/tcp": null
},
"SandboxKey": "/var/run/docker/netns/102744ffe3f0",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"services": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID":
"197fbe7b6c76141ba9284311476b363998c852b4718d548226fb9fe32a6ec0ce",
"EndpointID":
"d475269e2fcdc75760ae06365c45bfa63246b0e76c5761b607c215be441674a4",
"Gateway": "",
"IPAddress": "192.168.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:c0:a8:00:03"
}
}
}
{code}
And basiclly in Mesos state.json the IPAddr value is empty. This value is what
we use to register the service in Consul..
Am I doing something the wrong way? Is there anyway to rewrite this behavior?
Feel free to ask me if you need mor information.
Thanks
> Set Docker labels based on TaskInfo labels.
> ---
>
> Key: MESOS-4446
> URL: https://issues.apache.org/jira/browse/MESOS-4446
> Project: Mesos
> Issue Type: Story
> Components: docker
>Reporter: Gennady Feldman
>Assignee: Abhishek Dasgupta
>
> So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be
> possible to pass those onto the docker container?
> This would really help with doing "docker inspect" on the mesos-slave nodes
> as well as allow us to better collect docker metrics about the
> tasks/containers that are currently running on the slave.
> docker supports labels out of the box. See here:
> https://docs.docker.com/engine/userguide/labels-custom-metadata/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-4446) Set Docker labels based on TaskInfo labels.
[
https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137627#comment-15137627
]
Martin Evgeniev edited comment on MESOS-4446 at 2/8/16 8:29 PM:
HI guys,
First of all i want to ask if any of this Mesos labels stuff is documented? I
cant find anything :(
The second thing i want to know if there is anyway to make Mesos expose any
custom value form the docker inspect command. The main problem is that right
now it only looks for the container IPAddr by this
"Docker.NetworkSettings.IPAddress" and the docker overlay network this changes
a bit and if you have custom network the json looks like this:
{code}
"NetworkSettings": {
"Bridge": "",
"SandboxID":
"102744ffe3f07313c0c00e5880fe825d0791a04cecd88d807f8bb40b9cc043ef",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"443/tcp": null,
"80/tcp": null
},
"SandboxKey": "/var/run/docker/netns/102744ffe3f0",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"services": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID":
"197fbe7b6c76141ba9284311476b363998c852b4718d548226fb9fe32a6ec0ce",
"EndpointID":
"d475269e2fcdc75760ae06365c45bfa63246b0e76c5761b607c215be441674a4",
"Gateway": "",
"IPAddress": "192.168.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:c0:a8:00:03"
}
}
}
{code}
And basiclly in Mesos state.json the IPAddr value is empty. This value is what
we use to register the service in Consul..
Am I doing something the wrong way? Is there anyway to rewrite this behavior?
Feel free to ask me if you need mor information.
Thanks
was (Author: suizman):
HI guys,
First of all i want to ask if any of this Mesos labels stuff is documented? I
cant find anything :(
The second think i want to know if there is anyway to make Mesos expose any
custom value form the docker inspect command. The main problem is that right
now it only looks for the container IPAddr by this
"Docker.NetworkSettings.IPAddress" and the docker overlay network this changes
a bit and if you have custom network the json looks like this:
{code}
"NetworkSettings": {
"Bridge": "",
"SandboxID":
"102744ffe3f07313c0c00e5880fe825d0791a04cecd88d807f8bb40b9cc043ef",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"443/tcp": null,
"80/tcp": null
},
"SandboxKey": "/var/run/docker/netns/102744ffe3f0",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"services": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID":
"197fbe7b6c76141ba9284311476b363998c852b4718d548226fb9fe32a6ec0ce",
"EndpointID":
"d475269e2fcdc75760ae06365c45bfa63246b0e76c5761b607c215be441674a4",
"Gateway": "",
"IPAddress": "192.168.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:c0:a8:00:03"
}
}
}
{code}
And basiclly in Mesos state.json the IPAddr value is empty. This value is what
we use to register the service in Consul..
Am I doing something the wrong way? Is there anyway to rewrite this behavior?
Feel free to ask me if you need mor information.
Thanks
> Set Docker labels based on TaskInfo labels.
> ---
>
> Key: MESOS-4446
> URL: https://issues.apache.org/jira/browse/MESOS-4446
> Project: Mesos
> Issue
