[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves

Wednesday, 10 January 2018

This is a multi-part message in MIME format...

------------=_1515569110-24537-319
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Barak Korren created OVIRT-1835:
-----------------------------------

             Summary: Create an automated update mechanism for slaves
                 Key: OVIRT-1835
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
             Project: oVirt - virtualization made easy
          Issue Type: Improvement
          Components: oVirt CI
            Reporter: Barak Korren
            Assignee: infra

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

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)

------------=_1515569110-24537-319
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Barak Korren created OVIRT-1835:</h3>
<pre>   Summary: Create an automated update mechanism for slaves
       Key: OVIRT-1835
       URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
   Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
  Reporter: Barak Korren
  Assignee: infra</pre>
<p>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.</p>
<p>Some things we'd like such a mechanism to provide:</p>
<ul><li><p>Require a minimal amount of manual work (Best case scenario
&ndash; nothing more then merging a repository update patch would be
needed).</p></li>
<li><p>Test updated slaves before putting them back to production
use</p></li>
<li><p>Allow rolling back failed updates</p></li></ul>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)</p>

------------=_1515569110-24537-319--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011