Package node
A Package node represents a software package in your environment and is linked to all Host nodes which contain it.
Package node lifecycle
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.
Creation
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;
- name
- version
- revision
- epoch
- architecture (for example: i386, x86_64)
- OS information.
Package nodes are shared by all host nodes with the same package installed, the same architecture and that are running the same OS.
Update
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.
Removal
To remove a Package node manually, find the necessary Package node, select it in the list and pick Destroy from the Actions list.
Package node attributes
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. Only populated on Linux. |
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. |
Package node relationships
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. |
Comments
Log in or register to comment.