Previous Topic: Connections EntityNext Topic: Overview


Package Descriptor Syntax

This section contains the following topics:

Overview

Package Sub-entity

'class' Sub-entity

'volume' Sub-entity

'protocol' Sub-entity

'resources' Sub-entity

The package descriptor is a table of contents file that defines the contents of an application or of a component library (a catalog). The package descriptor also contains references to volume images that are outside the application's root directory. The application is installed on the grid controller, while the volumes may reside on any of the grid's servers. For applications, it also contains the configuration settings component of the application.

Following are the different types of package descriptors:

application

ToC for an entire application, contains the application's configuration data and references to other package descriptors

catalog

ToC for a catalog (library of components), contains a list of components

recycle, clipboard

ToC for work directories used by the GUI tools. They have a format similar to the catalog package descriptor.

The package descriptor contains one entity of type package.

An application package descriptor may also contain an entity of type 'assembly', with the same structure as the one found in an assembly descriptor, except that it cannot have terminals and properties on the boundary. It is used as the topmost component of the application containing the property settings for the application itself with a single subordinate that is the application's main assembly.

The 'package' entity has the following attributes:

type=

one of: application, catalog, volcache (obsolete), recycle or clipboard.

description=

A human-readable description of the package's contents.

uid=

An ID assigned to the application at the time it was installed. This ID is an integer value in the range 1..254 and is unique among the applications installed on the same cluster of servers.

template=

0/1 designating whether the application is a template. Supported in CA AppLogic® 1.2.5

user1=

Free-form user-defined text intended for specifying billing code.

user2=

Free-form user-defined text intended for specifying billing code.

pref_virt_mode=

This is a string that should be one of the following supported VMM modes in CA AppLogic® 3.0:

  • xen_pv
  • xen_hvm
  • vmware

If present, it instructs CA AppLogic® to use the preferred VMM for all of the application's components that claim to support it (in their 'virtualization/modes=... setting), provided that there is available computing resource (CPU/memory) running under that VMM. The pref_virt_mode attribute DOES NOT support the legacy VMM names 'hvm' and 'paravirt'.

The 'package' entity has the following sub-entities, described in detail below:

package

a reference to another package, which is part of the same application. This is used only if type=application .

class

defines a component class, including the name of the component descriptor file.

volume

a reference to a volume, defining an application-specific data volume. This is used only in application packages

protocol

defines a protocol filter

resources

defines the set of servers on which the application can be scheduled to run. Optionally, resources define the numeric ranges from which IP addresses can be assigned to the components of the application. This is used only in application package descriptors.