Wrong instruction of deployment OpenWRT VNF

[Nguyen Hai]

The current instruction guide of deployment OpenWRT-based VNF is using the TOSCA-based template that contains the basic configuration of Firewall. But, the existing OpenWRT driver does not support yet. It can only support the injecting OpenWRT configuration from a separate .yaml file.

For example, when we create a VNFD "tosca-vnfd-openwrt.yaml", this can only work with the config file (or param file) such as "tosca-config-openwrt-vrouter.yaml", "tosca-config-openwrt-with-firewall.yaml". The template named "tosca-vnfd-openwrt-with-firewall-rules.yaml" in "deploy_openwrt.rst" does not work.

[Nguyen Hai (nguyentrihai93-deactivatedaccount)]

Review: https://review.openstack.org/#/c/543413/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/543413
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=da9e0e4b9b0ba9dbea1c985b0ae169e5a910120c
Submitter: Zuul
Branch: master

commit da9e0e4b9b0ba9dbea1c985b0ae169e5a910120c
Author: Nguyen Hai <email address hidden>
Date: Mon Feb 12 19:18:14 2018 +0900

    Modify OpenWRT image & rewrite deployment OpenWRT instruction

    This patch adds the customized OpenWRT image that enables DHCP making
    the VNF can be ping. Therefore, the continuously respawning of VNF
    can be fixed.

    This patch also rewrites the instruction of deploying VNF
    based on OpenWRT.

    Change-Id: Ieb4d98fe374676bad101a6c2965354a9b19ea0a2
    Closes-Bug: #1557008
    Closes-Bug: #1749243
    Closes-Bug: #1709557