qa host firmware updates

[Tim Flink]

I mentioned this a while ago but just recently figured out the
process details and got the permissions I needed to complete the work.

Our hosts are getting pretty old and most of them haven't seen a
firmware update since they were installed 3-4 years ago. This hasn't
been a problem for most of the hosts but one of them (qa06) has always
been a special case due to how its' disk shows up.

The firmware was updated on qa06 in January and since we couldn't get
the same version that's on the rest of the qa hosts, we ended up using
the newest available versions.

I'd like to get all our hosts at the same firmware versions but the
process of doing that update is a bit painful and can't be done while
the host is in use (requires re-imaging and several reboots -
thankfully all the hosts are ansible controlled and the recovery is
mostly a matter of waiting for the playbooks to finish) so I'm not
planning to do them all at the same time.

While we still have some spare capacity (ie, before we deploy
taskotron), I'm planning to update the firmware on each of the qa
machines by taking them down one at a time, doing the updates and
reconfiguring them for autoqa, autoqa-stg or beaker.

The only place where this will cause a disruption is in beaker, since
we only have one host allocated to that. Both autoqa and autoqa-stg
have multiple hosts allocated so while they might slow down a bit,
they'll both continue to function during the updates.

Since nobody is using beaker at the moment, I'm going to tackle that
host next. It should be back up by the end of the day. I'll update the
thread when I've finished all the upgrades.

Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/qa-devel/attachments/20140404/c6a2ffbc/attachment.sig>