On Jan 21, 2018, at 10:54, Tom Dawson <[email protected]> wrote:
> After following the above guide, how will our new installations handle
> updates as-and-when they are released by Paravel?
>
> a) will the machines automatically upgrade to new versions of Rivendell?
No. By default, *nothing* will ever update itself automatically. CentOS does
provide an ‘opt-in' mechanism for enabling ‘automatic’ updates, but I strongly
dis-recommend its use. Rivendell is designed for continual, 24/7 use; you
really don’t want updates occurring unless you’ve specifically initiated that
action and are prepared to deal with the resultant possible service
interruption.
> c) how do we allow/approve an update when we're ready?
>
> Is the last step of removing 'rivendell-install' the key to this, or is there
> something else to be aware of?
>
> Additionally, what's the recommended best practice for CentOS itself, do we
> remove update sources, or leave them intact but just avoid running 'yum
> update' ?
I like to break updates down into two basic classes:
1) Rivendell
2) Everything else —i.e. the operating system (CentOS)
I always try to do these two classes *separately* — that way, if something
unexpected happens (rare, but not unheard-of), troubleshooting tends to be much
simpler.
To update *just* Rivendell, do (as root):
yum update rivendell
The system will print a bunch of stuff, and then finally (if there is an update
available) present a list of two packages with the version number, called
‘rivendell’ and ‘rivendell-base’. Enter ‘Y’ to go ahead and apply the update.
(Once in a great while, there may be additional ‘dependent’ packages pulled in
in addition to these two). If there is no update available —i.e. you’re already
at the current release version — the command will do nothing, but simply return
with ‘No packages marked for update’ and then exit.
To update everything else, while leaving Rivendell pinned at the currently
installed version, do (as root):
yum --disablerepo=Paravel-Broadcast update
Depending on what the OS update entails (kernel or glibc packages), you may
need a full reboot following it. Rivendell-only updates generally do *not*
require reboots (though they will require that any open Rivendell modules be
restarted).
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| A room without books is like a body without a soul. |
| -- Cicero |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
