<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 19, 2015 at 10:24 PM, Assaf Muller <span dir="ltr"><<a href="mailto:amuller@redhat.com" target="_blank">amuller@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Aug 19, 2015 at 2:34 PM, Gal Sagie <span dir="ltr"><<a href="mailto:gal.sagie@gmail.com" target="_blank">gal.sagie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello all,
<div><br></div><div>Recently i have came across two use cases that having "binding" information, or metadata</div><div>for networks can be useful. (similar to the port binding profile for that matter)</div><div><br></div><div>For example:</div><div><br></div><div>1) In project Kuryr we want to have a binding information which maps the Neutron network</div><div> to docker network (And we might want to do it prior to the docker network being created,</div><div> that is assign a network that is ready to be attached) so this field also needs to be editable</div><div> (just like the port binding profile)</div><div><br></div><div>2) For multi site OpenStack (multi cloud) use cases we might want to share information which</div><div> binds logically same network that is created at each OpenStack cloud site (and hence the ID's</div><div> are different).</div><div> (Something like this could be useful for project Tricircle for example)</div><div><br></div><div>3) Use cases for multi controllers environments? (each controller manage different networks?)</div><div><br></div><div>I believe adding such optional field to the network API is really low risk due to its being optional</div><div>and i believe other use cases can be found to leverage it.</div></div></blockquote><div><br></div></span><div>I wonder if we should just add a key/pair tuples "tags" or "metadata" generic field instead. There's</div><div>been similar requests floating about that could also use a place to dump their data in.</div></div></div></div></blockquote><div><br><div>I think something similar was proposed as part of QoS but it was decided against. I personally think<br></div>that having metadata for the entities (networks and ports) makes a lot of sense.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div dir="ltr"><div><br></div><div>Feel free to share ideas/comments.</div><div><br></div><div>If there are no strong objections to it, i will add an RFE/Spec to add this ability.</div><div><br></div><div>Thanks</div><span><font color="#888888"><div>Gal.</div><div><br></div><div><br></div></font></span></div>
<br></span>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>