As tiburon progresses …

We are now booting: Redhat 6.1, Centos 6.0, Ubuntu 11.04, and others (including VMs!) via tiburon. Completely painless for compute and storage nodes. This is letting us get to the next phase: Application Specific Nodes (or “appliances on demand” in more common language).

Basic idea is, spend zero … identically zero time on your expensive private/public cluster/cloud/grid/yadda yadda doing an installation. Seriously, you should not be paying cloud providers for this, and if you are, this is a problem. We will be building tools (better ones than we have now) to automate the heck out of building images/appliances/… And apart from Windows, we think we can do this with most flavors of Linux, possibly some of BSD (and darn it, would love to do this with OSX … hint hint hint).

Same image that booted the 1TB ram server also boots our tiny 16 GB compute node, our 4GB VM, …

Yeah, that is utility. Once its configured, the hardest thing for this is boot time.

Add in some of our gui/cli goodness (also being updated/adapted), and yeah this starts looking downright interesting.

Viewed 38292 times by 4755 viewers


4 thoughts on “As tiburon progresses …

  1. @Damien:

    Not yet … though technically, there is no reason its not possible. Windows doesn’t quite have the same conception of operating from PXE boot as does Linux/Unix. We can boot images via a SAN or iSCSI, but the auto image creation is the hard part (and from looking at it in the past, this is one of many places where windows falls down badly).

    We will look at this, and see if we can give a helping hand. A shared registry would be … a unmitigated disaster … so we need to see what we can separate and what we can keep in common. Moreover, as windows likes to have all its apps configure registry entries, this means you lose much of the benefit of this sort of operation.

    The other issue is licensing and license management. Windows HPC cluster (in part) handles this for you. I rather doubt Microsoft would look kindly upon someone attempting to fulfill the same void with a non-sanctioned product. If I am wrong (and I know Microsofties read this blog), please contact me offline. We are completely agnostic on the node OS side.

Comments are closed.