Files

Yasufumi Ogawa ddf28104a3 Update version of cirros image to 0.5.2

We've been using old cirros-0.4.0 for long time, and don't need to fix
the version of cirros to 0.4.0. This patch is update to the latest
0.5.2.

Most of the changes in this patch is replacing `image`, `hash` and
`version` in TOSCA definition files. The rest of them are:

* Replace images. First one is only an actual image, and rest of them
  are empty text files which is a trick for reducing total size in
  tacker repo. So, text files are not replaced, but renamed simply.
  * tacker/tests/etc/samples/etsi/nfv/common/Files/images/cirros-0.5.2-x86_64-disk.img
  * samples/vnf_packages/Files/images/cirros-0.5.2-x86_64-disk.img
  * tacker/tests/etc/samples/etsi/nfv/test_csar_utils_data/sample_vnfpkg_no_meta_single_vnfd/Files/images/cirros-0.5.2-x86_64-disk.img
  * tacker/tests/etc/samples/sample_vnf_package_csar_in_meta_and_manifest/Files/images/cirros-0.5.2-x86_64-disk.img

* Update functional tests verifying images. A refactor of defining
  package size is included.

* Update devstack script, and helper scripts under `contrib` dir.

* Update API references and documents describing usage of the image.

Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>

Implements: blueprint update-cirros-052
Change-Id: I081b791dc986ab10f4845784b3e19dbb626e3cac

2021-08-30 21:31:12 +09:00

3.4 KiB

Raw Blame History

Orchestrating VNFs with attached Volumes

To support persistent volumes to VNF, the TOSCA NFV profile supports a new type of nodes. Tacker has now the feature of parsing of those new nodes and creation of cinder volumes which are attached to the VDUs.

Prerequisites

To have persistent volume support to VDUs, we must enable cinder service in addition to the other services needed by Tacker.

VNFD Changes

There are two steps to have volume attached to VDU:

Create volume or Use an existing volume.
Attach Volume to VDU

Create Volume

To add volume, we need to add the below node to the VNFD:

VB1:
  type: tosca.nodes.BlockStorage.Tacker
  properties:
    size: 1 GB

Use Existing Volume

We can also attach an already created/existing volume with VNF by providing volume_id in input.

topology_template:
  inputs:
    my_vol:
      description: volume id
      type: string

  VB1:
    type: tosca.nodes.BlockStorage.Tacker
    properties:
      volume_id: my_vol

Attach volume to VDU

Next attach the created volume to VDU as below:

CB1:
  type: tosca.nodes.BlockStorageAttachment
  properties:
    location: /dev/vdb
    requirements:
      - virtualBinding:
          node: VDU1
      - virtualAttachment:
          node: VB1

With these additions, the new VNFD looks like below:

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0
description: Demo example

metadata:
  template_name: sample-tosca-vnfd

topology_template:
  node_templates:
    VDU1:
      type: tosca.nodes.nfv.VDU.Tacker
      capabilities:
        nfv_compute:
          properties:
            num_cpus: 1
            mem_size: 512 MB
            disk_size: 1 GB
      properties:
        image: cirros-0.5.2-x86_64-disk
        availability_zone: nova
        mgmt_driver: noop
        config: |
          param0: key1
          param1: key2

    CP1:
      type: tosca.nodes.nfv.CP.Tacker
      properties:
        management: true
        order: 0
        anti_spoofing_protection: false
      requirements:
        - virtualLink:
            node: VL1
        - virtualBinding:
            node: VDU1

    VB1:
      type: tosca.nodes.BlockStorage.Tacker
      properties:
        size: 1 GB

    CB1:
      type: tosca.nodes.BlockStorageAttachment
      properties:
        location: /dev/vdb
      requirements:
        - virtualBinding:
            node: VDU1
        - virtualAttachment:
            node: VB1

    VL1:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: net_mgmt
        vendor: Tacker

3.4 KiB Raw Blame History