This project is part of the NUBOMEDIA research initiative.

The Nubomedia PaaS manager is the manager for PaaS Platform that exposes REST API to allow Nubomedia users to build and deploy applications on the Nubomedia Platform. This is a short guide to deploy and install the Nubomedia PaaS Manager.

The PaaS Manager is implemented in java using the spring.io framework. This manager requires that all infrastructure is running:

• Openbaton is up and running
• The MS-VNFM is up, running and registered to Openbaton
• The PaaS is configured and running (this API are tested with version 1.1 of Openshift binaries)
• A keystore with the PaaS SSL certificates exists and is available on the PaaS API machine (you can use this guide or this software to do that)

You can install the Nubomedia PaaS manager either automatically by downloading and executing the bootstrap or manually. Both options are described below.

The bootstrap repository contains the script to install and start the Nubomedia PaaS Manager automatically. In order to do it you can run the following command:

bash <(curl -fsSkl https://raw.githubusercontent.com/fhg-fokus-nubomedia/nubomedia-paas/master/bootstrap)

At the end of the installation process the Nubomedia PaaS Manager dashboard is reachable at localhost:8081

Afterwards the source code of the Nubomedia PaaS Manager is located in /opt/nubomedia/nubomedia-paas. Check if the NFVO and/or the MS-VNFM is not installed and started, otherwise the Nubomedia PaaS Manager start will fail and you need to start it manually when the NFVO and the MS-VNFM are up and running.

In case the Nubomedia PaaS Manager are already installed you can start them manually using the provided script as described here

1. Download the source code from git:

git clone https://github.com/fhg-fokus-nubomedia/nubomedia-paas.git

2. Change the properties file to reflect your infrastructure configuration:

vim nubomedia-paas/src/main/resources/paas.properties

3. Run the provided script to create the base folder for properties file (and copy the file in it)

cd nubomedia-paas/
./nubomedia-paas.sh init

NOTE if you are not root it will ask for sudo password

3. Compile the code using the provided script

cd nubomedia-paas/
./nubomedia-paas.sh compile

The Nubomedia PaaS Manager can to started by executing the following command (in the directory nubomedia-paas)

./nubomedia-paas.sh start

Once the Nubomedia PaaS Manager is started you can access the screen session that is in another window with the ms-vnfm running:

screen -r nubomedia

and move to the windows named nubomedia-paas

The configuration can to fount in /etc/nubomedia/paas.properties.

Here you can configure:

• PaaS address
• NFVO
• PaaS API address
• MS-VNFM
• Vim (according to ETSI Specification) properties
• NSD image
• Database
• Log Levels

After changing any configuration, you need to restart

Issues and bug reports should to posted to the GitHub NUBOMEDIA-PaaS Issue List

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Need some support, wish to contribute? Then get in contact with us via our mailinglist!

Issues and bug reports should to posted to the GitHub NUBOMEDIA-PaaS Issue List

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.