HP VAN SDN Controller Administrator Guide v3

2.3.4.1.3 Application Zip File Content Criteria
The application zip file contains all of the component files that make up an OSGi application. In
order for the Application Manager to accept this as a valid application, certain criteria must be
met:
• Must contain one file with a “.descriptor” extension containing the key-value pairs described
above.
• Must contain at least one bundle (JAR), PAR, or WAR file.
• All application component files must be valid OSGi artifacts. That is, all JAR, PAR, and WAR
files must contain a manifest file with valid OSGi meta-data in it.
• The application must be self-contained, in that any third party dependency not already delivered
by the SDN controller must be included with the application. Note that in most cases you must
convert the third party JARs into OSGi bundles or embed the third party content in the
application. The details on how to accomplish this is beyond the scope of this manual and
you should consult the appropriate OSGi/Virgo reference documentation.
• By default, all JAR files must be signed by a trusted authority. Note that this can be disabled
in the controller. See chapter 3 “Running the Controller Without Jar-Signing Validation”.
• The application must be properly signed by an authority that is recognized by the SDN
controller.
A Virgo Plan file will be used if provided, but is not required. The Application Manager will only
deploy JAR, PAR, WAR, Plan, and “.properties” files. Other files in the application zip file are
ignored unless they are declared as an artifact in a Plan file.
2.3.4.1.4 Application State 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 1 Application States
DescriptionState
The application is running and servicing requests.ACTIVE
A new application has been downloaded to the controller and is ready to be installed.STAGED
A new version of an existing running application has been downloaded to the controller and the new
version is ready to be installed (upgrade/downgrade).
UPGRADE_STAGED
A transitive state indicating a new application is in the process of being installed.INSTALLING
A transitive state indicating the existing application is being stopped and a new version of the
application is being installed.
UPGRADING
A transitive state indicating a non-installed version of an application is being deleted from the controller.CANCELING
A transitive state indicating the application is in the process of being disabled (stopping).DISABLING
The application is disabled (stopped). A disabled application is not automatically started when the
controller restarted.
DISABLED
A transitive state indicating the application is being started.ENABLING
A transitive state indication an application is being stopped and completely removed from the controller.UNINSTALLING
The application is stopped and not servicing requests. An application can only be in this state when
it is stopped externally to the SDN controller (e.g. the virgo console).
RESOLVED
24 SDN Controller Console