...
Motivation: Having issues with MSO provisioning on Rackspace
Artifacts
...
log files for each VM and set of docker containers - or how to aggregate them - not necessarily at the SumoLogic level
...
- need all REST API endpoints
Use or combine with Overall Deployment Architecture to determine what a fully functional set of VMs, processes and containers should look like for 1.0.0 and 1.1.0 - so we can be sure that the ONAP deployment is sound as much as possible before provisioning VFs.
...
API Endpoints
TODO: get swagger docs for all servers
This is an expanding list of API endpoints to verify your ONAP deployment - ideally we would post a postman config and environment file.
...
Postman/Curl REST calls
...
sdnc_controller_container
...
Username / Password / Authorization Token
An aside: (I didn't realize that or I forgot an aspect of base64 - dthat we could reverse engineer the password/username combination from the encoded <alphanumeric_token> in the header key:value = Authorization:Basic <alphanumeric_token>. Again thanks Yves - use a public site like https://www.base64decode.org/ For example for MSO we take the token SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA== and get InfraPortalClient:password1$ which is defined throughout the ONAP codebase in for example the VID DockerFile.
...
Prerequisites
If running postman https endpoints (some of our VM's run SSL like AAI - but MSO for example will still run straight HTTP) - trust the server certificate in Postman (thank you Yves): You won't be able to run an https endpoint until the certificate is trusted in Chrome - paste an https request into the browser - one time - to enable the trusted certificate in postman.
...
// fix java.security.cert.CertificateException: No subject alternative names present |
|---|
MSO VM
WIP: work in progress
...
GET /aai/v8/service-design-and-creation/services HTTP/1.1 | {"service": [{ |
|---|
API Endpoints
TODO: get swagger docs for all servers
This is an expanding list of API endpoints to verify your ONAP deployment - ideally we would post a postman config and environment file.
| VM | Container | ext port | URL | user:pass | gerrit source |
| SDNC | sdnc_controller_container | 8282 | http://sdnc:8282/apidoc/explorer/index.html | admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U |
Robot Healthcheck
There actually is a set of scripts already on the robot vm inside its docker container - currently attempting to get these to pass (won't check your VFs though)
root@16e8d4997655:/var/opt/OpenECOMP_ETE# ./runTags.sh -i health h -d ./html -V /share/config/robot_properties_ete.py |
|---|
| ID | VM | Container | Process | Healthcheck |
|---|---|---|---|---|
| AAI | ||||
| MSO |
Artifacts Required
log files for each VM and set of docker containers - or how to aggregate them - not necessarily at the SumoLogic level
- VM/container or JVM health checks - ideally something like New Relic agents on the box
- Would be nice to have something we can run on vm1-robot that would automate a healthcheck on all the containers