eBooks/eGuides

End User Computing - A Hybrid Multicloud Approach

Issue link: https://insights.oneneck.com/i/1437687

Contents of this Issue

Navigation

Page 13 of 36

14 A building block is a predefined set of infrastructure that maps to a specific amount of resources or number of users. This approach is one of the best ways to approach infrastructure design with end user computing. By using this approach, one can develop an architecture that offers a predictable cost, performance, and capacity scaling model. When determining building block size, choose what increments you need to scale users and how the infrastructure selection can accommodate the choices. For instance, one may want to scale users in increments of 50 to 100 users, but the infrastructure choice does not scale in that small of increments well. This may force the design to scale in larger increments of 500 or 1,000 users. If the infrastructure choice scales in large blocks, one can choose to scale to mesh with that or just accept the fact that the infrastructure costs will not scale in the same way the user deployment blocks will. This simply means that the organization would be purchasing infrastructure in blocks of 1,000 users and only be deploying in groups of 50 to 100 users. It does make the costs of the virtual desktops or user sessions look expensive when purchasing the large block to deploy a smaller amount of users. This evens out if the organization does deploy all of the planned users. Building block style architectures are helpful in any design project, but EUC deployments always have common chunks of users and use cases that have similar characteristics and are deployed in groups. To continue with the example of a 100 user block size, by understanding the resource requirements of 100 users, one can ensure that the block of infrastructure is able to provide everything those users require. If each user requires 15 IOPS at steady state and 30GB of storage capacity, along with 2GB of memory, and 200MHZ of CPU, the architect then knows that the building blocks must provide 1500 IOPS, 3TB of capacity, 200GB of memory, and 20GHZ of CPU. The architect can design the building blocks to contain additional resources, but none of them can be below those values. We also want to avoid the waste of including too much extra in each block that we can't utilize. Building Blocks

Articles in this issue

Archives of this issue

view archives of eBooks/eGuides - End User Computing - A Hybrid Multicloud Approach