WO2021051534A1 - 云主机创建方法和系统 - Google Patents

云主机创建方法和系统 Download PDF

Info

Publication number
WO2021051534A1
WO2021051534A1 PCT/CN2019/117136 CN2019117136W WO2021051534A1 WO 2021051534 A1 WO2021051534 A1 WO 2021051534A1 CN 2019117136 W CN2019117136 W CN 2019117136W WO 2021051534 A1 WO2021051534 A1 WO 2021051534A1
Authority
WO
WIPO (PCT)
Prior art keywords
plug
cloud platform
control server
delivery control
file
Prior art date
Application number
PCT/CN2019/117136
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 WO2021051534A1 publication Critical patent/WO2021051534A1/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/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482—Procedural
    • 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

Definitions

  • This application relates to a method and system for creating a cloud host.
  • Citrix XenDesktop (XenDesktop) is a set of desktop virtualization solutions that can transform Windows desktops and applications into an on-demand service that can be delivered to any user at any location and using any device, providing all the business needs of users Complete virtual application and desktop solutions. While reducing IT costs, employees can work freely anytime, anywhere. Citrix XenDesktop can deliver Windows desktops and applications from any cloud (public cloud, on-premises or hybrid cloud) in the modern digital workspace.
  • Citrix XenDesktop mainly include servers from foreign service providers such as Citrix, Microsoft, and Verizon. Therefore, compared with domestic cloud service providers, when you need to use Citrix XenDesktop virtual desktops, you can only virtualize the virtual desktops to the virtualization platforms of foreign providers by connecting to the servers provided by the above-mentioned foreign service providers. . Not only does it increase its own operation and maintenance costs, but also because the servers provided by foreign suppliers are not applicable to all platforms, the scope of application is relatively narrow.
  • a method and system for creating a cloud host are provided.
  • a method for creating a cloud host includes:
  • the desktop delivery control server receives the cloud host creation instruction carrying the cloud platform identifier and the resource identifier sent by the terminal;
  • the desktop delivery control server calls the docking plug-in in response to the cloud host creation instruction, and calls the corresponding cloud platform interface according to the cloud platform identification through the docking plug-in, and sends the resource identification to the corresponding cloud platform;
  • the cloud platform obtains corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
  • a cloud host creation system includes:
  • the terminal is used to generate a creation instruction carrying a cloud platform identifier and a resource identifier, and send the creation instruction to the desktop delivery control server;
  • the desktop delivery control server is used to receive the cloud host creation instruction carrying the cloud platform identifier and the resource identifier sent by the terminal; call the docking plug-in, and call the corresponding cloud platform interface through the docking plug-in according to the cloud platform identifier
  • the resource identifier is sent to the corresponding cloud platform;
  • the cloud platform is used to obtain corresponding resource data according to the resource identifier, and create a corresponding cloud host based on the resource data.
  • Fig. 1 is an application scenario diagram of a method for creating a cloud host according to one or more embodiments.
  • Fig. 2 is a schematic flowchart of a method for creating a cloud host according to one or more embodiments.
  • Fig. 3 is a schematic flowchart of a method for creating a cloud host in another embodiment.
  • Fig. 4 is a schematic flowchart of completing the registration steps of the connector according to the registration instruction according to one or more embodiments.
  • Fig. 5 is a sequence diagram of a method for creating a cloud host according to one or more embodiments.
  • the method for creating a cloud host can be applied to the application environment as shown in FIG. 1.
  • the terminal 102 communicates with the desktop delivery control server 104 through the network, and the desktop delivery control server 104 communicates with the cloud platform 106 through the network.
  • the terminal 102 generates a creation instruction carrying a cloud platform identifier and a resource identifier, and sends the creation instruction to the desktop delivery control server 104.
  • the desktop delivery control server 104 receives the cloud host creation instruction carrying the cloud platform identification and resource identification sent by the terminal; calls the docking plug-in, and calls the corresponding cloud platform interface according to the cloud platform identification through the docking plug-in, and sends the resource identification to the corresponding cloud platform 106.
  • the cloud platform 106 obtains corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
  • the terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
  • the desktop delivery control server 104 may be implemented by an independent server or a server cluster composed of multiple servers.
  • a method for creating a cloud host which includes the following steps:
  • Step S202 The desktop delivery control server receives the cloud host creation instruction that carries the cloud platform identifier and the resource identifier sent by the terminal.
  • the desktop delivery controller is a DDC (Desktop Delivery Controller) server of the Citrix XenDesktop side
  • the terminal is a computer device with a DDC server installed.
  • the cloud host creation instruction is a request used by the terminal to instruct the DDC server to create a cloud host.
  • the cloud platform identifier is the unique identifier of the cloud platform and is used to identify the corresponding cloud platform.
  • the cloud host creation instruction refers to an instruction used to instruct the DDC server to create a cloud host on the corresponding cloud platform.
  • the resource identifier is the unique identifier of the resource data required to create the cloud platform resource. Identification includes but is not limited to ID (Identity, identification number), number, name, etc.
  • the cloud host creation instruction is an instruction triggered by the user on the terminal to instruct the DDC server to create a cloud host on the corresponding cloud platform.
  • Cloud hosting is a virtualization technology similar to VPS hosting (Virtual Private Server).
  • VPS uses virtualization software to virtualize multiple parts similar to independent Part of it can be a separate operating system, and the management method is the same as that of the host.
  • the cloud host virtualizes multiple parts similar to independent hosts on a group of cluster hosts. Each host in the cluster has an image of the cloud host, which greatly improves the security and stability of the virtual host, unless all clusters are If all the hosts have problems, the cloud host cannot be accessed.
  • the cloud platform is a platform that provides cloud computing services. It provides a virtual environment for countless sites through countless physical hosts. It can be understood that the cloud host in this embodiment is a virtual host from the cluster hosts provided by the cloud platform.
  • the user selects the cloud platform identifier of the cloud platform that creates the cloud host and the resource identifier of the required resource data through the operating terminal.
  • the terminal After receiving the user's selected cloud platform identification and resource identification, the terminal generates a cloud host creation instruction. And the cloud platform identifier and resource identifier are sent to the DDC server along with the created cloud host creation instruction.
  • step S204 the desktop delivery control server calls the docking plug-in in response to the cloud host creation instruction, and calls the corresponding cloud platform interface according to the cloud platform identification through the docking plug-in, and sends the resource identification to the corresponding cloud platform.
  • a plug-in is a program written in compliance with a certain standard application program interface
  • a docking plug-in is a program used to interface with the DDC server and cloud platform.
  • the traditional DDC server receives the cloud host creation instruction, it creates the corresponding cloud host in the virtual cloud platform of the cooperating foreign service provider.
  • domestic service providers who have not cooperated, they cannot create a cloud host on their own cloud platform by sending a create cloud host instruction to the DDC server. Therefore, in this embodiment, the docking between the DDC server and the cloud platform is realized through the written docking program.
  • the cloud platform interface refers to the API interface (Application Programming Interface) of the cloud platform.
  • the DDC server After the DDC server receives the instruction to create a cloud host, it calls the docking plug-in pre-deployed in the DDC server, and docks with the cloud platform corresponding to the cloud platform identifier through the docking plug-in.
  • the docking plug-in determines the cloud platform to be docked according to the cloud platform identifier, and then calls the pre-appointed API interface of the cloud platform, and sends the resource identifier to the cloud platform through the API interface.
  • Step S206 The cloud platform obtains corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
  • Resource data includes network resources, template mirroring resources, storage resources, computing solution resources, etc.
  • the desktop delivery control server receives the cloud host creation instruction carrying the cloud platform identifier and the resource identifier sent by the terminal, and then calls the docking plug-in in response to the cloud host creation instruction. This ensures that the desktop delivery control server calls plug-ins on demand according to instructions and saves resources.
  • the desktop delivery control server uses the docking plug-in to call the cloud platform interface of the cloud platform identification, and sends the resource identification to the cloud platform, thereby ensuring that the desktop delivery control server is connected to the cloud platform through the docking plug-in.
  • the cloud platform obtains the corresponding resource data according to the resource identifier, and completes the creation of the cloud host according to the resource data, thereby ensuring that the virtual cloud host of the virtual cloud platform can be created on Citrix XenDesktop. Realize the independent creation of cloud hosts on the cloud platform, expand the scope of application, and reduce the cost of operation and maintenance.
  • step S206 the cloud platform obtains corresponding resource data according to the resource identifier, and after creating the corresponding cloud host based on the resource data, the following steps are further included:
  • Step S208 The desktop delivery control server obtains the cloud host information of the created cloud host, calls the docking plug-in, and sends a disk resource creation instruction carrying the cloud host information to the cloud platform.
  • the disk resource creation instruction is used to request the corresponding cloud platform to create a disk instruction, and the created disk is used to store cloud host information.
  • the DDC server obtains the cloud host information of the created cloud host.
  • a disk creation instruction is generated, and the docking plug-in is called to send the obtained cloud host information along with the disk creation instruction to the corresponding cloud platform.
  • Cloud host information includes host ID (host number), host name, DDC address corresponding to the host, and domain control information.
  • step S210 the cloud platform responds to the disk resource creation instruction to create a disk with a preset capacity.
  • step S212 the cloud platform writes the cloud host information into the preset capacity disk, and mounts the preset capacity disk to the disk service cloud host.
  • the preset capacity disk refers to a disk with a preset capacity.
  • the preset capacity disk may be a 1GB disk.
  • Disk service cloud host refers to a cloud host that is pre-deployed in the cloud platform to manage the identity disk of the cloud host.
  • the disk service cloud host is developed based on the Golang language.
  • the cloud platform after the cloud platform receives the disk resource creation instruction sent by the DDC server calling the docking plug-in, in response to the disk resource creation instruction, the cloud platform calls the disk service cloud host to create a disk with a capacity of 1GB. Then, write the cloud host information into the created 1GB disk, and mount the disk to the disk server cloud host. Or, when the cloud platform receives the disk resource creation instruction sent by the DDC server calling the docking plug-in, and responds to the disk resource creation instruction to create a 1GB disk, first mount the disk to the disk service cloud host, and then install the cloud The host information is written to the disk. You can write the cloud host information to the disk through the Linux dd command.
  • step S214 the docking plug-in associates the preset capacity disk with the cloud host information written into the corresponding cloud host by identification.
  • the cloud host when the cloud host information of the cloud host has been written into the created preset capacity disk, the cloud host is identified and associated with the preset capacity disk, so as to establish the association between the disk and the cloud host.
  • the identification association can be understood as binding or mapping the disk ID (disk number) of the preset capacity disk and the host ID of the cloud host.
  • step S202 before the desktop delivery control server receives the cloud host creation instruction carrying the cloud platform identifier and the resource identifier sent by the terminal, it further includes the step of registering the docking plug in the desktop delivery control server.
  • Registering the docking plug-in in the desktop delivery control server includes the following steps:
  • Step S1 the desktop delivery control server receives the registration instruction sent by the terminal.
  • the registration instruction refers to an instruction used to instruct the desktop delivery control server to complete the registration of the docking plug-in. Specifically, the user generates a registration instruction by operating the terminal, and the terminal sends the registration instruction to the desktop delivery control server.
  • step S2 the desktop delivery control server completes the registration of the connector according to the registration instruction.
  • the desktop delivery control server After receiving the registration instruction, the desktop delivery control server obtains the corresponding plug-in file and registration path according to the registration instruction, and completes the registration of the docking plug-in based on the plug-in file.
  • the plug-in file and registration path may be sent to the desktop delivery control server together according to the registration instruction, or acquired by the desktop delivery control server sending an acquisition request to the terminal, or acquired by the desktop delivery control server from the storage path of the plug-in file.
  • the completion of the registration of the docking plug-in by the desktop delivery control server according to the registration instruction includes the following steps:
  • Step S402 Obtain the first plug-in file and the corresponding registration path.
  • Step S404 Delete the preset interface file from the first plug-in file to obtain the second plug-in file.
  • the first plug-in file is the original plug-in file obtained by the desktop delivery control server, and the registration path refers to the address where the plug-in is registered.
  • the second plug-in file is the first plug-in file after deleting the preset interface file. That is, the first plug-in file refers to a plug-in file that includes the preset interface file, and the second plug-in file refers to a plug-in file that does not include the preset interface file.
  • the preset interface file includes a creation interface file (Citrix.MachineCreationAPI.dll) and a management interface file (Citrix.ManagedMachineAPI.dll). Since the desktop delivery control server already includes the creation interface file and the management interface file, in order to avoid misunderstandings caused by duplication of files, when registering the docking plug-in, the preset interface file is deleted and then registered.
  • the desktop delivery control server obtains the first plug-in file and the registration path
  • the corresponding preset interface file is found from the first plug-in file by the file name of the preset interface file, and the preset interface file is retrieved from the first plug-in file. Delete one plug-in file to obtain the second plug-in file.
  • Step S406 After the second plug-in file is copied to the registration path, the registration of the plug-in is completed based on the preset registration script file and the second plug-in file.
  • the registration script is a pre-written program file used to register the docking plug-in.
  • the registration script is a Powershell file. Specifically, after the second plug-in file is obtained, the second plug-in file is copied to the registration path corresponding to the registration. Run the preset registration script file and the second plug-in file to complete the registration of the docking plug-in, that is, the docking plug-in has been registered to the desktop delivery control server.
  • the docking plug-in is registered on the desktop delivery control server, so as to facilitate subsequent connection between the desktop delivery control server and the cloud platform.
  • the desktop delivery control server after the desktop delivery control server completes the registration of the docking plug-in according to the registration instruction, it further includes the step of calling the registered docking plug-in by the desktop delivery control server and using the docking plug-in to connect to the cloud platform.
  • the desktop delivery control server calls the registered docking plug-in, and using the docking plug-in to connect to the cloud platform specifically includes: the desktop delivery control server receives a connection instruction carrying a connection key and a cloud platform identifier. The desktop delivery control server responds to the connection instruction and calls the docking plug-in. After the desktop delivery control server uses the docking plug-in to verify that the connection key is correct, it connects to the cloud platform based on the preset connection mode and the cloud platform identifier.
  • connection instruction is a request for instructing the docking plug-in to connect the cloud platform with the desktop delivery control server.
  • the connection key is used to identify the identity of the terminal user who sends the connection instruction. Connection keys include but are not limited to account passwords, etc.
  • the default connection method is http.
  • the registration completion information is fed back to the terminal.
  • the terminal receives the feedback information that the registration of the docking plug is completed, it displays the feedback information of the registration completion on the display screen of the terminal to prompt the user that the registration is completed.
  • the user inputs the connection key at the terminal by operating the terminal to trigger the generation of the connection instruction.
  • the terminal After the terminal generates the connection instruction, it sends the connection instruction and the connection key corresponding to the connection instruction to the desktop delivery control server.
  • the desktop delivery control server synchronously calls the registered docking plug-in. The connection key is verified by the docking plug-in.
  • the docking plug-in When the connection key is verified correctly, the docking plug-in connects the desktop delivery control server and the cloud platform based on the preset connection mode.
  • the docking plug-in integrates with the desktop delivery control server through an interface, and connects with the cloud platform through a Web API. Verification of the connection key can be understood as the connection key is a key that exists in the key store and has connection authority.
  • the desktop delivery control server when the desktop delivery control server calls the registered docking plug-in and uses the docking plug-in to connect to the cloud platform, the desktop delivery control server obtains resource data from the cloud platform by calling the docking plug-in, and generates the corresponding resource data Resource ID.
  • the docking plug-in is used to obtain the resource data on the cloud platform.
  • the corresponding resource identifiers are generated for the resource data and stored locally in the desktop delivery control server.
  • the generated resource identifiers are displayed on the terminal for the user to select. The user determines the resource data of the cloud platform through the generated resource identifier, and selects the required resource data.
  • a sequence diagram of a method for creating a cloud host is provided.
  • the terminal After the desktop delivery control server registers the docking plug-in, the terminal generates a creation instruction carrying a cloud platform identifier and a resource identifier, and will create the instruction Send to the desktop delivery control server.
  • the desktop delivery control server receives the cloud host creation instruction that carries the cloud platform identifier and the resource identifier sent by the terminal.
  • the docking plug-in is called, and the corresponding cloud platform interface is called by the docking plug-in according to the cloud platform ID to send the resource ID to the corresponding cloud platform.
  • the cloud platform obtains corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
  • a cloud host creation system including a terminal 102, a desktop delivery control server 104, and a cloud platform 106, specifically.
  • the terminal 102 is configured to generate a creation instruction carrying a cloud platform identifier and a resource identifier, and send the creation instruction to the desktop delivery control server 104.
  • the desktop delivery control server 104 receives the cloud host creation instruction carrying the cloud platform identification and resource identification sent by the terminal 102; calls the docking plug-in, and calls the corresponding cloud platform interface according to the cloud platform identification through the docking plug-in, and sends the resource identification to the corresponding cloud Platform 106.
  • the cloud platform 106 obtains corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
  • the desktop delivery control server 404 is also used to obtain cloud host information of the created cloud host, call the docking plug-in, and send a disk resource creation instruction carrying the cloud host information to the cloud platform 406.
  • the cloud platform 406 is also used to respond to a disk resource creation instruction to create a disk with a preset capacity
  • the cloud platform 406 is also used to write the cloud host information into the preset capacity disk, and mount the preset capacity disk to the disk service cloud host.
  • the desktop delivery control server 404 is also used to call the docking plug-in to identify and associate the preset capacity disk with the cloud host information written into the corresponding cloud host.
  • the desktop delivery control server 404 is also used to receive registration instructions sent by the terminal.
  • the desktop delivery control server 404 is also used to obtain the first plug-in file and the corresponding registration path;
  • the registration of the plug-in is completed based on the preset registration script file and the second plug-in file.
  • the desktop delivery control server 404 is also used to obtain the creation interface file and the management interface file in the first plug-in file;
  • the creation interface file and the management interface file are deleted from the first plug-in file to obtain the second plug-in file.
  • the desktop delivery control server 404 is also used to call the registered docking plug-in, and use the docking plug-in to connect to the cloud platform.
  • the desktop delivery control server 404 is also configured to receive a connection instruction carrying a connection key and a cloud platform identifier
  • connection key After verifying that the connection key is correct by using the docking plug-in, it connects to the cloud platform based on the preset connection method and the cloud platform identifier.
  • the desktop delivery control server 404 is also used to call the docking plug-in to obtain resource data from the cloud platform, and to generate a resource identifier corresponding to the resource data.
  • the desktop delivery control server 404 is also used to determine that the connection key is correct when the docking plug-in is used to verify that the connection key exists in the key library and has connection authority.
  • the desktop delivery control server 404 is also used to obtain the disk number of the preset capacity disk and the host number of the cloud host;
  • Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种云主机创建方法，包括：桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令；桌面交付控制服务器响应云主机创建指令调用对接插件，并通过对接插件根据平台标识调用对应的云平台接口将资源标识发送至对应的云平台；云平台根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机。

Description

云主机创建方法和系统
相关申请的交叉引用
本申请要求于2019年9月18日提交中国专利局，申请号为2019108833088，申请名称为“云主机创建方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种云主机创建方法和系统。
背景技术
Citrix XenDesktop(思杰虚拟桌面)是一套桌面虚拟化解决方案，可将Windows桌面和应用转变为一种按需服务，向任何地点、使用任何设备的任何用户交付，提供满足用户的所有业务需求的完整虚拟应用和桌面解决方案。在降低IT成本的同时，让员工可以随时随地自由工作。Citrix XenDesktop在现代数字化工作空间中可以从任何云(公共云、内部部署或混合云)交付Windows桌面和应用。
然而，发明人意识到，目前Citrix XenDesktop官方支持的虚拟化平台主要有思杰、微软以及威睿等国外服务供应商的服务器。因此，相对于国内云服务供应商而言，当需要使用Citrix XenDesktop的虚拟桌面时，目前只能通过对接上述国外服务供应商提供的服务器，将虚拟桌面虚拟化到国外供应商的虚拟化平台中。不仅增加了自身的运营维护成本，且由于国外供应商提供的服务器并不能够适用于所有的平台，导致适用范围比较窄。
发明内容
根据本申请公开的各种实施例，提供一种云主机创建方法和系统。
一种云主机创建方法，包括：
桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令；
桌面交付控制服务器响应云主机创建指令调用对接插件，并通过所述对接插件根据所述云平台标识调用对应的云平台接口将所述资源标识发送至对应的云平台；及
所述云平台根据所述资源标识获取对应的资源数据，基于所述资源数据创建对应的云主机。
一种云主机创建系统，所述系统包括：
终端，用于生成携带有云平台标识和资源标识的创建指令，并将所述创建指令发送至桌面交付控制服务器；
桌面交付控制服务器，用于接收所述终端发送的携带有云平台标识和资源标识的云主机创建指令；调用对接插件，并通过所述对接插件根据所述云平台标识调用对应的云平台接口将所述资源标识发送至对应的云平台；及
云平台，用于根据所述资源标识获取对应的资源数据，基于所述资源数据创建对应的云主机。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中云主机创建方法的应用场景图。
图2为根据一个或多个实施例中云主机创建方法的流程示意图。
图3为另一个实施例中云主机创建方法的流程示意图。
图4为根据一个或多个实施例中根据注册指令完成对接插件的注册步骤的流程示意图。
图5为根据一个或多个实施例中云主机创建方法的时序图。
具体实施方式
为了使本申请的技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供的云主机创建方法，可以应用于如图1所示的应用环境中。终端102通过网络与桌面交付控制服务器104进行通信，桌面交付控制服务器104通过网络与云平台106进行通信。终端102生成携带有云平台标识和资源标识的创建指令，并将创建指令发送至桌面交付控制服务器104。桌面交付控制服务器104接收终端发送的携带有云平台标识和资源标识的云主机创建指令；调用对接插件，并通过对接插件根据云平台标识调用对应的云平台接口将资源标识发送至对应的云平台106。云平台106根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机。终端102可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备，桌面交付控制服务器104可以用独立的服务器或者是多个服务器组成的服务器集群来实现。
在一些实施例中，如图2所示，提供了一种云主机创建方法，包括以下步骤：
步骤S202，桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令。
桌面交付控制器为Citrix XenDesktop方的DDC(Desktop Delivery Controller，桌面交付控制器)服务器，终端为安装了DDC服务器的计算机设备。云主机创建指令则是终端用于指示DDC服务器创建云主机的请求。云平台标识为云平台的唯一标识，用于标识对应的云平台。云主机创建指令是 指用于指示DDC服务器在对应的云平台创建云主机的指令。资源标识则是创建云平台资源所需的资源数据的唯一标识。标识包括但不限于ID(Identity，身份标识号码)、编号、名称等。
具体地，云主机创建指令是由用户在终端触发的用于指示DDC服务器在对应的云平台创建云主机的指令。云主机是是一种类似VPS主机(Virtual Private Server虚拟专用服务器)的虚拟化技术，VPS是采用虚拟软件在一台主机上虚拟出多个类似独立主机的部分，能够实现单机多用户，每个部分都可以做单独的操作系统，管理方法同主机一样。而云主机是在一组集群主机上虚拟出多个类似独立主机的部分，集群中每个主机上都有云主机的一个镜像，从而大大提高了虚拟主机的安全稳定性，除非所有的集群内主机全部出现问题，云主机才会无法访问。而云平台则是提供云计算服务的平台，是通过不计其数的实体主机提供不计其数的站点的虚拟环境。可以理解为，本实施例中的云主机则是通过云平台提供的集群主机中虚拟出的主机。
当用户有创建云主机的需求时，通过操作终端选择创建云主机的云平台的云平台标识，以及所需资源数据的资源标识。终端接收到用户的选择云平台标识和资源标识后，生成云主机创建指令。并云平台标识和资源标识随创建的云主机创建指令发送至DDC服务器。
步骤S204，桌面交付控制服务器响应云主机创建指令调用对接插件，并通过对接插件根据云平台标识调用对应的云平台接口将资源标识发送至对应的云平台。
插件是一种遵循一定规范的应用程序接口编写出来的程序，对接插件则是用于与DDC服务器以及云平台进行对接的程序。传统DDC服务器接收到云主机创建指令后，即在合作的国外服务商的虚拟云平台中创建对应的云主机。然而，对于没有合作的国内服务商而言，无法通过向DDC服务器发送创建云主机指令在自身的云平台中创建云主机。因此，在本实施例中，通过编写的对接程序实现DDC服务器和云平台的对接。云平台接口是指云平台的API接口(Application Programming Interface,应用程序编程接口)。
具体地，当DDC服务器接收到创建云主机指令后，调用预先部署在DDC服务器中的对接插件，通过对接插件与云平台标识对应的云平台进行对接。对接插件根据云平台标识确定需要对接的云平台，然后调用该云平台预先约定好的API接口，通过该API接口将资源标识发送至云平台。
步骤S206，云平台根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机。
具体地，当云平台接收到资源标识后，根据资源标识获取对应的资源数据，建立对应的云主机。资源数据包括网络资源、模板镜像资源、存储资源、计算方案资源等。
上述云主机创建方法，桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令后，响应云主机创建指令调用对接插件。从而确保桌面交付控制服务器根据指令按需调用插件，节省资源。桌面交付控制服务器利用对接插件调用云平台标识的云平台接口，向云平台发送资源标识，从而确保通过对接插件实现桌面交付控制服务器与云平台的连接。云平台根据资源标识获取对应的资源数据，根据资源数据完成云主机的创建，从而确保能够在Citrix XenDesktop上创建虚拟云平台的虚拟云主机。实现了在云平台上自主创建云主机，扩大适用范围，且减少了运营维护的成本。
在一些实施例中，如图3所示，在步骤S206，云平台根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机之后，还包括以下步骤：
步骤S208，桌面交付控制服务器获取创建的云主机的云主机信息，调用对接插件，发送携带云主机信息的磁盘资源创建指令至云平台。
磁盘资源创建指令用于请求对应的云平台创建磁盘的指令，创建的磁盘用于存储云主机信息。
具体地，当云主机创建完成后，DDC服务器获取创建的云主机的云主机信息。同时生成磁盘创建指令，并调用对接插件将获取的云主机信息随磁盘创建指令发送至对应的云平台。云主机信息包括主机ID(主机号)、主机名、主机对应的DDC地址以及域控信息等。
步骤S210，云平台响应磁盘资源创建指令，创建预设容量磁盘。
步骤S212，云平台将云主机信息写入预设容量磁盘中，并将预设容量磁盘挂载到磁盘服务云主机上。
预设容量磁盘是指预先设定好容量的磁盘，在本实施例中，预设容量磁盘可以是1GB大小的磁盘。磁盘服务云主机是指在云平台中预先部署的用户管理云主机身份磁盘的云主机，磁盘服务云主机基于Golang语言开发。
具体地，云平台接收到DDC服务器调用对接插件发送的磁盘资源创建指令后，响应该磁盘资源创建指令，调用磁盘服务云主机创建一块1GB容量大小的磁盘。然后，将云主机信息写入创建的1GB容量大小的磁盘中，并将该磁盘挂载到磁盘服务器云主机上。或者，当云平台接收到DDC服务器调用对接插件发送的磁盘资源创建指令后，响应该磁盘资源创建指令创建一块1GB大小的磁盘后，首先将该磁盘挂载到磁盘服务云主机上，再将云主机信息写入至该磁盘中。可以通过Linux dd命令将云主机信息写入磁盘中。
步骤S214，对接插件将已写入云主机信息的预设容量磁盘与对应的云主机进行标识关联。
具体地，当云主机的云主机信息已被写入创建的预设容量磁盘中，则将云主机与该预设容量磁盘进行标识关联，从而建立该磁盘与云主机的关联。标识关联可以理解为将预设容量磁盘的磁盘ID(磁盘号)与云主机的主机ID进行绑定或者映射等。
在本实施例中，通过将云主机信息写入创建的磁盘并把该磁盘挂在到云平台的磁盘服务云主机上，便于云平台对云主机信息进行管理。
在一些实施例中，在步骤S202，桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令之前，还包括在桌面交付控制服务器中注册对接插件的步骤。
在桌面交付控制服务器中注册对接插件，包括以下步骤：
步骤S1，桌面交付控制服务器接收终端发送的注册指令。
注册指令是指用于指示桌面交付控制服务器完成对接插件注册的指令。 具体地，用户通过操作终端生成注册指令，终端将该注册指令发送至桌面交付控制服务器。
步骤S2，桌面交付控制服务器根据注册指令完成对接插件的注册。
具体地，桌面交付控制服务器接收到注册指令后，根据注册指令获取对应的插件文件和注册路径，基于插件文件完成对接插件的注册。插件文件和注册路径可以是根据注册指令一并发送给桌面交付控制服务器的，或者由桌面交付控制服务器向终端发送获取请求获取的，或者由桌面交付控制服务器向插件文件的存储路径提取获取的。
在一些实施例中，如图4所示，桌面交付控制服务器根据注册指令完成对接插件的注册包括以下步骤：
步骤S402，获取第一插件文件以及对应的注册路径。
步骤S404，从第一插件文件中删除预设接口文件，得到第二插件文件。
第一插件文件为桌面交付控制服务器获取的原始的插件文件，注册路径是指对接插件注册的地址。第二插件文件即为删除预设接口文件的后的第一插件文件。也就是说，第一插件文件是指包括预设接口文件的插件文件，第二插件文件是指不包括预设接口文件的插件文件。在本实施例中，预设接口文件包括创建接口文件(Citrix.MachineCreationAPI.dll)和管理接口文件(Citrix.ManagedMachineAPI.dll)。由于桌面交付控制服务器中已经包括了创建接口文件和管理接口文件，为避免文件重复带来误会，注册对接插件时则将预设接口文件删除后再进行注册。
具体地，当桌面交付控制服务器获取到第一插件文件和注册路径后，通过预设接口文件的文件名从第一插件文件中查找到对应的预设接口文件，将该预设接口文件从第一插件文件中删除，得到第二插件文件。
步骤S406，将第二插件文件复制到注册路径后，基于预设注册脚本文件和第二插件文件完成对接插件的注册。
注册脚本为预先编写好，用于注册对接插件的程序文件。注册脚本为Powershell文件。具体地，当获取到第二插件文件后，将第二插件文件复制 到注册对应的注册路径中。运行预设注册脚本文件和第二插件文件，完成对接插件的注册，即对接插件已经注册至桌面交付控制服务器。
在本实施例中，在桌面交付控制服务器在利用云平台创建云主机之前，在桌面交付控制服务器注册好对接插件，从而便于后续实现桌面交付控制服务器与云平台的连接。
在一些实施例中，当桌面交付控制服务器根据注册指令完成对接插件的注册之后，还包括桌面交付控制服务器调用已注册的对接插件，利用对接插件与所述云平台连接的步骤。
桌面交付控制服务器调用已注册的对接插件，利用对接插件与所述云平台连接具体包括：桌面交付控制服务器接收携带有连接密钥和云平台标识的连接指令。桌面交付控制服务器响应连接指令，调用对接插件。桌面交付控制服务器利用对接插件验证连接密钥正确后，基于预设连接方式和云平台标识与云平台连接。
连接指令是用于指示对接插件将云平台与桌面交付控制服务器进行连接的请求。连接密钥是指用于识别发送连接指令的终端用户的身份。连接密钥包括但不限于账户密码等。预设连接方式为http方式。
具体地，当桌面交付控制服务器完成对接插件注册后向终端反馈注册完成的信息。而终端接收到对接插件注册完成的反馈信息后，将注册完成的反馈信息显示在终端的显示屏上提示用户已经注册完成。进一步的，用户通过操作终端，在终端输入连接密钥触发连接指令的生成。当终端生成连接指令后，将连接指令以及连接指令对应的连接密钥发送至桌面交付控制服务器。桌面交付控制服务器根据接收到携带有连接密钥的连接指令后，同步调用注册好的对接插件。利用对接插件对连接密钥进行验证，当连接密钥验证正确后，对接插件基于预设的连接方式将桌面交付控制服务器与云平台进行连接。对接插件与桌面交付控制服务器通过接口方式集成，与云平台通过Web API方式连接。对连接密钥进行验证可以理解为，连接密钥为密钥库中存在的密钥，且有连接权限的密钥。
在一些实施例中，当桌面交付控制服务器调用已注册的对接插件，利用对接插件与云平台连接之后，桌面交付控制服务器通过调用对接插件从云平台中获取资源数据，并生成与资源数据对应的资源标识。
具体地，当桌面交付控制服务器通过对接插件与云平台实现连接后，利用对接插件获取云平台上的资源数据。并且，将该些资源数据生成对应的资源标识后存储在桌面交付控制服务器本地，当用户在终端发起云主机创建指令时，将生成资源标识显示在终端供用户选择。用户通过生成的资源标识确定云平台的资源数据，并选择所需的资源数据。
应该理解的是，虽然图2-4的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-4中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在一些实施例中，如图5所示，提供一种云主机创建方法时序图，当桌面交付控制服务器注册对接插件后，终端生成携带有云平台标识和资源标识的创建指令，并将创建指令发送至桌面交付控制服务器。桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令。响应创建指令调用对接插件，并通过对接插件根据云平台标识调用对应的云平台接口将资源标识发送至对应的云平台。云平台根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机。
在一些实施例中，提供一种云主机创建系统，包括终端102、桌面交付控制服务器104和云平台106，具体地。
终端102用于生成携带有云平台标识和资源标识的创建指令，并将创建指令发送至桌面交付控制服务器104。
桌面交付控制服务器104接收终端102发送的携带有云平台标识和资源标识的云主机创建指令；调用对接插件，并通过对接插件根据云平台标识调用对应的云平台接口将资源标识发送至对应的云平台106。及
云平台106根据资源标识获取对应的资源数据，基于资源数据创建对应的云主机。
在一些实施例中，桌面交付控制服务器404还用于获取创建的云主机的云主机信息，调用对接插件，发送携带云主机信息的磁盘资源创建指令至云平台406。
云平台406还用于响应磁盘资源创建指令，创建预设容量磁盘；
云平台406还用于将云主机信息写入预设容量磁盘中，并将预设容量磁盘挂载到磁盘服务云主机上。及
桌面交付控制服务器404还用于调用对接插件将已写入云主机信息的预设容量磁盘与对应的云主机进行标识关联。
在一些实施例中，桌面交付控制服务器404还用于接收终端发送的注册指令；及
根据注册指令完成对接插件的注册。
在一些实施例中，桌面交付控制服务器404还用于获取第一插件文件以及对应的注册路径；
从第一插件文件中删除预设接口文件，得到第二插件文件；及
将第二插件文件复制到注册路径后，基于预设注册脚本文件和第二插件文件完成对接插件的注册。
在一些实施例中，桌面交付控制服务器404还用于获取第一插件文件中的创建接口文件和管理接口文件；及
从第一插件文件中删除创建接口文件和管理接口文件，得到第二插件文件。
在一些实施例中，桌面交付控制服务器404还用于调用已注册的对接插件，利用对接插件与云平台连接。
在一些实施例中，桌面交付控制服务器404还用于接收携带有连接密钥和云平台标识的连接指令；
响应连接指令，调用对接插件；及
利用对接插件验证连接密钥正确后，基于预设连接方式和云平台标识与云平台连接。
在一些实施例中，桌面交付控制服务器404还用于调用对接插件从云平台获取资源数据，并生成与资源数据对应的资源标识。
在一些实施例中，桌面交付控制服务器404还用于当利用对接插件验证连接密钥存在于密钥库中且有连接权限时，确定连接密钥正确。
在一些实施例中，桌面交付控制服务器404还用于获取预设容量磁盘的磁盘号和云主机的主机号；及
将磁盘号与主机号绑定。
关于云主机创建系统的具体限定可以参见上文中对于云主机创建方法的限定，在此不再赘述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种云主机创建方法，包括：
    桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令；
    桌面交付控制服务器响应云主机创建指令调用对接插件，并通过所述对接插件根据所述云平台标识调用对应的云平台接口将所述资源标识发送至对应的云平台；及
    所述云平台根据所述资源标识获取对应的资源数据，基于所述资源数据创建对应的云主机。
  2. 根据权利要求1所述的方法，其特征在于，所述云平台根据所述资源标识获取对应的资源数据，基于所述资源数据创建对应的云主机之后，包括：
    所述桌面交付控制服务器获取创建的所述云主机的云主机信息，调用所述对接插件，发送携带所述云主机信息的磁盘资源创建指令至所述云平台；
    所述云平台响应所述磁盘资源创建指令，创建预设容量磁盘；
    所述云平台将所述云主机信息写入所述预设容量磁盘中，并将所述预设容量磁盘挂载到磁盘服务云主机上；及
    所述桌面交付控制服务器调用所述对接插件将已写入所述云主机信息的预设容量磁盘与对应的云主机进行标识关联。
  3. 根据权利要求1所述的方法，其特征在于，所述桌面交付控制服务器接收终端发送的携带有云平台标识和资源标识的云主机创建指令之前，包括：
    所述桌面交付控制服务器接收终端发送的注册指令；及
    所述桌面交付控制服务器根据所述注册指令完成所述对接插件的注册。
  4. 根据权利要求3所述的方法，其特征在于，所述桌面交付控制服务器根据所述注册指令完成所述对接插件的注册，包括：
    获取第一插件文件以及对应的注册路径；
    从所述第一插件文件中删除预设接口文件，得到第二插件文件；及
    将所述第二插件文件复制到所述注册路径后，基于预设注册脚本文件和 所述第二插件文件完成所述对接插件的注册。
  5. 根据权利要求4所述的方法，其特征在于，所述从所述第一插件文件中删除预设接口文件，得到第二插件文件，包括：
    获取所述第一插件文件中的创建接口文件和管理接口文件；及
    从所述第一插件文件中删除所述创建接口文件和管理接口文件，得到第二插件文件。
  6. 根据权利要求3所述的方法，其特征在于，所述桌面交付控制服务器根据所述注册指令完成所述对接插件的注册之后，包括：
    所述桌面交付控制服务器调用已注册的所述对接插件，利用所述对接插件与所述云平台连接。
  7. 根据权利要求6所述的方法，其特征在于，所述桌面交付控制服务器调用已注册的所述对接插件，利用所述对接插件与所述云平台连接，包括：
    所述桌面交付控制服务器接收携带有连接密钥和云平台标识的连接指令；
    所述桌面交付控制服务器响应所述连接指令，调用所述对接插件；及
    所述桌面交付控制服务器利用所述对接插件验证所述连接密钥正确后，基于预设连接方式和所述云平台标识与所述云平台连接。
  8. 根据权利要求6所述的方法，其特征在于，所述桌面交付控制服务器调用已注册的所述对接插件，利用所述对接插件与所述云平台连接之后，包括：
    桌面交付控制服务器调用对接插件从所述云平台获取资源数据，并生成与所述资源数据对应的资源标识。
  9. 根据权利要求7所述的方法，其特征在于，当所述桌面交付控制器利用所述对接插件验证所述连接密钥存在于密钥库中且有连接权限时，确定所述连接密钥正确。
  10. 根据权利要求2所述的方法，其特征在于，所述桌面交付控制服务器调用所述对接插件将已写入所述云主机信息的预设容量磁盘与对应的云主 机进行标识关联，包括：
    获取所述预设容量磁盘的磁盘号和所述云主机的主机号；及
    将所述磁盘号与所述主机号绑定。
  11. 一种云主机创建系统，包括：
    终端，用于生成携带有云平台标识和资源标识的创建指令，并将所述创建指令发送至桌面交付控制服务器；
    桌面交付控制服务器，用于接收所述终端发送的携带有云平台标识和资源标识的云主机创建指令；调用对接插件，并通过所述对接插件根据所述云平台标识调用对应的云平台接口将所述资源标识发送至对应的云平台；及
    云平台，用于根据所述资源标识获取对应的资源数据，基于所述资源数据创建对应的云主机。
  12. 根据权利要求11所述的系统，其特征在于，所述桌面交付控制服务器还用于获取创建的所述云主机的云主机信息，调用所述对接插件，发送携带所述云主机信息的磁盘资源创建指令至所述云平台；
    所述云平台还用于响应所述磁盘资源创建指令，创建预设容量磁盘；
    所述云平台还用于将所述云主机信息写入所述预设容量磁盘中，并将所述预设容量磁盘挂载到磁盘服务云主机上；及
    所述桌面交付控制服务器调用所述对接插件将已写入所述云主机信息的预设容量磁盘与对应的云主机进行标识关联。
  13. 根据权利要求11所述的系统，其特征在于，所述桌面交付控制服务器还用于接收终端发送的注册指令；及
    所述桌面交付控制服务器还用于根据所述注册指令完成所述对接插件的注册。
  14. 根据权利要求13所述的系统，其特征在于，所述桌面交付控制服务器还用于获取第一插件文件以及对应的注册路径；
    从所述第一插件文件中删除预设接口文件，得到第二插件文件；及
    将所述第二插件文件复制到所述注册路径后，基于预设注册脚本文件和 所述第二插件文件完成所述对接插件的注册。
  15. 根据权利要求14所述的系统，其特征在于，所述桌面交付控制服务器还用于获取所述第一插件文件中的创建接口文件和管理接口文件；及
    从所述第一插件文件中删除所述创建接口文件和管理接口文件，得到第二插件文件。
  16. 根据权利要求13所述的系统，其特征在于，所述桌面交付控制服务器还用于调用已注册的所述对接插件，利用所述对接插件与所述云平台连接。
  17. 根据权利要求16所述的系统，其特征在于，所述桌面交付控制服务器还用于接收携带有连接密钥和云平台标识的连接指令；
    响应所述连接指令，调用所述对接插件；及
    利用所述对接插件验证所述连接密钥正确后，基于预设连接方式和所述云平台标识与所述云平台连接。
  18. 根据权利要求16所述的系统，其特征在于，所述桌面交付控制服务器还用于调用对接插件从所述云平台获取资源数据，并生成与所述资源数据对应的资源标识。
  19. 根据权利要求17所述的系统，其特征在于，所述桌面交付控制器还用于当利用所述对接插件验证所述连接密钥存在于密钥库中且有连接权限时，确定所述连接密钥正确。
  20. 根据权利要求12所述的系统，其特征在于，所述桌面交付控制服务器还用于获取所述预设容量磁盘的磁盘号和所述云主机的主机号；及
    将所述磁盘号与所述主机号绑定。
PCT/CN2019/117136 2019-09-18 2019-11-11 云主机创建方法和系统 WO2021051534A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910883308.8 2019-09-18
CN201910883308.8A CN110795182B (zh) 2019-09-18 2019-09-18 云主机创建方法和系统

Publications (1)

Publication Number Publication Date
WO2021051534A1 true WO2021051534A1 (zh) 2021-03-25

Family

ID=69427358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/117136 WO2021051534A1 (zh) 2019-09-18 2019-11-11 云主机创建方法和系统

Country Status (2)

Country Link
CN (1) CN110795182B (zh)
WO (1) WO2021051534A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112306926B (zh) * 2020-10-12 2022-12-27 苏州浪潮智能科技有限公司 一种云平台中指定虚拟硬盘类型的方法和系统
CN112333008B (zh) * 2020-10-22 2023-01-24 济南浪潮数据技术有限公司 一种云主机整机备份还原方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580302A (zh) * 2013-10-18 2015-04-29 宇宙互联有限公司 云服务管理系统及云联云管理系统
CN106101258A (zh) * 2016-07-08 2016-11-09 腾讯科技（深圳）有限公司 一种混合云的接口调用方法、装置及系统
CN108063824A (zh) * 2017-12-22 2018-05-22 云南天成科技有限公司 一种云服务系统及构建方法
CN108449418A (zh) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 一种混合云平台管理系统及方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104468240B (zh) * 2014-12-29 2018-03-27 成都极驰科技有限公司 云终端管理方法、装置
WO2018006872A1 (zh) * 2016-07-08 2018-01-11 腾讯科技（深圳）有限公司 一种混合云的接口调用方法及装置
US10114659B2 (en) * 2016-09-30 2018-10-30 Vmware, Inc. Remote provisioning of hosts in public clouds
CN108574718B (zh) * 2017-04-19 2021-03-26 北京金山云网络技术有限公司 一种云主机创建方法及装置
CN107241421A (zh) * 2017-06-21 2017-10-10 北京云联万维技术有限公司 一种云主机资源预留方法和装置
CN107463411A (zh) * 2017-08-16 2017-12-12 北京新网数码信息技术有限公司 一种云主机初始化方法及装置
CN107888695B (zh) * 2017-11-23 2019-09-13 新华三云计算技术有限公司 云平台创建镜像的方法和云平台设备
CN109995814B (zh) * 2017-12-29 2021-08-13 中移(苏州)软件技术有限公司 云主机资源的迁移方法及装置、通信设备、存储介质
CN108462745B (zh) * 2018-03-14 2021-04-27 海通证券股份有限公司 一种新型云平台资源管理与交付方法和装置
CN108984266B (zh) * 2018-06-15 2021-09-03 华为技术有限公司 一种虚拟机的管理方法、装置及系统
CN109617990B (zh) * 2018-12-29 2021-12-07 长威信息科技发展股份有限公司 一种融合通信资源云共享方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580302A (zh) * 2013-10-18 2015-04-29 宇宙互联有限公司 云服务管理系统及云联云管理系统
CN106101258A (zh) * 2016-07-08 2016-11-09 腾讯科技（深圳）有限公司 一种混合云的接口调用方法、装置及系统
CN108063824A (zh) * 2017-12-22 2018-05-22 云南天成科技有限公司 一种云服务系统及构建方法
CN108449418A (zh) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 一种混合云平台管理系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WU KUN-XI, FENG GUANG, LU ZHI-XIANG, FANG DAO-KUN: "Ｒesearch and Design of Virtual Cloud Desktop Systems", JOURNAL OF GUANGDONG UNIVERSITY OF TECHNOLOGY / GUANG DONG GONG YE DA XUE XUE BAO, CHINESE ELECTRONIC PERIODICAL SERVICES, CHINA, vol. 32, no. 1, 1 February 2015 (2015-02-01), CHINA, pages 113 - 116, XP055792928, ISSN: 1007-7162, DOI: 10.3969/j.issn.1007-7162.2015.01.023 *

Also Published As

Publication number Publication date
CN110795182A (zh) 2020-02-14
CN110795182B (zh) 2024-09-13

Similar Documents

Publication Publication Date Title
US10880287B2 (en) Out of box experience application API integration
AU2015363218B2 (en) No password user account access
US10263910B2 (en) Resource calling for hybrid applications
WO2021036877A1 (zh) 一种信息处理方法、设备和计算机存储介质
CN107209678B (zh) 用于移动设备的自适应克隆的系统和方法
US9712605B2 (en) Method and system for providing server virtual machine for real-time virtual desktop service, and server device supporting the same
US9830099B1 (en) Secure erase of storage devices
US10873586B2 (en) Systems and methods for secure data access control
US9930063B2 (en) Random identifier generation for offline database
WO2021051534A1 (zh) 云主机创建方法和系统
JP2016523425A (ja) リモーティングセッションを通じた非サポートファイル形式の開封
WO2020093976A1 (zh) 一种资源变更的方法及装置、设备、存储介质
WO2022142536A1 (zh) 灰度发布方法、系统、装置、设备及存储介质
US20240106902A1 (en) Communication protocols for an online content management system
EP3065058B1 (en) A method and a device for flowing data between entities
KR20180124582A (ko) 모바일 클라우드 시스템 및 그 동작 방법
US20180337922A1 (en) Method and device for controlling smart device, server and storage medium
WO2021139261A1 (zh) 应用部署方法、装置及介质
US20230030729A1 (en) Method and apparatus for displaying page
US20180270246A1 (en) Information processing system, information processing apparatus, and information processing method
US9466056B2 (en) Content item delivery for payment
CN111274176B (zh) 一种信息处理方法、电子设备、系统及存储介质
WO2020001617A1 (zh) 获取验证信息的方法和数据中心
CN104991871A (zh) 云终端usb重定向方法与系统
US20240012665A1 (en) Optimized creation of identity information for provisioned virtual machines

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: 19946124

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19946124

Country of ref document: EP

Kind code of ref document: A1