tacker scaling+monitoring feature has issues in monitoring

Bug #1624149 reported by Santosh
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Govindaiah M

Bug Description

When a vnf with following template is created, 2 VDUs are created as apart of 1 vnf (default_instances=2).
Monitoring is enabled and hence, monitoring framework will try to ping host ["u'a', u'b'] where a and b are ips assigned to vdus. This will fail with unknown host error and vnf will be re spawned (failure: respawn) . This will happen continuously creating an unstable vnf.

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: sample-tosca-vnfd-scaling

  template_name: sample-tosca-vnfd-scaling

      type: tosca.nodes.nfv.VDU.Tacker
            num_cpus: 1
            mem_size: 512 MB
            disk_size: 1 GB
        image: cirros-0.3.4-x86_64-uec
        mgmt_driver: noop
        availability_zone: nova
          name: ping
            failure: respawn
            count: 3
            interval: 10
            monitoring_delay: 45
            timeout: 2
        config_drive: true

      type: tosca.nodes.nfv.CP.Tacker
        management: true
        anti_spoofing_protection: false
        - virtualLink:
            node: VL1
        - virtualBinding:
            node: VDU1

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

    - SP1:
        type: tosca.policy.tacker.Scaling
          increment: 1
          cooldown: 60
          min_instances: 1
          max_instances: 8
          default_instances: 2
          targets: [VDU1]

Changed in tacker:
assignee: nobody → Govindaiah M (govindaiah-m)
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.