| commit | 249699f8fb908359213697055b66637c9baeda99 | [log] [tgz] |
|---|---|---|
| author | Determe, Sebastien (sd378r) <sd378r@intl.att.com> | Tue Aug 08 03:14:52 2017 -0700 |
| committer | Sébastien Determe <sd378r@intl.att.com> | Tue Aug 08 12:36:19 2017 +0000 |
| tree | 0041a981ee940c8aaf32ecaf77916c36b8f25988 | |
| parent | e63aa2efcd5dff2af82b39368d5989763c9cdd6f [diff] |
Rework of the unit tests (mainly IT) Rework of the unit tests (mainly IT) + new example files and test resource config Change-Id: I4970b3710c7decdc8a3265a86115097d4394ad80 Issue-Id: CLAMP-1 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
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.
Owner: ONAP CLAMP Dev team Mailing List : onap-discuss@lists.onap.org Add the following prefix to Subject on the mailing list : [CLAMP] See here to subscribe : https://wiki.onap.org/display/DW/Mailing+Lists
https://wiki.onap.org/display/DW/CLAMP+Project
Jenkins Job: ${jenkins-joblink}
CLAMP UI: ${cockpit-link}
Logs: ${elk-link}
You can use the following command to build the clamp docker image:
mvn clean install -P docker
Currently, the clamp docker image can be deployed with small configuration needs. Though, you might need to make small adjustments to the configuration. As clamp is spring based, you can use the SPRING_APPLICATION_JSON environment variable to update its parameters.
There are two needed datasource for Clamp. By default, both will try to connect to the localhost server using the credentials available in the example SQL files. If you need to change the default database host and/or credentials, you can do it by using the following json as SPRING_APPLICATION_JSON environment variable :
{"spring": { "datasource": {"url":"jdbc:mysql://anotherDB.onap.org:3306/camunda?autoReconnect=true", "username": "admin", "password": "admin"}, "cldsdatasource": {"url":"jdbc:mysql://anotherDB.onap.org:3306/clds?autoReconnect=true", "username": "admin", "password": "admin"} } }
A docker-compose example file can be found under the extra/docker/clamp/ folder.
Once the image has been built and is available locally, you can use the docker-compose up command to deploy a prepopullated database and a clamp instance available on http://localhost:8080/designer/index.html.
Clamp uses logback framework to generate logs. The logback.xml file cand be found under the src/main/resources/ folder.
With the default log settings, all logs will be generated into console and into root.log file under the Clamp root folder. The root.log file is not allowed to be appended, thus restarting the clamp will result in cleaning of the old log files.