CN115037742B - Method and system for autonomously supplying loose coupling idle cloud host - Google Patents
Method and system for autonomously supplying loose coupling idle cloud host Download PDFInfo
- Publication number
- CN115037742B CN115037742B CN202210432196.6A CN202210432196A CN115037742B CN 115037742 B CN115037742 B CN 115037742B CN 202210432196 A CN202210432196 A CN 202210432196A CN 115037742 B CN115037742 B CN 115037742B
- Authority
- CN
- China
- Prior art keywords
- client
- cloud host
- data table
- service interface
- mac address
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000008878 coupling Effects 0.000 title abstract description 7
- 238000010168 coupling process Methods 0.000 title abstract description 7
- 238000005859 coupling reaction Methods 0.000 title abstract description 7
- 235000013599 spices Nutrition 0.000 claims description 44
- 238000001514 detection method Methods 0.000 claims description 2
- 238000012544 monitoring process Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 3
- 238000012800 visualization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- 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/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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a method and a system for independently supplying a loose coupling idle cloud host based on an open source OpenStack platform, an open source Spi ce Server and a C I ent, belonging to the technical field of desktop virtualization, and comprising the following steps: s1, integrating relevant information of an OpenStack platform and client information, creating a database and generating a data table module; s2, an SOA service interface is established by depending on an OpenStack platform AP I and a Li bvi rt AP I; s3, updating the service process of the idle cloud host information in the data table in the step S1 at regular time; s4, the client selects an idle cloud host login module; s5, the client calls the Sp i ce C l i ent terminal to successfully log in the cloud host, adds the center jump time of the data table and the Mac address of the client in the step S1, and monitors Sp i ce C l i ent the terminal process in real time; s6, the client side updates the center jump time of the data table in the step S1 at regular time; and S7, the client deletes the center jump time of the data table and the Mac address of the client in the step S1 and exits.
Description
Technical Field
The invention relates to the technical field of desktop virtualization, in particular to an idle cloud host autonomous supply method and system based on an open source OpenStack platform, an open source Spice Server and a Client, which are loosely coupled with a native environment (the OpenStack platform, the Spice Server and the Client) and have stronger use universality.
Background
The open source OpenStack platform implements server virtualization, virtualizing servers as multiple cloud hosts to provide user usage.
The open source Spice Server and the Client adopt an open source Spice protocol to realize the visualization of the cloud host desktop, and provide different cloud host desktop services for different users. The Spice Server is distributed to different port numbers of different cloud hosts, and the Spice Client realizes the desktop visualization of the cloud hosts based on the port numbers by utilizing the Spice protocol.
For any cloud host user, two blind areas exist in the use of the Spice Client: 1. the port number information distributed to different cloud hosts by the Spice Server is not clear; 2. whether the current cloud host resources are occupied or not is unclear, the idle cloud host cannot be accurately acquired to cause use conflict, and user experience is unfriendly.
Disclosure of Invention
In order to solve the problems, the invention provides a loose coupling idle cloud host autonomous supply method and a system, wherein the method mainly aims to construct a cloud host use data table and update at fixed time so as to realize idle cloud host judgment, the idle cloud host autonomous supply is realized by means of the system, and the method and the system are loosely coupled with open-source native environments (Openstack, spice Server and Spice Client).
The technical scheme of the invention is as follows:
the technical scheme adopted by the invention is as follows: a method and system for self-provisioning of loosely coupled idle cloud hosts, comprising:
s1, integrating OpenStack related information and client information, creating a database and generating a data module;
s2, an SOA service interface is established by relying on an OpenStack platform API, a Libvirt API and the data table generated in the step S1;
s3, calling an S2SOA service interface, and updating the hollow cloud host information service process in the data table generated in the step S1 at regular time;
s4, the client selects an item to log in the cloud host, the step S2 is called to judge whether an idle cloud host belonging to the selected item exists or not, the step S5 is executed if the idle cloud host belongs to the selected item, and the login operation is ended if the idle cloud host does not exist;
s5, a Client hiding panel is used for calling the Spice Client terminal to successfully log in the cloud host, a step S2SOA service interface is used for adding the Client heartbeat time and the Client Mac address to the step S1 data table, the Spice Client terminal process is monitored in real time, and when the Spice Client terminal process exists, the step 6 is executed, otherwise, the step 7 is executed.
S6, the client calls the step S2SOA service interface to update the heartbeat time of the client terminal in the data table in the step S1 at regular time.
And S7, the client calls the step S2SOA service interface to delete the heartbeat time of the client and the Mac address of the client in the data table in the step S1 and finish the process.
In the above method, in step S1, four data tables are generated, the table structure is shown in fig. 1 to 4 attached to the description, and the method and the system provided by the invention are based on the four data tables.
In the above method, in step S2, a service-oriented component is constructed by using the Openstack platform API, the Libvirt API, and the data table generated in S1, and the implementation functions include: querying an Openstack platform Mysql database, starting a cloud host, querying a cloud host service port number, adding and deleting data tables generated by the search S1, and the like.
In the method, in step S3, the related information of the cloud host in the data table generated in step S1 is analyzed by calling the SOA service interface in step S2, and the running state (active or stop) of the cloud host is queried and whether the heartbeat time is out of date is judged regularly, if the running state of the cloud host is stop, the cloud host is started and the Mac address and heartbeat time information occupying the client of the cloud host are deleted; and if the heartbeat time of the cloud host is out of date, deleting the Mac address and the heartbeat time information occupying the client side of the cloud host. The basis for judging the idle state of the cloud host is divided into three cases: the cloud host is in a state of stop, no occupied client Mac address and heartbeat time exist, occupied client Mac address and heartbeat time exist and heartbeat time is over.
In the above method, in step S4, the client first selects the item to log in the cloud host, performs a judgment of the idle cloud host, and performs the operation of S5. The judging process comprises the following steps: (1) judging the correctness of the client setting, displaying prompt information if the client setting is wrong, and executing the step (2) if the client setting is correct; (2) invoking step S2SOA to inquire that the current state of a cloud host belonging to the selected item is a stop record, invoking step S2SOA if the current state is the stop record, starting the cloud host by utilizing UUID of the cloud host in the record, deleting Mac address and heartbeat time field value of the record Client, invoking step S2SOA to inquire the Spice port number corresponding to UUID of the cloud host in the record, invoking Spice Client terminal, logging in the cloud host, and executing step S5; if not, executing the step (3); (3) invoking step S2SOA to query a record with an Mac address being empty in the S1 data table, invoking step S2SOA to query a service port number corresponding to a UUID of the cloud host in the record, invoking a service Client terminal, logging in the cloud host, and executing step S5; if not, executing the step (4); (4) invoking step S2 the SOA returns a record (wherein the cloud host is affiliated with the selected item) satisfying: the current time minus the Client heartbeat time field value in the step S1 data table is greater than the hyper-parameter Client heartbeat interval time threshold value, if the current time minus the Client heartbeat time field value is greater than the hyper-parameter Client heartbeat interval time threshold value, calling a step S2SOA, deleting the Mac address of the recorded Client and the Client heartbeat time field value, calling the step S2SOA to inquire the Spice port number corresponding to the UUID of the cloud host in the record, calling the Spice Client terminal, logging in the cloud host, and executing the step S5; if not, displaying prompt information and ending the login.
In the above method, in step S5, the Client hides the panel, calls the alice Client terminal to successfully log in the cloud host, adds the Client heartbeat time and the Client Mac address to the data table in step S1, and monitors the process of the alice Client terminal in real time.
In the above method, in step S6, the client periodically updates the heartbeat time of the client terminal in the data table in step S1.
In the above method, in step S7, the client deletes the client heartbeat time and the client Mac address in the data table in step S1 and exits.
The beneficial effects are that: 1. according to the method and the system for autonomously supplying the loosely coupled idle cloud host, the cloud host service condition data table is constructed, and the idle cloud host can be known by inquiring the data table. The idle cloud host is divided into three cases: the cloud host is in a state of stop, no occupied client Mac address and heartbeat time exist, occupied client Mac address and heartbeat time exist and heartbeat time is over. The cloud host information is prevented from being known by a user through autonomous judgment of the idle cloud host and the client, and the cloud host information is provided for the user in a black box mode. 2. According to the method and the system for autonomously supplying the loosely coupled idle cloud host, in the steps S7 and S3, resources of the cloud host can be timely released, and the utilization rate is improved. 3. The method and the system for autonomously supplying the loose coupling idle cloud host realize loose coupling with the original environment (an open source Openstack platform, an open source Spice Server and a Client) through the data table generated by the S1 and the SOA service interface established by the S2, are loose coupled with the version and the applicable operating system, are convenient for users to use, and have strong universality.
Drawings
The invention will be further described with reference to the accompanying drawings, in which:
FIG. 1 is an OpenInf table structure in a system database of the present invention;
FIG. 2 is a Pro_Inf table structure in the system database of the present invention;
FIG. 3 is a CcB _auto table structure in the system database of the present invention;
FIG. 4 is a Pro_Inf table structure in the system database of the present invention;
FIG. 5 is a system database initialization interface of the present invention;
FIG. 6 is a panel diagram of a client cloud desktop login terminal according to the present invention;
FIG. 7 is a panel diagram of a client cloud desktop login terminal according to the present invention;
FIG. 8 is a panel diagram of a client cloud desktop login terminal according to the present invention;
FIG. 9 is a flowchart of a data table idle cloud host information service process generated in the step S1 of updating the timing of the present invention;
FIG. 10 is a flow chart of client login cloud desktop according to the present invention;
FIG. 11 is a flow chart of a method and system for self-provisioning of a loosely coupled, idle cloud host in accordance with the present invention;
Detailed Description
The present invention will be described in further detail below in order to make the objects, technical solutions and effects of the present invention more clear and distinct.
A method and a system for autonomously supplying a loosely coupled idle cloud host are used for judging whether the cloud host is idle in an open source Openstack virtualization system and autonomously supplying users. Judging whether the cloud host is idle or not and autonomously supplying the cloud host to the user system, wherein the cloud host comprises a system database, an initialization Web, SOA component services, a service process for updating idle information of the cloud host, a cloud host login terminal and the like. The cloud host login terminal adopts an open source Spice protocol, and the specific implementation of the cloud host login terminal is completed by an open source Spice Server and Spice Client terminal.
The system realizes independent supply of the loose coupling idle cloud host based on an open source Openstack platform, an open source Spice Server and Spice Client. The default preconditions are that the open source Openstack platform is built, the Spice Server is installed, and the Spice Client terminal is generated.
The system database table supporting autonomous provisioning of the loosely coupled idle cloud host includes: four tables of open_inf, pro_inf, ccb_auto, htb_inv, etc., as shown in fig. 1-4.
Open_inf table, as shown in fig. 1. The method comprises the steps that connection of three fields of a controller_ip, a mysql_port, a mysql_user and a mysql_password to an Openstack platform Mysql database is realized, so that table information in the database is acquired; three fields of the controller_ ip, controller _ user, controller _password are used for realizing the Libvirt API in the step S2; the identity field is used to implement Openstack API rights authentication.
Pro_Inf table, as shown in FIG. 2, five fields are used to implement the Openstack platform project_name project_membrane_name user rights authentication.
The CcB _auto table records the cloudcomputer_uuid cloud host idle status under the project_name item, as shown in fig. 3, where the client_mac field indicates the Mac address of the client that is using the cloudhost UUID as the cloudcomputer_uuid, and the client_heartbeat field indicates the heartbeat time of the client that is using the cloudhost UUID as the cloudcomputer_uuid.
HtB _Inv table, as shown in FIG. 4, the client_heartbeat_interval threshold represents a client heartbeat time interval threshold, and is used for judging whether the current cloud host is being used by the client, if the client heartbeat time and the current time difference are greater than the threshold, the cloud host is in an idle state currently, otherwise, the cloud host is in an occupied state currently; the client_heartbeat_sendtimer_val indicates that the client is sending a heartbeat interval at regular time to update the client_heartbeat field in the CcB _auto table; the s3_executioninterval field indicates a service process step S3 loop execution interval for updating cloud host idle information.
FIG. 5 is an initializing Web interface for a system database, implementing data initialization for the system database. In addition to the two fields of the client_name and client_heartbeat in the system database CcB _auto table, other fields and other data tables will be populated with data in this initialization. Wherein the two fields of project_name and cloutcomputer_uuid in CcB _auto table call the SOA component service to implement the filling of data in step S2.
And after the data initialization in the system database is completed, the actual cloud host login operation is performed.
The user selects an item needing to be logged in, such as ComputerCourse, clicks a login button, firstly carries out configuration detection on the Spice Client terminal, returns prompt information shown in fig. 7 if the position of the Spice Client terminal running file is not detected or the service IP address of the SOA component in step S2 is incorrect, and otherwise carries out searching and login operation of the idle cloud host. Fig. 8 is a configuration interface of a Spice Client terminal, and fig. 10 is a flowchart of a Client logging into a cloud desktop.
The idle cloud host searching steps are as follows: (1) according to the IP address of the component service of the step S2SOA in the configuration of the Client-side Spice Client, the step S2SOA is called to inquire that the current state of a cloud host (belonging to and selecting items) is a stop record, if the current state of the cloud host is a stop record, the step S2SOA is called, cloud host starting is carried out by utilizing UUIDs of the cloud hosts in the record, the values of the fields of the Client-side mac and the Client-side Spice are deleted, the step S2SOA is called to inquire the Spice port number corresponding to the UUIDs of the cloud hosts in the record, finally, the Spice Client terminal is called, the cloud host is logged in, and the step S5 is continuously executed; if not, executing the step (2); (2) invoking step S2SOA to query a record with an empty Mac address in the CcB _auto table (wherein the UUID of the cloud host belongs to a selected item), if the record exists, invoking step S2SOA to query a Spice port number corresponding to the UUID of the cloud host in the record, invoking a Spice Client terminal, logging in the cloud host, and continuing to execute step S5; if not, executing the step (3); (3) invoking step S2 the SOA returns a record (wherein the cloud host UUID is affiliated with the selected item) satisfying: the current time minus CcB _auto table client_heartbeat field value is greater than the client_heartbeat_ interval threshold field value in HtB _Inv table, if yes, calling step S2SOA, deleting the record client_mac and the client_heartbeat field value, calling step S2SOA to inquire the service port number corresponding to the cloud host UUID in the record, calling the service Client terminal, logging in the cloud host, and continuing to execute step S5; if the display prompt information does not exist, the display prompt information is shown in fig. 6.
Step S5 is an operation in the case where there is an idle cloud host. Firstly, hiding a Client panel, calling an S2SOA to add data to two fields of a client_mac and a client_heartbeat in a system data table CcB _auto, and monitoring a Spice Client terminal process in real time. And S6, executing the operation when the Spice Client terminal process exists, otherwise, executing the operation S7.
Step S6 is an operation performed by one timing cycle. If the step S2SOA is invoked to calculate that the current time minus the last heartbeat time of the client is greater than the client_heartbeat_senddinginterval field value in the HtB _inv table, the heartbeat time corresponding to the Mac address of the client in the CcB _auto table is updated.
The step S7 operation is an operation after detecting that the Spice Client terminal process exits. Firstly, calling step S2SOA to delete the client_mac and client_heartbeat field data in the CcB _auto table, and then ending the client process.
Claims (1)
1. A method for autonomous provisioning of a loosely coupled, idle cloud host, comprising:
s1, integrating relevant information of an OpenStack platform and client information, creating a database, and generating a data table;
s2, an SOA service interface is established by relying on an OpenStack platform API, a Libvirt API and the data table generated in the step S1;
s3, calling the SOA service interface in the step S2, and updating the hollow cloud host information service process in the data table generated in the step S1 at regular time;
s4, the client selects an item to log in the cloud host, firstly, client setting detection is carried out, prompt information is displayed if the setting is incorrect, the SOA service interface in the step S2 is called to judge whether an idle cloud host belonging to the selected item exists or not if the idle cloud host belongs to the selected item, the step S5 is executed, and the login operation is ended if the idle cloud host does not exist;
s5, hiding a panel by the Client, calling an SOA service interface in the step S2 to splice a Spice Client to log in a cloud host address, calling the Spice Client terminal to log in the cloud host successfully, calling the SOA service interface in the step S2 to add the Client heartbeat time and the Client Mac address to the data table in the step S1, monitoring the Spice Client terminal process in real time, and executing the step 6 when the Spice Client terminal process exists, otherwise, executing the step 7;
s6, the client calls the SOA service interface in the step S2 to update the heartbeat time of the client terminal in the data table in the step S1 at regular time;
s7, the client calls the SOA service interface in the step S2 to delete the heartbeat time of the client and the Mac address of the client in the data table in the step S1 and ends the process;
in the step S2, a service-oriented component is constructed by using the Openstack platform API, the Libvirt API and the data table generated in the step S1, and the implementation functions include: querying a Mysql database of an Openstack platform, starting a cloud host, querying a cloud host service port number, adding and deleting data, and checking the data table operation generated by S1;
in the step S3, the related information of the cloud host in the data table generated in the step S1 is analyzed by calling the SOA service interface in the step S2, and whether the running state of the cloud host and the heartbeat time are out of date or not is judged at regular time, wherein the running state of the cloud host comprises active or stop, and if the running state of the cloud host is stop, the cloud host is started and Mac address and heartbeat time information occupying the client of the cloud host are deleted; if the heartbeat time of the cloud host expires, deleting Mac address and heartbeat time information occupying the client of the cloud host; the basis for judging the idle state of the cloud host is divided into three cases: the cloud host running state is stop, the occupied client Mac address and the heartbeat time do not exist, the occupied client Mac address and the heartbeat time exist, and the heartbeat time is over;
in the step S4, the client first selects a project to log in the cloud host, performs a judgment of an idle cloud host, and performs the operation of S5; the judging process comprises the following steps: (1) judging the correctness of the client setting, displaying prompt information if the client setting is wrong, and executing the step (2) if the client setting is correct; (2) invoking an SOA service interface in the step S2 to inquire that the current state of a cloud host belonging to the selected item is a stop record, invoking the SOA service interface in the step S2 if the current state is the stop record, starting the cloud host by utilizing the UUID of the cloud host in the record, deleting the Mac address and the heartbeat time field value of the record Client, invoking the SOA service interface in the step S2 to inquire the service port number corresponding to the UUID of the cloud host in the record, invoking the service Client terminal, logging in the cloud host, and executing the step S5; if not, executing the step (3); (3) invoking an SOA service interface in the step S2 to query a record with an empty Mac address in the data table in the step S1, invoking a Spice port number corresponding to a UUID of a cloud host in the SOA service interface query record in the step S2 if the record exists, invoking a Spice Client terminal, logging in the cloud host, and executing the step S5; if not, executing the step (4); (4) and (3) calling the SOA service interface in the step S2 to return a record, wherein the record meets the following conditions: the current time minus the Client heartbeat time field value in the data table of step S1 is greater than the hyper-parameter Client heartbeat interval time threshold value, if present, the SOA service interface of step S2 is invoked, deleting and recording the Mac address and the heartbeat time field value of the Client, calling the SOA service interface in the step S2 to inquire the service port number corresponding to the UUID of the cloud host in the record, calling the service Client terminal, logging in the cloud host, and executing the step S5; if not, displaying prompt information and ending the login;
in the step S5, the Client hides the panel, calls the alice Client terminal to successfully log in the cloud host, adds the heartbeat time of the Client and the Mac address of the Client to the data table in the step S1, and monitors the process of the alice Client terminal in real time;
in the step S6, the client updates the heartbeat time of the client terminal in the data table in the step S1 at regular time;
in the step S7, the client deletes the heartbeat time of the client and the Mac address of the client in the data table in the step S1 and exits.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210432196.6A CN115037742B (en) | 2022-04-22 | 2022-04-22 | Method and system for autonomously supplying loose coupling idle cloud host |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210432196.6A CN115037742B (en) | 2022-04-22 | 2022-04-22 | Method and system for autonomously supplying loose coupling idle cloud host |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115037742A CN115037742A (en) | 2022-09-09 |
| CN115037742B true CN115037742B (en) | 2024-02-20 |
Family
ID=83119255
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210432196.6A Active CN115037742B (en) | 2022-04-22 | 2022-04-22 | Method and system for autonomously supplying loose coupling idle cloud host |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115037742B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051710A (en) * | 2012-12-20 | 2013-04-17 | 中国科学院深圳先进技术研究院 | Virtual cloud platform management system and method |
| CN107181808A (en) * | 2017-06-01 | 2017-09-19 | 安徽祥云科技有限公司 | A kind of privately owned cloud system and operation method |
| CN107682445A (en) * | 2017-10-24 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of building method of the mobile cloud desktop platform based on cloud framework |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10949903B2 (en) * | 2017-05-05 | 2021-03-16 | Servicenow, Inc. | System, computer-readable medium, and method for blueprint-based cloud management |
-
2022
- 2022-04-22 CN CN202210432196.6A patent/CN115037742B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051710A (en) * | 2012-12-20 | 2013-04-17 | 中国科学院深圳先进技术研究院 | Virtual cloud platform management system and method |
| CN107181808A (en) * | 2017-06-01 | 2017-09-19 | 安徽祥云科技有限公司 | A kind of privately owned cloud system and operation method |
| CN107682445A (en) * | 2017-10-24 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of building method of the mobile cloud desktop platform based on cloud framework |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115037742A (en) | 2022-09-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10747569B2 (en) | Systems and methods of discovering and traversing coexisting topologies | |
| EP1267518B1 (en) | Multiple device management method and system | |
| US10331505B2 (en) | Application programming interface (API) hub | |
| CN108632354B (en) | Physical machine admission management method and device and cloud desktop management platform | |
| WO2020134545A1 (en) | Method for updating configuration, and related product | |
| US7254778B2 (en) | System and method browsing a network topology using a character driven interface | |
| CN103283209A (en) | Application service platform system and implementation method thereof | |
| WO2015101320A1 (en) | Account number generation method, terminal and background server | |
| CN107544837A (en) | Cloud service device performance data acquisition system, method and apparatus | |
| CN102413125B (en) | Single-point login method and system | |
| US20130047092A1 (en) | Communication client and a method for initiating a communication service | |
| CN115037742B (en) | Method and system for autonomously supplying loose coupling idle cloud host | |
| CN111125050A (en) | CephFS-based file storage method for providing NFS protocol in openstack environment | |
| KR20210089113A (en) | A method, an apparatus, an electronic device and a storage medium for communicating between private networks | |
| CN109918210B (en) | Method and terminal for displaying offline message | |
| CN110609763B (en) | Method, electronic device, and computer-readable medium for managing and executing data backup jobs | |
| CN116016209A (en) | Network automation method and device | |
| WO2012066652A1 (en) | Method for finding communication devices connected to communication network, and management device | |
| CN111949719B (en) | Method and device for realizing configuration tool of power system and related components | |
| US11770436B2 (en) | Web client with response latency awareness | |
| US11055079B2 (en) | Systems and methods for just-in-time application implementation | |
| Cisco | Using the Administration Application | |
| CN109451053B (en) | Page resource request message sending method, device, medium and computer equipment | |
| CN108881344B (en) | Service processing method and device, storage equipment and processing server | |
| CN110781001A (en) | Kubernetes-based container environment variable checking method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |