Monday, 2015-12-21

*** yinwei has joined #openstack-smaug01:34
yinweihello03:35
yinweiguys, one question about how to persist the plugin_id03:35
yinweiactually, it's liuan who raised this question during protection-service implementation03:37
yinweiAs Eran explained in review board, admin will configure the Provider, which is a bundle of plugins each for one resource-type. So API level will persist the Provider instance with a mapping: resource-type->plugin_id03:39
yinweiHowever, it's ProtectionService who actually use plugin. As we discussed before, plugin-manager actually start and load plugins in ProtectionService.  The question is ,how does ProtectionService know which plugin-id will map to which plugin instance?03:41
yinweiOr, plugin-id is actually a plugin-name configured by user in conf file, each name is corresponding to one plugin implementation (python class).  Both API service and ProtectionService read the conf, and thus understanding the mapping between plugin-name to plugin implementation (python class).03:43
*** avishay has joined #openstack-smaug06:11
openstackgerritchenying proposed openstack/smaug: basic API service: Create the base DAL into the DB  https://review.openstack.org/25931106:28
*** gampel has joined #openstack-smaug06:51
*** CrayZee has joined #openstack-smaug07:10
openstackgerritchenying proposed openstack/smaug: basic API service: Create the base DAL into the DB  https://review.openstack.org/25931107:24
*** zhongjun has joined #openstack-smaug08:28
openstackgerritzengchen proposed openstack/smaug: Authentication fails by keystonemiddleware  https://review.openstack.org/25876808:33
*** gampel1 has joined #openstack-smaug08:43
*** gampel has quit IRC08:45
*** gampel has joined #openstack-smaug08:46
*** gampel1 has quit IRC08:47
openstackgerritchenying proposed openstack/smaug: basic schedule service: Service class for binaries running on hosts  https://review.openstack.org/25990108:52
openstackgerritchenying proposed openstack/smaug: basic schedule service: Service class for binaries running on hosts  https://review.openstack.org/25990109:13
chenying_IMO, mapping is configured in conf. We can configure like this : CinderVolumePlugin = smaug.service.plugin.cindervolumeplugin  like driver class configured in the cinder.conf09:25
chenying_plugin-id  is the id of cindervolumeplugin class09:27
zengyingzheDoes this how cinder implement now?09:28
chenying_only bank_plugin_id is the instance of a  bank_plugin with different datasource url09:29
chenying_cinder driver only have a driver_name, need be configured in cinder.conf.  It do not have have a driver class id.09:36
yinweiishereYes, another option is to configure multiple plugins as multiple sections in conf: plugin_name=volume_backup;plugin_type=volume; plugin_class=smaug.service.plugin.cinder.volume.backup;09:38
chenying_and then using self.driver = importutils.import_object(09:38
chenying_volume_driver  Import a class and return an instance of it.09:38
yinweiisherefor each plugin, there will be one section which includes those 3 fields09:38
*** openstack has joined #openstack-smaug15:35
*** gampel1 has quit IRC16:49
*** zhonghua has quit IRC16:51
*** zhonghua-lee has joined #openstack-smaug16:55
*** gampel has joined #openstack-smaug18:24
openstackgerritMerged openstack/smaug: Authentication fails by keystonemiddleware  https://review.openstack.org/25876818:33
*** avishay has quit IRC20:19

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!