Although they started to gain real momentum circa 2011 or so, modular and containerized data centers are still spreading their way across the industry. The two models share many similarities: ease of deployment, the ability to add more computing power more or less on demand, highly energy efficient operation, and some degree of prefabrication. Depending on the enterprise and IT needs, each has distinct advantages and disadvantages for data center design and infrastructure procurement.
Why go modular or containerized? Both models provide a standardized kit to scale out a data center piece by piece. A facility can be designed with an initial baseload for power and then built out with racks, cooling, and support equipment as needed. As more customers come on or the company grows larger, new servers and networking equipment are added to meet demand.
Today’s shortage of qualified IT workers is no secret. This is a part of the larger problem of the skills gap and the even larger STEM (Science Technology, Engineering, Math) crisis. One way in which Green House Data has started to combat this shortage is through a partnership with the University of Wyoming.
By now you’re likely familiar with PUE, or Power Usage Effectiveness, an industry standard measurement for the energy efficiency of a data center. Despite some claims that PUE is easily manipulated or not enough to judge full environmental impact, many data centers (including Green House Data) are using PUE to measure efficiency.
The Green Grid, a consortium of technology companies who aim to improve data center efficiency, has collaborated with industry groups around the world to develop several new metrics to measure carbon emissions and energy use in the data center, including GEC, ERF, CUE, and DCeP. What are these new measurements, and how does Green House Data stack up?
The answer depends on each individual deployment, but no matter the use case, admins will have to work with legacy hardware and consider new devices to support a virtual desktop initiative. From laptops to mobile to thin-client, there are plenty of end user platforms supported by VMware Horizon View.
Desktop as a Service (DaaS), which delivers virtual desktop infrastructure from a cloud provider, allows devices other than PCs to access fully featured desktops that are hosted in the data center. Because servers do all the heavy lifting, these client devices don’t need to be particularly powerful, enabling a new wave of BYOD confusion and excitement, as well as the opportunity for capital expense reduction through less expensive client devices.
There are several options for virtual desktop pools in Horizon View that will change how administrators manage desktops and how users interact with them. There are three main pool types and two assignment types to choose from.
Desktop Pool Types
Unless you’re working with Microsoft Terminal Services machines (in which case you’ll choose Terminal Services pools to allow terminal servers to be treated as Horizon desktops), either migrating or using them alongside Horizon desktops, you’ll select from automatic or manual desktop pools.