https://osm.etsi.org/wikipub/api.php?action=feedcontributions&feedformat=atom&user=Thomasn 2026-05-11T05:49:00Z User contributions MediaWiki 1.39.1 https://osm.etsi.org/wikipub/index.php?title=(OLD)_Release_0_HowTo_guide_for_developers&diff=638 2016-06-16T15:52:48Z

<p>Thomasn: </p> <hr /> <div>==Architecture Overview==<br /> The OSM code is organized into four modules. The following diagram illustrates how these four components fit together: &lt;br&gt;<br /> [[File:osm_architecture.png|800px]] &lt;br&gt;&lt;br&gt;<br /> '''Launchpad (UI):''' 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. The following page describes [[Developer HowTo for UI Module|Developer HowTo for UI Module]]&lt;br&gt;<br /> '''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. The following page describes [[Developer HowTo for SO Module|Developer HowTo for SO Module]].&lt;br&gt;<br /> '''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. The following page describes [[Developer HowTo for RO Module|Developer HowTo for RO Module]]&lt;br&gt;<br /> '''Juju (CM):''' Juju provides the Configuration Manager for the VNFs. The Service Orchestrator interfaces with Juju server to configure the VNFs. The project is hosted on github : [https://github.com/juju/juju Juju development site]. VNFs developers should look first at developing Juju charms (language independent) here : [https://jujucharms.com/docs/stable/authors-intro charmer intro].<br /> <br /> ==Common Developer Guidelines==<br /> The following section provides developer guidelines across modules. For module specific guidelines refer to module specific links indicated above.<br /> * Please make sure that no one else is already working on an item in bugzilla before making changes. If someone is already working it, please check with the person first.<br /> * Similar rules applies when addressing a new feature/blueprint<br /> * Use meaningful comments when checking in the code<br /> * Use consistent conventions/style for changes to an existing module<br /> <br /> {{Feedback}}</div>

Thomasn