Hi Srini, For E2E slicing use case, the core NSSMF shall be using most of the existing ONAP features for instantiation and configuration of NFs.
For CNF day 2 configurations, it is proposed that the NSSMF shall be invoking SO ModifyConfig workflow. So the flow would be NSSMF->SO->CDS->Multi-Cloud->k8s plugin (configure API). The CNFs planned are dummy ones. So as such configmap or CR based configuration anything could be possible. But the thought was to use most basic mechanism for now. Thanks, Milind From: Addepalli, Srinivasa R <[email protected]> Sent: Monday, June 15, 2020 7:18 PM To: [email protected]; Milind Jalwadi <[email protected]>; Sood, Ritu <[email protected]>; Multanen, Eric W <[email protected]>; [email protected] Subject: RE: [k8splugin] configurationAPI usage for NSSMF implementation Hi Milind, On NSSMF: Is it that NSSMF takes care of creating consolidated config-map before it pushes it to the NF via K8s plugin? I am guessing that many CNFs do support RESTful API for incremental configuration (add/delete/modify a resource). To make it truly cloud native, some CNFs do expose these configurations as 'Custom Resources' in K8s. K8splugin Day2 configuration is also designed to support the CR based configuration. Is it that CNF you are thinking supports only configMap? Is it the reason why NSSMF consolidates all incremental configuration as one configMap? Thanks Srini From: Addepalli, Srinivasa R Sent: Friday, June 12, 2020 7:53 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Sood, Ritu <[email protected]<mailto:[email protected]>>; Multanen, Eric W <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [k8splugin] configurationAPI usage for NSSMF implementation Hi Milind, We did not try this out. But, we don't' see any reason why configmap can't be uploaded via Day2 configuration API of K8s plugin. You just need to upload the configmap template using template API. And then send the data using the values API. Thanks Srini From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Milind Jalwadi via lists.onap.org Sent: Thursday, June 11, 2020 10:21 AM To: Sood, Ritu <[email protected]<mailto:[email protected]>>; Multanen, Eric W <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [k8splugin] configurationAPI usage for NSSMF implementation Hi Ritu / k8s plug-in team, As part of the E2E slicing use case in Guilin release, we are planning to develop core NSSMF functionality. In this regards, for scenarios where NSSMF would need to initiate the configuration changes on the instantiated CNFs, we were planning to use the configuration APIs of k8s plug-in (version v1). For the use case scenario, we are thinking of using ConfigMap for uploading the new configuration (ex. day 2 configurations). Could you please confirm if the configuration API could be used to push the new ConfigMap for pods? We haven't used configuration API before and hence the query. Many Thanks, Milind ============================================================================================================================ 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 externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ Caution: Please do not click links or open attachments unless you recognize the sender and know the content is safe. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21343): https://lists.onap.org/g/onap-discuss/message/21343 Mute This Topic: https://lists.onap.org/mt/74823199/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
