CN111131440A - Resource scheduling method and device and server - Google Patents

Resource scheduling method and device and server Download PDF

Info

Publication number
CN111131440A
CN111131440A CN201911330558.5A CN201911330558A CN111131440A CN 111131440 A CN111131440 A CN 111131440A CN 201911330558 A CN201911330558 A CN 201911330558A CN 111131440 A CN111131440 A CN 111131440A
Authority
CN
China
Prior art keywords
server
instance
host
target
resource
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.)
Granted
Application number
CN201911330558.5A
Other languages
Chinese (zh)
Other versions
CN111131440B (en
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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201911330558.5A priority Critical patent/CN111131440B/en
Publication of CN111131440A publication Critical patent/CN111131440A/en
Application granted granted Critical
Publication of CN111131440B publication Critical patent/CN111131440B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms

Abstract

The disclosure provides a resource scheduling method, a resource scheduling device and a server, and relates to the technical field of cloud services. The method comprises the following steps: a first server receives a first resource calling request sent by a terminal; generating a second resource calling request according to the target server identification and the operation category; the second server calls the target host instance corresponding to the target server identification according to the second resource calling request, and executes the operation corresponding to the operation type, so that the cloud server of the first server is changed from multiple cloud servers to one cloud server, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.

Description

Resource scheduling method and device and server
Technical Field
The disclosure relates to the technical field of cloud services, and in particular to a resource scheduling method, a resource scheduling device and a server.
Background
In order to improve the user experience, an application developer provides a custom interface or an editing interface for a user, so that the user can perform operations such as customization or editing on the application. After the terminal finishes self-defining or editing application, the relevant data which are self-defined or edited can be uploaded to the server. With the development of cloud service technology, more and more application developers design usable cloud servers of the application, and a user can call the usable cloud servers through the usable cloud servers to store related data.
In the related art, different users may use cloud servers provided by different cloud server developers. And a cloud server developer designs an operation page or API (Application programming interface) of the cloud server itself. Therefore, the operating page or API is different for different cloud servers. In order to meet the use requirements of more users, when an application developer develops an application server, the application developer needs to deploy the server on cloud servers developed by different developers so as to meet the requirements of different users for calling the cloud servers.
In the related art, in the process of application development or maintenance, different cloud servers deployed for the servers need to be developed, so that the application development time is prolonged, and the application development efficiency is low.
Disclosure of Invention
The embodiment of the disclosure provides a resource scheduling method, a resource scheduling device and a server, and the technical scheme for improving the development efficiency of an application program across a plurality of cloud servers is as follows:
in one aspect, a method for scheduling resources is provided, where the method includes:
receiving a first resource calling request sent by a terminal, wherein the first resource calling request carries the operation category of the resource calling operation and a target server identifier of a target cloud server;
generating a second resource calling request according to the target server identification and the operation category;
and calling a second server through the second resource calling request, executing the operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing the operation corresponding to the operation category through calling the target host instance.
In a possible implementation manner, before the receiving the first resource invocation request sent by the terminal, the method further includes:
receiving a plurality of server identifications of a plurality of cloud servers sent by the second server, wherein the plurality of cloud servers are cloud servers for generating a plurality of host instances stored in the second server;
after receiving the first resource calling request sent by the terminal, the method further includes:
determining a target server identifier carried by the first resource request;
when the target server identifier exists in the plurality of server identifiers, executing the step of generating a second resource calling request according to the target server identifier and the operation category;
when the target server identification does not exist in the plurality of server identifications, generating prompt information; and sending the prompt information to the terminal, wherein the terminal is used for receiving the prompt information and displaying the prompt information, and the prompt information is used for prompting a user that the identification of the current target server is wrong.
In another possible implementation manner, when the operation type is to acquire a host instance, the invoking a second server through the second resource invocation request includes:
sending the second resource calling request to the second server, where the second resource calling request is used to request the second server to call a host instance in a target cloud server, and the second server is used to determine, according to the second resource calling request, a target host instance corresponding to a target server identifier from cached multiple host instance information, and send instance information of the target host instance to the first server;
receiving instance information of a target host instance sent by the second server;
and sending the instance information to the terminal.
In another aspect, a method for resource invocation is provided, the method comprising:
sending a host instance obtaining request to a plurality of cloud servers, wherein the host instance obtaining request is used for requesting the plurality of cloud servers to generate at least one host instance, and sending instance information of the at least one host instance to a second server, wherein the instance information comprises a server identifier of the cloud server generating the host instance;
receiving instance information of at least one host instance sent by a plurality of cloud servers;
storing instance information for at least one of said host instances;
when a second resource calling request sent by a first server is received, determining a target server identifier of a target cloud server according to the second resource calling request, wherein the second resource calling request carries the operation category of the resource calling operation and the target server identifier of the target cloud server;
selecting a target host instance from at least one stored host instance according to the target cloud server identification and the instance information of the at least one host instance;
and executing the operation corresponding to the operation type of the resource calling operation according to the target host example.
In one possible implementation, when the operation type is to acquire a host instance;
the executing the operation corresponding to the operation type of the resource calling operation according to the target host example comprises:
and sending the instance information of the target host instance to the first server, wherein the first server is used for receiving the instance information of the target host instance and sending the instance information of the target host instance to a terminal.
In another possible implementation manner, the method further includes:
periodically detecting the number of host instances corresponding to the plurality of stored cloud servers;
and when the number of the host instances is smaller than the preset number, executing a step of sending host instance acquisition requests to a plurality of cloud servers.
In another possible implementation manner, the storing instance information of at least one of the host instances includes:
configuring the received at least one host instance according to the server parameters of the first server;
storing instance information of at least one of the host instances for which configuration is complete.
In another aspect, an apparatus for scheduling resources is provided, the apparatus including:
the first receiving module is used for receiving a first resource calling request sent by a terminal, wherein the first resource calling request carries the operation category of the resource calling operation and the target server identification of a target cloud server;
the first generation module is used for generating a second resource calling request according to the target server identification and the operation type;
the calling module is used for calling a second server through the second resource calling request, executing the operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the plurality of instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing the operation corresponding to the operation category through calling the target host instance.
In one possible implementation, the apparatus further includes:
a second receiving module, configured to receive a plurality of server identifiers of a plurality of cloud servers sent by the second server, where the plurality of cloud servers are cloud servers that generate a plurality of host instances stored in the second server;
a first determining module, configured to determine a target server identifier carried by the first resource request;
the calling module is further configured to generate a second resource calling request according to the target server identifier and the operation category when the target server identifier exists in the plurality of server identifiers;
the second generation module is used for generating prompt information when the target server identifier does not exist in the plurality of server identifiers; and sending the prompt information to the terminal, wherein the terminal is used for receiving the prompt information and displaying the prompt information, and the prompt information is used for prompting a user that the identification of the current target server is wrong.
In another possible implementation manner, when the operation type is to acquire a host instance, the invoking module is further configured to send the second resource invoking request to the second server, where the second resource invoking request is used to request the second server to invoke the host instance in the target cloud server, and the second server is configured to determine, according to the second resource invoking request, a target host instance corresponding to a target server identifier from the cached information of multiple host instances, and send instance information of the target host instance to the first server; receiving instance information of a target host instance sent by the second server; and sending the instance information to the terminal.
In another aspect, an apparatus for resource invocation is provided, the apparatus including:
a sending module, configured to send a host instance obtaining request to a plurality of cloud servers, where the host instance obtaining request is used to request the plurality of cloud servers to generate at least one host instance, and send instance information of the at least one host instance to a second server, where the instance information includes a server identifier of a cloud server that generates the host instance;
a third receiving module, configured to receive instance information of at least one host instance sent by multiple cloud servers;
the storage module is used for storing the instance information of at least one host instance;
the second determining module is used for determining a target server identifier of a target cloud server according to a second resource calling request when the second resource calling request sent by the first server is received, wherein the second resource calling request carries the operation type of the resource calling operation and the target server identifier of the target cloud server;
the selecting module is used for selecting a target host instance from at least one stored host instance according to the target cloud server identification and the instance information of the at least one host instance;
and the operation execution module is used for executing the operation corresponding to the operation type of the resource calling operation according to the target host example.
In another possible implementation manner, when the operation type is to acquire a host instance;
the operation execution module is further configured to send instance information of the target host instance to the first server, where the first server is configured to receive the instance information of the target host instance and send the instance information of the target host instance to a terminal.
In another possible implementation manner, the apparatus further includes:
the detection module is used for periodically detecting the number of the stored host instances corresponding to the plurality of cloud servers;
the sending module is further configured to send a host instance obtaining request to the plurality of cloud servers when the number of the host instances is smaller than a preset number.
In another possible implementation manner, the storage module is further configured to configure the received at least one host instance according to a server parameter of the first server; storing instance information of at least one of the host instances for which configuration is complete.
In another aspect, a server is provided, where the server includes a processor and a memory, where the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the resource calling method according to the embodiment of the present disclosure.
In another aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, the at least one instruction being loaded and executed by a processor to implement a resource calling method as described in an embodiment of the present disclosure.
The technical scheme provided by the embodiment of the disclosure has the following beneficial effects:
in the embodiment of the disclosure, a first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries an operation category of a current resource calling operation and a target server identifier of a target cloud server; generating a second resource calling request according to the target server identification and the operation category; and calling a second server through a second resource calling request, executing operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing operation corresponding to the operation category through calling the target host instance. Therefore, the cloud servers of the first server are changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
Fig. 1 is a schematic diagram illustrating an implementation environment involved in a resource scheduling method according to an exemplary embodiment of the present disclosure;
FIG. 2 is a flowchart of a method for scheduling resources according to an exemplary embodiment;
FIG. 3 is a timing diagram illustrating a method for scheduling resources according to an exemplary embodiment;
FIG. 4 is a flowchart of a method for scheduling resources according to an example embodiment;
FIG. 5 is a flowchart of a method for scheduling resources according to an exemplary embodiment;
fig. 6 is a block diagram of a resource scheduling apparatus according to an exemplary embodiment;
fig. 7 is a block diagram of a resource scheduling apparatus according to an exemplary embodiment;
fig. 8 is a schematic structural diagram of a server provided according to an embodiment of the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the present disclosure more apparent, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a schematic diagram illustrating an implementation environment involved in a resource scheduling method according to an exemplary embodiment of the present disclosure. Referring to fig. 1, the implementation environment includes: the terminal comprises a terminal 101, a first server 102, a second server 103 and a plurality of cloud servers 104. The data interaction between the terminal 101 and the first server 102 may be performed through a network connection, the data interaction between the first server 102 and the second server 103 may be performed through a network connection, and the data interaction between the second server 103 and each cloud server 104 may be performed through a network connection or a data interface.
An application program may be installed in the terminal 101, and the application program may call a host instance in the cloud server 104. The terminal 101 may be a mobile phone, a computer, a tablet computer, or an intelligent wearable device. The application program can provide a user with a user-defined interface or an application program with an editing interface, the user can define the content of the application program by the user-defined interface, and the user can edit the content of the application program by the editing interface. For example, the application program may be a game application including a game map, an interface for customizing the game map is provided for the user in the game application, and accordingly, the user may customize the game map in the game through the customized interface and upload the relevant data of the game map to the cloud server 104.
The first server 102 is a background server for the application program and is used for providing services for the application program in the terminal 101. The second server 103 is a resource call server, the second server 103 may store information of a plurality of cloud resources of a plurality of cloud servers 104, the cloud resources may be host instances, and correspondingly, the information of the cloud resources may be instance information of the host instances. When the second server 103 receives the second resource calling request sent by the first server 102, the host instance matched with the target cloud server 104 is called according to the second resource calling request sent by the first server 102, and the operation matched with the operation category is executed, wherein the operation category can be operation of obtaining the host instance, host password modification, host name modification, power on and power off and the like. Each cloud server 104 may generate at least one host instance and send information of the generated host instance to the second server 103, so that the second server 103 may store instance information of the at least one host instance for the first server 102 to tune.
In the implementation manner, a first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries an operation category of the resource calling operation and a target server identifier of a target cloud server; generating a second resource calling request according to the target server identification and the operation category; and calling a second server through a second resource calling request, executing operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing operation corresponding to the operation category through calling the target host instance. Therefore, the cloud servers of the first server are changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
Fig. 2 is a flowchart of a resource scheduling method according to an exemplary embodiment, and in the embodiment of the present disclosure, a second server acquires host instances of a plurality of cloud servers as an example for description. As shown in fig. 2, the method comprises the steps of:
step 201: the second server sends host instance acquisition requests to the plurality of cloud servers.
The plurality of cloud servers are developed and maintained by different cloud server developers respectively. Therefore, when the second server calls the host instance in any cloud server, the host instance corresponding to the cloud server needs to be called according to the data interface matched with the cloud server. A developer of the second server may develop the second server for a different cloud server. Correspondingly, in the development process of the second server, a developer of the second server develops the resource calling code of the second server according to the data interfaces of different cloud servers. The resource calling code is used for calling a data interface of the cloud server matched with the resource calling code when the code is operated, and sending a host instance obtaining request to the cloud server through the data interface.
The host instance acquisition request carries the server identifier of the second server.
As shown in fig. 3 and fig. 4, fig. 3 is a timing diagram of a resource scheduling method according to an exemplary embodiment, and fig. 4 is a flowchart of a resource scheduling method according to an exemplary embodiment, where instance information of host instances of a plurality of cloud servers may be stored in a second server. Correspondingly, when the second server acquires the host instance information of the plurality of cloud servers, the second server may send host instance acquisition requests to the plurality of cloud servers respectively. In one possible implementation, the second server may periodically send a host instance acquisition request to the cloud server. The period in which the second server sends the host instance obtaining request to the cloud server may be a first preset duration.
It should be noted that, the second server may send the host instance obtaining request to the multiple cloud servers at the same time every other first preset time, and the second server may also send the resource obtaining request to the cloud server corresponding to the first preset time every other first preset time, which is not specifically limited in the embodiment of the present disclosure. The first preset time length may be set as needed, and the first preset time lengths corresponding to different cloud servers may be the same or different. For example, the first preset time period may be 10min, 30min, 1h, or the like.
In the implementation manner, the second server sends the host instance obtaining request to the cloud server every first preset time, so that the number of the host instances in the second server is sufficient, the second server can directly call the locally stored host instances, the time required by the cloud server to generate the host instances is saved, and the speed of the second server calling the host instances of the cloud server is improved.
In another possible implementation manner, the second server determines the number of currently stored available host instances, and when the number of available host instances is smaller than a preset number, the second server sends a host instance obtaining request to the cloud server.
In the implementation manner, the second server sends the host instance obtaining request to the cloud server according to the number of the available host instances cached currently, so that the host instances generated by the cloud server cannot be used in time and the host instance waste is caused when the number of the available host instances stored in the second server is too large while the number of the host instances in the second server is ensured to be sufficient.
It should be noted that the second server may count the number of available host instances cached in the second server in real time; the second server can also detect the number of host instances cached currently when receiving a second resource calling request sent by the first server; the second server can also periodically detect the number of the stored host instances corresponding to the plurality of cloud servers, and when the number of the host instances is smaller than a preset number, the second server sends host instance obtaining requests to the plurality of cloud servers.
The period of detecting, by the second server, the number of host instances corresponding to the plurality of cloud servers may be a second preset time duration, where the second preset time duration may be the same as the first preset time duration, the second preset time duration may also be different from the first preset time duration, and the second preset time duration may also be set and changed as needed, which is not specifically limited in the embodiment of the present disclosure. For example, the second preset time period may be 10min, 30min, 1h, or the like.
The first server may detect the total number of the currently stored available host instances, and the second server may also detect the number of the available host instances corresponding to each cloud server respectively. Correspondingly, the preset number may be the total number of available host instances of all cloud servers currently cached; the preset number may also be the number of available host instances respectively corresponding to each cloud server currently cached. When the preset number is the number of available host instances respectively corresponding to each cloud server currently cached, the preset number corresponding to each cloud server may be the same or different, and the preset number may be set as required, which is not specifically limited in the embodiments of the present disclosure. For example, the predetermined number may be 10, 12, 15, or the like.
In the implementation manner, the second server periodically detects the number of the currently cached available host instances, and sends the host instance obtaining request to the cloud server according to the number of the currently cached available host instances, so that the second server can send the host instance obtaining request to the cloud server in time, the number of the host instances in the second server is ensured to be sufficient, and meanwhile, the problem that the host instances generated by the cloud server cannot be used in time due to the fact that the number of the available host instances stored in the second server is too large is avoided, and the host instances are wasted.
In addition, the host instance acquisition request may also carry the target number of the host instance to be acquired. The target number may be set as needed, and in the embodiment of the present disclosure, the target number is not particularly limited. For example, the target number may be 5, 10, 12, or 15, etc.
Step 202: and the cloud server receives a host instance acquisition request sent by the second server.
In this step, the cloud server receives, according to the called interface, a host instance acquisition request sent by the second server.
Step 203: the cloud server generates at least one host instance.
In this step, the cloud server generates the at least one host instance according to the received host instance obtaining request, and obtains an instance identifier of the at least one host instance, where the instance identifier at least includes a server identifier of the cloud server that generates the host instance, and the instance information may also include information such as a host name and a memory.
Step 204: and the cloud server sends the generated instance information of the at least one host instance to the second server.
In this step, the cloud server sends the instance information in the at least one host instance to the second server according to the server identifier of the second server.
Step 205: the second server receives instance information of at least one host instance sent by the cloud server.
The second server may receive instance information of at least one host instance sent by the cloud server according to different data interfaces, respectively.
It should be noted that, in the step 202 and 205, for a plurality of cloud servers for which the second server sends the host instance obtaining request, each cloud server may generate at least one host instance according to the step 202 and 204, and send the at least one host instance to the second server, and accordingly, the second server may receive instance information of the at least one host instance sent by each cloud server through the step 205. Moreover, the second server may receive instance information of at least one host instance sent by the plurality of cloud servers, and the second server may also receive instance information of the host instance sent by the plurality of servers at the same time. In the embodiments of the present disclosure, this is not particularly limited.
Step 206: the second server stores instance information for the at least one host instance.
A cache pool 401 may be provided in the second server, and the second server stores the received instance information of the at least one host instance in the cache pool 401. The second server may be provided with a cache pool 401, and the instance information of at least one host instance returned by the plurality of cloud servers may be stored in the same cache pool 401. The second server may further include a cache pool 401 corresponding to each cloud server, and store the received instance information of at least one host instance returned by different cloud servers in the cache pool 401 corresponding to the cloud server. In the embodiments of the present disclosure, this is not particularly limited.
It should be noted that, after the second server receives the instance information of at least one host instance, the second server configures the received at least one host instance according to the server parameters of the first server; instance information of the at least one host instance for which the configuration is complete is stored. The first server performs initial configuration on the at least one host instance according to the server parameters of the first server, so that the at least one host instance can provide services for the application program corresponding to the first server, and the second server stores the configured instance information of the at least one host instance in the cache pool 401.
In the implementation manner, the second server sends a host instance obtaining request to the plurality of cloud servers, wherein the host instance obtaining request is used for requesting the plurality of cloud servers to generate at least one host instance, and the instance information of the at least one host instance is sent to the second server, and the instance information comprises a server identifier of the cloud server generating the host instance; receiving instance information of at least one host instance sent by a plurality of cloud servers; storing instance information for at least one host instance; when a second resource calling request sent by the first server is received, determining a target server identifier of a target cloud server according to the second resource calling request, wherein the second resource calling request carries the operation type of the resource calling operation and the target server identifier of the target cloud server; selecting a target host instance from the stored at least one host instance according to the target cloud server identification and the instance information of the at least one host instance; according to the target host example, the operation corresponding to the operation type of the resource calling operation is executed, so that the number of the cloud servers of the first server is changed into one, the difference of the cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
Fig. 5 is a flowchart of a resource scheduling method according to an exemplary embodiment, and in the embodiment of the present disclosure, a first server is used to receive a second resource invocation request of a terminal, invoke a second server through the second resource invocation request, and invoke a resource through the second server, thereby performing a corresponding operation. As shown in fig. 5, the method comprises the steps of:
step 501: the first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries the operation type of the resource calling operation and the target server identification of the target cloud server.
The terminal can display a resource calling interface, and the terminal can receive the operation category of the resource calling operation and the target server identification of the target cloud server, which are input by a user, through the resource calling interface. The resource calling interface may be an interface of an application program that needs to call the cloud resource in the terminal, and the resource calling interface may also be an operation interface of a cloud server developed by a server developer of the cloud server.
Continuing to refer to fig. 3 and 4, the terminal receives input information input by the user, where the input information includes an operation category of the resource calling operation and a target server identifier of the target cloud server; detecting whether a confirmation operation for the input information is received at present, when the confirmation operation is received, continuing to execute the step of receiving the input information, when the confirmation operation is received, generating a first resource calling request according to the operation type and the target server identification, and sending the first resource calling request to the first server. Correspondingly, the first server receives a first resource calling request sent by the terminal.
When the first server receives a first resource calling request sent by the terminal, the first resource calling request can be verified.
In one possible implementation, the first server checks security of the first resource invocation request. Correspondingly, the resource calling request also carries a terminal identifier of the terminal, and the first server verifies the security of the application program installed in the terminal according to the terminal identifier, wherein the terminal identifier may be a user account of the application program logged in the terminal, and the like. The security verification may be verification of usage security of the account, for example, sending verification information through a social communication account bound to the user account, and performing security verification on the first resource invocation request by receiving the verification information sent through the user account. The security verification may also be a security verification of a usage specification for the account. For example, the application program may be a game application, and the first server may perform security verification of a usage specification on the user account corresponding to the first resource invocation request, detect whether the game account is normally used, and prevent situations such as cheating.
In another possible implementation manner, the first server checks validity of the first resource invocation request. Accordingly, before this step, the first server receives a plurality of server identifications of a plurality of cloud servers sent by the second server, where the plurality of cloud servers are cloud servers that generate a plurality of host instances stored in the second server. The server identifications of the plurality of cloud servers are the server identifications of the cloud servers of which the second server can call the host instance. Accordingly, the first server may check validity of the first resource invocation request according to the server resources of the plurality of cloud servers. The process of checking the validity of the first resource invocation request may be implemented by the following steps (1) - (4), including:
(1) and the first server determines the target server identification carried by the first resource request.
In this step, the first server obtains, from the first resource invocation request, the target server identifier of the target cloud server carried in the first resource invocation request.
(2) When the target server identifier exists in the plurality of server identifiers, the first server performs step 502.
When the server identifiers of the plurality of cloud servers stored in the first server carry the target server identifier, and it is determined that the second server can provide cloud services for the terminal, step 502 is executed.
(3) When the target server identification does not exist in the plurality of server identifications, the first server generates prompt information.
And when the target server identification does not exist in the plurality of server identifications, determining that the second server cannot provide cloud service for the terminal, and generating prompt information by the first server.
(4) The first server sends the prompt message to the terminal, the terminal is used for receiving the prompt message and displaying the prompt message, and the prompt message is used for prompting a user that the current target server is identified incorrectly.
And the first server sends the generated prompt information to the terminal, the terminal displays the prompt information to prompt the user that the current target server identifier is wrong, receives the target server identifier input by the user again and generates a new first resource calling request.
In the implementation mode, the first server verifies the first resource calling request, and sends the information which does not accord with the verification condition to the first terminal in time, so that the effectiveness of calling the second server by the first server is improved.
Step 502: and the first server generates a second resource calling request according to the target server identification and the operation category.
In this step, the first server generates a second resource calling request according to the verified target server identifier and the operation type, where the second resource calling request carries the operation type of the resource calling operation, the target server identifier of the target cloud server, and the server identifier of the second server.
Step 503: and the first server calls the second server through the second resource calling request, and the second server executes the operation corresponding to the operation type.
With continued reference to fig. 3 and 4, the first server requests to invoke the second server via a second resource invocation request. The second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request, and executing the operation corresponding to the operation type by calling the target host instance.
The first server may request the second server to call the host instance of the target cloud server by sending the second resource call request to the second server, and perform a corresponding operation. The process may be: and the first server sends the second resource calling request to the second server, wherein the second resource calling request is used for requesting the second server to call the host instance in the target cloud server.
In the implementation manner, the first server sends the second resource calling request to the second server, so that the first server can call the host instance of the cloud server by calling the second server, the first server only needs to request the second server to complete resource calling, and does not need to send the resource calling request to the cloud server any more, so that the cloud server of the first server is changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed any more for the first server, the application development time is shortened, and the application development efficiency is improved.
Step 504: when a second resource calling request sent by the first server is received, the second server determines a target server identifier of the target cloud server according to the second resource calling request.
Continuing to refer to fig. 3 and fig. 4, the second resource invocation request carries the operation category of the resource invocation operation and the target server identifier of the target cloud server. When the second server receives a second resource calling request sent by the first server, the second server extracts the target server identification of the target cloud server from the second resource calling request.
Step 505: and the second server selects a target host instance from the stored at least one host instance according to the target cloud server identification and the instance information of the at least one host instance.
In this step, the second server selects a target host instance corresponding to the target server identifier from the stored instance information of at least one host instance according to the target server identifier.
It should be noted that the target host instance may be an unused host instance, and the target host instance may also be an occupied host instance, which is not specifically limited in the embodiment of the present disclosure. The operation category comprises obtaining a host instance, changing a host name, modifying a password, turning on and off the computer and the like. When the operation type of the current resource calling operation carried in the second resource calling request is to acquire the host instance, the target host instance is an unused host instance.
When the operation type of the resource calling operation carried in the second resource calling request is operations of changing a host name, modifying a password, turning on and off the computer and the like, the target host instance is an occupied host instance. Correspondingly, the second resource calling request also carries the host identity of the target host instance. This step can be replaced by: and the second server selects the target host instance from the target cloud server according to the target cloud server identification, the host identification of the target host instance and the instance information of the at least one host instance.
Step 506: and the second server executes the operation corresponding to the operation type of the resource calling operation according to the target host example.
In this step, the second server executes the relevant operation through the target host instance according to the operation type of the resource calling operation. The operation category comprises obtaining a host instance, changing a host name, modifying a password, turning on and turning off the computer, and the like.
With continued reference to fig. 3 and 4, when the operation category is acquiring a host instance, the second server may perform the following operations: the second server sends instance information of the target host instance to the first server. The first server receives instance information of the target host instance sent by the second server. And the first server sends the instance information of the target host instance to the terminal.
It should be noted that, after the second terminal sends the instance information of the target host instance to the first server, the target host instance is marked as an unavailable host instance, or an occupied host instance is deleted from the locally stored instance information of the host instance, so that when the second server detects the number of host instances, the occupied host instance can be removed to obtain an accurate number of available host instances.
Correspondingly, when the operation category is operations of changing the host name, modifying the password, turning on and turning off the computer and the like, and when the second server stores the instance information of the occupied host instance, the second server can locally perform operations of changing the host name or modifying the password; when the second server does not store the instance information of the occupied host instance, the second server can complete operations of changing the host name, modifying the password, turning on and off the computer and the like from the target cloud server through the target server identifier of the target cloud server.
In the embodiment of the disclosure, a first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries an operation category of a current resource calling operation and a target server identifier of a target cloud server; generating a second resource calling request according to the target server identification and the operation category; and calling a second server through a second resource calling request, executing operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing operation corresponding to the operation category through calling the target host instance. Therefore, the cloud servers of the first server are changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
Fig. 6 is a block diagram of a resource scheduling apparatus according to an example embodiment. Referring to fig. 6, the apparatus includes:
a first receiving module 601, configured to receive a first resource calling request sent by a terminal, where the first resource calling request carries an operation category of the resource calling operation and a target server identifier of a target cloud server;
a first generating module 602, configured to generate a second resource invocation request according to the target server identifier and the operation category;
the invoking module 603 is configured to invoke a second server according to a second resource invoking request, execute an operation corresponding to an operation category by the second server, store instance information of multiple host instances in the second server, where the multiple instance information includes a server identifier of a cloud server that generates the host instances, and invoke a target host instance corresponding to the target server identifier according to the second resource invoking request, and execute the operation corresponding to the operation category by invoking the target host instance.
In one possible implementation, the apparatus further includes:
the second receiving module is used for receiving a plurality of server identifications of a plurality of cloud servers sent by a second server, wherein the plurality of cloud servers are cloud servers for generating a plurality of host instances stored in the second server;
the first determining module is used for determining a target server identifier carried by the first resource request;
the invoking module 603 is further configured to, when a target server identifier exists in the plurality of server identifiers, generate a second resource invoking request according to the target server identifier and the operation category;
a second generating module 602, configured to generate a prompt message when a target server identifier does not exist in the multiple server identifiers; and sending the prompt information to a terminal, wherein the terminal is used for receiving the prompt information and displaying the prompt information, and the prompt information is used for prompting the user that the current target server is identified wrongly.
In another possible implementation manner, when the operation type is to acquire a host instance, the invoking module 603 is further configured to send a second resource invoking request to the second server, where the second resource invoking request is used to request the second server to invoke the host instance in the target cloud server, and the second server is configured to determine, according to the second resource invoking request, a target host instance corresponding to the target server identifier from the cached multiple host instance information, and send instance information of the target host instance to the first server; receiving instance information of a target host instance sent by a second server; and sending the instance information to the terminal.
In the embodiment of the disclosure, a first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries an operation category of a current resource calling operation and a target server identifier of a target cloud server; generating a second resource calling request according to the target server identification and the operation category; and calling a second server through a second resource calling request, executing operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing operation corresponding to the operation category through calling the target host instance. Therefore, the cloud servers of the first server are changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
Fig. 7 is a block diagram of a resource scheduling apparatus according to an example embodiment. Referring to fig. 7, the apparatus includes:
a sending module 701, configured to send a host instance obtaining request to a plurality of cloud servers, where the host instance obtaining request is used to request the plurality of cloud servers to generate at least one host instance, and send instance information of the at least one host instance to a second server, where the instance information includes a server identifier of a cloud server that generates the host instance;
a third receiving module 702, configured to receive instance information of at least one host instance sent by multiple cloud servers;
a storage module 703, configured to store instance information of at least one host instance;
a second determining module 704, configured to determine, when a second resource calling request sent by the first server is received, a target server identifier of the target cloud server according to the second resource calling request, where the second resource calling request carries an operation category of the resource calling operation and the target server identifier of the target cloud server;
a selecting module 705, configured to select a target host instance from the stored at least one host instance according to the target cloud server identifier and the instance information of the at least one host instance;
and an operation executing module 706, configured to execute, according to the target host instance, an operation corresponding to the operation type of the resource invoking operation.
In another possible implementation, when the operation type is to acquire a host instance;
the operation executing module 706 is further configured to send the instance information of the target host instance to the first server, where the first server is configured to receive the instance information of the target host instance and send the instance information of the target host instance to the terminal.
In another possible implementation manner, the apparatus further includes:
the detection module is used for periodically detecting the number of the stored host instances corresponding to the plurality of cloud servers;
the sending module 701 is further configured to send a host instance obtaining request to the multiple cloud servers when the number of host instances is smaller than the preset number.
In another possible implementation manner, the storage module 703 is further configured to configure the received at least one host instance according to a server parameter of the first server; instance information of the at least one host instance for which the configuration is complete is stored.
In the embodiment of the disclosure, a first server receives a first resource calling request sent by a terminal, wherein the first resource calling request carries an operation category of a current resource calling operation and a target server identifier of a target cloud server; generating a second resource calling request according to the target server identification and the operation category; and calling a second server through a second resource calling request, executing operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing operation corresponding to the operation category through calling the target host instance. Therefore, the cloud servers of the first server are changed into one from multiple cloud servers, the difference of the multiple cloud servers to the first server is eliminated, when the first server is developed, only the application program of the first server can be developed, the cloud server is not developed for the first server, the application development time is shortened, and the application development efficiency is improved.
It should be noted that: in the resource scheduling apparatus provided in the foregoing embodiment, only the division of the functional modules is illustrated in resource scheduling, and in practical applications, the function allocation may be completed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to complete all or part of the functions described above. In addition, the resource scheduling apparatus and the resource scheduling method provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Fig. 8 is a schematic structural diagram of a server provided in an embodiment of the present disclosure, where the server 800 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 801 and one or more memories 802, where the memory 802 stores at least one instruction, and the at least one instruction is loaded and executed by the processors 801 to implement the methods provided by the foregoing method embodiments. Of course, the server 800 may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the server 800 may also include other components for implementing the functions of the device, which are not described herein again. The server 800 may be a first server or a second server.
In an exemplary embodiment, a computer-readable storage medium is further provided, in which at least one instruction is stored, and the at least one instruction is loaded and executed by a server to implement the resource scheduling method in the foregoing embodiments. The computer readable storage medium may be a memory. For example, the computer-readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is meant as an alternative embodiment of the disclosure and not as a limitation of the disclosure, and any modification, equivalent replacement, or improvement made within the spirit and principle of the disclosure should be included in the scope of protection of the disclosure.

Claims (10)

1. A method for scheduling resources, the method comprising:
receiving a first resource calling request sent by a terminal, wherein the first resource calling request carries the operation category of the resource calling operation and a target server identifier of a target cloud server;
generating a second resource calling request according to the target server identification and the operation category;
and calling a second server through the second resource calling request, executing the operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing the operation corresponding to the operation category through calling the target host instance.
2. The method according to claim 1, wherein before the receiving the first resource invocation request sent by the terminal, the method further comprises:
receiving a plurality of server identifications of a plurality of cloud servers sent by the second server, wherein the plurality of cloud servers are cloud servers for generating a plurality of host instances stored in the second server;
after receiving the first resource calling request sent by the terminal, the method further includes:
determining a target server identifier carried by the first resource request;
when the target server identifier exists in the plurality of server identifiers, executing the step of generating a second resource calling request according to the target server identifier and the operation category;
when the target server identification does not exist in the plurality of server identifications, generating prompt information; and sending the prompt information to the terminal, wherein the terminal is used for receiving the prompt information and displaying the prompt information, and the prompt information is used for prompting a user that the identification of the current target server is wrong.
3. The method of claim 1, wherein when the operation type is get host instance, the invoking a second server through the second resource invocation request comprises:
sending the second resource calling request to the second server, where the second resource calling request is used to request the second server to call a host instance in a target cloud server, and the second server is used to determine, according to the second resource calling request, a target host instance corresponding to a target server identifier from cached multiple host instance information, and send instance information of the target host instance to the first server;
receiving instance information of a target host instance sent by the second server;
and sending the instance information to the terminal.
4. A method for resource invocation, the method comprising:
sending a host instance obtaining request to a plurality of cloud servers, wherein the host instance obtaining request is used for requesting the plurality of cloud servers to generate at least one host instance, and sending instance information of the at least one host instance to a second server, wherein the instance information comprises a server identifier of the cloud server generating the host instance;
receiving instance information of at least one host instance sent by a plurality of cloud servers;
storing instance information for at least one of said host instances;
when a second resource calling request sent by a first server is received, determining a target server identifier of a target cloud server according to the second resource calling request, wherein the second resource calling request carries the operation category of the resource calling operation and the target server identifier of the target cloud server;
selecting a target host instance from at least one stored host instance according to the target cloud server identification and the instance information of the at least one host instance;
and executing the operation corresponding to the operation type of the resource calling operation according to the target host example.
5. The method of claim 4, wherein when the operation type is get host instance;
the executing the operation corresponding to the operation type of the resource calling operation according to the target host example comprises:
and sending the instance information of the target host instance to the first server, wherein the first server is used for receiving the instance information of the target host instance and sending the instance information of the target host instance to a terminal.
6. The method of claim 4, further comprising:
periodically detecting the number of host instances corresponding to the plurality of stored cloud servers;
and when the number of the host instances is smaller than the preset number, executing a step of sending host instance acquisition requests to a plurality of cloud servers.
7. The method of claim 4, wherein said storing instance information for at least one of said host instances comprises:
configuring the received at least one host instance according to the server parameters of the first server;
storing instance information of at least one of the host instances for which configuration is complete.
8. An apparatus for scheduling resources, the apparatus comprising:
the first receiving module is used for receiving a first resource calling request sent by a terminal, wherein the first resource calling request carries the operation category of the resource calling operation and the target server identification of a target cloud server;
the first generation module is used for generating a second resource calling request according to the target server identification and the operation type;
the calling module is used for calling a second server through the second resource calling request, executing the operation corresponding to the operation category through the second server, storing instance information of a plurality of host instances in the second server, wherein the plurality of instance information comprises a server identifier of a cloud server generating the host instances, and the second server is used for calling a target host instance corresponding to the target server identifier according to the second resource calling request and executing the operation corresponding to the operation category through calling the target host instance.
9. An apparatus for resource invocation, the apparatus comprising:
a sending module, configured to send a host instance obtaining request to a plurality of cloud servers, where the host instance obtaining request is used to request the plurality of cloud servers to generate at least one host instance, and send instance information of the at least one host instance to a second server, where the instance information includes a server identifier of a cloud server that generates the host instance;
a third receiving module, configured to receive instance information of at least one host instance sent by multiple cloud servers;
the storage module is used for storing the instance information of at least one host instance;
the second determining module is used for determining a target server identifier of a target cloud server according to a second resource calling request when the second resource calling request sent by the first server is received, wherein the second resource calling request carries the operation type of the resource calling operation and the target server identifier of the target cloud server;
the selecting module is used for selecting a target host instance from at least one stored host instance according to the target cloud server identification and the instance information of the at least one host instance;
and the operation execution module is used for executing the operation corresponding to the operation type of the resource calling operation according to the target host example.
10. A server, comprising a processor and a memory, wherein at least one instruction is stored in the memory and loaded and executed by the processor to implement a resource invocation method according to any of claims 1 to 3, or to implement a resource invocation method according to any of claims 4 to 7.
CN201911330558.5A 2019-12-20 2019-12-20 Resource scheduling method and device and server Active CN111131440B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911330558.5A CN111131440B (en) 2019-12-20 2019-12-20 Resource scheduling method and device and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911330558.5A CN111131440B (en) 2019-12-20 2019-12-20 Resource scheduling method and device and server

Publications (2)

Publication Number Publication Date
CN111131440A true CN111131440A (en) 2020-05-08
CN111131440B CN111131440B (en) 2021-09-28

Family

ID=70501105

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911330558.5A Active CN111131440B (en) 2019-12-20 2019-12-20 Resource scheduling method and device and server

Country Status (1)

Country Link
CN (1) CN111131440B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114095200A (en) * 2021-09-28 2022-02-25 阿里巴巴（中国）有限公司 Resource access authority management method and device, electronic equipment and medium
WO2022068748A1 (en) * 2020-09-29 2022-04-07 华为云计算技术有限公司 Method, apparatus and system for scheduling computing instance

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005028A1 (en) * 2001-06-27 2003-01-02 International Business Machines Corporation Method and apparatus for controlling the number of servers in a hierarchical resource environment
CN102130959A (en) * 2011-03-22 2011-07-20 浪潮(北京)电子信息产业有限公司 System and method for scheduling cloud storage resource
KR101284353B1 (en) * 2012-11-16 2013-07-08 박순영 The method of cloud based hosting the push notification relay system supported transferring massive data between one device as host and many device as clients
CN106959820A (en) * 2016-01-11 2017-07-18 杭州海康威视数字技术股份有限公司 A kind of data extraction method and system
CN107426288A (en) * 2017-05-26 2017-12-01 郑州云海信息技术有限公司 A kind of resource-sharing schedule method and apparatus based on storage network
AU2018100381A4 (en) * 2018-03-27 2018-05-10 Chongqing University Of Posts And Telecommunications A physical resource scheduling method in cloud cluster
CN110517032A (en) * 2019-08-29 2019-11-29 北京三快在线科技有限公司 Resource transfers method, system, device, server and storage medium
CN110535961A (en) * 2019-09-03 2019-12-03 中国联合网络通信集团有限公司 Resource acquiring method, device, electronic equipment and storage medium
CN110570282A (en) * 2019-09-10 2019-12-13 腾讯科技（深圳）有限公司 cross-region resource transfer method, device, equipment and storage medium

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005028A1 (en) * 2001-06-27 2003-01-02 International Business Machines Corporation Method and apparatus for controlling the number of servers in a hierarchical resource environment
CN102130959A (en) * 2011-03-22 2011-07-20 浪潮(北京)电子信息产业有限公司 System and method for scheduling cloud storage resource
KR101284353B1 (en) * 2012-11-16 2013-07-08 박순영 The method of cloud based hosting the push notification relay system supported transferring massive data between one device as host and many device as clients
CN106959820A (en) * 2016-01-11 2017-07-18 杭州海康威视数字技术股份有限公司 A kind of data extraction method and system
CN107426288A (en) * 2017-05-26 2017-12-01 郑州云海信息技术有限公司 A kind of resource-sharing schedule method and apparatus based on storage network
AU2018100381A4 (en) * 2018-03-27 2018-05-10 Chongqing University Of Posts And Telecommunications A physical resource scheduling method in cloud cluster
CN110517032A (en) * 2019-08-29 2019-11-29 北京三快在线科技有限公司 Resource transfers method, system, device, server and storage medium
CN110535961A (en) * 2019-09-03 2019-12-03 中国联合网络通信集团有限公司 Resource acquiring method, device, electronic equipment and storage medium
CN110570282A (en) * 2019-09-10 2019-12-13 腾讯科技（深圳）有限公司 cross-region resource transfer method, device, equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
徐琛杰等: "面向微服务系统的运行时部署优化", 《计算机应用与软件》 *
童志伟: "PaaS私有云平台及其负载自适应算法", 《软件导刊》 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022068748A1 (en) * 2020-09-29 2022-04-07 华为云计算技术有限公司 Method, apparatus and system for scheduling computing instance
CN114095200A (en) * 2021-09-28 2022-02-25 阿里巴巴（中国）有限公司 Resource access authority management method and device, electronic equipment and medium
CN114095200B (en) * 2021-09-28 2023-12-01 阿里巴巴（中国）有限公司 Resource access authority management method and device, electronic equipment and medium

Also Published As

Publication number Publication date
CN111131440B (en) 2021-09-28

Similar Documents

Publication Publication Date Title
JP6996005B2 (en) Resource configuration method, equipment, terminals, and storage media
CN108763090B (en) Test environment deployment method, device, computer equipment and storage medium
WO2020108085A1 (en) Resource allocation method and apparatus, terminal, and storage medium
CN110825539B (en) Service processing method and device
US10936371B2 (en) Method for resource allocation and related products
CN111814089B (en) Page rendering method and device, rendering server and storage medium
CN105119966A (en) Official account management method and device
CN110750415B (en) Interface service configuration method, device, medium and computer equipment
CN111131440B (en) Resource scheduling method and device and server
CN114615340B (en) Request processing method and device, computer equipment and storage device
CN112767135B (en) Configuration method and device of rule engine, storage medium and computer equipment
CN110955499A (en) Processor core configuration method, device, terminal and storage medium
CN108989547B (en) Light emission control method, device, terminal and storage medium
JP2006211638A (en) Scenario editing apparatus, dummy base station test simulator for wireless communication, dummy terminal test simulator for wireless communication, scenario editing method, test processing method, computer readable storage medium with program stored thereon, and program
CN114222003A (en) Service calling method, system, device, equipment and storage medium
CN107734050B (en) Load machine distribution method, computing equipment and load machine distribution system
CN108345508B (en) Interface call testing method and device
CN109388420A (en) Application upgrade test method, device, computer equipment and storage medium
CN114328196A (en) Method, device and equipment for testing data leakage prevention system and storage medium
CN113934552A (en) Method and device for determining function code, storage medium and electronic device
CN114610446A (en) Method, device and system for automatically injecting probe
CN114282760A (en) Workflow generation method and device combining dynamic form and dynamic flow
CN107562501A (en) A kind of smart machine management-control method and system
CN113434234A (en) Page jump method, device, computer readable storage medium and processor
CN110727416A (en) Development framework generation method and related device

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