[Info-vax] Desirable features for VMS

[Arne Vajhøj]

On 1/29/2024 6:21 PM, Hans Bachner wrote:
> Marc Van Dyck schrieb am 29.01.2024 um 16:36:
>> Dave Froble formulated the question :
>>> I'd just note that the OSs would be included as applications, so 
>>> re-starting them from where they were interrupted would be included 
>>> in the concept.  So, yeah, the monitor would be outside/over the OSs. 
>>> Perhaps something like happens with VMs.  Except VMs want to move the 
>>> activity to another system, not recover on the same system.
>>
>> Whatever the design and implementation, this would be a really useful
>> and marketable addition to the OpenVMS cluster concept. Clusters were
>> invented 40 years ago to implement horizontal scalability, because
>> vertical scalability was impossible, technically or financially. This
>> issue has mostly disappeared today, current hardware being able to
>> deliver any power we might want. Today's clusters are essentially
>> put in place for redundancy or disaster recovery purposes ; the next
>> logical step should be to provide this redundancy in a transparent way
>> to the system user.
>>
>> This should also be, as opposed to simple user niceties, something that
>> allows VSi to make money with.
> 
> Would OpenVMS Service Control cover your needs?
> 
> <https://vmssoftware.com/products/service-control/>
> 
> Service Control was originally developed by Wolfgang Burger at HP in 
> Vienna and later adopted by VSI. As far as I know it is (still) offered 
> as a service, not a product - but only VSI can tell.

This indeed seems like the app<--->VMS equivalent of
VM<--->ESXi.

You define an app to be running on one node in the cluster
and if something happens then the software start the app
on another node.

Like you define a VM to be running on one ESXi server in the
cluster and if something happens then VMWare spin up
the VM on another ESXi server.

Arne