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. |
| AAF ← A&AI | PASS | PASS | A&AI Pair Wise Testing for Casablanca Release, AAI also uses new BasicAuthConvert code to support old ID formats |
AAF ← APPC | PASS | PASS | APPC |
| (Takamune) validated Authentication and API calls (10/22) | |||
| AAF ← CLAMP | PASS | PASS | Waiting for Clamp PTL to report AAF usage (10/22) However, Integration-SB4 (Plantania) reports:
|
| AAF ← Portal | PASS | PASS | All tickets closed by Sunder (10/22) |
AAF ← Policy | PASS | PASS(*) | AAF ← Portal ← Policy |
OK AAF ← Policy (Heartbeat) OK AAF ← Policy (PDP-D) OK (*) AAF ← Policy (PDP-X) retest POLICY-1217. |
| AAF ← Portal ← VID |
| PASS | PASS |
VID contacts AAF indirectly through Portal (10/22) | |||
| AAF ← SDNC | PASS | PASS | SDNC wants to utilize BasicAuthConvert code (like AAI), instructions sent |