[Info-vax] Distributed Applications, Hashgraph, Automation

[Stephen Hoffman]

On 2018-02-25 15:48:02 +0000, Kerry Main said:

>> 
>> -----Original Message-----
>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of
>> Stephen Hoffman via Info-vax
>> Sent: February 24, 2018 7:10 PM
>> To: info-vax at rbnsn.com
>> Cc: Stephen Hoffman <seaohveh at hoffmanlabs.invalid>
>> Subject: Re: [Info-vax] Distributed Applications, Hashgraph,
> Automation
>> 
>> On 2018-02-24 20:52:20 +0000, Kerry Main said:
>> 
>>> Never been much of an issue if its just the OS (modparams) and TCPIP 
>>> (tcpip$config).
>> 
>> No, it's not.   Go try it.  We'll wait.
>> 
> 
> If just changing the node name and the TCPIP address as part of a new 
> OS deployment (e.g. gold image deployment - what we are talking about 
> here), then this is not a big deal.
> 
> Done it many times.

Go try changing a host name of a previously-installed and non-trivial 
OpenVMS system.  Getting a domain-change request can be a real 
challenge, absent a strategy built on guests or containers.


>>> If Apps involved, then it does get a bit more tricky, but that is the 
>>> same on *NIX and Windows as well.
>> 
>> When are apps not involved in a deployment?
>> 
> 
> In most cases I have been involved with, you deploy apps after the OS.  
> Ideally, not on the system disk but we all know there are poorly 
> written Apps that expect to be on the system disk.
> 
> In fact using todays concepts, you deploy the OS image and "App 
> containers" separately on non-system disk partitions. Just need to 
> change a few start-up items.

Those other platforms are better about managing their host names than 
OpenVMS, and that rolling out servers with those platforms is easier 
than with OpenVMS, and that OpenVMS has no concept of isolating 
installed apps, nor does regenerating and testing monolithic masters 
work very well in environments that are getting updates as often as 
they're arriving now and into the future.  Among other details.

>>> Its certainly not a show stopper.
>> 
>> Given that host names and DNS forward and reverse translations are all 
>> involved with network security, don't bet on that.
> 
> The topic here is changing the server name and IP address of a new gold 
> image deployment.
> 
> Regardless of how the server is deployed, the network implications like 
> DNS AND FW rules still need to be addressed, but this also applies to 
> VMware Windows/Linux images using templates.
> 
> Btw, one idea that HP internal IT was talking about doing just before I 
> left in 2012 was deploying gold images based on a server based DHCP 
> strategy for each NIC with long TTL's e.g. 5 days.
> 
> Interesting idea, but I am not sure if they followed through on this or not.

So... was HP / HPE IT doing that with OpenVMS?



-- 
Pure Personal Opinion | HoffmanLabs LLC