Publish/Subscribe Context Broker - Orion Context Broker

Chapter:
Data/Context Management
Version:
Latest
Updated:
2017-03-09
Contact Person:
Ask in Stack Overflow with tag fiware-orion
-
Feedback:
criteria value label
The overall label is the average of all individual labels assessed by Sep 2016
Documentation completeness Excellent A+++
Documentation soundness Very Good A++
APIs Failure Rate 0 tests failed/executed A+++
Detected defects by Priority 0 average bugs priority A+++
Time to respond issues < 1 day A+++
Time to fix issues < 1 day A+++
Scalability 1,02 response time/thread number A+++
Performance 1900 updates/sec A+++
Stability No memory leaks detected A+++
Although taking the binaries from our forge is sometimes an option, you may want to choose automated deployment facilities provided in the FIWARE Cloud environment you are using. The following is a description of those facilities in the FIWARE PPP Testbed (available to FIWARE PPP partners) and the FIWARE Lab (open to any developer). There are three basic automated deployment mechanisms available:
  • Images. A ready-made Virtual Machine, with the GE deployed and properly configured. This is pretty simple but it does not allow for any customised options and it requires a dedicated Virtual Machine.
  • Deploying a dedicated GE instance in your own virtual infrastructure. There will be images that will allow you to deploy a VM that contains a chef agent. Once such VM is deployed, you can deploy the GE software plus additional software by using automated facilities.
  • Deploying a dedicated GE instance based on blueprint templates for this GE. By integrating or extending a Blueprint Template available for this GE you can define your own Blueprint Template which defines the virtual infrastructure for your applications.
For this particular generic enabler instance the available deployment methods are as follows:

Deploying a dedicated GE instance based on an image

In order to deploy a dedicated instance of this GEi perform the following actions:
  1. Access the FIWARE Cloud Portal (http://cloud.lab.fiware.org)
  2. Login with your login/password (if you don't have a login/password, please register on http://account.lab.fiware.org)
  3. Click on the "Images" option at the left, then "Launch" selecting the row with the name orion-psb-image-Rn (where n is an image version number, such as 4.1).
In a matter of minutes a ready-to-use VM instance of this GEi will appear in the "Instances" area (see the FIWARE Cloud Portal guide for additional information on VM management using FIWARE Cloud). Note that orion-psb-image-Rn include not only Orion Context Broker but also other useful software related with it, such as Cygnus, the Orion PEP proxy and Rush. The RPMs installed in the image could be older than the most recent ones at FIWARE RPM reposiory, so it is strongly recommended that you update to the latest versions (read the welcome message upon SSH login for details).

Deploying a dedicated GE instance in your own virtual infrastructure

The Orion Context Broker can be installed via Chef recipes deploying an image with a chef agent installed. Then, you can go to the Instance tab and press the “Add software” button to automatically install the GE (called orion) and additional software from the software catalogue. The instructions to deploy software using recipes are available on a tutorial available on http://lab.fiware.org

Deploying a dedicated GE instance based on blueprint templates for this GE

There may be Blueprint Templates associated to this GE in the catalogue of available FIWARE Blueprint Templates. The orion-cb-sa can be used as the basis for your own Blueprint Template or to extend the Blueprint Template you are defining for your own applications. The orion-cb-sa automates the deployment of a dedicated GE instance on top of several VMs via Chef recipes defined for orion in the software catalogue. The instructions to define, extend and instantiate blueprint templates are available from a tutorial available on http://lab.fiware.org

Using the Docker container

This GE implementation provides a Docker container that can be used to run your own instance. The Dockerfile can be found here. The DockerHub page for this GE implementation can be found here.