Distributed software management system and method for carrier rocket, equipment and storage medium

Abstract

The invention discloses a distributed software management system and method for a carrier rocket, equipment and a storage medium, and belongs to the field of computers.The distributed software management system for the carrier rocket comprises a configuration side, a server side, a registration management module and a client side which are arranged in the same subnet; the configuration end is used for providing software distribution, uploading configuration files, controlling software versions and managing permissions; the configuration end can upload data including software, configuration files, users and permissions to the server; the server side is used for carrying out distributed storage, data management and proofreading on the uploaded data; the client is used for initiating a request to the server to download, unload and update a file; requests sent by the configuration side, the server side and the client side are distributed by the registration management module. According to the method, manual deployment is not needed during software deployment, one-button deployment can be realized, the software deployment time is effectively shortened, and the software deployment efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a distributed software management system, method, device and storage medium for launch vehicles. Background Art

[0002] In the current rocket software design field, due to security and confidentiality reasons, all software configuration items are produced from the product library, and then entered into the operating computer one by one through media such as CDs. Even if only the configuration file is updated, it still needs to be entered manually. Although it meets the confidentiality requirements, the process requires a lot of manpower and time. If the computers that need to deploy the software are in different places, the deployment cost will increase exponentially.

[0003] In view of this, it is necessary to provide a new technical solution to solve the above problems. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a launch vehicle distributed software management system and method, equipment, and storage medium, which no longer requires manual deployment when deploying software, and can achieve one-click deployment, effectively reducing software deployment time and improving software deployment efficiency.

[0005] A launch vehicle distributed software management system includes a configuration terminal, a service terminal, a registration management module and a client terminal arranged in the same subnet; The configuration end is used to provide software distribution, configuration file upload, software version control and permission management; the configuration end can upload data including software, configuration files, users, and permissions to the server end; The server is provided with a database for distributed storage, data management and proofreading of uploaded data; The client is used to initiate a request to the server to download, uninstall and update files; The requests sent by the configuration end, the service end and the client end are allocated by a registration management module.

[0006] Preferably, when starting up, the client, the configuration end and the server end all connect to the registration management module to register their own IP addresses and states.

[0007] Preferably, the configuration terminal needs to be logged in with administrator privileges when in use.

[0008] Preferably, the client has an automatic verification function for verifying the software version and configuration information.

[0009] Preferably, the client has a user authority filtering function for displaying the software that the user can use according to the user authority.

[0010] According to another aspect of the present application, a launch vehicle distributed software management method is also provided, and software management is performed using the launch vehicle distributed software management system, including: When the system starts, the client, configuration end, and server end all connect to the registration management module and register their own IP and status through the registration management module; After the client, configuration end, and server are all registered, a single configuration end uploads data, and the server uses the Hbase database to store the files and information data in the data uploaded by the configuration end in a distributed manner; When the client downloads or updates the software, the registration management module assigns the client to the corresponding server and establishes a link. The corresponding server sends information data to the client, and the client downloads the corresponding file for software installation.

[0011] Preferably, when the client downloads or updates the software, the registration management module assigns the client to the corresponding server and establishes a link, the corresponding server sends information data to the client, and the client downloads the corresponding file for software installation, including: When a single client downloads or updates software, the registration management module randomly assigns a server to establish a connection with it. The corresponding server sends the information data to the client in the form of TCP. After the client reads the information data, it downloads the file through its built-in Hbase database port. When multiple clients download or update software at the same time, the registration management module assigns different clients to different servers through the least connection algorithm, and connects different clients to their corresponding servers. The corresponding server sends information data to the client in the form of TCP. After the client reads the information data, it downloads the file through its built-in Hbase database port.

[0012] According to another aspect of the present application, a computing device is also provided, including: a processor and a memory storing a computer program, wherein when the computer program is run by the processor, the launch vehicle distributed software management method is executed.

[0013] According to another aspect of the present application, a computer-readable storage medium is also provided, on which computer instructions are stored. When the instructions are executed on a computer, the computer executes the launch vehicle distributed software management method.

[0014] Compared with the prior art, this application has at least the following beneficial effects: 1. The launch vehicle distributed software management system of the present invention no longer requires manual deployment when deploying launch vehicle related software, and can achieve one-click deployment, effectively reducing software deployment time and improving software deployment efficiency.

[0015] 2. The launch vehicle distributed software management system of the present invention only requires one subnet for deployment and does not require access to the external Internet, thereby ensuring the necessary security environment for the launch vehicle system.

[0016] 3. The launch vehicle distributed software management system of the present invention has the function of authority management. Untrusted users can log in to the relevant computers and still cannot operate the relevant software without knowing the passwords of other authorized users, thus ensuring overall security. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Hereinafter, some specific embodiments of the present invention will be described in detail in an exemplary and non-limiting manner with reference to the accompanying drawings. The same reference numerals in the accompanying drawings indicate the same or similar components or parts. It should be understood by those skilled in the art that these drawings are not necessarily drawn to scale. In the accompanying drawings: Figure 1 The figure is a schematic diagram of module connections of the distributed software management system for launch vehicles of the present invention.

[0018] The above drawings include the following reference numerals: 10. Configuration end; 20. Server end; 30. Registration management module; 40. Client end. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0020] like Figure 1 As shown, a launch vehicle distributed software management system includes a configuration terminal 10, a service terminal 20, a registration management module 30 and a client terminal 40 arranged in the same subnet; The configuration terminal 10 is used to provide software distribution, configuration file upload, software version control and permission management; the configuration terminal 10 can upload data including software, configuration files, users, and permissions to the server 20.

[0021] The server 20 is provided with a database for distributed storage, data management and proofreading of uploaded data.

[0022] The client 40 is used to initiate a request to the server 20 to download, uninstall and update files.

[0023] The requests sent by the configuration end 10 , the service end 20 and the client end 40 are allocated by the registration management module 30 .

[0024] There may be several server terminals 20 and client terminals 40. The registration management module 30 is a distributed registration management module. When a service instance is started, it will actively send a registration request containing its own key information to the registration management module 30. When the client terminal 40, the configuration terminal 10 and the server terminal 20 are started, they all connect to the registration management module 30 to register their own IP addresses and status.

[0025] By uploading the software configuration item to the server 20, and then installing it with one click on the client 40 on the computer to be deployed, the software deployment efficiency is effectively improved. In addition, by uploading the software configuration item to the server 20, and then updating it with one click on the client 40 on the computer to be deployed, or by forcibly updating the client software on the server, the software update efficiency can be effectively improved.

[0026] Preferably, the configuration terminal 10 needs to be logged in with administrator privileges when in use.

[0027] Preferably, both the client 40 and the server 20 have an automatic verification function for verifying the software version and configuration information. During deployment and updating, the server 20 and the client 40 perform automatic verification, and avoid errors during manual verification through the computer's automatic verification algorithm. The automatic verification function of the client 40 can ensure the smooth operation of the client application, which is an important means to improve user experience and maintain system security.

[0028] Preferably, the client 40 has a user authority filtering function that displays the software that can be used according to the user authority. By logging in different users, the authority is isolated to ensure security.

[0029] Based on the same inventive idea, the present application also provides a launch vehicle distributed software management method, which uses the launch vehicle distributed software management system to perform software management, including: When the system starts, the client 40, the configuration terminal 10 and the server 20 are all connected to the registration management module 30, and register their own IP and status through the registration management module 30; After the client 40, the configuration terminal 10 and the server 20 are all registered, a single configuration terminal 10 uploads data, and the server 20 stores the files and information data in the data uploaded by the configuration terminal 10 in a distributed manner through the Hbase database.

[0030] When the client 40 downloads or updates software, the registration management module 30 assigns the client 40 to the corresponding server 20 and establishes a link. The corresponding server 20 sends information data to the client 40, and the client 40 downloads the corresponding file for software installation.

[0031] The requests from the client 40 , the configuration terminal 10 and the server 20 are distributed by the registration management module 30 , so as to ensure the flow balance and network fault tolerance when multiple clients 40 download.

[0032] Specifically, when a single client 40 downloads or updates software, the registration management module 30 randomly assigns a server 20 to establish a link with it, and the corresponding server 20 sends information data to the client 40 in the form of TCP. After the client 40 reads the information data, it downloads the file through its built-in Hbase database port.

[0033] When multiple clients 40 are downloading or updating software at the same time, the registration management module 30 assigns different clients 40 to different servers 20 through the least connection algorithm, and connects different clients 40 with their corresponding servers 20. The corresponding server 20 sends the information data to the client 40 in the form of TCP. After the client 40 reads the information data, it downloads the file through its built-in Hbase database port.

[0034] For ease of description, spatially relative terms such as "above", "above", "on the upper surface of", "above", etc. may be used here to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" can include both "above" and "below". The device can also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatially relative descriptions used here are interpreted accordingly.

[0035] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0037] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A distributed software management system for launch vehicles, characterized in that: It includes a configuration terminal, a server terminal, a registration management module and a client terminal which are set in the same subnet; The configuration end is used to provide software distribution, configuration file upload, software version control and permission management; the configuration end can upload data including software, configuration files, users, and permissions to the server end; The server is provided with a database for distributed storage, data management and proofreading of uploaded data; The client is used to initiate a request to the server to download, uninstall and update files; The requests sent by the configuration end, the service end and the client end are allocated by a registration management module.

2. The launch vehicle distributed software management system according to claim 1, characterized in that: When starting up, the client, the configuration end and the server end all connect to the registration management module to register their own IP addresses and states.

3. The launch vehicle distributed software management system according to claim 1, characterized in that: The configuration terminal needs to be logged in with administrator privileges when in use.

4. The launch vehicle distributed software management system according to claim 1, characterized in that: The client has an automatic verification function for verifying the software version and configuration information.

5. The launch vehicle distributed software management system according to claim 4, characterized in that: The client has a user authority filtering function that displays the software that the user can use according to the user authority.

6. A method for distributed software management of a launch vehicle, characterized in that: Using the launch vehicle distributed software management system according to any one of claims 1 to 5 to perform software management, comprising: When the system starts, the client, configuration end, and server end all connect to the registration management module and register their own IP and status through the registration management module; After the client, configuration end, and server are all registered, a single configuration end uploads data, and the server uses the Hbase database to store the files and information data in the data uploaded by the configuration end in a distributed manner; When the client downloads or updates the software, the registration management module assigns the client to the corresponding server and establishes a link. The corresponding server sends information data to the client, and the client downloads the corresponding file for software installation.

7. The launch vehicle distributed software management method according to claim 6, characterized in that: When the client downloads or updates the software, the registration management module assigns the client to the corresponding server and establishes a link. The corresponding server sends information data to the client, and the client downloads the corresponding file for software installation, including: When a single client downloads or updates software, the registration management module randomly assigns a server to establish a connection with it. The corresponding server sends the information data to the client in the form of TCP. After the client reads the information data, it downloads the file through its built-in Hbase database port. When multiple clients download or update software at the same time, the registration management module assigns different clients to different servers through the least connection algorithm, and connects different clients to their corresponding servers. The corresponding server sends information data to the client in the form of TCP. After the client reads the information data, it downloads the file through its built-in Hbase database port.

8. A computing device, characterized in that include: A processor and a memory storing a computer program, wherein when the computer program is executed by the processor, the launch vehicle distributed software management method as described in claim 6 or 7 is executed.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the instructions are executed on a computer, the computer executes the launch vehicle distributed software management method as described in claim 6 or 7.

Images