[Info-vax] Data Center Operations: DC/OS, Apache Mesos

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at info-vax.com] On Behalf Of
> Paul Sture via Info-vax
> Sent: 05-Jun-16 3:18 AM
> To: info-vax at info-vax.com
> Cc: Paul Sture <nospam at sture.ch>
> Subject: Re: [New Info-vax] Data Center Operations: DC/OS, Apache
> Mesos
> 
> On 2016-06-03, Stephen Hoffman <seaohveh at hoffmanlabs.invalid>
> wrote:
> >
> > There have been suggestions here in the comp.os.vms newsgroup that
> > OpenVMS head toward a distributed data center operating system,
> and
> > there have been a few discussions both here in comp.os.vms and at
> the
> > 2015 OpenVMS boot camp around adding support for containers on
> OpenVMS
> > (both as containers and in the guise of app stacking).
> 
> A very timely post, as I was building myself a test environment to
> go through the SaltStack tutorials when it arrived :-)  [1]
> 
> > If that sounds interesting, have a look at Mesoshere's DC/OS:
> > https://dcos.io/docs/1.7/overview/what-is-dcos/
> >
> > As dealing with all that is part of what Apache Mesos — the
> > underpinnings of DC/OS — provides.  http://mesos.apache.org
> 
> Thanks for the links.
> 
> > Through Mesos, DC/OS allows scheduling on local boxes through
> various
> > means, as well as on AWS and Azure services.
> >
> > FWIW, the "When you’re operating a datacenter, there are a set of
> > common operations that you do because you have to, not because you
> want
> > to. In a single computer environment, your operating system
> > automatically takes care of these things. When was the last time you
> > had to manually tell your laptop which processor core to run your
> > application on?  For those of you who responded with anything other
> > than “never”, there are some amazing computers at the Computer
> History
> > Museum that you might want to check out." line was good for a
> chuckle.
> 
> Just last year when I was mucking around with scientific stuff.  Before
> that, 1997 when pinning a CPU hog of a 16-bit app to a second processor
> so that workstation tasks could continue as normal on the primary
> processor (OK, a tower system rather than laptop...).
> 
> > No, I haven't seen a port of Mesos to OpenVMS, and I'd tend to expect
> > the down-standard C++ support on OpenVMS probably lacks a few
> features
> > necessary for the port.
> >
> > But maybe this gives some of you some idea of where parts of the
> > high-end and data center computing markets are already headed.
> 
> Yep.
> 
> [1] <https://saltstack.com/community/>
> 
> As an aside, the SaltStack tutorials suggest using Vagrant.  It's more
> than a year since I tried Vagrant but I found it bandwidth hungry to the
> point where that aspect, for me, outweighed the advertised advantages
> of
> the product.
> 
> Slight (Vagrant inspired, but Vagrant is far from the only guilty party
> here) rant follows.
> 
> I don't care how fast your internet connection is, there's still no
> point in repeatedly downloading the same stuff again and again.  If
> you've got the bandwidth to saturate the spinning rust disks I have
> here, you've probably got much faster I/O systems as well and you're in
> the same boat as I am.
> 

Looks interesting - had not seen this before. Thx. I would be interested
In how applicable or easy it is to manage a OpenVMS environment with 
This.

Note - my own semi-rant follows .. 

:-)

While Saltworks & Mestos and many other server mgmt. focused prods
who have come and gone over the last few decades have discovered is
that large companies are not looking just for one server mgmt. prod
that does everything they want. For many of these companies, they
already have commercial multi-platform products in place that augment 
what the base OS's provide. As an example HP Server Automation (SA)
(formerly one of the many companies HP bought)

http://www8.hp.com/h20195/V2/GetPDF.aspx/4AA4-6406ENW.pdf
http://www8.hp.com/ca/en/software-solutions/server-automation-software/

CA, IBM, BMC all have similar server mgmt. products that plug into Mgmt. 
frameworks very easily. (albeit with limited support for OpenVMS due to 
the years of neglect from DEC / Compaq / HP.

They want server mgmt. products that can plug into enterprise mgmt.
frameworks that manage reactive and synthetic events and alerts from 
not only servers, but also those from facilities, networks, storage, DB's 
and applications.

It is only by managing all of the different aspects of IT that can affect
an IT Service that a company can really become much more proactive
in the way it delivers and supports IT.

Not that I am pushing HP, but when evaluating new server mgmt. prods 
I would encourage looking at how this product would fit into a mgmt. 
Framework such as HP's OneView:
http://www8.hp.com/h20195/v2/GetDocument.aspx?docname=4AA5-3811ENW
(see fig 4 where Mesos and SaltStack would fit as a server resource mgr)

Given this is more open than anything I have seen from HPE, it makes me
wonder if someone external wrote this mgmt arch  for HPE, but that is 
pure 100% speculation on my part. 

Regards,

Kerry Main
Kerry dot main at starkgaming dot com