Note: In General, AAF is the END Source of Information... Thus, clients can talk to AAF, but it does not talk to other ONAP clients.
| Projects Name | HEAT | OOM | Notes |
|---|
| Health Check |
PASS | PASS | AAF Refactored OOM is working well. | PASS | PASS | A&AI Pair Wise Testing for Casablanca Release, AAI also uses new BasicAuthConvert code to support old ID formats | PASS | PASSAPPC (Takamune) validated Authentication and API calls (10/22) | PASS | PASS | Waiting for Clamp PTL to report AAF usage (10/22)However, Integration-SB4 (Plantania) reports:CLAMP -> AAF: When the user wants to run operations in CLAMP, CLAMP accesses AAF to get user permissions.Status: SUCCESS PortalPASS | PASS | All tickets closed by Sunder (10/22) | AAF ← Policy | PASS | PASS(*) | AAF ← ← Policy OKAAF ← Policy (Heartbeat) OK
AAF ← Policy (PDP-D) OK(*) (PDP-X) retest POLICY-1217.PASS | PASS | VID contacts AAF indirectly through Portal (10/22) SDNCPASS | PASS | wants to utilize BasicAuthConvert code (like AAI), instructions sent
