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

List:       mesos-user
Subject:    ipv6 resource or attributes
From:       Charles Allen <charles.allen () metamarkets ! com>
Date:       2015-11-19 20:58:46
Message-ID: CAM4_YMarYakk1=kWjx1e3UX1QrxAZNrTmjPCM=+P6cYJcn04MQ () mail ! gmail ! com
[Download RAW message or body]

From just a cursory glance at
http://mesos.apache.org/documentation/attributes-resources/ I'm curious if
ipv6 addresses can be used as a text resource or attribute.

I have not experimented with this at all yet, and was wondering if such use
cases are intended to be supported.

It seems that it might be possible to use an ipv4 address as the text of a
set attribute

some_key:{127.0.0.1}

but not as a distinct text resource or attribute

some_key:127.0.0.1

as that would collide with the float specification in a strict
interpretation

But it seems that an ipv6 address like 2001:db8::ff00:42:8329  wold cause
problems both as a distinct text attirbute/resource

some_key:2001:db8::ff00:42:8329

or as part of a set

some_key:{2001:db8::ff00:42:8329}

because `:' is not listed among the allowed characters for text.

Is this correct reading of the attributes and resources specification?

Thanks,
Charles Allen

[Attachment #3 (text/html)]

<div dir="ltr">From just a cursory glance at  <a \
href="http://mesos.apache.org/documentation/attributes-resources/">http://mesos.apache.org/documentation/attributes-resources/</a> \
I&#39;m curious if ipv6 addresses can be used as a text resource or \
attribute.<div><br></div><div>I have not experimented with this at all yet, and was \
wondering if such use cases are intended to be supported.</div><div><br></div><div>It \
seems that it might be possible to use an ipv4 address as the text of a set \
attribute</div><div><br></div><div>some_key:{127.0.0.1}</div><div><br></div><div>but \
not as a distinct text resource or \
attribute</div><div><br></div><div>some_key:127.0.0.1</div><div><br></div><div>as \
that would collide with the float specification in a strict \
interpretation</div><div><br></div><div>But it seems that an ipv6 address like \
2001:db8::ff00:42:8329   wold cause problems both as a distinct text \
attirbute/resource</div><div><br></div><div>some_key:2001:db8::ff00:42:8329</div><div><br></div><div>or \
as part of a set</div><div><br></div><div>some_key:{2001:db8::ff00:42:8329}</div><div><br></div><div>because \
`:&#39; is not listed among the allowed characters for text.  \
</div><div><br></div><div>Is this correct reading of the attributes and resources \
specification?</div><div><br></div><div>Thanks,</div><div>Charles \
Allen</div><div><br></div><div><br></div></div>



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