Hi Ambica,
Marco has provided some extra responses on the thread
https://lists.onap.org/g/onap-discuss/topic/29859955
As mentioned there, the "failure" log shows output for a second "vserver" entry
that appears to be a kind of duplicate:
"vserver":{
"vserver-id":"2eeef97c-bfb4-4e10-944d-f1ad3aa8dba0",
"vserver-name":"sprout-2.me.cw-ngv.com",
"vserver-name2":"sprout-2.me.cw-ngv.com",
"prov-status":"ACTIVE",
"vserver-selflink":"http://10.126.0.50:8774/v2.1/ac3ad678c9044ebba5190dd3dc531765/servers/2eeef97c-bfb4-4e10-944d-f1ad3aa8dba0",
"in-maint":false,
"is-closed-loop-disabled":false,
"resource-version":"1549265237018"
"vserver":{
"vserver-id":"5675e8cb-406b-40ff-a437-d1e9dff9fdee",
"vserver-name":"sprout-2.me.cw-ngv.com",
"vserver-name2":"sprout-2.me.cw-ngv.com",
"prov-status":"ACTIVE",
"vserver-selflink":"http://10.126.0.50:8774/v2.1/ac3ad678c9044ebba5190dd3dc531765/servers/5675e8cb-406b-40ff-a437-d1e9dff9fdee",
"in-maint":false,
"is-closed-loop-disabled":false,
"resource-version":"1550138633591"
I guess this is not the intention.
Could you please confirm that you and Kedar have attempted again with a fresh
data?
As this query previously worked for you on the same AAI instance, I think that
means there could only be a difference in the data setup of the scenario.
As I understand it, the "extra-properties" is a sub-object of the
"inventory-response-item", which is generated by the server as the response to
the query.
It is not a value that is manually set by the user through the REST API.
The query itself is coded in Gremlin inside the aai-traversal microservice,
with the output mapped to the REST API response.
Referring to
aai\traversal\aai-traversal\src\main\java\org\onap\aai\dbgraphmap\SearchGraph.java
:
- The server code checks for "model-invariant-id-local" and
"model-version-id-local" properties
- If these are not empty or null, the server queries for a model
matching those criteria
- If the exactly 1 matching model is found, then the model-name property
is set
For the "service-instance" item, the "success" log shows an empty "selflink",
while the "failure" log shows
"selflink":"restconf/config/GENERIC-RESOURCE-API:services/service/15ba64a2-87b0-4f79-bf2d-11e4e19e0f1c/service-data/service-topology/".
Not sure what this means for the scenario.
For the "generic-vnf" item, both the "success" log and "failure" log show that
model-name is:
- "model-name":"Sprout-Scaling-VF"
However, they have different values for "model-invariant-id",
"model-version-id" and "model-customization-id", suggesting that perhaps some
new models have been distributed from SDC in between the test runs?
The "success" log shows "vnf-type":"Sprout-Service/Sprout-Scaling-VF 0", while
the "failure" log shows "vnf-type":"Sprout-Scaling2/Sprout-Scaling-VF 0", so
the second level "model-name" properties for the "service-instance" are also
different, as expected.
The second-level "model-name" properties for the "vf-module" show the same
"model-name":"SproutScalingVf..base_sprout..module-0" and
"model-name":"SproutScalingVf..scaling_sprout..module-1", but they also have
different values for "model-invariant-id", "model-version-id" and
"model-customization-id", again suggesting perhaps some new models have been
distributed from SDC in between the test runs?
Looking more into the "success" log, it seems that:
- The extra-property for "property-name":"model-ver.model-version-id"
has the same value as the "model-version-id" in the corresponding object in the
same "inventory-response-item".
- The extra-property for "property-name":"model.model-invariant-id" has
the same value as the "model-invariant-id" in the corresponding object in the
same "inventory-response-item".
- The extra-property for "property-name":"model-ver.model-name" has the
same value as the "model-name" in the same "inventory-response-item".
It appears as though the required data fields are available, just from a
different part of the response schema.
Has there been some error message in the cleanup phase of the first run?
Maybe this is causing problems for your second run?
Keong
From: Ambica Chattoraj [mailto:[email protected]]
Sent: Saturday, 16 February 2019 00:13
To: Keong Lim <[email protected]>
Subject: FW: [aai][policy] Not getting all extra-properties in AAI named query
Hi Keong ,
We are facing the below mentioned issue. Can you please help us with the
understanding of named query.
And also how can we update the "extra-property" fields.
Thanks & Regards,
Ambica
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kedar Ambekar
Sent: Friday, February 15, 2019 11:42 AM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] [aai][policy] Not getting all extra-properties in AAI
named query
Hi,
We are trying to test the Scaleout scenario by generating an ONSET event to be
picked up by policy. We are using Casablanca release with OOM based
installation.
We are observing that the AAI data returned in response to named query for the
vserver does not have the fields model-ver.model-name and
model-ver.model-version-id in the extra-properties section for the service,
vnf and vf module data. Hence policy is not able to send the same to SO and the
scale-out fails at SO because of missing parameters.
When we searched, came across closed Jira ticket
https://jira.onap.org/browse/AAI-456 that was reported for Amsterdam which had
similar issue.
Attached log has the named query response for the error scenario.
Btw, this scenario used to work for us before on the same AAI instance.
Attached logs for this previous success scenario as well.
Appreciate any inputs on this !
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy statement, you may
review the policy at http://www.techmahindra.com/Disclaimer.html externally
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
============================================================================================================================
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15606): https://lists.onap.org/g/onap-discuss/message/15606
Mute This Topic: https://lists.onap.org/mt/29859955/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-