Hi All,

As discussed in the summit, "vdu_autoheal" monitoring policy action implementation should be as per ETSI standard HealVnfRequest interface [1] (refer comment given on patch https://review.openstack.org/#/c/612595/9  )
Started working on the same but have some quires  so needs some feedback and inputs.

As per the ETSI doc [1] the data model for HealVnfRequest contains two request parameters (cause anddditionalParams)
(Check section: 5.5.2.9 Type: HealVnfReques from [1])

The Request Payload for HealVnfRequest (ETSI data structure: HealVnfRequest) should be the dictionary as mentioned in [2] 
(Check section: Healing VNFs Using ETSI API from [2])

But the “addtionalParams”  parameter should be part of "HealVnfOpConfig” and that expects two parameters (cause and parameter) as mentioned in [3]
(Check section: 7.1.5.6 HealVnfOpConfig information element from [3])

So accordingly I have designed the request data for vdu_autoheal monitoring policy action as below:

Heal Request Data for monitoring:

{ 
"cause": "",
  "additionalParams":  [ 

{“parameter”: <Resource name given in the vnfd template for eg. VDU1>,  “cause”: [<Reason for failure of the resource>]}, 

{“parameter”: <Resource name given in the vnfd template for eg. CP1>,  “cause”: [<Reason for failure of the resource]}
 ]
}

Please let me know the opinion about the same.

Also "HealVnfOpConfig” having type as “tosca.datatypes.nfv.VnfHealOperationConfiguration”  as per the ONAP [4] and the schema for that is as mentioned below:

Schema:

tosca.datatypes.nfv.VnfHealOperationConfiguration

    derived_from: tosca.datatypes.Root
    properties: 
        #parameters:
            #modeled as part of the operation parameter list
        causes:
            type: list
            entry_schema:
                 type: string




so does that mean we can accepts this request in tosca template for HealVnfRequest?

[1]: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.05.01_60/gs_NFV-SOL003v020501p.pdf  
[2]: https://www.cisco.com/c/en/us/td/docs/net_mgmt/elastic_services_controller/4-3/user/guide/Cisco-Elastic-Services-Controller-User-Guide-4-3managing_VNF_lifecycle_using_etsi_API.pdf    
[3]: https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/02.01.01_60/gs_NFV-IFA011v020101p.pdf  
[4]: https://onap.readthedocs.io/en/beijing/submodules/modeling/modelspec.git/docs/ONAP%20Model%20Spec/dm/DataTypes.html