Open Stack

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)?

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.

-Bob

On 2/29/16 4:38 PM, Kevin Benton wrote:
> You're correct. Right now there is no way via the HTTP API to find 
> which segments a port is bound to.
> This is something we can certainly consider adding, but it will need 
> an RFE so it wouldn't land until Newton at the earliest.
>
> 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.
>
> On Mon, Feb 29, 2016 at 6:48 AM, Ihar Hrachyshka <ihrachys at redhat.com 
> <mailto:ihrachys at redhat.com>> wrote:
>
>     Fixed neutron tag in the subject.
>
>     Marc <marc at koderer.com <mailto:marc at koderer.com>> wrote:
>
>         Hi Neutron team,
>
>         I am currently working on a feature for hierarchical port
>         binding support in
>         Manila [1] [2]. Just to give some context: In the current
>         implementation Manila
>         creates a neutron port but let it unbound (state DOWN).
>         Therefore Manila uses
>         the port create only retrieve an IP address and segmentation
>         ID (some drivers
>         only support VLAN here).
>
>         My idea is to change this behavior and do an actual port
>         binding action so that
>         the configuration of VLAN isn’t a manual job any longer. And
>         that multi-segment
>         and HPB is supported on the long-run.
>
>         My current issue is: How can Manila retrieve the segment
>         information for a
>         bound port? Manila only is interested in the last (bottom)
>         segmentation ID
>         since I assume the storage is connected to a ToR switch.
>
>         Database-wise it’s possible to query it using
>         ml2_port_binding_levels table.
>         But AFAIK there is no API to query this. The only information
>         that is exposed
>         are all segments of a network. But this is not sufficient to
>         identify which
>         segments actually used for a port binding.
>
>         Regards
>         Marc
>         SAP SE
>
>         [1]:
>         https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support
>         [2]: https://review.openstack.org/#/c/277731/
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160229/fde22973/attachment.html>