Imunify adds several repositories to the system. In addition to the main repository, rollouts repos are added. What are these repositories, how do they work, and should they always be enabled?
- Any OS
- Any panel
All rollout repositories (except rollout-bypass) of Imunify360 should be enabled, but they are initially empty. When initiating a new update via roll-out, the right number of IP addresses (e.g. 3% of servers) is generated from those we already know that Imunify is installed there. The known combinations of operating systems, panels, and products are factored in when generating the list of IPs to which the rollout update will be available.
For the generated list of IP addresses in the rollout repositories, the new version of the packages becomes available, while the other servers do not have access to this update.
By default, the rollout-bypass repository remains disabled and is used by the roll-out script imunify-force-update.sh to get access to the update, bypassing the limitations of regular rollout repositories.
The gradual upgrade system is used for Imunify packages. New stable Imunify360 versions are scheduled for the gradual roll-out from our production repository and are available for all customers in about two weeks or less from the release.