Description of Use Case / Requirement:

As CLAMP is going into maintenance mode in Honolulu because :
-) there is not enough diversity interest from the community (only AT&T contributing actively since several releases ) as highlighted by the maturity review done during Guilin release.

So to keep the CLAMP functionality the plan is to merge that functionality into the Policy Framework this will allow ONAP to:

-) keep CLAMP functions into ONAP

-) reduce ONAP footprint

-) consolidate the UI (Control loop UI and policy)

CLAMP and Policy team have already discussed and are ok with that direction.

In practice we plan to integrate the CLAMP repo into the Policy framework, either by keeping and renaming the current repo or creating a new repo and copying the old CLAMP repo into that new one.

The goal for Honolulu would be to integrate the missing specific Policy UI into the CLAMP GUI and use the existing Policy API for the feeding.

 Should be the Assignee - use @ notation): osgn422w

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

 Move/Clone current CLAMP project repo under Policy Project repos

Project Impact (Test Only (TO), Code (C)): C **

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

CLAMP : S

Policy: S

Integration Leads (use @ notation): 

Company Engagement: 

 AT&T