Software source upgrading method and device based on credential environment

Abstract

The invention discloses a software source upgrading method and device based on a credential environment, and relates to the technical field of software upgrading, and the method comprises the following steps: in a development stage, a developer packages a YUM source in a full amount and sends the YUM source to a tester, the tester finds a BUG through testing and feeds back the BUG to the developer, and the developer repairs the BUG and puts a repaired rpm package into a specified directory; after the test is completed, a tester obtains a YUM source full package from a specified directory, and a YUM source product package is generated; in the upgrading stage, when the rpm package needs to be upgraded, a tester adds the repaired rpm package to a specified directory of the YUM source, and a newest index is generated; and after the test of the repaired rpm package is completed, the tester issues the repaired rpm package and the latest index package to the client site upgrade personnel, and the client site upgrade personnel completes upgrade of the rpm package online. According to the method, the YUM software source can be managed and maintained in the Linux operating system so as to support installation, updating and version control of the software package, and efficient management of the software source is achieved.

Description

Technical Field

[0001] The present invention relates to the field of software upgrade technology, and specifically to a software source upgrade method and device based on a trusted computing environment. Background Art

[0002] YUM (Yellowdog Updater, Modified) is an open source package management tool widely used in Linux systems. It is used to automatically manage the installation, upgrade and dependencies of software packages. It simplifies the user's operation process by downloading and installing software packages from specified software sources. YUM supports multiple software sources, and users can configure different software sources to meet different requirements, such as stability, security or specific function requirements.

[0003] In a large-scale server environment, it is usually necessary to manage software packages on multiple servers to ensure that the software versions on all servers are consistent in order to maintain the stability and security of the system. YUM can specify the software source through the configuration file, thereby controlling the source and version of the software package on the server. However, in a multi-person collaborative environment, if everyone directly modifies the YUM configuration file, it may cause configuration conflicts and inconsistencies, making it difficult to track who made which changes. The traditional YUM management method lacks an effective version control mechanism. Once the configuration file is modified incorrectly, it may be difficult to restore to the previous state. In addition, as the number of servers increases, manually managing the YUM configuration on each server becomes very complicated and time-consuming. Summary of the invention

[0004] In view of the limitations of traditional YUM management methods in multi-person collaboration and version control, the present invention provides a software source upgrade method and device based on a trusted innovation environment to solve the problem that the YUM source occupies too much space and it is difficult for customers to upgrade on site.

[0005] In the first aspect, the present invention provides a software source upgrade method based on a trusted innovation environment, and the technical solution adopted to solve the above technical problems is as follows:

[0006] A method for upgrading software sources based on a trusted innovation environment comprises the following steps:

[0007] During the development phase, developers package the full YUM source package and send it to testers. Testers test the full YUM source package and report any bugs they find to developers. Developers then fix the bugs and put the fixed rpm package into the specified directory of the YUM source. After the test is completed, testers obtain the full YUM source package from the specified directory, generate a YUM source product package, and release it to the customer's on-site upgrade personnel.

[0008] During the upgrade phase, when the rpm package needs to be upgraded, the developer provides the repaired rpm package, and the tester appends the repaired rpm package to the specified directory of the YUM source and generates the latest index; after completing the test of the repaired rpm package, the tester releases the repaired rpm package and the latest index package to the customer's on-site upgrade personnel, who complete the upgrade of the rpm package online.

[0009] Optionally, during the development phase, the tester tests the full package of the YUM source, and reports any bugs to the developer. The developer then fixes the bug and puts the fixed rpm package into the Update / Packages directory of the YUM source. After the test is completed, the tester obtains the full package of the YUM source from the Update / Packages directory and generates a YUM source product package, where the full package of the YUM source includes all rpm packages to be released and metadata for the YUM source.

[0010] Further optionally, during the upgrade phase, the tester appends the repaired rpm package to the Update / Packages directory of the YUM source and generates the latest Update / repodata index; after the test is completed, the tester releases the repaired rpm package and the latest repodata index package to the customer's on-site upgrade personnel, where the latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages;

[0011] The customer's on-site upgrade personnel perform the following operations to complete the online upgrade of the rpm package:

[0012] Append the repaired rpm package to the Update / Packages directory of the YUM source;

[0013] Replace the original Update / repodata index package with the latest repodata index package;

[0014] Clear the YUM cache on your local machine;

[0015] Upgrade the repaired rpm package.

[0016] Optionally, if a problem is found in the repaired rpm package during the upgrade phase, perform a rollback operation as follows:

[0017] Delete the repaired rpm package;

[0018] Replace the latest Update / repodata index package with the original Update / repodata index package.

[0019] In the second aspect, the present invention provides a software source upgrade device based on a trusted innovation environment, and the technical solution adopted to solve the above technical problems is as follows:

[0020] A software source upgrade device based on a trusted innovation environment, comprising:

[0021] Role login module, used for users to log in to the operation page as developers or testers;

[0022] The package repair module is deployed on the operation page. It is used by developers to package the entire YUM source and send it to testers during the development phase. It is also used by developers to fix bugs and put the repaired rpm package into the specified directory of the YUM source.

[0023] Feedback release module, deployed on the operation page, is used by testers to feedback bugs found during the YUM source full package testing process to developers during the development phase. It is also used to obtain the full package of the YUM source from the specified directory after the test is completed, generate the YUM source product package, and release it to the customer's on-site upgrade personnel;

[0024] The test generation module is deployed on the operation page. When the rpm package needs to be upgraded, it is used for testers to append the repaired rpm package to the specified directory of the YUM source and generate the latest index;

[0025] The test release module is deployed on the operation page and is used by testers to test the repaired rpm package. After the test is qualified, the repaired rpm package and the latest index package are released to the customer's on-site upgrade personnel. The customer's on-site upgrade personnel complete the upgrade of the rpm package online.

[0026] Optionally, during the development phase, the developer puts the repaired rpm package into the Update / Packages directory of the YUM source through the packaging repair module. After the test is completed, the tester obtains the full package of the YUM source from the Update / Packages directory through the feedback release module to generate a YUM source product package, where the full package of the YUM source includes all the rpm packages to be released and the metadata for the YUM source.

[0027] Further optionally, during the upgrade phase, the tester appends the repaired rpm package to the Update / Packages directory of the YUM source through the test generation module and generates the latest Update / repodata index;

[0028] After the test is completed, the tester releases the repaired rpm package and the latest repodata index package to the customer's on-site upgrade personnel through the test release module. The latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages;

[0029] The customer's on-site upgrade personnel manually perform the following operations to complete the online upgrade of the rpm package:

[0030] Append the repaired rpm package to the Update / Packages directory of the YUM source;

[0031] Replace the original Update / repodata index package with the latest repodata index package;

[0032] Clear the YUM cache on your local machine;

[0033] Upgrade the repaired rpm package.

[0034] Optionally, the software source upgrade device involved further includes a rollback operation module;

[0035] If a problem is found in the repaired rpm package during the upgrade phase, the customer's on-site upgrade personnel will perform a rollback operation through the rollback operation module. The specific steps are as follows:

[0036] Delete the repaired rpm package;

[0037] Replace the latest Update / repodata index package with the original Update / repodata index package.

[0038] The software source upgrade method and device based on the trust creation environment of the present invention have the following beneficial effects compared with the prior art:

[0039] 1. The present invention can manage and maintain YUM software sources in the Linux operating system to support the installation, update and version control of software packages, so as to solve the problem that the YUM source occupies too much space and the customer's on-site upgrade is difficult, and at the same time realize the efficient management of software sources, improve system management efficiency and software security;

[0040] 2. When the YUM source needs to be upgraded, the present invention can directly upgrade the incremental part without the need for an overall full upgrade, thereby reducing the data transmission volume of the YUM source upgrade and increasing the upgrade speed; when software package vulnerabilities continue to appear, the repair speed can be effectively increased. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Attached Figure 1 is a flow chart of a method according to Embodiment 1 of the present invention;

[0042] Attached Figure 2 This is a module connection block diagram of the second embodiment of the present invention. DETAILED DESCRIPTION

[0043] In order to make the technical solution, the technical problem solved and the technical effect of the present invention more clearly understood, the technical solution of the present invention is clearly and completely described below in conjunction with specific embodiments.

[0044] Embodiment 1:

[0045] Combined with Figure 1 This embodiment proposes a software source upgrade method based on a trusted innovation environment, which includes:

[0046] (I) During the development phase:

[0047] (1.1) The developer packages the entire YUM source and sends it to the tester.

[0048] (1.2) Testers test the entire YUM source package and report any bugs they find during testing to developers, who then fix the bugs and put the fixed rpm package into the Update / Packages directory of the YUM source.

[0049] (1.3) After the test is completed, the tester obtains the full package of the YUM source from the specified Update / Packages directory, generates a YUM source product package, and releases it to the customer's on-site upgrade personnel. The full package of the YUM source includes all the rpm packages to be released and the metadata for the YUM source.

[0050] (ii) During the upgrade phase:

[0051] (2.1) When the rpm package needs to be upgraded, the developer provides the repaired rpm package, and the tester appends the repaired rpm package to the specified Update / Packages directory and generates the latest Update / repodata index.

[0052] The command to generate repodata is as follows:

[0053] cd Update / ;createrepo. /

[0054] (2.2) After completing the test of the repaired rpm package, the tester will release the repaired rpm package and the latest epodata index package to the customer's on-site upgrade personnel. The latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages.

[0055] (2.3) The customer's on-site upgrade personnel perform the following operations to complete the online upgrade of the rpm package:

[0056] Append the repaired rpm package to the Update / Packages directory of the YUM source;

[0057] Replace the original Update / repodata index package with the latest repodata index package;

[0058] Use the yum clean all command to clear the YUM cache on the local computer;

[0059] Upgrade the repaired rpm package. Take openssh package upgrade as an example. Run yum update openssh. The yum command will search for the highest version of openssh package in the repodata index in the YUM source: penssh-8.8p1-23.oe2203sp1.x86_64.rpm. If the local version is lower than the version in the yum source, you can execute the upgrade task to upgrade the local version to openssh-8.8p1-23.oe2203sp1.x86_64.

[0060] (III) If a problem is found in the repaired rpm package during the upgrade phase, a rollback operation is performed as follows:

[0061] Delete the repaired rpm package;

[0062] Replace the latest Update / repodata index package with the original Update / repodata index package.

[0063] Embodiment 2:

[0064] Combined with Figure 2 This embodiment proposes a software source upgrade device based on a trusted innovation environment, which includes:

[0065] Role login module, used for users to log in to the operation page as developers or testers;

[0066] The package repair module is deployed on the operation page. It is used by developers to package the entire YUM source and send it to testers during the development phase. It is also used by developers to fix bugs and put the repaired rpm package into the specified directory of the YUM source.

[0067] Feedback release module, deployed on the operation page, is used by testers to feedback bugs found during the YUM source full package test to developers during the development phase. It is also used to obtain the full package of the YUM source from the specified Update / Packages directory after all tests pass, generate the YUM source product package, and release it to the customer's on-site upgrade personnel. The full package of the YUM source includes all the rpm packages to be released and the metadata for the YUM source;

[0068] The test generation module is deployed on the operation page. When the rpm package needs to be upgraded, it is used to append the rpm package repaired by the developer to the specified Update / Packages directory and generate the latest pdate / repodata index;

[0069] The test release module is deployed on the operation page and is used by testers to test the repaired rpm package. After the test is qualified, the repaired rpm package and the latest repodata index package are released to the customer's on-site upgrade personnel. The customer's on-site upgrade personnel complete the upgrade of the rpm package online. Among them, the latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages.

[0070] In this embodiment, the customer on-site upgrade personnel manually perform the following operations to complete the online upgrade of the rpm package:

[0071] Append the repaired rpm package to the Update / Packages directory of the YUM source;

[0072] Replace the original Update / repodata index package with the latest repodata index package;

[0073] Use the yum clean all command to clear the YUM cache on the local computer;

[0074] Upgrade the repaired rpm package. Take openssh package upgrade as an example. Run yum update openssh. The yum command will search for the highest version of openssh package in the repodata index in the YUM source: penssh-8.8p1-23.oe2203sp1.x86_64.rpm. If the local version is lower than the version in the yum source, you can execute the upgrade task to upgrade the local version to openssh-8.8p1-23.oe2203sp1.x86_64.

[0075] It should be added that the software source upgrade device involved also includes a rollback operation module;

[0076] If a problem is found in the repaired rpm package during the upgrade phase, the customer's on-site upgrade personnel will perform a rollback operation through the rollback operation module. The specific steps are as follows:

[0077] Delete the repaired rpm package;

[0078] Replace the latest Update / repodata index package with the original Update / repodata index package.

[0079] In summary, by adopting the software source upgrade method and device based on the trusted innovation environment of the present invention, when the YUM source needs to be upgraded, the incremental part can be upgraded directly without the need for an overall full upgrade, thereby reducing the data transmission volume of the YUM source upgrade and improving the upgrade speed; when software package vulnerabilities continue to appear, the repair speed can be effectively improved.

[0080] The above specific examples are used to explain the principles and implementation methods of the present invention in detail. These examples are only used to help understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made by technicians in this technical field without departing from the principles of the present invention should fall within the scope of patent protection of the present invention.

Claims

1. A software source upgrade method based on a trusted innovation environment, characterized in that: The steps include: During the development phase, developers package the full YUM source package and send it to testers. Testers test the full YUM source package and report any bugs they find to developers. Developers then fix the bugs and put the fixed rpm package into the specified directory of the YUM source. After the test is completed, testers obtain the full YUM source package from the specified directory, generate a YUM source product package, and release it to the customer's on-site upgrade personnel. During the upgrade phase, when the rpm package needs to be upgraded, the developer provides the repaired rpm package, and the tester appends the repaired rpm package to the specified directory of the YUM source and generates the latest index; after completing the test of the repaired rpm package, the tester releases the repaired rpm package and the latest index package to the customer's on-site upgrade personnel, who complete the upgrade of the rpm package online.

2. According to the software source upgrade method based on the trusted innovation environment as described in claim 1, it is characterized in that: During the development phase, testers test the full package of the YUM source and report any bugs they find to developers. The developers then fix the bugs and put the fixed rpm package into the Update / Packages directory of the YUM source. After the test is completed, testers obtain the full package of the YUM source from the Update / Packages directory and generate a YUM source product package, where the full package of the YUM source includes all rpm packages to be released and metadata for the YUM source.

3. According to a method for upgrading software sources based on a trusted innovation environment as described in claim 2, it is characterized in that: During the upgrade phase, the tester will add the repaired rpm package to the Update / Packages directory of the YUM source and generate the latest Update / repodata index. After the test is completed, the tester will release the repaired rpm package and the latest repodata index package to the customer's on-site upgrade personnel. The latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages. The customer's on-site upgrade personnel perform the following operations to complete the online upgrade of the rpm package: Append the repaired rpm package to the Update / Packages directory of the YUM source; Replace the original Update / repodata index package with the latest repodata index package; Clear the YUM cache on your local machine; Upgrade the repaired rpm package.

4. According to a method for upgrading software sources based on a trusted innovation environment as described in claim 1, it is characterized in that: If a problem is found in the repaired rpm package during the upgrade phase, a rollback operation is performed.

5. According to the software source upgrade method based on the trusted innovation environment as described in claim 4, it is characterized in that: If a problem is found in the repaired rpm package during the upgrade phase, a rollback operation is performed as follows: Delete the repaired rpm package; Replace the latest Update / repodata index package with the original Update / repodata index package.

6. A software source upgrade device based on a trusted innovation environment, characterized in that: It includes: Role login module, used for users to log in to the operation page as developers or testers; The package repair module is deployed on the operation page. It is used by developers to package the entire YUM source and send it to testers during the development phase. It is also used by developers to fix bugs and put the repaired rpm package into the specified directory of the YUM source. Feedback release module, deployed on the operation page, is used by testers to feedback bugs found during the YUM source full package testing process to developers during the development phase. It is also used to obtain the full package of the YUM source from the specified directory after the test is completed, generate the YUM source product package, and release it to the customer's on-site upgrade personnel; The test generation module is deployed on the operation page. When the rpm package needs to be upgraded, it is used for testers to append the repaired rpm package to the specified directory of the YUM source and generate the latest index; The test release module is deployed on the operation page and is used by testers to test the repaired rpm package. After the test is qualified, the repaired rpm package and the latest index package are released to the customer's on-site upgrade personnel. The customer's on-site upgrade personnel complete the upgrade of the rpm package online.

7. A software source upgrade device based on a trusted innovation environment according to claim 6, characterized in that: During the development phase, developers use the packaging and repair module to put the repaired rpm package into the Update / Packages directory of the YUM source. After the test is completed, the tester obtains the full package of the YUM source from the Update / Packages directory through the feedback release module to generate a YUM source product package. The full package of the YUM source includes all the rpm packages to be released and the metadata for the YUM source.

8. According to claim 7, a software source upgrade device based on a trusted innovation environment is characterized in that: During the upgrade phase, the tester adds the repaired rpm package to the Update / Packages directory of the YUM source through the test generation module and generates the latest Update / repodata index; After the test is completed, the tester releases the repaired rpm package and the latest repodata index package to the customer's on-site upgrade personnel through the test release module. The latest repodata index package contains a compressed file or directory of all software package metadata, which is used to let the YUM source know which software packages are available and the detailed information of these software packages; The customer's on-site upgrade personnel manually perform the following operations to complete the online upgrade of the rpm package: Append the repaired rpm package to the Update / Packages directory of the YUM source; Replace the original Update / repodata index package with the latest repodata index package; Clear the YUM cache on your local machine; Upgrade the repaired rpm package.

9. A software source upgrade device based on a trusted innovation environment according to claim 6, characterized in that: The device also includes a rollback operation module; When a problem is found in the repaired rpm package during the upgrade phase, the customer's on-site upgrade personnel can perform a rollback operation through the rollback operation module.

10. A software source upgrade device based on a trusted innovation environment according to claim 9, characterized in that: The specific steps of the rollback operation module to perform the rollback operation are: Delete the repaired rpm package; Replace the latest Update / repodata index package with the original Update / repodata index package.

Images