Description of Use Case / Requirement:

As CLAMP is in maintenance mode in Honolulu and being archived in Istanbul 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 successfully finalized the Honolulu POC implementation, So CLAMP integration to Policy is actually effective and already working.

the CLAMP repo has been copied into a new repo under the Policy framework repo, the new repo is named "policy/clamp".

The goal for Istanbul would be to solve bugs discovered during the release.

 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):  jhh

note that the integration team has a basic-clamp script for integration validation too in the CI chain, see:

https://jira.onap.org/browse/INT-1819

Company Engagement: 

 AT&T