the pre-order article, perhaps many students will reflect that in the daily project, very few can have the opportunity to build a more than a table of the environment, this for me what role?
In fact, the size of the project is from small to large, in the overall design logic is exactly the same.
For example, in the Infrastructure section, we can use 2 sets of infrastructure to support the size of the site .
The density of desktop hosting depends on the load of your users ' usage scenarios to determine your density.
It is also necessary to consider the The number of cores in the CPU, the more in theory, the more users can support.
In addition, for example: DDC,StoreFront, High availability of SQL must not be ignored, to achieve at least two-machine redundancy.
At the same time, storage planning is also a top priority in desktop projects, but many times it takes a lot of money to buy storage without actually using the storage.
The reason is that in a desktop virtualization project, unless you consider DR, otherwise he has only the following two basic requirements for storage:
Enough space
IOPS enough
It's easy to say, but it's not easy to do. One of the most easily overlooked is the user data piece. Because people generally will be the desktop hosting, infrastructure resources to give a full, and the user this block is often ignored.
In fact, in a desktop project, the reasonable plan is to put the user data in a unified storage in the shared class store, to ensure that any device, desktop access to obtain data.
and user data is more used in the form of network disk mount, then it involves two pieces of content:
User's Roaming profile
User Network disk data
either way, he needs a Microsoft-based CIFS/SMB protocol to support, and that's why in desktop projects, users are often advised to use NAS class storage.
if, as in this example, you use the SAN Storage You need to deploy stand-alone Windows server as a file server.
then back to storage planning this piece, with the server, storage technology upgrade, now for The io pressure of a VM can be digested by a variety of new technologies in fact, and the IO pressure is virtually negligible after reasonable planning. This is why, in this case, there is very little planning for the IO of any one type of VM , because its io is too small.
and in view of the user data, he is due to use The CIFS/SMB protocol is inherently unable to use these storage-level optimizations, and because Roaming profile needs to be read from storage to the virtual machine every time a user opens his or her desktop, if the storage, network performance is not good, The direct result is that the user will feel particularly slow to boot.
While the network disk data will not be read every time, but if the user's individual file is particularly large, the result may be slow reading.
so at this stage, most of the time we will be like solid-state drive resources such as priority to the user Data section, followed by the virtual machine. at the same time, at the network level, it is very important to provide enough bandwidth to complete the interaction of user data/profile. because it boils down to the end, we want to provide the user with an optimal experience. This is the most necessary consideration at the user level.
Written at the end:
The various methods described in this series of documents are, in fact, a standardized choice, because in each project, we can use the hardware (server, network, storage), the user needs are different, we may need to because of time, land, and people to reasonably plan a project, but this logical architecture design ideas are unchanged.
along with the development of technology, similar to Solutions such as SDN,Server Sans, gigabit,40G throughput Networks,and FCOE are in fact beneficial advances in a variety of solutions, including desktop virtualization.
Reference Documentation:
Citrix Virtual Desktop Handbook 7.x
http://support.citrix.com/article/CTX139331
This article is from the "Citrix in the Cloud" blog, be sure to keep this source http://kaiqian.blog.51cto.com/236001/1717067
How to plan to build a large set of Citrix Desktop virtualization architectures-PostScript