User experience is the driving force behind an organization's digital transformation strategy. There is a direct relationship between customer satisfaction and the ability to acquire and retain new customers. Applications play center stage as most products and services are delivered through websites, mobile applications, or both. Microservices-based applications give businesses the ability to more granularly iterate and scale their applications based on customer feedback. This is directly tied to happier customers and increased revenue. As more businesses look to drive innovation using containers and microservices, they face some major headwinds, not least of which is standardizing on Kubernetes to accelerate their application modernization efforts.
VMworld 2019 made a glorious return to its more traditional location at the Moscone Center in San Francisco. This was a welcomed location change across the VMware community (except, perhaps, for the hotel room costs) after a three-year stint in steaming Las Vegas. The marketing tag line was “Make your mark…” and the general session theme was “Build, Run, Manage.” Kubernetes played center stage which isn’t a surprise considering this is the first VMworld since the Heptio acquisition was announced at VMworld Europe in 2018. In this blog post I’ll cover the major announcements and sprinkle in some honorable mentions that caught my eye. This is not an all-inclusive list of all the happenings at VMworld as that would be more of a blog series than a post. Feel free to reach out on our contact us page if you have questions about announcements you don’t see mentioned in here.
As the end of general support for both vSphere 5.5 and vSAN 5.5 approaches in this fall—many CIOs and IT directors are wondering if upgrading to the latest version of vSphere is a wise move beyond just the comfort of running a supported version of the product. After all—VMs are pretty standard fare for data centers today. What can a new version of vSphere really offer?
First of all—many people are hailing vSphere 6.5 as the most beneficial upgrade in years, and customers are moving it into production environments at an unprecedented rate. The impending end of general support only accounts for some of that production adoption—the remainder resides in the strengths and benefits of vSphere 6.5. In fact—vSphere 6.5 if the foundation of VMware’s hybrid cloud strategy moving forward—and is required for cross-cloud architectures. This fact alone may account for its rapid adoption, but let’s explore a bit further.
The move to hyper-converged infrastructures (HCI) is on!
However, many CIOs hit the brakes when it comes to knowing how to implement HCI initiatives and not wreck the IT budget. Certainly—one doesn’t want to replace all the existing equipment in the data center with converged infrastructure appliances all at once. Is there a way to use existing infrastructure and still take advantage of hyper-convergence and software-defined infrastructure while planning for equipment replacements down the road?
The simple answer is YES. And by building on existing infrastructure and leveraging commodity x86 equipment—CIOs can experience significant CapEx savings compared to hardware replacements. Certainly CIOs’ ears prick up when they hear figures of nearly 50% savings,1 but what does this mean for an IT department? Are there any other advantages to creating a virtual SAN now versus just waiting to implement HCI appliances as hardware refresh cycles come due?
It is critical that differences between software-defined storage (SDS) and storage virtualization be understood. While there is some overlap between the two—an ideal solution combines both SDS and storage virtualization for maximum benefit to the organization.
After months of running the vSphere 5.1 appliance in my lab, I decided to install the 5.5 appliance to see just how far this little gem has come. So, I downloaded and deployed the OVA, and moved onto initial configuration. After the initial configuration was completed, I decided to tweak some values in the interface. First and foremost - the DHCP configuration had to go. Followed by setting the host FQDN, which was strangely omitted from the initial configuration. This made running AD authentication a little difficult since AD integration requires that the appliance have an FQDN before it will accept the configuration.
Deploying pools can be done using the VMware View Administrator. The Add Pool wizard in the Administrator takes us through a series of steps which include user assignment, pool Identification, provisioning settings, advanced storage options etc. (refer to the figure below). In this article we will learn a different approach to deploying pools - using a powerCLI cmdlet.
In this article, we will discuss how to prepare Visual Studio to perform various VMware tasks. VMware PowerCLI is a Windows PowerShell interface for managing and automating various vSphere tasks. Using VMware PowerCLI cmdlets in Visual Studio we can create, customize, or manage vSphere inventory objects.