# ONAP MSO ---- ---- # Introduction ONAP MSO is delivered with **2 Docker containers**, 1 hosting the **database** (MariaDB) and 1 hosting the **JBoss** application server running all ONAP MSO code. Both containers runs on the same machine and can be started with **`docker-compose`**. # Compiling MSO MSO can be compiled with `mvn clean install`. Integration tests are started with the following profile `-P with-integration-tests` **to be edited for rrelease** Docker containers are build with the following profile `-P docker -Ddocker.buildArg.chef_repo_branch_name=bugfix/external_adress -Ddocker.buildArg.chef_repo_git_username=git -Ddocker.buildArg.chef_repo_address=23.253.149.175/mso -Ddocker.buildArg.chef_repo_git_name=chef-repo` # Getting the containers ONAP MSO containers are stored on [here](https://nexus3.onap.org:10002) for the releases, and [here](https://nexus3.onap.org:10003) for the snapshots The following Docker images are the actual deployment images used for running MSO | Name | Tag | Description | |-----------------|---------|-------------------------------------------------------------------------------------------------------------------------------| | onap/mso | 1.0.0 | Contains **JBoss** + **OpenJDK** + **MSO** components (BPMN engine and MSO API handlers and adapters) | | library/mariadb | 10.1.11 | **MariaDB** image from Docker.io, this image hosts the database and is preloaded with MSO schema and configuration at startup | # Starting MSO ### docker-compose You can use `docker-compose` to start MSO. The file is as the root of the directory. See `Getting the containers` to pull the images ### Heat template A heat template that can be used on RackSpace to spin up the MSO Host VM and run docker-compose is currently being built by the Demo Team. # Accessing MSO MSO UIs are not really used for operating MSO, but they provide information on what is currently happening and get an insight on the components. ### MSO JBoss console JBoss Wildly provides administrative functions through the application [server console](https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Accessingthewebconsole]. Said console can be used to have a look at the status of MSO. It is providing details on deployed artifacts and gives a remote access to the main server log file The UI can be accessed trough http://containerHostName:9990/ The configuration preloads a default user (admin) with the standard `placeholder` password. The configuration of JBoss should not be touched. But it is possible to look at the two following sections for insights on the MSO health : ![deployments or runtime](http://img11.hostingpics.net/pics/332403image2016112412225.png) Deployments shows what is deployed and running on the application server, you should see the following once MSO is up and running (Actual names of the War files may differ but their numbers and general format should be the same) ***to be upload when rrelease*** Runtime can be used to have a look a the main server log files, see JVM status and parameters, environment settings etc,... ![runtime monitor](http://img11.hostingpics.net/pics/244948image20161124123216.png) See the logging section below for more details about other logfiles (EELF framework) ### MSO Camunda Cockpit console MSO orchestration processes can be monitored with the [Camunda Engine cockpit UI](https://camunda.org/features/cockpit/). It gives an insight about the available processes, allows to trigger them manually and provides monitoring of the currently running processes **IMPORTANT NOTE** : since ONAP MSO only uses Camunda Community version it is not possible to see history of running process as this is an Enterprise feature only. #### Accessing the Cockpit The cockpit is available at the following address : http://containerHostname:8080/cockpit When the container is started it will create a default admin user (admin) with the password `placeholder` for UI The
This source repository contains the code for SDN Controller operations, administration and maintenance utilities. This code depends on the following, which should be downloaded and compiled first:

1. org.openecomp.sdnc/sdnc-core
2. org.openecomp.sdnc/sdnc-adaptors
3. org.openecomp.sdnc/sdnc-northbound
4. org.openecomp.sdnc/sdnc-plugins

To compile this code:

1. Make sure your local Maven settings file ($HOME/.m2/settings.xml) contains references to the OpenECOMP repositories and OpenDaylight repositories.  See example-settings.xml for an example.

2. To compile, run "mvn clean install".