Hi, there are many changes. All of them are mentioned in the following requirement https://jira.onap.org/browse/REQ-182 and are detailed in here https://jira.onap.org/browse/INT-1184. Both VNF-API and GR-API are supported now. Changes you may be impacted are:
* During the distribution of helm package the definition is created base on vf-module model identifiers: invariant-id (r definition) and uuid (rb version) * Profile creation can be skipped, "default" empty profile is always created automatically * For instantiation, user params section was replaced with SDNC parameters section in the preload phase and sdnc parameters can be used to pass the override params for helm instantiation. In SDNC params there is required "k8s-rb-profile-name" param to specify name of the profile you want to use. RB definition identifiers are related with previously mentioned vf-module identifiers and they are generated by SO in time the of instantiation. Details can be found in here https://github.com/onap/multicloud-k8s/blob/master/src/k8splugin/api/brokerhandler.go Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Poland, Advanced Network Solutions Agency Mob.: +48 519 310 854 Orange Polska, Obrzeżna 7, 02-691 Warsaw www.orange.pl<http://www.orange.pl/> From: HARDY Thierry TGI/OLN [mailto:[email protected]] Sent: Tuesday, May 5, 2020 9:09 AM To: [email protected]; Rajewski Łukasz - Hurt Subject: #multicloud #k8s Evolution for Frankfurt Dear all, I'm looking for a description of the different evolutions that have been implemented for future Frankfurt release concerning the instantiation of CNFs (K8s containers functions). I implemented a CNF use case (using onap-tests tool and included in xtesting-onap open source project for daily tests on ONAP) on elalto release that allows to instantiate a nginx helm package but trying to run it on master release (future Frankfurt), I faced errors linked to the fact that rbdefintion and profile objects are certainly no longer used while sending the SO request with VNF API. Last updates may require to use GR_API instead of VNF_API .... All information regarding backward compatibility with elalto release implementation will be welcome. Thank you in advance for your help Regards Thierry -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20947): https://lists.onap.org/g/onap-discuss/message/20947 Mute This Topic: https://lists.onap.org/mt/73992997/21656 Mute #multicloud: https://lists.onap.org/mk?hashtag=multicloud&subid=2740164 Mute #k8s: https://lists.onap.org/mk?hashtag=k8s&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
