Updated Bridge: https://zoom.us/j/455740750
...
| Duration | Agenda Item | Requested by | Notes / Links | |
|---|---|---|---|---|
| START RECORDING | ||||
| Release planning reminders | Policy team Sprint | |||
| Discussion Resolution on Deploy/Undeploy PAP API | ||||
CLAMP Team Sprint | ||||
| Q/A | ||||
ATTENDEES
NOTES
- M3 tomorrow
- Discussed CSIT wiki and remaining tests to implement
- Jorge put together conclusions on PDP to PAP interaction
- (A) healthcheck and statistics reports, and query API
- Return response to the best of the PAP system’s state knowledge (which should converge to accuracy based on the periodic reports expected from PDPs).
- The new healthcheck interface will be new the interface to robot framework.
- (B) For deploy, state change, delete API similarly, PAP will return Client Application a response, either success or failure.
- Success if all preconditions are satisfied given the current knowledge that PAP knows about PDP states at the point of time of receiving the request.
- Validation checks will ensure among other checks will ensure that the policy is in the database (from API) with a policy id, that there are PDPs available to serve the policy, etc … PAP will place the deploy in DMaaP and return success if all the previous is successful. Failure otherwise. In the unexpected case that the policy is not loaded by no PDP, PAP eventually will come to terms as it is receiving the periodic PDP Status reports and will note a mismatch to an “expectation” that the policy is served. The recovery action or alarming in that situation is still to decide, not critical at this point to make a decision on it.
- Meet later to discuss Deploy API for CLAMP and API payload swagger
- Need Liam's review in later this week to clean that up
- Need to have API payloads ready for CLAMP by Monday!!!
RECORDING
| View file | ||||
|---|---|---|---|---|
|