WO2022253044A1 - 一种云桌面设置方法、系统及设备 - Google Patents

一种云桌面设置方法、系统及设备 Download PDF

Info

Publication number
WO2022253044A1
WO2022253044A1 PCT/CN2022/094655 CN2022094655W WO2022253044A1 WO 2022253044 A1 WO2022253044 A1 WO 2022253044A1 CN 2022094655 W CN2022094655 W CN 2022094655W WO 2022253044 A1 WO2022253044 A1 WO 2022253044A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud desktop
client
container
image
cloud
Prior art date
Application number
PCT/CN2022/094655
Other languages
English (en)
French (fr)
Inventor
徐英杰
南俊杰
侯昌华
王传军
Original Assignee
华为云计算技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2022253044A1 publication Critical patent/WO2022253044A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45587—Isolation or security of virtual machine instances

Definitions

  • the present application relates to the field of computers, in particular to a method, system and equipment for setting up a cloud desktop.
  • cloud desktops are increasingly used in office scenarios.
  • the cost of a single desktop, the speed of service provisioning, and the compatibility of applications have become the focus of competition among manufacturers.
  • Cloud desktops provisioned based on virtual machines are widely used, but virtual machines have the disadvantage of long startup time.
  • the present application provides a cloud desktop construction setting method, which can improve the management efficiency of the cloud desktop.
  • the first aspect of the present application provides a cloud desktop construction setting method, which is characterized in that the cloud desktop construction method is applied to a cloud desktop management system, and the method includes: receiving a first cloud desktop distribution request, the first cloud desktop distribution The request carries the verification information of the first client and the personalization data of the cloud desktop of the first client, wherein the personalization data of the cloud desktop of the first client is used to indicate the cloud desktop application that the first client needs to use; according to the first client
  • the cloud desktop personalized data setting of a client provides a first container of the first cloud desktop; according to the verification information of the first client, a first communication channel is set between the first container and the first client, wherein the first A client accesses the first desktop cloud environment provided by the first container via the first communication channel.
  • the cloud desktop setting method utilizes the container to provide the cloud desktop, utilizes the characteristics of fast creation speed of the container, effectively simplifies the setting steps of the cloud desktop, and thus improves the management efficiency of the data visualization interface.
  • the cloud desktop personalization data of the first client determine the first cloud desktop application and the second cloud desktop application required by the first client; The first mirror image of the cloud desktop application and the second mirror image provided with the second cloud desktop application; the first personalized mirror image is set according to the first mirror image and the second mirror image; according to the first personalized mirror image on the physical machine Create the first container in .
  • the method for setting the cloud desktop avoids the process of recreating the mirror image by obtaining the application required by the client in the mirror library, thereby improving the management efficiency of the data visualization interface.
  • the first container is created in the operating system of the physical machine according to the first personalized image.
  • the cloud desktop setting method creates a container according to the first personalized image in the operating system of the physical machine, which effectively improves the management efficiency of the data visualization interface.
  • the first container is created in the operating system of the first virtual machine of the physical machine according to the first personalized image.
  • the cloud desktop setting method creates a container according to the first personalized image in the operating system of the virtual machine, which effectively improves the management efficiency of the data visualization interface. At the same time, physical isolation is better achieved by using virtual machines.
  • a second cloud desktop provisioning request is received, and the second cloud desktop provisioning request carries the verification information of the second client and the cloud desktop personalization data of the second client, wherein the cloud desktop of the second client
  • the personalization data is used to indicate the cloud desktop application that the second client needs to use; according to the cloud desktop personalization data of the second client, the second container of the second cloud desktop is provided, and according to the verification information of the second client, the A second communication channel is set between the second container and the second client, wherein the second client accesses the second desktop cloud environment provided by the second container via the second communication channel.
  • the cloud desktop personalization data of the second client determine the third cloud desktop application and the fourth cloud desktop application required by the second client; The third mirror image of the cloud desktop application and the fourth mirror image provided with the fourth cloud desktop application; according to the third mirror image and the fourth mirror image, a second personalized mirror image is set; according to the second personalized mirror image on the physical machine
  • the second container is created in the operating system.
  • the second container is installed in the operating system of the second virtual machine of the physical machine according to the second personalized image, and the first virtual machine and the second virtual machine interact with each other in the physical machine isolation.
  • the second aspect of the present application provides a cloud desktop management system data visualization interface management system, the system is used to implement the method provided by the first aspect.
  • the system includes an interaction module and a processing module.
  • the interaction module is configured to receive a first cloud desktop issuance request, the first cloud desktop issuance request carries the verification information of the first client and the cloud desktop personalization data of the first client, wherein the cloud desktop personality of the first client
  • the personalized data is used to indicate the service request sent by the user of the cloud desktop application that the first client needs to use
  • the processing unit is configured to provide the first container of the first cloud desktop according to the cloud desktop personalized data setting of the first client; Set up a first communication channel between the first container and the first client according to the authentication information of the first client, wherein the first client accesses the first desktop provided by the first container via the first communication channel
  • the cloud environment service requests to create a virtual machine and a container, and the container runs on the virtual machine.
  • the processing module is further configured to determine the first cloud desktop application and the second cloud desktop application required by the first client according to the cloud desktop personalization data of the first client; Select the first image set with the first cloud desktop application and the second image set with the second cloud desktop application; set the first personalized image according to the first image and the second image; set the first personalized image according to the first The personalized image creates the first container in the physical machine.
  • the processing module is further configured to create the first container in the operating system of the physical machine according to the first personalized image.
  • the processing module is further configured to create the first container in the operating system of the first virtual machine of the physical machine according to the first personalized image.
  • the interaction module is also used to receive a second cloud desktop provisioning request, the second cloud desktop provisioning request carrying the verification information of the second client and the cloud desktop personalization data of the second client, wherein
  • the cloud desktop personalized data of the second client is used to indicate the cloud desktop application that the second client needs to use
  • the processing module is also used to provide the second cloud desktop application according to the cloud desktop personalized data of the second client A second container, setting up a second communication channel between the second container and the second client according to the verification information of the second client, wherein the second client accesses the second container via the second communication channel to provide The second desktop cloud environment.
  • the processing module is further configured to determine the third cloud desktop application and the fourth cloud desktop application required by the second client according to the cloud desktop personalization data of the second client; Select the third image with the third cloud desktop application and the fourth image with the fourth cloud desktop application; set the second personalized image according to the third image and the fourth image; set the second personalized image according to the second personality
  • the second container is created in the operating system of the physical machine through the optimized image.
  • the processing module is further configured to install the second container in the operating system of the second virtual machine of the physical machine according to the second personalized image, the first virtual machine and the second virtual machines are isolated from each other in this physical machine.
  • a third aspect of the present application provides a computing device cluster, where the cluster includes at least one computing device, and each computing device includes a processor and a memory.
  • the processor of the at least one computing device is configured to execute the instructions stored in the memory, so that the cluster of computing devices executes the method according to the first aspect or any implementation manner of the first aspect.
  • the fourth aspect of the present application provides a computer program product containing instructions, and when the instruction is run on a cluster of computer equipment, the cluster of computer equipment executes the method of the above-mentioned first aspect or any implementation manner of the first aspect .
  • a fifth aspect of the present application provides a computer-readable storage medium, the computer-readable storage medium includes computer program instructions, and when the computer program instructions are executed by a cluster of computing devices, the cluster of computing devices executes A method of any implementation of an aspect.
  • Fig. 1 is a schematic diagram of a cloud desktop management system involved in the present application
  • Fig. 2 is the flowchart of a kind of cloud desktop setting method involved in the present application
  • Fig. 3 is a schematic diagram of a cloud desktop management interface involved in the present application.
  • Fig. 4 is a schematic diagram of a container management involved in the present application.
  • Fig. 5 is a schematic diagram of a container image setting method involved in the present application.
  • FIG. 6 is a schematic diagram of another container image setting method involved in the present application.
  • Fig. 7 is a schematic diagram of another cloud desktop setting method involved in the present application.
  • Fig. 8 is a schematic structural diagram of a container creation involved in the present application.
  • Fig. 9 is a schematic structural diagram of a cloud desktop management system involved in the present application.
  • FIG. 10 is a schematic diagram of a computing device involved in the present application.
  • Fig. 11 is a schematic diagram of a computing device cluster involved in the present application.
  • Fig. 12 is a schematic diagram of another computing device cluster involved in the present application.
  • Fig. 13 is a schematic diagram of another computing device cluster involved in the present application.
  • FIG. 1 shows an application scenario of a cloud desktop setting method 100 provided in this application.
  • the resource pool includes multiple physical machines, and each physical machine includes computing resources, storage resources, network resources, and the like.
  • Common physical machines include servers and personal computers (personal computers, PCs).
  • the cloud desktop management system 200 After the cloud desktop management system 200 receives the cloud desktop provisioning request from the tenant, it creates a container (container) in the resource pool according to the request, and the container is used to run/provide the cloud desktop. Considering that containers have the advantage of fast startup speed, creating/running cloud desktops based on containers can effectively improve the efficiency of cloud desktop provisioning.
  • a virtual machine may also be created according to a request. Wherein, one or more containers may run in each virtual machine.
  • a virtual machine corresponds to a type of tenant, and a container corresponds to a tenant. That is, by creating virtual machines, the isolation between different types of tenants can be realized, further improving the security of the distributed cloud desktops.
  • the cloud desktop management system 200 receives a tenant's cloud desktop provisioning request.
  • the cloud desktop management system 200 performs cloud desktop provisioning according to the cloud desktop provisioning request sent by the tenant.
  • the cloud desktop management system 200 is deployed at the remote end, and the terminal device on the tenant side communicates with the container on the cloud desktop management system 200 side through a desktop communication protocol.
  • the tenant accesses the corresponding cloud desktop via the client on the terminal device on the tenant side.
  • the cloud desktop is provided by a container corresponding to the client on the terminal device on the tenant side.
  • the data generated/updated due to the operation of the tenant is stored in the container where the cloud desktop is located. This is because in the aforementioned desktop communication protocol, the client on the tenant side only provides functions such as display, audio playback, and keyboard and mouse interaction. That is, the tenant's data is not transmitted or stored to ensure data security.
  • a desktop communication module is respectively deployed symmetrically in the client and the server. Specifically, the client and the server perform data transmission based on the desktop communication protocol through their respective desktop communication modules.
  • the cloud desktop provisioning request sent by the tenant also carries verification information.
  • the verification information is verification information of the client.
  • the authentication information of the client includes information such as authentication information of the client, an Internet Protocol Address (Internet Protocol Address, IPA) of the client, and a type of the client.
  • IPA Internet Protocol Address
  • the client authentication information also includes identity information of the tenant, for example, the enterprise and department of the tenant.
  • the authentication information of the client can be used to set up a communication channel between the container corresponding to the client and the client. Further, the client accesses the desktop cloud environment provided by the container corresponding to the client via the communication channel. The specific setting and access process will be described in detail below.
  • the cloud desktop provisioning request sent by the tenant also carries cloud desktop personalization data.
  • the personalization data of the cloud desktop includes one or more of the following: the account name and password of the operating system, the name of the application that needs to run on the cloud desktop, the image file of the application that needs to run on the cloud desktop, the account name and password of the application. password etc.
  • the aforementioned cloud desktop personalized data is also transmitted through the desktop communication protocol.
  • the desktop communication protocol used in this application is independent computing architecture (independent computing architecture, ICA), remote desktop protocol (remote desktop protocol, RDP), independent computing environment protocol (simple protocol for independent computing environment, One of the common desktop communication protocols such as SPICE) and Huawei desktop protocol (HDP).
  • independent computing architecture independent computing architecture
  • RDP remote desktop protocol
  • independent computing environment protocol simple protocol for independent computing environment
  • SPICE SPICE
  • HDMI Huawei desktop protocol
  • S102 The cloud desktop management system 200 issues the virtual machine according to the provisioning request.
  • the administrator can use the cloud desktop management system 200 to provision virtual machines.
  • FIG. 3 shows a cloud desktop management interface 300 .
  • the administrator can view the cloud desktop provisioning request in the task list control 302 .
  • the cloud desktop management system 200 has received 13 cloud desktop provisioning requests and has not yet processed them.
  • the administrator can expand the 13 cloud desktop issuance requests (not shown in FIG. 3 ) by clicking on the number before the word "request to be issued”. Further, the administrator can select a request to be processed by clicking on the multiple requests.
  • administrators can be the operation and maintenance personnel of the cloud vendor in the public cloud scenario, or the operation and maintenance personnel of the enterprise where the tenant is located.
  • the administrator can respond to the request. Specifically, the administrator can issue containers.
  • provisioning of virtual machines may also be performed.
  • the administrator first selects a physical machine from the resource pool in the physical machine selection control 308, and the selected physical machine is used to run the cloud desktop instance.
  • the resource pool includes at least 4 physical machines.
  • the basic information of the physical machine can be obtained in the information display control 304 on the left.
  • the information display control 304 displays the deployment area of the physical machine, computing resources, storage resources, network resources and Internet Protocol (Internet Protocol, IP) addresses.
  • a virtual machine may be selected in the virtual machine selection control 310 .
  • the information display control 304 on the left will display the basic information of the selected virtual machine (not shown in FIG. 3 ).
  • the basic information includes the deployment area of the virtual machine, computing resources, storage resources, network resources and Internet Protocol (Internet Protocol, IP) addresses.
  • the virtual machine selection control 310 displays that the virtual machines are all running on the selected physical machine. That is, as shown in FIG. 3 , at least VM1 , VM2 and VM3 run on physical machine 1 .
  • the virtual machine after receiving the cloud desktop provisioning request from the tenant, if the virtual machine is not running on the selected physical machine, the virtual machine can be provisioned by clicking the add button first. Further, one of the distributed virtual machines is selected to run the cloud desktop. Specifically, when adding a new virtual machine, parameters included in the virtual machine need to be set. For example, a virtual machine includes computing resources, storage resources, network resources, and a kernel (kernel). The specific interface for setting virtual machine parameters is not shown in FIG. 3 .
  • the virtual machine provisioning operation performed by clicking the add button is based on the virtual machine provisioning service.
  • the tenant can also view historical issuance records in the task list control 302 .
  • the historical distribution record may include the number of the physical machine and the number of the virtual machine where the historically distributed cloud desktop instance is located.
  • cloud desktops of the same type of tenant usually run on the same virtual machine.
  • the cloud desktops of employees in the same department can run on the same virtual machine.
  • how to run the cloud desktops of employees in the same department on the same virtual machine will be introduced in S104.
  • the provisioning operation of the virtual machine by the administrator may not be based on the provisioning request of the tenant.
  • the administrator can pre-divide the physical machines according to needs. That is, the number and specifications of virtual machines running on each physical machine are determined in advance.
  • the administrator can also add and delete virtual machines.
  • the cloud desktop management system 200 can automatically provision virtual machines according to provisioning requests.
  • S102 is an optional step. Also, the execution time of S102 is not necessarily earlier than that of S104. That is, S102 may be executed before S104, or may be executed after S104. Optionally, S102 and S104 may be executed simultaneously.
  • S104 The cloud desktop management system 200 releases the container according to the release request.
  • the administrator can use the cloud desktop management system 200 to provision containers.
  • the administrator can select a physical machine in the physical machine selection control 308. Further, the administrator can click the add button in the container creation control 312 to create/issue the container. Specifically, the above operations are implemented based on the container provisioning service.
  • the administrator's operation instructions for the cloud desktop system need to be converted into operations such as the creation and deletion of specific containers through the management control system.
  • the cloud desktop management system 200 may automatically release containers according to the release request.
  • FIG. 4 shows an architecture diagram of container management.
  • the architecture diagram shown in FIG. 4 includes a management control system control terminal 401 running on the management plane, a management control system agent 402 running on the service plane, a container engine 405, a virtual machine 403, and a virtual machine deployed on the virtual machine.
  • a plurality of system containers (404A-404C).
  • the management control system control terminal 401 running on the management plane side routes it to the management in the specific virtual machine via a virtual access gateway (vAG).
  • vAG virtual access gateway
  • Control system agent 402 the management control system agent 402 running on the business side needs to transmit the operation instruction to the container engine 405 after receiving the operation instruction.
  • the management control system agent 402 is also used to return the operation result to the management control system control terminal 401 .
  • the container engine 405 After receiving a specific operation instruction, the container engine 405 will execute the operation of creating, deleting, starting or stopping the system container (404A-404C) according to the operation instruction.
  • the virtual machine 403 is used to provide a common kernel for multiple system containers, and as the smallest unit of security isolation to ensure independence among tenants.
  • the application required by the client may be determined. Further, application images can be obtained from the server where the cloud desktop is located, and the personalized image corresponding to the client can be set according to these images. The personalized image will be used to create/run the container corresponding to the client.
  • the image of the application can also be obtained from the container mirror repository.
  • the container image repository is used to store container images.
  • the container engine can import the container image in the container repository to allow the first container to use the container image, and the first container can also publish the unified view layer in Figure 6 as a new container image to the container image repository , so that other containers can use the container image.
  • the container image function allows container users to quickly deploy their own container images to different operating environments through the image repository. After obtaining the image of the application from the container image warehouse, you can set the personalized image corresponding to the client according to the images of multiple applications.
  • the container image layer in Figure 6 is a container image that can be shared by multiple first containers-3, the container layer is unique to each container, and the unified view layer is mounted under a specific directory of each container, and the unified view Layers superimpose the contents of container layers and container image layers.
  • a first container when the first container reads file 1 mounted in a specific directory, it only needs to directly read file 1 in the container image layer.
  • file 2 in the container image layer is copied to the container layer, and data is written to file 2 in the container layer, but file 2 in the container image layer will not modified.
  • File 3 is the same as file 1.
  • file 4 will be created in the container layer, and the container image layer will not be modified.
  • different container images can be superimposed according to the personalized data of the cloud desktop corresponding to the client, so as to quickly assemble a personalized container image with all the applications required by the tenant. And based on the personalized container image, a cloud desktop is provided for the tenant.
  • the container may run on the operating system of the physical machine instead of the operating system of the virtual machine.
  • a container engine runs on a physical machine.
  • the operating systems of the above physical machines include common operating systems, such as windows, unix, linux, and mac. That is, the cloud desktop management system 200 can create a container in the operating system of the physical machine according to the personalized image corresponding to the client.
  • cloud desktops of the same type of tenant usually run on the same physical machine.
  • the cloud desktops of employees in the same department can run on the same physical machine. This ensures that the data between different departments are isolated from each other and ensures the security of cloud desktop data.
  • the container may run on the operating system of the virtual machine instead of directly running on the operating system of the physical machine.
  • at least one container runs on a virtual machine.
  • each virtual machine also includes a container engine and an interaction module.
  • the interaction module is used to realize the interaction between the virtual machine kernel and the container.
  • each container contains an interaction agent inside, and the interaction agent is used to realize the data transmission between the container and the virtual machine.
  • the operating system of the above virtual machine is similar to the operating system of the physical machine. For example, windows, unix, linux and mac, etc. That is, the cloud desktop management system 200 can create a container in the operating system of the virtual machine according to the personalized image corresponding to the client.
  • one container is used to run one tenant's cloud desktop. That is, one container corresponds to one tenant.
  • a virtual machine contains multiple containers, so a virtual machine can correspond to multiple tenants of the same type. For example, for a company's cloud desktop management system, tenants in the same department can be considered as the same type of tenants. Therefore, running the cloud desktops of tenants in different departments on different virtual machines effectively realizes the isolation between different types of tenants and improves the security of the system.
  • the operating system in the container is usually an operating system based on the linux kernel.
  • the unity operating system UOS
  • the unity operating system CentOS
  • Debain community enterprise operating system
  • the aforementioned operating systems are stored in containers in the form of images.
  • administrators can also configure page interface components (web interface, WI), single name service (Unified Name Service, UNS), vAG, virtual load balance (virtual load balance, vLB), unified Set parameters such as Identity and Access Management (IAM).
  • WI web interface
  • UNS Unified Name Service
  • vAG virtual load balance
  • vLB virtual load balance
  • IAM Identity and Access Management
  • the WI provides a login interface for the cloud terminal user.
  • UNS is a service that supports access to multiple desktop management systems with different WI domain names through a unified domain name, reducing the switching and jumping of users between different WI domain names.
  • the vAG can logically divide an access gateway (AG) device into multiple virtual AGs (VAGs), and each VAG can work independently under the control of different media gateway controllers.
  • vLB mainly provides (virtual) load balancing services to tenants. Users can apply for a load balancer and associate business hosts with the load balancer.
  • IAM is a security management service of the public cloud system, providing identity management, permission assignment, and access control functions.
  • personalization settings can be performed using the personalization data of the cloud desktop received in S100.
  • the account name and password of the tenant's operating system and the applications that the tenant needs to run on the cloud desktop can be stored in the cloud desktop system in advance.
  • the tenant and the distributed cloud desktop can communicate based on the desktop communication protocol. That is, tenants can use the server-side cloud desktop running on the tenant side based on the desktop communication protocol.
  • the above-mentioned container may also be a system container (system container).
  • system container is a lightweight host virtualization technology based on container technology.
  • the system container provides the same behavior as the virtual machine, has a complete operating system, and starts a complete operating system.
  • system containers can support systemd.
  • systemd is an initialization system in the Linux system. Its design goal is to overcome the inherent shortcomings of the existing initialization system, optimize the instruction logic of the system, and thereby improve the startup speed of the system. Since the system container engine supports systemd, its life cycle management is similar to that of a virtual machine, so it can realize functions such as loading and unloading applications in the system and starting and stopping the operating system in the container.
  • each system container in the virtual machine does not have an independent kernel (kernel), but shares the kernel of the host machine, adaptive modifications are required to support the new architecture of the new container plus the common kernel of the host machine , to ensure the normal use of some kernel mode functions (such as universal serial bus (universal serial bus, USB)).
  • some kernel mode functions such as universal serial bus (universal serial bus, USB)
  • the implementation method is to run the function entity of the kernel function required by the container in the kernel of the host machine.
  • the function entity realizes the interaction between the inner and outer layers through the corresponding proxy component in the container, so as to ensure the normal use of some kernel mode functions.
  • tenants accessing the cloud desktop management system 200 include at least tenant 1 and tenant 2 .
  • tenant 1 accesses the cloud desktop management system 200 through a first client
  • tenant 2 accesses the cloud desktop management system through a second client.
  • FIG. 7 shows a schematic flow diagram of a method for disaster recovery switching, which may specifically include:
  • the cloud desktop management system 200 receives a first cloud desktop request sent by a tenant 1 through a first client.
  • Tenant 1's cloud desktop provisioning request carries the verification information of the first client and the personalization data of the first client's cloud desktop, wherein the verification information of the first client includes the verification information including the identification and authentication information of the first client and , information such as the Internet protocol address (Internet Protocol Address, IPA) of the first client and the type of the first client.
  • the first client authentication information further includes identity information of the tenant 1, for example, the enterprise and department of the tenant 1, and so on.
  • the cloud desktop personalization data of the first client includes one or more of the following: the account name and password of the operating system corresponding to the first client, the name of the application that needs to run on the cloud desktop in the first client, the name of the first client The client needs to run the image file of the application on the cloud desktop, the account name and password of the application, etc.
  • S502 The cloud desktop management system 200 issues the virtual machine 1 according to the first cloud desktop provisioning request.
  • the administrator can use the cloud desktop management system 200 to provision the virtual machine 1 . Specifically, after making a selection in the physical machine selection control 308 and the virtual machine selection control 310 in FIG. 3 , provisioning of the virtual machine 1 can be realized.
  • S502 is an optional step. Also, the execution time of S502 is not necessarily earlier than that of S504. That is, S502 may be executed before S504, or may be executed after S504. Optionally, S502 and S504 may be executed simultaneously.
  • S504 The cloud desktop management system 200 releases the first container according to the first cloud desktop provisioning request.
  • the administrator can use the cloud desktop management system 200 to distribute the first container. Specifically, after selecting the physical machine selection control 308 and the container selection control 312 in FIG. 3 , the first container can be issued. Optionally, the virtual machine can also be selected through the virtual machine selection control 310 .
  • the first container issued for tenant 1 is located in VM1 , and VM1 is located in physical machine 1 .
  • the following takes the first container corresponding to tenant 1 as an example to introduce.
  • a first container (first container) for providing the first cloud desktop may be set.
  • the required application can be determined according to the personalization data of the cloud desktop of the first client.
  • the mirror image of the application can be obtained from a remote server or a mirror warehouse. According to the acquired image of the application, the first personalized image corresponding to tenant 1 can be obtained. Running the first personalized image can complete the creation of the first container (first container).
  • the mirror warehouse can be located in the server where the cloud desktop is located.
  • it may also be located in the server where the first client is located.
  • the applications required by the first client include a first cloud desktop application and a second cloud desktop application.
  • the cloud desktop management system 200 can acquire the image file of the first cloud desktop application and the image file of the second cloud desktop application in the mirror warehouse, and set the first personality for the first client at the unified view layer according to these two image files mirror image.
  • a first communication channel may be set between the first container and the first client, wherein the first client communicates via the first A communication channel accesses the first desktop cloud environment provided by the first container.
  • the cloud desktop management system 200 receives the second cloud desktop request sent by the tenant 2 through the second client.
  • the cloud desktop provisioning request of tenant 2 carries the verification information of the second client and the cloud desktop personalization data of the second client, wherein the verification information of the second client includes the identity authentication information of the second client and , the Internet Protocol Address (Internet Protocol Address, IPA) of the second client and the information such as the type of the second client.
  • the second client authentication information further includes identity information of the tenant 2, for example, the enterprise and department of the tenant 2, and the like.
  • the cloud desktop personalization data of the second client includes one or more of the following: the account name and password of the operating system corresponding to the second client, the name of the application that needs to run on the cloud desktop in the second client, the name of the second client The client needs to run the image file of the application on the cloud desktop, the account name and password of the application, etc.
  • S508 The cloud desktop management system 200 issues the virtual machine 2 according to the second cloud desktop request.
  • the administrator can use the cloud desktop management system 200 to provision the virtual machine 2 .
  • provisioning of the virtual machine 2 can be realized.
  • VM1 on physical machine 1 is allocated to tenant 1
  • VM2 on physical machine 1 is allocated to tenant 2. That is, the virtual machine corresponding to tenant 1 and the virtual machine corresponding to tenant 2 belong to different virtual machines in the same physical machine.
  • whether the virtual machines corresponding to the tenant 1 and the tenant 2 are located in the same physical machine is determined according to the authentication information of the tenant 1 and the tenant 2.
  • the verification information of tenant 1 indicates that the enterprise of tenant 1 and the verification information of tenant 2 indicate that the enterprise of tenant 2 is the same
  • virtual machines corresponding to tenant 1 and tenant 2 can be created on the same physical machine.
  • the verification information of tenant 1 indicates that the enterprise of tenant 1 is different from that of tenant 2
  • the virtual machines corresponding to tenant 1 and tenant 2 can be created on different physical machines.
  • S510 The cloud desktop management system 200 releases the second container according to the second cloud desktop request.
  • the administrator can use the cloud desktop management system 200 to issue the second container. Specifically, after selecting the physical machine selection control 308 and the container selection control 312 in FIG. 3 , the second container can be issued.
  • the virtual machine can also be selected through the virtual machine selection control 310 .
  • Whether the containers corresponding to tenant 1 and tenant 2 are located on the same physical machine or virtual machine is determined based on the authentication information of tenant 1 and tenant 2.
  • the containers corresponding to tenant 1 and tenant 2 can be installed in different VMs respectively, where VM1 Isolation from VM2 in the same physical machine realizes the mutual isolation of the containers corresponding to tenant 1 and tenant 2.
  • a second communication channel may be set between the second container (second container) and the second client, wherein the second client The terminal accesses the second desktop cloud environment provided by the second container (second container) via the second communication channel.
  • the execution sequence of the whole of S500 to S504 and the whole of S506 to S510 is not in any order. Specifically, the whole of S500 to S504 can be executed before the whole of S506 to S510, and the whole of S500 to S504 can also be executed after the whole of S506 to S510. Optionally, the whole of S500 to S504 and the whole of S506 to S510 can also be executed at the same time.
  • the present application also provides a cloud desktop management system 200, as shown in FIG. 9 , including:
  • the interaction unit 202 is configured to receive a cloud desktop provisioning request in S100. In S100 , the interaction unit 202 also performs receiving of the operation instruction issued by the administrator based on the selected information in the cloud desktop management interface 300 shown in FIG. 3 .
  • the storage unit 204 is configured to store basic information of each physical machine in S100. Further, the administrator releases the operation record of the container in S104, and the basic information of the issued container will also be stored in the storage unit 204.
  • the storage unit 204 is also used to store basic information of each virtual machine in S100.
  • the administrator issues the operation record of the virtual machine in S102 , and the basic information of the allocated virtual machine will also be stored in the storage unit 204 .
  • the processing unit 206 is configured to implement provisioning of the virtual machine according to the operation instruction in S102.
  • the issuing of the container according to the operation instruction is also performed by the processing unit 206 .
  • the operation of determining the cloud desktop application required by the client according to the personalization data of the cloud desktop of the client is performed by the processing unit 206 .
  • the processing unit is further configured to select an image provided with the cloud desktop application in the image library in S104 to set a personalized image, and create a container in the physical machine according to the personalized image.
  • the operation of creating a container in the operating system of the virtual machine of the physical machine according to the personalized image in S104 is also performed by the processing unit 206 .
  • the processing unit 206 is further configured to establish a communication channel between the issued container and the client in S104.
  • the present application also provides a computing device 600 .
  • the computing device includes: a bus 602 , a processor 604 , a memory 606 and a communication interface 608 .
  • the processor 604 , the memory 606 and the communication interface 608 communicate through the bus 602 .
  • Computing device 600 may be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 600 .
  • the bus 602 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one line is used in FIG. 10 , but it does not mean that there is only one bus or one type of bus.
  • Bus 604 may include pathways for communicating information between various components of computing device 600 (eg, memory 606 , processor 604 , communication interface 608 ).
  • the processor 604 may include processing such as a central processing unit (central processing unit, CPU), a graphics processing unit (graphics processing unit, GPU), a microprocessor (micro processor, MP) or a digital signal processor (digital signal processor, DSP). Any one or more of them.
  • CPU central processing unit
  • GPU graphics processing unit
  • MP microprocessor
  • DSP digital signal processor
  • the memory 606 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM).
  • Processor 604 can also include non-volatile memory (non-volatile memory), such as read-only memory (read-only memory, ROM), flash memory, mechanical hard disk (hard disk drive, HDD) or solid state hard disk (solid state drive, SSD).
  • Executable program codes are stored in the memory 606 , and the processor 604 executes the executable program codes to implement the aforementioned cloud desktop setting method 100 .
  • the memory 406 stores instructions for the cloud desktop management system 200 to execute the cloud desktop setting method 100 .
  • the communication interface 603 implements communication between the computing device 600 and other devices or communication networks by using transceiver modules such as but not limited to network interface cards and transceivers.
  • the embodiment of the present application also provides a computing device cluster.
  • the computing device cluster includes at least one computing device 600 .
  • the memory 606 of one or more computing devices 600 in the computing device cluster may store the same instructions of the cloud desktop management system 200 for executing the cloud desktop setting method 100 .
  • one or more computing devices 600 in the computing device cluster may also be used to execute some instructions of the cloud desktop management system 200 for executing the cloud desktop setting method 100 .
  • a combination of one or more computing devices 600 can jointly execute the instructions of the cloud desktop management system 200 for executing the cloud desktop setting method 100 .
  • the memory 606 in different computing devices 600 in the computing device cluster may store different instructions for executing some functions of the cloud desktop management system 200 .
  • Figure 12 shows a possible implementation.
  • two computing devices 600A and 600B are connected through a communication interface 608 .
  • Instructions for performing the functions of the interaction unit 202 and the processing unit 206 are stored on memory in the computing device 600A.
  • Instructions for performing the functions of the storage unit 204 are stored on the memory in the computing device 600B.
  • the memories 606 of the computing devices 600A and 600B jointly store instructions for the cloud desktop management system 200 to execute the cloud desktop setting method 100 .
  • connection mode between computing device clusters shown in FIG. 12 may be based on the consideration that the cloud desktop setting method 100 provided in this application needs to store a large amount of basic device information. Therefore, it is considered that the storage function is performed by the computing device 600B.
  • computing device 600A shown in FIG. 12 may also be performed by multiple computing devices 600 .
  • the functions of computing device 600B may also be performed by multiple computing devices 600 .
  • one or more computing devices in a cluster of computing devices may be connected through a network.
  • the network may be a wide area network or a local area network or the like.
  • Figure 13 shows a possible implementation. As shown in FIG. 13 , two computing devices 600C and 600D are connected through a network. Specifically, it is connected to the network through a communication interface in each computing device.
  • the memory 606 in the computing device 600C stores instructions for executing the interaction unit 202 .
  • the memory 606 in the computing device 600D stores instructions for executing the storage unit 204 and the processing unit 206 .
  • connection mode between the computing device clusters shown in FIG. 13 can be considered that the cloud desktop setting method 100 provided by this application needs to store a large amount of device basic information and perform a large number of cloud desktop provisioning operations. Therefore, it is considered that the storage unit
  • the functions implemented by 204 and processing unit 206 are executed by computing device 600D.
  • computing device 600C shown in FIG. 13 may also be performed by multiple computing devices 600 .
  • the functions of computing device 600D may also be performed by multiple computing devices 600 .
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that a computing device can store, or a data storage device such as a data center that includes one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state hard disk), etc.
  • the computer-readable storage medium includes instructions, and the instructions instruct a computing device to execute the above-mentioned cloud desktop management system 200 for executing the cloud desktop setting method 100 .
  • the embodiment of the present application also provides a computer program product including instructions.
  • the computer program product may be a software or program product containing instructions, executable on a computing device or stored on any available medium.
  • the computer program product runs on at least one computer device, at least one computer device is made to execute the above cloud desktop setting method 100 .

Abstract

本申请提供了一种云桌面设置方法，其特征在于，所述方法包括：接收第一云桌面发放请求，所述第一云桌面发放请求携带有第一客户端的验证信息和所述第一客户端的云桌面个性化数据，其中，所述第一客户端的云桌面个性化数据用于指示所述第一客户端需要使用的云桌面应用；进一步地，根据所述第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器；根据所述第一客户端的验证信息在所述第一容器与所述第一客户端之间设置第一通信通道，其中，所述第一客户端经由所述第一通信通道访问所述第一容器提供的第一桌面云环境。所述云桌面构建方法通过利用容器提供云桌面，有效地简化了云桌面的设置步骤，提高了云桌面的设置效率。

Description

一种云桌面设置方法、系统及设备 技术领域
本申请涉及计算机领域，特别涉及一种云桌面的设置方法、系统及设备。
背景技术
随着云计算技术的发展，云桌面凭借其信息安全、移动办公、灵活扩展、快速配置、集中运维等优势，在办公场景的使用占比越来越高。随着云桌面的快速推广，单桌面的成本、业务发放的速度、应用的兼容性已经成为各厂商竞争的焦点。基于虚拟机发放的云桌面被广泛应用，但虚拟机存在启动时间较长的缺点。
因此，如何提升云桌面的设置效率成为了亟待解决的问题。
发明内容
本申请提供了一种云桌面构建设置方法，能够提高云桌面的管理效率。
本申请的第一方面提供了一种云桌面构建设置方法，其特征在于，该云桌面构建方法应用于云桌面管理系统，该方法包括：接收第一云桌面发放请求，该第一云桌面发放请求携带有第一客户端的验证信息和该第一客户端的云桌面个性化数据，其中该第一客户端的云桌面个性化数据用于指示该第一客户端需要使用的云桌面应用；根据该第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器；根据该第一客户端的验证信息在该第一容器与该第一客户端之间设置第一通信通道，其中，该第一客户端经由该第一通信通道访问该第一容器提供的第一桌面云环境。接收用户发送的业务请求；根据该业务请求创建虚拟机和容器，该容器运行在该虚拟机上。
该云桌面设置方法利用容器提供云桌面，利用了容器创建速度快的特点，有效地简化了云桌面的设置步骤，从而提高了数据可视化界面的管理效率。
在一些可能的设计中，根据该第一客户端的云桌面个性化数据，确定该第一客户端所需的第一云桌面应用和第二云桌面应用；在镜像库中选择设置有该第一云桌面应用的第一镜像和设置有该第二云桌面应用的第二镜像；根据该第一镜像和该第二镜像设置第一个性化镜像；根据该第一个性化镜像在物理机中创建该第一容器。
该云桌面设置方法通过在镜像库中获取客户端所需的应用，避免了重新创建镜像的过程，从而提高了数据可视化界面的管理效率。
在一些可能的设计中，根据该第一个性化镜像在该物理机的操作系统中创建该第一容器。
该云桌面设置方法在物理机的操作系统中根据该第一个性化镜像创建容器，有效地提高了数据可视化界面的管理效率。
在一些可能的设计中，根据该第一个性化镜像在该物理机的第一虚拟机的操作系统中创建该第一容器。
该云桌面设置方法在虚拟机的操作系统中根据该第一个性化镜像创建容器，有效地提高了数据可视化界面的管理效率。同时，利用虚拟机更好地实现了物理隔离。
在一些可能的设计中，接收第二云桌面发放请求，该第二云桌面发放请求携带有第二客户端的验证信息和该第二客户端的云桌面个性化数据，其中该第二客户端的云桌面个性化数据用于指示该第二客户端需要使用的云桌面应用；根据该第二客户端的云桌面个性化数据设置提供第二云桌面的第二容器，根据该第二客户端的验证信息在该第二容器与该第二客户端之间设置第二通信通道，其中，该第二客户端经由该第二通信通道访问该第二容器提供的第二桌面云环境。
在一些可能的设计中，根据该第二客户端的云桌面个性化数据，确定该第二客户端所需的第三云桌面应用和第四云桌面应用；在镜像库中选择设置有该第三云桌面应用的第三镜像和设置有该第四云桌面应用的第四镜像；根据该第三镜像和该第四镜像设置第二个性化镜像；根据该第二个性化镜像在该物理机的操作系统中创建该第二容器。
在一些可能的设计中，根据该第二个性化镜像在该物理机的第二虚拟机的操作系统中安装该第二容器，该第一虚拟机与该第二虚拟机在该物理机中相互隔离。
本申请的第二方面提供了一种云桌面管理系统数据可视化界面管理系统，该系统用于执行第一方面提供的方法。具体的，该系统包括交互模块和处理模块。该交互模块，用于接收第一云桌面发放请求，该第一云桌面发放请求携带有第一客户端的验证信息和该第一客户端的云桌面个性化数据，其中该第一客户端的云桌面个性化数据用于指示该第一客户端需要使用的云桌面应用用户发送的业务请求；该处理单元，用于根据该第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器；根据该第一客户端的验证信息在该第一容器与该第一客户端之间设置第一通信通道，其中，该第一客户端经由该第一通信通道访问该第一容器提供的第一桌面云环境业务请求创建虚拟机和容器，该容器运行在该虚拟机上。
在一些可能的设计中，该处理模块，还用于根据该第一客户端的云桌面个性化数据，确定该第一客户端所需的第一云桌面应用和第二云桌面应用；在镜像库中选择设置有该第一云桌面应用的第一镜像和设置有该第二云桌面应用的第二镜像；根据该第一镜像和该第二镜像设置第一个性化镜像；根据该第一个性化镜像在物理机中创建该第一容器。
在一些可能的设计中，该处理模块，还用于根据该第一个性化镜像在该物理机的操作系统中创建该第一容器。
在一些可能的设计中，该处理模块，还用于根据该第一个性化镜像在该物理机的第一虚拟机的操作系统中创建该第一容器。
在一些可能的设计中，该交互模块，还用于接收第二云桌面发放请求，该第二云桌面发放请求携带有第二客户端的验证信息和该第二客户端的云桌面个性化数据，其中该第二客户端的云桌面个性化数据用于指示该第二客户端需要使用的云桌面应用；该处理模块，还用于根据该第二客户端的云桌面个性化数据设置提供第二云桌面的第二容器，根据该第二客户端的验证信息在该第二容器与该第二客户端之间设置第二通信通道，其中，该第二客户端经由该第二通信通道访问该第二容器提供的第二桌面云环境。
在一些可能的设计中，该处理模块，还用于根据该第二客户端的云桌面个性化数据，确定该第二客户端所需的第三云桌面应用和第四云桌面应用；在镜像库中选择设置有该第三云桌面应用的第三镜像和设置有该第四云桌面应用的第四镜像；根据该第三镜像和该第四镜像设置第二个性化镜像；根据该第二个性化镜像在该物理机的操作系统中创建该第二容器。
在一些可能的设计中，该处理模块，还用于根据该第二个性化镜像在该物理机的第二虚 拟机的操作系统中安装该第二容器，该第一虚拟机与该第二虚拟机在该物理机中相互隔离。
本申请的第三方面提供了一种计算设备集群，该集群包括至少一个计算设备，每个计算设备包括处理器和存储器。该至少一个计算设备的处理器用于执行该存储器中存储的指令，以使得该计算设备集群执行如第一方面或第一方面的任一种实现方式的方法。
本申请的第四方面提供了一种包含指令的计算机程序产品，当该指令在计算机设备集群上运行时，使得该计算机设备集群执行上述第一方面或第一方面的任一种实现方式的方法。
本申请的第五方面提供了一种计算机可读存储介质，该计算机可读存储介质包括计算机程序指令，当该计算机程序指令由计算设备集群执行时，该计算设备集群执行如第一方面或第一方面的任一种实现方式的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请涉及的一种云桌面管理系统的示意图；
图2是本申请涉及的一种云桌面设置方法的流程图；
图3是本申请涉及的一种云桌面管理界面的示意图；
图4是本申请涉及的一种容器管理的示意图；
图5是本申请涉及的一种容器镜像设置方法的示意图；
图6是本申请涉及的另一种容器镜像设置方法的示意图；
图7是本申请涉及的另一种云桌面设置方法的示意图；
图8是本申请涉及的一种容器创建的结构示意图；
图9是本申请涉及的一种云桌面管理系统的结构示意图；
图10是本申请涉及的一种计算设备的示意图；
图11是本申请涉及的一种计算设备集群的示意图；
图12是本申请涉及的另一种计算设备集群的示意图；
图13是本申请涉及的另一种计算设备集群的示意图。
具体实施方式
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解，这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。
图1示出了本申请提供的一种云桌面设置方法100的应用场景。如图所示，与云桌面管理系统200相连的有资源池和至少一个租户。其中，所述资源池包括多个物理机，每一物理机上包括有计算资源、存储资源和网络资源等。常见的物理机有服务器和个人电脑(personal computer，PC)等。
云桌面管理系统200在接受到租户发出的云桌面发放请求后，根据所述请求在所述资源池中创建容器(container)，所述容器用于运行/提供云桌面。考虑到容器具有启动速度快的优势，基于容器创建/运行云桌面可以有效地提升云桌面的发放效率。
在一些可能的实现方式中，还可以根据请求创建虚拟机(virtual machine,VM)。其中， 每一虚拟机中可以运行有一个或多个容器。通常来说，一个虚拟机对应一类租户，而一个容器对应一个租户。也即，通过创建虚拟机可以实现不同类别租户之间的隔离，进一步地提升发放的云桌面的安全性。
接下来结合图2对云桌面设置方法100的流程进行介绍。
S100：云桌面管理系统200接收租户的云桌面发放请求。
云桌面管理系统200根据租户发出的云桌面发放请求，进行云桌面的发放。
通常来说，云桌面管理系统200部署在远端，租户侧的终端设备通过桌面通信协议与云桌面管理系统200侧的容器进行通信。租户经由租户侧的终端设备上的客户端访问与之对应的云桌面。其中，云桌面是由与租户侧的终端设备上的客户端对应的容器提供的。此外，因租户的操作产生/更新的数据均保存在云桌面所在的容器中。这是因为在前述桌面通信协议中，租户侧的客户端仅提供显示、音频播放和键鼠交互等功能。也即，不对租户的数据进行传输或存储，以保证数据的安全性。
在一些可能的实现方式中，在客户端和服务端中对称地分别部署有一个桌面通信模块。具体地，客户端和服务端通过各自包含的桌面通信模块，基于桌面通信协议进行数据传输。
在一些可能的实现方式中，租户发出的云桌面发放请求还携带有验证信息。其中，所述验证信息为客户端的验证信息。具体地，客户端的验证信息包括客户端的鉴权信息、客户端的互联网协议地址(Internet Protocol Address，IPA)和客户端的类型等信息。
可选的，客户端验证信息还包括租户的身份信息，例如，租户所在的企业和部门等。
因此，客户端的验证信息可以用于在所述客户端对应的容器与所述客户端之间设置通信通道。进一步地，所述客户端经由所述通信通道访问所述客户端对应的容器提供的桌面云环境。具体的设置和访问过程将在下文中进行详细介绍。
在一些可能的实现方式中，租户发出的云桌面发放请求还携带有云桌面个性化数据。其中，云桌面个性化数据包括下述的一种或多种：操作系统的账户名和密码、需要运行在云桌面上的应用名称、需要运行在云桌面上的应用的镜像文件、应用的账户名和密码等。上述的云桌面个性化数据也是通过桌面通信协议进行传输。
在一些可能的实现方式中，本申请采用的桌面通信协议为独立计算架构(independent computing architecture,ICA)、远程桌面协议(remote desktop protocol,RDP)、独立计算环境协议(simple protocol for independent computing environment,SPICE)和华为桌面协议(huawei desktop protocol,HDP)等常见的桌面通信协议中的一种。
S102：云桌面管理系统200根据发放请求发放虚拟机。
根据S100中接收到的租户发出的云桌面发放请求，管理员可以利用云桌面管理系统200进行虚拟机的发放。
图3示出了一种云桌面管理界面300。
在接收到租户发出的云桌面发放请求后，管理员可以在任务清单控件302中查看该云桌面发放请求。如图3所示，云桌面管理系统200已经接收到13个云桌面发放请求，且尚未处理。管理员可以通过点击“待发放请求”字样前的数字，展开这13个云桌面发放请求(未在图3中示出)。进一步地，管理员可以在多个请求中通过点击的方式选择一个请求进行处理。
需要说明的是，上述管理员可以是在公有云场景下云厂商的运维人员，也可以是租户所 在企业的运维人员。
当管理员选择了一个请求之后，管理员可以对该请求进行响应。具体地，管理员可以进行容器的发放操作。可选的，还可以进行虚拟机的发放。
具体地，管理员首先在物理机选择控件308中从资源池中选择一个物理机，所述选择的物理机用于运行云桌面实例。如图3所示，资源池中至少包括4台物理机。管理员在下拉列表中选择了一台物理机后，可以在左侧的信息展示控件304中获得该物理机的基本信息。具体地，信息展示控件304中展示有物理机的部署地区、计算资源、存储资源、网络资源和互联网协议(Internet Protocol,IP)地址。
可选的，在物理机选择控件308中选择了一台物理机后，可以在虚拟机选择控件310中选择一台虚拟机。同理，在选择了一台虚拟机后，左侧的信息展示控件304中将展示所述被选择的虚拟机的基本信息(未在图3中示出)。该基本信息包括虚拟机的部署地区、计算资源、存储资源、网络资源和互联网协议(Internet Protocol,IP)地址。
需要说明的是，在物理机选择控件308中选择了一台物理机后，虚拟机选择控件310中展示虚拟机均为运行在所述选择的物理机上。也即，如图3所示，物理机1上至少运行有VM1、VM2和VM3。
在一些可能的实现方式中，在接收到租户的云桌面发放请求后，选择的物理机上尚未运行虚拟机时，可以首先通过点击增加按钮进行虚拟机的发放。进一步地，从发放的虚拟机中选择一台用于运行云桌面。具体地，在对虚拟机进行新增时，需要对虚拟机包括的参数进行设置。例如，虚拟机包括的计算资源、存储资源、网络资源以及内核(kernel)。具体的对虚拟机参数的设置的界面未在图3中示出。
需要说明的是，通过点击增加按钮进行虚拟机的发放操作是基于虚拟机发放服务进行的。
在一些可能的实现方式中，租户还可以在任务清单控件302中查看历史发放记录。其中，历史发放记录可以包括历史发放的云桌面实例所在的物理机的编号和虚拟机的编号。通过查看历史发放记录，可以为响应待发放请求提供参考。
在一些可能的实现方式中，同一虚拟机上通常运行有同一类租户的云桌面。例如，在同一家公司中，相同部门的员工的云桌面可以运行在同一虚拟机上。具体地，如何将相同部门的员工的云桌面运行在同一虚拟机上将在S104中进行介绍。
在一些可能的实现方式中，管理员进行虚拟机的发放操作可以不基于租户的发放请求。具体地，管理员可以根据需要预先对各物理机进行划分。也即，预先确定运行在各物理机上的虚拟机的数量和规格。
在一些可能的实现方式中，管理员还可以进行虚拟机的新增和删除操作。
在一些可能的实现方式中，云桌面管理系统200可以自动根据发放请求发放虚拟机。
需要说明的是，S102为可选的步骤。并且，S102的执行时间不必然早于S104。也即，S102可以先于S104被执行，也可以后于S104被执行。可选的，S102和S104可以同时被执行。
S104：云桌面管理系统200根据发放请求发放容器。
根据S100中接收到的租户发出的云桌面发放请求，管理员可以利用云桌面管理系统200进行容器的发放。
在接收到租户发出的云桌面发放请求后，管理员可以在物理机选择控件308中选择一台 物理机。进一步地，管理员可以在容器创建控件312中点击新增按钮实现容器的创建/发放。具体地，上述操作的实现是基于容器发放服务进行的。
在这一类可能的实现方式中，管理员对于云桌面系统的操作指令需要经由管理控制系统，转化为具体容器的创建、删除等操作。
在一些可能的实现方式中，云桌面管理系统200可以自动根据发放请求发放容器。
具体地，图4示出容器管理的架构图。图4示出的架构图中包括运行在管理面侧的管理控制系统控制端401、运行在业务面的管理控制系统代理端402、容器引擎405、虚拟机403和部署在所述虚拟机上的多个系统容器(404A-404C)。
图4示出的管理面接收管理员发出的操作指令后，由运行在管理面侧的管理控制系统控制端401经由虚拟接入网关(virtual access gateway，vAG)路由至具体的虚拟机中的管理控制系统代理端402。与之相对的，运行在业务面侧的管理控制系统代理端402在接收到操作指令后，需要将所述操作指令传递至容器引擎405。此外，管理控制系统代理端402还用于将操作结果返回至管理控制系统控制端401。
容器引擎405在接收到具体的操作指令后，将根据所述操作指令执行创建、删除、启动或停止系统容器(404A-404C)的操作。
虚拟机403用于为多个系统容器提供公共内核，并作为安全隔离的最小单位保证租户间的独立性。
具体地，根据在S100中接收到客户端地云桌面个性化数据，可以确定所述客户端所需要的应用。进一步地，可以从云桌面所在的服务器中获取应用的镜像，并且根据这些镜像设置所述客户端对应的个性化镜像。所述个性化镜像将用于创建/运行所述客户端对应的容器。
在一些可能的实现方式中，应用的镜像也可以从容器镜像仓库中获取。其中，容器镜像仓库用于存储容器镜像。如图5所示，容器引擎可导入容器仓库中的容器镜像，让第一容器使用该容器镜像，第一容器也可以将图6中的统一视图层作为新的容器镜像发布到容器镜像仓库中，让其他容器可以使用到该容器镜像。容器镜像功能可以让容器用户快速地通过镜像仓库将自己的容器镜像部署到不同的运行环境中。从容器镜像仓库获取了应用的镜像后，可以根据多个应用的镜像设置客户端对应的个性化镜像。
其中，图6中的容器镜像层为一个可供多个第一容器-3共享的容器镜像，容器层为每个容器独有，统一视图层挂载到每个容器的特定目录下，统一视图层叠加了容器层和容器镜像层的内容。针对一个第一容器，当第一容器读取挂载到特定目录下的文件1，此时直接读取容器镜像层的文件1即可。当第一容器对特定目录下的文件2写入数据，此时容器镜像层的文件2被复制到容器层中，在容器层中的文件2被写入数据，容器镜像层的文件2不会被修改。文件3同文件1，当第一容器要在特定目录下创建文件4，此时文件4会创建在容器层中，容器镜像层不会被修改。
基于上述容器镜像叠加技术，可以根据客户端对应的云桌面个性化数据叠加不同的容器镜像，从而快速地组装出一个设置有租户所需的所有应用的个性化容器镜像。并基于所述个性化容器镜像为租户提供云桌面。
在一些可能的实现方式中，容器可以运行在物理机的操作系统上，而非虚拟机的操作系统上。在这一可能的实现方式中，物理机上运行有容器引擎。
需要说明的是，上述物理机的操作系统包括常见的操作系统，例如，windows、unix、linux 和mac等。也即，云桌面管理系统200可以根据客户端对应的个性化镜像在所述物理机的操作系统中创建容器。
在这一可能的实现方式中，同一物理机上通常运行有同一类租户的云桌面。例如，在同一家公司中，相同部门的员工的云桌面可以运行在同一物理机上。从而保证不同部门之间的数据相互隔离，保证云桌面数据的安全性。
在一些可能的实现方式中，容器可以运行在虚拟机的操作系统上，而非直接运行在物理机的操作系统上。在这一可能的实现方式中，一个虚拟机上运行有至少一个容器。其中，每一虚拟机中还包括容器引擎和交互模块。而交互模块用于实现虚拟机内核与容器之间的交互。同时，为了实现与虚拟机的交互，每一容器的内部包含一个交互代理，所述交互代理用于实现容器与虚拟机的数据传输。
需要说明的是，上述虚拟机的操作系统与物理机的操作系统类似。例如，windows、unix、linux和mac等。也即，云桌面管理系统200可以根据客户端对应的个性化镜像在所述虚拟机的操作系统中创建容器。
在这一可能的实现方式中，通常一个容器用于运行一个租户的云桌面。也即，一个容器对应一个租户。而一个虚拟机中包含多个容器，因此一个虚拟机可以对应多个同类型的租户。例如，对于一个公司的云桌面管理系统而言，相同部门的租户可以被认为是同类型的租户。因此，将不同部门的租户的云桌面运行在不同的虚拟机上，有效地实现了不同类型租户之间的隔离，提升了系统的安全性。
在上述的几种实现方式中，容器中的操作系统通常是基于linux内核的操作系统。例如，统信操作系统(unity operating system，UOS)是2019年开发的，是一款基于linux的操作系统。类似的还有社区企业操作系统(community enterprise operating system,CentOS)以及Debain等。其中，前述的操作系统都是以镜像的形式存在容器中的。
在一些可能的实现方式中，管理员还可以根据需要对页面接口组件(web interface，WI)、单一名称服务(Unified Name Service,UNS)、vAG、虚拟负载均衡(virtual load balance，vLB)、统一身份认证服务(Identity and Access Management,IAM)等参数进行设置。
其中，WI为云终端用户提供登录界面。用户登录时，WI对用户的合法身份进行认证。UNS是一种支持通过统一的域名访问具有不同WI域名的多套桌面管理系统的服务，减少用户在不同的WI域名间进行的切换和跳转。vAG可以把一个接入网关(access gateway，AG)设备从逻辑上划分成多个虚拟的AG(VAG)，每个VAG可以分别在不同媒体网关控制器的控制下独立工作。vLB主要向租户提供(虚拟)负载均衡服务，用户可以申请负载均衡器，将业务主机关联到负载均衡器。IAM是公有云系统的安全管理服务，提供身份管理、权限分配和访问控制功能。在完成了上述的容器的发放之后，可以利用在S100中接收到的云桌面个性化数据，进行个性化设置。例如，可以将租户的操作系统的账户名和密码，以及租户需要运行在云桌面上的应用预先存储至云桌面系统中。进一步地，租户和完成发放的云桌面可以基于桌面通信协议进行通信。也即，租户可以基于桌面通信协议，使用运行在租户侧的服务端云桌面。
可选的，上述容器还可以是系统容器(system container)。系统容器是以容器技术为基础的轻量级主机虚拟化技术，系统容器提供与虚拟机一致的行为，拥有完整的运行系统，启动完整的操作系统。
相比于传统的应用容器，系统容器可以支持systemd。其中，systemd是Linux系统中的一种初始化系统，它的设计目标是克服现有初始化系统固有的缺点，优化系统的指令逻辑，从而提高系统的启动速度。系统容器引擎由于支持systemd，其在生命周期管理上与虚拟机类似，因此可以实现系统内应用装卸及容器内操作系统启停等功能。
需要说明的是，由于虚拟机内的各个系统容器内没有独立的内核(kernel)，而是共用宿主机的内核，因此需要进行适应性的修改来支持新的容器加宿主机公共内核的新架构，以保证部分内核态功能(例如通用串行总线(universal serial bus，USB))的正常使用。具体地，实现方法为在宿主机的内核中运行容器所需要的内核功能的函数实体，该函数实体通过容器内对应的代理组件实现内外层交互，从而保证部分内核态功能的正常使用。
为便于理解，下面结合具体场景示例对云桌面设置方法100进行详细描述。在一种场景示例中，接入云桌面管理系统200的租户至少包括租户1和租户2。其中，租户1通过第一客户端接入云桌面管理系统200，租户2通过第二客户端接入云桌面管理系统。参阅图7，示出了一种容灾切换方法的流程示意图，该方法具体可以是包括：
S500：云桌面管理系统200接收租户1通过第一客户端发送的第一云桌面请求。
租户1的云桌面发放请求中携带有第一客户端的验证信息和所述第一客户端的云桌面个性化数据，其中，第一客户端的验证信息包括验证信息包括第一客户端的标识鉴权信息和、第一客户端的互联网协议地址(Internet Protocol Address，IPA)和第一客户端的类型等信息。可选的，第一客户端验证信息还包括租户1的身份信息，例如，租户1所在的企业和部门等。第一客户端的云桌面个性化数据包括下述的一种或多种：第一客户端对应的操作系统的账户名和密码、第一客户端中需要运行在云桌面上的应用名称、第一客户端中需要运行在云桌面上的应用的镜像文件、所述应用的账户名和密码等。
S502：云桌面管理系统200根据第一云桌面发放请求发放虚拟机1。
根据S500中接收到的第一云桌面发放请求，管理员可以利用云桌面管理系统200进行虚拟机1的发放。具体地，通过在图3中物理机选择控件308和虚拟机选择控件310中进行选择后，可以实现虚拟机1的发放。
需要说明的是，S502为可选的步骤。并且，S502的执行时间不必然早于S504。也即，S502可以先于S504被执行，也可以后于S504被执行。可选的，S502和S504可以同时被执行。
S504：云桌面管理系统200根据第一云桌面发放请求发放第一容器。
根据S500中接收到的第一云桌面发放请求，管理员可以利用云桌面管理系统200进行第一容器的发放。具体地，通过在图3中物理机选择控件308和容器选择控件312中进行选择后，可以实现第一容器的发放。可选的，还可以通过虚拟机选择控件310对虚拟机进行选择。
如图8所示，为租户1发放的第一容器位于VM1中，而VM1位于物理机1中。
具体地，关于容器的创建过程，下面以租户1对应的第一容器为例进行介绍。
根据在S500中接收到的第一客户端的云桌面个性化数据，可以设置用于提供第一云桌面的第一容器(第一容器)。具体地，根据第一客户端的云桌面个性化数据可以确定需要的应用。
进一步地，可以在远程服务器或镜像仓库中获取应用的镜像。根据获取的应用的镜像，可以获得租户1对应的第一个性化镜像。运行所述第一个性化镜像，即可完成第一容器(第 一容器)的创建。
其中，镜像仓库可以位于云桌面所在的服务器中。可选的，还可以位于第一客户端所在的服务器中。
例如，所述第一客户端所需的应用包括第一云桌面应用和第二云桌面应用。云桌面管理系统200可以在镜像仓库中获取第一云桌面应用的镜像文件和第二云桌面应用的镜像文件，并且根据这两个镜像文件在统一视图层为第一客户端设置第一个性化镜像。
根据在S500中接收到的所述第一客户端的验证信息，可以在所述第一容器与所述第一客户端之间设置第一通信通道，其中，所述第一客户端经由所述第一通信通道访问所述第一容器提供的第一桌面云环境。
在上述的步骤中，基于容器镜像叠加技术，可以根据第一客户端对应的云桌面个性化数据叠加不同的容器镜像，从而快速地组装出一个设置有租户1所需的所有应用的个性化容器镜像。并基于所述个性化容器镜像为租户1提供云桌面。
S506：云桌面管理系统200接收租户2通过第二客户端发送的第二云桌面请求。
类似的，租户2的云桌面发放请求中携带有第二客户端的验证信息和所述第二客户端的云桌面个性化数据，其中，第二客户端的验证信息包括第二客户端的标识鉴权信息和、第二客户端的互联网协议地址(Internet Protocol Address，IPA)和第二客户端的类型等信息。可选的，第二客户端验证信息还包括租户2的身份信息，例如，租户2所在的企业和部门等。第二客户端的云桌面个性化数据包括下述的一种或多种：第二客户端对应的操作系统的账户名和密码、第二客户端中需要运行在云桌面上的应用名称、第二客户端中需要运行在云桌面上的应用的镜像文件、所述应用的账户名和密码等。
S508：云桌面管理系统200根据第二云桌面请求发放虚拟机2。
根据S506中接收到的租户2发出的第二云桌面发放请求，管理员可以利用云桌面管理系统200进行虚拟机2的发放。具体地，通过在图3中物理机选择控件308和虚拟机选择控件310中进行选择后，可以实现虚拟机2的发放。
如图8所示，为租户1发放物理机1中的VM1，为租户2发放物理机1中的VM2。也即，租户1对应的虚拟机和租户2对应的虚拟机属于同一物理机中的不同虚拟机。
其中，租户1和租户2对应的虚拟机是否位于同一物理机是根据租户1和租户2的验证信息确定的。
例如，当租户1的验证信息指示租户1所在企业和租户2的验证信息指示租户2所在企业相同时，可以将租户1和租户2对应的虚拟机创建于同一物理机上。反之，当租户1的验证信息指示租户1所在企业和租户2的验证信息指示租户2所在企业不同时，可以将租户1和租户2对应的虚拟机创建于不同物理机上。
S510：云桌面管理系统200根据第二云桌面请求发放第二容器。
根据S508中接收到的第二云桌面发放请求，管理员可以利用云桌面管理系统200进行第二容器的发放。具体地，通过在图3中物理机选择控件308和容器选择控件312中进行选择后，可以实现第二容器的发放。可选的，还可以通过虚拟机选择控件310对虚拟机进行选择。
租户1和租户2对应的容器是否位于同一物理机或虚拟机上，是根据租户1和租户2的验证信息确定的。
例如，当当租户1的验证信息指示租户1所在的部门和租户2的验证信息指示租户2所 在的部门不同时，可以将租户1和租户2对应的容器分别安装在不同的VM中，其中，VM1和VM2在同一物理机中相互隔离实现了将租户1和租户2对应的容器的相互隔离。
根据在S506中接收到的所述第二客户端的验证信息，可以在所述第二容器(第二容器)与所述第二客户端之间设置第二通信通道，其中，所述第二客户端经由所述第二通信通道访问所述第二容器(第二容器)提供的第二桌面云环境。
需要说明的是，S500至S504这个整体和S506至S510这个整体的执行顺序不分先后。具体地，S500至S504这个整体可以先于S506至S510这个整体被执行，S500至S504这个整体也可以后于S506至S510这个整体被执行。可选的，S500至S504这个整体还可以与S506至S510这个整体同时被执行。
第二容器
上文中结合图1至图8，详细描述了本申请所提供的云桌面设置方法，下面将结合图9至图13，描述根据本申请所提供的装置和计算设备。
本申请还提供一种云桌面管理系统200，如图9所示，包括：
交互单元202，用于在S100中接收云桌面发放请求。在S100中，管理员在图3示出的云桌面管理界面300中基于选择的信息发出的操作指令的接收也是由交互单元202执行。
存储单元204，用于在S100中存储各个物理机的基本信息。进一步地，管理员在S104中发放容器的操作记录，以及发放的容器的基本信息也将被存储在存储单元204中。
可选的，存储单元204还用于在S100中存储各个虚拟机的基本信息。管理员在S102中发放虚拟机的操作记录，以及发放的虚拟机的基本信息也将被存储在存储单元204中。
处理单元206，用于在S102中根据操作指令实现虚拟机的发放。S104中根据操作指令实现容器的发放也是由处理单元206执行的。具体地，在S104中，根据客户端的云桌面个性化数据，确定客户端所需的云桌面应用的操作是由处理单元206执行的。处理单元还用于在S104中在镜像库中选择设置有所述云桌面应用的镜像设置个性化镜像，并且根据所述个性化镜像在物理机中创建容器。
可选的，在S104中根据个性化镜像在物理机的虚拟机的操作系统中创建容器的操作也是由处理单元206执行。
处理单元206，还用于在S104中建立发放的容器与客户端之间的通信通道。
本申请还提供一种计算设备600。如图10所示，计算设备包括：总线602、处理器604、存储器606和通信接口608。处理器604、存储器606和通信接口608之间通过总线602通信。计算设备600可以是服务器或终端设备。应理解，本申请不限定计算设备600中的处理器、存储器的个数。
总线602可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。总线604可包括在计算设备600各个部件(例如，存储器606、处理器604、通信接口608)之间传送信息的通路。
处理器604可以包括中央处理器(central processing unit，CPU)、图形处理器(graphics  processing unit，GPU)、微处理器(micro processor，MP)或者数字信号处理器(digital signal processor，DSP)等处理器中的任意一种或多种。
存储器606可以包括易失性存储器(volatile memory)，例如随机存取存储器(random access memory，RAM)。处理器604还可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器，机械硬盘(hard disk drive，HDD)或固态硬盘(solid state drive，SSD)。存储器606中存储有可执行的程序代码，处理器604执行该可执行的程序代码以实现前述云桌面设置方法100。具体的，存储器406上存有云桌面管理系统200用于执行云桌面设置方法100的指令。
通信接口603使用例如但不限于网络接口卡、收发器一类的收发模块，来实现计算设备600与其他设备或通信网络之间的通信。
本申请实施例还提供了一种计算设备集群。如图11所示，所述计算设备集群包括至少一个计算设备600。计算设备集群中的一个或多个计算设备600中的存储器606中可以存有相同的云桌面管理系统200用于执行云桌面设置方法100的指令。
在一些可能的实现方式中，该计算设备集群中的一个或多个计算设备600也可以用于执行云桌面管理系统200用于执行云桌面设置方法100的部分指令。换言之，一个或多个计算设备600的组合可以共同执行云桌面管理系统200用于执行云桌面设置方法100的指令。
需要说明的是，计算设备集群中的不同的计算设备600中的存储器606可以存储不同的指令，用于执行云桌面管理系统200的部分功能。
图12示出了一种可能的实现方式。如图12所示，两个计算设备600A和600B通过通信接口608实现连接。计算设备600A中的存储器上存有用于执行交互单元202和处理单元206的功能的指令。计算设备600B中的存储器上存有用于执行存储单元204的功能的指令。换言之，计算设备600A和600B的存储器606共同存储了云桌面管理系统200用于执行云桌面设置方法100的指令。
图12所示的计算设备集群之间的连接方式可以是考虑到本申请提供的云桌面设置方法100需要对大量的设备基础信息进行存储。因此，考虑将存储功能交由计算设备600B执行。
应理解，图12中示出的计算设备600A的功能也可以由多个计算设备600完成。同样，计算设备600B的功能也可以由多个计算设备600完成。
在一些可能的实现方式中，计算设备集群中的一个或多个计算设备可以通过网络连接。其中，所述网络可以是广域网或局域网等等。图13示出了一种可能的实现方式。如图13所示，两个计算设备600C和600D之间通过网络进行连接。具体地，通过各个计算设备中的通信接口与所述网络进行连接。在这一类可能的实现方式中，计算设备600C中的存储器606中存有执行交互单元202的指令。同时，计算设备600D中的存储器606中存有执行存储单元204和处理单元206的指令。
图13所示的计算设备集群之间的连接方式可以是考虑到本申请提供的云桌面设置方法100需要对大量的设备基础信息进行存储，和执行大量的云桌面发放操作，因此考虑将存储单元204和处理单元206实现的功能交由计算设备600D执行。
应理解，图13中示出的计算设备600C的功能也可以由多个计算设备600完成。同样，计算设备600D的功能也可以由多个计算设备600完成。
本申请实施例还提供了一种计算机可读存储介质。所述计算机可读存储介质可以是计算设备能够存储的任何可用介质或者是包含一个或多个可用介质的数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘)等。该计算机可读存储介质包括指令，所述指令指示计算设备执行上述应用于云桌面管理系统200用于执行云桌面设置方法100。
本申请实施例还提供了一种包含指令的计算机程序产品。所述计算机程序产品可以是包含指令的，能够运行在计算设备上或被储存在任何可用介质中的软件或程序产品。当所述计算机程序产品在至少一个计算机设备上运行时，使得至少一个计算机设备执行上述云桌面设置方法100。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的保护范围。

Claims (17)

  1. 一种云桌面设置方法，其特征在于，包括：
    接收第一云桌面发放请求，所述第一云桌面发放请求携带有第一客户端的验证信息和所述第一客户端的云桌面个性化数据，其中所述第一客户端的云桌面个性化数据用于指示所述第一客户端需要使用的云桌面应用；
    根据所述第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器；
    根据所述第一客户端的验证信息在所述第一容器与所述第一客户端之间设置第一通信通道，其中，所述第一客户端经由所述第一通信通道访问所述第一容器提供的第一桌面云环境。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器，包括：
    根据所述第一客户端的云桌面个性化数据，确定所述第一客户端所需的第一云桌面应用和第二云桌面应用；
    在镜像库中选择设置有所述第一云桌面应用的第一镜像和设置有所述第二云桌面应用的第二镜像；
    根据所述第一镜像和所述第二镜像设置第一个性化镜像；
    根据所述第一个性化镜像在物理机中创建所述第一容器。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述第一个性化镜像在物理机中创建所述第一容器，包括：
    根据所述第一个性化镜像在所述物理机的操作系统中创建所述第一容器。
  4. 根据权利要求2所述的方法，其特征在于，所述根据所述个性化镜像在物理机中创建所述第一容器，包括：
    根据所述第一个性化镜像在所述物理机的第一虚拟机的操作系统中创建所述第一容器。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    接收第二云桌面发放请求，所述第二云桌面发放请求携带有第二客户端的验证信息和所述第二客户端的云桌面个性化数据，其中所述第二客户端的云桌面个性化数据用于指示所述第二客户端需要使用的云桌面应用；
    根据所述第二客户端的云桌面个性化数据设置提供第二云桌面的第二容器，根据所述第二客户端的验证信息在所述第二容器与所述第二客户端之间设置第二通信通道，其中，所述第二客户端经由所述第二通信通道访问所述第二容器提供的第二桌面云环境。
  6. 根据权利要求5所述的方法，其特征在于，所述根据所述第二客户端的云桌面个性化数据设置提供第二云桌面的第二容器，包括：
    根据所述第二客户端的云桌面个性化数据，确定所述第二客户端所需的第三云桌面应用 和第四云桌面应用；
    在镜像库中选择设置有所述第三云桌面应用的第三镜像和设置有所述第四云桌面应用的第四镜像；
    根据所述第三镜像和所述第四镜像设置第二个性化镜像；
    根据所述第二个性化镜像在所述物理机的操作系统中创建所述第二容器。
  7. 根据权利要求6所述的方法，其特征在于，所述根据所述第二个性化镜像在物理机中创建所述第二容器，包括：
    根据所述第二个性化镜像在所述物理机的第二虚拟机的操作系统中安装所述第二容器，所述第一虚拟机与所述第二虚拟机在所述物理机中相互隔离。
  8. 一种云桌面管理系统，其特征在于，包括：
    交互模块，用于接收第一云桌面发放请求，所述第一云桌面发放请求携带有第一客户端的验证信息和所述第一客户端的云桌面个性化数据，其中所述第一客户端的云桌面个性化数据用于指示所述第一客户端需要使用的云桌面应用；
    处理模块，用于根据所述第一客户端的云桌面个性化数据设置提供第一云桌面的第一容器；根据所述第一客户端的验证信息在所述第一容器与所述第一客户端之间设置第一通信通道，其中，所述第一客户端经由所述第一通信通道访问所述第一容器提供的第一桌面云环境。
  9. 根据权利要求8所述的系统，其特征在于，所述处理模块，还用于根据所述第一客户端的云桌面个性化数据，确定所述第一客户端所需的第一云桌面应用和第二云桌面应用；在镜像库中选择设置有所述第一云桌面应用的第一镜像和设置有所述第二云桌面应用的第二镜像；根据所述第一镜像和所述第二镜像设置第一个性化镜像；根据所述第一个性化镜像在物理机中创建所述第一容器。
  10. 根据权利要求9所述的系统，其特征在于，所述处理模块，还用于根据所述第一个性化镜像在所述物理机的操作系统中创建所述第一容器。
  11. 根据权利要求9所述的系统，其特征在于，所述处理模块，还用于根据所述第一个性化镜像在所述物理机的第一虚拟机的操作系统中创建所述第一容器。
  12. 根据权利要求10所述的系统，其特征在于，所述交互模块，还用于接收第二云桌面发放请求，所述第二云桌面发放请求携带有第二客户端的验证信息和所述第二客户端的云桌面个性化数据，其中所述第二客户端的云桌面个性化数据用于指示所述第二客户端需要使用的云桌面应用；所述处理模块，还用于根据所述第二客户端的云桌面个性化数据设置提供第二云桌面的第二容器，根据所述第二客户端的验证信息在所述第二容器与所述第二客户端之间设置第二通信通道，其中，所述第二客户端经由所述第二通信通道访问所述第二容器提供的第二桌面云环境。
  13. 根据权利要求12所述的系统，其特征在于，所述处理模块，还用于根据所述第二客户端的云桌面个性化数据，确定所述第二客户端所需的第三云桌面应用和第四云桌面应用；在镜像库中选择设置有所述第三云桌面应用的第三镜像和设置有所述第四云桌面应用的第四镜像；根据所述第三镜像和所述第四镜像设置第二个性化镜像；根据所述第二个性化镜像在所述物理机的操作系统中创建所述第二容器。
  14. 根据权利要求13所述的系统，其特征在于，所述处理模块，还用于根据所述第二个性化镜像在所述物理机的第二虚拟机的操作系统中安装所述第二容器，所述第一虚拟机与所述第二虚拟机在所述物理机中相互隔离。
  15. 一种计算设备集群，其特征在于，包括至少一个计算设备，每个计算设备包括处理器和存储器；
    所述至少一个计算设备的处理器用于执行所述至少一个计算设备的存储器中存储的指令，以使得所述计算设备集群执行如权利要求1至7中任一所述的方法。
  16. 一种包含指令的计算机程序产品，其特征在于，当所述指令被计算机设备集群运行时，使得所述计算机设备集群执行如权利要求的1至7中任一所述的方法。
  17. 一种计算机可读存储介质，其特征在于，包括计算机程序指令，当所述计算机程序指令由计算设备集群执行时，所述计算设备集群执行如权利要求1至7中任一所述的方法。
PCT/CN2022/094655 2021-06-03 2022-05-24 一种云桌面设置方法、系统及设备 WO2022253044A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110620379 2021-06-03
CN202110620379.6 2021-06-03
CN202111092817.2A CN115437728A (zh) 2021-06-03 2021-09-17 一种云桌面设置方法、系统及设备
CN202111092817.2 2021-09-17

Publications (1)

Publication Number Publication Date
WO2022253044A1 true WO2022253044A1 (zh) 2022-12-08

Family

ID=84271860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/094655 WO2022253044A1 (zh) 2021-06-03 2022-05-24 一种云桌面设置方法、系统及设备

Country Status (2)

Country Link
CN (1) CN115437728A (zh)
WO (1) WO2022253044A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888485A (zh) * 2012-12-19 2014-06-25 华为技术有限公司 云计算资源的分配方法、装置及系统
CN109960551A (zh) * 2017-12-26 2019-07-02 中国电信股份有限公司 云桌面服务方法、平台和计算机可读存储介质
WO2020020154A1 (zh) * 2018-07-23 2020-01-30 中兴通讯股份有限公司 云桌面离线管理的方法、设备和存储介质
CN110851224A (zh) * 2019-11-11 2020-02-28 西安雷风电子科技有限公司 一种基于容器的idv云桌面的智能切换系统及方法
CN111290815A (zh) * 2020-01-21 2020-06-16 湖南麒麟信安科技有限公司 融合共享用户环境、容器和虚拟机的多模式虚拟桌面的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888485A (zh) * 2012-12-19 2014-06-25 华为技术有限公司 云计算资源的分配方法、装置及系统
CN109960551A (zh) * 2017-12-26 2019-07-02 中国电信股份有限公司 云桌面服务方法、平台和计算机可读存储介质
WO2020020154A1 (zh) * 2018-07-23 2020-01-30 中兴通讯股份有限公司 云桌面离线管理的方法、设备和存储介质
CN110851224A (zh) * 2019-11-11 2020-02-28 西安雷风电子科技有限公司 一种基于容器的idv云桌面的智能切换系统及方法
CN111290815A (zh) * 2020-01-21 2020-06-16 湖南麒麟信安科技有限公司 融合共享用户环境、容器和虚拟机的多模式虚拟桌面的方法及系统

Also Published As

Publication number Publication date
CN115437728A (zh) 2022-12-06

Similar Documents

Publication Publication Date Title
US9367947B2 (en) Remote rendering of three-dimensional images using virtual machines
JP6771650B2 (ja) クラウドコンピューティングシステムにおいて仮想マシンが物理サーバにアクセスするための方法、装置、およびシステム
US10013421B2 (en) Trusted file indirection
US9213568B2 (en) Assigning states to cloud resources
US8924703B2 (en) Secure virtualization environment bootable from an external media device
US8413142B2 (en) Storage optimization selection within a virtualization environment
US8887227B2 (en) Network policy implementation for a multi-virtual machine appliance within a virtualization environtment
US9052940B2 (en) System for customized virtual machine for a target hypervisor by copying image file from a library, and increase file and partition size prior to booting
US20110276661A1 (en) Methods and systems for delivering applications from a desktop operating system
WO2010100769A1 (ja) セキュリティ管理装置及び方法
JP2019500666A (ja) マシンレベルアイソレーションを有するマルチテナントマルチセッションカタログ
JP2018523192A (ja) 分散型コンピューティング環境における仮想マシンインスタンス上のコマンドの実行
JP7379517B2 (ja) セキュア・インターフェース制御セキュア・ストレージ・ハードウェアのタグ付け方法、システム、プログラム
US11159367B2 (en) Apparatuses and methods for zero touch computing node initialization
US20150346931A1 (en) Method and System for Managing Peripheral Devices for Virtual Desktops
CN111090498B (zh) 虚拟机启动方法、装置、计算机可读存储介质及电子设备
KR101680702B1 (ko) 클라우드 기반 웹 호스팅 시스템
Alani et al. What is the Cloud?
WO2020247235A1 (en) Managed computing resource placement as a service for dedicated hosts
US20130238673A1 (en) Information processing apparatus, image file creation method, and storage medium
JP5606476B2 (ja) クライアント管理システム、クライアント管理方法及びプログラム
JP5951002B2 (ja) 選択的ポリシーによるホストと複数のゲストとの間での構成要素伝播の実現
US10979289B2 (en) Apparatuses and methods for remote computing node registration and authentication
US11360824B2 (en) Customized partitioning of compute instances
WO2022253044A1 (zh) 一种云桌面设置方法、系统及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22815091

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE