WO2016000623A1 - 初始化智能终端设备的方法、装置及系统 - Google Patents
初始化智能终端设备的方法、装置及系统 Download PDFInfo
- Publication number
- WO2016000623A1 WO2016000623A1 PCT/CN2015/083102 CN2015083102W WO2016000623A1 WO 2016000623 A1 WO2016000623 A1 WO 2016000623A1 CN 2015083102 W CN2015083102 W CN 2015083102W WO 2016000623 A1 WO2016000623 A1 WO 2016000623A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- package
- installation
- terminal device
- test
- installation package
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
Definitions
- the present invention relates to computer initialization techniques, and in particular, to a method, device and system for initializing an intelligent terminal device.
- smart terminal devices such as videophones, conference terminals, mobile phones, personal computers with built-in multimedia functions, personal digital assistants, and servers, are becoming more and more widely used.
- the number is also increasing.
- the environment initialization of the smart terminal device is required, that is, the parameter initialization configuration of the smart terminal device and the installation of the application software are performed, so that the user can be based on the intelligent terminal after initialization.
- the corresponding service is used on the device, and the initialization of the smart terminal device mainly includes:
- Intelligent terminal device parameter initialization configuration including: disk partition initialization configuration, time server initialization configuration, domain name server initialization configuration, system parameter initialization configuration, application software repository source initialization configuration, and host name correction configuration.
- the corresponding operating system is installed, and other application software (the operating system is one of the application software) is installed based on the installed operating system, and 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.
- Lnmp Lox, Nginx, Mysql, Php
- Lamp Liux, Apache, MySQL, Perl/PHP/Python
- Memcached Redis, Mongodb, Varnish, Haproxy.
- Step one install Nginx, including:
- the Nginx package is: tar-xzvf nginx-version.tar.gz;
- install Php including:
- the Php package is: tar-xzvf php-version.tar.gz;
- the Mysql package is: tar-xzvf php-version.tar.gz;
- Step 1 Step 2 and Step 3 are not in sequence.
- the installation process some manual compilation and configuration operations are involved.
- the server is completed. Compile and install the Lnmp process.
- the method for initializing the smart terminal device by means of the manual compilation of the software package requires an installer to perform some manual compilation and configuration operations for each intelligent terminal device, and some configuration operations are simple repetitions.
- the configuration operation makes the time required for initializing the cluster intelligent terminal device long and the initialization efficiency is low.
- each intelligent terminal device needs to be initialized for a corresponding time, and thus, the total initialization time is long;
- the intelligent terminal device has a wide coverage, for example, needs to be targeted Different application scenarios are initialized separately; again, during the process of installing the application package, manual compilation and other operations are required, which makes the installation time long; and, the installation process needs to be monitored to prevent problems in the application software installation.
- the security of each smart terminal device The installation process is repetitive, allowing the installer to take a long time to complete the installation.
- the present invention has been made in order to provide a method, apparatus and system for initializing a smart terminal device that overcomes the above problems or at least partially solves the above problems.
- a method of initializing a smart terminal device comprising:
- the smart terminal device to be initialized is triggered to read the built-in installation package configuration file, and obtains the installation package from the server-initiated service according to the read installation package configuration file and installs it.
- an apparatus for initializing a smart terminal device comprising: a packaging module, a testing module, and an initialization communication module, wherein
- the test module is configured to perform an installation process test on the received installation package. If the installation process test is not passed, the test fails to pass the notification to the packaging module, and if the installation process is tested, the test pass notification is output to the packaging module;
- Initializing a communication module configured to edit an installation package configuration file including server address information, and configured to be to be initialized to the smart terminal device, and configured to provide the smart terminal device to be initialized And installing the service of the package, and pointing the directory of the service to a storage path for storing the installation package, starting the service, and communicating with the intelligent terminal device to be initialized, to output the installation package to the intelligent terminal device to be initialized for installation .
- a system for initializing a smart terminal device comprising: an installation package packager, an installation package test machine, a server, and a smart terminal device to be initialized, wherein
- Install package packer edit the installation software application documentation and use the edited documentation to package the application package as an installation package, output to the installation package test machine; receive the test package test machine output test notification, will The tested installation package is output to the server; the test that receives the output of the installation package tester fails the notification, modifies the edited manual, and repackages the application package as an RPM package with the modified description file, and the package will be repackaged. Output to the installation package test machine;
- the installation package test machine is used to perform the installation process test on the received installation package. If the installation process test is not passed, the test fails to pass the test to the installation packager, and if the installation process test passes, the test pass notification is output to the installation packager;
- a server configured to edit an installation package configuration file including server address information, and configured to the smart terminal device to be initialized, install a service for providing the installation package to the intelligent terminal device to be initialized, and point the directory of the service to the storage a storage path of the installation package, starting the service, and communicating with the intelligent terminal device to be initialized, to output the installation package to the intelligent terminal device to be initialized for installation;
- the smart terminal device to be initialized is used to read the built-in installation package configuration file, and obtain the installation package from the server-initiated service according to the read installation package configuration file and install it.
- a program comprising readable code, when the readable code is run on a terminal device, causing the terminal device to perform the method of initializing the smart terminal device.
- a readable medium wherein the program is stored.
- the application package is packaged by using the edited description file by pre-editing the description file of the installation application software.
- the RPM package, and the installation package configuration file including the server address information is preset in the intelligent terminal device to be initialized, and the intelligent terminal device to be initialized obtains the installation package from the server through the built-in installation package configuration file after startup, and the installation package is adopted.
- the description file edited by the embodiment of the present invention is encapsulated, so that the smart terminal device can automatically install after acquiring the installation package, thereby solving the technical problem of initializing the waste of labor and material resources of the smart terminal device, especially the initialization required.
- the beneficial effects of reducing the time required for initializing the smart terminal device and improving the initialization efficiency are obtained.
- FIG. 1 is a flowchart of a method 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
- FIG. 3 is a diagram showing a system structure for initializing an intelligent terminal device according to an embodiment of the present invention
- Figure 4 shows a block diagram of a server configured to perform the method according to the invention
- Figure 5 shows a memory unit configured to hold or carry program code implementing a method in accordance with the present invention.
- the method for manually initializing the environment of the smart terminal device by using the software package is manually compiled.
- the installer needs to perform some manual configuration operations, and some configuration operations are simple repeated configuration operations, so that the smart to be initialized
- the number of terminal devices is large, the time required for initialization is long and the initialization efficiency is low.
- the Yellow Dog UpdaterModified server is a desktop operating system (Fedora) and Red Hat (Red Hat) and Software and System Development (SUSE), Community Enterprise Operating System (CentOS, Community Enterprise Operating).
- the Shell front-end package manager in System based on Red Hat Software Management Tool (RPM, RedHat Package Manager), enables the intelligent terminal device after initialization to automatically download RPM packages from the specified server for application installation and update. And can automatically handle the application's dependencies, to achieve a package of all the applications installed once, without having to tediously download and install again and again.
- the RPM package available for Yum download is maintained by the Linux community, including the application package provided by Fedora itself and the Fedora Extras application package from Red Hat Software Management Toolkit (RPMfusion) and RPM.
- RPMfusion Red Hat Software Management Toolkit
- Yum server can use Yum technology to install a single application software and the dependencies of the application software. You can also use the Yum group technology to install the application software installation package.
- the software installation package includes multiple application software and corresponding dependencies of multiple application software.
- the Yum server involves the following technologies:
- RPM packet technology is used to personalize the native version of the application software, so that the personalized application software (RPM package) can be applied to different application scenarios to save application software compilation and installation. , the time required for debugging, reducing labor costs.
- the server (Yum server) stores the RPM package or the RPM group package generated by the RPM packet technology, and after the client after the initialization is established with the network connection, the server can automatically download and download from the server. Install RPM packages or RPM packages to achieve efficient and reliable application software installation.
- the Yum technology and the Yum group technology are applied to initialize the smart terminal device.
- the RPM packet technology, the Rsync technology, and the Yum application software warehouse management technology are comprehensively utilized to solve the cumbersome redundant steps of the prior art in the initialization process.
- FIG. 1 is a flowchart of a method for initializing an intelligent terminal device according to an embodiment of the present invention. Referring to Figure 1, the process includes:
- Step 101 Edit an instruction file for installing application software, and package the application software package into an installation package by using the edited description file and store it in the server;
- the installation package includes but is not limited to the RPM package.
- the RPM package generated by the application package can be encapsulated with the edited description file, and can be automatically installed according to the written installation process.
- Each application software corresponds to a description file.
- the Spec file is a specification for making an RPM package, and the Spec file includes: a macro definition part, a preamble part, a description part, and an installation process part. among them,
- the macro definition part is used to define the macro name and the content of the macro name mapping.
- the macro is similar to the variable when programming. If the macro name is referenced in subsequent applications, it will be expanded to the content of the reference macro name mapping.
- the macro definition part is an optional item.
- the preface is used to set the application package name, the source code compression package name corresponding to the application software, the application package information that is dependent on the compilation, and the application package information that is dependent on the installation.
- the application package information that is dependent on compile time, and the application package information that is dependent on the installation are optional, and depending on whether the application software is compiled and installed, it depends on other applications.
- the program package is determined.
- the preamble may also include: a version number, a release number, and the like.
- the description part is optional.
- Installation process section Used to set up the installation process of the application software, including the following script segment description:
- Preparation phase including:
- step A11 in the foreword part of the query description file, whether the application software to be installed needs to rely on other application software, if yes, install the other application software that depends on, step A12 is performed, otherwise, step A12 is directly executed;
- the application software to be installed needs to rely on other application software, for example, when installing the application software A, the application software B needs to be installed first, then in the preparation stage, the application software B is installed first. .
- A12 extract the source code compression package corresponding to the source code compression package name in the preamble to a preset compilation directory.
- the pre-configured compilation directory can be set by the above macro definition, for example, decompressed into the BUILD directory, and used to prepare for the next compilation stage.
- the source code compression package corresponding to the source code compression package name is set in the application software package.
- Installation phase (%install): The installation phase is to install the compiled binary application file, application configuration file, service script file, etc. into a preset virtual root directory for temporary storage.
- the virtual root directory is the root directory of the host (to be initialized smart terminal device) on which the RPM package is subsequently installed.
- the virtual root directory may be represented by a macro "buildroot”.
- Cleanup phase After the installation is complete, delete the virtual root directory set in the installation phase.
- File list (%file): The file list is the core part of the Spec file. Only the files listed in the file list will be encapsulated into the RPM package. Among them, the files in the file list are the files necessary to install the application software.
- the application software may be personalized, and the Spec file may further include:
- Post-installation phase Used to personalize the installed application software.
- a change log script segment may also be set in the installation process section to describe the update log of the application software.
- the program code segments corresponding to the preparation phase, the compilation phase, the installation phase, the cleanup phase, the file list, and the post-installation phase can be written to the corresponding paragraphs in the shell program.
- encapsulating the edited description file and the application package into an RPM package includes:
- the RPM package can be generated by the rpmbuild-bb ⁇ specfile> command line.
- the -bb parameter means that the RPM package is generated only according to the specfile.
- the application software package is sequentially encapsulated according to the macro definition part, the preamble part, the description part, and the installation process part included in the edited description file to generate an RPM package.
- the method may further include:
- the test is to automatically install the RPM package by using rsync. If there is a problem in the RPM package installation, the Spec file is modified according to the displayed prompt information, and then, The application package is packaged according to the modified Spec file, and the RPM package is generated, and then the installation process is tested until the installation process test passes. Thereby, the error probability of the initialization process is reduced, the success rate and reliability of the intelligent terminal device initialization are improved, and the efficiency of initializing the smart terminal device is improved.
- the method may further include:
- the generated RPM packages are combined, and the package configuration file is edited for the combined RPM package, and the edited package configuration file and the combined RPM package are encapsulated into RPM group packages.
- the RPM package tested through the installation process may be grouped and managed according to different application scenario requirements, that is, according to different application scenario requirements.
- the RPM packets are combined to implement the setting of the application scenario by one initialization, which effectively reduces user operations and reduces the time required for initialization.
- the index path of the packet metadata is saved, and the included RPM packet information is performed.
- the configuration may also edit the group configuration file corresponding to the combined RPM package according to the RPM package obtained by the group management, and each combined RPM package corresponds to a group configuration file.
- editing the package configuration file includes:
- the command behavior of the yum-groups-manager command is installed: yum install yum-utils.norch.
- the yum-groups-manager command is used to trigger the execution of subsequent processes.
- each RPM package create an index corresponding to the file in each RPM package.
- This step is an optional step.
- the command behavior for creating an index createrepo-d--update path.
- the "-d" parameter is a required parameter, and path is an index path.
- the group package configuration command is invoked, and the created index is applied to the called group package configuration command to obtain a group package configuration file.
- the package configuration command is as follows:
- -n parameter specify the group name of the group
- --id parameter Generate a unique identifier for the group package
- --save parameter save the package metadata to the file in the preset index path
- --mandatory parameter Specifies one or more RPM packages contained in the package.
- the package configuration file format may be in an Extensible Markup Language (XML) format.
- XML Extensible Markup Language
- the yum-groups-manager command is used to generate a group named "LNMP-2.2.20-5.2.5".
- the unique identifier of the group is LNMP, which is described as "1.2. 9 version of the nginx program, version 5.2.5 of the php program, version 5.5 of the mysql program", LNMP-2.2.20-5.2.5 group of metadata stored in /usr/local/www/CentOS/5/os
- the RPM package included in this group includes Qihoo-App-nginx, Qihoo-app-php, and Qihoo-App-mysql.
- the method may further include:
- the package configuration file corresponding to the combined RPM package is updated.
- the update includes: delete, modify, increase, and the like.
- Update the command behavior of the package configuration file createrepo--verbose-g path/repodata/*.xml path.
- the newly added RPM package can be searched by the smart terminal device.
- command line for updating the package configuration file is as follows:
- the packaged RPM package is placed in a preset server.
- Step 102 Edit an installation package configuration file that includes server address information, and configure the configuration file to be initialized to the smart terminal device.
- the server includes but is not limited to a 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.
- Step 103 Install a service on the server, and point the directory of the service to a storage path where the installation package is stored, and start a service;
- the service is used to provide the installation package to the to-be-initialized smart terminal device.
- the hypertext transfer protocol daemon (HTTPD) service is installed on the server, and the HTTPD service directory is pointed to the RPM package storage path where the RPM package is stored, and the HTTPD service is started.
- HTTPD hypertext transfer protocol daemon
- the smart terminal device may be monitored by the activated service and responded to the request of the smart terminal device.
- Step 104 The smart terminal device to be initialized is triggered to read the built-in installation package configuration file, and the installation package is obtained from the server-initiated service according to the read installation package configuration file and is installed.
- the intelligent terminal device to be initialized edits the directory file of the RPM package storage path mapping,
- the catalog file can be set to /etc/Yum.repos.d/CentOS.repo.
- the installation file is stored in the directory file on the intelligent terminal device to be initialized mapped in the RPM package storage path.
- the command line for editing the directory file /etc/Yum.repos.d/CentOS.repo is as follows:
- the installation package is obtained from the server-initiated service according to the read installation package configuration file, so that the installation package can be installed according to the edited description file.
- dozens of intelligent terminal devices to be initialized can be simultaneously turned on, and the installation package is obtained from the server through the built-in installation package configuration file after startup, and the installation package is performed by using the description file edited by the embodiment of the present invention.
- the encapsulation enables the intelligent terminal device to automatically install after obtaining the installation package, without manual compilation of the software package, and implementing RPM package installation on multiple intelligent terminal devices to be initialized in parallel, thereby greatly improving the efficiency and reliability of the initialization. Sex.
- the method for initializing the smart terminal device in the embodiment of the present invention can save a large amount of resources in time cost and labor cost by utilizing the RPM packet technology, the Yum application software warehouse management technology, and the Rsync technology in the initialization process.
- the application software source code is copied to a Yum server for compilation and installation, and an installation package is generated, and the application software source code is copied to each intelligent terminal device that needs to be initialized. Compiling and installing takes less time and is more efficient to initialize and update.
- the installation source code needs to be compiled on each of the to-be-initialized smart terminal devices.
- the application package is encapsulated into an RPM package by using the edited description file.
- the terminal device can be directly run by running Yumgroupinstallsoftwarename. For example, for 1000 smart terminal devices that need to install an application software, the time required for the prior art to compile and install the source code. The cost is still 1000 times that of the embodiment of the present invention.
- FIG. 2 shows a device structure for initializing an intelligent terminal device according to an embodiment of the present invention.
- the device includes: a packaging module, a testing module, and an initialization communication module, where
- the packaging module is used to edit the description file of the installation application software, and the application package is encapsulated into an RPM package by the edited description file, and output to the test module; the test output of the test module is notified, and the RPM package passed through the test is output to Initializing the communication module; receiving the test output of the test module fails to notify, modifying the edited manual, and re-packaging the application software package into an RPM package by using the modified description file, and outputting to the test module;
- the content in the Spec file includes: a macro definition part for defining a macro name and a content of the macro name mapping; and a source code compression package name corresponding to the application software package name, the application software, and the compilation
- the application package information that depends on it, the preface of the application package information that is dependent on the installation; the description section for a brief introduction to the application package and the installation process section for setting up the installation process for the application software.
- the installation process includes: a preparation stage script segment description, a compilation stage script segment description, an installation phase script segment description, a cleanup phase script segment description, and a file list script segment description.
- the application software package and the Spec file corresponding to the application software package are specified, packaged and packaged, and an RPM package is generated.
- the packaging module is further configured to: according to the preset application scenario, confirm that the RPM package corresponding to the application scenario passes the test, combine the RPM packages corresponding to the application scenario, and edit the group configuration file for the combined RPM package.
- the edited package configuration file and the combined RPM package are encapsulated into RPM group packages, and output to the initialization communication module.
- the editing group package configuration file includes:
- the test module is configured to perform an installation process test on the received RPM package. If the installation process test is not passed, the test fails to pass the notification to the packaging module, and if the installation process is tested, the test pass notification is output to the packaging module;
- the specific prompt information that fails the test may be carried in the test failure notification.
- the HTTPD service is started, thereby providing Communication support.
- each module in the device can be implemented by independent physical devices, which will be described below.
- FIG. 3 shows a system structure for initializing a smart terminal device according to an embodiment of the present invention.
- the system includes: an RPM packager, an RPM package tester, a Yum server, and a smart terminal device to be initialized, wherein the RPM packager, the RPM package tester, and the Yum server constitute the device shown in FIG.
- RPM packager used to edit the installation software application documentation and use the edited documentation to package the application package into an RPM package and output it to the RPM package test machine; the test that receives the RPM package test machine output will pass the notification.
- the tested RPM package is output to the Yum server; the test that receives the RPM packet tester output fails the notification, modifies the edited manual, and repackages the application package as an RPM package with the modified description file, and the repackaged RPM package Output to the RPM package test machine;
- the RPM packager includes: a community enterprise operating system (CentOS, Community Enterprise Operating System) 5RPM packager and a CentOS6 RPM packager.
- Community enterprise operating system Compute resource pool
- CentOS6 RPM packager CentOS6 RPM packager
- the RPM packetizer is further configured to: according to the preset application scenario, confirm that the RPM packet corresponding to the application scenario passes the test, combine the RPM packets corresponding to the application scenario, and configure the group package for the combined RPM package.
- File, edited package configuration file with combined RPM The package is packaged as an RPM group package and output to the Yum server.
- the RPM automatic synchronization technology is used, and the RPM packetizer transmits the RPM group package (the plurality of RPM packages and the corresponding generated Yum group configuration file) obtained after the group management to the Yum server.
- the RPM package testing machine is used to perform the installation process test on the received RPM package. If the installation process test is not passed, the RPM packager outputs a test failure notification. If the installation process is tested, the RPM packager outputs a test notification notification;
- the Rsync automatic synchronization technology is used to transmit the RPM package generated by the package to the RPM package test machine for the installation process test, so that the RPM package generated by the package is tested through the installation process, thereby improving the reliability of the initialization intelligent terminal device. And efficiency. If there is a problem in the RPM package installation, the RPM packager can be notified to modify the Spec file on the RPM baler according to the prompt information, and then the RPM packer outputs the modified RPM package to the RPM package test machine for installation process test. Until the test passes.
- the RPM package is transmitted to the CentOS5 RPM package test machine for testing; corresponding to the CentOS6 RPM packager, the RPM package is transmitted to the CentOS6 RPM package test machine for testing. That is, corresponding to the RPM baler, the RPM package tester includes: CentOS5 RPM package test machine and CentOS6 RPM package test machine. After the test is no problem, the RPM package test machine notifies the RPM packer that the CentOS5 RPM packer and the CentOS6 RPM packer will be grouped and managed corresponding to the tested RPM package.
- a Yum server for editing an installation package configuration file including server address information, and configuring the smart terminal device to be initialized, installing a service for providing the installation package to the smart terminal device to be initialized, and installing the service
- the directory points to a storage path for storing the installation package, starts the service, and communicates with the intelligent terminal device to be initialized, so as to output the installation package to the intelligent terminal device to be initialized for installation;
- the Yum server is a CentOS5 Yum server (server); corresponding to the CentOS6 RPM packager, and the Yum server is a CentOS6Yum server. That is, the Yum server includes: CentOS5 Yum server and CentOS6Yum server.
- the smart terminal device to be initialized is used to read the built-in installation package configuration file, according to the read Install the package configuration file, get the installation package from the server-initiated service, and install it.
- the smart terminal device to be initialized includes: a CentOS5 client and a CentOS6 client.
- the CentOS5 client and the CentOS6 client communicate with the CentOS5 Yum server and the CentOS6Yum server respectively through the Hypertext Transfer Protocol (HTTP) protocol to perform an automatic initialization process.
- HTTP Hypertext Transfer Protocol
- the number of CentOS5 clients is one or more, and the number of CentOS6 clients is one or more.
- modules in the devices of the embodiments can be adaptively changed and placed 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 further they may be divided into a plurality of sub-modules or sub-units or sub-components.
- any combination of the instructions including companion All of the features disclosed in the claims, the abstract and the drawings, and all processes or units of any of the methods or devices disclosed herein are combined.
- Each feature disclosed in this specification including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.
- the various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof.
- a microprocessor or digital signal processor may be used in practice to implement some or all of some or all of the components of the apparatus and system for initializing a smart terminal device in accordance with an embodiment of the present invention.
- the invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein.
- a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals.
- Such signals may be downloaded from an Internet website server, provided on a carrier signal, or provided in any other form.
- FIG. 4 shows a terminal device that can implement the method of initializing a smart terminal device according to the present invention.
- the terminal device conventionally includes a processor 410 and a program product or readable medium in the form of a memory 420.
- Memory 420 can be an electronic memory such as a flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, or ROM.
- Memory 420 has a memory space 430 of program code 431 configured to perform any of the method steps described above.
- storage space 430 configured as program code can include various program code 431 that are each configured to implement various steps in the above methods.
- These program codes can be read from or written to one or more program products.
- These program products include program code carriers such as memory cards.
- Such a program product is typically a portable or fixed storage unit as described with reference to FIG.
- the storage unit may have a storage section, a storage space, and the like arranged similarly to the storage 420 in the terminal device of FIG.
- the program code can be compressed, for example, in an appropriate form.
- the storage unit includes readable code 431', i.e., code that can be read by a processor such as 410, which The code, when run by the terminal device, causes the terminal device to perform the various steps in the methods described above.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
一种初始化智能终端设备的方法、装置及系统。该方法包括:编辑用于安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包并存储在服务器中(101);编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备(102);在所述服务器上安装用于向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务(103);触发待初始化智能终端设备读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装(104)。
Description
本发明涉及计算机初始化技术,具体涉及一种初始化智能终端设备的方法、装置及系统。
随着计算机通信技术以及互联网技术的发展,智能终端设备,例如,可视电话机、会议终端机、移动电话、内置多媒体功能的个人计算机、个人数字助理、服务器的应用越来越广泛,应用的数量也越来越多。在智能终端设备上架后至交付给业务应用使用前,需要对智能终端设备进行环境的初始化,即对智能终端设备进行参数初始化配置以及安装应用程序软件,以使用户能够在基于初始化后的智能终端设备上使用相应的业务,初始化智能终端设备主要包括:
1)智能终端设备参数初始化配置,包括:磁盘分区初始化配置、时间服务器初始化配置、域名服务器初始化配置、系统参数初始化配置、应用程序软件仓库源初始化配置以及主机名校正配置等。
2)应用程序软件安装。根据不同智能终端设备的用途,安装相应的操作系统,基于安装的操作系统,进行其他应用程序软件(操作系统为应用程序软件的一种)安装,应用程序软件包括但不限于:Lnmp(Linux、Nginx、Mysql、Php)、Lamp(Linux、Apache、MySQL、Perl/PHP/Python)、Memcached、Redis、Mongodb、Varnish、Haproxy。
以对一台4CPU、8G随机存储器(RAM,RandomAccessMemory)的服务器进行初始化,即在服务器上编译安装Lnmp为例,包括如下步骤一、步骤二以及步骤三:
步骤一,安装Nginx,包括:
a,解压Nginx软件包,该Nginx软件包为:tar-xzvf nginx-version.tar.gz;
b,对解压的Nginx软件包进行手工编译(具体参数不对外公布):./configure;make-j4;
c,安装编译的Nginx软件包:make install。
二,安装Php,包括:
a,解压Php软件包,该Php软件包为:tar-xzvf php-version.tar.gz;
b,手工编译解压的Php软件包(具体参数不对外公布):./configure;make-j4;
c,安装编译的Php软件包:make install。
三,安装Mysql,包括:
a,解压Mysql软件包,该Mysql软件包为:tar-xzvf php-version.tar.gz;
b,手工编译解压的Mysql软件包(具体参数不对外公布):./configure;make-j4;
c,安装编译的Mysql软件包:make install。
所应说明的是,步骤一、步骤二以及步骤三并没有先后顺序之分,其中,在安装过程中,需要涉及一些手动编译、配置的操作流程,完成上述三个步骤之后,完成在服务器上编译安装Lnmp的流程。
由上述可见,现有通过软件包手工编译的方式对智能终端设备进行初始化的方法,对于每一智能终端设备,需要安装人员进行一些手动编译、配置的操作流程,且一些配置操作为简单的重复配置操作,使得进行集群智能终端设备初始化所需的时间长、初始化效率低。具体来说,首先,当需要初始化的智能终端设备数量多,初始化每一智能终端设备都需要相应的时间,因而,总的初始化时间长;其次,智能终端设备初始化涵盖面广,例如,需要针对不同的应用场景,分别进行初始化;再次,在安装应用程序软件包的过程中,需要进行手动编译等操作,使得安装时间长;而且,需要监测安装流程,以防止在应用程序软件安装中出现问题;最后,每一智能终端设备的安
装流程都是重复性的,使得安装人员完成安装所需的时间长。
发明内容
鉴于上述问题,提出了本发明以便提供一种克服上述问题或者至少部分地解决上述问题的初始化智能终端设备的方法、装置及系统。
依据本发明的一个方面,提供了初始化智能终端设备的方法,该方法包括:
编辑用于安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包并存储在服务器中;
编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备;
在所述服务器上安装用于向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务;
触发待初始化智能终端设备读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
根据本发明的另一个方面提供了一种初始化智能终端设备的装置,该装置包括:打包模块、测试模块以及初始化通信模块,其中,
打包模块,用于编辑安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包,输出至测试模块;接收测试模块输出的测试通过通知,将通过测试的安装包输出至初始化通信模块;接收测试模块输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,输出至测试模块;
测试模块,用于对接收的安装包进行安装流程测试,如果未通过安装流程测试,向打包模块输出测试未通过通知,如果通过安装流程测试,向打包模块输出测试通过通知;
初始化通信模块,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装用于向所述待初始化智能终端设备提供
所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装。
根据本发明的再一个方面提供了一种初始化智能终端设备的系统,该系统包括:安装包打包机、安装包测试机、服务器以及待初始化智能终端设备,其中,
安装包打包机,用于编辑安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包,输出至安装包测试机;接收安装包测试机输出的测试通过通知,将通过测试的安装包输出至服务器;接收安装包测试机输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,将重新封装的安装包输出至安装包测试机;
安装包测试机,用于对接收的安装包进行安装流程测试,如果未通过安装流程测试,向安装打包机输出测试未通过通知,如果通过安装流程测试,向安装打包机输出测试通过通知;
服务器,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装;
待初始化智能终端设备,用于读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
根据本发明的另一个方面提供了一种程序,包括可读代码,当所述可读代码在终端设备上运行时,导致所述终端设备执行所述的初始化智能终端设备的方法。
根据本发明的另一个方面提供了一种可读介质,其中存储了所述的程序。
根据本发明的初始化智能终端设备的方法、装置及系统,通过预先编辑安装应用程序软件的说明文件,利用编辑的说明文件封装应用程序软件包为
RPM包,并在待初始化智能终端设备中预置包含服务器地址信息的安装包配置文件,待初始化智能终端设备在启动后通过内置的安装包配置文件从服务器中获取安装包,而由于安装包采用本发明实施例编辑的说明文件进行封装,使得智能终端设备在获取安装包后,可以自动进行安装,由此解决了初始化智能终端设备在人力、物力上成本浪费的技术问题,尤其是需要初始化的智能终端数量较多时,取得了减少初始化智能终端设备所需的时间、提升初始化效率的有益效果。
上述说明仅是本发明技术方案的概述,为了能够更清楚了解本发明的技术手段,而可依照说明书的内容予以实施,并且为了让本发明的上述和其它目的、特征和优点能够更明显易懂,以下特举本发明的具体实施方式。
通过阅读下文优选实施方式的详细描述,各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的,而并不认为是对本发明的限制。而且在整个附图中,用相同的参考符号表示相同的部件。在附图中:
图1示出了本发明实施例初始化智能终端设备的方法流程;
图2示出了本发明实施例初始化智能终端设备的装置结构;
图3示出了本发明实施例初始化智能终端设备的系统结构;
图4示出了配置为执行根据本发明的方法的服务器的框图;以及
图5示出了配置为保持或者携带实现根据本发明的方法的程序代码的存储单元。
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例,然而应当理解,可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反,提供这些实施例是为了能够更透彻地
理解本公开,并且能够将本公开的范围完整的传达给本领域的技术人员。
现有通过软件包手工编译对智能终端设备进行环境初始化的方法,对于每一智能终端设备,需要安装人员进行一些手动配置的操作,且一些配置操作为简单的重复配置操作,使得在待初始化智能终端设备数量较多的情况下,初始化所需的时间长、初始化效率低。
黄狗更新修改(Yum,Yellowdog UpdaterModified)服务器是一个在桌面操作系统(Fedora)和红帽(RedHat)以及软件与系统开发(SUSE,Software and System Development)、社区企业操作系统(CentOS,Community Enterprise Operating System)中的Shell前端软件包管理器,基于红帽软件管理工具(RPM,RedHat Package Manager),能够使得实现初始化后的智能终端设备可以从指定的服务器,自动下载RPM包进行应用程序安装、更新,并能自动处理应用程序的依赖性关系,实现一次安装应用程序所有依赖的软件包,而无须繁琐地一次次下载、安装。其中,可供Yum下载的RPM包由Linux社区维护,包括Fedora自身提供的应用程序软件包以及源自红帽软件管理工具软件包仓库(RPMfusion)和RPM的Fedora Extras应用程序软件包。根据安装方式的不同,Yum服务器既可以采用Yum技术,安装单个应用程序软件以及该应用程序软件的依赖关系,也可以采用Yum组(Yum group)技术,安装应用程序软件安装包,在该应用程序软件安装包中,包括有多个应用程序软件以及多个应用程序软件相对应的依赖关系。
Yum服务器涉及到如下技术:
1)RPM封包技术,用于对原生版本的应用程序软件进行个性化处理,使得个性化处理后的应用程序软件(RPM包)可以适用于不同的应用场景,用以节约应用程序软件编译、安装、调试所需的时间,减少人工成本。
2)Yum应用程序软件仓库管理技术,用于针对不同的应用场景,对RPM包进行组合,形成RPM组(RPM group)包,并对RPM组包进行集中统一管理,解决应用程序软件间的相互依赖以及各不同应用场景所需的应用程序软件包组,便于用户方便、快捷、高效完成指定任务。
3)远程镜像自动同步(Rsync,Remote sync)技术,采用客户端/服务器
(C/S,Client/Server)模式,服务器(Yum服务器)存储利用RPM封包技术生成的RPM包或RPM组包,在实现初始化后的客户端与服务器建立网络连接后,能够自动从服务器下载并安装RPM包或RPM组包,从而实现应用程序软件安装的高效、可靠。
本发明实施例中,对于现有通过软件包手工编译的方式对智能终端设备进行初始化的方案在时间成本以及人力成本上的消耗,考虑将Yum技术以及Yum group技术应用于对智能终端设备进行初始化,从而解决初始化工作在人力、物力上成本的浪费,减少初始化所需的时间、提升初始化效率。具体来说,综合利用RPM封包技术、Rsync技术、Yum应用程序软件仓库管理技术,解决现有技术在初始化过程中的繁琐冗余步骤。
图1示出了本发明实施例初始化智能终端设备的方法流程。参见图1,该流程包括:
步骤101,编辑用于安装应用程序软件的说明文件,利用编辑的说明文件封装应用程序软件包为安装包并存储在服务器中;
本步骤中,安装包包括但不限于RPM包。通过分析应用程序软件安装流程,并将应用程序安装流程编写为说明(Spec)文件,用以使利用编辑的说明文件封装应用程序软件包生成的RPM包,可以根据该编写的安装流程进行自动安装。其中,每一应用程序软件对应有一说明文件。
本发明实施例中,Spec文件是制作RPM包的说明书,Spec文件中包含:宏定义部分、前言部分、描述部分以及安装流程部分。其中,
宏定义部分,用于定义宏名以及宏名映射的内容,宏类似编程时的变量,如果后续应用中引用宏名,将会展开为该引用宏名映射的内容。通过利用宏定义,可以提高说明文件的可维护性、增强可移植性等。
本发明实施例中,宏定义部分为可选项。
前言部分,用于设置应用程序软件包名、应用程序软件对应的源代码压缩包名、编译时依赖的应用程序软件包信息、安装时依赖的应用程序软件包信息等。其中,编译时依赖的应用程序软件包信息、安装时依赖的应用程序软件包信息为可选项,根据应用程序软件编译及安装是否需要依赖其它应用
程序软件包确定。该前言部分还可以包括:版本号、发布(release)号等信息。
描述(%description)部分:该部分用于在用户不了解应用程序软件包时,可以通过RPM-qi等命令查询该应用程序软件包的简要介绍。
本发明实施例中,描述部分为可选项。
安装流程部分:用于设置应用程序软件的安装流程,包括以下脚本段描述:
1.准备阶段(%pre),包括:
A11,查询说明文件中的前言部分,获取待安装的应用程序软件是否需要依赖其它应用程序软件,如果是,安装依赖的所述其它应用程序软件,执行步骤A12,否则,直接执行步骤A12;
本步骤中,如果待安装的应用程序软件需要依赖其它应用程序软件,例如,在安装应用程序软件A时,需要先安装应用程序软件B,则在该准备阶段,先对应用程序软件B进行安装。
A12,将前言部分中的源代码压缩包名对应的源代码压缩包解压至预先设置的编译目录下。
本步骤中,预先设置的编译目录可以通过上述宏定义的方式进行设置,例如,解压至BUILD目录下,用于为下一步编译阶段做好准备。
本发明实施例中,源代码压缩包名对应的源代码压缩包设置在应用程序软件包中。
2.编译阶段(%build):在该阶段,编译预先设置的编译目录下解压的源代码压缩包。
3.安装阶段(%install):安装阶段是将编译生成的二进制应用程序文件、应用程序配置文件、服务(service)脚本文件等安装到一个预先设置的虚拟根目录下,用于临时存储,该虚拟根目录为后续安装RPM包的主机(待初始化智能终端设备)的根目录。
本发明实施例中,该虚拟根目录可以用宏“buildroot”表示。
4.清理阶段(%clean):在安装完成后,删除安装阶段设置的虚拟根目录。
5.文件列表(%file):文件列表为Spec文件的核心部分,只有在文件列表中列出的文件,最终才会封装进RPM包中。其中,文件列表中的文件为安装应用程序软件所必需的文件。
作为可选实施例,在一些应用程序软件安装后,可以对该应用程序软件进行个性化的功能设置,Spec文件还可以包括:
6.安装后阶段(%post):用于对安装的应用程序软件进行个性化功能设置。
实际应用中,还可以在安装流程部分,设置卸载前以及卸载后阶段(%preun、%postun),以分别对卸载前、卸载后的操作进行设置。
作为可选实施例,还可以在安装流程部分,设置日志(Changelog)脚本段,用以对应用程序软件的更新日志进行说明。
上述脚本段中,可以通过编写shell程序,以实现预先设置的操作。例如,可以将准备阶段、编译阶段、安装阶段、清理阶段、文件列表以及安装后阶段对应的程序代码段写入shell程序中的相应段落。
作为可选实施例,将编辑的说明文件与应用程序软件包封装为RPM包包括:
调用rpmbuild命令,指定应用程序软件包以及该应用程序软件包对应的Spec文件,进行打包封装,生成RPM包。
本步骤中,例如,通过rpmbuild-bb<specfile>命令行,可以生成RPM包。其中,-bb参数表示只按照specfile文件生成RPM包。
本发明实施例中,根据编辑的说明文件包含的宏定义部分、前言部分、描述部分以及安装流程部分,依序对应用程序软件包进行封装,生成RPM包。
作为可选实施例,在生成RPM包后,该方法可以还包括:
对生成的RPM包进行安装流程测试,如果未通过安装流程测试,修改说明文件,直至经过修改后生成的RPM包通过安装流程测试。
本步骤中,进行测试为利用rsync将RPM包进行自动安装,如果在RPM包安装中存在问题,则根据显示的提示信息,对Spec文件进行修改,然后,
按照重新修改的Spec文件封装应用程序软件包,生成RPM包,再进行安装流程测试,直至安装流程测试通过。从而降低初始化过程中的报错概率,提升智能终端设备初始化时的成功率和可靠性,提升初始化智能终端设备的效率。
作为另一可选实施例,在生成RPM包或生成的RPM包经过安装流程测试后,该方法可以还包括:
根据应用场景,将生成的RPM包进行组合,并为组合的RPM包编辑组包配置文件,将编辑的组包配置文件与组合的RPM包封装为RPM组包。
本步骤中,由于不同的应用场景,需要安装不同组合的应用程序软件包,例如,如前所述,对于Lnmp,需要安装Linux、Nginx、Mysql以及Php,对于Lamp,需要安装Linux、Apache、MySQL以及PHP。因而,本发明实施例中,为了提升安装后使用智能终端设备的用户的业务体验,可以按照不同的应用场景需求,对通过安装流程测试的RPM包进行分组管理,即根据不同的应用场景需求,对RPM包进行组合,从而实现一次初始化即可完成应用场景的设置,有效减少用户操作,降低初始化所需时间。
在进行分组管理后,为了对组合的RPM包中的各RPM包的应用场景中的各参数,例如,对组合的RPM包进行描述,保存组包元数据的索引路径,包含的RPM包信息进行配置,还可以根据分组管理得到的RPM包,编辑组合的RPM包对应的组包配置文件,每一组合的RPM包对应一组包配置文件。
本步骤中,以智能终端设备为Yum服务器为例,编辑组包配置文件包括:
B11,安装yum-groups-manager命令;
本步骤中,安装yum-groups-manager命令的命令行为:yum install yum-utils.norch。yum-groups-manager命令用于触发执行后续的流程。
B12,在每一RPM包中,创建该每一RPM包中文件对应的索引;
本步骤为可选步骤,通过为RPM包中文件创建对应的索引,可以减少查询文件时所需的时间,提高查询效率。创建索引的命令行为:createrepo-d--update path。其中,“-d”参数为必需参数,path为索引路径。
B13,调用组包配置命令,将创建的索引应用在调用的组包配置命令中,得到组包配置文件。
本步骤中,组包配置命令如下:
yum-groups-manager-n″groupname″--id=″groupid″--description=″......″--save=path/repodata/*.xml--mandatory RPM[RPM]...
其中,
-n参数:指定组(group)包名;
--id参数:生成组(group)包的唯一标识;
--description参数:对组包进行简单的描述,方便用户了解信息;
--save参数:保存组包元数据到预先设置的索引路径下的文件中;
--mandatory参数:指定组包中包含的一个或多个RPM包。
作为可选实施例,组包配置文件格式可以采用可扩展标记语言(XML,Extensible Markup Language)格式。
举例来说,对于一生成的组包配置文件:
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--mandatory Qihoo-App-nginxQihoo-App-phpQihoo-App-mysql
在该组包配置文件中,表示利用安装的yum-groups-manager命令生成一个组名为“LNMP-2.2.20-5.2.5”的组,该组的唯一标识为LNMP,描述为“1.2.9版本的nginx程序,版本为5.2.5的php程序,版本为5.5的mysql程序”,LNMP-2.2.20-5.2.5组的元数据保存在/usr/local/www/CentOS/5/os/x86_64/repo data/mygroups.xml文件中,该组包含的RPM包有Qihoo-App-nginx、Qihoo-app-php以及Qihoo-App-mysql三个软件包。
作为可选实施例,该方法还可以还包括:
在组合的RPM包发生更新后,更新该组合的RPM包对应的组包配置文件。
本步骤中,更新包括:删除、修改、增加等。更新组包配置文件的命令行为:createrepo--verbose-g path/repodata/*.xml path。
通过更新组包配置文件,可以使新增的RPM包能被智能终端设备搜索到。
例如:一更新组包配置文件的命令行具体如下:
createrepo--verbose-g/usr/local/www/CentOS/5/os/x86_64/repodata/mygr oups.xml/usr/local/www/CentOS/5/os/x86_64/
在该命令行中,利用creatrepo命令,通过指定group的元数据文件/usr/local/www/CentOS/5/os/x86_64/repodata/mygroups.xml,将在/usr/local/www/CentOS/5/os/x86_64目录下更新组包配置文件,使得智能终端设备可以搜索到此次Yum server上更新的RPM组包。
本发明实施例中,封装好的RPM包放置于预先设置的服务器中。
步骤102,编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备中;
本步骤中,服务器包括但不限于Yum服务器。安装包配置文件还可以进一步包括但不限于以下信息:服务器域名信息、服务器统一资源定位符信息、服务器IP地址信息、安装包存储地址信息、安装包类型信息等。
步骤103,在所述服务器上安装服务,并将所述服务的目录指向存放安装包的存储路径,启动服务;
本步骤中,作为可选实施例,服务用于向所述待初始化智能终端设备提供所述安装包。在所述服务器上安装超文本传输协议守护程序(HTTPD,Hypertext Transfer Protocol Daemon)服务,并将HTTPD服务的目录指向存放RPM包的RPM包存储路径,启动HTTPD服务。
本发明实施例中,在启动服务后,可以通过启动的服务监测智能终端设备并响应智能终端设备的请求。
步骤104,触发待初始化智能终端设备读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
本步骤中,待初始化智能终端设备编辑RPM包存储路径映射的目录文件,
例如,目录文件可以设置为/etc/Yum.repos.d/CentOS.repo。这样,在安装时,将安装文件存储在RPM包存储路径映射的待初始化智能终端设备上的目录文件。编辑目录文件/etc/Yum.repos.d/CentOS.repo的命令行如下:
[ADDOPS-base]
name=ADDOPS-$releasever-Base
baseurl=http://Yum-serverIP/addops/$releasever/os/$basearch/
gpgcheck=0
本发明实施例中,根据读取的安装包配置文件,从服务器启动的服务中获取安装包,从而可以使得安装包按照编辑的说明文件进行安装。
本发明实施例中,可以同时开启数十台待初始化智能终端设备,并在启动后通过内置的安装包配置文件从服务器中获取安装包,而由于安装包采用本发明实施例编辑的说明文件进行封装,使得智能终端设备在获取安装包后,可以自动进行安装,无需进行软件包手工编译,实现以并行方式对多台待初始化智能终端设备进行RPM包安装,从而大大提高了初始化的效率以及可靠性。
由上述可见,本发明实施例的初始化智能终端设备的方法,通过在初始化过程中利用RPM封包技术、Yum应用程序软件仓库管理技术以及Rsync技术,可以在时间成本、人力成本上节省大量的资源。例如,本发明实施例中,只需将应用程序软件源代码拷贝到一台Yum服务器上进行编译安装,生成安装包,相对于将应用程序软件源代码拷贝到每台需要初始化的智能终端设备上进行编译安装,所需时间更短,初始化更新效率更高。举例来说,对于1000台智能终端设备需要安装某一应用程序软件的情形,仅拷贝该应用程序软件源代码所需的时间,现有技术为本发明实施例的1000倍;进一步地,现有技术中,需要在每台待初始化智能终端设备上编译安装源代码,而本发明实施例中,只需要编写一份Spec文件,利用编辑的说明文件封装应用程序软件包为RPM包,待初始化智能终端设备直接通过运行Yumgroupinstallsoftwarename即可。举例来说,对于1000台智能终端设备需要安装某一应用程序软件的情形,现有技术在源代码编译安装上所需的时间
成本依然是本发明实施例的1000倍。
图2示出了本发明实施例初始化智能终端设备的装置结构。参见图2,该装置包括:打包模块、测试模块、初始化通信模块,其中,
打包模块,用于编辑安装应用程序软件的说明文件,利用编辑的说明文件封装应用程序软件包为RPM包,输出至测试模块;接收测试模块输出的测试通过通知,将通过测试的RPM包输出至初始化通信模块;接收测试模块输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,输出至测试模块;
本发明实施例中,Spec文件中的内容包含:用于定义宏名以及宏名映射的内容的宏定义部分;用于设置应用程序软件包名、应用程序软件对应的源代码压缩包名、编译时依赖的应用程序软件包信息、安装时依赖的应用程序软件包信息的前言部分;用于应用程序软件包的简要介绍的描述部分以及用于设置应用程序软件的安装流程的安装流程部分。其中,安装流程部分包括:准备阶段脚本段描述、编译阶段脚本段描述、安装阶段脚本段描述、清理阶段脚本段描述以及文件列表脚本段描述。
较佳地,通过调用rpmbuild命令,指定应用程序软件包以及该应用程序软件包对应的Spec文件,进行打包封装,生成RPM包。
作为可选实施例,打包模块还用于根据预先设置的应用场景,确认应用场景对应的RPM包通过测试,将该应用场景对应的RPM包进行组合,并为组合的RPM包编辑组包配置文件,将编辑的组包配置文件与组合的RPM包封装为RPM组包,输出至初始化通信模块。
本发明实施例中,编辑组包配置文件包括:
安装yum-groups-manager命令;在每一RPM包中,创建该每一RPM包中文件对应的索引;调用组包配置命令,将创建的索引应用在调用的组包配置命令中,得到组包配置文件。
测试模块,用于对接收的RPM包进行安装流程测试,如果未通过安装流程测试,向打包模块输出测试未通过通知,如果通过安装流程测试,向打包模块输出测试通过通知;
本发明实施例中,可以在测试未通过通知中,携带未通过测试的具体提示信息。
初始化通信模块,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装。
本发明实施例中,作为可选实施例,通过在初始化通信模块上安装超文本传输协议守护程序服务,并将HTTPD服务的目录指向存放RPM包的RPM包存储路径,启动HTTPD服务,从而可以提供通信支持。
所应说明的是,该装置中的各模块,可以通过相互独立的物理设备实现,下面进行描述。
图3示出了本发明实施例初始化智能终端设备的系统结构。参见图3,该系统包括:RPM打包机、RPM包测试机、Yum服务器以及待初始化智能终端设备,其中,RPM打包机、RPM包测试机、Yum服务器组成图2所示的装置。
RPM打包机,用于编辑安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为RPM包,输出至RPM包测试机;接收RPM包测试机输出的测试通过通知,将通过测试的RPM包输出至Yum服务器;接收RPM包测试机输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,将重新封装的RPM包输出至RPM包测试机;
本发明实施例中,RPM打包机包括:社区企业操作系统(CentOS,Community Enterprise Operating System)5RPM打包机以及CentOS6 RPM打包机。
作为可选实施例,RPM打包机还用于根据预先设置的应用场景,确认应用场景对应的RPM包通过测试,将该应用场景对应的RPM包进行组合,并为组合的RPM包编辑组包配置文件,将编辑的组包配置文件与组合的RPM
包封装为RPM组包,输出至Yum服务器。
本发明实施例中,利用Rsync自动同步技术,RPM打包机将进行分组管理后得到的RPM组包(多个RPM包以及对应生成的Yum group配置文件)传输至Yum服务器。
RPM包测试机,用于对接收的RPM包进行安装流程测试,如果未通过安装流程测试,向RPM打包机输出测试未通过通知,如果通过安装流程测试,向RPM打包机输出测试通过通知;
本发明实施例中,利用Rsync自动同步技术,将打包生成的RPM包传输到RPM包测试机进行安装流程测试,以使打包生成的RPM包通过安装流程测试,从而提升初始化智能终端设备的可靠性和效率。如果在RPM包安装中存在问题,则可以通知RPM打包机根据提示信息,在RPM打包机上对Spec文件进行修改,然后,RPM打包机将修改的RPM包再输出至RPM包测试机进行安装流程测试,直至测试通过。
对应CentOS5 RPM打包机,RPM包传输到CentOS5 RPM包测试机进行测试;对应CentOS6 RPM打包机,RPM包传输到CentOS6 RPM包测试机进行测试。即对应于RPM打包机,RPM包测试机包括:CentOS5 RPM包测试机以及CentOS6 RPM包测试机。测试无问题后,RPM包测试机通知RPM打包机,CentOS5 RPM打包机和CentOS6 RPM打包机将对应通过测试的RPM包进行分组管理。
Yum服务器,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装用于向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装;
本发明实施例中,对应CentOS5 RPM打包机,Yum服务器为CentOS5 Yum服务器(server);对应CentOS6 RPM打包机,Yum服务器为CentOS6Yum server。即Yum服务器包括:CentOS5 Yum server以及CentOS6Yum server。
待初始化智能终端设备,用于读取内置的安装包配置文件,根据读取的
安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
本发明实施例中,待初始化智能终端设备包括:CentOS5客户端以及CentOS6客户端。作为可选实施例,在CentOS5客户端和CentOS6客户端上,通过超文本传输协议(HTTP,Hypertext Transfer Protocol)协议,分别与CentOS5 Yum server以及CentOS6Yum server通信,以进行自动初始化流程。
作为可选实施例,CentOS5客户端的数量为一台或多台,CentOS6客户端的数量为一台或多台。
在此提供的算法和显示不与任何特定计算机、虚拟系统或者其它设备固有相关。各种通用系统也可以与基于在此的示教一起使用。根据上面的描述,构造这类系统所要求的结构是显而易见的。此外,本发明也不针对任何特定编程语言。应当明白,可以利用各种编程语言实现在此描述的本发明的内容,并且上面对特定语言所做的描述是为了披露本发明的最佳实施方式。
在此处所提供的说明书中,说明了大量具体细节。然而,能够理解,本发明的实施例可以在没有这些具体细节的情况下实践。在一些实例中,并未详细示出公知的方法、结构和技术,以便不模糊对本说明书的理解。
类似地,应当理解,为了精简本公开并帮助理解各个发明方面中的一个或多个,在上面对本发明的示例性实施例的描述中,本发明的各个特征有时被一起分组到单个实施例、图、或者对其的描述中。然而,并不应将该公开的方法解释成反映如下意图:即所要求保护的本发明要求比在每个权利要求中所明确记载的特征更多的特征。更确切地说,如下面的权利要求书所反映的那样,发明方面在于少于前面公开的单个实施例的所有特征。因此,遵循具体实施方式的权利要求书由此明确地并入该具体实施方式,其中每个权利要求本身都作为本发明的单独实施例。
本领域那些技术人员可以理解,可以对实施例中的设备中的模块进行自适应性地改变并且把它们设置在与该实施例不同的一个或多个设备中。可以把实施例中的模块或单元或组件组合成一个模块或单元或组件,以及此外可以把它们分成多个子模块或子单元或子组件。除了这样的特征和/或过程或者单元中的至少一些是相互排斥之外,可以采用任何组合对本说明书(包括伴
随的权利要求、摘要和附图)中公开的所有特征以及如此公开的任何方法或者设备的所有过程或单元进行组合。除非另外明确陈述,本说明书(包括伴随的权利要求、摘要和附图)中公开的每个特征可以由提供相同、等同或相似目的的替代特征来代替。
此外,本领域的技术人员能够理解,尽管在此所述的一些实施例包括其它实施例中所包括的某些特征而不是其它特征,但是不同实施例的特征的组合意味着处于本发明的范围之内并且形成不同的实施例。例如,在下面的权利要求书中,所要求保护的实施例的任意之一都可以以任意的组合方式来使用。
本发明的各个部件实施例可以以硬件实现,或者以在一个或者多个处理器上运行的软件模块实现,或者以它们的组合实现。本领域的技术人员应当理解,可以在实践中使用微处理器或者数字信号处理器(DSP)来实现根据本发明实施例的初始化智能终端设备的装置及系统中的一些或者全部部件的一些或者全部功能。本发明还可以实现为用于执行这里所描述的方法的一部分或者全部的设备或者装置程序(例如,计算机程序和计算机程序产品)。这样的实现本发明的程序可以存储在计算机可读介质上,或者可以具有一个或者多个信号的形式。这样的信号可以从因特网网站服务器上下载得到,或者在载体信号上提供,或者以任何其他形式提供。
例如,图4示出了可以实现根据本发明的初始化智能终端设备方法的终端设备。该终端设备传统上包括处理器410和以存储器420形式的程序产品或者可读介质。存储器420可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM或者ROM之类的电子存储器。存储器420具有配置为执行上述方法中的任何方法步骤的程序代码431的存储空间430。例如,配置为程序代码的存储空间430可以包括分别配置为实现上面的方法中的各种步骤的各个程序代码431。这些程序代码可以从一个或者多个程序产品中读出或者写入到这一个或者多个程序产品中。这些程序产品包括诸如存储卡之类的程序代码载体。这样的程序产品通常为如参考图5所述的便携式或者固定存储单元。该存储单元可以具有与图4的终端设备中的存储器420类似布置的存储段、存储空间等。程序代码可以例如以适当形式进行压缩。通常,存储单元包括可读代码431’,即可以由例如诸如410之类的处理器读取的代码,这
些代码当由终端设备运行时,导致该终端设备执行上面所描述的方法中的各个步骤。
本文中所称的“一个实施例”、“实施例”或者“一个或者多个实施例”意味着,结合实施例描述的特定特征、结构或者特性包括在本发明的至少一个实施例中。此外,请注意,这里“在一个实施例中”的词语例子不一定全指同一个实施例。
应该注意的是上述实施例对本发明进行说明而不是对本发明进行限制,并且本领域技术人员在不脱离所附权利要求的范围的情况下可设计出替换实施例。在权利要求中,不应将位于括号之间的任何参考符号构造成对权利要求的限制。单词“包含”不排除存在未列在权利要求中的元件或步骤。位于元件之前的单词“一”或“一个”不排除存在多个这样的元件。本发明可以借助于包括有若干不同元件的硬件以及借助于适当编程的计算机来实现。在列举了若干装置的单元权利要求中,这些装置中的若干个可以是通过同一个硬件项来具体体现。单词第一、第二、以及第三等的使用不表示任何顺序。可将这些单词解释为名称。
Claims (21)
- 一种初始化智能终端设备的方法,包括:编辑用于安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包并存储在服务器中;编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备;在所述服务器上安装用于向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务;触发待初始化智能终端设备读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
- 如权利要求1所述的方法,所述说明文件包含:前言部分以及安装流程部分,其中,前言部分,用于设置应用程序软件包名以及应用程序软件对应的源代码压缩包名;安装流程部分:用于设置应用程序软件的安装流程。
- 如权利要求2所述的方法,所述说明文件还包含用于定义宏名以及宏名映射的内容的宏定义部分、和/或,用于描述应用程序软件包的简要介绍的描述部分。
- 如权利要求2所述的方法,所述安装流程部分包括:准备阶段脚本段描述、编译阶段脚本段描述、安装阶段脚本段描述、清理阶段脚本段描述以及文件列表脚本段描述。
- 如权利要求4所述的方法,所述安装流程部分还包括:安装后阶段脚本段描述、和/或,卸载前脚本段描述、和/或,卸载后阶段脚本段描述、和/或,日志脚本段描述。
- 如权利要求4或5所述的方法,所述准备阶段脚本段描述包括:A11,查询说明文件中的前言部分,获取待安装的应用程序软件是否需要依赖其它应用程序软件,如果是,安装依赖的所述其它应用程序软件,执行 步骤A12,否则,直接执行步骤A12;A12,将前言部分中的源代码压缩包名对应的源代码压缩包解压至预先设置的编译目录下。
- 如权利要求1所述的方法,所述利用编辑的说明文件封装应用程序软件包为安装包包括:调用rpmbuild命令,指定应用程序软件包以及该应用程序软件包对应的说明文件,进行打包封装,生成安装包。
- 如权利要求1所述的方法,在所述生成安装包后,所述方法还包括:对生成的安装包进行安装流程测试,如果未通过安装流程测试,修改说明文件,直至经过修改后生成的安装包通过安装流程测试。
- 如权利要求8所述的方法,所述方法还包括:根据应用场景,将通过安装流程测试的安装包进行组合,并为组合的安装包编辑组包配置文件,将编辑的组包配置文件与组合的安装包封装为安装组包。
- 如权利要求9所述的方法,所述编辑组包配置文件包括:安装yum-groups-manager命令;在每一安装包中,创建该每一安装包中文件对应的索引;调用组包配置命令,将创建的索引应用在调用的组包配置命令中,得到组包配置文件。
- 如权利要求9所述的方法,所述组包配置文件采用可扩展标记语言格式。
- 如权利要求1所述的方法,所述根据读取的安装包配置文件,从服务器启动的服务中获取安装包包括:在服务器上安装超文本传输协议守护程序服务,并将超文本传输协议守护程序服务的目录指向存放安装包的安装包存储路径,启动超文本传输协议守护程序服务;在待初始化智能终端设备上,编辑所述安装包存储路径映射的目录文件;启动的待初始化智能终端设备读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包;在所述安装包存储路径映射的目录文件安装所述安装包。
- 一种初始化智能终端设备的装置,该装置包括:打包模块、测试模块以及初始化通信模块,其中,打包模块,用于编辑安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包,输出至测试模块;接收测试模块输出的测试通过通知,将通过测试的安装包输出至初始化通信模块;接收测试模块输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,输出至测试模块;测试模块,用于对接收的安装包进行安装流程测试,如果未通过安装流程测试,向打包模块输出测试未通过通知,如果通过安装流程测试,向打包模块输出测试通过通知;初始化通信模块,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装用于向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装。
- 如权利要求13所述的装置,所述打包模块还用于根据预先设置的应用场景,确认应用场景对应的安装包通过测试,将该应用场景对应的安装包进行组合,并为组合的安装包编辑组包配置文件,将编辑的组包配置文件与组合的安装包封装为安装组包,输出至初始化通信模块。
- 如权利要求13或14所述的装置,所述说明文件包含:用于定义宏名以及宏名映射的内容的宏定义部分;用于设置应用程序软件包名以及应用程序软件对应的源代码压缩包名、编译时依赖的应用程序软件包信息、安装时依赖的应用程序软件包信息的前言部分;用于应用程序软件包的简要介绍的描述部分以及用于设置应用程序软件的安装流程的安装流程部分。
- 一种初始化智能终端设备的系统,该系统包括:安装包打包机、安 装包测试机、服务器以及待初始化智能终端设备,其中,安装包打包机,用于编辑安装应用程序软件的说明文件并且利用编辑的说明文件将应用程序软件包封装为安装包,输出至安装包测试机;接收安装包测试机输出的测试通过通知,将通过测试的安装包输出至服务器;接收安装包测试机输出的测试未通过通知,修改所述编辑的说明书,并利用修改的说明文件重新封装应用程序软件包为RPM包,将重新封装的安装包输出至安装包测试机;安装包测试机,用于对接收的安装包进行安装流程测试,如果未通过安装流程测试,向安装打包机输出测试未通过通知,如果通过安装流程测试,向安装打包机输出测试通过通知;服务器,用于编辑包含服务器地址信息的安装包配置文件,并配置到待初始化智能终端设备,安装向所述待初始化智能终端设备提供所述安装包的服务,并将所述服务的目录指向存放安装包的存储路径,启动所述服务,与待初始化智能终端设备通信,以将安装包输出至所述待初始化智能终端设备进行安装;待初始化智能终端设备,用于读取内置的安装包配置文件,根据读取的安装包配置文件,从服务器启动的服务中获取安装包并进行安装。
- 如权利要求16所述的系统,所述安装打包机还用于根据预先设置的应用场景,确认应用场景对应的安装包通过测试,将该应用场景对应的安装包进行组合,并为组合的安装包编辑组包配置文件,将编辑的组包配置文件与组合的安装包封装为安装组包,输出至服务器。
- 如权利要求16所述的系统,利用远程镜像自动同步技术将打包生成的安装包传输到安装包测试机。
- 如权利要求16所述的系统,所述安装打包机包括:社区企业操作系统5安装打包机以及社区企业操作系统6安装打包机。
- 一种程序,包括可读代码,当所述可读代码在终端设备上运行时,导致所述终端设备执行根据权利要求1-12中的任一个所述的初始化智能终端设备的方法。
- 一种可读介质,其中存储了如权利要求20所述的程序。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410310129.2A CN105335173A (zh) | 2014-07-01 | 2014-07-01 | 初始化智能终端设备的方法、装置及系统 |
CN201410310129.2 | 2014-07-01 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016000623A1 true WO2016000623A1 (zh) | 2016-01-07 |
Family
ID=55018463
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/083102 WO2016000623A1 (zh) | 2014-07-01 | 2015-07-01 | 初始化智能终端设备的方法、装置及系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN105335173A (zh) |
WO (1) | WO2016000623A1 (zh) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108647527A (zh) * | 2018-04-17 | 2018-10-12 | 阿里巴巴集团控股有限公司 | 文件打包、文件包解包方法、装置及网络设备 |
CN110727440A (zh) * | 2019-10-08 | 2020-01-24 | 中国电子科技集团公司第二十八研究所 | 一种软件封装方法 |
CN110895471A (zh) * | 2018-09-12 | 2020-03-20 | 北京京东尚科信息技术有限公司 | 安装包生成方法、装置、介质及电子设备 |
CN111198744A (zh) * | 2018-11-16 | 2020-05-26 | 中标软件有限公司 | 自动化应用程序容器化和镜像备份发布的方法 |
CN111949310A (zh) * | 2020-08-07 | 2020-11-17 | 苏州浪潮智能科技有限公司 | 一种基于异构云平台的内置服务外接方法及装置 |
CN112764796A (zh) * | 2019-11-05 | 2021-05-07 | 阿里巴巴集团控股有限公司 | 安装包生成系统 |
CN112925587A (zh) * | 2021-03-11 | 2021-06-08 | 北京百度网讯科技有限公司 | 用于初始化应用的方法和装置 |
CN113031964A (zh) * | 2021-03-25 | 2021-06-25 | 恒安嘉新(北京)科技股份公司 | 一种大数据应用的管理方法、装置、设备及存储介质 |
CN113760304A (zh) * | 2020-06-03 | 2021-12-07 | 汉朔科技股份有限公司 | 一种系统的配置方法、装置、设备及介质 |
CN115412516A (zh) * | 2022-08-30 | 2022-11-29 | 上海哔哩哔哩科技有限公司 | 客服功能实现方法、装置、计算设备及存储介质 |
CN116755724A (zh) * | 2022-11-29 | 2023-09-15 | 华东师范大学 | 一种pca软件及安装方法 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106371865A (zh) * | 2016-08-26 | 2017-02-01 | 浪潮(北京)电子信息产业有限公司 | 一种软件环境部署方法和系统 |
CN108228201A (zh) * | 2017-12-28 | 2018-06-29 | 广州亦云信息技术股份有限公司 | 基于软件仓库的软件管理方法、电子设备及存储介质 |
CN108594330A (zh) * | 2017-12-28 | 2018-09-28 | 南京信息工程大学 | 基于云服务器的自动气象数据监测系统 |
CN108920157B (zh) * | 2018-06-13 | 2021-02-23 | 平安科技(深圳)有限公司 | Nginx软件的安装方法、装置、计算机设备及存储介质 |
CN112486510A (zh) * | 2020-11-04 | 2021-03-12 | 深圳市金百锐通信科技有限公司 | 用于软件安装的方法、装置、终端设备及存储介质 |
CN112445576B (zh) * | 2020-11-30 | 2024-04-16 | 中国人寿保险股份有限公司 | 一种屏蔽业务差异的设备调用方法及相关设备 |
CN113885896B (zh) * | 2021-09-29 | 2024-06-25 | 平安银行股份有限公司 | 应用程序软件包安装方法、装置、计算机设备及存储介质 |
CN113821229A (zh) * | 2021-10-29 | 2021-12-21 | 北京光启元数字科技有限公司 | 一种程序安装方法、装置、设备及介质 |
CN114296776A (zh) * | 2021-12-08 | 2022-04-08 | 山东齐鲁数通科技有限公司 | 一种服务包配置调用方法、装置、终端设备及存储介质 |
CN117270896A (zh) * | 2023-11-15 | 2023-12-22 | 中孚安全技术有限公司 | 一种应用程序自动识别安装方法、系统、装置及存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020131405A1 (en) * | 2001-02-14 | 2002-09-19 | Ching-Fang Lin | Java based information exchange process and system thereof |
US20100058319A1 (en) * | 2008-08-28 | 2010-03-04 | Hitachi, Ltd. | Agile deployment of server |
CN103281373A (zh) * | 2013-05-30 | 2013-09-04 | 烽火通信科技股份有限公司 | 家庭网关智能升级装置及升级方法 |
CN103580908A (zh) * | 2012-08-10 | 2014-02-12 | 百度在线网络技术(北京)有限公司 | 服务器的配置方法及系统 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050235281A1 (en) * | 2004-04-19 | 2005-10-20 | Telefonaktiebolaget L M Ericsson (Publ) | Combined software installation package |
CN103713924B (zh) * | 2013-12-24 | 2017-03-08 | 汉柏科技有限公司 | 云计算平台服务的升级方法及系统 |
-
2014
- 2014-07-01 CN CN201410310129.2A patent/CN105335173A/zh active Pending
-
2015
- 2015-07-01 WO PCT/CN2015/083102 patent/WO2016000623A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020131405A1 (en) * | 2001-02-14 | 2002-09-19 | Ching-Fang Lin | Java based information exchange process and system thereof |
US20100058319A1 (en) * | 2008-08-28 | 2010-03-04 | Hitachi, Ltd. | Agile deployment of server |
CN103580908A (zh) * | 2012-08-10 | 2014-02-12 | 百度在线网络技术(北京)有限公司 | 服务器的配置方法及系统 |
CN103281373A (zh) * | 2013-05-30 | 2013-09-04 | 烽火通信科技股份有限公司 | 家庭网关智能升级装置及升级方法 |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11100244B2 (en) | 2018-04-17 | 2021-08-24 | Advanced New Technologies Co., Ltd. | File packaging and unpackaging methods, apparatuses, and network devices |
CN108647527B (zh) * | 2018-04-17 | 2020-11-17 | 创新先进技术有限公司 | 文件打包、文件包解包方法、装置及网络设备 |
CN108647527A (zh) * | 2018-04-17 | 2018-10-12 | 阿里巴巴集团控股有限公司 | 文件打包、文件包解包方法、装置及网络设备 |
CN110895471A (zh) * | 2018-09-12 | 2020-03-20 | 北京京东尚科信息技术有限公司 | 安装包生成方法、装置、介质及电子设备 |
CN111198744B (zh) * | 2018-11-16 | 2023-05-30 | 中标软件有限公司 | 自动化应用程序容器化和镜像备份发布的方法 |
CN111198744A (zh) * | 2018-11-16 | 2020-05-26 | 中标软件有限公司 | 自动化应用程序容器化和镜像备份发布的方法 |
CN110727440B (zh) * | 2019-10-08 | 2022-10-04 | 中国电子科技集团公司第二十八研究所 | 一种软件封装方法 |
CN110727440A (zh) * | 2019-10-08 | 2020-01-24 | 中国电子科技集团公司第二十八研究所 | 一种软件封装方法 |
CN112764796A (zh) * | 2019-11-05 | 2021-05-07 | 阿里巴巴集团控股有限公司 | 安装包生成系统 |
CN113760304A (zh) * | 2020-06-03 | 2021-12-07 | 汉朔科技股份有限公司 | 一种系统的配置方法、装置、设备及介质 |
CN111949310B (zh) * | 2020-08-07 | 2022-07-19 | 苏州浪潮智能科技有限公司 | 一种基于异构云平台的内置服务外接方法及装置 |
CN111949310A (zh) * | 2020-08-07 | 2020-11-17 | 苏州浪潮智能科技有限公司 | 一种基于异构云平台的内置服务外接方法及装置 |
CN112925587A (zh) * | 2021-03-11 | 2021-06-08 | 北京百度网讯科技有限公司 | 用于初始化应用的方法和装置 |
CN113031964A (zh) * | 2021-03-25 | 2021-06-25 | 恒安嘉新(北京)科技股份公司 | 一种大数据应用的管理方法、装置、设备及存储介质 |
CN113031964B (zh) * | 2021-03-25 | 2023-12-26 | 恒安嘉新(北京)科技股份公司 | 一种大数据应用的管理方法、装置、设备及存储介质 |
CN115412516A (zh) * | 2022-08-30 | 2022-11-29 | 上海哔哩哔哩科技有限公司 | 客服功能实现方法、装置、计算设备及存储介质 |
CN116755724A (zh) * | 2022-11-29 | 2023-09-15 | 华东师范大学 | 一种pca软件及安装方法 |
CN116755724B (zh) * | 2022-11-29 | 2024-02-02 | 华东师范大学 | 一种pca软件安装方法 |
Also Published As
Publication number | Publication date |
---|---|
CN105335173A (zh) | 2016-02-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016000623A1 (zh) | 初始化智能终端设备的方法、装置及系统 | |
US11599348B2 (en) | Container image building using shared resources | |
WO2022170801A1 (zh) | iOS应用程序构建方法及装置、电子设备及存储介质 | |
US8595693B2 (en) | Model driven deployment of composite applications | |
US9959108B2 (en) | Fast deployment across cloud platforms | |
US9053236B1 (en) | Automated directory services test setup utility | |
WO2017166446A1 (zh) | 漏洞修复方法和装置 | |
CN105117268B (zh) | 一种实现linux系统自动安装的安装方法及系统 | |
US11016785B2 (en) | Method and system for mirror image package preparation and application operation | |
WO2016000126A1 (zh) | 一种自动化部署方法和终端 | |
US11113050B2 (en) | Application architecture generation | |
CN108897547B (zh) | 一种软件自动化部署方法及装置 | |
WO2015154612A1 (zh) | 扩展apk文件应用的方法及装置 | |
CN106371881B (zh) | 一种用于服务器内程序版本更新的方法和系统 | |
CN113064595A (zh) | 一种基于Docker镜像的QT应用程序编译方法和装置 | |
CN109558142B (zh) | 一种开放网络安装环境移植方法与装置 | |
WO2019056187A1 (zh) | 应用部署方法、装置及系统 | |
US20120066674A1 (en) | Techniques for conditional deployment of application artifacts | |
Salvador et al. | Embedded Linux Development with Yocto Project | |
CN105468427A (zh) | 一种自动编译和发布的实现方法及系统 | |
WO2019029451A1 (zh) | 发布移动应用的方法和电子设备 | |
CN109254765B (zh) | 定时任务管理方法、装置、计算机设备及存储介质 | |
CN113835713B (zh) | 源码包下载方法、装置、计算机设备和存储介质 | |
CN111651352A (zh) | 一种仓库代码的合并方法及装置 | |
CN110659022B (zh) | 一种基于Java自动调用Python脚本的方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15814075 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15814075 Country of ref document: EP Kind code of ref document: A1 |