Administrator's Guide

Table 7 Application States (continued)
DescriptionState
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
Table 8 Error condition management
DescriptionState
If an error condition occurs when “staging” the application,
then it actually does not exist. (Error conditions in this stage
clean up after themselves.)
NEW > STAGEDNEW > UPGRADE-STAGED
If an OSGi deployment exception is encountered, the
application is moved to DISABLED if it fails to deploy as it
STAGED > ACTIVE
is. If a File I/O or URI exception is encountered, the
application remains in the installing state.
If an exception is encountered (OSGi deployment, File I/O,
or URI), rollback attempt is made, as listed below.
UPGRADE-STAGED > ACTIVE
(Depending on the original exception, not all options may
be possible).
1. Calls AppStore.deleteStore on the upgraded version of
the application.
2. Attempts to redeploy the original version of the
application.
If any exception is encountered, the application remains
in UNINSTALLING state
ANY STATE – UNINSTALLED
If an exception is encountered, remains in DISABLING
state.
ANY STATE – DISABLED
If an OSGi deployment exception is encountered, the
application is moved to the DISABLED state if it fails to
DISABLED > ENABLED
deploy as it is. If any other exception is encountered (file
I/O or URI), the application remains in the ENABLING
state.
To access the link to the OSGi artifacts for an application, click on the bullet for the application
in the web GUI. For example, clicking on the bullet for the “Path Diagnostics” application displays
the link to identity of the associated OSGi artifacts:
Figure 48 Links to OSGi artifacts associated with individual applications
100 Requirements for applications