Re: [openstack-dev] [cinder] [nova] [scheduler] Nova node name passed to Cinder
Hello Vishvananda, > Initialize connection passes that data to cinder in the call. The connector > dictionary in the call should contain the info from nova: > > https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L1051 Ah yes, I see. Thank you very much! Regards, Phil -- : Ing. Philipp Marek : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com : DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ 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
Re: [openstack-dev] [cinder] [nova] [scheduler] Nova node name passed to Cinder
On Jan 26, 2015, at 10:16 PM, Philipp Marek wrote: > Hello Vish, > >> Nova passes ip, iqn, and hostname into initialize_connection. That should >> give you the info you need. > thank you, but that is on the _Nova_ side. > > I need to know that on the Cinder node already: > >>> For that the cinder volume driver needs to know at > ... >>> time which Nova host will be used to access the data. > > but it's not passed in there: > >>> The arguments passed to this functions already include an >>> "attached_host" value, sadly it's currently given as "None"... > > > Therefore my question where/when that value is calculated… Initialize connection passes that data to cinder in the call. The connector dictionary in the call should contain the info from nova: https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L1051 > > > Regards, > > Phil > > -- > : Ing. Philipp Marek > : LINBIT | Your Way to High Availability > : DRBD/HA support and consulting http://www.linbit.com : > > DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. > > __ > 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
Re: [openstack-dev] [cinder] [nova] [scheduler] Nova node name passed to Cinder
Hello Vish, > Nova passes ip, iqn, and hostname into initialize_connection. That should > give you the info you need. thank you, but that is on the _Nova_ side. I need to know that on the Cinder node already: > > For that the cinder volume driver needs to know at ... > > time which Nova host will be used to access the data. but it's not passed in there: > > The arguments passed to this functions already include an > > "attached_host" value, sadly it's currently given as "None"... Therefore my question where/when that value is calculated... Regards, Phil -- : Ing. Philipp Marek : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com : DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ 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
Re: [openstack-dev] [cinder] [nova] [scheduler] Nova node name passed to Cinder
Nova passes ip, iqn, and hostname into initialize_connection. That should give you the info you need. Vish On Jan 26, 2015, at 3:21 AM, Philipp Marek wrote: > Hello everybody, > > I'm currently working on providing DRBD as a block storage protocol. > For that the cinder volume driver needs to know at > >initialize_connection, >create_export, and >ensure_export > > time which Nova host will be used to access the data. > > I'd like to ask for a bit of help; can somebody tell me which part of > the code decides that, and where the data flows? > Is it already known at that time which node will receive the VM? > > The arguments passed to this functions already include an > "attached_host" value, sadly it's currently given as "None"... > > > Thank you for any tips, ideas, and pointers into the code - and, > of course, even more so for full-blown patches on review.openstack.org ;) > > > Regards, > > Phil > > > -- > : Ing. Philipp Marek > : LINBIT | Your Way to High Availability > : DRBD/HA support and consulting http://www.linbit.com : > > DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. > > __ > 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
