...
Note:- No much difference in both the ways when once comes to the simulator implementation, basically, the 5GC instances (5GC Instantiation and Modify Config flow through CDS ) don't contain the slice profile information in the CBA package and some config information about DCAE. In the second approach, you had an updated CBA with slice-profile information and required DCAE config data for simulators in the second way of deployment.
Deployment Steps for Option1:
- Download this Helm Package for core simulators deployments instead of helm charts provided in this 5GC Instantiation and Modify Config flow through CDS instantiation. (Updated the helm charts with simulator docker images: lttscoresimulators/amf_simulators:v1.1, lttscoresimulators/smf_simulators:v1.1, lttscoresimulators/upf_simulators:v1.1) . After downloading Helm charts, update your DCAE-VES Collector IP, Port & required granularity_period under values.yaml in all the helm charts of AMF, SMF & UPF.
...
- Use the same CBA package provided in the 5GC instantiation flow and continue the design and deployment steps for core-simulators instantiations as CNF's.
- AMF/SMF/UPF Simulators will start simulating the PM Data for all the active S-NSSAI's and sends the fileReady notification to VES-Collector based on the granularity period.
- PM files of respective simulators are saved under the SFTP user directory. (i.e. /data/admin/pm_directory/ )
Deployment Steps for Option2:
- TBD: Here with the above helm charts, we will provide you a modified CBA package which has the slice profile information also as part of it, based on that slice profile information simulators will generate the PM data.
...