Cloud computing has evolved from focusing only on how to construct, secure, manage, monitor, and utilize IaaS, PaaS, and SaaS clouds. As the paradigm matures, it is moving from a pure resource management paradigm to a data and resource management paradigm. (Read More)
SDDC is the next evolution in on-site data center technology. It has taken the knowledge gained from the server virtualization revolution and blended it with software-defined storage and networking to create a data center defined and managed by software running on invisible hardware.
Hybrid Cloud covers the technologies and operational processes, both technical and business, for deploying, consuming, and utilizing this paradigm.
Major areas of focus include barriers to adoption; progress on the part of vendors in removing those barriers; where the lines of responsibility are drawn between the cloud vendor and the customer for IaaS, PaaS, SaaS, and hybrid clouds; and management tools that are essential to deploying and managing the cloud, ensuring its security and the performance of applications.
This post on reddit appears to intimate that VMware is closing its API for virtual switches to all parties, including its long-standing networking partner Cisco. When I first read the post, I thought the move was a retrograde step by VMware and another veiled dig at its ecosystem. The post links to an official blog post on the VMware site stating that moving forward, VMware “will have a single virtual switch strategy that focuses on two sets of native virtual switch offerings – VMware vSphere® Standard Switch and vSphere Distributed Switch™ for VMware vSphere, and the Open virtual switch (OVS).”
From a numbers perspective, this makes sense, as about 99% of its customers are already using this single model of standard virtual switch and/or distributed virtual switch. It does fall into what research is stating. We at TVP Strategy applaud any attempt at reducing complexity, but we do find the fact that this announcement was hidden away in a blog post obtuse in the extreme.
There is a lot of talk of having enterprises build and operate IT infrastructure the same way hyperscalers do. AWS, Google, and Microsoft can build and operate cloud platforms that are very cost effective. The logic is that enterprise businesses can use the same techniques to build and operate their own efficient data centers. I believe that there is some merit in large enterprises trying to follow the hyperscalers’ methods and models. I also think that the nontechnical parts are far more important than the hardware and software selection. We come back to the three parts of a solution: people, process, and technology. Most enterprises look only at the technology part of hyperscale and miss the place where the real efficiency occurs. Hyperscalers are all about minimizing the people and optimizing the processes.
The title of this article is “In the Hybrid Cloud, Your Role Matters, but…,” and there is a big “but” there. How you use your role is what really matters. Whether you are a cloud, virtualization, or container administrator, evangelist, or architect, how you use your role makes or breaks the secure hybrid cloud. We have written a lot about technology, but it’s the people who really make the technology a win for the business. It is the processes you develop that make the difference. It is the roles you entrench that can hurt your prospects. So, how do we eliminate the “but”?
I really do not see hyperconverged infrastructure (HCI) as the final product for the leading vendors. It is more of a minimum viable product than a finished solution. Converging compute and storage has made infrastructure management easier, but there is still a whole lot of IT that is not easier. I sometimes tell people that their role is changing or going away after they deploy HCI. I usually tell them to move up the stack. Up the stack is closer to the business that employs them and uses the IT. Up the stack is getting closer to the applications and the data, and then to the users. The next move for HCI vendors is to move up that stack to make application development, deployment, and operation easier.
Citrix and Microsoft have each been gritting their teeth at VMware for years. Despite that, VMware has experienced longstanding success in the virtualization space. Clearly, neither Citrix nor Microsoft expected VMware to develop into such a powerhouse.
You may or may not be aware that I have just moved house, and, me being me, I have not done it by halves. My family and I up’d sticks to the other side of the world, and we landed in Perth—not Scotland, but Australia. Call it a cross-cloud migration; this obviously was fraught with difficulties and did not go as smoothly as planned. This has got me thinking about moving home in a cloud environment, whether from site to site, region to region, or cloud provider to cloud provider. In a perfect world, this should be as simple as live migration is today between like-minded virtualization hosts: VMware to VMware, Hyper-V to Hyper-V. The unfortunate truth is that this is not the case.