OpenNaaS works as an standalone OSGi application as it is explained in Technologies. In It deploys an OSGi container and, in top of it, OpenNaaS is deployed as a set of OSGi bundles. OpenNaaS architecture is divided in two parts: core and extensions. Core is the basic functionality of OpenNaaS and extensions are optional OSGi bundles to add more features.

...

OpenNaaS define basic core components providing common model to develop extension extensions on the top of it. They are placed in core project.

Resource

A Resource is the logical representation of a physical or virtual device. It has a descriptor, a model and one or more capabilities. A resource can be a router, a switch, etc.

In OpenNaaS source code, resource is defined by org.opennaas.core.resources.IResource Java interface and implemented by org.opennaas.core.resources.Resource Java class in org.opennaas.core.resources project.

Resource Descriptor

A resource is instantiated in OpenNaaS from its Resource Descriptor, an XML file which provides the necessary parameters to configure a resource. It contains the type, the name and the capabilities of the resource.

In OpenNaaS source code, resource descriptor is defined by org.opennaas.core.resources.descriptor.ResourceDescriptor Java class in org.opennaas.core.resources project. Samples of Resource descriptors can be found in utils/examples/descriptors folder.

Resource Model

The Resource Model is a description of a resource which contains all the information that OpenNaaS can access from it. It is based in the CIM specification.

In OpenNaaS source code, resource model is defined by org.opennaas.core.resources.IModel Java interface in org.opennaas.core.resources project. Each resource implementation defines its own model implementing this interface.

Resource Life cycle

Resources have a Resource Life Cycle as it is defined in System Architecture. It is defined by an state diagram and its transitions.

...

Resource Manager

The Resource Manager uses these descriptors Resource Descriptors to instantiate each resource in OpenNaaS. Moreover it provides the interface between the user and OpenNaaS to manage resources' life cycle. It delegates to Resource Repositories operations which depend on each resource type.

Resource Repository

Resource RepositoryRepositories are created for each type of resource. Each repository has the responsibility of managing resources of a concrete type. The Resource Manager interacts with each repository. Moreover, when a resource repository is created, it publishes itself as an OSGi service to provide to Resource Manager a way to instantiate resources of each type.

...

A Capability represents a feature or an ability which a resource can do. Each resource 's type has a set of supported capabilities which define its features.  The list of capabilities for a given resource is a subset of these supported ones, and it is specified in the resource descriptor.

In OpenNaaS source code, capability is defined by org.opennaas.core.resources.capability.ICapability Java interface and partially implemented by org.opennaas.core.resources.capability.AbstractCapability Java abstract class in org.opennaas.core.resources project. Each concrete capability implements this Java class defining its own implementation.

...

Capabilities have Capability FactoryFactories allowing instantiating and initializing capabilities of a resource.

...

In OpenNaaS source code, action is defined by org.opennaas.core.resources.action.IAction Java interface and implemented by org.opennaas.core.resources.action.Action Java class in org.opennaas.core.resources project. In the same project, action set is defined by org.opennaas.core.resources.action.IActionSet Java interface and implemented by org.opennaas.core.resources.action.ActionSet Java class. Finally, in the same project, command is defined by org.opennaas.core.resources.command.ICommand Java interface and implemented by org.opennaas.core.resources.command.Command Java class.

Finally, action set, action and command can be UML modelled as:

Protocol Manager and Protocol Session Manager

OpenNaaS uses lots of different protocols in its operations. The Protocol Manager copes with each protocol and session. A Protocol Session Manager is instantiated for each session each protocol session established with each concrete device. The user can interact with OpenNaaS creating, removing, editing or getting information of each protocol session and protocol.

In OpenNaaS source code, protocol manager is defined by org.opennaas.core.resources.protocol.IProtocolManager Java interface and implemented by org.opennaas.core.protocols.sessionmanager.ProtocolManager Java class in orgclass in org.opennaas.core.resources projectresources project. In the same project, protocol session manager is defined byby org.opennaas.core.resources.protocol.IProtocolSessionManager Java interface and implemented by org.opennaas.core.protocols.sessionmanager.ProtocolSessionManager Java class. Each protocol has implementations of its own protocol session.

Extension components

Each resource type and concrete capability are developed as extensions of OpenNaaS. Extensions are placed in extensions project. In current OpenNaaS development, there are a set of resources, each of them has one ore more capabilities with zero or one driver developedmore developed drivers. More information can be found in Compatibility Matrix.

Queue Manager

The Queue Manager is a mandatory capability of each resource. It is a transaction execution engine (sometimes simply misnamed queue) that queues actions and executes them. If anything goes wrong, the operation is rolled back. It has an state diagram defined by four states:

...

In OpenNaaS source code, there are resource descriptor examples for router resources in the project folder utils/examples. There are this these resource descriptor examples:

...

Chassis capability allows doing operations with router like activating/deactivating interfaces, creating/deleting sub-interfaces, creating/deleting logical routers, adding/removing interfaces in logical routers or setting interface encapsulation labels.

In OpenNaaS source code, IP Chassis capability is defined by org.opennaas.extensions.router.capability.chassis.IChassisCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.router.capability.chassis.ChassisCapability in router.capability.chassis extension project.

...

Static route capability allows creating/deleting static routes in the router (defined by RFC 791).

In OpenNaaS source code, IP Static Route capability is defined by org.opennaas.extensions.router.capability.staticroute.IStaticRouteCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.router.capability.staticroute.StaticRouteCapability in router.capability.staticroute extension project.

...

OSPF capability allows activating/deactivating Open Shortest Path First protocol in routers (also called OSPF, defined by RFC 2328). It allows too configuring or Also, it allows configuring/clearing current OSPF configurations. Besides it allows configuring/removing OSPF areas, adding/removing interfaces in OSPF areas, enabling/disabling OSPF interfaces. Finally, it allows getting/showing OSPF configuration.

In OpenNaaS source code, IP OSPF capability is defined by org.opennaas.extensions.router.capability.ospf.IOSPFCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.router.capability.ospf.OSPFCapability in router.capability.ospf extension project.

GRE Tunnel capability

GRE tunnel Tunnel capability allows creating/deleting Generic Router Encapsulation tunnels (also called GRE tunnels, defined by RFC 2784).

In OpenNaaS source code, IP GRE Tunnel capability is defined by org.opennaas.extensions.router.capability.gretunnel.IGRETunnelCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.router.capability.gretunnel.GRETunnelCapability in router.capability.gretunnel extension project.

...

VRRP capability allows configuring/uncofiguring VRRP protocol in router (defined by RFC 5798). Moreover, it allows updating VRRP virtual IP address and VRRP priority.

In OpenNaaS source code, IP VRRP capability is defined by org.opennaas.extensions.router.capability.vrrp.IVRRPCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.router.capability.vrrp.VRRPCapability in router.capability.vrrp extension project.

...

OpenNaaS has developed extensions for Juniper Network Operating System (also called Junos) present in Juniper routers. It provides compatibility with Juniper routers using Junos version 10.0. Each router resource capability has a Junos implementation of Action and Command.

In OpenNaaS source code, Junos action Action is defined by org.opennaas.extensions.router.junos.actionssets.actions.JunosAction Java abstract class in router.actionsets.junos extension project. In the same project, in actionssets/actions folder there are specific folders for each router resource capability action implementations. Moreover, in the same project, each router resource capability action set has specific implementation in in actionssets folder. Finally, in the same project, commandsets/commands folder has specific implementation of each router resource capability command based on org.opennaas.extensions.router.junos.commandsets.commands.JunosCommand abstract Java class.

...

Connections capability allows creating/removing fibre optics connections in the optical switch.

In OpenNaaS source code, Monitoring Connections capability is defined by org.opennaas.extensions.roadm.capability.connections.IConnectionsCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.roadm.capability.connections.ConnectionsCapability in roadm.capability.connections extension project.

...

OpenNaaS has developed extensions for W-onesys optical switches, concretely a concretely ROADM Proteus S8 ones. Each ROADM switch resource capability has a W-onesys implementation of Action and Command.

...

OpenNaaS has developed extensions to use GÉANT AutoBAHN bandwidth allocation system (also called Automated Bandwidth Allocation across Heterogeneous Networks). It allows allocating Layer 2 circuits with bandwidth allocatedwith allocated bandwidth.

In OpenNaaS source code, Autobahn action is defined by org.opennaas.extensions.bod.autobahn.AutobahnAction Java abstract class in bod.autobahn extension project. In the same project, in bod folder there are specific classes for each BoD resource capability action implementationsimplementation. Moreover, in the same folder, the BoD resource capability action set is defined by org.opennaas.extensions.bod.autobahn.bod.BoDActionSet Java class. Finally, in the same project, commands folder has specific implementations of each BoD resource capability command based on org.opennaas.extensions.bod.autobahn.commands.AutobahnCommand abstract Java class.

...

The Virtual Customer Premises Equipment resource(also called vCPE) is a CPE deployed following Network as a Service (NaaS) paradigm. More Information about vCP vCPE can be found in this paper.

...

The vCPE Builder capability allows building/destroying vCPE networks.

In OpenNaaS source code, vcPE vCPE Builder capability is defined by org.opennaas.extensions.vcpe.capability.builder.IVCPENetworkBuilderCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.vcpe.capability.builder.IVCPENetworkBuilderCapability in vcpe extension project.

...

The vCPE IP capability allows updating a set of IP addresses in a given vCPE network.

In OpenNaaS source code, vcPE vCPE IP capability is defined by org.opennaas.extensions.vcpe.capability.ip.IVCPEIPCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.vcpe.capability.ip.VCPEIPCapability in vcpe extension project.

...

The vCPE VRRP capability allows updating virtual VRRP IP addresses in a given vCPE network. Moreover, it allows changing VRRP priority in a given vCPE network

In OpenNaaS source code, vcPE vCPE VRRP capability is defined by org.opennaas.extensions.vcpe.capability.vrrp.IVCPEVRRPCapability Java interface which defines the capability itself and implemented by org.opennaas.extensions.vcpe.capability.vrrp.VCPEVRRPCapability in vcpe extension project.

...

A Web Services API allows to interact between user and OpenNaaS. It is developed using Apache CXF and dOSGI technologies and provides a REST API. Broadly, all the capability are registered services that publish their interfaces in this API. Moreover, Resource Manager and Protocol Manager register their interfaces too. Method registerService of org.opennaas.core.resources.capability.AbstractCapability Java abstract class shows how a capability interface is published as Web Service API using these technolgiesthese technologies.

Conclusion

Finally, OpenNaaS can be summarized in this module diagram:

...