Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

Hi Li Ma, I think its a good idea. I suggest for first stage, pass the CONF as optional parameter in addition to the db_ip and db_port. This way you will have minimum code changes at first patch. If we see its working ok, we can later remove db_ip and db_port and adjust the other drivers in

Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

good suggestion！ At 2015-12-25 19:07:10, "Li Ma" wrote: >Hi all, currently, we only support db_ip and db_port in the >configuration file. Some DB SDK supports clustering, like Zookeeper. >You can specify a list of nodes when client application starts to >connect to

Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

My intention is to pass db-host-list (maybe it is defined in the conf file) to db backend drivers. I find that there's '**args' available [1], but it seems not working due to [2]. I suggest to use a simpler method to allow user-defined configuration that is removing db_ip and db_port parameters

[openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

Hi all, currently, we only support db_ip and db_port in the configuration file. Some DB SDK supports clustering, like Zookeeper. You can specify a list of nodes when client application starts to connect to servers. I'd like to implement this feature, specifying ['ip1:port', 'ip2:port',

Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

Hi Li Ma, This approach makes sense to me, i was also thinking about the ability for the user to specify additional arguments and parameters to the DB driver. Feel free to register a bug and work on that. Thanks Gal. On Fri, Dec 25, 2015 at 1:07 PM, Li Ma wrote: > Hi