...
Then, we can use a Postman collection that has 3 Rest Calls and some code to automate the instantiation of the vFW use case:
|
|
|---|
- 1st Rest call will give us the service model details like UUID, Invariant UUID, and Service Model Name.
|  Image Modified
|
- 2nd Rest call will give us the VNF and VF Module details.
|
- 3rd Rest call will pull the details from the 1st and 2nd calls, and build the SO Service Assignment and Activation request.
|
- I added a 4th Rest call in the collection that will pull the request id from the 3rd call coming from SO, and will show us the status of the requets, so we can track the progress, and see if it completes successfully.
|
| Note |
|---|
| title | STEP CDS2: Expose SO Catalog API |
|---|
|
SO Catalog DB is NOT exposed by default, you will need something like the command below to be able to send the CDS #2 rest call to SO Catalog and get back the service VNF model details. | Code Block |
|---|
kubectl -n onap expose pod onap-so-so-catalog-db-adapter-56d9cc554b-9fszd --type=LoadBalancer |
|
| Info |
|---|
|
| Note |
|---|
| title | STEP CDS2: Expose SO Catalog API |
|---|
| SO Catalog DB is NOT exposed by default, you will need something like the command below to be able to send the CDS #2 rest call to SO Catalog and get back the service VNF model details. | Code Block |
|---|
kubectl -n onap expose pod onap-so-so-catalog-db-adapter-56d9cc554b-9fszd --type=LoadBalancer |
|
|
Environment preparation for the Postman Collection:
...
