For the moment Manila does following: - creates Neutron port, consider "reserves" network info. - then calls its own share driver that supports network handling and that driver does binding on its backend. - Neutron does not have info about real usage of a port and its info.
So, it is correct to say that "bind" operation is performed by each Manila share driver on its own way. Manila common code (not share-driver-specific) does only "reservation" for now. Would be good to have common possibility to write "bind" info to Neutron that was performed by Manila. It is very undesired to write separate Neutron driver for each Manila backend that supports networking. Valeriy On Tue, Mar 1, 2016 at 7:22 AM, Kevin Benton <ke...@benton.pub> wrote: > >This seems gross and backwards. It makes sense as a short term hack but > given that we have time to design this correctly I'd prefer to get this > information in a more straighforward way. > > Well it depends on what is happening here. If Manilla is wiring up a > specific VLAN for a port, that makes it part of the port binding process, > in which case it should be an ML2 driver. Can you provide some more details > about what Manilla is doing with this info? > > On Mon, Feb 29, 2016 at 5:29 PM, Ben Swartzlander <b...@swartzlander.org> > wrote: > >> On 02/29/2016 04: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. >>> >> >> I believe Newton is the target for this work. This is feature freeze week >> after all. >> >> 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. >>> >> >> This seems gross and backwards. It makes sense as a short term hack but >> given that we have time to design this correctly I'd prefer to get this >> information in a more straighforward way. >> >> -Ben Swartzlander >> >> >> On Mon, Feb 29, 2016 at 6:48 AM, Ihar Hrachyshka <ihrac...@redhat.com >>> <mailto:ihrac...@redhat.com>> wrote: >>> >>> Fixed neutron tag in the subject. >>> >>> Marc <m...@koderer.com <mailto:m...@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-requ...@lists.openstack.org?subject:unsubscribe >>> < >>> http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe >>> < >>> http://openstack-dev-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kind Regards Valeriy Ponomaryov www.mirantis.com vponomar...@mirantis.com
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
