At this year’s OpenStack Summit in Austin, Texas, the message was clear. OpenStack needs to pivot from a science experiment to a production system. Even though this is happening, it has been happening slowly. Some would argue that it has been achieved for the likes of PayPal and other extremely large institutions, such as AT&T. However, running, configuring, and installing OpenStack still takes more knowledge than the average enterprise system administrator has available to them. The new Certified OpenStack Administrator certification is a way to exhibit a level of competence for the age of the new OpenStack: the production-ready OpenStack.
Articles Tagged with OpenStack
In the industry, OpenStack is seen as very hard to implement. Considering this, I began to think that most people who deploy OpenStack try to bite off too a large chunk of OpenStack at one go, to implement it all instead of just what they need. OpenStack is a cloud management platform, not the hypervisor, so perhaps we can take some lessons from how we installed VMware products when we just started out. We still implement things using the same patterns for vSphere. We should revisit OpenStack with this history in mind.
How much private cloud do you really need? A private cloud is all about the IT department getting out of the way of its internal customers, enabling business units and individual developers to provision their own VMs and get on with doing their jobs. But building and operating a private cloud is a complex, and therefore expensive, task. There needs to be a large payoff before there is a real business benefit. Some businesses don’t really need a private cloud platform. Often, their business processes will prevent real self-service on their private cloud. For these organizations, there may be simpler ways to achieve their desired business outcomes.
Building a private cloud was a high priority for a number of organizations in 2014. This priority carried over into 2015 because it is hard to execute. For many organizations, it has carried over again into 2016. Of course, the definition of a private cloud has changed in that time, too. Some organizations are happy simply to have consistent VMs deployed in response to a helpdesk ticket. Other organizations aspire to have the AWS in their own datacenter. One significant trend is the use of public cloud services to manage on-premises private clouds. The other trend is OpenStack in the enterprise, rather than only in academia and hyperscale where it started.
On the twenty-first of October, HP announced that it is shutting down its Helion Public Cloud, which it built to compete head-to-head with AWS, GCS, and Azure. According to HP Cloud executive Bill Hilf, it is doing so to concentrate on helping its “customers to build and run the best cloud environment suited to their needs.”
Welcome to The Virtualization Practice’s week-long coverage of VMworld US 2015. Tune in all week for our daily recap of the major announcements and highlights from the world’s premier virtualization and cloud conference.
With all the forward-looking business out of the way (see the Day 1, Day 2, and Day 3 recaps), VMworld took a breath yesterday and focused on other parts of the ecosystem. The first annual Developer Day was held as part of the VMworld DevOps program track, and it included a Hackathon where coders and non-coders could compete for prizes. Non-coders had a series of increasingly difficult challenges to complete. Coders worked to create the most useful, creative, and complex tools and services on vCloud Air, judged at the end of the day, and were awarded prizes like a guitar signed by Alabama Shakes and the Neon Trees, the VMworld Party bands.