Comment 4 for bug 1618724

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/367599
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=a8e0aa35eb5e8bb66f00d5d437b6f1345f6e2a75
Submitter: Jenkins
Branch: master

commit a8e0aa35eb5e8bb66f00d5d437b6f1345f6e2a75
Author: Sripriya <email address hidden>
Date: Thu Sep 8 12:24:59 2016 -0700

    Derive infra driver using VIM type

    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