Dublin
Access Shared Cassandra DB
Code Block | ||
---|---|---|
| ||
root@staging-rancher:~/oom/kubernetes/sdc/charts/sdc-cs# kubectl -n onap exec -it dev-cassandra-cassandra-0 bash root@dev-cassandra-cassandra-0:/# cqlsh -u cassandra -p cassandra Connected to cassandra at 127.0.0.1:9042. [cqlsh 5.0.1 | Cassandra 2.2.14 | CQL spec 3.3.1 | Native protocol v4] Use HELP for help. cassandra@cqlsh> describe keyspaces; sdccomponent system_auth sdcaudit system_distributed sdctitan workflow system dox system_traces sdcrepository zusammen_dox aaigraph sdcartifact zusammen_workflow |
Casablanca
Credential for basic authentication when access with REST
Username | Password |
aai | Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U |
vid | Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U |
vIMS service design and creation video (voice is in Chinese)
CSAR used by CMCC for R2
Huawei: vSBC_update_v03.csar
Nokia:cscf.v2.csar/etsi_config.json
CSARs used by CMCC for R1
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 healthcheck url http://10.12.5.154:30205/sdc2/rest/healthCheck, sample output is:
Code Block | ||||
---|---|---|---|---|
| ||||
{ "sdcVersion": "1.3.6", "siteMode": "unknown", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "DE", "healthCheckStatus": "DOWN", "description": "U-EB cluster is not available" }, { "healthCheckComponent": "CASSANDRA", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "ON_BOARDING", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK", "componentsInfo": [ { "healthCheckComponent": "ZU", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.6", "description": "OK" }, { "healthCheckComponent": "CAS", "healthCheckStatus": "UP", "version": "2.1.17", "description": "OK" } ] }, { "healthCheckComponent": "DCAE", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK" }, { "healthCheckComponent": "TOSCA_LAB", "healthCheckStatus": "UP", "version": "1.3.0", "description": "OK" } ] } ] } |
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