ATIS 0200006-2012 Virtual Desktop Requirements.pdf

1、 ATIS-0200006 ATIS Standard on - VIRTUAL DESKTOP REQUIREMENTS ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies ac

2、tively formulate standards in ATIS Committees and Forums, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numer

3、ous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Pr

4、oject (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more informa

5、tion, please visit .Notice of Disclaimer further study is needed. ATIS-0200006 16 Appendix A (Informative) A Service Provider Deployment Options This document describes two approaches - “General” and “Static” - for Virtual Desktop Infrastructure Federation. The two approaches map directly to two dep

6、loyment options. When both options are available, a service provider may use them in combination. The result is a “Hybrid” deployment option that would overcome the resource allocation and cost limitations in the “Static” option while providing the control granularity offered in the “General” option

7、 The Hybrid deployment option is described below. The current hypervisor technologies have a lot in common in terms of the supported operating systems and other system functions like failover and load balancing. As such, it may not be always necessary to instantiate a user virtual machine in a virt

8、ual data center, as suggested by the “Static” option. While moving the user virtual machine from a Primary VDP to the Supporting VDP, the following scheme is suggested: 1. If the user is a premium user, use a virtual machine resource in the virtual data center. 2. If the user is not a premium user,

9、try to find a virtual machine resource with the required user characteristics in the supporting VDP. 3. If step 2 fails, use a virtual machine resource in the virtual data center for the user. 4. If step 3 fails, try to find other supporting VDPs which may not be most proximal to the user. With the

10、Hybrid”option, 1. The capacity and the cost of the dedicated virtual data center can be kept contained; 2. The supporting VDP is less likely to run out of capacity; and 3. Premium users can benefit from the virtual data center solution. A comparison of the deployment options “General”, “Static”, an

11、d “Hybrid” is in Table A.1 below. Table A.1: Comparison of deployment options - “General”, “Static”, and “Hybrid” Feature General Static Hybrid Resource allocation granularity at Supporting VDP Virtual machines and physical machines Group of Physical machines Virtual and/or group of Physical Machine

12、s Capacity estimation at Supporting VDP (taking into account user mobility patterns) Granular Coarse Granular OAM&P complexity Complex Simple Complex Performance Requirements at Supporting VDP (compute) No Guarantee Always Guarantee Minimum Guarantee Overall cost (Primary VDP perspective) Low High Medium The three deployment options “General”, “Static”, and “Hybrid” have distinct tradeoffs in terms of cost, performance, and management complexity. The VD service providers can choose an option convenient to them based on these tradeoffs.