CN110795182A - Cloud host creation method and system - Google Patents

Cloud host creation method and system Download PDF

Info

Publication number
CN110795182A
CN110795182A CN201910883308.8A CN201910883308A CN110795182A CN 110795182 A CN110795182 A CN 110795182A CN 201910883308 A CN201910883308 A CN 201910883308A CN 110795182 A CN110795182 A CN 110795182A
Authority
CN
China
Prior art keywords
cloud platform
control server
delivery control
cloud
desktop delivery
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN201910883308.8A
Other languages
Chinese (zh)
Inventor
贾冲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Priority to CN201910883308.8A priority Critical patent/CN110795182A/en
Priority to PCT/CN2019/117136 priority patent/WO2021051534A1/en
Publication of CN110795182A publication Critical patent/CN110795182A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • G06F9/452Remote windowing, e.g. X-Window System, desktop virtualisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/448Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482Procedural
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45562Creating, deleting, cloning virtual machine instances

Abstract

The application relates to a cloud host creation method and system. The method comprises the following steps: the desktop delivery control server receives a cloud host establishing instruction which is sent by a terminal and carries a cloud platform identifier and a resource identifier; and calling the docking plug-in, and calling the corresponding cloud platform interface through the docking plug-in according to the platform identifier to send the resource identifier to the corresponding cloud platform. And the cloud platform acquires corresponding resource data according to the resource identification, and creates a corresponding cloud host based on the resource data. By adopting the method, the cloud platform and the Citrix XenDesktop can be connected, and the cloud host of the cloud platform can be established on the Citrix XenDesktop.

Description

Cloud host creation method and system
Technical Field
The present application relates to the field of computer technologies, and in particular, to a cloud host creation method and system.
Background
Citrix XenDesktop (SimeJose virtual desktop) is a set of desktop virtualization solution, Windows desktops and applications can be converted into an on-demand service, the on-demand service is delivered to any user using any equipment at any place, and complete virtual applications and desktop solutions meeting all business requirements of the user are provided. The IT cost is reduced, and meanwhile, the staff can freely work at any time and any place. Citrix XenDesktop can deliver Windows desktops and applications from any cloud (public, in-house, or hybrid) in modern digital workspaces.
However, currently, the virtualized platform supported by Citrix XenDesktop official is mainly servers of foreign service providers such as cijek, microsoft and borui. Therefore, compared to a domestic cloud service provider, if a virtual desktop of CitrixXenDesktop needs to be used, the virtual desktop can only be virtualized into a virtualization platform of a foreign service provider by interfacing with a server provided by the foreign service provider. Not only increases the operation and maintenance cost of the server, but also has a narrow application range because the server provided by foreign suppliers cannot be applied to all platforms.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a cloud host creation method and system capable of reducing operation and maintenance costs.
A cloud host creation method, the method comprising:
the desktop delivery control server receives a cloud host establishing instruction which is sent by a terminal and carries a cloud platform identifier and a resource identifier;
the desktop delivery control server responds to a cloud host creating instruction to call a docking plug-in, and calls a corresponding cloud platform interface through the docking plug-in according to the cloud platform identification to send the resource identification to a corresponding cloud platform;
and the cloud platform acquires corresponding resource data according to the resource identification, and creates a corresponding cloud host based on the resource data.
In one embodiment, after the cloud platform acquires the corresponding resource data according to the resource identifier and creates the corresponding cloud host based on the resource data, the method includes:
the desktop delivery control server acquires the created cloud host information of the cloud host, calls the docking plug-in, and sends a disk resource creating instruction carrying the cloud host information to the cloud platform;
the cloud platform responds to the disk resource creating instruction and creates a disk with a preset capacity;
the cloud platform writes the cloud host information into the preset capacity disk and mounts the preset capacity disk onto a disk service cloud host;
and the desktop delivery control server calls the docking plug-in to perform identification association on the preset capacity disk written with the cloud host information and the corresponding cloud host.
In one embodiment, before the desktop delivery control server receives a cloud host creation instruction carrying a cloud platform identifier and a resource identifier and sent by a terminal, the method includes:
the desktop delivery control server receives a registration instruction sent by a terminal;
and the desktop delivery control server finishes the registration of the docking plug-in according to the registration instruction.
In one embodiment, the desktop delivery control server completes registration of the docking plugin according to the registration instruction, including:
acquiring a first plug-in file and a corresponding registration path;
deleting a preset interface file from the first plug-in file to obtain a second plug-in file;
and after copying the second plug-in file to the registration path, finishing the registration of the docking plug-in based on a preset registration script file and the second plug-in file.
In one embodiment, after the desktop delivery control server completes registration of the docking plugin according to the registration instruction, the method includes:
and the desktop delivery control server calls the registered docking plug-in, and is connected with the cloud platform by using the docking plug-in.
In one embodiment, the method for transferring the desktop delivery control server to the cloud platform by using the desktop delivery control server to transfer the registered docking plug-in 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;
and after the desktop delivery control server verifies that the connection key is correct by using the docking plug-in, the desktop delivery control server is connected with the cloud platform based on a preset connection mode and the cloud platform identification.
In one embodiment, the method for invoking the registered docking plug-in by the desktop delivery control server, after connecting with the cloud platform by using the docking plug-in, includes:
and the desktop delivery control server calls a docking plug-in to acquire resource data from the cloud platform and generates a resource identifier corresponding to the resource data.
A cloud host creation system, the system comprising:
the terminal is used for generating a creation instruction carrying a cloud platform identifier and a resource identifier and sending the creation instruction to the desktop delivery control server;
the desktop delivery control server is used for receiving a cloud host establishing instruction which is sent by the terminal and carries a cloud platform identifier and a resource identifier; calling a docking plug-in, and calling a corresponding cloud platform interface according to the cloud platform identification through the docking plug-in to send the resource identification to a corresponding cloud platform;
and the cloud platform is used for acquiring corresponding resource data according to the resource identifier and creating a corresponding cloud host based on the resource data.
In one embodiment, the desktop delivery control server is further configured to acquire created cloud host information of the cloud host, call the docking plug-in, and send a disk resource creation instruction carrying the cloud host information to the cloud platform;
the cloud platform is further used for responding to the disk resource creating instruction and creating a disk with a preset capacity;
the cloud platform is further used for writing the cloud host information into the preset capacity disk and mounting the preset capacity disk onto a disk service cloud host;
and the desktop delivery control server calls the docking plug-in to perform identification association on the preset capacity disk written with the cloud host information and the corresponding cloud host.
In one embodiment, the desktop delivery control server is further configured to receive a registration instruction sent by a terminal; and the desktop delivery control server is also used for finishing the registration of the docking plug-in according to the registration instruction.
According to the cloud host creating method and system, after the desktop delivery control server receives the cloud host creating instruction which is sent by the terminal and carries the cloud platform identification and the resource identification, the cloud host creating instruction is responded to call the docking plug-in. Therefore, the desktop delivery control server is ensured to call the plug-in unit according to the instruction and the resources are saved. The desktop delivery control server calls a cloud platform interface of the cloud platform identification by using the docking plug-in unit and sends the resource identification to the cloud platform, so that the connection between the desktop delivery control server and the cloud platform is ensured to be realized through the docking plug-in unit. The cloud platform acquires corresponding resource data according to the resource identification, and the cloud host is established according to the resource data, so that the virtual cloud host of the virtual cloud platform can be established on the Citrix XenDesktop. The cloud host can be automatically created on the cloud platform, the application range is expanded, and the operation and maintenance cost is reduced.
Drawings
FIG. 1 is a diagram illustrating an example of an application scenario for a cloud host creation method;
FIG. 2 is a flowchart illustrating a method for creating a cloud host in one embodiment;
FIG. 3 is a flowchart illustrating a method for creating a cloud host in accordance with another embodiment;
FIG. 4 is a flowchart illustrating the steps of registering a docking plugin according to a registration instruction in one embodiment;
fig. 5 is a timing diagram of a cloud host creation method in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The cloud host creation method provided by the application can be applied to the application environment shown in fig. 1. The terminal 102 communicates with the desktop delivery control server 104 through a 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 the cloud platform identifier and the resource identifier, and sends the creation instruction to the desktop delivery control server 104. The desktop delivery control server 104 receives a cloud host creation instruction which is sent by a terminal and carries a cloud platform identifier and a resource identifier; and calling the docking plug-in, and calling the corresponding cloud platform interface according to the cloud platform identifier through the docking plug-in to send the resource identifier to the corresponding cloud platform 106. The cloud platform 106 obtains the 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 not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the desktop delivery control server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, there is provided a cloud host creation method, including the steps of:
step S202, the desktop delivery control server receives a cloud host creation instruction which is sent by the terminal and carries the cloud platform identification and the resource identification.
The Desktop delivery controller is a DDC (Desktop delivery controller) server of a Citrix XenDesktop party, and the terminal is computer equipment provided with the DDC server. The cloud host creation instruction is a request for instructing the DDC server to create a cloud host by the terminal. The cloud platform identification is the only identification of the cloud platform and is used for identifying the corresponding cloud platform. The cloud host creation instruction is an instruction for instructing the DDC server to create a cloud host on a corresponding cloud platform. The resource identifier is a unique identifier of resource data required for creating the cloud platform resource. Identification includes, but is not limited to, an ID (Identity), a number, a name, and the like.
Specifically, the cloud host creation instruction is an instruction triggered by a user at a terminal and used for instructing the DDC server to create a cloud host at a corresponding cloud platform. The cloud host is a virtualization technology similar to a VPS (Virtual Private Server) host, the VPS adopts Virtual software to simulate a plurality of parts similar to independent hosts on one host, single machine and multiple users can be realized, each part can be used as an independent operating system, and the management method is the same as that of the host. The cloud host is a part which is similar to a plurality of independent hosts and is virtualized on a group of cluster hosts, and each host in the cluster is provided with a mirror image of the cloud host, so that the safety and stability of the virtual host are greatly improved, and the cloud host cannot access the virtual host unless all the hosts in the cluster have problems. The cloud platform is a platform for providing cloud computing services, and is a virtual environment for providing countless sites through countless entity hosts. It can be understood that the cloud host in this embodiment is a virtualized host in the cluster host provided by the cloud platform.
When a user has a requirement for creating a cloud host, the cloud platform identification of the cloud platform for creating the cloud host and the resource identification of the required resource data are selected through the operation terminal. And after the terminal receives the cloud platform identification and the resource identification selected by the user, generating a cloud host establishing instruction. And the cloud platform identification and the resource identification are sent to the DDC server along with the created cloud host creation instruction.
And S204, the desktop delivery control server responds to the cloud host creation instruction to call the docking plug-in, and calls the corresponding cloud platform interface according to the cloud platform identification through the docking plug-in to send the resource identification to the corresponding cloud platform.
The plug-in is a program written by an application program interface following a certain specification, and the docking plug-in is a program for docking with the DDC server and the cloud platform. After receiving the cloud host creating instruction, the traditional DDC server creates a corresponding cloud host in a virtual cloud platform of a cooperative foreign service provider. However, for domestic servers who do not cooperate, it is impossible to create a cloud host in their own cloud platform by sending a create cloud host instruction to the DDC server. Therefore, in the embodiment, the DDC server and the cloud platform are docked by the written docking program. The cloud platform Interface refers to an API (Application Programming Interface) of the cloud platform.
Specifically, after the DDC server receives a command for creating the cloud host, a docking plug-in pre-deployed in the DDC server is called, and the docking plug-in is docked with the cloud platform corresponding to the cloud platform identifier. And the docking plug-in determines the cloud platform to be docked according to the cloud platform identification, then calls an API (application programming interface) agreed in advance by the cloud platform, and sends the resource identification to the cloud platform through the API.
Step S206, the cloud platform acquires corresponding resource data according to the resource identification, and creates a corresponding cloud host based on the resource data.
Specifically, after the cloud platform receives the resource identifier, the corresponding resource data is acquired according to the resource identifier, and the corresponding cloud host is established. Wherein the resource data comprises network resources, template mirror resources, storage resources, calculation scheme resources and the like
In the cloud host creation party, after the desktop delivery control server receives a cloud host creation instruction which is sent by the terminal and carries the cloud platform identifier and the resource identifier, the desktop delivery control server responds to the cloud host creation instruction to call the docking plug-in. Therefore, the desktop delivery control server is ensured to call the plug-in unit according to the instruction and the resources are saved. The desktop delivery control server calls a cloud platform interface of the cloud platform identification by using the docking plug-in unit and sends the resource identification to the cloud platform, so that the connection between the desktop delivery control server and the cloud platform is ensured to be realized through the docking plug-in unit. The cloud platform acquires corresponding resource data according to the resource identification, and the cloud host is established according to the resource data, so that the virtual cloud host of the virtual cloud platform can be established on the Citrix XenDesktop. The cloud host can be automatically created on the cloud platform, the application range is expanded, and the operation and maintenance cost is reduced.
In an embodiment, as shown in fig. 3, in step S206, after the cloud platform acquires the corresponding resource data according to the resource identifier and creates the corresponding cloud host based on the resource data, the method further includes the following steps:
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 creating instruction carrying the cloud host information to the cloud platform.
The disk resource creating instruction is used for requesting a corresponding cloud platform to create a disk instruction, and the created disk is used for storing cloud host information.
Specifically, after the creation of the cloud host is completed, the DDC server obtains cloud host information of the created cloud host. And meanwhile, generating a disk creation instruction, and calling the docking plug-in to send the acquired cloud host information to the corresponding cloud platform along with the disk creation instruction. The cloud host information comprises a host ID, a host name, a DDC address corresponding to the host, domain control information and the like.
Step S210, the cloud platform responds to the disk resource creating instruction, and creates a disk with a preset capacity.
Step S212, the cloud platform writes the cloud host information into a preset capacity disk, and mounts the preset capacity disk onto the disk service cloud host.
The preset capacity disk refers to a disk with a preset capacity, and in this embodiment, the preset capacity disk is preferably a 1GB disk. The disk service cloud host refers to a cloud host which is deployed in a cloud platform in advance and used for managing a cloud host identity disk by a user, and the disk service cloud host is developed based on a Golang language.
Specifically, after receiving a disk resource creation instruction sent by a DDC server calling a docking plug-in, the cloud platform responds to the disk resource creation instruction and calls a disk service cloud host to create a disk with the capacity of 1 GB. Further, the cloud host information is written into the created disk with the capacity of 1GB, and the disk is mounted on the disk server cloud host. Or after the cloud platform receives a disk resource creating instruction sent by the DDC server calling the docking plug-in, a disk with the size of 1GB is created in response to the disk resource creating instruction, the disk is firstly mounted on the disk service cloud host, and then the cloud host information is written into the disk. The cloud host information can be written into the disk through a Linux dd command.
Step S214, the docking plug-in associates the preset capacity disk written with the cloud host information with the corresponding cloud host.
Specifically, when the cloud host information of the cloud host is written into the created preset capacity disk, the cloud host is associated with the preset capacity disk in an identification manner, so that the association between the disk and the cloud host is established. The identifier association may be understood as binding or mapping the disk ID of the preset capacity disk and the host ID of the cloud host.
In this embodiment, the cloud platform can manage the cloud host information conveniently by writing the cloud host information into the created disk and hanging the disk on a disk service cloud host of the cloud platform.
In one embodiment, before the step S202, the desktop delivery control server receives a cloud host creation instruction carrying a cloud platform identifier and a resource identifier sent by a terminal, the method further includes a step of registering a connector in the desktop delivery control server.
Registering a docking plugin in a desktop delivery control server, comprising the steps of:
in step S1, the desktop delivery control server receives the registration instruction sent by the terminal.
The registration instruction is an instruction for instructing the desktop delivery control server to complete registration of the docking plugin. Specifically, a user generates a registration instruction through an operation terminal, and the terminal sends the registration instruction to the desktop delivery control server.
And step S2, the desktop delivery control server completes the registration of the docking plug-in according to the registration instruction.
Specifically, after receiving the registration instruction, the desktop delivery control server acquires the corresponding plug-in file and the registration path according to the registration instruction, and completes registration of the plug-in based on the plug-in file. The plug-in file and the registration path may be sent to the desktop delivery control server together according to the registration instruction, or obtained by the desktop delivery control server sending an obtaining request to the terminal, or obtained by the desktop delivery control server extracting the storage path of the plug-in file.
In one embodiment, as shown in fig. 4, the desktop delivery control server completing the registration of the docking plug-in according to the registration instruction includes the following steps:
step S402, acquiring a first plug-in file and a corresponding registration path.
Step S404, deleting a preset interface file from the first plug-in file to obtain a second plug-in file.
The first plug-in file is an original plug-in file acquired by the desktop delivery control server, and the registration path refers to an address registered by the docking plug-in. The second plug-in file is the first plug-in file after the preset interface file is deleted. That is, the first plug-in file refers to a plug-in file including a preset interface file, and the second plug-in file refers to a plug-in file not including the preset interface file. In the present embodiment, the preset interface files include a create interface file (citrix. machinery creation api.dll) and a manage interface file (citrix. managed machinery api.dll). Because the desktop delivery control server already comprises the creation interface file and the management interface file, in order to avoid misunderstanding caused by file repetition, the preset interface file is deleted and then registered when the butting plug-in is registered.
Specifically, after the desktop delivery control server obtains the first plug-in file and the registration path, the corresponding preset interface file is searched from the first plug-in file through the file name of the preset interface file, and the preset interface file is deleted from the first plug-in file to obtain a second plug-in file.
Step S406, after copying the second plug-in file to the registration path, finishing the registration of the docking plug-in based on the preset registration script file and the second plug-in file.
The registration script is pre-written and is used for registering a program file of the docking plug-in. The registration script is a Powershell file. Specifically, after the second plug-in file is acquired, the second plug-in file is copied to a registration path corresponding to the registration. And running the preset registration script file and the second plug-in file to complete the registration of the docking plug-in, namely the docking plug-in is registered to the desktop delivery control server.
In this embodiment, before the desktop delivery control server creates the cloud host by using the cloud platform, the docking plug-in is registered in the desktop delivery control server, so that the connection between the desktop delivery control server and the cloud platform is conveniently realized subsequently.
In one embodiment, after the desktop delivery control server completes registration of the docking plugin according to the registration instruction, the method further comprises the step of calling the registered docking plugin by the desktop delivery control server and connecting the docking plugin with the cloud platform.
The desktop delivery control server calls the registered docking plug-in, and the connection with the cloud platform by using the docking plug-in specifically comprises the following steps: and the desktop delivery control server receives a connection instruction carrying the connection key and the cloud platform identifier. And the desktop delivery control server responds to the connection instruction and calls the docking plug-in. And after the desktop delivery control server verifies that the connection key is correct by using the docking plug-in, the desktop delivery control server is connected with the cloud platform based on a preset connection mode and the cloud platform identification.
The connection instruction is used for indicating the docking plug-in to connect the cloud platform with the desktop delivery control server. The connection key refers to an identity for identifying the end user who sent the connection instruction. The connection key includes, but is not limited to, an account password, etc. The preset connection mode is an http mode.
Specifically, after the desktop delivery control server completes registration of the docking plug-in, the information of completion of registration is fed back to the terminal. And after the terminal receives the feedback information of the registration completion of the docking plug-in, the feedback information of the registration completion is displayed on a display screen of the terminal to prompt that the user is already registered. Further, the user inputs the connection key at the terminal to trigger the generation of the connection instruction by operating the terminal. And after the terminal generates the connection instruction, sending the connection instruction and the connection key corresponding to the connection instruction to the desktop delivery control server. And the desktop delivery control server synchronously calls the registered docking plug-ins after receiving the connection instruction carrying the connection key. And verifying the connection key by using the docking plug-in, and connecting the desktop delivery control server with the cloud platform by using the docking plug-in based on a preset connection mode after the connection key is verified correctly. The docking plug-in is integrated with the desktop delivery control server in an interface mode and connected with the cloud platform in a Web API mode. The verification of the join key may be understood as that the join key is a key existing in a key store and having join rights.
Further, in an embodiment, after the desktop delivery control server calls the registered docking plug-in and connects with the cloud platform by using the docking plug-in, the desktop delivery control server acquires the resource data from the cloud platform by calling the docking plug-in and generates a resource identifier corresponding to the resource data.
Specifically, after the desktop delivery control server is connected with the cloud platform through the docking plug-in, the docking plug-in is used for acquiring resource data on the cloud platform. And generating corresponding resource identifiers for the resource data, storing the resource identifiers in the local desktop delivery control server, and displaying the generated resource identifiers on the terminal for the user to select when the user initiates a cloud host creation instruction on the terminal. And the user determines the resource data of the cloud platform through the generated resource identification, and selects the required resource data.
It should be understood that although the various steps in the flow charts of fig. 2-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In an embodiment, as shown in fig. 5, a timing chart of a cloud host creation method is provided, where after a desktop delivery control server registers a docking plug-in, a terminal generates a creation instruction carrying a cloud platform identifier and a resource identifier, and sends the creation instruction to the desktop delivery control server. The desktop delivery control server receives a cloud host creating instruction which is sent by a terminal and carries a cloud platform identifier and a resource identifier. And responding to the creation instruction to call the docking plug-in, and calling the corresponding cloud platform interface through the docking plug-in according to the cloud platform identification to send the resource identification to the corresponding cloud platform. And the cloud platform acquires corresponding resource data according to the resource identification, and creates a corresponding cloud host based on the resource data.
In one embodiment, a cloud host creation system is provided that includes a terminal 102, a desktop delivery control server 104, and a cloud platform 106, wherein,
the terminal 102 is configured to generate a creation instruction carrying the cloud platform identifier and the resource identifier, and send the creation instruction to the desktop delivery control server 104. The desktop delivery control server 104 receives a cloud host creation instruction which is sent by the terminal 102 and carries a cloud platform identifier and a resource identifier; and calling the docking plug-in, and calling the corresponding cloud platform interface according to the cloud platform identifier through the docking plug-in to send the resource identifier to the corresponding cloud platform 106. The cloud platform 106 obtains the corresponding resource data according to the resource identifier, and creates a corresponding cloud host based on the resource data.
In an embodiment, the desktop delivery control server 404 is further configured to obtain cloud host information of the created cloud host, call a 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 configured to respond to the disk resource creating instruction and create a disk with a preset capacity; the cloud platform 406 writes the cloud host information into the preset capacity disk, and mounts the preset capacity disk onto the disk service cloud host. The desktop delivery control server 404 calls the docking plug-in to perform identification association between the preset capacity disk written with the cloud host information and the corresponding cloud host.
In one embodiment, the desktop delivery control server 404 is further configured to receive a registration instruction sent by the terminal; and finishing the registration of the docking plug-in according to the registration instruction.
In one embodiment, the desktop delivery control server 404 is further configured to obtain the first plug-in file and the corresponding registration path; deleting a preset interface file from the first plug-in file to obtain a second plug-in file; and after copying the second plug-in file to the registration path, finishing the registration of the butting plug-in based on the preset registration script file and the second plug-in file.
In one embodiment, the desktop delivery control server 404 is further configured to invoke a registered docking plug-in with which to interface with the cloud platform.
In one embodiment, the desktop delivery control server 404 is further configured to receive a connection instruction carrying a connection key and a cloud platform identifier; responding to the connection instruction, and calling the docking plug-in; and after the butt-joint plug-in is used for verifying that the connection key is correct, the connection with the cloud platform is carried out based on a preset connection mode and the cloud platform identification.
In one embodiment, the desktop delivery control server 404 is further configured to invoke a docking plugin to obtain resource data from the cloud platform and generate a resource identifier corresponding to the resource data.
For specific limitations of the cloud host creation system, reference may be made to the above limitations of the cloud host creation method, which is not described herein again. The modules in the cloud host creation system can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A cloud host creation method, the method comprising:
the desktop delivery control server receives a cloud host establishing instruction which is sent by a terminal and carries a cloud platform identifier and a resource identifier;
the desktop delivery control server responds to a cloud host creating instruction to call a docking plug-in, and calls a corresponding cloud platform interface through the docking plug-in according to the cloud platform identification to send the resource identification to a corresponding cloud platform;
and the cloud platform acquires corresponding resource data according to the resource identification, and creates a corresponding cloud host based on the resource data.
2. The method according to claim 1, wherein the obtaining, by the cloud platform, the corresponding resource data according to the resource identifier, and after creating the corresponding cloud host based on the resource data, comprises:
the desktop delivery control server acquires the created cloud host information of the cloud host, calls the docking plug-in, and sends a disk resource creating instruction carrying the cloud host information to the cloud platform;
the cloud platform responds to the disk resource creating instruction and creates a disk with a preset capacity;
the cloud platform writes the cloud host information into the preset capacity disk and mounts the preset capacity disk onto a disk service cloud host;
and the desktop delivery control server calls the docking plug-in to perform identification association on the preset capacity disk written with the cloud host information and the corresponding cloud host.
3. The method of claim 1, wherein before the desktop delivery control server receives a cloud host creation instruction carrying a cloud platform identifier and a resource identifier sent by a terminal, the method comprises:
the desktop delivery control server receives a registration instruction sent by a terminal;
and the desktop delivery control server finishes the registration of the docking plug-in according to the registration instruction.
4. The method of claim 3, wherein the desktop delivery control server completing the registration of the docking plugin according to the registration instruction comprises:
acquiring a first plug-in file and a corresponding registration path;
deleting a preset interface file from the first plug-in file to obtain a second plug-in file;
and after copying the second plug-in file to the registration path, finishing the registration of the docking plug-in based on a preset registration script file and the second plug-in file.
5. The method of claim 3, wherein after the desktop delivery control server completes registration of the docking plugin according to the registration instruction, the method comprises:
and the desktop delivery control server calls the registered docking plug-in, and is connected with the cloud platform by using the docking plug-in.
6. The method of claim 5, wherein the desktop delivery control server calls the registered docking plugin, and the docking plugin is used to connect with the cloud platform, and the method comprises:
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;
and after the desktop delivery control server verifies that the connection key is correct by using the docking plug-in, the desktop delivery control server is connected with the cloud platform based on a preset connection mode and the cloud platform identification.
7. The method of claim 5, wherein the desktop delivery control server calls the registered docking plugin, and after connecting with the cloud platform by using the docking plugin, the method comprises:
and the desktop delivery control server calls a docking plug-in to acquire resource data from the cloud platform and generates a resource identifier corresponding to the resource data.
8. A cloud host creation system, the system comprising:
the terminal is used for generating a creation instruction carrying a cloud platform identifier and a resource identifier and sending the creation instruction to the desktop delivery control server;
the desktop delivery control server is used for receiving a cloud host establishing instruction which is sent by the terminal and carries a cloud platform identifier and a resource identifier; calling a docking plug-in, and calling a corresponding cloud platform interface according to the cloud platform identification through the docking plug-in to send the resource identification to a corresponding cloud platform;
and the cloud platform is used for acquiring corresponding resource data according to the resource identifier and creating a corresponding cloud host based on the resource data.
9. The system of claim 8, wherein the desktop delivery control server is further configured to obtain cloud host information of the created cloud host, invoke the docking plugin, and send a disk resource creation instruction carrying the cloud host information to the cloud platform;
the cloud platform is further used for responding to the disk resource creating instruction and creating a disk with a preset capacity;
the cloud platform is further used for writing the cloud host information into the preset capacity disk and mounting the preset capacity disk onto a disk service cloud host;
and the desktop delivery control server calls the docking plug-in to perform identification association on the preset capacity disk written with the cloud host information and the corresponding cloud host.
10. The system of claim 8, wherein the desktop delivery control server is further configured to receive a registration instruction sent by a terminal;
and the desktop delivery control server is also used for finishing the registration of the docking plug-in according to the registration instruction.
CN201910883308.8A 2019-09-18 2019-09-18 Cloud host creation method and system Pending CN110795182A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910883308.8A CN110795182A (en) 2019-09-18 2019-09-18 Cloud host creation method and system
PCT/CN2019/117136 WO2021051534A1 (en) 2019-09-18 2019-11-11 Cloud host creation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910883308.8A CN110795182A (en) 2019-09-18 2019-09-18 Cloud host creation method and system

Publications (1)

Publication Number Publication Date
CN110795182A true CN110795182A (en) 2020-02-14

Family

ID=69427358

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910883308.8A Pending CN110795182A (en) 2019-09-18 2019-09-18 Cloud host creation method and system

Country Status (2)

Country Link
CN (1) CN110795182A (en)
WO (1) WO2021051534A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112306926A (en) * 2020-10-12 2021-02-02 苏州浪潮智能科技有限公司 Method and system for specifying virtual hard disk type in cloud platform
CN112333008A (en) * 2020-10-22 2021-02-05 济南浪潮数据技术有限公司 Cloud host complete machine backup and restoration method, device, equipment and storage medium

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241421A (en) * 2017-06-21 2017-10-10 北京云联万维技术有限公司 A kind of cloud host resource method for obligating and device
CN107463411A (en) * 2017-08-16 2017-12-12 北京新网数码信息技术有限公司 A kind of cloud main frame initial method and device
US20180095771A1 (en) * 2016-09-30 2018-04-05 Vmware, Inc. Remote Provisioning of Hosts in Public Clouds
CN107888695A (en) * 2017-11-23 2018-04-06 新华三云计算技术有限公司 Cloud platform creates the method and cloud platform equipment of mirror image
CN108449418A (en) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 A kind of mixed cloud platform management system and method
CN108462745A (en) * 2018-03-14 2018-08-28 海通证券股份有限公司 A kind of Novel cloud platform resource management and delivery method and device
CN108574718A (en) * 2017-04-19 2018-09-25 北京金山云网络技术有限公司 A kind of cloud host creation method and device
CN108984266A (en) * 2018-06-15 2018-12-11 华为技术有限公司 A kind of management method of virtual machine, apparatus and system
US20190082026A1 (en) * 2016-07-08 2019-03-14 Tencent Technology (Shenzhen) Company Limited Interface invocation method and apparatus for hybrid cloud
CN109617990A (en) * 2018-12-29 2019-04-12 长威信息科技发展股份有限公司 A kind of converged communication resource cloud sharing method and system
CN109995814A (en) * 2017-12-29 2019-07-09 中移(苏州)软件技术有限公司 Moving method and device, communication equipment, the storage medium of cloud host resource

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580302A (en) * 2013-10-18 2015-04-29 宇宙互联有限公司 Cloud service management system and cloud-cloud management system
CN106101258B (en) * 2016-07-08 2021-05-25 腾讯科技(深圳)有限公司 Interface calling method, device and system of hybrid cloud
CN108063824A (en) * 2017-12-22 2018-05-22 云南天成科技有限公司 A kind of cloud service system and construction method

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190082026A1 (en) * 2016-07-08 2019-03-14 Tencent Technology (Shenzhen) Company Limited Interface invocation method and apparatus for hybrid cloud
US20180095771A1 (en) * 2016-09-30 2018-04-05 Vmware, Inc. Remote Provisioning of Hosts in Public Clouds
CN108574718A (en) * 2017-04-19 2018-09-25 北京金山云网络技术有限公司 A kind of cloud host creation method and device
CN107241421A (en) * 2017-06-21 2017-10-10 北京云联万维技术有限公司 A kind of cloud host resource method for obligating and device
CN107463411A (en) * 2017-08-16 2017-12-12 北京新网数码信息技术有限公司 A kind of cloud main frame initial method and device
CN107888695A (en) * 2017-11-23 2018-04-06 新华三云计算技术有限公司 Cloud platform creates the method and cloud platform equipment of mirror image
CN109995814A (en) * 2017-12-29 2019-07-09 中移(苏州)软件技术有限公司 Moving method and device, communication equipment, the storage medium of cloud host resource
CN108462745A (en) * 2018-03-14 2018-08-28 海通证券股份有限公司 A kind of Novel cloud platform resource management and delivery method and device
CN108449418A (en) * 2018-03-29 2018-08-24 新华三云计算技术有限公司 A kind of mixed cloud platform management system and method
CN108984266A (en) * 2018-06-15 2018-12-11 华为技术有限公司 A kind of management method of virtual machine, apparatus and system
CN109617990A (en) * 2018-12-29 2019-04-12 长威信息科技发展股份有限公司 A kind of converged communication resource cloud sharing method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
吴坤喜: "虚拟云桌面的系统架构研究与设计", 《广东工业大学学报》, vol. 32, no. 1, pages 113 - 116 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112306926A (en) * 2020-10-12 2021-02-02 苏州浪潮智能科技有限公司 Method and system for specifying virtual hard disk type in cloud platform
CN112306926B (en) * 2020-10-12 2022-12-27 苏州浪潮智能科技有限公司 Method and system for specifying virtual hard disk type in cloud platform
CN112333008A (en) * 2020-10-22 2021-02-05 济南浪潮数据技术有限公司 Cloud host complete machine backup and restoration method, device, equipment and storage medium
CN112333008B (en) * 2020-10-22 2023-01-24 济南浪潮数据技术有限公司 Cloud host complete machine backup and restoration method, device, equipment and storage medium

Also Published As

Publication number Publication date
WO2021051534A1 (en) 2021-03-25

Similar Documents

Publication Publication Date Title
US10827008B2 (en) Integrated user interface for consuming services across different distributed networks
US11887176B2 (en) Method for registering customized device, server, and terminal
CN110019081B (en) Data persistence processing method, device and system and readable storage medium
JP6298197B2 (en) Access to supplemental data based on identifiers derived from corresponding primary application data
US10924590B1 (en) Virtual workspace experience visualization and optimization
WO2020093976A1 (en) Resource change method and device, apparatus, and storage medium
CN110795182A (en) Cloud host creation method and system
CN108459910A (en) A kind of method and apparatus for deleting resource
US11237854B2 (en) Providing a virtual desktop within a computing environment
EP3065058B1 (en) A method and a device for flowing data between entities
CN109583182B (en) Method and device for starting remote desktop, electronic equipment and computer storage medium
CN114422236B (en) Intelligent device access method and device and electronic device
CN103067365A (en) Set top box, client-side, system and method for virtual desktop access
WO2014011493A1 (en) Hybrid application environments
CN109739615B (en) Mapping method and device of virtual hard disk and cloud computing platform
CN110286956B (en) Plug-in operation method and device and electronic equipment
WO2020001617A1 (en) Method for obtaining verification information and data center
CN112910871B (en) Method for accessing artificial customer service, customer service platform and service platform
US20230345240A1 (en) Contextual authentication for secure remote sessions
US20180359211A1 (en) Systems and methods for a communication system
CN113220282A (en) Development processing method, device and storage medium for small program
CN117077194A (en) Method, system, equipment and medium for realizing electronic document signing across platforms
CN116841601A (en) Data processing method, system, computer system and storage medium
CN114741251A (en) Processing method and device for embedded point, electronic equipment and computer readable storage medium
WO2021139261A1 (en) Application deployment method and device, and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40020773

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination