(OLD) Release 0 HowTo guide for developers

From OSM Public Wiki
Revision as of 00:02, 6 May 2016 by Gunturu (talk | contribs)
Jump to: navigation, search

The OSM code is organized into four modules. The following diagram illustrates how these four components fit together:
Osm architecture.png

Launchpad (User Interface): Launchpad provides the user interface to the OSM orchestrator. From the Launchpad user can manage the catalog, compose the NS/VNF descriptors and perform the lifecycle management on Network Services. In addition, the UI also provides the ability execute the NS/VNF level configuration primitives.
Service Orchestrator (SO): Service Orchestrator is responsible for End-to-End service orchestration. It is responsible for instantiating the NS, and starting the configuration plugins such as JUJU charms.
Resource Orchestrator (RO): Resource Orchestrator is responsible for creating and placement of compute and networking resources. It is also responsible for interfacing with SDN controller.
Juju Charms (Charms):Juju charms provide the VNF abstraction and configuration for the VNFs. The Service Orchestrator interfaces with the JUJU charm to configure the VNF.