Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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 NameHEATOOMNotes
Health CheckPASSPASSAAF Refactored OOM is working well.
 AAF ← A&AIPASSPASSA&AI Pair Wise Testing for Casablanca Release, AAI also uses new BasicAuthConvert code to support old ID formats

AAF ← APPC

PendingPendingAPPC revalidating for CasaBlanca (10/22)
AAF ← CLAMPPASSPASSWaiting for Clamp PTL to report AAF usage (10/22)
However, Integration-SB4 (Plantania) reports:
  1. CLAMP -> AAF: When the user wants to run operations in CLAMP, CLAMP accesses AAF to get user permissions. Status: SUCCESS
 
 AAF ← PortalPASSPASSAll tickets closed by Sunder (10/22)
 AAF ← Portal ← PolicyPASSPASS

Policy contacts AAF indirectly through Portal (10/22)

 AAF ← Portal ← VIDPASSPASS

VID contacts AAF indirectly through Portal (10/22)

AAF ← SDNCPASSPASS

SDNC wants to utilize BasicAuthConvert code (like AAI), instructions sent




  • No labels