[Info-vax] IS everyone waiting?

[Phillip Helbig undress to reply]

In article <mailman.6.1476973052.7066.info-vax_rbnsn.com at rbnsn.com>,
"Kerry Main" <kemain.nospam at gmail.com> writes: 

> > the cluster where stuff like SYS$SYLOGIN, SYSUAF and so on can
> > reside.  This can be done, but folks roll their own.  One can
> > redefine SYS$SYSROOT, but this can be tricky.  Also, this would
> > give a fixed order for the translations, which might not be
> always
> > appropriate.)
> 
> Not sure what the point is. 
> 
> When any OpenVMS customer uses common system disks in a cluster,
> the recommendation is to setup a common non-system disk between
> the OS instances to share common files. That's a decades old best
> practice for the OpenVMS community. 
> 
> Reference sect 11.3:
> http://h41379.www4.hpe.com/doc/82final/6318/6318pro_020.html 

Yes, been doing it for years, decades even.

> While automating this might seem like a benefit, many Cust's
> would also argue that because of all the various custom config's,
> this is better left to the local SysAdmin.

Not completely automating it, but rather making upgrades easier.  In 
other words, allow even a "fresh" upgrade but keep all customizations in 
place, or at least offer some way of automatically determining what 
needs to be updated.

> Setting up a OpenVMS cluster has lots of benefits, but like every
> OS platform, OpenVMS clusters do require more planning and work
> to setup and configure than an individual system.

Right, and it's even fun, but there are some things which could be 
changed.  For example, disks are now cheap, so just install everything 
without asking, don't compress HELP libraries, and so on.