Making Old Skills Do New Work
Charon's orbit around our blog's pages

Linux distro not an issue for Charon installs

Linux KVMHP 3000 manager James Byrne has wondered about the kind of Linux used as a platform for Charon on the 3000. His heart's desire has been preserving the ongoing lifespan of MPE apps. For 3000 managers who haven't much budget left for their legacy server, though, here's a matter of spending additional money on a proprietary part of a virtualization solution, no matter how stable it is.

That's not an issue that will hold up Charon from doing its work to preserve applications, according to our Stromasys contact there.

There's an alliance between Linux and MPE as a result of Charon. It also says something about MPE/iX and its continuing value. Stromasys believes as much, investing in R&D that not even HP could get budgeted so it might give MPE/iX a way to boot on Intel's hardware. Extend the value of your apps with fresh hardware, the vendor says about Charon. To this day, even HP-UX won't jumpstart on Intel systems—unless they're Itanium servers. X86-Xeon won't work with HP's Unix. Now there's word of an impending PA-RISC emulation coming for HP-UX for Charon.

There's another issue worth considering in Byrne's organization, Hart & Lyne. The Canadian logistics company has Linux wired extensively into its datacenter. Already having been burned with an HP pullout from MPE, the solutions that go forward at Hart & Lyne must meet strict open source requirements to run in the datacenter. Nobody wants to be caught in a vendor-controlled blind alley again.

Byrne has resisted using something called KVM, and how genuine open source Linux needs to adhere to that product. Byrne described KVM as a Linux-kernel-based virtualization system, and as such it is therefore open source software.

Doug Smith, the HP 3000 Director of Business Development at Stromasys, said KVM isn't a part of the Charon installation set. "KVM is part of the Linux kernel, the part that allows Linux within itself to create virtual machines—kind of like a hypervisor. This is not utilized by our software."

KVM users have strong feelings about following hard-line open source licensing. Byrne's issue is that VMware's software—which isn't required for every Charon install, by the way—looks like it might be operating outside the General Public License utilized by many open source solutions. Managers like Byrne only feel safe inside the bounds of GPL. This hasn't troubled untold thousands of VMware customers.

Byrne says that "Charon-HPA runs on ESXi vmkernel, which VMware claims is not derived from Linux." Then he explains why that's a problem for his company's adoption of Charon.

VMware has been sued by Linux developers for violations of the GPLv2 with respect to the Linux kernel. It was alleged that VMware is in fact using GPL code but are not providing the source for their derived vmkernel, as is required by the terms of the GPLv2.

VMware is thus attempting to benefit from Open Source projects through misappropriation of public goods for private profit, and attempting to assert proprietary rights over the work of others. In short, they are not a company we wish to deal with, either directly or by proxy.

(Below, VMware's overview of the architecture of VMware's ESXi architecture.)

VMware ESXi architectureRegardless of what happens between VMware and those Linux developers, VMware doesn't have to be deployed as part of Charon HPA. VMware is a commonly used component, but it's not mandatory.

This alliance of Linux and MPE was well beyond a dream back in the days when the HP lab for MPE was closing. A fully open sourced OS acting as a cradle for a legacy OS that was first created in the proprietary era? Cats and dogs living together. It says something nice about the flexibility of Linux, a trait that's a byproduct of its open source development community.

The enduring value of MPE and the 3000's architecture is something Byrne sees clearly after decades of managing 3000s. "The real problem with the HP 3000 is that it just works," he said, "and so every other issue gets precedence above migration." Hardware keeps aging, though, an issue that can spark a change in how MPE gets hosted.