Create an automated update mechanism for slaves

Description

While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by 'global-setup.sh'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.

Some things we'd like such a mechanism to provide:

  • Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed).

  • Test updated slaves before putting them back to production use

  • Allow rolling back failed updates

Activity

Show:

Barak Korren December 15, 2018 at 4:53 PM

Even if slaves are ephemeral, you need an update mecahnism for the base
image. Even more so then in non-ephemeral ones...

בתאריך שבת, 15 בדצמ׳ 2018, 17:25, מאת Eyal Edri (oVirt JIRA) <

Eyal Edri December 15, 2018 at 3:24 PM

I'm not sure we need to invest in this if the aim is to more to ephemeral slaves, either containers or VMs.

Details

Assignee

Reporter

Components

Priority

Created January 10, 2018 at 7:25 AM
Updated December 15, 2018 at 4:53 PM