The Virtualization Practice is a collection of technologists. We concentrate on virtualization and cloud technologies and companies. We look at products, services, methodologies, and mindsets. Below are our findings and thoughts on all things virtual and cloud. We invite you to add your thoughts and comments on each article.
If your product, organization, or company works in, fixes problems within, or enables virtual and cloud environments, we are interested in hearing from you. Our goal is to educate the market about what technologies are available for virtual and cloud environments. We cover all aspects of cloud, from Transformation & Agility to Security, including stops along the way to discuss SDDC & Hybrid Cloud, IT as a Service, Data Protection, and End User Computing.
In addition, we take this information and create reference architectures for use by other technologists. These architectures suggest placement of various products within the environment to provide functional and secure hybrid clouds. Our architectures consider placement of storage, physical and virtual servers, security, end user computing, and networks within data centers and hybrid clouds.
We also review licensing related to the hypervisors on the market, including Hyper-V, Xen, KVM, vSphere, and several derivative works. Licensing costs associated with running virtualized data within your data center are examined as well.
Although virtualization and cloud environments have been around for many years, we still find that many people do not know what products are available. We are here to solve that problem by providing education and a look at what the future may hold. We do this by taking briefings, talking with end users, administrators, and C-levels, researching various topics, and concentrating on thought leadership in the areas of virtualization and cloud technologies and services. This allows us to help our sponsors by determining how their products fit into virtual and cloud environments. We assist our sponsors by getting the word out via our newsletter, social media, and this site.
Throughout all the years I have been working in information technology, security has been an area that engineers have striven to improve. As a result, we have make our environments as secure as possible. We have always looked to make the security of our systems stronger. Security has evolved over time. One example of this evolution is the concept of password management. IT professionals have helped drive the change from simple passwords to more secure passphrases to two-factor authentication added as another layer of security.
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.
Over the last couple of weeks, I have been thinking about costs relating to a building a new virtualization-based data center. “What?” I hear you say. “Everywhere is virtualized—there is no such thing as a greenfield site anymore!” I would have said that myself, but in the last month I have come across three, one of which is a company worth over a billion pounds.
On Monday, LANDESK announced its plans to acquire AppSense. LANDESK is a well-known, stable technology company based in Utah, whereas AppSense has had several tumultuous years as it has sought to define its niche within the virtualization market. This pairing appears to be a good move for both organizations, with AppSense likely being the greater beneficiary.
IT as a Service (ITaaS) is changing nearly every day. In the past, it was mainly about automating deployment through the contents of a service catalog. Today, it has grown to include IT operations analytics (ITOA). What matters isn’t whether we can select an application from a service catalog, but rather how we monitor and react to issues during the lifetime of the application. With containers, which are all about automation, ITaaS has to change not only to include ITOA, but also to react to the results of the analytics.