Versions Compared

Old Version 8

changes.mady.by.user Bin Yang

Saved on

compared with

New Version Current

changes.mady.by.user Christopher McCray

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Project NameOOMNotes
Health CheckPASS

MultiVIM ↔ APPC, via API

FailN/ANo change to the interface from Amsterdam.

Test by apidoc: http://10.12.6.138:30230/apidoc/explorer/index.html#!/appc-provider(2016-01-04)/restart_post_2

Request url:

http://10.12.6.138:30230/restconf/operations/appc-provider:restart

The input is:   

  {
          "input":{
                "common-request-header":{
                      "service-request-id":"1"
                },
                "vnf-resource":{
                      "vm-id":"http://msb-iag.onap:80/api/multicloud-titaniumcloud/v1/CloudOwner/RegionOne/compute/v2.1/0e148b76ee8c42f78d37013bf6b7b1ae/servers/56a02ba6-d550-4210-a5dd-740cfa960fa2",
                      "identity-url":"http://msb-iag.onap:80/api/multicloud-titaniumcloud/v1/CloudOwner/RegionOne/identity/v2.0"
                }
          }
}

The output:

{ "output": { "common-response-header": { "completed": "2018-10-10 07:04:33.000093", "reason": "APPC0060E Application null graph APPC:topology-operation-all:2.0.0 completed with failure: error code = 500, message = APPC0020E Provider http://msb-iag.onap:80/api/multicloud-titaniumcloud/v1/CloudOwner/RegionOne/identity/v2.0 cannot be found or cannot be resolved to one of the known providers, [[null, http://localhost:8181/apidoc/explorer/index.html]].", "service-request-id": "1", "success": false, "duration": 271413 }, "vm-id": "http://msb-iag.onap:80/api/multicloud-titaniumcloud/v1/CloudOwner/RegionOne/compute/v2.1/0e148b76ee8c42f78d37013bf6b7b1ae/servers/56a02ba6-d550-4210-a5dd-740cfa960fa2" } }
MultiVIM ↔ SO, via APIongoingPASS

Tested on OOF pod -

vFW Create/Query/Delete have been performed successfully.
vFW Create tested with oof_directives - verified that flavor was replaced in Multicloud before stack instantiation

The pairwise testing has been on track now. SO could issue the API request to multicloud and multicloud could receive the request. The next step is that SO adaptor change the request body so that multicloud could decode it correctly

.

MultiVIM ↔ VFC, via APIN/Ano pair-wise testing needed since nothing new from VFC's perspective
MultiVIM ↔ OOF, via APIStoppedN/ANo change to the interface from Beijing.Relies on SO/MultiVIM testing which was ongoing
MultiVIM ↔ AAI, via APIPASSThe VIM registration/onboarding exercise verified that both multicloud framework and plugin for windriver work well with AAI within OOM deployed ONAP
MultiVIM ↔ MSB, via API (gateway)PASSThe VIM registration/onboarding exercise verified that both multicloud framework and plugin for windriver work well with MSB within OOM deployed ONAP
MultiVIM ↔ ESR, via API (register)PASSThe VIM registration/onboarding exercise verified that both multicloud framework and plugin for windriver work well with AAI within OOM deployed ONAP