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] <[email protected]> On Behalf Of Chandra Sent: Thursday, December 27, 2018 2:28 AM To: [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 (#14729): https://lists.onap.org/g/onap-discuss/message/14729 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]] -=-=-=-=-=-=-=-=-=-=-=-
