Everything you know about OpenStack is wrong

The future of IT infrastructure delivery?


Innovation not waiting for the old guard to die

The physicist Max Planck famously declared: "Science advances one funeral at a time". IT can often feel like this. In our own data centres incomprehensible design choices are retained and implemented because "that's how it's always been". Vendors become inflexible and begin to view all problems as things to be contorted and manipulated such that their existing portfolio will solve the problem.

For innovation to move faster than the passing of the torch from one generation to the next there needs to be a means to incorporate new solutions with minimal risk. The "plug and play" nature of OpenStack (mostly) works.

Any component can be swapped out and replaced with something else. Even seemingly major parts of OpenStack – such as Cinder – can be replaced if someone feels there's a good reason to do so. Neutron – the core Software Defined Networking (SDN) and Network Function Virtualization (NFV) component – is a common target. To be fair, SDN and NFV are common targets in all stacks vying for datacenter dominance.

Neutron has originally designed merely as a reference implementation, and the NFV portion isn't really all that good. At the OpenStack conference in Vancouver in May 2015 I met a number of companies that offered replacements for some or all of Neutron. (If VMworld should be renamed "StorageWorld", OpenStack was "SDNWorld".)

Don't feel that the NFV options in Neutron are good enough? License a commercial alternative and with a little bit of work your OpenStack deployment now uses Midokura instead. Easy peasy.

This has allowed innovation to find a home.

When I talked about storage previously, I talked about array vendors. These folks sell storage that's separate from compute and networking and simply plugs in to OpenStack in a manner not so very different from how it's worked for ages.

This is what most organisations are comfortable with, but other storage categories are emerging. Hyperconvergence is a great example, and you'll find vendors like VMware, Maxta, SimpliVity, Nutanix all offering up OpenStack compatibility. For many of the hyperconverged players there's more to their integration than just a Cinder driver, and that's really the point.

Encouraging innovation

By levelling the playing field OpenStack encourages innovation. If your storage array can be easily swapped for any other without affecting anything else in the stack then you have to start competing on merit. Either your prices have to be better than the next guy or you have to do something clever with that storage that the next guy can't do nearly so well.

And maybe making storage arrays isn't enough. Those pesky hyper-converged companies can do storage and compute together. Some are adding networking, better management tools, integration with public clouds, and more. Maybe there's some value in "doing one thing and doing it well", maybe that deep integration is appealing.

OpenStack is ready for the enterprise, the service provider, the SMB and everyone in between. That doesn't mean those organisations are ready for OpenStack. Working with OpenStack requires discarding everything we've learned about how infrastructure "should" work and relearning a new, more dynamic and interchangeable "should".

OpenStack is incomplete, and it always will be. OpenStack can never be finished because the companies that participate in its ecosystem will be constantly inventing new niches that require new standards and new means of integrating with the rest of the stack whilst preserving that "design out lock-in" mentality.

OpenStack is the attempt to provide a framework for IT infrastructure to interoperate without having to have such things be legislated. We can't let IT infrastructure compatibility be legislated.

Computers are not trains. We don't have hundreds of years to sort-of-but-not-quite get things standardised. IT evolves far faster that governments ever will and it has outgrown the increasingly bureaucratic standards bodies used thus far.

OpenStack is more than just a means to manage and maintain IT infrastructure. It's a grand experiment in changing how we deal with change. It is as much about balancing the needs of the many against the profit of the few as it is about lighting up a VM or providing a self-serve user interface.

OpenStack may fail. OpenStack may succeed. Either way, it will change how we manage change in our data centres forever. ®


Other stories you might like

  • DigitalOcean sets sail for serverless seas with Functions feature
    Might be something for those who find AWS, Azure, GCP overly complex

    DigitalOcean dipped its toes in the serverless seas Tuesday with the launch of a Functions service it's positioning as a developer-friendly alternative to Amazon Web Services Lambda, Microsoft Azure Functions, and Google Cloud Functions.

    The platform enables developers to deploy blocks or snippets of code without concern for the underlying infrastructure, hence the name serverless. However, according to DigitalOcean Chief Product Officer Gabe Monroy, most serverless platforms are challenging to use and require developers to rewrite their apps for the new architecture. The ultimate goal being to structure, or restructure, an application into bits of code that only run when events occur, without having to provision servers and stand up and leave running a full stack.

    "Competing solutions are not doing a great job at meeting developers where they are with workloads that are already running today," Monroy told The Register.

    Continue reading
  • Patch now: Zoom chat messages can infect PCs, Macs, phones with malware
    Google Project Zero blows lid off bug involving that old chestnut: XML parsing

    Zoom has fixed a security flaw in its video-conferencing software that a miscreant could exploit with chat messages to potentially execute malicious code on a victim's device.

    The bug, tracked as CVE-2022-22787, received a CVSS severity score of 5.9 out of 10, making it a medium-severity vulnerability. It affects Zoom Client for Meetings running on Android, iOS, Linux, macOS and Windows systems before version 5.10.0, and users should download the latest version of the software to protect against this arbitrary remote-code-execution vulnerability.

    The upshot is that someone who can send you chat messages could cause your vulnerable Zoom client app to install malicious code, such as malware and spyware, from an arbitrary server. Exploiting this is a bit involved, so crooks may not jump on it, but you should still update your app.

    Continue reading
  • Google says it would release its photorealistic DALL-E 2 rival – but this AI is too prejudiced for you to use
    It has this weird habit of drawing stereotyped White people, team admit

    DALL·E 2 may have to cede its throne as the most impressive image-generating AI to Google, which has revealed its own text-to-image model called Imagen.

    Like OpenAI's DALL·E 2, Google's system outputs images of stuff based on written prompts from users. Ask it for a vulture flying off with a laptop in its claws and you'll perhaps get just that, all generated on the fly.

    A quick glance at Imagen's website shows off some of the pictures it's created (and Google has carefully curated), such as a blue jay perched on a pile of macarons, a robot couple enjoying wine in front of the Eiffel Tower, or Imagen's own name sprouting from a book. According to the team, "human raters exceedingly prefer Imagen over all other models in both image-text alignment and image fidelity," but they would say that, wouldn't they.

    Continue reading

Biting the hand that feeds IT © 1998–2022