...
Send vCPE homing template to HAS, E.g.
$ curl -X POST --user admin1:plan.15 -H 'Content-Type: application/json' \
-d @homing.json localhost:8091/v1/plansHint: homing.json may be created by conjoining
Code Block { "name": "vCPE homing Beijing 2.0.0-ONAP", "template": <<HAS Homing Specification (R')>> }
where HAS Homing Specification (R') = https://wiki.onap.org/display/DW/vCPE+Homing+Use+Case
Hint: for username:password (--user above) see ~/conductor.conf, conductor_api section
ISSUE_1: At this point a request fails with an error and the following message is returned for the homing request:
After a 5 mins long timeout, the HAS api component replies back with error:
Code Block language js { "error_message": { "explanation": "Unable to create Plan.", "code": 500, "error": { "message": "The server has either erred or is incapable of performing the requested operation.", "type": "HTTPInternalServerError" }, "title": "Internal Server Error" } }
The underlying communication can be observed by capturing network traffic on the docker bridges by Wireshark. The communication is stuck (which causes the timeout at the api component) after a faulty MUSIC reply:
Request to MUSIC sent by the controller: PUT /MUSIC/rest/v2/keyspaces/conductor_rpc/tables/controller/rows?id=<<Some UUID>>
- This request is a database primitive of the MUSIC API which modifies a row identified by <<Some UUID>> in table *controller* of keyspace *conductor_rpc*. The data of the new database entry is delivered in the HTTP request body (not included here), which can be captured by Wireshark observing the communication between the controller HAS component and MUSIC.
MUSIC's reply: "Exception thrown while doing the critical put, check sanctity of the row/conditions:\nnull"
- The produced HTTP stream between `controller` and MUSIC captured with Wireshark:
View file name HAS-MUSIC consitency-atomic.txt height 250
...