vIMS service design and creation video (voice is in Chinese)
CSARs used by CMCC
ZTE: resource-ZteEpcMmeVf-csar_fix.csar | ZteEpcSpgwVf-csar.csar
Huawei: Huawei_vMME.csar | Huawei_vSPGW_fixed.csar | Huawei_vHSS.csar | Huawei_vPCRF_aligned_fixed.csar | vSBC_aligned.csar
Nokia: vCSCF_v3.0.csar
If there is an update on SDC TOSCA node type, you need to delete Cassandra database file from SDC VM, and download docker images
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
ubuntu@vm03-sdc:~$ sudo rm -rf /data/CS/ ubuntu@vm03-sdc:~$ sudo bash -x /opt/sdc_vm_init.sh |
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Inside container sbc-BE, change log configuration root@405b964017de:/var/lib/jetty# vi /var/lib/jetty/config/catalog-be/logback.xml Enable enable-all-log to true <property scope="context" name="enable-all-log" value="true" /> Change log level from INFO to DEBUG in all places |
Code Block | ||||
---|---|---|---|---|
| ||||
On SDC VM, run: ubuntu@vm03-sdc:~$ tail -f /data/logs/BE/SDC/SDC-BE/debug.log |
SDC image includes VoLTE CSARs which will be used to do self-test when SDC starts. The test result is in an HTML report
Code Block | ||||
---|---|---|---|---|
| ||||
root@vm03-sdc:~# ls -l /data/logs/sdc-sanity/ExtentReport/SDC*.html -rw-r--r-- 1 root root 31929 Oct 29 13:51 /data/logs/sdc-sanity/ExtentReport/SDC_CI_Extent_Report.html |
SDC ignores zip file in vendor CSAR Artifacts/ directory. See
Jira | ||||||
---|---|---|---|---|---|---|
|
The workaround is after VSP onboarding and import, go to Deployment Artifacts on VNF design GUI, and click Add Artifact then choose Type as Other. From there you should be able to upload your zip file. The zip file will be stored under Artifacts/Other directory of SDC output TOSCA CSAR file.
VoLTE Service Design
Step 1. Create New VSP by upload vendor VNF CSAR.
Step 2. Create VNF by importing VSP, and submit for testing