x
/
vmware-nsx
Code Issues Proposed changes

Use AFTER_INIT in lieu of AFTER_CREATE 

AFTER_CREATE should be dedicated to data store operations.

Change-Id: I2b17ee41a9bfc020099c4f2f251afa32bb48b290
Depends-on: I9e717e9e4ae4414067477712ac02870fe1041e70
This commit is contained in:
Armando Migliaccio 2016-06-28 11:44:40 -07:00
parent 8b1a76a6d2
commit a3184b1128
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
vmware_nsx/nsxlib/v3/cluster.py
View File

@ -258,7 +258,7 @@ class ClusteredAPI(object):
# reinitialize upon fork for api workers to ensure each
# process has its own keepalive loops + state
registry.subscribe(
_init_cluster, resources.PROCESS, events.AFTER_CREATE)
_init_cluster, resources.PROCESS, events.AFTER_INIT)
def _init_endpoints(self, providers,
min_conns_per_pool, max_conns_per_pool):

2
vmware_nsx/plugins/nsx_v/plugin.py
View File

@ -172,7 +172,7 @@ class NsxVPluginV2(addr_pair_db.AllowedAddressPairsMixin,
self.init_is_complete = False
registry.subscribe(self.init_complete,
resources.PROCESS,
events.AFTER_CREATE)
events.AFTER_INIT)
self.metadata_proxy_handler = None
config.validate_nsxv_config_options()
neutron_extensions.append_api_extensions_path(