Update¶
Operations Center acts as the update hub for IncusOS servers. IncusOS servers contact Operations Center to look for newer software and download updates if available. This allows deployments to easily operate in an air gaped environment by only having one place to push new update files to.
Operations Center handles the central IncusOS update management. In this role, Operations Center keeps the relevant updates available locally.
Operations Center has a single source configured in the config file. If Operations Center does have internet access, it checks the registered update source on a recurring schedule (by default hourly) for new updates and downloads them to the local cache.
It is also possible to operate Operations Center in air gapped environments, where the updates are provided manually by the administrators.
Filtering¶
The updates, which should be downloaded and be made available for the managed IncusOS instances, can be filtered based on various criteria.
See filtering for more information on the syntax of the filtering expression.
Update level filters¶
Update level filters are configured using the filter_expression config key
in the Update settings.
They allow filtering of updates based on their metadata.
Property |
Description |
Example |
|---|---|---|
|
Update channels, the update is part of |
|
|
Source the update originates from |
|
|
Timestamp when the update has been published |
|
|
Severity of the update |
|
|
Unique identifier of the update |
|
|
Version of the update |
|
The following properties are available during filtering as well, but they are not really useful as filter criteria and are only listed here for completeness.
changelog: Content of the changelogupdate_status: state from Operations Center point of view, if the update isreadyorpending; when the filtering is applied, the updates are neverreadyurl: Source URL of the update
File level filters¶
File level filters are configured using the file_filter_expression config key
in the Update settings.
They allow filtering of update files based on their metadata.
Property |
Description |
Example |
|---|---|---|
|
Architecture the update file applies to |
|
|
Component of the update file |
|
|
Name of the update file |
|
|
SHA256 checksum of the update file |
|
|
Size of the update file in bytes |
|
|
Type of the update file |
|