control, monitoring, you must learn control! -. Yoda
The control layer is about creating a unique foundation for the consistent solution that supports layers-users (users, access and resources)
you can not make the control layer if you have not defined your user layer, access layer and resource layer. The control layer of the XenDesktop 7 plan is divided into
- Access Controllers - responsible for providing connectivity to resources as defined by the access layer
- Controllers office - manage and maintain the virtualized resources to the environment
- infrastructure controllers - standard infrastructure components
as to the control layer is to define what and how servers / devices you need to support the layers of the user. This is based on the size of the user groups, as well as the overall design for the user groups.
The first part of the control layer focuses on access controllers, which should not be confused with the access layer. The access layer defines the access conditions that are associated with each user group. The gatekeepers are the devices that allows you to implement these policies. If all your users are local and you do not require a remote access policy, then you will not need a NetScaler Gateway Access Controller.
The second part is on desktop delivery controllers. Delivery Controllers make sure that you are assigned to the right resource. They ensure that the resource is ready. And they do that resources are updated appropriately. XenDesktop 7, this bucket controllers has been reduced in size. You will not see XenApp controllers (zone data collectors) because the "XenApp" in XenDesktop 7 use the same framework. This means that users XenDesktop and XenApp users rely on the same desktop delivery controller!
Finally, the last part of the gate control layer on the other components, the supporting cast of characters that includes database servers, license server and hypervisor controller servers (vCenter , SCVMM, XenServer) Note :. XenServer does not really have a dedicated controller as vSphere and Hyper-V
When we update the conceptual architecture to now include our control layer, you get the following:
as you can see, almost all starts with 2 bodies so that we have a certain level of fault tolerance in that if one instance fails, we have a second instance to handle the load. Licensing is only one instance because it is built within the 30 day grace period, so who cares if it fails. You have 30 days to obtain licenses running again before the notice of users
Daniel -. Lead Architect
Follow @djfeller
0 Komentar