In my last article, I started a discussion about automation and the tools of the trade for automation and orchestration. The post focused on Microsoft PowerShell as one side of the automation coin—one of the primary tools of the trade when working within Microsoft, VMware, and Citrix virtualization and orchestration solutions. Why PowerShell? Quite simply, it’s a powerful platform that has a robust community supporting it, and companies outside of Microsoft have invested a great deal of time and development to integrate PowerShell into their main administration and management platforms for working with VMware vSphere and Citrix Xen. So, if PowerShell is one side of the automation tools coin, what’s on the flip side?
IT as a Service
IT as a Service (ITaaS) covers private clouds, hybrid clouds, and on-premises clouds, as well as cloud management, including performance management offerings used to create and manage these entities. Consider this IT consumption as a utility. (Read More)
This topic explores Infrastructure as a Service (IaaS) private and hybrid cloud offerings, Platform as a Service (PaaS) private and hybrid cloud offerings, and Software as a Service (SaaS). It also investigates emerging areas such as Desktop as a Service (DaaS), Storage as a Service, and Applications as a Service.
The key areas covered include enterprise applications and use cases that are appropriate for private and hybrid clouds, and how consumers and vendors should select cloud management offerings they will use to manage the various types of cloud services and the journey to the cloud: from A to Z and all points between.
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.
As we have stated before on The Virtualization Practice, Oracle has woken up to the cloud in a very large way. Acquisitions such as Ravello Systems, StackEngine, and Datalogix have the potential to turn this leviathan into a dominant cloud player.
Oracle has started to move from a position of catch-up, though acquisitions, into an active development phase. Recently, CEO Safra Catz met with India’s Prime Minister, Shri Narendra Modi, to announce a series of investments and continued expansion into India. As one of these investments, Oracle opened an incubation center, the Oracle Startup Cloud Accelerator, on April 8 in Bengaluru. The center was inaugurated by President of Product Development Thomas Kurian. The company has already stated that several more centers will be launched later in Chennai, Gurgaon, Hyderabad, Mumbai, Noida, Pune, Trivandrum, and Vijayawada. Oracle’s Sanket Atal, group vice president of development, will lead the initiative.
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.
Recently, a number of marketing campaigns have seemed to be inventing complexity to try to give products the appearance of having some sort of competitive advantage. The invented complexity involves real-world items that many folks just do not use, or even care about, in order to make products look like something different. We have spoken about in-kernel vs. VSA in the past, but now we are seeing invented complexity within the mainstream storage world.
Every day, IT professionals live and breathe applications, yet our focus for operational tools is a single container, virtual machine, database, etc. How do these items map to the application in use? Even the monolithic-looking applications of yesterday were actually made up of services. Those services will be reborn as microservices within the applications of tomorrow. How do we make this transition? Is it possible with a container as a service model? Or should we scratch the past and start over?