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 ← Portal ← Policy AAF ← Policy | PASS | PASS | AAF ← Policy ← Portal is OK as tested today in SB04 (10/24)> AAF ← Policy APIs, passed last week tests in SB04. It needs to be retested as the bootstrapping data was manually changed. It will be retested with the new image that incorporates this AAF bootstrapping data mentioned above. The tickets to track enabling and retest it in Policy side: POLICY-1216, 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 |