CN113434281B - Equipment scheduling method and cloud platform - Google Patents
Equipment scheduling method and cloud platform Download PDFInfo
- Publication number
- CN113434281B CN113434281B CN202110812592.7A CN202110812592A CN113434281B CN 113434281 B CN113434281 B CN 113434281B CN 202110812592 A CN202110812592 A CN 202110812592A CN 113434281 B CN113434281 B CN 113434281B
- Authority
- CN
- China
- Prior art keywords
- information
- equipment
- cloud platform
- host
- tag
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000012423 maintenance Methods 0.000 claims abstract description 27
- 238000012360 testing method Methods 0.000 claims description 39
- 239000008186 active pharmaceutical agent Substances 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 13
- 238000002372 labelling Methods 0.000 claims description 7
- 238000002955 isolation Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 13
- 230000000694 effects Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 241000282693 Cercopithecidae Species 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000003247 decreasing effect Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
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 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 tag information so as to realize the scheduling of the terminal equipment. The application further provides a cloud platform. According to the equipment scheduling method and the cloud platform, the scheduling of the terminal equipment can be realized without physical isolation, so that the maintenance cost is low, and the cloud platform is flexible enough.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a device scheduling method, a cloud platform, a computer device, and a computer readable storage medium.
Background
The current real machine scheduling scheme of the mobile phone room is mainly that different cabinets execute different testing tasks or all cabinets execute the same type of tasks through physical isolation.
The company generally has a plurality of Business Units (BU) and Business lines, the requirements of different BU and Business lines on automatic test are different, and the same has different environmental requirements on automatic equipment, so that a large number of true machines are subjected to equipment scheduling in a physical isolation mode, and the maintenance cost is high and the automation equipment is not flexible enough.
Disclosure of Invention
The application aims to provide a device 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 carried out in a physical isolation mode, so that the maintenance cost is high and the equipment scheduling is not flexible.
An aspect of an embodiment of the present application provides a device scheduling method, including: the 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 tag information so as to realize the scheduling of the terminal equipment.
Optionally, the cloud platform receives device information of the terminal device and host information of the host, including: the cloud platform deploys equipment management services on the host; 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 labeling the terminal device by the cloud platform to obtain label information includes: setting the task type for the terminal equipment through the UI of the cloud platform; or setting the task type for the terminal equipment through a maintenance tag interface of the cloud platform.
Optionally, the acquiring the device information and the host information from the cloud platform according to the tag information includes: and providing a database for storing the equipment information, the host information and the tag information.
Optionally, the acquiring 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 an equipment identification number of the terminal equipment and an IP address of the host through the tag information; the cloud platform acquires the tag information transmitted into the interface through the equipment; and the cloud platform queries 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 REST APIs, the device acquisition interface is called through a test script, and the maintenance tag interface is called through a front 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 label module is used for labeling the terminal equipment to obtain label information; and the acquisition module is used for acquiring the equipment information and the host information according to the tag information so as to realize the scheduling of the terminal equipment.
An aspect of an embodiment 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, the processor implementing the steps of the device scheduling method as described above when executing the computer program.
An aspect of an embodiment of the present application further provides a computer readable storage medium comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the device scheduling method as described above when executing the computer program.
According to the equipment scheduling method, the cloud platform, the computer equipment and the computer readable storage medium, the cloud platform is used for labeling the terminal equipment to obtain the label information, the equipment information and the host information are acquired from the cloud platform according to the label information, and the scheduling of the terminal equipment can be achieved without physical isolation, so that the maintenance cost is low, and the terminal equipment is flexible enough.
Drawings
FIG. 1 schematically illustrates a schematic diagram of an application environment of the device scheduling method of the present application;
FIG. 2 schematically illustrates a schematic diagram of an application environment of the device scheduling method of the present application;
fig. 3 schematically shows a flow chart of a device scheduling method according to a first embodiment of the application;
FIG. 4 is a sub-step diagram of step S302 in FIG. 3;
FIG. 5 is a sub-step diagram 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 sub-step diagram of step S306 in FIG. 3;
FIG. 8 is a sub-step diagram 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 illustrates a hardware architecture diagram of a computer device adapted to implement a device scheduling method according to a third embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that the descriptions of "first," "second," etc. in the embodiments of the present application are for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In addition, the technical solutions of the embodiments may be combined with each other, but it is necessary to base that the technical solutions can be realized by those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not within the scope of protection claimed in 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 in which the steps are performed, but are merely used to facilitate description of the present application and to distinguish between each step, and thus should not be construed as limiting the present application.
The following is an explanation of the terminology involved in the present application:
And (5) real machine scheduling: for the cloud testing service platform, the real machine scheduling PaaS platform is a set of mobile phone automatic test system constructed on the mobile phone hardware machine room, so that an App can automatically test and schedule on mobile phones of different brands, systems and hardware, a user is helped to know the adaptation condition of the App, test time is saved, and test efficiency is improved.
Device SN number: the SN is known as the Serial Number, and the SN Number of a device is a unique identifier of the device and can be used to specify the device to perform an automation task.
Devicehub: and a host machine for mounting the equipment.
BU: abbreviation for Business Unit (Business Unit).
HTTP: is an abbreviation of the hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP), a request-response protocol that can be used to make request-responses between a client and a server.
GET: an HTTP request method requests data from a specified resource.
POST: an HTTP request method submits data to be processed to a specified resource.
IP: is an abbreviation for internet protocol (Internet Protocol).
API: is an abbreviation for application program interface (Application Programming Interface).
REST: is an abbreviation for expression of the state transition (Representational STATE TRANSFER).
UI: is an abbreviation for User Interface (User Interface).
APP: is an abbreviation for Application.
The current real machine scheduling scheme of the mobile phone room is mainly that different cabinets execute different testing tasks or all cabinets execute the same type of tasks through physical isolation.
The company generally has a plurality of BU and business lines, the requirements of the different BU and business lines on the automatic test are different, the same has different environmental requirements on the automatic equipment, and the method has the following defects that how to classify and schedule massive true machines according to the test task types if the deployment and maintenance cost in a physical isolation mode is too high:
(1) The test task types which can be supported by each device cannot be dynamically adjusted, and each adjustment needs to be carried out to the machine room to adjust the physical position;
(2) The acquisition device needs to hard code the SN number of the device in the test script code, and the maintenance cost is too high.
It is an object of the present application to provide a device scheduling scheme that is low in maintenance costs and flexible enough.
Fig. 1 and 2 schematically show a schematic view of an application environment 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 an android device (e.g., an android mobile phone) and an iOS device (e.g., an iOS mobile phone), for example. Fig. 1 shows, by way of example, 3 hosts 10, 3 Android devices, 3 iOS devices, and not as a limitation of the present application.
Referring to fig. 1 and fig. 2, the cloud platform 20 deploys a 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 fixed time (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, alternatively, the HTTP interface may be a REST API, which is friendly, but may be any other interface.
Device grouping is achieved by tagging each terminal device 11 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 of the cloud platform 20, and use the set task type as tag information (may also be 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, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
The cloud platform 20 provides a device acquisition 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 through tag information (e.g., task type) of the incoming terminal device 11. As an example, the device acquisition interface 23 may be called by a test script, and may be an HTTP interface, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
The test script can realize remote connection of the terminal device 11 by calling the device to obtain host information (such as devicehub IP, IP address) of the interface 23 to the host 10 and device information (such as device SN number) of the terminal device 11, and then execute specific service logic.
In general, the present application implements grouping of terminal devices 11 (e.g., mobile phones) by labeling the terminal devices 11 (e.g., mobile phones), and the same terminal device 11 (e.g., mobile phones) can label multiple tags, so that remote connection information of the terminal device 11 meeting the conditions can be obtained according to the label information (also called device label) of the terminal device 11 in the test script, that is: and scheduling to the terminal equipment (such as a mobile phone) meeting the condition.
For example, if a certain APP needs to be subjected to a pressure test, a device tag (such as a task type) of a true machine (such as a mobile phone) that needs to be selected is "mondy-64", then the test script transmits two parameters, i.e. a device tag (such as a task type) and an operating system type (such as Android or iOS), to the device tag (such as a task type) "mondy-64" through a device acquisition interface 23 (such as an HTTP interface, specifically, REST API) provided by the cloud platform 20, and the cloud platform 20 returns a device SN number and devicehub IP that satisfy the device tag (such as a task type) "mondy-64". Therefore, a true machine (such as a mobile phone) meeting the conditions can be remotely connected according to the acquired equipment SN number and devicehub IP to perform pressure test on the APP.
Various embodiments are provided below, which may be used to implement the device scheduling schemes described above. For ease of understanding, an exemplary description will be made below with the cloud platform/computer device as the execution subject.
Example 1
Fig. 3 schematically shows a flow chart of a device scheduling method according to a first embodiment of the application.
As shown in fig. 3, the device scheduling method according to the 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 ensures the real-time reporting effect of the device information of the terminal device 11 and the host information of the host 10 by deploying the device management service 12 on 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 through the real-time reporting interface 21 at fixed time intervals (for example, 1 second), and the cloud platform 20 may receive the device information and the host information reported by the device management service 12 in real time through the real-time reporting interface 21 at fixed time intervals (for example, 1 second).
As an example, the device information may include a device identification number (e.g., a 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, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the real-time reporting interface 21 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/REGISTRYDEVICE;
The request mode is as follows: a POST;
Request parameters: device SN number, brand, model, operating system type, operating system version, device connection status, ROM version, CPU hardware information, CPU architecture information, devicehub IP, devicehub name;
The real-time reporting of the device information can be realized by regularly calling the real-time reporting interface 21 (HTTP interface) to transmit the appointed parameters.
It should be noted that the above HTTP interface example is only an example, and is not meant to limit the present application.
Returning 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 the task type is set for the terminal device 11 through the maintenance tag interface 22 of the cloud platform 20.
The effect of device grouping is achieved on the cloud platform 20 by tagging each terminal device 11 (e.g., setting a task type). As an example, the tagging may include two ways, one is to manually set a task type attribute through the UI of the cloud platform 20, and use the set task type as 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 take 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, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the maintenance tag interface 22 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/updateTaskType;
The request mode is as follows: a 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 diagram 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, mid-perf, and the like. The task types shown in fig. 6 are only examples, and are not limiting to the present application, and may be increased or decreased according to specific requirements.
Returning 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 tag information is improved, and therefore the efficiency of equipment scheduling is improved.
As an example, the device information includes a device identification number (such as a 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.
By way of example, table 1 shows a schematic diagram of a database. For example, the database may include fields as follows: brand model number, SN number (Device identification number of terminal Device 11), device Hub (host name), devicehub IP (IP address of host 10), service status, device status, task type (tag information), remarks, update date, and the like. Wherein, the "service status" and the "device status" are physical status labels, and the "task type" is a service status label. Table 1 shows by way of example, but not by way of limitation, the fields of the database may be increased or decreased according to specific requirements.
TABLE 1
As an example, the "service state" and the "device state" in "table 1" may be maintained by the test script invoking the HTTP interface of the cloud platform 20, and an example of the HTTP interface may be as follows:
HTTP interface name: http:// demo. Test/minor/updateDevice;
The request mode is as follows: a POST;
Request parameters: device SN number, device status, service status;
the service state and 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 a device acquisition interface 23, where the device acquisition interface 23 is configured to return, through the tag information (such as a task type) that is input, the device identification number of the terminal device 11 and the IP address of the host 10; step S804, the label information is transmitted in through the equipment acquisition interface 23; in 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 acquisition interface 23 may be called by a test script, and may be an HTTP interface, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the device acquisition interface 23 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/getLabDevices;
The request mode is as follows: GET;
Request parameters: operating system type, task type;
and (5) returning a result: devicehub IP, device SN number;
By means of the device acquisition interface 23 (HTTP interface): and inquiring devicehub IP and the SN number of the equipment meeting 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, where a field/attribute in the record is called a task type, and the labeling effect is achieved by setting this field, and the labels are mainly the task types, such as the identification of different test tasks, e.g. monkey, perf, etc.
The device information of the terminal device 11, the host information (e.g. devicehub IP) of the host 10 and the corresponding task type information are stored in the database, and the device information and devicehub IP information corresponding to the database are queried according to the label by means of REST API and returned to the user.
The labels comprise service state labels and physical state labels, wherein the service state labels refer to different service test types such as a monkey test, a performance test, a compatibility test and the like, the physical state labels refer to off-line and maintenance states of equipment, off-line labels are set if the equipment is off-line, and maintenance labels are automatically set if the terminal equipment is over-high in temperature or under-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, one or more program modules being stored in a storage medium and executed by one or more processors to complete the embodiments of the present application. Program modules in accordance with the embodiments of the present application are directed to a series of computer program instruction segments capable of performing the specified functions, and the following description describes each program module in detail.
As shown in fig. 9, the cloud platform 900 may include a receiving module 902, a tag module 904, and an obtaining module 906.
A receiving module 902, 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 a 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.
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 through the real-time reporting interface 21 at fixed time intervals (for example, 1 second), and the receiving module 902 may receive the device information and the host information reported by the device management service 12 in real time through the real-time reporting interface 21 at fixed time intervals (for example, 1 second).
As an example, the device information may include a device identification number (e.g., a 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, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the real-time reporting interface 21 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/REGISTRYDEVICE;
The request mode is as follows: a POST;
Request parameters: device SN number, brand, model, operating system type, operating system version, device connection status, ROM version, CPU hardware information, CPU architecture information, devicehub IP, devicehub name;
The real-time reporting of the device information can be realized by regularly calling the real-time reporting interface 21 (HTTP interface) to transmit the appointed 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 tag module 904 is configured to tag the terminal device 11 to obtain tag 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 a UI; or the task type is set to the terminal device 11 via the maintenance tag interface 22.
The effect of device grouping is achieved on the cloud platform 20 by tagging each terminal device 11 (e.g., setting a task type). As an example, the tagging may include two ways, one is to manually set a task type attribute through a UI, and use the set task type as 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 take 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 page of the cloud platform 20, and may be an HTTP interface, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the maintenance tag interface 22 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/updateTaskType;
The request mode is as follows: a 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 acquisition 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.
As an example, the device information includes a device identification number (such as a 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, the acquisition module 906 provides a device acquisition interface 23, and the device acquisition interface 23 is configured to return the device identification number of the terminal device 11 and the IP address of the host 10 through the tag information (e.g., task type) that is entered. The acquiring module 906 inputs the tag information through the device acquiring 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 acquisition interface 23 may be called by a test script, and may be an HTTP interface, alternatively, the HTTP interface may be a REST API, which is friendly, and may be any other interface.
For example, the device acquisition interface 23 (HTTP interface) instance may be as follows:
HTTP interface name: http:// demo. Test/minor/getLabDevices;
The request mode is as follows: GET;
Request parameters: operating system type, task type;
and (5) returning a result: devicehub IP, device SN number;
By means of the device acquisition interface 23 (HTTP interface): and inquiring devicehub IP and the SN number of the equipment meeting 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 a device scheduling method according to a third embodiment of the present application. In an exemplary embodiment of the present application, the computer apparatus 1000 may be an apparatus capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction. For example, it 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 a stand-alone server, or a server cluster composed of a plurality of servers), a gateway, or 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 together by a system bus. Wherein:
memory 1010 includes at least one type of computer-readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), 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, magnetic disk, optical disk, etc. In some embodiments, the memory 1010 may be an internal storage module of the computer device 1000, such as a hard disk or memory of the computer device 1000. In other embodiments, the memory 1010 may also be an external storage device of the computer device 1000, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, abbreviated as SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like, which are provided on the computer device 1000. Of course, the memory 1010 may also include both internal memory modules of the computer device 1000 and external memory devices. In this embodiment, the memory 1010 is typically used to store an operating system and various types of application software installed on the computer device 1000, such as program codes of a device scheduling method, and the like. In addition, the memory 1010 can also be used to temporarily store various types of data that have been output or are to be output.
The processor 1020 may be a central processing unit (Central Processing Unit, abbreviated as CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 1020 is generally used 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, and the like. In this embodiment, processor 1020 is used to execute program code or process data stored in memory 1010.
The network interface 1030 may include a wireless network interface or a wired network interface, with the network interface 1030 typically being used to establish a communications link between the computer device 1000 and other computer devices. For example, the network interface 1030 is used to connect the computer device 1000 to an external terminal through a network, establish a data transmission channel and a communication link between the computer device 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 for mobile communications (Global System of Mobile communication, abbreviated as GSM), wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, etc.
It should be noted that FIG. 10 only shows a computer device having components 1010-1030, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead.
In this embodiment, the device scheduling method stored in the memory 1010 may also be divided into one or more program modules and executed by one or more processors (the processor 1020 in this embodiment) to perform an embodiment of the present application.
Example IV
The embodiment of the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the device scheduling method in the embodiment.
In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card 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 a computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may also be an external storage device of a computer device, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, abbreviated as SMC), a Secure Digital (abbreviated as SD) card, a flash memory card (FLASH CARD), or the like, which are provided on the computer device. Of course, the computer-readable storage medium may also include both internal storage units of a computer device and external storage devices. In this embodiment, the computer readable storage medium is typically used to store an operating system and various types of application software installed on a computer device, such as program codes of the device scheduling method in the embodiment, and the like. Furthermore, 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 application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated into a single integrated circuit module. Thus, embodiments of the application are not limited to any specific combination of hardware and software.
The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (11)
1. A method of scheduling devices, the method comprising:
The 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;
acquiring the equipment information and the host information from the cloud platform according to the tag information so as to realize the scheduling of the terminal equipment;
wherein one of the terminal devices corresponds to at least one tag;
The tag information includes: the task type is the identification of different test tasks;
the scheduling of the terminal equipment comprises the following steps: the cloud platform provides an equipment acquisition interface, and the equipment acquisition interface is called through a test script.
2. The device scheduling method of claim 1, wherein the cloud platform receives device information of a terminal device and host information of a host, and comprises:
The cloud platform deploys equipment management services on the host;
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 of claim 3, wherein the labeling the terminal device by the cloud platform to obtain label information comprises:
Setting the task type for the terminal equipment through the UI of the cloud platform; or (b)
And setting the task type for the terminal equipment through a maintenance tag interface of the cloud platform.
5. The device scheduling method of claim 3, wherein the obtaining the device information and the host information from the cloud platform according to the tag information comprises:
And providing a database for storing the equipment information, the host information and the tag information.
6. The device scheduling method according to any one of claims 1 to 5, wherein the acquiring 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 an equipment identification number of the terminal equipment and an IP address of the host through the tag information;
the cloud platform acquires the tag information transmitted into the interface through the equipment;
And the cloud platform queries the equipment identification number of the terminal equipment and the IP address of the host machine in the database according to the tag 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 device acquisition interface and the maintenance tag interface are 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.
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 label module is used for labeling the terminal equipment to obtain label information;
The acquisition module is used for acquiring the equipment information and the host information according to the tag information so as to realize the scheduling of the terminal equipment;
wherein one of the terminal devices corresponds to at least one tag;
The tag information includes: the task type is the identification of different test tasks;
the scheduling of the terminal equipment comprises the following steps: the cloud platform provides an equipment acquisition interface, and the equipment acquisition interface is called through a test script.
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 is adapted to implement the steps of the device scheduling method of any one of claims 1-7 when the computer program is executed by the processor.
10. A computer readable storage medium, wherein a computer program is stored in the computer readable storage medium, and the computer program is executable by at least one processor, so that the at least one processor performs the steps of the device scheduling method of any one of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, realizes the steps of the method according to any one of claims 1 to 7.
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 CN113434281A (en) | 2021-09-24 |
| CN113434281B true 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) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113794781B (en) * | 2021-11-16 | 2022-02-11 | 佛山技研智联科技有限公司 | Data acquisition method, device, equipment and storage medium |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN106126347A (en) * | 2016-08-17 | 2016-11-16 | 浪潮电子信息产业股份有限公司 | A kind of method effectively realizing mainframe cluster scheduling of resource 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 |
| CN108733553A (en) * | 2017-04-18 | 2018-11-02 | 北京嘀嘀无限科技发展有限公司 | Configuration method, the device and system of test device based on docker |
| 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 |
| 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 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7313564B2 (en) * | 2002-12-03 | 2007-12-25 | Symbioware, Inc. | 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 |
| CN110582750A (en) * | 2017-04-28 | 2019-12-17 | 北京嘀嘀无限科技发展有限公司 | system and method for task scheduling and device management |
| US10728135B2 (en) * | 2017-10-13 | 2020-07-28 | Keysight Technologies, Inc. | Location based test agent deployment in virtual processing environments |
| WO2019089446A1 (en) * | 2017-10-30 | 2019-05-09 | Hitachi Vantara Corporation | Generating testing infrastructure on a cloud for testing software applications |
-
2021
- 2021-07-19 CN CN202110812592.7A patent/CN113434281B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 | 浪潮电子信息产业股份有限公司 | A kind of method effectively realizing mainframe cluster scheduling of resource 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 |
| 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 |
| 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)
| Title |
|---|
| "Testing Cloud Services. How to test Saas, Paas and Iaas";Kees Blokland，Martin Pol，Jeroen Mengerink;《EuroSTAR Software Testing Community》;20190910;全文 * |
| 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》.2014,全文. * |
| 严丽云 ; 何震苇 ; 杨新章 ; 张凌 ; 侯韶新 ."基于Kubernetes的容器化数据库及其集群方案".《电信科学》.2018,全文. * |
| 基于云计算技术的软件测试探索;虞泽凡;;自动化技术与应用(第12期);全文 * |
| 马永 ; 王萍 ; 管建超."基于Docker的应用资源池技术研究".《电力信息与通信技术》 .2018,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113434281A (en) | 2021-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108874558B (en) | Message subscription method of distributed transaction, electronic device and readable storage medium | |
| JP2019523462A (en) | Multitask scheduling method, system, application server, and computer-readable storage medium | |
| CN107800565B (en) | Inspection method, inspection device, inspection system, computer equipment and storage medium | |
| CN109388417B (en) | Communication protocol updating method, system and terminal equipment | |
| CN109361525B (en) | Method, device, control terminal and medium for restarting distributed deployment of multiple services | |
| CN104504587A (en) | Advertisement monitoring method and device, electronic apparatus | |
| CN112422450B (en) | Computer equipment, and flow control method and device for service request | |
| CN108255735B (en) | Associated environment testing method, electronic device and computer readable storage medium | |
| CN112395187A (en) | Test method, test system, computer device and storage medium | |
| CN113434281B (en) | Equipment scheduling method and cloud platform | |
| CN103905441A (en) | Data acquisition method and device | |
| CN111736938A (en) | Information display method and device, storage medium and electronic device | |
| JP2006235831A (en) | Condition management device, method, and program | |
| CN107404456B (en) | Error positioning method and device | |
| CN107277087B (en) | Data processing method and device | |
| CN108965403B (en) | Operation and maintenance monitoring connection establishing method and terminal equipment | |
| CN112818270B (en) | Data cross-domain transfer method and device and computer equipment | |
| CN112804099A (en) | Parameter batch configuration method and device, computer equipment and readable storage medium | |
| CN109766235A (en) | Configuration file detection method, system, equipment and medium based on software supervision | |
| CN113392131A (en) | Data processing method and device and computer equipment | |
| CN108196962B (en) | Method and device for realizing calling of interfaces of different versions | |
| CN111522642B (en) | Method for acquiring and inquiring state monitoring data of wind turbine generator, and electronic equipment | |
| CN110602655B (en) | Short message-based equipment communication address modification method and device and readable storage medium | |
| CN112653567B (en) | Monitoring method, monitoring device, computer equipment and storage medium | |
| CN111162988B (en) | Message distribution method and system |
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 |