CN113434281A - Equipment scheduling method and cloud platform - Google Patents

Equipment scheduling method and cloud platform Download PDF

Info

Publication number
CN113434281A
CN113434281A CN202110812592.7A CN202110812592A CN113434281A CN 113434281 A CN113434281 A CN 113434281A CN 202110812592 A CN202110812592 A CN 202110812592A CN 113434281 A CN113434281 A CN 113434281A
Authority
CN
China
Prior art keywords
information
cloud platform
equipment
host
interface
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
CN202110812592.7A
Other languages
Chinese (zh)
Other versions
CN113434281B (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.)
Shanghai Hode Information Technology Co Ltd
Original Assignee
Shanghai Hode Information Technology 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 Shanghai Hode Information Technology Co Ltd filed Critical Shanghai Hode Information Technology Co Ltd
Priority to CN202110812592.7A priority Critical patent/CN113434281B/en
Publication of CN113434281A publication Critical patent/CN113434281A/en
Application granted granted Critical
Publication of CN113434281B publication Critical patent/CN113434281B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • 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/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application provides a device scheduling method, which comprises the following steps: the method comprises the steps that a cloud platform receives equipment information of terminal equipment and host information of a host; the cloud platform tags the terminal equipment to obtain tag information; and acquiring the equipment information and the host information from the cloud platform according to the label information so as to realize the scheduling of the terminal equipment. The application also provides a cloud platform. According to the equipment scheduling method and the cloud platform, the terminal equipment can be scheduled without physical isolation, so that the maintenance cost is low, and the equipment scheduling method and the cloud platform are flexible enough.

Description

Equipment scheduling method and cloud platform
Technical Field
The present application relates to the field of computer technologies, and in particular, to an apparatus scheduling method, a cloud platform, a computer apparatus, and a computer-readable storage medium.
Background
Most of the current real machine scheduling schemes of the mobile phone machine room are implemented by physically isolating different cabinets to execute different test tasks or all cabinets to execute the same type of tasks.
A plurality of service units (BU) and service lines are generally arranged in a company, different BU and service lines have different requirements on automated testing, and the same requirements on automated equipment have different environmental requirements, so that a large number of genuine machines are subjected to equipment scheduling in a physical isolation manner, and the maintenance cost is high and the maintenance is not flexible enough.
Disclosure of Invention
The application aims to provide an equipment scheduling method, a cloud platform, computer equipment and a computer-readable storage medium, which are used for solving the following technical problems: the equipment scheduling is performed in a physical isolation mode, so that the maintenance cost is high and the flexibility is not high.
One aspect of the embodiments of the present application provides a device scheduling method, where the method includes: the method comprises the steps that a cloud platform receives equipment information of terminal equipment and host information of a host; the cloud platform tags the terminal equipment to obtain tag information; and acquiring the equipment information and the host information from the cloud platform according to the label information so as to realize the scheduling of the terminal equipment.
Optionally, the receiving, by the cloud platform, the device information of the terminal device and the host information of the host includes: the cloud platform deploys equipment management services on the host machine; and the cloud platform receives the equipment information and the host information reported by the equipment management service in real time.
Optionally, the device information includes a device identification number of the terminal device; the host information comprises an IP address of the host; the tag information includes a task type of the terminal device.
Optionally, the tagging, by the cloud platform, of the terminal device to obtain tag information includes: setting the task type for the terminal equipment through a UI of the cloud platform; or setting the task type for the terminal equipment through a maintenance label interface of the cloud platform.
Optionally, the obtaining the device information and the host information from the cloud platform according to the tag information includes: providing a database for storing the device information, the host information and the tag information.
Optionally, the obtaining the device information and the host information from the cloud platform according to the tag information further includes: the cloud platform provides an equipment acquisition interface, and the equipment acquisition interface is used for returning the equipment identification number of the terminal equipment and the IP address of the host machine through the transmitted label information; the cloud platform transmits the label information through the equipment acquisition interface; and the cloud platform inquires the equipment identification number of the terminal equipment and the IP address of the host machine in the database according to the label information and returns the equipment identification number of the terminal equipment and the IP address of the host machine.
Optionally, the device acquisition interface and the maintenance tag interface are both REST APIs, the device acquisition interface is called through a test script, and the maintenance tag interface is called through a front-end page of the cloud platform.
An aspect of an embodiment of the present application further provides a cloud platform, including: the receiving module is used for receiving the equipment information of the terminal equipment and the host information of the host; the tag module is used for tagging the terminal equipment to obtain tag information; and the acquisition module is used for acquiring the equipment information and the host information according to the label information so as to realize the scheduling of the terminal equipment.
An aspect of the embodiments of the present application further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the device scheduling method as described above.
An aspect of the embodiments of the present application further provides a computer-readable storage medium, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the device scheduling method as described above.
In the device scheduling method, the cloud platform, the computer device, and the computer-readable storage medium provided by this embodiment, the cloud platform tags the terminal device to obtain tag information, and obtains the device information and the host information from the cloud platform according to the tag information, so that the terminal device can be scheduled without physical isolation, and therefore, the method and the system are low in maintenance cost and flexible enough.
Drawings
Fig. 1 is a schematic diagram schematically illustrating an application environment of the device scheduling method of the present application;
FIG. 2 is a schematic diagram schematically illustrating an application environment of the device scheduling method of the present application;
fig. 3 schematically shows a flowchart of a device scheduling method according to a first embodiment of the present application;
FIG. 4 is a diagram illustrating sub-steps of step S302 in FIG. 3;
FIG. 5 is a diagram illustrating the substeps of step S304 in FIG. 3;
FIG. 6 is a schematic diagram of the UI of step S502 in FIG. 5;
FIG. 7 is a diagram illustrating sub-steps of step S306 in FIG. 3;
FIG. 8 is a diagram illustrating sub-steps of step S306 in FIG. 3;
fig. 9 schematically shows a block diagram of a cloud platform according to a second embodiment of the present application; and
fig. 10 schematically shows a hardware architecture diagram of a computer device suitable for implementing the device scheduling method according to a third embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the descriptions relating to "first", "second", etc. in the embodiments of the present application are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.
In the description of the present application, it should be understood that the numerical references before the steps do not identify the order of performing the steps, but merely serve to facilitate the description of the present application and to distinguish each step, and therefore should not be construed as limiting the present application.
The following are explanations of terms referred to in the present application:
real machine scheduling: for a cloud test service platform, a real machine scheduling PaaS platform is a set of mobile phone automatic test system constructed on a mobile phone hardware machine room, so that an App can be automatically tested and scheduled on mobile phones of different brands, systems and hardware, users can be helped to know the adaptation condition of the App, the test time is saved, and the test efficiency is improved.
Device SN number: the SN is known as a Serial Number, and the SN Number of a device is a unique identifier of the device, and can be used for specifying the device to execute an automation task.
Devicehub: and mounting a host machine of the equipment.
BU: abbreviation for Business Unit (Business Unit).
HTTP: is an abbreviation of hypertext Transfer Protocol (HTTP), and is a request-response Protocol that can be used for request-response between a client and a server.
GET: an HTTP request method requests data from a specified resource.
POST: an HTTP request mode submits data to be processed to a specified resource.
IP: is an abbreviation of Internet Protocol (Internet Protocol).
API: is an abbreviation of Application Programming Interface (Application Programming Interface).
REST: is an abbreviation for the expression of the layer State transition (reproducible State Transfer).
UI (user interface): is an abbreviation for User Interface (User Interface).
APP: is an abbreviation of Application program (Application).
Most of the current real machine scheduling schemes of the mobile phone machine room are implemented by physically isolating different cabinets to execute different test tasks or all cabinets to execute the same type of tasks.
Generally, companies have a plurality of BUs and service lines, different BUs and service lines have different requirements on automatic testing, the same automatic equipment has different environmental requirements, how to classify and schedule massive genuine machines according to the types of testing tasks is high, and if the deployment and maintenance cost in a physical isolation mode is too high, the following defects are mainly caused:
(1) the test task types which can be supported by each device cannot be dynamically adjusted, and the physical position of the device needs to be adjusted in a machine room each time;
(2) the SN number of the equipment needs to be hard-coded in the test script code for obtaining the equipment, and the maintenance cost is too high.
The purpose of the application is to provide a low maintenance cost and flexible enough equipment scheduling scheme.
Fig. 1 and fig. 2 schematically show application environments of the device scheduling method of the present application.
Referring to fig. 1, a host 10 mounts a plurality of terminal devices 11, and the plurality of terminal devices 11 may include, for example, an Andriod device (e.g., an Andriod handset) and an iOS device (e.g., an iOS handset). Fig. 1 shows, by way of example, 3 hosts 10, 3 Android devices, and 3 iOS devices, which are not intended to limit the present application.
Referring to fig. 1 and fig. 2, the cloud platform 20 deploys the device management service 12 on each host 10, and the device management service 12 reports the device information of the terminal device 11 and the host information of the host 10 to the cloud platform 20 in real time. As an example, the device management service 12 may report the device information of the terminal device 11 and the host information of the host 10 to the cloud platform 20 in real time at regular intervals (e.g., 1 second) through the real-time reporting interface 21. As an example, the real-time reporting interface 21 may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
The device grouping is realized on the cloud platform 20 by tagging each terminal device 11. As an example, the tagging may include two ways, one is to manually set a task type attribute through a UI of the cloud platform 20, and use the set task type as tag information (also referred to as a device tag) of the terminal device 11; the other is to automatically set a task type attribute to the terminal device 11 through the maintenance tag interface 22, and use the set task type as tag information (also referred to as a device tag) of the terminal device 11. As an example, the maintenance tag interface 22 may be called by a front-end page of the cloud platform 20, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
The cloud platform 20 provides a device obtaining interface 23, and returns host information (e.g. devicehub IP, IP address) of the host 10 to which the terminal device 11 belongs and device information (e.g. device SN number) of the terminal device 11 by passing in the label information (e.g. task type) of the terminal device 11. As an example, the device obtaining interface 23 may be called by a test script, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
The test script may call the device obtaining interface 23 to obtain the host information (e.g., devicehub IP, IP address) of the host 10 and the device information (e.g., device SN number) of the terminal device 11, so as to implement remote connection of the terminal device 11, and then execute a specific service logic.
In summary, the present application implements grouping of terminal devices 11 (e.g., mobile phones) by tagging terminal devices 11 (e.g., mobile phones) (e.g., setting task type attributes), and a plurality of tags may be tagged on the same terminal device 11 (e.g., mobile phone), so that remote connection information of terminal devices 11 meeting conditions can be obtained according to tag information (also referred to as device tags) of terminal devices 11 in a test script, that is: and dispatching to the terminal equipment (such as a mobile phone) meeting the condition.
For example, if a certain APP needs to be subjected to a stress test, and a device tag (for example, a task type) of a real machine (for example, a mobile phone) that needs to be selected is "mondy-64", then the test script transmits two parameters, namely, the device tag (for example, the task type) and an operating system type (for example, Android or iOS), through a device obtaining interface 23 (for example, an HTTP interface, which may be specifically a REST API) provided by the cloud platform 20, and the cloud platform 20 returns a device SN number and a devicehub IP that satisfy the device tag (for example, the task type) "mondy-64". Therefore, the APP can be remotely connected with a real machine (such as a mobile phone) meeting the conditions according to the acquired SN number of the device and the devicehub IP to carry out pressure test on the APP.
Various embodiments are provided below, which can be used to implement the device scheduling schemes described above. For ease of understanding, the following description will be exemplarily described with a cloud platform/computer device as the execution subject.
Example one
Fig. 3 schematically shows a flowchart of a device scheduling method according to a first embodiment of the present application.
As shown in fig. 3, a device scheduling method according to a first embodiment of the present application may include steps S302 to S306, where:
in step S302, the cloud platform 20 receives the device information of the terminal device 11 and the host information of the host 10.
As an example, as shown in fig. 4, the step S302 may include steps S402 to S404. Wherein: step S402, deploying a device management service 12 on the host 10; in step S404, the cloud platform 20 receives the device information and the host information reported by the device management service 12 in real time. As an example, the cloud platform 20 deploys the device management service 12 on the host 10, so as to ensure a real-time reporting effect of the device information of the terminal device 11 and the host information of the host 10.
As an example, the device management service 12 may report the device information of the terminal device 11 and the host information of the host 10 to the cloud platform 20 in real time at regular intervals (e.g., 1 second) through the real-time reporting interface 21, and the cloud platform 20 may receive the device information and the host information reported by the device management service 12 in real time at regular intervals (e.g., 1 second) through the real-time reporting interface 21.
As an example, the device information may include a device identification number (e.g., device SN number) of the terminal device 11; the host information may include an IP address of the host 10. The real-time reporting interface 21 may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
For example, the real-time reporting interface 21(HTTP interface) may be as follows:
HTTP interface name: test/mirror/regioStreydevice;
the request mode comprises the following steps: POST;
request parameters: device SN number, brand, model, operating system type, operating system version, device connection state, ROM version, CPU hardware information, CPU architecture information, devicehub IP, devicehub name;
the real-time reporting of the device information can be realized by calling the real-time reporting interface 21(HTTP interface) at regular time to transmit the specified parameters.
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
Referring back to fig. 3, in step S304, the cloud platform 20 tags the terminal device 11 to obtain tag information.
In an exemplary embodiment of the present application, the tag information may include a task type of the terminal device 11. As an example, as shown in fig. 5, the step S304 may include a step S502. Wherein: step S502, setting the task type to the terminal device 11 through the UI of the cloud platform 20; or setting the task type for the terminal device 11 through the maintenance tag interface 22 of the cloud platform 20.
The device grouping effect is realized by labeling each terminal device 11 (for example, setting a task type) on the cloud platform 20. As an example, the tagging may include two ways, one is to manually set the task type attribute through the UI of the cloud platform 20, and use the set task type as the tag information of the terminal device 11; the other is to automatically set a task type attribute to the terminal device 11 through the maintenance tag interface 22, and use the set task type as tag information of the terminal device 11. As an example, the maintenance tag interface 22 may be called by a front-end page of the cloud platform 20, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
By way of example, the maintenance tag interface 22(HTTP interface) example may be as follows:
HTTP interface name: test/mirror/updatetask type;
the request mode comprises the following steps: POST;
request parameters: device SN number, task type;
the task type tag information of the terminal device 11 can be updated according to the device SN number of the terminal device 11 by calling the maintenance tag interface 22(HTTP interface).
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
As an example, fig. 6 schematically shows a schematic view of the UI of step S502 in fig. 5. The task types of the terminal device 11 may include monkey-32, ui, appcrawler, test, monkey-64, monkey, high-perf, midle-perf, and so on. The task types shown in fig. 6 are only examples and are not limiting to the present application, and the task types may be increased or decreased according to specific requirements.
Referring back to fig. 3, in step S306, the device information and the host information are obtained from the cloud platform 20 according to the tag information, so as to implement scheduling of the terminal device 11.
As an example, as shown in fig. 7, the step S306 may include a step S702. Step S702, providing a database for storing the device information, the host information, and the tag information. By providing the database, the efficiency of acquiring the equipment information and the host information according to the label information is improved, and therefore the efficiency of equipment scheduling is improved.
The device information includes, for example, a device identification number (e.g., device SN number) of the terminal device 11; the host information includes an IP address of the host 10; the tag information includes a task type of the terminal device 11.
As an example, table 1 illustrates a schematic diagram of a database. By way of example, the database may include the following fields: brand model, SN number (Device identification number of the terminal Device 11), Device Hub (host name), Device Hub IP (IP address of the host 10), traffic status, Device status, task type (tag information), notes, update date, etc. The "business state" and the "device state" are physical state labels, and the "task type" is a business state label. Table 1 shows the fields of the database by way of example, but the fields of the database may be increased or decreased according to specific needs without limiting the present application.
TABLE 1
Figure BDA0003168974270000101
Figure BDA0003168974270000111
As an example, the "business state" and the "device state" in "table 1" may be maintained by the test script calling the HTTP interface of the cloud platform 20, an example of which may be as follows:
HTTP interface name: http:// demo. test/mirror/updateDevice;
the request mode comprises the following steps: POST;
request parameters: device SN number, device state, service state;
the service state and the connection state of the terminal device 11 can be updated according to the device SN number of the terminal device 11 by calling the HTTP interface.
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
As an example, as shown in fig. 8, the step S306 may further include steps S802-S806. In step S802, the cloud platform 20 provides an equipment obtaining interface 23, where the equipment obtaining interface 23 is used to return the equipment identification number of the terminal equipment 11 and the IP address of the host 10 by transmitting the tag information (for example, task type); step S804, the tag information is transmitted through the device acquisition interface 23; step S806, the cloud platform 20 queries the device identification number of the terminal device 11 and the IP address of the host 10 in the database according to the tag information, and returns the device identification number of the terminal device 11 and the IP address of the host 10.
As an example, the device obtaining interface 23 may be called by a test script, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
By way of example, the device acquisition interface 23(HTTP interface) example may be as follows:
HTTP interface name: test/mirror/getLabDevices;
the request mode comprises the following steps: GET;
request parameters: operating system type, task type;
and returning a result: devicehub IP, device SN number;
by means of the device acquisition interface 23(HTTP interface): and inquiring the devicehub IP and the equipment SN number which meet the conditions according to the type of the operating system and the label information (task type).
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
In the exemplary embodiment of the present application, each terminal device 11 has a record in the database, a field/attribute in the record is called task type, and the effect of tagging is achieved by setting the field, and the tag is mainly task type, such as identification of monkey, perf, and other different testing tasks.
The device information of the terminal device 11, the host information (for example, devicehub IP) of the host 10 and the corresponding task type information are stored in the database, and the device information and the devicehub IP information corresponding to the database are queried according to the tag by means of REST API and returned to the user.
The labels comprise a service state label and a physical state label, wherein the service state label refers to different service test types such as monkey test, performance test, compatibility test and the like, the physical state label refers to the offline and maintenance states of the equipment, the offline label can be set if the equipment is disconnected, and the maintenance label can be automatically set if the terminal equipment is over-high in temperature or over-low in electric quantity.
Example two
Fig. 9 schematically illustrates a block diagram of a cloud platform according to a second embodiment of the present application, which may be partitioned into one or more program modules, stored in a storage medium, and executed by one or more processors to implement the second embodiment of the present application. The program modules referred to in the embodiments of the present application refer to a series of computer program instruction segments that can perform specific functions, and the following description will specifically describe the functions of the program modules in the embodiments.
As shown in fig. 9, the cloud platform 900 may include a receiving module 902, a tagging module 904, and an obtaining module 906.
The receiving module 902 is configured to receive device information of the terminal device 11 and host information of the host 10.
As an example, the receiving module 902 is configured to deploy the device management service 12 on the host 10, and receive the device information and the host information reported by the device management service 12 in real time. By deploying the device management service 12 on the host 10, the real-time reporting effect of the device information of the terminal device 11 and the host information of the host 10 is ensured.
For example, the device management service 12 may report the device information of the terminal device 11 and the host information of the host 10 to the cloud platform 20 in real time at regular intervals (e.g., 1 second) through the real-time reporting interface 21, and the receiving module 902 may receive the device information and the host information reported by the device management service 12 in real time at regular intervals (e.g., 1 second) through the real-time reporting interface 21.
As an example, the device information may include a device identification number (e.g., device SN number) of the terminal device 11; the host information may include an IP address of the host 10. The real-time reporting interface 21 may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
For example, the real-time reporting interface 21(HTTP interface) may be as follows:
HTTP interface name: test/mirror/regioStreydevice;
the request mode comprises the following steps: POST;
request parameters: device SN number, brand, model, operating system type, operating system version, device connection state, ROM version, CPU hardware information, CPU architecture information, devicehub IP, devicehub name;
the real-time reporting of the device information can be realized by calling the real-time reporting interface 21(HTTP interface) at regular time to transmit the specified parameters.
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
The label module 904 is configured to label the terminal device 11 to obtain label information.
As an example, the tag information may include a task type of the terminal device 11. The tag module 904 is configured to set the task type to the terminal device 11 through the UI; or set the task type to the terminal device 11 through the maintenance tag interface 22.
The device grouping effect is realized by labeling each terminal device 11 (for example, setting a task type) on the cloud platform 20. As an example, the tagging may include two ways, one is to manually set a task type attribute through the UI, and use the set task type as the tag information of the terminal device 11; the other is to automatically set a task type attribute to the terminal device 11 through the maintenance tag interface 22, and use the set task type as tag information of the terminal device 11.
As an example, the maintenance tag interface 22 may be called through a front page of the cloud platform 20, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, but may also be an interface in another form.
By way of example, the maintenance tag interface 22(HTTP interface) example may be as follows:
HTTP interface name: test/mirror/updatetask type;
the request mode comprises the following steps: POST;
request parameters: device SN number, task type;
the task type tag information of the terminal device 11 can be updated according to the device SN number of the terminal device 11 by calling the maintenance tag interface 22(HTTP interface).
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
An obtaining module 906, configured to obtain the device information and the host information according to the tag information, so as to implement scheduling of the terminal device 11.
As an example, the obtaining module 906 provides a database for storing the device information, the host information, and the tag information. By providing the database, the efficiency of acquiring the equipment information and the host information is improved, so that the efficiency of equipment scheduling is improved.
The device information includes, for example, a device identification number (e.g., device SN number) of the terminal device 11; the host information includes an IP address of the host 10; the tag information includes a task type of the terminal device 11.
The obtaining module 906 provides a device obtaining interface 23, and the device obtaining interface 23 is configured to return the device identification number of the terminal device 11 and the IP address of the host 10 by passing the tag information (such as task type) in. The obtaining module 906 sends the tag information through the device obtaining interface 23, queries the device identification number of the terminal device 11 and the IP address of the host 10 in the database according to the tag information, and returns the device identification number of the terminal device 11 and the IP address of the host 10.
As an example, the device obtaining interface 23 may be called by a test script, and may be an HTTP interface, and optionally, the HTTP interface may be a REST API, which is friendly, and may also be an interface in another form.
By way of example, the device acquisition interface 23(HTTP interface) example may be as follows:
HTTP interface name: test/mirror/getLabDevices;
the request mode comprises the following steps: GET;
request parameters: operating system type, task type;
and returning a result: devicehub IP, device SN number;
by means of the device acquisition interface 23(HTTP interface): and inquiring the devicehub IP and the equipment SN number which meet the conditions according to the type of the operating system and the label information (task type).
It should be noted that the above HTTP interface example is only an example and is not meant to limit the present application.
EXAMPLE III
Fig. 10 schematically shows a hardware architecture diagram of a computer device 1000 adapted to the device scheduling method according to a third embodiment of the present application. In an exemplary embodiment of the present application, the computer device 1000 may be a device capable of automatically performing numerical calculation and/or information processing according to instructions set or stored in advance. For example, the server may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers), a gateway, and the like. As shown in fig. 10, the computer device 1000 includes at least, but is not limited to: the memory 1010, processor 1020, and network interface 1030 may be communicatively linked to each other via a system bus. Wherein:
the memory 1010 includes at least one type of computer-readable storage medium including flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 1010 may be an internal storage module of the computer device 1000, such as a hard disk or a memory of the computer device 1000. In other embodiments, the memory 1010 may be an external storage device of the computer device 1000, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 1000. Of course, the memory 1010 may also include both internal and external memory modules of the computer device 1000. In this embodiment, the memory 1010 is generally used for storing an operating system and various application software installed in the computer device 1000, such as program codes of the device scheduling method. In addition, the memory 1010 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 1020 may be, in some embodiments, a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data Processing chip. The processor 1020 is generally configured to control the overall operation of the computer device 1000, such as performing control and processing related to data interaction or communication with the computer device 1000. In this embodiment, the processor 1020 is configured to execute program codes stored in the memory 1010 or process data.
The network interface 1030 may comprise a wireless network interface or a wired network interface, with the network interface 1030 typically being used to establish communications links between the computer device 1000 and other computer devices. For example, the network interface 1030 is used to connect the computer apparatus 1000 to an external terminal via a network, establish a data transmission channel and a communication link between the computer apparatus 1000 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), or Wi-Fi.
It should be noted that FIG. 10 only shows a computer device having components 1010 and 1030, but it should be understood that not all of the shown components are required and that more or fewer components may be implemented instead.
In this embodiment, the device scheduling method stored in the memory 1010 may be further divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 1020) to implement the embodiment of the present application.
Example four
Embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the device scheduling method in the embodiments.
In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the computer readable storage medium may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the computer device. Of course, the computer-readable storage medium may also include both internal and external storage devices of the computer device. In this embodiment, the computer-readable storage medium is generally used for storing an operating system and various types of application software installed in the computer device, for example, the program code of the device scheduling method in the embodiment, and the like. Further, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are to be output.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims (10)

1. A method for scheduling devices, the method comprising:
the method comprises the steps that a cloud platform receives equipment information of terminal equipment and host information of a host;
the cloud platform tags the terminal equipment to obtain tag information;
and acquiring the equipment information and the host information from the cloud platform according to the label information so as to realize the scheduling of the terminal equipment.
2. The device scheduling method according to claim 1, wherein the receiving, by the cloud platform, the device information of the terminal device and the host information of the host comprises:
the cloud platform deploys equipment management services on the host machine;
and the cloud platform receives the equipment information and the host information reported by the equipment management service in real time.
3. The device scheduling method of claim 1, wherein the device information includes a device identification number of the terminal device; the host information comprises an IP address of the host; the tag information includes a task type of the terminal device.
4. The device scheduling method according to claim 3, wherein the tagging of the terminal device by the cloud platform to obtain tag information comprises:
setting the task type for the terminal equipment through a UI of the cloud platform; or
And setting the task type for the terminal equipment through a maintenance label interface of the cloud platform.
5. The device scheduling method according to claim 3, wherein the obtaining the device information and the host information from the cloud platform according to the tag information includes:
providing a database for storing the device information, the host information and the tag information.
6. The device scheduling method according to any one of claims 1 to 5, wherein the obtaining the device information and the host information from the cloud platform according to the tag information further includes:
the cloud platform provides an equipment acquisition interface, and the equipment acquisition interface is used for returning the equipment identification number of the terminal equipment and the IP address of the host machine through the transmitted label information;
the cloud platform transmits the label information through the equipment acquisition interface;
and the cloud platform inquires the equipment identification number of the terminal equipment and the IP address of the host machine in the database according to the label information and returns the equipment identification number of the terminal equipment and the IP address of the host machine.
7. The device scheduling method of claim 6, wherein: the equipment acquisition interface and the maintenance label interface are both REST APIs, the equipment acquisition interface is called through a test script, and the maintenance label interface is called through a front-end page of the cloud platform.
8. A cloud platform, comprising:
the receiving module is used for receiving the equipment information of the terminal equipment and the host information of the host;
the tag module is used for tagging the terminal equipment to obtain tag information;
and the acquisition module is used for acquiring the equipment information and the host information according to the label information so as to realize the scheduling of the terminal equipment.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor, when executing the computer program, is adapted to carry out the steps of the device scheduling method according to any of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a computer program which is executable by at least one processor to cause the at least one processor to perform the steps of the device scheduling method according to any one of claims 1 to 7.
CN202110812592.7A 2021-07-19 2021-07-19 Equipment scheduling method and cloud platform Active CN113434281B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110812592.7A CN113434281B (en) 2021-07-19 2021-07-19 Equipment scheduling method and cloud platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110812592.7A CN113434281B (en) 2021-07-19 2021-07-19 Equipment scheduling method and cloud platform

Publications (2)

Publication Number Publication Date
CN113434281A true CN113434281A (en) 2021-09-24
CN113434281B CN113434281B (en) 2024-05-28

Family

ID=77760922

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110812592.7A Active CN113434281B (en) 2021-07-19 2021-07-19 Equipment scheduling method and cloud platform

Country Status (1)

Country Link
CN (1) CN113434281B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113794781A (en) * 2021-11-16 2021-12-14 佛山技研智联科技有限公司 Data acquisition method, device, equipment and storage medium
WO2024130729A1 (en) * 2022-12-23 2024-06-27 Oppo广东移动通信有限公司 Information transmission method, client device, and cloud platform

Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040107415A1 (en) * 2002-12-03 2004-06-03 Konstantin Melamed Web-interactive software testing management method and computer system including an integrated test case authoring tool
CN103825964A (en) * 2014-03-19 2014-05-28 北京邮电大学 SLS (Service Level Specification) scheduling device and SLS scheduling method based on cloud computing PaaS (platform-as-a-service) platform
CN104333488A (en) * 2014-11-04 2015-02-04 哈尔滨工业大学 Cloud service platform performance test method
US20150100684A1 (en) * 2012-06-08 2015-04-09 Stephane Maes Test and management for cloud applications
CN106126347A (en) * 2016-08-17 2016-11-16 浪潮电子信息产业股份有限公司 Method for effectively realizing host cluster resource scheduling under cloud platform
CN106850330A (en) * 2016-12-09 2017-06-13 中电科华云信息技术有限公司 Intelligentized cloud desktop Performance Test System and method
JP2017117309A (en) * 2015-12-25 2017-06-29 ムーバクラウド株式会社 Smartphone application test automatization system
CN106933729A (en) * 2015-12-29 2017-07-07 苏宁云商集团股份有限公司 A kind of method of testing and system based on cloud platform
US10042618B1 (en) * 2017-05-05 2018-08-07 Servicenow, Inc. Integration application creator design
CN108616417A (en) * 2018-03-27 2018-10-02 广州掌动智能科技有限公司 Cloud test platform and its control method
US20180314565A1 (en) * 2017-04-28 2018-11-01 Beijing Didi Infinity Technology And Development C O., Ltd. System and method for task scheduling and device management
CN108733553A (en) * 2017-04-18 2018-11-02 北京嘀嘀无限科技发展有限公司 Configuration method, the device and system of test device based on docker
US20190116110A1 (en) * 2017-10-13 2019-04-18 Keysight Technologies, Inc. Location Based Test Agent Deployment In Virtual Processing Environments
CN110708210A (en) * 2019-08-30 2020-01-17 深圳壹账通智能科技有限公司 Cloud test configuration method and device, computer equipment and storage medium
CN110716778A (en) * 2019-09-10 2020-01-21 阿里巴巴集团控股有限公司 Application compatibility testing method, device and system
CN111464405A (en) * 2020-04-02 2020-07-28 宁波智轩物联网科技有限公司 Cloud controller
CN111488217A (en) * 2019-01-29 2020-08-04 阿里巴巴集团控股有限公司 Cloud server deployment method and management equipment
US20200278920A1 (en) * 2017-10-30 2020-09-03 Hitachi Vantara Corporation Generating Testing Infrastructure on a Cloud for Testing Software Applications
CN111913886A (en) * 2020-08-07 2020-11-10 平安科技（深圳）有限公司 Mobile phone APP automatic test method, device, equipment and storage medium
CN111930626A (en) * 2020-08-12 2020-11-13 中国工商银行股份有限公司 Automatic testing method and device based on PaaS cloud service
CN112162927A (en) * 2020-10-13 2021-01-01 网易（杭州）网络有限公司 Test method, medium and device of cloud computing platform and computing equipment
CN112905337A (en) * 2021-02-07 2021-06-04 中国工商银行股份有限公司 Software and hardware hybrid deployment MySQL cluster scheduling method and device
KR20210067415A (en) * 2019-11-29 2021-06-08 주식회사 데브스택 Platform providing system based on cloud computing and platform provision method using the same

Patent Citations (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040107415A1 (en) * 2002-12-03 2004-06-03 Konstantin Melamed Web-interactive software testing management method and computer system including an integrated test case authoring tool
US20150100684A1 (en) * 2012-06-08 2015-04-09 Stephane Maes Test and management for cloud applications
CN103825964A (en) * 2014-03-19 2014-05-28 北京邮电大学 SLS (Service Level Specification) scheduling device and SLS scheduling method based on cloud computing PaaS (platform-as-a-service) platform
CN104333488A (en) * 2014-11-04 2015-02-04 哈尔滨工业大学 Cloud service platform performance test method
JP2017117309A (en) * 2015-12-25 2017-06-29 ムーバクラウド株式会社 Smartphone application test automatization system
CN106933729A (en) * 2015-12-29 2017-07-07 苏宁云商集团股份有限公司 A kind of method of testing and system based on cloud platform
CN106126347A (en) * 2016-08-17 2016-11-16 浪潮电子信息产业股份有限公司 Method for effectively realizing host cluster resource scheduling under cloud platform
CN106850330A (en) * 2016-12-09 2017-06-13 中电科华云信息技术有限公司 Intelligentized cloud desktop Performance Test System and method
CN108733553A (en) * 2017-04-18 2018-11-02 北京嘀嘀无限科技发展有限公司 Configuration method, the device and system of test device based on docker
US20180314565A1 (en) * 2017-04-28 2018-11-01 Beijing Didi Infinity Technology And Development C O., Ltd. System and method for task scheduling and device management
US20190042206A1 (en) * 2017-05-05 2019-02-07 Servicenow, Inc. Integration application creator design
US10042618B1 (en) * 2017-05-05 2018-08-07 Servicenow, Inc. Integration application creator design
US20190116110A1 (en) * 2017-10-13 2019-04-18 Keysight Technologies, Inc. Location Based Test Agent Deployment In Virtual Processing Environments
US20200278920A1 (en) * 2017-10-30 2020-09-03 Hitachi Vantara Corporation Generating Testing Infrastructure on a Cloud for Testing Software Applications
CN108616417A (en) * 2018-03-27 2018-10-02 广州掌动智能科技有限公司 Cloud test platform and its control method
CN111488217A (en) * 2019-01-29 2020-08-04 阿里巴巴集团控股有限公司 Cloud server deployment method and management equipment
CN110708210A (en) * 2019-08-30 2020-01-17 深圳壹账通智能科技有限公司 Cloud test configuration method and device, computer equipment and storage medium
CN110716778A (en) * 2019-09-10 2020-01-21 阿里巴巴集团控股有限公司 Application compatibility testing method, device and system
KR20210067415A (en) * 2019-11-29 2021-06-08 주식회사 데브스택 Platform providing system based on cloud computing and platform provision method using the same
CN111464405A (en) * 2020-04-02 2020-07-28 宁波智轩物联网科技有限公司 Cloud controller
CN111913886A (en) * 2020-08-07 2020-11-10 平安科技（深圳）有限公司 Mobile phone APP automatic test method, device, equipment and storage medium
CN111930626A (en) * 2020-08-12 2020-11-13 中国工商银行股份有限公司 Automatic testing method and device based on PaaS cloud service
CN112162927A (en) * 2020-10-13 2021-01-01 网易（杭州）网络有限公司 Test method, medium and device of cloud computing platform and computing equipment
CN112905337A (en) * 2021-02-07 2021-06-04 中国工商银行股份有限公司 Software and hardware hybrid deployment MySQL cluster scheduling method and device

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
JUNZAN ZHOU; BO ZHOU; SHANPING LI: ""Automated Model-Based Performance Testing for PaaS Cloud Services"", 《2014 IEEE 38TH INTERNATIONAL COMPUTER SOFTWARE AND APPLICATIONS CONFERENCE WORKSHOPS》, 22 December 2014 (2014-12-22) *
KEES BLOKLAND，MARTIN POL，JEROEN MENGERINK: ""Testing Cloud Services. How to test Saas, Paas and Iaas"", 《EUROSTAR SOFTWARE TESTING COMMUNITY》, 10 September 2019 (2019-09-10) *
严丽云; 何震苇; 杨新章; 张凌; 侯韶新: ""基于Kubernetes的容器化数据库及其集群方案"", 《电信科学》, 20 December 2018 (2018-12-20) *
虞泽凡;: "基于云计算技术的软件测试探索", 自动化技术与应用, no. 12 *
马永;王萍;管建超: ""基于Docker的应用资源池技术研究"", 《电力信息与通信技术》, 15 August 2018 (2018-08-15) *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113794781A (en) * 2021-11-16 2021-12-14 佛山技研智联科技有限公司 Data acquisition method, device, equipment and storage medium
WO2024130729A1 (en) * 2022-12-23 2024-06-27 Oppo广东移动通信有限公司 Information transmission method, client device, and cloud platform

Also Published As

Publication number Publication date
CN113434281B (en) 2024-05-28

Similar Documents

Publication Publication Date Title
CN108874558B (en) Message subscription method of distributed transaction, electronic device and readable storage medium
CN113434281B (en) Equipment scheduling method and cloud platform
CN109361525B (en) Method, device, control terminal and medium for restarting distributed deployment of multiple services
CN111651494B (en) Data processing method, device, equipment and computer readable storage medium
CN108681504A (en) Automated testing method, test server and computer readable storage medium
CN110895472A (en) Method and device for identifying service change
CN111666145A (en) Message processing method and system of message queue and computer equipment
CN107729213A (en) A kind of background task monitoring method and device
CN112422450B (en) Computer equipment, and flow control method and device for service request
CN112395187A (en) Test method, test system, computer device and storage medium
CN112804099A (en) Parameter batch configuration method and device, computer equipment and readable storage medium
CN104219280A (en) Intelligent application data transmission channel
CN109766235A (en) Configuration file detection method, system, equipment and medium based on software supervision
CN114675940A (en) Application instance construction method, device and equipment
CN114237634A (en) Application release risk identification method, device, equipment, medium and program product
CN113704355A (en) Data synchronization method, electronic device and storage medium
CN114416560A (en) Program crash analysis aggregation method and system
CN112667513A (en) Test method, test device, test equipment and storage medium
CN109254782A (en) Installation method of operating system and device
CN110602655B (en) Short message-based equipment communication address modification method and device and readable storage medium
CN102356599B (en) Register method of CIM distribution program in CIM system and CIMOM
CN113407445B (en) End-to-end automatic testing method and device and electronic equipment
CN115334006B (en) Gray level verification method and system based on client implementation
CN110221869B (en) Method and device for configuring data center operating environment
CN108037981B (en) Accessory management method and 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