Sign inSign up

openbaton/vnfm-dummy-rest

By openbaton

•Updated about 9 years ago

Imitates the behavior of a real VNFManager. For communicating with the NFVO it uses the Rest API.

Image
1

368

openbaton/vnfm-dummy-rest repository overview

Copyright © 2015-2016 Open Baton⁠. Licensed under Apache v2 License⁠.

⁠Dummy VNFManager Rest

The Dummy-VNFManager-Rest imitates the behaviour of a real VNFManager. For the communication with the NFVO it uses the NFVO's Rest API.
If you use the Dummy-VNFManager-Rest for deploying a network service it will not create any resources. When the NFVO sends commands to the Dummy-VNFManager-Rest, it will answer as if it executed them although it actually did not. In this way Openbaton can be tested without actually deploying anything.

⁠Technical Requirements

In order to execute the dummy-vnfm-rest, you need to have a running and configured NFVO.

⁠How to install the Dummy VNFManager Rest from source code

Git clone the project into the /opt/openbaton directory (you may need to be logged in as root user, unless you change the permissions on the /opt/openbaton folder):

mkdir /opt/openbaton
git clone https://github.com/openbaton/dummy-vnfm-rest.git

And Execute

cd /opt/openbaton/dummy-vnfm-rest; ./dummy-vnfm.sh compile

to compile it.

⁠How to use the Dummy VNFManager Rest

To start the Dummy-VNFM-Rest execute

cd /opt/openbaton/dummy-vnfm-rest;./dummy-vnfm.sh start

This will create a new screen window which you can access using screen -x openbaton.

If you want to run the Dummy VNFManager Rest on another machine than on which the NFVO is running you first have to configure it. The problem is that the endpoint which is sent to the NFVO is by default http://localhost:8080⁠, but if the VNFManager runs on another machine the NFVO will not be able to reach the VNFManager because the endpoint does not specify the manager's correct location. To change that you have to adapt the endpoint in the conf.properties file in the resource folder of the VNFManager.
Furthermore you have to tell the VNFManager where the NFVO is running. This can be done by changing the properties in the application.properties file which is also located in the project's resource folder.
You can change the following properties:

PropertyFunction
server.portThe port on which the VNFM will listen for the NFVO's messages. Do not forget to also change the endpoint in conf.properties if you change it.
vnfm.rest.nfvoHostThe ip address of the machine on which the NFVO is running.
vnfm.rest.nfvoPortThe port on which the NFVO is running.
vnfm.rest.nfvoSslSet this to true if the NFVO uses SSL.

Instead of changing the properties directly in the project you can also create an external properties file.
To do this create the file /etc/openbaton/dummy-vnfm-rest.properties and copy the properties of the previously mentioned application.properties file into it.

To use the Dummy-VNFManager-Rest for "deploying" a network service you have to store a VimInstance with type test in the NFVO and the Virtual Network Function Descriptors used to describe the network service have to define their endpoint as test.

⁠How to extend the Dummy VNFManager Rest

If you want the Dummy VNFManager Rest to behave differently you can change it's behaviour in the DummyRestVNFManager.java class. In this class all the methods are defined that will be executed by a VNFM while deploying a network service.

⁠Issue tracker

Issues and bug reports should be posted to the GitHub Issue Tracker of this project

⁠What is Open Baton?

Open Baton is an open source project providing a comprehensive implementation of the ETSI Management and Orchestration (MANO) specification and the TOSCA Standard.

Open Baton provides multiple mechanisms for interoperating with different VNFM vendor solutions. It has a modular archiecture which can be easily extended for supporting additional use cases.

It integrates with OpenStack as standard de-facto VIM implementation, and provides a driver mechanism for supporting additional VIM types. It supports Network Service management either using the provided Generic VNFM and Juju VNFM, or integrating additional specific VNFMs. It provides several mechanisms (REST or PUB/SUB) for interoperating with external VNFMs.

It can be combined with additional components (Monitoring, Fault Management, Autoscaling, and Network Slicing Engine) for building a unique MANO comprehensive solution.

⁠Source Code and documentation

The Source Code of the other Open Baton projects can be found here⁠ and the documentation can be found here⁠

⁠News and Website

Check the Open Baton Website⁠

Follow us on Twitter @openbaton⁠

⁠Licensing and distribution

Copyright © [2015-2016] Open Baton project

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.

⁠Support

The Open Baton project provides community support through the Open Baton Public Mailing List and through StackOverflow using the tags openbaton.

⁠Supported by

Tag summary

Content type

Image

Digest

Size

72.1 MB

Last updated

about 9 years ago

docker pull openbaton/vnfm-dummy-rest