Hi Ramya, Thanks for the clarifications. We have followed steps as you mentioned and looks like multiple actions are getting supported. We have not uploaded the reference file in CDT but right actions in the capability artefact.
Please refer to steps we followed- 1. Uploaded PD and template for configure action ( No reference file uploaded) - Capability reference contains the Configure action 2. Uploaded PD and template for ConfigScaleout Action (No reference file uploaded) - Capability reference contains the Configscaleout+Configure action as well. 3. Configure Action request for VNF sent via dmaap- The action was successful. 4. ConfigScaleOut request for VNF sent via dmaap - The action was successful. Regards Chandrashekhar Thakare From: BALAJI, RAMYA P [mailto:[email protected]] Sent: 31 December 2018 20:34 To: Chandrashekhar Thakare <[email protected]>; [email protected] Subject: RE: [appc] Multiple Actions against single VNF type Here are my answers in black: Also if we create the single capability artefact, I hope we can still have different template and parameter definition against each Action? - Yes- The capability artifact is generated from the reference artifact while the others are uploaded or created from the design tool by the user. I could not understand this design implementation though.. Consider that first we have created the artefact for Configure and then few days later we need to support Restart, how do we handle this situation? - If the reference file first created did not have the Restart, you can add the missing action to the reference file. The reference file should ideally contain all the actions we would like to perform on that vnf type. If you are using the configuration design tool, you can use the same to add the missing action, by selecting the same vnf type and bringing up the existing reference artifact and modifying it in the tool itself. Do we need to update the Configure reference template as well including both action as Restart and Configure? Do we have any generic implementation to support all actions? Assuming you are still referring to the reference file here -If you are using the design tool, all actions are presented in the drop down of the configuration design tool and may be selected from there itself Attaching a sample file with just the reference data JSON element for a reference file that contains more than one action block. Thanks. Ramya From: Chandrashekhar Thakare <[email protected]<mailto:[email protected]>> Sent: Monday, December 31, 2018 12:48 AM To: BALAJI, RAMYA P <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [appc] Multiple Actions against single VNF type Hi Ramya, Thanks for your response. Yes we are creating the separate reference file against each action. Could you please share reference file containing multiple actions? Also if we create the single capability artefact, I hope we can still have different template and parameter definition against each Action? I could not understand this design implementation though.. Consider that first we have created the artefact for Configure and then few days later we need to support Restart, how do we handle this situation? Do we need to update the Configure reference template as well including both action as Restart and Configure? Do we have any generic implementation to support all actions? Regards Chandrashekhar Thakare From: BALAJI, RAMYA P [mailto:[email protected]] Sent: 31 December 2018 07:06 To: [email protected]<mailto:[email protected]>; Chandrashekhar Thakare <[email protected]<mailto:[email protected]>> Subject: RE: [appc] Multiple Actions against single VNF type Hi: The 450 message is obtained when the capability artifact does not support the action that is currently being attempted. The reference artifact for the vnf type is supposed to contain all permitted actions for that vnf type. Are you generating separate reference artifacts for each of these actions ? If so, please correct that. Ensure you create the reference artifact with BOTH Configure and ConfigScaleOut actions for the VNF type. That will generate a capability artifact containing both actions and allow you to execute those flows. Thanks Ramya From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Chandra Sent: Thursday, December 27, 2018 2:28 AM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [appc] Multiple Actions against single VNF type Hi , We were running the test for Configure and ConfigScaleout against single VNF. It seems that at any point of time APPC can support the latest action against which the CDT templates are uploaded. For e.g. If we load CDT templates against the Configure and Configuscaleout against same VNF then, the configure request will be rejected with error as 450:Request not supported.. The query which is implemented looks like below, which always finds the max from ASDC artifacts and fetches the latest updated templates . The SQL query is - select max(internal_version) as maxInternalVersion, artifact_name as artifactName from ASDC_ARTIFACTS where artifact_name in (select artifact_name from ASDC_REFERENCE where vnf_type= $vnf_type and file_category = 'capability' ); Few queries regarding this behaviour are - 1. Any specific architectural/design constraints by which we have restricted such progression? 2. Can we change this behaviour to make sure we should be able to utilize the different action against the same VNF by checking the latest templates against the specific action? Regards Chandrashekhar Thakare ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=j1C9otY4aHrwL_sO8xu4Qg&m=Vf529CQOSMvV_mi7x0nPbbyVmEn1ISTrAVQebVZrKv4&s=sU4zzBd1wiCfxK9waK1tvVOUR0H0-EUgV-KzcBQ9X0g&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=j1C9otY4aHrwL_sO8xu4Qg&m=Vf529CQOSMvV_mi7x0nPbbyVmEn1ISTrAVQebVZrKv4&s=0YJRh9A7HzObbEtVKwh2NzJy_iGYS10k1jIrbzo7kiI&e=> internally within TechMahindra. ============================================================================================================================ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14741): https://lists.onap.org/g/onap-discuss/message/14741 Mute This Topic: https://lists.onap.org/mt/28863462/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
