[Info-vax] VSI and Process Software announcement

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf
> Of Stephen Hoffman via Info-vax
> Sent: 25-Sep-16 3:20 PM
> To: info-vax at rbnsn.com
> Cc: Stephen Hoffman <seaohveh at hoffmanlabs.invalid>
> Subject: Re: [Info-vax] VSI and Process Software announcement
> 
> On 2016-09-24 20:41:29 +0000, Kerry Main said:
> >
> > No it does not.  How is remote management /profiling better
> than
> > secure console management?
> 
> Then you probably haven't used remote server management.
> What I've
> used works quite well, and the ability to detect and adopt a newly
> booted server is very handy.   For a larger data center, I'd prefer
> all
> that to be entirely automated.  Wire up the rack and power up
> the box and either the FIS or the console brings the box online to
> the provisioning servers.  OpenVMS isn't good at this, at all.
> OpenVMS is still stuck with serial console concepts and
> operations, and most of that chatter is a confusing and problem-
> masking mess and a complete waste of photons.
> 
> > As an example, in your ideal scenario, how do you archive
> console
> > messages, what someone has typed at the console before the
> OS is up
> > and do console HW event alerting?
> 
> I'd prefer to not have anybody on the console line, even for first
> boot.   I regularly work with servers that don't even have serial
> consoles.  Or DVDs, for that matter.
> 
> > I would be interested in hearing about what you are describe as
> > "already available and already working".
> 
> I'm already using what I'm describing here.   As are other folks.
> I'd
> like to be able to use and integrated with these capabilities on
> OpenVMS, and — since I'm looking at 2021 and beyond — I'd like
> better versions of what's available.
> 

In large shops, you want a common multi-platform console log strategy as part of the enterprise mgmt. strategy. You do not want individual OS's each with a separate or proprietary console log solution that will not fit into the enterprise strategy. 

In some cases for security reasons, you want the console log strategy to be totally separate from the host OS or network device so a OS/network priv'ed person cannot change the console log files that might be stored on the local server. For audit purposes, you may even want the console log files backed up as part of your data mgmt. strategy.

What Apple has does not fit this corporate requirement, hence my earlier question about what OS/HW server are you talking about?

Regards,

Kerry Main
Kerry dot main at starkgaming dot com