Tacker: ETSI MANO NFV Orchestrator / VNF Manager. See https://wiki.openstack.org/wiki/Tacker
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

6.3 KiB

Deploying OpenWRT as VNF

Once tacker is installed successfully, follow the steps given below to get started with deploying OpenWRT as VNF.

  1. Ensure Glance already contains OpenWRT image.

    Normally, Tacker tries to add OpenWRT image to Glance while installing via devstack. By running openstack image list to check OpenWRT image if exists.

    $ openstack image list
    | ID                                   | Name                     | Status |
    | 8cc2aaa8-5218-49e7-9a57-ddb97dc68d98 | OpenWRT                  | active |
    | 32f875b0-9e24-4971-b82d-84d6ec620136 | cirros-0.4.0-x86_64-disk | active |
    | ab0abeb8-f73c-467b-9743-b17083c02093 | cirros-0.5.1-x86_64-disk | active |

    If not, you can get the customized image of OpenWRT 15.05.1 in your tacker repository, or download the image from. Unzip the file by using the command below:

    $ cd /path/to/tacker/samples/images/
    $ gunzip openwrt-x86-kvm_guest-combined-ext4.img.gz

    Then upload the image into Glance by using command below:

    $ openstack image create OpenWRT --disk-format qcow2 \
          --container-format bare \
          --file /path/to/openwrt-x86-kvm_guest-combined-ext4.img \
  2. Configure OpenWRT

    The example below shows how to create the OpenWRT-based Firewall VNF. First, we have a yaml template which contains the configuration of OpenWRT as shown below:



    We also have another configuration yaml template with some firewall rules of OpenWRT.



    In this template file, we specify the mgmt_driver: openwrt which means this VNFD is managed by openwrt driver. This driver can inject firewall rules which defined in VNFD into OpenWRT instance by using SSH protocol. We can run cat /etc/config/firewall to confirm the firewall rules if inject succeed.

  3. Create a sample vnfd

    $ openstack vnf descriptor create \
        --vnfd-file tosca-vnfd-openwrt.yaml <VNFD_NAME>
  4. Create a VNF

    $ openstack vnf create --vnfd-name <VNFD_NAME> \
          --config-file tosca-config-openwrt-firewall.yaml <NAME>
  5. Check the status

    $ openstack vnf list
    $ openstack vnf show <VNF_ID>

    We can replace the firewall rules configuration file with tosca-config-openwrt-vrouter.yaml, tosca-config-openwrt-dnsmasq.yaml , or tosca-config-openwrt-qos.yaml to deploy the router, DHCP, DNS, or QoS VNFs. The openwrt VNFM management driver will do the same way to inject the desired service rules into the OpenWRT instance. You can also do the same to check if the rules are injected successful: cat /etc/config/network to check vrouter, cat /etc/config/dhcp to check DHCP and DNS, and cat /etc/config/qos to check the QoS rules.

  6. Notes

    1. OpenWRT user and password

      The user account is 'root' and password is '', which means there is no password for root account.

    2. Procedure to customize the OpenWRT image

      The OpenWRT is modified based on KVM OpenWRT 15.05.1 to be suitable for Tacker. The procedure is following as below:

      $ cd ~
      $ wget https://archive.openwrt.org/chaos_calmer/15.05.1/x86/kvm_guest/openwrt-15.05.1-x86-kvm_guest-combined-ext4.img.gz \
              -O openwrt-x86-kvm_guest-combined-ext4.img.gz
      $ gunzip openwrt-x86-kvm_guest-combined-ext4.img.gz
      $ mkdir -p imgroot
      $ sudo kpartx -av openwrt-x86-kvm_guest-combined-ext4.img
      # Replace the loopXp2 with the result of above command, e.g., loop0p2
      $ sudo mount -o loop /dev/mapper/loopXp2 imgroot
      $ sudo chroot imgroot /bin/ash
      # Set password of this image to blank, type follow command and then enter two times
      $ passwd
      # Set DHCP for the network of OpenWRT so that the VNF can be ping
      $ uci set network.lan.proto=dhcp; uci commit
      $ exit
      $ sudo umount imgroot
      $ sudo kpartx -dv openwrt-x86-kvm_guest-combined-ext4.img