commit | e01f4a5f5e4258e5b02593bda5cb0c5ec87b1899 | [log] [tgz] |
---|---|---|
author | Remigiusz Janeczek <remigiusz.janeczek@nokia.com> | Wed Feb 24 09:15:48 2021 +0100 |
committer | Christophe Closset <christophe.closset@intl.att.com> | Thu Feb 25 13:30:20 2021 +0000 |
tree | 6cd6ffc6df7f126178ceb0f5e64ec90e21b267cf | |
parent | 5c50d66c0ddcc3de44ed897151ea8431550af07b [diff] |
Add UI/Rest sanity checks for helm package onboarding Issue-ID: SDC-3185 Signed-off-by: Remigiusz Janeczek <remigiusz.janeczek@nokia.com> Change-Id: I17f19987c76647b448a409fda6b4a85e058d9612
SDC is the ONAP visual modeling and design tool. It creates internal metadata that describes assets used by all ONAP components, both at design time and run time.
The SDC manages the content of a catalog and logical assemblies of selected catalog items to completely define how and when VNFs are realized in a target environment. A complete virtual assembly of specific catalog items, together with selected workflows and instance configuration data, completely defines how the deployment, activation, and life-cycle management of VNFs are accomplished.
SDC manages four levels of assets:
The key output of SDC is a set of models containing descriptions of asset capabilities and instructions to manage them. These models are stored in the SDC Master Reference Catalog for the entire enterprise to use.
There are four major components of SDC:
Note that if you're working on Windows, it's important to enable long paths for your machine; otherwise git won't be able to handle some files.
In order to do so just add this section to your global git.config file under the [core]
key:
longpaths = true
SDC is built from several projects while the parent "sdc" contains the main pom.xml for all of them:
In order to build all the projects, as mentioned in the onap wiki https://wiki.onap.org/display/DW/Setting+Up+Your+Development+Environment, the settings.xml (https://git.onap.org/oparent/plain/settings.xml) from the oparent project must be installed in your ~/.m2 folder and referenced by your IDE. Once maven is set up properly, go to sdc project and run the command: mvn clean install
By default, the "all" maven profile will be executed but others exist:
DOCKER_HOST
and value: tcp://<ip_address>:2375
in order to build and upload local dockers to a local environment.More flags to use in the build process are:
After having started SDC with the command mvn clean install -P start-sdc
, you can access it by accessing this URL: http://<ip_address>:8285/login
As ONAP AAF is not present, the url provided uses the 8285 simulator ports, just click on the user you want to use for accessing SDC (i.e. Carlos Santana) For more information regarding using the webseal_simulator please refer to the following guide: SDC Simulator
The following table shows the SDC containers found after a maven "start-sdc":
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 968a8168e412 onap/sdc-backend-init:latest "/bin/sh -c /home/${…" 9 minutes ago Exited (0) 54 seconds ago sdc-backend-init-1 621c0fda1b0f onap/sdc-backend-all-plugins:latest "sh -c ${JETTY_BASE}…" 9 minutes ago Up 9 minutes 0.0.0.0:4000->4000/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp sdc-backend-all-plugins-1 d823078776d8 onap/sdc-onboard-backend:latest "sh -c ${JETTY_BASE}…" 9 minutes ago Up 9 minutes 0.0.0.0:4001->4001/tcp, 0.0.0.0:8081->8081/tcp, 0.0.0.0:8445->8445/tcp, 8080/tcp sdc-onboard-backend-1 4729b0b7f0fe onap/sdc-simulator:latest "sh -c ${JETTY_BASE}…" 9 minutes ago Up 9 minutes 0.0.0.0:8285->8080/tcp, 0.0.0.0:8286->8443/tcp sdc-simulator-1 583e0d7fa300 onap/sdc-onboard-cassandra-init:latest "/home/sdc/startup.sh" 9 minutes ago Exited (0) 9 minutes ago sdc-onboard-cassandra-init-1 92085524f19f onap/sdc-cassandra-init:latest "/home/sdc/startup.sh" 10 minutes ago Exited (0) 9 minutes ago sdc-cassandra-init-1 c6e90dd7ddaf selenium/standalone-firefox:2.53.1 "/opt/bin/entry_poin…" 10 minutes ago Up 10 minutes 0.0.0.0:4444->4444/tcp standalone-firefox-1 e02139c0379b onap/sdc-frontend:latest "sh -c ${JETTY_BASE}…" 10 minutes ago Up 10 minutes 0.0.0.0:6000->6000/tcp, 0.0.0.0:8181->8181/tcp, 0.0.0.0:9443->9443/tcp, 8080/tcp sdc-frontend-1 96843fae9e4c onap/sdc-cassandra:latest "/root/startup.sh" 10 minutes ago Up 10 minutes 7000-7001/tcp, 7199/tcp, 9160/tcp, 0.0.0.0:9042->9042/tcp sdc-cassandra-1
For further information and an image explaining the containers dependency map please refer to the following page: SDC Docker Diagram
To access the logs, there are different options:
docker exec -it -u root sdc-XXXXXXXX-1 sh
Then look at the logs generally in /var/lib/jetty/logs or /var/log/onap (that may differ !)/tmp/sdc-integration-tests
, In that folder you can obtain the logs of the different containersAfter having started SDC with the command mvn clean install -P start-sdc
, different java remote debug ports are opened by default:
Look at the pom.xml of the integration-tests module to have a better understanding of all the docker settings provided to start SDC.
The integration are composed of 2 parts, one to test the BE Apis and another one to test the FE with selenium. The selenium tests make use of the selenium/standalone-firefox:2.53.1 container.
About BE APIs tests, onboarding E2E flow : Onboarding E2E flow cover following SDC functionality:
Onboard of VNF Create VF from VSP Certify VF Create Service Add VF to service Certify Service Export TOSCA and validate it structure using external TOSCA parser
**as part of execution we open a connection to Titan and perform resources clean up both before and after tests execution (only resource with “ci” prefix will be deleted from the catalog) List of VNFs/PNFs that proceed by onboarding flow, located in integration-tests/src/test/resources/Files/
)
sample-signed-pnf-cms-includes-cert-1.0.1-SNAPSHOT.zip sample-signed-pnf-1.0.1-SNAPSHOT.zip sample-pnf-1.0.1-SNAPSHOT.csar sample-pnf-custom-type.csar base_vfw.zi base_vvg.zip database-substitution-mappings.csar helm.zip Huawei_vHSS.csar Huawei_vMME.csar infra.zip resource-ZteEpcMmeVf-csar_fix.csar vbng.zip vbrgemu.zip vfw.zip vgmux.zip vgw.zip vLB.zip vLBMS.zip vSBC_update_v03.csar vsp-vgw.csar vvg.zip ZteEpcMmeVf.csar
Those tests execute the following There are 2 options to start them:
mvn clean install -P start-sdc
, run the command mvn clean install -P run-integration-tests
integration-tests/src/test/resources/ci/testSuites/backend
integration-tests/src/test/resources/ci/testSuites/frontend
In order to access the SDC UI from your dev environment you need to do the following:
webpack.server.js
found under the catalog-ui folder in the main sdc project and update the "localhost" variable to be the ip of your local vagrant machine.npm start -- --env.role <wanted_role>
with the wanted role to login to SDC as.For more information regarding SDC on OOM please refer to the following page: SDC on OOM
Install nodejs & gulp
Problem | Why is this happening | Solution |
---|---|---|
npm cannot reach destination | onboarding proxy | When within onboarding network, you should set onboarding proxy to NPM as the following: |
npm config set proxy http://genproxy:8080 | ||
npm config set https-proxy http://genproxy:8080 | ||
git protocol is blocked | onboarding network | When within onboarding network, you should set globally that when git |
and cannot connect | rules for protocols | protocol is used, it will be replaced with "https" |
git config --global url."https://".insteadOf git:// |
In order to check the life state of SDC you can run the command health
from inside the vagrant. Alternatively you can run the following commands to check the FE and BE status:
FE - curl http://<ip_address>:8181/sdc1/rest/healthCheck
BE - curl http://<ip_address>:8080/sdc2/rest/healthCheck
Another method to check about problems in SDC is to look at the log files.
The jetty(Applicative) are found in the respective folder according to the wanted section For example, the BE logs will found under the directory /BE
.
For more information regarding SDC Troubleshooting please refer to the following guide: SDC Troubleshooting