Now
it's time you've proven. Your suggested solutions are reliable and
functional and you can extract the information from the assessment and
testing steps. It is time to make a suitable plan for the operating
environment.
Choosing the right technology:
An
important point to consider is the difference between the type of user
use of the product and the differences in the technologies that are
available in VMware Horizon products. The first time you are collecting
information (the information gathering methods described earlier), you
are at a very important stage because your conclusion is that the
technology will meet the needs of users. There are several technologies
available to provide users with different services. Technologies like
Horizon View, Horizon Mirage, ThinApp, App Volumes.
Preparation for presentation in the operational environment:
You
now have all the information you need about the environment. Business
requirements and goals are specified. Different modes are designed to
provide the best response to users. You can now specify how the
implementation environment works. From here, you have to follow very
carefully and carefully. The solution has been tested, proven concepts,
and Pilot stage. Now is the time to start exciting. There are several
ways to do things, but keep in mind that you can start calmly and with
patience and implement processes over time. You can guarantee your
success by moving in principle over time.
Horizon View Pod and Block Architecture:
Let's
start with the main concepts of the Horizon View design: Pod and Block
reference architecture. This section covers the overall underlying
development and implementation of Horizon View. Horizon View Pod and
Block Architecture is a provider of infrastructure and reference
architectures that supports 10,000 users. This feature is available
through a modular approach to expand the infrastructure with the Horizon
View Block, and can support 2,000 users. This means you will have 2,000
virtual desktops.
Management
modules such as Management Block are expanded. It will also include
extensions such as Connection Servers and Security Servers. The blocks
are expanded to 2 thousand in size to reach 10 thousand (5 blocks). This
5-block configuration is called a pod. It will be a huge and spacious
space for you. If you're familiar with the cloud pod architecture and
put it in combination with pod and block, you can generally provide more
than 50,000 users. During the projects, you've heard a lot of these
sentences that, for example, I have only 500 users and I need the same
number of desktops, so pod and block architecture does not work for me.
But we want you to have a correct understanding of the subject and
design principles of how to expand Horizon View. In design with small
scales, you only need a pod that only contains a block.
As
mentioned earlier, the management block contains all of the components
of the Horizon view infrastructure. These components include Connection
Server and Security Server. The following diagram illustrates the
following:
There
are a number of ESXi hosts within each desktop, these hosts have enough
capacity to provide virtual desktops for you. VCenter is also
responsible for managing these desktops. In this process, there are
other components that manage this process:
To
view and deploy virtual desktops with Linked Clone, we need View
Composer. Also, a SQL statement will take the role of the View Composer
database and we need a database for View Events. The created machines
should be set to HA and the duplication process should be specific and
regular. But the most important part of the story is shared storage,
which can also be shared as a block.
If
you have only one vCenter, you will have a lot of restrictions on
simultaneously sending operations on cars. This is important, for
example, when a large number of virtual desktops are turned on in Pools
or Recompose. If there are too many vCenters, costly operations will
increase and speed will go up.
Cloud Pod architecture
has expanded to the previous version of Horizon View. You can easily
combine up to 25 pics of cloud pod into 5 sites. This condition will
allow you to provide 50,000 desktop users. In this way, when connecting
different Pods, users will be able to get their desktop from different
pools and at different pods and sites. As an administrator, you can
globally access all cloud pods.
Microsoft
Active Directory Lightweight Service and View Interpod API are two
services that are used to communicate between pods. When you enable the
Cloud Pod from the command line inside the Connection Viewer server,
VIPA (the connection between the pods) starts. And they send information
between themselves to find the desktops they need. By default, when a
user connects to the Horizon View and has a global Entitlement, it is
preferable to using virtual desktops than other users.
When
the scope settings are made, you can specify which View Connection
Server to search for where virtual machines are located and which
Entitlement searches. You can do the following:
• View : All Sites Searches for any virtual podcast or hosted apps to search for any Pod within the federations.
•
Within Site: To find virtual desktops or hosted apps, only Pods that
are found on similar sites are searched. The same sites mean that the
user is connected to them.
• Within Pod: To find virtual desktops or Hosted Applications, only the Pod that the user is connected to is searched.
vSphere Design for Horizon View:
Now
you have an overview of the basic design and basic conditions. It's
time to look at components that are part of the architecture. For
example, vSphere is the virtualization platform.
Here's
how to install and configure vSphere and ESXi on the hosts. Although
there is a general discussion about the requirements and how to
configure vCenter and host and cluster. Technically, you can have
Horizon View and other virtual servers run in a set of infrastructures
with a vCenter.
As we discussed earlier, there are two
infrastructure areas for Horizon View: the Management Block management
block running vCenter, View Composer, View Connection Server, and the
other where their virtual desktops run. It is recommended that the two
components be physically distributed on separate ESXs and clusters to
minimize your risk. It is also possible to run Horizon View components
on a separate vCenter. The vCenter separation from the Horizon
components means that there is less competition with prerequisites and
priorities when we decide to upgrade the systems.
Maximum settings:
When
you are building the right infrastructure for VDI, you can quickly and
easily capture the settings. Do not forget that the maximum is not the
ultimate goal, but our limitations. When designing, keep in mind that
the risk of losing individual components, such as the vCenter server or
View Connection, is always there. We will talk more about this in future
articles.
Want to download this blog as a PDF document, click the link below:
Abd El-Rahman Oreiby
Senior Data Center Engineer
Al Thuraya Security Egypt
www.abdelrahmanoreiby.weebly.com
No comments:
Post a Comment