遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/1197)
<a href="https://www.bestpractices.dev/projects/1197"><img src="https://www.bestpractices.dev/projects/1197/badge"></a>
CLAMP is a platform for designing and managing control loops. It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it. Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it.
It interacts with other systems to deploy and execute the closed loop. For example, it pushes the control loop design to the SDC catalog, associating it with the VF resource. It requests from DCAE the instantiation of microservices to manage the closed loop flow. Further, it creates and updates multiple policies in the Policy Engine that define the closed loop flow.
The ONAP CLAMP platform abstracts the details of these systems under the concept of a control loop model. The design of a control loop and its management is represented by a workflow in which all relevant system interactions take place. This is essential for a self-service model of creating and managing control loops, where no low-level user interaction with other components is required.
At a higher level, CLAMP is about supporting and managing the broad operational life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the ability to design, test, deploy and update control loop automation - both closed and open. Automating these functions would represent a significant saving on operational costs compared to traditional methods.
https://wiki.onap.org/display/DW/Resources+and+Repositories
All source files are copyrighted and licensed according to contribution guidelines.
Git and Gerrit are used.
THis policy is enforced in Gerrit code review tool
All builds are fully automated and reproductiible from the source. (buidls are maven based) All scripts are publicly available under the ci-management repo : https://gerrit.onap.org/r/gitweb?p=ci-management.git;a=tree;h=refs/heads/master;hb=refs/heads/master
The test is launched by default while building the software, this is integrated in the maven build. This is explained in the development guide for CLAMP : https://wiki.onap.org/display/DW/CLAMP+Development+Guide
For each pull request, the project needs to be built successfully before the Merge option becomes activated. The test will be run automatically during the building process as well. Once build successfully and all tests has past, the Merge option will be activated. see https://jenkins.onap.org
The project is moving towards this goal.
all connection can be secured by TLS (configurable) https://wiki.onap.org/display/DW/CLAMP+Project
CLAMP uses AAF and thus defaults all clients to HTTP/S TLS 1.1 & 1.2
// X-Content-Type-Options was not set to "nosniff".
This mainly java based or javascript we don't use compiler to generate binaries. we didn't configure csp header eiher.
Assert are used mainly in the unit test for now. We throw exceptions by ourselves in Clamp code.
后退