HP VAN SDN Controller Administrator Guide
15
Table 1 Mandatory and Optional Table Attributes
Mandatory Attributes*
Optional Attributes
App_id
Description
App_name
Vendor
Version
Built_In
Support_team
Licensing-related
*Without these attributes the application deployment will fail.
It must contain at least one bundle or a par file. It can contain a plan file which will contain
information regarding the bundles in the application.
Application Criteria
Application components must be valid OSGi artifacts. (Includes having the proper
structure to be executed in an OSGi environment.)
The application must be self-contained, in that any third party dependency that is not
already delivered by the SDN controller must be included with the application.
The default behavior is to validate that the application jar files have been signed by a
trusted authority.
The application must be properly signed by an authority that is recognized by the SDN
controller.
Application States and OSGi Artifacts
In the default state, or when an application has been started, it is in the ACTIVE state and is
servicing requests. Application states include the following:
Table 2 Application States
ACTIVE
The application is running and servicing requests.
RESOLVED
The application is present, with all dependencies available, but is
stopped and not servicing requests.
STAGED
The application has been uploaded to the controller and can now
be installed.
STARTING
Intermediate state indicating the application is starting. Replaced by
ACTIVE when the application is fully enabled.
STOPPING
Intermediate state indicating the application is stopping. Replaced
by RESOLVED when the application has fully stopped.
INCONSISTENT
Some aspect of the selected application could not be started, but
other aspects are operating.
To view the OSGi artifacts, click on the application itself. For example, clicking on the Node
Manager application displays the identity of the associated OSGi artifacts: