-
Story
-
Resolution: Done
-
High
-
None
-
CC Sprint 18 (Jun 18-Jun 29), CC Sprint 19 (Jul 02-Jul 13)
As a user of POMBA, I expect the Network Discovery Context Builder to be fully compliant to the Context Builder API. This shall include all happy path and rainy day handling.
Details to be provided here, or in shared definition of API supported by all Context Builders. See
- https://wiki.onap.org/display/DW/POMBA+Context+Builders
- https://wiki.onap.org/display/DW/POMBA+Context+Builder+Swagger
If the request is not well-formed or is missing mandatory parameters, the request shall return an error, as appropriate based on the context builder API. If the request includes unsupported parameters, the request shall also be rejected.
- Mandatory
- serviceInstanceId
- Optional
- Not Applicable
- Unsupported
- modelVersionId
- modelInvariantId
I expect the following parameters to be tuneable
- How long to wait for a response from network discovery.
Note this shall support Basic Auth. Additional security enhancements are tracked separately.
Implementation Hint
The Microservice takes the given service instance id and decomposes it into pieces that can potentially be discovered by the Network Discovery Microserves, makes the appropriate calls to the Microservice and then stitches the results together and returns them to the call.
Definition of Done
- Compliant to the ask above
- Support for all ONAP best practices
- Code checked in, use documented on Wiki
- Demo to working group
Exclusions
- mentioned in
-
Page Loading...
1.
|
Discovery and Stitch | Closed | pleigh | |
2.
|
Add "final" modifiers to fields for SONAR coverage | Closed | shanedaniel | |
3.
|
Upversion pomba-audit-common to V1 | Closed | rtait | |
4.
|
Add logging of caught exceptions for SONAR coverage | Closed | shanedaniel | |
5.
|
Feedback from Demo | Closed | rtait | |
6.
|
Change URI from network-discovery to ndcontextbuilder | Closed | rtait |