Schema Proposal

1. tbc

Code Proposal

1. In AAI, when the "orchestration-status", "service-instance-location-id", "input-params" for a Service Instance changes, notify ExtAPI so it does not need to poll AAI
   
   • AAI does have precedent for publishing events to DMaaP
   • ExtAPI to be updated to consume events from DMaaP
   • need to get agreement about topic configuration
   • Discuss with Adrian OSullivan and Ludovic Robert, to confirm whether existing AAI-EVENT topic in DMaaP suffices for this requirement

   • From Jimmy Forsyth (AT&T) to Everyone: 01:51 AM
     @Brian, yes, AAI sends notification on all changes to DMaaP to the AAI_EVENT (or maybe it’s AAI-EVENT) topic

2. In client code using AAI API, make use of "nodes query" as shown in newly published documentation to optimise some queries on AAI data:
   • https://docs.onap.org/en/latest/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/nodesQuery.html
     
   • Ludovic Robert For example instead of
     • "GET /aai/v11/customers/{customerId}service-subscription/{service_subscriptionId}service-instance API/{service-instanceId}"
     • use "GET /aai/v11/nodes/service-instances/service-instance/{service-instanceId}" instead

     • From Jimmy Forsyth (AT&T) to Everyone: 01:51 AM
       @Adrian the answers are yes, service-instance-id is unique in ONAP and you can query it directly with the nodes query (see link above)

3. tbc