[Orca-users] Re: Format change in 0.27b

[Blair Zajac]

Hi Bernard,

I sent this to you in a separate message, but it's probably useful for
everybody on the list.

The change was necessary as I made the naming for the RRD files and HTML
files more general.  This was to fix the problem if the same data was loaded
into a GAUGE and a DERIVE style RRD, there would be no way to distinguish
them in the RRD filename.  In fact, the names would collide.

There's no easy way to have a Perl script do the renaming as was did in
the previous upgrades, because now an additional piece of information is
included in the output filename, in this case the style of RRD file.

Does the development box run fine and are the plots consistent between the
two versions of Orca?

Best,
Blair

Bernard wrote:
> 
> Sorry about the length of this !
> I only run orca on one production machine and it collates percol files
> shared to it via nfs.
> 
> I did the upgrade you mention from .23 when we moved to .26 some time back
> and it worked very well so it had those name changes.
> 
> I did the test upgrade to 0.27 on an isolated test box.  The html and rrd
> files are not shared between production and development servers.
> The development box was setup to run 0.26 like the production box and given
> a number of percol files, only, to work with locally.
> Once orca was run and the plots were created on the devel box the next test
> step was to upgrade orca to 27.
> 
> I did this and the got the name changes I mentioned.
> When orca starts up it prints to stdout the message "making directory
> o_hostname" and it is made in the rrd/orcallator path.
> 
> Some changes from lib/Orca/RRDFile.pm :
> 
> 0.26b1 :
> ------snip
>    # Create the paths to the data directory.
>    my $rrd_dir = $config_options{rrd_dir};
>    if ($config_groups{$group_name}{sub_dir}) {
>      $rrd_dir .= "/$subgroup_name";
>      unless (-d $rrd_dir) {
>        warn "$0: making directory `$rrd_dir'.\n";
>        recursive_mkdir($rrd_dir);
>      }
>    }
>    my $rrd_filename = "$rrd_dir/$name.rrd";
> 
>    # Create the new object.
> -----snip
> 
> 0.27b1 :
> -----snip
>   # Create the path to the RRD directory and filename.
>    my $group_name = $config_groups_names[$group_index];
>    my $dir = "$config_global{rrd_dir}/" .
>              name_to_fsname("${group_name}_${subgroup_name}", 0);
>    unless (-d $dir) {
>      warn "$0: making directory `$dir'.\n";
>      recursive_mkdir($dir);
>    }
>    my $rrd_filename = "$dir/$data_expression.rrd";
> 
>    # Create the new object.
> -----snip
> 
> Hope this detail is helping explain.
> 
> Regards
> Bernard
> 
> At 12:44 PM 10/10/2001 -0700, you wrote:
> >One question, how many machines did you run Orca on before the upgrade and
> >after the upgrade?  This could be due to the problem of running orcallator.se
> >on only one machine and then running it on multiple systems while doing the
> >upgrade.
> >
> >I'm guessing you started off with an Orca version older than 0.26 because I
> >don't recall any renaming from 0.26 to 0.27.
> >
> >You might want to take a look at step 8 of the INSTALL file.  It describes
> >how to do an upgrade on filenames.
> >
> >Before you do this, make sure to make a backup copy of all your files just
> >in case something doesn't work right.
> >
> >If this upgrade step fails and if you have all of your percol-* files,
> >probably the easiest approach is to delete all of your RRD and HTML files
> >and rerun Orca.  This will make sure that everything is correct and up to
> >date.
> 
>                    Yahoo! Groups Sponsor
>                           [Image]
> 
>