The MetalSoft enables users to keep track of individual component’s firmware and allows the mass upgrade using upgrade policies.
Upgrading a server’s individual components¶
At register time the system will check for the firmware of the various components of the server.
A separate, daily request is done to check for available upgrades using the server’s upgrade site (where available). Click “Check for available upgrades” to force a check.
Available upgrades will appear in the component’s list.
Firmware upgrade individual component
Component upgrades are typically done in one go to avoid rebooting the server multiple times. Check the components that need to be upgraded and click “Upgrade selected components to latest” to trigger a mass upgrade which will reboot the server.
If the server is allocated the user and all it’s delegates will be notified on email and the term for the upgrade will be set 24h from the moment of the button press.
Performing mass firmware upgrades¶
To perform mass upgrades of firmware components firmware upgrade policies must be used.
These define which components get upgrades and which not. Every night the check for new upgrades gets executed and the components with available upgrades are filtered through all the policies.
Firmware upgrade policy
The rules of a firmware upgrade policies are all combined using “and” and can match one or more of the following fields:
- Server Component Type
- Server Component Firmware Version
- Datacenter name
- Server Vendor
- Server Tags
- Server ID
There are two “Actions” for a firmware upgrade rule;
- Accept - This will trigger an immediate upgrade with user notification.
- Accept with confirmation - This will trigger a notification to be sent to the user via email which the user can use to postpone or cancel the upgrade
- Deny - This will block the upgrade of the respective component. Deny types are evaluated before accept ones. Thus they can be used to create exceptions.