a8e0aa35eb
Currently, infra driver name is derived from VNFD API attribute infra_driver during VNFD template onboarding. This limits the catalog to be used for a specific VIM type. VNFD template should be generic enough to be deployed on any VIM and should not contain infra driver specific information. This patch is a follow on for infra driver deprecation [1] infra_driver value in VNFD request is silently ignored. The infra driver derivation is now handled during VNF deployment workflow based on user provied vim_id and corresponding vim_type. [1] https://review.openstack.org/#/c/363455/ Partial-bug: #1618724 Partially Implements: blueprint infra-driver-refactor Change-Id: I44cfd18ab75e32872776952560d1f716e99301d5 |
||
---|---|---|
.. | ||
agent | ||
api | ||
cmd | ||
common | ||
db | ||
extensions | ||
hacking | ||
nfvo | ||
plugins | ||
services | ||
tests | ||
vm | ||
vnfm | ||
__init__.py | ||
_i18n.py | ||
auth.py | ||
context.py | ||
hooks.py | ||
manager.py | ||
policy.py | ||
service.py | ||
version.py | ||
wsgi.py |