TWI754488B - Electronic device and method of selecting carrier for software container - Google Patents

Abstract

An electronic device and a method of selecting a carrier for a software container. The method includes: packaging at least one file as a software container according to a compile file, and generating at least one label of the software container according to the compile file; classifying the software container according to a container classification table and the at least one label to generate a feature table, and defining a storage address of the software container according to a container interface table; testing the software container according to a test script to generate a testing result; receiving carrier profiles respectively corresponding to carriers, calculating weights respectively corresponding to the carriers according to the carrier profiles, selecting the carrier from the carriers according to the weights, and installing the software container at the storage address of the carrier; and transmitting the testing result and a carrier profile corresponding to the carrier.

Description

Electronic device and method for selecting a carrier for a soft container

The present invention relates to an electronic device and method for selecting a carrier for a soft container.

In order to provide users with stable and convenient services, and in the case of limited resources (such as physical devices or virtual devices), a carrier that is currently used less frequently is usually selected to install software containers. However, if the performance of the software container is reduced due to the influence of other software in the carrier, it is often necessary for the administrator to make changes to the software container, which wastes a lot of time and labor costs. In addition, the transfer process of the software container is quite slow, and after the transfer is completed, the administrator also needs to confirm whether the packaging of the software container is successful, the naming name and the container version are correct. When encountering the wrong container packaging, the administrator can only rely on the error analysis, and in the future maintenance and operation, the administrator cannot immediately put the software container on or off the shelf, and need to rely on the program developer to change the software container program again. code. Accordingly, business owners not only need to bear the increasing labor costs, but also need to continuously invest funds to upgrade each physical equipment.

The present invention provides an electronic device and method for selecting a carrier for a soft container, which can automatically select an appropriate carrier for the soft container.

An electronic device for selecting a carrier for a software container of the present invention includes a processor, a storage medium and a transceiver. The storage medium stores multiple modules. The processor is coupled to the storage medium and the transceiver, and accesses and executes a plurality of modules, wherein the plurality of modules include a container listing module, a container compilation module, a container classification module, a container verification module, and a stable container carrier ratio. Check the module for the module and container. The container racking module receives at least one file and a compiled file through the transceiver. The container compilation module includes a container temporary storage area, wherein the container compilation module encapsulates at least one file as a software container according to the compilation file, generates at least one label of the software container according to the compilation file, and stores the software container in the container temporary storage area. The container classification module classifies the software container according to the container type correspondence table and at least one label to generate a feature table, and determines the storage address of the software container according to the container interface correspondence table. The container verification module receives the test script through the transceiver, and tests the software container according to the test script to generate test results. The stable container carrier comparison module receives a plurality of carrier information corresponding to the plurality of carriers through the transceiver, calculates a plurality of weight values corresponding to the plurality of carriers according to the Select the carrier in the , and install the software container in the storage location of the carrier. The container verification module transmits the test result and the carrier information corresponding to the carrier through the transceiver.

In an embodiment of the present invention, the above-mentioned plurality of carrier information includes first carrier information corresponding to the carrier, and the plurality of weight values includes a first weight value corresponding to the carrier, wherein the stable container carrier comparison module is based on the first weight value. A carrier information calculates a first weight value, and selects a carrier in response to the first weight value being the largest of the plurality of weight values.

In an embodiment of the present invention, the above-mentioned first carrier information includes the number of abnormal occurrences corresponding to the carrier and the average number of abnormal occurrences corresponding to at least one carrier in the region where the carrier is located. A first function of subtracting the number of abnormal occurrences from the score is set to calculate a stable trend reference value, and a second function of subtracting the average number of abnormal occurrences from the average preset score is used to calculate the average stable trend reference value, wherein the stable container carrier is compared with the module The first weight value is calculated according to the stable trend reference value and the average stable trend reference value.

In an embodiment of the present invention, the above-mentioned first carrier information includes the performance corresponding to the carrier and the average performance of at least one carrier corresponding to the region where the carrier is located, wherein the stable container carrier comparison module calculates the first carrier according to the performance and the average performance. a weight value.

In an embodiment of the present invention, the above-mentioned first carrier information includes the recommended number of containers and the number of contained containers corresponding to the carrier, wherein the stable container carrier comparison module calculates the first number of containers according to the recommended number of containers and the number of contained containers. a weight value.

In an embodiment of the present invention, the above-mentioned first carrier information includes an expandable hardware configuration corresponding to the carrier and an established hardware configuration, wherein the stable container carrier comparison module is based on the expandable hardware configuration and the established hardware configuration. The body configuration calculates the first weight value.

In an embodiment of the present invention, the above-mentioned modules further include a container management module. The container management module manages the version of the software container according to the feature table, wherein the feature table contains the software container name of the software container.

In an embodiment of the present invention, the container temporary storage area includes a first software container and a second software container, wherein the container management module responds to the first software container name of the first software container and the first software container name of the second software container. The names of the two software containers are the same, and the first time stamp of the first software container is earlier than the second time stamp of the second software container, and it is determined that the second software container is an updated version of the first software container, wherein the container management module uses the first The second soft container replaces the first soft container in the container temporary storage area, and the first soft container is deleted after the first period of time.

In an embodiment of the present invention, the above-mentioned container compilation module generates software container names of the software containers according to the compilation file, wherein the feature table includes the software container names, and the container management module updates the software container names according to the container name correspondence table.

In an embodiment of the present invention, the above-mentioned container compilation module transmits an alert message through the transceiver in response to a mismatch between at least one file and the compilation file.

In an embodiment of the present invention, the above-mentioned container classification module transmits a warning message through the transceiver in response to a mismatch between the container type correspondence table and the at least one label.

In an embodiment of the present invention, the above-mentioned container verification module transmits an alert message through the transceiver in response to not receiving a response from the software container when testing the software container.

A method for selecting a carrier for a software container of the present invention includes: receiving at least one file and a compiled file; encapsulating at least one file into a software container according to the compiled file, generating at least one label of the software container according to the compiled file, and storing the software container in the container temporary storage area; classify the software container according to the container type correspondence table and at least one label to generate a feature table, and define the storage address of the software container according to the container interface correspondence table; receive the test script, and test the software according to the test script a container to generate test results; receive multiple carrier information corresponding to multiple carriers, calculate multiple weight values corresponding to multiple carriers according to the multiple carrier information, select a carrier from multiple carriers according to the multiple weight values, And the software container is installed in the storage address of the carrier; and the test result and the carrier information corresponding to the carrier are transmitted.

Based on the above, the present invention can complete the process of automatic packaging, classification, management, verification, comparison and putting on the shelf of the software container without human intervention. The present invention has the functions of streamlining and automation, and has the advantages of timeliness, correctness, integration, efficiency and convenience. The present invention can reduce the manpower required for reviewing a large number of software containers to be put on the shelf, and can greatly improve the convenience of maintenance, operation and management.

In order to make the content of the present invention more comprehensible, the following specific embodiments are given as examples according to which the present invention can indeed be implemented. Additionally, where possible, elements/components/steps using the same reference numerals in the drawings and embodiments represent the same or similar parts.

FIG. 1 is a schematic diagram of an electronic device 100 for selecting a carrier for a software container according to an embodiment of the present invention. The electronic device 100 may include a processor 110 , a storage medium 120 and a transceiver 130 .

The processor 110 is, for example, a central processing unit (CPU), or other programmable general-purpose or special-purpose micro control unit (micro control unit, MCU), microprocessor (microprocessor), digital signal processing digital signal processor (DSP), programmable controller, application specific integrated circuit (ASIC), graphics processor (graphics processing unit, GPU), image signal processor (image signal processor, ISP) ), image processing unit (IPU), arithmetic logic unit (ALU), complex programmable logic device (CPLD), field programmable gate array (field programmable gate array) , FPGA) or other similar elements or a combination of the above. The processor 110 may be coupled to the storage medium 120 and the transceiver 130 , and access and execute a plurality of modules and various application programs stored in the storage medium 120 .

The storage medium 120 is, for example, any type of fixed or removable random access memory (random access memory, RAM), read-only memory (ROM), and flash memory (flash memory). , hard disk drive (HDD), solid state drive (solid state drive, SSD) or similar components or a combination of the above components for storing a plurality of modules or various applications executable by the processor OOO. In this embodiment, the storage medium 120 can store a container listing module 121 , a container compilation module 122 , a container classification module 123 , a container management module 124 , a container verification module 125 , and a stable container carrier comparison module 126 As well as multiple modules such as the container confirmation module 127, the functions of which will be described later.

The transceiver 130 transmits and receives signals in a wireless or wired manner. Transceiver 130 may also perform operations such as low noise amplification, impedance matching, frequency mixing, up or down frequency conversion, filtering, amplification, and the like.

FIG. 2 is a schematic diagram illustrating selection of a carrier for a software container by the electronic device 100 according to an embodiment of the present invention. The container listing module 121 can receive one or more files and compiled files corresponding to the one or more files through the transceiver 130 . The container compilation module 122 may include a container staging area. The container compilation module 122 can obtain one or more files and a compilation file corresponding to the one or more files from the container listing module 121 . Then, the container compilation module 122 can package one or more files into a software container according to the compilation file.

The container compilation module 122 can generate the software container name of the software container according to the compilation file. For example, the build file may contain the software container name. The container compilation module 122 can name the software container according to the software container name in the compilation file. In addition, the container compilation module 122 can also create one or more labels (or indexes) for the packaged software container according to the compilation file, and store the software container in the container temporary storage area for the container verification module 125 to store. to increase the usage rate of the soft container. If during the process of packaging the software container, the container compilation module 122 finds that there is a file that does not match the compilation file, the container compilation module 122 will not generate the software container. In addition, the container compilation module 122 can record an abnormal situation in the log in response to the mismatch between the file and the compiled file, and can transmit a warning message or log through the transceiver 130 . The administrator can judge whether to reconfigure the files that need to be packaged into software containers or rewrite the compiled files according to the warning message or the prompt of the log.

The container classification module 123 may pre-store or obtain the container type correspondence table and the container interface correspondence table through the transceiver 130 . The container type correspondence table can record the relationship between labels and classifications. The container interface correspondence table can record the storage address of the software container. The container classification module 123 can classify the soft containers in the container temporary storage area according to the container type correspondence table and one or more labels of the soft containers to generate a feature table. The feature table may contain information such as software container names and/or classification results. The container classification module 123 can also determine the storage address of the software container according to the container interface correspondence table. In one embodiment, the container classification module 123 can receive an access command from an external electronic device through the transceiver 130, and output a feature table through the transceiver 130 according to the access command, so that the user of the external electronic device can determine the software Classification of containers. In one embodiment, the container classification module 123 can receive feedback commands from an external electronic device through the transceiver 130, and can update the feature table according to the feedback commands. In other words, when the software container is wrongly classified, the user can instruct the container classification module 123 to correct the classification result of the software container through a feedback command, thereby increasing the working efficiency of personnel and reducing the cost of manual review.

The container management module 124 can manage the version of the software container according to the feature table. Specifically, the container management module 124 can determine whether the feature table includes a plurality of software containers with the same software container name. If the feature table contains multiple software containers with the same software container name, it means that the container temporary storage area stores multiple software containers with the same software container name. Accordingly, the container management module 124 can read the time stamps of multiple software containers with the same software container name in the software temporary storage area, and determine the software container with the latest time stamp as the software container among the software containers. updated version.

The container management module 124 can replace the software container of the newer version with the software container of the old version, and can temporarily store the software container of the old version for a certain period of time. A specific area to store older versions of software containers. If the container management module 124 does not receive an instruction to restore the old version of the software container through the transceiver 130 during the specified period, the container management module 124 may delete the old version of the software container after the specified period of time. If the container management module 124 receives an instruction to restore the old version of the software container through the transceiver 130 at the specific time, the container management module 124 may replace the old version of the software container with the updated version of the software container.

In one embodiment, the container management module 124 may pre-store or obtain the container name correspondence table through the transceiver 130 . The container management module 124 can update the software container name of the software container according to the container name correspondence table. For example, the container management module 124 can filter out specific strings or symbols (eg, undetermined strings or symbols) in the software container names according to the container name correspondence table, or use the strings in the container name correspondence table or symbol to replace the specific string or symbol, thereby updating the software container name. Updating the software container name can effectively reduce the failure rate when the software container name is executed.

The container verification module 125 can receive the test script through the transceiver 130, and can test the software container in the container temporary storage area according to the test script to generate the test result. For example, the container validation module 125 may input parameters to the software container and receive output parameters from the software container according to the test script. The container verification module 125 can compare the input parameters and the output parameters to verify the number of bits, letters, characters or special parameters for the software container. During the testing of the software container, if the container verification module 125 does not receive a response from the software container, the container verification module 125 may determine that the testing process of the software container is abnormal, and may record the abnormal situation in the log. Accordingly, the container verification module 125 can transmit warning messages or logs to the management personnel through the transceiver 130 . The user can flexibly add or update the content of the test script to improve the compatibility rate of execution between software containers.

The stable container carrier comparison module 126 may receive, via the transceiver 130, a plurality of carrier information respectively corresponding to a plurality of carriers, wherein each of the plurality of carriers may include a server, a client, a desktop computer, a Notebook computers, network computers, workstations, personal digital assistants (PDAs), personal computers (personal computers, PCs) or tablet computers and other electronic devices with computing capabilities. The stable container carrier comparison module 126 can calculate a plurality of weight values corresponding to the plurality of carriers according to the plurality of carrier information, and can select a carrier from the plurality of carriers to install the software container according to the plurality of weight values. The stable container carrier comparison module 126 can install the soft container at the storage location of the selected carrier (ie, the storage location determined by the container classification module 123). In one embodiment, the stable container carrier comparison module 126 may include a container database. The container database can store the carrier information of the carrier in which the software container is installed for the reference of the management personnel.

…(1) The stable container carrier comparison module 126 can select the carrier for installing the software container by considering factors such as the stability trend, performance, efficiency or expandability of the carrier according to the carrier information, and store the carrier information of the carrier selected according to the above factors in the container. in the database. Specifically, the stable container carrier comparison module 126 can calculate the weight value of the carrier according to formula (1), and select the carrier with the largest weight value from the multiple carriers to install the software container. Each parameter in formula (1) can be obtained from carrier information.

…(1)

、

、

和

為權重因子。 Ds- i為前 i天之目標載體的穩定趨勢參考值 f1( i)以及目標載體所在區域的平均穩定趨勢參考值 f2( i)的函數，如公式（2）所示。 Q為穩定質量，並且 Q為 Ds- i（ i=1,2,…,n，n正整數）的函數。

…(2) In formula (1), W is the weight value,

,

,

and

is the weight factor. Ds - i is a function of the stable trend reference value f 1( i ) of the target carrier on the previous i day and the average stable trend reference value f 2( i ) of the area where the target carrier is located, as shown in formula (2). Q is the stable mass, and Q is a function of Ds - i ( i = 1,2,...,n, n positive integers).

…(2)

Specifically, the carrier information may include the number of abnormal occurrences B 1( i ) of the target carrier in the previous i days, and may include a plurality of carriers (the plurality of carriers including the target carrier) corresponding to the region where the target carrier is located. Average number of abnormal occurrences B2 ( i ) for i days, wherein each of the plurality of carriers is geographically the same as the target carrier, or each of the plurality of carriers and the target carrier are composed of the same Gateway management. The stable container carrier comparison module 126 may subtract the function g 1( B 1( i )) of the number of abnormal occurrences from the individual preset score A 1 corresponding to the target carrier to calculate the stable trend reference value f 1( i ). The stable container carrier comparison module 126 can calculate the average stable trend reference value f 2( i ) by subtracting the function g 2( B 2( i )) of the average number of abnormal occurrences from the average preset score corresponding to the region where the target carrier is located . The stable container carrier comparison module 126 can calculate the stable mass Q according to the stable trend reference value f 1( i ) and the average stable trend reference value f 2( i ), so as to calculate the weight value W according to the stable mass Q.

In formula (1), S is the carrier individual factor, and S is a function of efficacy B and average efficacy I. Specifically, the carrier information may further include the performance B of the target carrier, and may include the average performance I of a plurality of carriers in the region where the target carrier is located (the plurality of carriers include the target carrier). The stable container carrier comparison module 126 can calculate the individual factor S according to the performance B and the average performance I , so as to calculate the weight value W according to the individual factor S. In one embodiment, the performance of the carrier is related to parameters such as bandwidth of the carrier, hardware performance value, RAID array resources, or cache support.

The carrier information can also include the recommended number of containers O of the target carrier (which can be defined by the management personnel according to the specifications of the carrier), and the number of containers that have been accommodated by the target carrier U (ie: the number of software containers that the target carrier has installed) . The stable container-carrier comparison module 126 may calculate the weight value W according to the number O of the proposed container and the number U of the container already contained.

The carrier information can also include the expandable hardware configuration E of the target carrier (which can be defined by the administrator according to the specifications of the carrier), and can include the established hardware configuration F of the target carrier (ie: the hardware configuration of the target carrier that has been expanded) . The stable container carrier comparison module 126 can calculate the weight value W according to the suggested scalable hardware configuration E and the established hardware configuration F.

After the stable container carrier comparison module 126 selects an appropriate carrier for the soft container, the stable container carrier comparison module 126 may store the carrier information of the selected carrier in the container database. The container verification module 127 can obtain the carrier information from the container database, and can obtain the test result of the software container from the container verification module 125 . The container verification module 125 can transmit the carrier information to the management personnel through the transceiver 130 (eg, to the management personnel's electronic mailbox) for the management personnel's reference.

3 is a flowchart illustrating a method for selecting a carrier for a software container according to an embodiment of the present invention, wherein the method may be implemented by the electronic device 100 as shown in FIG. 1 . In step S301, at least one file and a compiled file are received. In step S302, at least one file is packaged into a software container according to the compiled file, at least one label of the software container is generated according to the compiled file, and the software container is stored in the container temporary storage area. In step S303, the software containers are classified according to the container type correspondence table and at least one label to generate a feature table, and the storage addresses of the software containers are defined according to the container interface correspondence table. In step S304, a test script is received, and the software container is tested according to the test script to generate a test result. In step S305, receiving a plurality of bearer information corresponding to the plurality of bearers respectively, calculating a plurality of weight values corresponding to the plurality of bearers according to the plurality of bearer information, selecting a bearer from the plurality of bearers according to the plurality of weight values, and Install the software container in the storage location of the carrier. In step S306, the test result and the carrier information corresponding to the carrier are transmitted.

To sum up, the container compiling module of the present invention can carry out the launch of the software container according to the business function characteristics. The container compilation module is responsible for encapsulating independent software containers, and assigning them to single or multiple file configurations, creating a single or multiple file encapsulation, that is, it is not necessary to repeatedly develop software containers with the same function. The container compilation module can also store the software container in the container temporary storage area, thereby effectively improving the utilization rate of the software container.

The container classification module of the present invention can classify software containers according to a user-defined configuration. Moreover, the configuration of the software container can be judged through the condition setting, and various types of software containers can be distinguished. The container classification module allows users to efficiently use the classified software containers, and can receive feedback from users, thereby increasing the efficiency of personnel work and effectively reducing the cost of manual review.

The container management module of the present invention can perform version management for software containers. The container management module can delete the old version of the software container and keep the old version for a certain period of time. Recoverable within the time limit. The container management module can also check and change the container naming rules, and automatically filter invalid names or symbols, which can effectively reduce the failure rate of container execution.

The container verification module of the present invention can test and verify the software container, and judge whether the software container can be executed normally according to the test and verification script. The container verification module can also flexibly increase and update the content of script data, and perform confirmation checks on input/output parameters, so as to effectively improve the compatibility rate between software containers.

The stable container carrier comparison module of the present invention can select a carrier suitable for installing a soft container from a large number of carriers. The stable container carrier comparison module can calculate the stable trend, performance, efficiency or scalability of each carrier through the calculation of the weight formula, and find the carrier that matches the software container in a short time, greatly improving the software container. The convenience of carrier maintenance and management.

The container confirmation module of the present invention can read the carrier information of the carrier in which the software container is installed, without the intervention of management personnel, and can reduce the error of information content reporting due to human factors. The container confirmation module can automatically filter out the information content according to the template sent by the mail, and send it back to the administrator's mailbox.

100: Electronics

110: Processor

120: Storage Media

121: Container Shelving Module

122: Container Compilation Module

123: Container classification module

124: Container Management Module

125: Container Verification Module

126: Stable container carrier comparison module

127: Container Confirmation Module

130: Transceiver

S301, S302, S303, S304, S305, S306: Steps

FIG. 1 is a schematic diagram illustrating an electronic device for selecting a carrier for a software container according to an embodiment of the present invention. FIG. 2 is a schematic diagram illustrating selection of a carrier for a software container by an electronic device according to an embodiment of the present invention. 3 is a flowchart illustrating a method of selecting a carrier for a soft container according to an embodiment of the present invention.

S301, S302, S303, S304, S305, S306: Steps

Claims (12)

An electronic device for selecting a carrier for a software container, comprising: a transceiver; a storage medium, storing a plurality of modules; and a processor, coupled to the storage medium and the transceiver, and accessing and executing the plurality of modules group, wherein the multiple modules include: a container listing module, which receives at least one file and a compilation file through the transceiver; a container compilation module, including a container temporary storage area, wherein the container compilation module is based on the The compilation file encapsulates the at least one file as the software container, generates at least one label of the software container according to the compilation file, and stores the software container in the container temporary storage area; the container classification module, The software container is classified according to the container type correspondence table and the at least one label to generate a feature table, and the storage address of the software container is determined according to the container interface correspondence table; the container verification module, through the transceiver receiving a test script, and testing the software container according to the test script to generate a test result, wherein the container verification module passes the transceiver in response to not receiving a response from the software container when testing the software container The device transmits a warning message; stabilizes the container-carrier comparison module, receives a plurality of carrier information corresponding to a plurality of carriers through the transceiver, and calculates a plurality of carrier information corresponding to the plurality of carriers according to the plurality of carrier information weight value, according to the plurality of weight values the carrier is selected from the plurality of carriers, and the soft container is installed at the storage location of the carrier; and a container validation module that transmits the test result and corresponding to the carrier through the transceiver The carrier information of the mentioned carrier. The electronic device of claim 1, wherein the plurality of bearer information includes first bearer information corresponding to the bearer, and the plurality of weight values includes a first weight value corresponding to the bearer, wherein the The stable container carrier comparison module calculates the first weight value according to the first carrier information, and selects the carrier in response to the first weight value being the largest of the plurality of weight values. The electronic device according to claim 2, wherein the first carrier information includes the number of abnormal occurrences corresponding to the carrier and the average number of abnormal occurrences of at least one carrier corresponding to the region where the carrier is located, wherein the stable container The carrier comparison module subtracts the first function of the number of abnormal occurrences from the individual preset scores to calculate a stable trend reference value, and subtracts the second function of the average number of abnormal occurrences from the average preset score to calculate the average stability A trend reference value, wherein the stable container carrier comparison module calculates the first weight value according to the stable trend reference value and the average stable trend reference value. The electronic device of claim 2, wherein the first carrier information includes performance corresponding to the carrier and an average performance of at least one carrier corresponding to an area where the carrier is located, wherein the stable container carrier is compared with a model The group calculates the first weight value based on the performance and the average performance. The electronic device of claim 2, wherein the first carrier information includes a recommended number of accommodating containers and a number of accommodating containers corresponding to the carrier, wherein the stable container-carrier comparison module accommodates containers according to the suggestion The first weight value is calculated based on the number and the number of the accommodated containers. The electronic device of claim 2, wherein the first carrier information includes an expandable hardware configuration and an established hardware configuration corresponding to the carrier, wherein the stable container carrier comparison module is based on the scalable hardware configuration. The first weight value is calculated by extending the hardware configuration and the established hardware configuration. The electronic device of claim 1, wherein the modules further comprise: a container management module, which manages the version of the software container according to the feature table, wherein the feature table includes the software of the software container Container name. The electronic device of claim 7, wherein the container temporary storage area includes a first software container and a second software container, wherein the container management module is responsive to the first software container name of the first software container and the The name of the second software container of the second software container is the same, and the first time stamp of the first software container is earlier than the second time stamp of the second software container, and the second software container is determined to be the same. an updated version of the first soft container, wherein the container management module replaces the first soft container in the container temporary area with the second soft container, and deletes the first soft container after a first period of time has elapsed Soft container. The electronic device according to claim 7, wherein the container compilation module generates a software container name of the software container according to the compilation file, wherein The feature table includes the software container name, wherein the container management module updates the software container name according to the container name correspondence table. The electronic device of claim 1, wherein the container compilation module transmits the alert message through the transceiver in response to a mismatch between the at least one file and the compilation file. The electronic device of claim 1, wherein the container classification module transmits the alert message through the transceiver in response to a mismatch between the container type correspondence table and the at least one label. A method for selecting a carrier for a software container, comprising: receiving at least one file and a compiled file; encapsulating the at least one file as the software container according to the compiled file, and generating at least one of the software container according to the compiled file label, and store the software container in the container temporary storage area; classify the software container according to the container type correspondence table and the at least one label to generate a feature table, and define the software container according to the container interface correspondence table storage address; receive a test script, and test the software container according to the test script to generate a test result; transmit a warning message in response to not receiving a response from the software container when testing the software container; receive a separate A plurality of carrier information corresponding to a plurality of carriers, a plurality of weight values corresponding to the plurality of carriers are calculated according to the plurality of carrier information, and a plurality of weight values corresponding to the plurality of carriers are calculated according to the plurality of carrier information. A weight value selects the carrier from the plurality of carriers, and installs the software container at the storage address of the carrier; and transmits the test result and carrier information corresponding to the carrier.

Images