<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Is Manila actually connecting (i.e. binding) something it controls
to a Neutron port, similar to how a Neutron L3 or DHCP agent
connects a network namespace to a port? Or does it just need to know
the details about a port bound for a VM (or a service)? <br>
<br>
If the former, it should probably be using something similar to
Neutron's interface drivers (or maybe Nova's new VIF library) so it
can work with arbitrary core plugins or ML2 mechanism drivers, and
any corresponding L2 agent. If it absolutely requires a VLAN on a
node's physical network, then Kevin's idea of a Manila-specific
mechanism driver that does the binding (without involving an L2
agent) may be the way to go.<br>
<br>
-Bob<br>
<br>
<div class="moz-cite-prefix">On 2/29/16 4:38 PM, Kevin Benton wrote:<br>
</div>
<blockquote
cite="mid:CAO_F6JPw4pZMSkzZP_j=V+hnbUhY2=6zOu+NFgFaVMSOuKCD5Q@mail.gmail.com"
type="cite">
<div dir="ltr">You're correct. Right now there is no way via the
HTTP API to find which segments a port is bound to.
<div>This is something we can certainly consider adding, but it
will need an RFE so it wouldn't land until Newton at the
earliest.</div>
<div><br>
</div>
<div>Have you considered writing an ML2 driver that just
notifies Manilla of the port's segment info? All of this
information is available to ML2 drivers in the PortContext
object that is passed to them.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Feb 29, 2016 at 6:48 AM, Ihar
Hrachyshka <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Fixed
neutron tag in the subject.<br>
<br>
Marc <<a moz-do-not-send="true"
href="mailto:marc@koderer.com" target="_blank">marc@koderer.com</a>>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
Hi Neutron team,<br>
<br>
I am currently working on a feature for hierarchical
port binding support in<br>
Manila [1] [2]. Just to give some context: In the
current implementation Manila<br>
creates a neutron port but let it unbound (state
DOWN). Therefore Manila uses<br>
the port create only retrieve an IP address and
segmentation ID (some drivers<br>
only support VLAN here).<br>
<br>
My idea is to change this behavior and do an actual
port binding action so that<br>
the configuration of VLAN isn’t a manual job any
longer. And that multi-segment<br>
and HPB is supported on the long-run.<br>
<br>
My current issue is: How can Manila retrieve the
segment information for a<br>
bound port? Manila only is interested in the last
(bottom) segmentation ID<br>
since I assume the storage is connected to a ToR
switch.<br>
<br>
Database-wise it’s possible to query it using
ml2_port_binding_levels table.<br>
But AFAIK there is no API to query this. The only
information that is exposed<br>
are all segments of a network. But this is not
sufficient to identify which<br>
segments actually used for a port binding.<br>
<br>
Regards<br>
Marc<br>
SAP SE<br>
<br>
[1]: <a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support"
rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support</a><br>
[2]: <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/277731/"
rel="noreferrer" target="_blank">https://review.openstack.org/#/c/277731/</a><br>
</div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a moz-do-not-send="true"
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 moz-do-not-send="true"
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>
</blockquote>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
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 moz-do-not-send="true"
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>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>