CN105335173A

CN105335173A - Method, apparatus and system for initializing intelligent terminal device

Info

Publication number: CN105335173A
Application number: CN201410310129.2A
Authority: CN
Inventors: 原宗阳
Original assignee: Beijing Qihoo Technology Co Ltd; Qizhi Software Beijing Co Ltd
Current assignee: Beijing Qihoo Technology Co Ltd; Qizhi Software Beijing Co Ltd
Priority date: 2014-07-01
Filing date: 2014-07-01
Publication date: 2016-02-17
Also published as: WO2016000623A1

Abstract

The invention discloses a method, an apparatus and a system for initializing an intelligent terminal device. The method comprises: editing an instruction file used for installing application software, packaging an application software package into an installation package by utilizing the edited instruction file, and storing the installation package in a server; editing an installation package configuration file containing server address information, and configuring the installation package configuration file to a to-be-initialized intelligent terminal device; installing a service used for providing the installation package for the to-be-initialized intelligent terminal device in the server, pointing a directory of the service to a storage path of storing the installation package, and starting the service; and triggering the to-be-initialized intelligent terminal device to read the embedded installation package configuration file, and according to the read installation package configuration file, obtaining the installation package from the service started by the server, and performing installation. By applying the method, the apparatus and the system, the initialization time can be shortened and the initialization efficiency can be improved.

Description

Method, device and system for initializing intelligent terminal equipment

Technical Field

The invention relates to a computer initialization technology, in particular to a method, a device and a system for initializing intelligent terminal equipment.

Background

With the development of computer communication technology and internet technology, intelligent terminal devices, such as video phones, conference terminals, mobile phones, personal computers with built-in multimedia functions, personal digital assistants, and servers, are increasingly used, and the number of applications is also increasing. After the intelligent terminal device is put on shelf until the intelligent terminal device is delivered to a service application for use, environment initialization needs to be carried out on the intelligent terminal device, namely, parameter initialization configuration and application software installation are carried out on the intelligent terminal device, so that a user can use corresponding services on the intelligent terminal device based on the initialization, and the initialization of the intelligent terminal device mainly comprises the following steps:

1) the initialization configuration of the parameters of the intelligent terminal equipment comprises the following steps: the system comprises a disk partition initialization configuration, a time server initialization configuration, a domain name server initialization configuration, a system parameter initialization configuration, an application software warehouse source initialization configuration, a host name correction configuration and the like.

2) And installing application software. Installing corresponding operating systems according to the purposes of different intelligent terminal devices, and installing other application software (the operating system is one of the application software) based on the installed operating systems, wherein the application software includes but is not limited to: lnmp (Linux, Nginx, Mysql, Php), Lamp (Linux, Apache, MySQL, Perl/PHP/Python), Memcached, Redis, Mongodb, Varnish, Haproxy.

Taking the example of initializing a server with 4CPU and 8G Random Access Memory (RAM), that is, compiling and installing Lnmp on the server, the method includes the following steps:

step one, installing Nginx, comprising:

a, decompressing a Nginx software package, wherein the Nginx software package is as follows: tar-xzvfnginx-version. tar.gz;

b, manually compiling the decompressed Nginx software package (specific parameters are not published outside): fastener; make-j 4;

c, installing the compiled Nginx software package: makeinstall.

Second, installing Php, including:

a, decompressing a Php software package, wherein the Php software package is as follows: tar-xzvffphp-version.

b, manually compiling the decompressed Php software package (specific parameters are not published externally): fastener; make-j 4;

c, installing the compiled Php software package: makeinstall.

Thirdly, installing Mysql, comprising:

a, decompressing a Mysql software package, wherein the Mysql software package comprises: tar-xzvffphp-version.

b, manually compiling the decompressed Mysql software package (specific parameters are not published externally): fastener; make-j 4;

c, installing the compiled Mysql software package: makeinstall.

It should be noted that the step one, the step two, and the step three are not sequentially divided, wherein in the installation process, some operation flows of manual compiling and configuring are required, and after the three steps are completed, the flow of compiling and installing the Lnmp on the server is completed.

As can be seen from the above, in the conventional method for initializing the intelligent terminal devices by manually compiling the software package, for each intelligent terminal device, some operation flows of manual compiling and configuring need to be performed by an installer, and some configuration operations are simple repeated configuration operations, so that the time required for initializing the cluster intelligent terminal devices is long, and the initialization efficiency is low. Specifically, first, when the number of the intelligent terminal devices to be initialized is large, corresponding time is required for initializing each intelligent terminal device, so that the total initialization time is long; secondly, the initialization coverage of the intelligent terminal equipment is wide, for example, the intelligent terminal equipment needs to be respectively initialized aiming at different application scenes; thirdly, in the process of installing the application software package, operations such as manual compiling and the like are required, so that the installation time is long; moreover, the installation process needs to be monitored to prevent problems in application software installation; finally, the installation process of each intelligent terminal device is repetitive, so that the time required by an installer to complete installation is long.

Disclosure of Invention

In view of the above, the present invention has been made to provide a method, apparatus and system for initializing a smart terminal device that overcome or at least partially solve the above-mentioned problems.

According to one aspect of the invention, a method for initializing a smart terminal device is provided, the method comprising:

editing a description file for installing the application software and packaging the application software package into an installation package by using the edited description file and storing the installation package in a server;

editing an installation package configuration file containing server address information, and configuring the installation package configuration file to intelligent terminal equipment to be initialized;

installing a service for providing the installation package for the intelligent terminal equipment to be initialized on the server, directing the directory of the service to a storage path for storing the installation package, and starting the service;

triggering the intelligent terminal equipment to be initialized to read the built-in installation package configuration file, and acquiring and installing the installation package from the service started by the server according to the read installation package configuration file.

Preferably, the specification document comprises: a preamble section and an installation flow section, wherein,

the introduction part is used for setting the package name of the application program software and the source code compression package name corresponding to the application program software;

the installation process part: the method is used for setting the installation flow of the application software.

Preferably, the description file further includes a macro definition part for defining the macro name and the content of the macro name mapping, and/or a description part for describing a brief introduction of the application software package.

Preferably, the installation process part includes: preparing a phase script segment description, compiling a phase script segment description, installing a phase script segment description, cleaning a phase script segment description, and file list script segment description.

Preferably, the installation process part further includes: installing a post-stage script segment description, and/or uninstalling a pre-stage script segment description, and/or uninstalling a post-stage script segment description, and/or a log script segment description.

Preferably, the preparation phase script segment description comprises:

a11, inquiring the preamble part in the instruction file, acquiring whether the application software to be installed needs to depend on other application software, if so, installing the dependent other application software, and executing the step A12, otherwise, directly executing the step A12;

and A12, decompressing the source code compressed packet corresponding to the source code compressed packet name in the preamble part to a preset compiling directory.

Preferably, the packaging the application software package into an installation package by using the edited description file comprises:

and calling the rpmbild command, designating the application program software package and the description file corresponding to the application program software package, packaging and packaging to generate the installation package.

Preferably, after the generating the installation package, the method further comprises:

and carrying out installation flow test on the generated installation package, and if the generated installation package does not pass the installation flow test, modifying the description file until the generated installation package after modification passes the installation flow test.

Preferably, the method further comprises:

and according to the application scene, combining the installation packages passing the installation process test, editing a package configuration file for the combined installation package, and packaging the edited package configuration file and the combined installation package into the installation package.

Preferably, the editing the package configuration file comprises:

install yum-groups-manager commands;

in each installation package, creating an index corresponding to the file in each installation package;

and calling the package configuration command, and applying the created index to the called package configuration command to obtain a package configuration file.

Preferably, the package configuration file is in an extensible markup language format.

Preferably, the obtaining the installation package from the service started by the server according to the read installation package configuration file includes:

installing the hypertext transfer protocol daemon service on the server, pointing a directory of the hypertext transfer protocol daemon service to an installation package storage path for storing an installation package, and starting the hypertext transfer protocol daemon service;

editing the directory file mapped by the storage path of the installation package on the intelligent terminal equipment to be initialized;

the method comprises the steps that the started intelligent terminal equipment to be initialized reads a built-in installation package configuration file, and an installation package is obtained from a service started by a server according to the read installation package configuration file;

and installing the installation package in the directory file mapped by the storage path of the installation package.

According to another aspect of the present invention, there is provided an apparatus for initializing a smart terminal device, the apparatus including: a packaging module, a testing module, and an initialization communication module, wherein,

the packaging module is used for editing the description file for installing the application program software, packaging the application program software package into an installation package by using the edited description file and outputting the installation package to the testing module; receiving a test passing notification output by the test module, and outputting the installation package passing the test to the initialization communication module; receiving a test failure notice output by the test module, modifying the edited specification, repackaging the application program software package into an RPM package by utilizing the modified specification file, and outputting the RPM package to the test module;

the test module is used for carrying out installation flow test on the received installation package, outputting a test failure notice to the packaging module if the installation flow test fails, and outputting a test passing notice to the packaging module if the installation flow test passes;

the initialization communication module is used for editing an installation package configuration file containing server address information, configuring the installation package configuration file to the intelligent terminal device to be initialized, installing the service for providing the installation package for the intelligent terminal device to be initialized, enabling the directory of the service to point to a storage path for storing the installation package, starting the service, communicating with the intelligent terminal device to be initialized, and outputting the installation package to the intelligent terminal device to be initialized for installation.

Preferably, the packaging module is further configured to confirm that the installation package corresponding to the application scenario passes the test according to the preset application scenario, combine the installation packages corresponding to the application scenario, edit the package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into the installation package, and output the installation package to the initialization communication module.

Preferably, the specification document comprises: a macro definition part for defining the macro name and the content of the macro name mapping; a preamble part for setting the application software package name and the source code compressed package name corresponding to the application software, the application software package information depending on compiling, and the application software package information depending on installing; a description section for brief introduction of the application software package and an installation flow section for setting an installation flow of the application software.

According to still another aspect of the present invention, there is provided a system for initializing a smart terminal device, the system including: installing a packaging machine, installing a packaging tester, a server and intelligent terminal equipment to be initialized, wherein,

the installation packaging machine is used for editing the description file of the installation application program software, packaging the application program software package into an installation package by using the edited description file and outputting the installation package to the installation package testing machine; receiving a test passing notice output by the installation package testing machine, and outputting the installation package passing the test to a server; receiving a test failure notice output by the installation package testing machine, modifying the edited description, repackaging the application program software package into an RPM (rotating speed) package by utilizing the modified description file, and outputting the repackaged installation package to the installation package testing machine;

the installation package testing machine is used for carrying out installation process testing on the received installation package, outputting a test failure notice to the installation packaging machine if the installation process testing fails, and outputting a test passing notice to the installation packaging machine if the installation process testing passes;

the server is used for editing an installation package configuration file containing server address information, configuring the installation package configuration file to the intelligent terminal equipment to be initialized, installing the service for providing the installation package for the intelligent terminal equipment to be initialized, pointing a directory of the service to a storage path for storing the installation package, starting the service, communicating with the intelligent terminal equipment to be initialized, and outputting the installation package to the intelligent terminal equipment to be initialized for installation;

and the intelligent terminal equipment to be initialized is used for reading the built-in installation package configuration file, acquiring the installation package from the service started by the server according to the read installation package configuration file, and installing the installation package.

Preferably, the installation packaging machine is further configured to confirm that the installation package corresponding to the application scenario passes the test according to the preset application scenario, combine the installation packages corresponding to the application scenario, edit the package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into the installation package, and output the installation package to the server.

Preferably, the installation package generated by packaging is transmitted to an installation package tester by using a remote mirror automatic synchronization technology.

Preferably, the installation baler comprises: community enterprise operating system 5 installs the baling press and community enterprise operating system 6 installs the baling press.

According to the method, the device and the system for initializing the intelligent terminal equipment, the description file for installing the application program software is edited in advance, the application program software package is packaged into the RPM (rotating speed) package by using the edited description file, the installation package configuration file containing the address information of the server is preset in the intelligent terminal equipment to be initialized, the intelligent terminal equipment to be initialized obtains the installation package from the server through the built-in installation package configuration file after being started, and the installation package is packaged by using the description file edited by the embodiment of the invention, so that the intelligent terminal equipment can be automatically installed after obtaining the installation package, and the technical problem that the cost of initializing the intelligent terminal equipment is wasted in manpower and material resources is solved, particularly when the number of the intelligent terminals to be initialized is large, the time required for initializing the intelligent terminal equipment is shortened, and the method and the system for initializing the intelligent terminal equipment, The beneficial effect of improving the initialization efficiency.

The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 shows a method flow for initializing an intelligent terminal device according to an embodiment of the present invention;

FIG. 2 shows an apparatus structure for initializing an intelligent terminal device according to an embodiment of the present invention; and the number of the first and second groups,

fig. 3 shows a system structure for initializing the intelligent terminal device according to the embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

In the existing method for environment initialization of intelligent terminal equipment through manual compiling of software packages, for each intelligent terminal equipment, some manual configuration operations need to be performed by an installer, and some configuration operations are simple repeated configuration operations, so that the time required for initialization is long and the initialization efficiency is low under the condition that the number of intelligent terminal equipment to be initialized is large.

The yellow dog update modified (Yum) server is a Shell front-end software package manager in a desktop operating system (Fedora), a red cap (RedHat) and software and system development (SUSE), a community enterprise operating system (centros), and can enable an initialized intelligent terminal device to automatically download an RPM package from a designated server for application installation and update and automatically process the dependency relationship of an application to realize the software package which all depends on the application once without fussy once downloading and installation. Wherein, the RPM package available for Yum download is maintained by Linux community, including the application software package provided by Fedora itself and the Fedora extra application software package from red hat software management tool software package warehouse (RPMfusion) and RPM. According to different installation modes, the Yum server can install a single application software and the dependency relationship of the application software by adopting a Yum technology, and can also install an application software installation package by adopting a Yum group (Yumgroup) technology, wherein the application software installation package comprises a plurality of application software and the dependency relationship corresponding to the plurality of application software.

Yum server involves the following technologies:

1) the RPM packaging technology is used for carrying out personalized processing on the application program software of the native version, so that the personalized application program software (RPM package) can be suitable for different application scenes, the time required by compiling, installing and debugging the application program software is saved, and the labor cost is reduced.

2) The Yum application software warehouse management technology is used for combining RPM (speed Per minute) packages according to different application scenes to form an RPM group (RPMgroup) package, and performing centralized unified management on the RPM package, so that the problem of interdependence among application software and the application software package groups required by different application scenes is solved, and a user can conveniently, quickly and efficiently finish a specified task.

3) The remote mirror image automatic synchronization (Rsync, remote sync) technology adopts a Client/Server (C/S, Client/Server) mode, a Server (Yum Server) stores an RPM packet or an RPM group packet generated by an RPM packaging technology, and after network connection between the initialized Client and the Server is established, the RPM packet or the RPM group packet can be automatically downloaded from the Server and installed, so that high-efficiency and reliable installation of application software is realized.

In the embodiment of the invention, for the consumption of the time cost and the labor cost of the conventional scheme for initializing the intelligent terminal equipment by manually compiling the software package, the Yum technology and the Yumgroup technology are considered to be applied to the initialization of the intelligent terminal equipment, so that the waste of the cost of the initialization work on the labor and the material resources is solved, the time required by the initialization is reduced, and the initialization efficiency is improved. Specifically, the RPM packaging technology, the Rsync technology and the Yum application software warehouse management technology are comprehensively utilized, and the problem of complex and redundant steps in the initialization process in the prior art is solved.

Fig. 1 shows a method flow for initializing an intelligent terminal device according to an embodiment of the present invention. Referring to fig. 1, the process includes:

step 101, editing a description file for installing application software, packaging an application software package into an installation package by using the edited description file, and storing the installation package in a server;

in this step, the installation package includes, but is not limited to, an RPM package. By analyzing the application software installation flow and compiling the application installation flow into a specification (Spec) file, so that the RPM package generated by the application software package is packaged by using the edited specification file, automatic installation can be performed according to the compiled installation flow. Wherein, each application software corresponds to a description file.

In the embodiment of the invention, the Spec file is a specification for manufacturing an RPM package, and the Spec file comprises the following components: a macro definition part, a preamble part, a description part and an installation flow part. Wherein,

and the macro definition part is used for defining the macro name and the content of the macro name mapping, the macro is similar to variables during programming, and if the macro name is quoted in subsequent application, the macro name is expanded into the content of quoting the macro name mapping. By utilizing macro definitions, maintainability, portability, etc. of the specification file may be improved.

In the embodiment of the present invention, the macro definition part is an option.

The introduction part is used for setting the name of an application software package, the name of a source code compression package corresponding to the application software, application software package information dependent on compiling, application software package information dependent on installing and the like. The information of the application software package depending on compiling and the information of the application software package depending on installing are optional items, and are determined according to whether the application software is compiled and installed and depends on other application software packages. The preamble may further include: version number, release number, etc.

Description (% description) section: this section is used to query the application package for brief introduction by command of RPM-qi, etc., when the user does not know the application package.

In the embodiment of the present invention, the description section is an option.

The installation process part: the installation process for setting the application software comprises the following script segment descriptions:

1. preparation phase (% pre) comprising:

in this step, if the application software to be installed needs to depend on other application software, for example, when the application software a is installed, the application software B needs to be installed first, and in this preparation stage, the application software B is installed first.

In this step, the preset compiling directory may be set in a manner defined by the macro, for example, decompressed under the BUILD directory to be ready for the next compiling stage.

In the embodiment of the invention, the source code compression packet corresponding to the source code compression packet name is arranged in the application program software package.

2. Compile stage (% build): at this stage, the source code compressed packets decompressed under the preset compilation directory are compiled.

3. Installation stage (% install): in the installation stage, the binary application program file, the application program configuration file, the service script file and the like generated by compiling are installed under a preset virtual root directory for temporary storage, wherein the virtual root directory is the root directory of a host (intelligent terminal equipment to be initialized) for subsequently installing an RPM (rotating speed) packet.

In the embodiment of the present invention, the virtual root directory may be represented by a macro "buildrop".

4. Cleaning phase (% clean): and after the installation is finished, deleting the virtual root directory set in the installation stage.

5. File list (% file): the file list is the core of the Spec file, and only files listed in the file list will eventually be packaged into an RPM package. Wherein the files in the file list are files necessary for installing the application software.

As an alternative embodiment, after some application software is installed, personalized function settings can be performed on the application software, and the Spec file can further comprise:

6. post-installation stage (% post): the method is used for carrying out personalized function setting on the installed application software.

In practical applications, the pre-unloading and post-unloading stages (% preun,% postun) may also be set in the installation flow portion, so as to set the operations before and after unloading, respectively.

As an alternative embodiment, a log (Changelog) script segment may be set in the installation flow part to describe the update log of the application software.

In the script section, preset operation can be realized by writing a shell program. For example, the preparation phase, the compiling phase, the installing phase, the cleaning phase, the file list and the program code sections corresponding to the post-installing phase can be written into the corresponding paragraphs in the shell program.

As an alternative embodiment, packaging the edited profile and the application software package as an RPM package comprises:

and calling an rpmbuild command, designating an application software package and a Spec file corresponding to the application software package, packaging and packaging to generate an RPM (revolution speed) package.

In this step, for example, an RPM packet may be generated by the rpmbuild-bb < specfile > command line. Wherein the-bb parameter indicates that the RPM package is generated only according to the specfile file.

According to the embodiment of the invention, the application software package is packaged in sequence according to the macro definition part, the introduction part, the description part and the installation flow part contained in the edited description file, and the RPM package is generated.

As an alternative embodiment, after generating the RPM packet, the method may further comprise:

and carrying out installation process test on the generated RPM packet, and if the generated RPM packet does not pass the installation process test, modifying the description file until the generated RPM packet passes the installation process test after modification.

In the step, the test is to automatically install the RPM package by using the rsync, if the RPM package is in a problem in installation, the Spec file is modified according to the displayed prompt information, then the application software package is packaged according to the re-modified Spec file to generate the RPM package, and then the installation process test is carried out until the installation process test is passed. Therefore, the error reporting probability in the initialization process is reduced, the success rate and the reliability of the intelligent terminal device during initialization are improved, and the efficiency of initializing the intelligent terminal device is improved.

As another alternative, after generating the RPM package or the generated RPM package is tested by the installation process, the method may further include:

and according to the application scene, combining the generated RPM packets, editing a package packet configuration file for the combined RPM packets, and packaging the edited package packet configuration file and the combined RPM packets into an RPM package packet.

In this step, application software packages of different combinations need to be installed due to different application scenarios, for example, as described above, Linux, Nginx, Mysql, and Php need to be installed for Lnmp, and Linux, Apache, Mysql, and Php need to be installed for Lamp. Therefore, in the embodiment of the invention, in order to improve the service experience of a user using the intelligent terminal device after installation, the RPM packets tested by the installation process can be managed in groups according to different application scene requirements, that is, the RPM packets are combined according to different application scene requirements, so that the setting of the application scene can be completed by one-time initialization, the user operation is effectively reduced, and the time required by the initialization is reduced.

After the grouping management is performed, in order to describe each parameter in the application scenario of each RPM packet in the combined RPM packet, for example, the combined RPM packet, an index path of the package metadata is saved, and the included RPM packet information is configured, a package configuration file corresponding to the combined RPM packet may be edited according to the RPM packet obtained by the grouping management, and each combined RPM packet corresponds to one package configuration file.

In this step, taking the intelligent terminal device as the Yum server as an example, editing the package configuration file includes:

b11, installing yum-groups-manager command;

in this step, the command behavior of yum-groups-manager command is installed: mercinstalumyum-utils. The yum-groups-manager command is used to trigger execution of subsequent flows.

B12, in each RPM packet, creating an index corresponding to the file in each RPM packet;

the step is an optional step, and by creating the corresponding index for the file in the RPM packet, the time required for inquiring the file can be reduced, and the inquiring efficiency is improved. Command behavior to create index: createrepo-d-updatepath. Wherein, the parameter of "-d" is the necessary parameter, and the path is the index path.

B13, calling the package configuration command, and applying the created index in the called package configuration command to obtain a package configuration file.

In this step, the package configuration command is as follows:

yum-groups-manager-n"groupname"--id＝"groupid"--description＝"…..."--save＝path/repodata/*.xml--mandatoryRPM[RPM]…

wherein,

-n parameters: specifying a group package name;

-id parameter: generating a unique identification of a group (group) packet;

-description parameter: the package is simply described, so that a user can conveniently know information;

- -save parameter: storing the package metadata into a file under a preset index path;

- -directory parameter: one or more RPM packets contained in the group packet are specified.

As an alternative embodiment, the package configuration file format may be in extensible markup language (XML) format.

For example, for a generated package configuration file:

yum-groups-manager-n"LNMP-2.2.20-5.2.5"--id＝"LNMP"--description＝"Nginx-1.2.9,Php-5.2.5,MySQL-5.5"--save＝/usr/local/www/CentOS/5/os/x86_64/repodata/mygroups.xml--mandatoryQihoo-App-nginxQihoo-App-phpQihoo-App-mysql

in the group configuration file, it is shown that a group named "LNMP-2.2.20-5.2.5" is generated by using installed yum-groups-manager command, the unique identifier of the group is LNMP, which is described as "version 1.2.9 nginx program, version 5.2.5 php program, version 5.5 mysql program", and the metadata of LNMP-2.2.20-5.2.5 group is stored in/usr/local/www/centros/5/os/x 86_ 64/reposata/mygroups.

As an alternative embodiment, the method may further include:

and after the combined RPM packet is updated, updating the group packet configuration file corresponding to the combined RPM packet.

In this step, the updating includes: delete, modify, add, etc. Command behavior to update package configuration files: createrepo-verbose-gpath/repodata/. xmlpath.

By updating the package configuration file, the newly added RPM package can be searched by the intelligent terminal device.

For example: a command line to update a package configuration file is specified as follows:

createrepo--verbose-g/usr/local/www/CentOS/5/os/x86_64/repodata/mygroups.xml/usr/local/www/CentOS/5/os/x86_64/

in the command line, with the creattrepo command, the group package configuration file will be updated under the/usr/local/www/CentOS/5/os/x 86_64 directory by specifying the metadata file/usr/local/www/CentOS/5/os/x 86_ 64/repada/mygroup.

In the embodiment of the invention, the packaged RPM packet is placed in a preset server.

Step 102, editing an installation package configuration file containing server address information, and configuring the installation package configuration file into intelligent terminal equipment to be initialized;

in this step, the server includes, but is not limited to, Yum server. The installation package configuration file may further include, but is not limited to, the following information: server domain name information, server uniform resource locator information, server IP address information, installation package storage address information, installation package type information, and the like.

103, installing a service on the server, directing the directory of the service to a storage path for storing an installation package, and starting the service;

in this step, as an optional embodiment, the service is configured to provide the installation package to the intelligent terminal device to be initialized. Installing hypertext transfer protocol daemon (HTTPD) service on the server, pointing a directory of the HTTPD service to an RPM packet storage path storing an RPM packet, and starting the HTTPD service.

In the embodiment of the invention, after the service is started, the intelligent terminal equipment can be monitored through the started service and the request of the intelligent terminal equipment is responded.

And 104, triggering the intelligent terminal equipment to be initialized to read the built-in installation package configuration file, and acquiring and installing the installation package from the service started by the server according to the read installation package configuration file.

In this step, the smart terminal device to be initialized edits the directory file mapped to the storage path of the RPM package, for example, the directory file may be set to/etc/yum. Thus, at installation time, the installation file is stored in the directory file on the intelligent terminal device to be initialized mapped by the RPM package storage path. The command lines to edit directory file/etc/yum.

[ADDOPS-base]

name＝ADDOPS-$releasever-Base

baseurl＝http://Yum-serverIP/addops/$releasever/os/$basearch/

gpgcheck＝0

In the embodiment of the invention, the installation package is obtained from the service started by the server according to the read configuration file of the installation package, so that the installation package can be installed according to the edited description file.

In the embodiment of the invention, dozens of intelligent terminal devices to be initialized can be started simultaneously, the installation package is acquired from the server through the built-in installation package configuration file after the intelligent terminal devices are started, and the installation package is packaged by the description file edited by the embodiment of the invention, so that the intelligent terminal devices can be automatically installed after the installation package is acquired, manual compiling of software packages is not needed, RPM package installation of the intelligent terminal devices to be initialized in a parallel mode is realized, and the efficiency and reliability of initialization are greatly improved.

As can be seen from the above description, the method for initializing an intelligent terminal device according to the embodiment of the present invention can save a large amount of resources in terms of time cost and labor cost by using the RPM package technology, the Yum application software warehouse management technology, and the Rsync technology in the initialization process. For example, in the embodiment of the present invention, only the application software source code needs to be copied to one Yum server for compiling and installing, and an installation package is generated, so that compared with the case where the application software source code is copied to each intelligent terminal device that needs to be initialized for compiling and installing, the time required is shorter, and the initialization update efficiency is higher. For example, for the situation that 1000 pieces of intelligent terminal equipment need to install a certain application software, only the time required for copying the source code of the application software is 1000 times that of the prior art in the embodiment of the present invention; furthermore, in the prior art, source codes need to be compiled and installed on each intelligent terminal device to be initialized, but in the embodiment of the present invention, only one Spec file needs to be compiled, an application software package is packaged into an RPM package by using an edited description file, and the intelligent terminal device to be initialized directly runs the yumgroupinstalsaltwarewandername. For example, for the situation that 1000 pieces of intelligent terminal equipment need to install a certain application software, the time cost required by the prior art on source code compiling installation is still 1000 times that of the embodiment of the present invention.

Fig. 2 shows an apparatus structure for initializing an intelligent terminal device according to an embodiment of the present invention. Referring to fig. 2, the apparatus includes: a packaging module, a testing module, an initialization communication module, wherein,

the packaging module is used for editing the description file for installing the application program software, packaging the application program software package into an RPM package by using the edited description file and outputting the RPM package to the testing module; receiving a test passing notice output by the test module, and outputting the RPM pack passing the test to the initialization communication module; receiving a test failure notice output by the test module, modifying the edited specification, repackaging the application program software package into an RPM package by utilizing the modified specification file, and outputting the RPM package to the test module;

in the embodiment of the present invention, the content in the Spec file comprises: a macro definition part for defining the macro name and the content of the macro name mapping; a preamble part for setting the name of the application software package, the name of a source code compression package corresponding to the application software, the information of the application software package depending on compilation and the information of the application software package depending on installation; a description section for brief introduction of the application software package and an installation flow section for setting an installation flow of the application software. Wherein, the installation flow part includes: preparing a phase script segment description, compiling a phase script segment description, installing a phase script segment description, cleaning a phase script segment description, and file list script segment description.

Preferably, the rpmbuild command is called to designate the application software package and the Spec file corresponding to the application software package, and the RPM package is generated by packaging and encapsulating the rpmbuild command.

As an optional embodiment, the packaging module is further configured to determine, according to a preset application scenario, that an RPM packet corresponding to the application scenario passes a test, combine the RPM packets corresponding to the application scenario, edit a package configuration file for the combined RPM packet, package the edited package configuration file and the combined RPM packet into an RPM package, and output the RPM package to the initialization communication module.

In the embodiment of the present invention, editing a package configuration file includes:

install yum-groups-manager commands; in each RPM packet, creating an index corresponding to the file in each RPM packet; and calling the package configuration command, and applying the created index to the called package configuration command to obtain a package configuration file.

The testing module is used for carrying out installation process testing on the received RPM packet, outputting a test failure notice to the packaging module if the RPM packet fails the installation process testing, and outputting a test passing notice to the packaging module if the RPM packet passes the installation process testing;

in the embodiment of the invention, the specific prompt message of failing the test can be carried in the test failure notification.

The initialization communication module is used for editing an installation package configuration file containing server address information, configuring the installation package configuration file to the intelligent terminal device to be initialized, installing the service for providing the installation package for the intelligent terminal device to be initialized, directing the directory of the service to a storage path for storing the installation package, starting the service, communicating with the intelligent terminal device to be initialized, and outputting the installation package to the intelligent terminal device to be initialized for installation.

In the embodiment of the invention, as an optional embodiment, the http d service is started by installing the hypertext transfer protocol daemon service on the initialization communication module and pointing the directory of the http d service to the RPM packet storage path storing the RPM packet, so that communication support can be provided.

It should be noted that the modules in the apparatus may be implemented by independent physical devices, which are described below.

Fig. 3 shows a system structure for initializing the intelligent terminal device according to the embodiment of the present invention. Referring to fig. 3, the system includes: RPM baling press, RPM package test machine, Yum server and wait to initialize intelligent terminal equipment, wherein, RPM baling press, RPM package test machine, Yum server constitute the device that fig. 2 shows.

The RPM packer is used for editing the description file for installing the application program software, packaging the application program software package into an RPM package by using the edited description file and outputting the RPM package to the RPM package tester; receiving a test passing notice output by the RPM packet tester, and outputting the RPM packet passing the test to the YUm server; receiving a test failure notice output by the RPM packet testing machine, modifying the edited specification, repackaging the application program software packet into an RPM packet by using the modified specification file, and outputting the repackaged RPM packet to the RPM packet testing machine;

in an embodiment of the present invention, an RPM baler comprises: a community enterprise operating system (centros) 5RPM baler and a centros 6RPM baler.

As an optional embodiment, the RPM packing machine is further configured to confirm that the RPM package corresponding to the application scenario passes the test according to a preset application scenario, combine the RPM package corresponding to the application scenario, edit a package configuration file for the combined RPM package, package the edited package configuration file and the combined RPM package into an RPM package, and output the RPM package to the Yum server.

In the embodiment of the invention, by utilizing an Rsync automatic synchronization technology, an RPM packer transmits an RPM group packet (a plurality of RPM packets and a corresponding generated YUMgoup configuration file) obtained after the group management to a YUM server.

The RPM pack testing machine is used for carrying out installation process testing on the received RPM pack, outputting a test failure notice to the RPM packer if the installation process testing fails, and outputting a test passing notice to the RPM packer if the installation process testing passes;

in the embodiment of the invention, the Rsync automatic synchronization technology is utilized to transmit the RPM packet generated by packaging to the RPM packet testing machine for carrying out the installation process test, so that the RPM packet generated by packaging passes the installation process test, and the reliability and the efficiency of initializing the intelligent terminal equipment are improved. If there is a problem in the installation of the RPM packer, the RPM packer can be informed to modify the Spec file on the RPM packer according to the prompt information, and then the RPM packer outputs the modified RPM packer to the RPM packer tester again for the installation flow test until the test is passed.

Corresponding to the CentOS5RPM packer, the RPM pack is transmitted to a CentOS5RPM pack tester for testing; corresponding to the CentOS6RPM baler, the RPM bale was transferred to the CentOS6RPM bale tester for testing. That is, corresponding to an RPM baling machine, an RPM bale testing machine includes: a CentOS5RPM pack tester and a CentOS6RPM pack tester. After no problem is tested, the RPM bale tester informs the RPM balers, and the CentOS5RPM balers and the CentOS6RPM balers perform grouping management corresponding to the RPM bales passing the test.

The YUM server is used for editing an installation package configuration file containing server address information, configuring the installation package configuration file to the intelligent terminal equipment to be initialized, installing the service for providing the installation package for the intelligent terminal equipment to be initialized, directing the directory of the service to a storage path for storing the installation package, starting the service, communicating with the intelligent terminal equipment to be initialized, and outputting the installation package to the intelligent terminal equipment to be initialized for installation;

in the embodiment of the invention, the Yum server is a CentOS5Yum server (server) corresponding to a CentOS5RPM packer; corresponding to a CentOS6RPM baler, the Yum server is a CentOS6 yummer. Namely, the Yum server includes: CentOS5YumServer and CentOS6 YumServer.

In the embodiment of the present invention, the intelligent terminal device to be initialized includes: a CentOS5 client and a CentOS6 client. As an alternative embodiment, on the CentOS5 client and the CentOS6 client, the automatic initialization process is performed by communicating with the CentOS5 yummer and the CentOS6 yummer, respectively, through hypertext transfer protocol (HTTP) protocol.

As an alternative embodiment, the number of CentOS5 clients is one or more, and the number of CentOS6 clients is one or more.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components of the apparatus and system for initializing a smart terminal device according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet web server or provided on a carrier signal or in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

The invention discloses A1. a method for initializing intelligent terminal equipment, which comprises the following steps:

A2. The method of a1, the specification file comprising: a preamble section and an installation flow section, wherein,

A3. According to the method as described in a2, the description file further includes a macro definition part for defining the macro name and the content of the macro name mapping, and/or a description part for describing the brief introduction of the application software package.

A4. The method of a2, the installation flow portion comprising: preparing a phase script segment description, compiling a phase script segment description, installing a phase script segment description, cleaning a phase script segment description, and file list script segment description.

A5. The method of a4, the installation flow portion further comprising: installing a post-stage script segment description, and/or uninstalling a pre-stage script segment description, and/or uninstalling a post-stage script segment description, and/or a log script segment description.

A6. The method of A4 or A5, the preparation phase script segment description comprising:

A7. The method of a1, wherein packaging the application package into an installation package using the edited description file comprises:

A8. The method of a1, after the generating an installation package, the method further comprising:

A9. The method of A8, the method further comprising:

A10. The method of a9, the editing the package group configuration file comprising:

install yum-groups-manager commands;

A11. According to the method of a9, the package configuration file is in an extensible markup language format.

A12. According to the method of a1, the obtaining an installation package from a server-started service according to the read installation package configuration file includes:

A13. An apparatus for initializing a smart terminal device, the apparatus comprising: a packaging module, a testing module, and an initialization communication module, wherein,

A14. According to the apparatus described in a13, the packaging module is further configured to confirm that the installation package corresponding to the application scenario passes the test according to the preset application scenario, combine the installation packages corresponding to the application scenario, edit a package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into the installation package, and output the installation package to the initialization communication module.

A15. The apparatus of A13 or A14, the specification file comprising: a macro definition part for defining the macro name and the content of the macro name mapping; a preamble part for setting the application software package name and the source code compressed package name corresponding to the application software, the application software package information depending on compiling, and the application software package information depending on installing; a description section for brief introduction of the application software package and an installation flow section for setting an installation flow of the application software.

A16. A system for initializing a smart terminal device, the system comprising: installing a packaging machine, installing a packaging tester, a server and intelligent terminal equipment to be initialized, wherein,

A17. According to the system described in a16, the installation packaging machine is further configured to confirm that the installation package corresponding to the application scenario passes the test according to the preset application scenario, combine the installation packages corresponding to the application scenario, edit a package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into an installation package, and output the installation package to the server.

A18. According to the system as described in a16, the installation package generated by packaging is transmitted to an installation package tester by using a remote mirror image automatic synchronization technology.

A19. The system of a16, the installation baler comprising: community enterprise operating system 5 installs the baling press and community enterprise operating system 6 installs the baling press.

Claims

1. A method for initializing a smart terminal device, comprising:

2. The method of claim 1, the specification file comprising: a preamble section and an installation flow section, wherein,

3. The method of claim 2, wherein the description file further comprises a macro definition part for defining the macro name and the content of the macro name mapping, and/or a description part for describing a brief introduction of the application software package.

4. The method of claim 2, the installation flow portion comprising: preparing a phase script segment description, compiling a phase script segment description, installing a phase script segment description, cleaning a phase script segment description, and file list script segment description.

5. The method of claim 4, the installation flow portion further comprising: installing a post-stage script segment description, and/or uninstalling a pre-stage script segment description, and/or uninstalling a post-stage script segment description, and/or a log script segment description.

6. The method of claim 4 or 5, the preparing phase script segment description comprising:

7. An apparatus for initializing a smart terminal device, the apparatus comprising: a packaging module, a testing module, and an initialization communication module, wherein,

8. The apparatus of claim 7, wherein the packaging module is further configured to, according to a preset application scenario, confirm that an installation package corresponding to the application scenario passes a test, combine the installation packages corresponding to the application scenario, edit a package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into an installation package, and output the installation package to the initialization communication module.

9. A system for initializing a smart terminal device, the system comprising: installing a packaging machine, installing a packaging tester, a server and intelligent terminal equipment to be initialized, wherein,

10. The system of claim 9, wherein the installation packaging machine is further configured to confirm that the installation package corresponding to the application scenario passes the test according to the preset application scenario, combine the installation packages corresponding to the application scenario, edit the package configuration file for the combined installation package, package the edited package configuration file and the combined installation package into the installation package, and output the installation package to the server.