[Orca-users] Re: Retired hosts

[Andy Waddington]

> Date: Mon, 26 Jan 2004 16:20:19 -0700
> From: Jason.Santos at aps.com
> Subject: [Orca-users] Retired hosts
> To: orca-users at orcaware.com
> Message-ID: <EB589D6F2AF5534CAB3AAF26B9836B40E2711E at ntm007.apsc.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello,
>
> Just was wondering if anyone had an elegant solution to removing retired
> hosts from the main Orca web page, ideally migrating them to a separate
> section or another web page entirely.  Alternatively, would it be easier
> to mark retired hosts with a special character after their names?
>
> Thanks!
>
> -- 

Interesting topic.  This is our solution...

When we have a host that is retired or dropped from reporting we deal with
the three pieces separately:

The raw data is compressed and moved offline - in fact after each day's data
is processed and the rrds are updated the raw data is already unnecessary
(except for possibly having to rebuild from scratch) so we compress and
archive every file for every server every day by default.  Our set up is a
daily update of the data for each host using ftp or scp and "orca -o" rather
than running everything continuously so this works well.

Dealing with the rrds depends on the situation.  Normally we have no use for
them so they are deleted.  If necessary we could always rebuild the rrds
from the raw data, but if we know that there is a good chance a host will be
reused in the future we might keep the rrds offline with the raw data
temporarily.

The html we want to keep available but separate from the hosts that still
update daily.  To do this we mv the host's png directory and the
*_{host}-*.html under the html_dir to the archive location.  Rather than
keep all the html and pngs the next step is normally to use an html to pdf
tool on o_{host}-all.html to build a single standalone snapshot of the Orca
output that can be downloaded when needed.


Since the location of the html_dir, rrd_dir and find_files for each host are
well defined it is possible to script most of the above... but we haven't
gone that far yet since someone with an itchy trigger finger who deletes
rrds that are still in use would create an unnecessarily big problem.


Are there any other solutions out there?

Andy