You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


If there is an update on SDC TOSCA node type, you need to delete Cassandra database file from SDC VM, and download docker images

SDC Normative TOSCA Node Type Update 
ubuntu@vm03-sdc:~$ sudo rm -rf /data/CS/
ubuntu@vm03-sdc:~$ sudo bash -x /opt/sdc_vm_init.sh
SDC Enable Debug Log 
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
SDC-BE Log Files
On SDC VM, run:
ubuntu@vm03-sdc:~$ tail -f /data/logs/BE/SDC/SDC-BE/debug.log
CSAR Onboarding SDC Self Test Report 
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  SDC-483 - Getting issue details... STATUS  

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. 



  • No labels