1 / 25

Cloud Framework and Requirements for Desktop as a Service

ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014). Cloud Framework and Requirements for Desktop as a Service. Myeong-Hoon Oh, Senior Member, ETRI mhoonoh@etri.re.kr. Contents. Cloud Computing Requirements for high-level

frankin
Download Presentation

Cloud Framework and Requirements for Desktop as a Service

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITU Workshop on “Cloud Computing Standards – Today and the Future” (Geneva, Switzerland 14 November 2014) Cloud Framework and Requirements for Desktop as a Service Myeong-Hoon Oh, Senior Member, ETRI mhoonoh@etri.re.kr

  2. Contents • Cloud Computing Requirements for high-level • Based on Recommendation of Y.3501(Cloud computing framework and high-level requirements) • Cloud Computing Requirements for Desktop as a Service • Based on Recommendation of Y.3503 (Requirements for Desktop as a Service)

  3. Contents • Cloud Computing Requirements for high-level • Based on Recommendation of Y.3501(Cloud computing framework and high-level requirements) • Cloud Computing Requirements for Desktop as a Service • Based on Recommendation of Y.3503 (Requirements for Desktop as a Service)

  4. Scope of Y.3501 • Provides a cloud computing framework by addressing high-level requirements and use cases for • Cloud computing • Infrastructure as a service (IaaS) • Network as a service (NaaS) • Desktop as a service (DaaS) • Inter-cloud • End-to-end cloud resource management • Cloud infrastructure

  5. Development Methodology of Y.3501 One use case may derive multiple requirements Use-case- driven approach for requirements A new edition will include new use cases and requirements Future edition of Y.3501

  6. Use Cases in Y.3501

  7. General Requirements for cloud computing in Y.3501

  8. General Requirements for cloud computing in Y.3501

  9. General Requirements for cloud computing in Y.3501

  10. Edition plan for Y.3501

  11. Contents • Cloud Computing Requirements for high-level • Based on Recommendation of Y.3501(Cloud computing framework and high-level requirements) • Cloud Computing Requirements for Desktop as a Service • Based on Recommendation of Y.3503 (Requirements for Desktop as a Service)

  12. Summary of Y.3503 • As one of cloud computing service categories, desktop as a service (DaaS) provides cloud service customers with desktop functions remotely delivered by cloud service providers. • Recommendation ITU-T Y.3503 introduces the concept of DaaS, and describes general and functional requirements. To derive those requirements, relevant use cases are also presented.

  13. Concept of DaaS • Virtual desktop is an environment for accessing end user's desktop functions remotely. • DaaS is defined as a cloud service category in which the capabilities provided to the cloud service customer are the ability to build, configure, manage, store, execute and deliver users' desktop functions remotely.

  14. General Configuration for DaaS (1) CSC CSP • DaaS client • A physical device and associate software running on the device that enables a user to access DaaS • Connection manager • Responsible for connecting a user to suitable virtual desktop • Providing user authentication, assignment of a virtual desktop, and coordination of a delivery protocol

  15. General Configuration for DaaS (2) • Resource pool • An abstraction of software resource such as OS, application and user profiles. • Can provide provisioning information of software resources to Connection manager • Virtualization infrastructure • support H/W and S/W resources and create virtual resources • Virtual desktop delivery • transfer a virtual desktop to remote DaaS client through the network • Provides the communication channels between the DaaS client and DaaS platform

  16. DaaS requirement in Y.3503 • General requirements • Totally 13 was identified • Four from Y.3501 • Functional requirements • Totally 39 was extracted • 16 for operation and management • 9 for DaaS platform-side • 5 for DaaS client-side • 7 for DaaS platform-DaaS client interaction • 2 for DaaS security

  17. General Requirements in Y.3503

  18. Functional Requirements – Operation & Management in Y.3503 (1)

  19. Functional Requirements – Operation & Management in Y.3503 (2)

  20. Functional Requirements – DaaS Platform-side in Y.3503

  21. Functional Requirements – DaaS Client-side in Y.3503

  22. Functional Requirements – DaaS Platform-DaaS Client Interaction in Y.3503

  23. Functional Requirements – DaaS Security in Y.3503

  24. DaaS Use Cases in Y.3503 Office automation of development-oriented enterprise Customer service call centre Scenario of DaaS user Local resource usage Service continuation for DaaS Home application using DaaS Charging scheme for DaaS

  25. Conclusions • In Y.3501 • Identified general requirements for cloud computing, IaaS, NaaS, DaaS, inter-cloud, e2e resource management, and cloud infrastructure • Next edition will include more extended requirements and new requirements for use cases of existing and new domains, respectively. • In Y.3503 • Suggested DaaS concept and general configurations • Based on several relevant use cases, DaaS specific general and functional requirements have been derived. • Next edition (Y.DaaS-arch) is under development and will cover identification of DaaS functionalities and relationship between DaaS and cloud computing reference architecture in Y.3502

More Related