openSUSE admin

Let me add a few comments you won't like ;-)

I did the distribution upgrade on status2.o.o, and, well, there's a reason why I didn't also update status1.o.o - the Cachet version we use isn't compatible with the new PHP version :-(

Of course this shouldn't stop us from updating, but we'll have to upgrade Cachet before upgrading the distribution. (We can use status2.o.o to test it before breaking^Wupdating status1.o.o.)

I have to admit that I did a manual Cachet update a while ago (because I didn't realize we have it packaged as RPM), so maybe some cleanup can't hurt. Needless to say that I can help with that - just ping me ;-)

BTW: it looks like home:ecsos:monitoring/cachet is the most up-to-date Cachet package in OBS ("only" 6 months since the last update). (I didn't review it besides checking the version number and change dates.)

BTW2: AFAIK Cachet dropped RSS support upstream (because it was incomplete) some months ago, therefore please publish a note that the RSS feed will be discontinued, and that users can/should subscribe to the mail notifications instead. Ideally, this should be done some days before upgrading so that people have a chance to see it in their RSS reader.

cboltz wrote:

Of course this shouldn't stop us from updating, but we'll have to upgrade Cachet before upgrading the distribution. (We can use status2.o.o to test it before breaking^Wupdating status1.o.o.)

JFYI: I upgraded status2.opensuse.org to 15.1, including an upgrade of Cachet to the current 2.4 branch, today :-)
Of course: no package, only git + composer...

I dumped the database backup form status1 on status2 and did a

php artisan app:update

which brought everything up again.

FYI2: There is a script on root@status1:/root/bin/prepare_status2.sh
=> copies DB backups and current cert to status2
=> runs root@status2:/root/bin/restore_config.sh
==> this prepares (not actively switching apache) status2 to become status1

=> Idea: run /root/bin/prepare_status2.sh every day to have status2 following status1 with a day behind, so switching is still a manual task, but would just require a small config change in apache to use the status.opensuse.org certificates.

Where should such information go to?
Salt?

BTW2: AFAIK Cachet dropped RSS support upstream (because it was incomplete) some months ago, therefore please publish a note that the RSS feed will be discontinued, and that users can/should subscribe to the mail notifications instead. Ideally, this should be done some days before upgrading so that people have a chance to see it in their RSS reader.

Let's see how status2 behaves at the moment.

Thanks for doing the update, and sorry for the late answer!

While I moved nearly all the machine info to salt (pillar/id/), some things (typically additional documentation that goes beyond the machine info) are still in the wiki - ideally referenced in the documentation section of pillar/id/ ;-)

The information from comment #3 should be in the wiki (at least for now) - https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Statusopensuseorg still exists.

Unfortunately status{1,2}.o.o never made it into salt, AFAIK it doesn't even have salt-minion running :-( Long(er)-term, (some of?) the information should really be stored in salt, ideally in a file.managed for the prepare_status2.sh script ;-)

BTW: running this script daily to keep status2.o.o mostly in sync sounds like a good idea.

The information how to upgrade Cachet also sounds like something that should be stored in the wiki - unless you find a good way to automate it with salt of course ;-)

(Actually, the important point is to have this information stored somewhere[tm] - if we find a better place, moving it is easy.)

Regarding the no longer existing RSS feed - the perfect solution would be to configure Alias /rss /some/where/rss-gone.rss, which should be a small handmade RSS file with a single entry saying that the RSS feed is gone ;-)

I just added the following line to /etc/apache2/vhosts.d/Cachet.conf on status{1,2}.opensuse.org:

Alias /rss /srv/www/htdocs/cachet-rss-gone.xml

(and of course also created that file).

A quick test in Akregator shows that it works as expected - even if it's slightly confusing if a RSS feed tells you via RSS that RSS is no longer supported ;-)

That means that only updating https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Statusopensuseorg is left - Lars, since you are more familiar with the setup, I'd prefer if you would do that ;-)