{"push_id":1376863971,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"c266bb2ff0740276eb9b33c09a837697631d01be","before":"70df3d75e7a0a473961361c3818f59a136f44eae","commits":[{"sha":"c807cd6c8a8f766cd1296b38eab21f296dfbd412","author":{"name":"Li Ma","email":"2c58dd48909a01566b2f85840ed9ff3759a05c6d@gmail.com"},"message":"Start network connections after neutron forks workers\n\nInitially, neutron-server will fork multiple workers for API and RPC.\nIt loads mechanism drivers and all the resources after mechanism\ndriver initialization will be forked including network connections.\nIt will make the external SDN system unstable, bring races and finally\nmake it unstable or dead.\n\nThe PluginWorker and process notification has been proposed in neutron\nin liberty [1]. It provides several ways to deal with the multi-process\nand multi-thread in mechansim driver.\n\nIn dragonflow, we need to make sure the northbound database connection\nis initialized after the neutron workers are forked. So we use process\nnotification here to initialize the connections.\n\n[1] https://review.openstack.org/#/c/189391/\n\nChange-Id: I076a831630e0f99f2ebbb39764aa43859b064bca","distinct":true,"url":"https://api.github.com/repos/openstack/dragonflow/commits/c807cd6c8a8f766cd1296b38eab21f296dfbd412"},{"sha":"c266bb2ff0740276eb9b33c09a837697631d01be","author":{"name":"Jenkins","email":"61eb39d4445155efb6068840385577c11776cd20@review.openstack.org"},"message":"Merge \"Start network connections after neutron forks workers\"","distinct":true,"url":"https://api.github.com/repos/openstack/dragonflow/commits/c266bb2ff0740276eb9b33c09a837697631d01be"}]}
{"actor":{"display_login":"openstack-gerrit"}}