<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0"></p>
<div>Hi All,<br>
<br>
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
<a href="https://review.openstack.org/#/c/612595/9" class="OWAAutoLink" id="LPlnk99356" previewremoved="true">
https://review.openstack.org/#/c/612595/9</a> )<br>
Started working on the same but have some quires so needs some feedback and inputs.<br>
<br>
As per the ETSI doc [1] the data model for HealVnfRequest contains two request parameters (cause anddditionalParams)<br>
(Check section: 5.5.2.9 Type: HealVnfReques from [1])<br>
<br>
The Request Payload for HealVnfRequest (ETSI data structure: HealVnfRequest) should be the dictionary as mentioned in [2] <br>
(Check section: Healing VNFs Using ETSI API from [2])<br>
<br>
But the “addtionalParams” parameter should be part of "HealVnfOpConfig” and that expects two parameters (cause and parameter) as mentioned in [3]<br>
(Check section: 7.1.5.6 HealVnfOpConfig information element from [3])<br>
<br>
So accordingly I have designed the request data for vdu_autoheal monitoring policy action as below:<br>
<br>
Heal Request Data for monitoring:<br>
<br>
{ <br>
"cause": "",<br>
"additionalParams": [ </div>
<div>{“parameter”: <Resource name given in the vnfd template for eg. VDU1>, “cause”: [<Reason for failure of the resource>]}, </div>
<div>{“parameter”: <Resource name given in the vnfd template for eg. CP1>, “cause”: [<Reason for failure of the resource]}<br>
]<br>
}<br>
<br>
Please let me know the opinion about the same.<br>
<br>
Also "HealVnfOpConfig” having type as “tosca.datatypes.nfv.VnfHealOperationConfiguration” as per the ONAP [4] and the schema for that is as mentioned below:<br>
<br>
Schema:<br>
<br>
tosca.datatypes.nfv.VnfHealOperationConfiguration<br>
<br>
derived_from: tosca.datatypes.Root<br>
properties: <br>
#parameters:<br>
#modeled as part of the operation parameter list<br>
causes:<br>
type: list<br>
entry_schema:<br>
type: string<br>
<br>
<br>
<br>
<br>
so does that mean we can accepts this request in tosca template for HealVnfRequest?<br>
<br>
[1]: <a href="https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.05.01_60/gs_NFV-SOL003v020501p.pdf" class="OWAAutoLink" id="LPlnk582897" previewremoved="true">
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.05.01_60/gs_NFV-SOL003v020501p.pdf</a> <br>
[2]: <a href="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" class="OWAAutoLink" id="LPlnk88928" previewremoved="true">
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</a> <br>
[3]: <a href="https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/02.01.01_60/gs_NFV-IFA011v020101p.pdf" class="OWAAutoLink" id="LPlnk647614" previewremoved="true">
https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/02.01.01_60/gs_NFV-IFA011v020101p.pdf</a> <br>
[4]: <a href="https://onap.readthedocs.io/en/beijing/submodules/modeling/modelspec.git/docs/ONAP%20Model%20Spec/dm/DataTypes.html" class="OWAAutoLink" id="LPlnk112105" previewremoved="true">
https://onap.readthedocs.io/en/beijing/submodules/modeling/modelspec.git/docs/ONAP%20Model%20Spec/dm/DataTypes.html</a> </div>
<br>
<br>
<p></p>
<p style="margin-top:0;margin-bottom:0">Regards,</p>
<p style="margin-top:0;margin-bottom:0">Bhagyashri Shewale</p>
</div>
Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly
to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.
</body>
</html>