A Package node represents a software package in your environment and is linked to all Host Nodes which contain it.
The following section describes the scenarios in which a Package is created, updated or destroyed. Package nodes are identical in behavior to Patch Nodes, see Patch Node.
Package nodes are created when they are first detected on a host. The generated key of a Package node consists of the following critical properties;
Package nodes are shared by all host nodes with the same package installed, the same architecture and that are running the same operating system.
A Package node is never updated because its key consists of the critical properties described above, and a change to any of these properties will result in a new Package node being created.
Package nodes are never removed.
The attributes and relationships of a Package node are described in the table below.
UI Name |
Description |
---|---|
Name |
Name. |
Vendor |
Package vendor. |
Version |
Package version. |
Epoch |
Package epoch. |
Revision |
Package revision. |
Operating System |
Operating System this Package is for. Derived from the os_type attribute of the Host Nodes it is installed on. |
Not displayed in UI |
Unique key. |
Architecture |
CPU type Package runs under. |
Description |
Package description. |
Solaris Full Name |
Full Solaris package name. |
The relationships of a Package node are described in the table below.
UI name |
Relationship |
Description |
---|---|---|
Hosts |
|
Hosts with this package. |
Not displayed in UI |
|
Software related in some way to this package. |
Not displayed in UI |
|
Software whose attributes have been partly or wholly determined from this package. |