CN117251192A - Method, device, equipment and storage medium for managing enterprise-level system - Google Patents
Method, device, equipment and storage medium for managing enterprise-level system Download PDFInfo
- Publication number
- CN117251192A CN117251192A CN202311308920.5A CN202311308920A CN117251192A CN 117251192 A CN117251192 A CN 117251192A CN 202311308920 A CN202311308920 A CN 202311308920A CN 117251192 A CN117251192 A CN 117251192A
- Authority
- CN
- China
- Prior art keywords
- update
- updating
- enterprise
- deliverables
- managing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000012384 transportation and delivery Methods 0.000 claims abstract description 39
- 238000007726 management method Methods 0.000 claims abstract description 37
- 230000008569 process Effects 0.000 claims abstract description 26
- 238000012423 maintenance Methods 0.000 claims abstract description 18
- 238000011161 development Methods 0.000 claims abstract description 16
- 238000004519 manufacturing process Methods 0.000 claims description 13
- 238000012360 testing method Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 230000009286 beneficial effect Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 20
- 230000018109 developmental process Effects 0.000 description 12
- 230000000694 effects Effects 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000033772 system development Effects 0.000 description 2
- 238000003326 Quality management system Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000002071 nanotube Substances 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
-
- 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
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method, a device, equipment and a storage medium for managing an enterprise-level system, wherein the method comprises the following steps: defining relationships and hierarchies among the nodes to form a topological structure; determining deliverables involved in the development and operation processes, and submitting the deliverables to a public warehouse for management; calculating an updating flow required in the operation and maintenance process, and establishing association among the topological structure, the deliverables and the updating flow; and arranging the topological structure and the update sequence of the delivery object to realize system update. The invention can effectively manage topology, delivery and update flow, has the advantages of automatic management and cross-platform applicability, is beneficial to improving the efficiency and reliability of enterprise-level system management, reduces the management cost and has wide application prospect.
Description
Technical Field
The present invention relates to the field of distributed file systems, and more particularly, to a method, apparatus, device, and storage medium for managing enterprise-level systems.
Background
With the development of business digitization of various industries, more and more enterprises realize business informatization, and more businesses are supported based on an information system, so that the requirements on topology management and update flow management of the information system are higher and higher in order to ensure the normal operation of the businesses. The topology describes the relation among all components in the system, the deliverables refer to the contents such as software, configuration files, documents and the like related in the process of system development and operation and maintenance, and the update flow refers to the update operation required in the process of system operation and maintenance, including software update, configuration update and the like. How to manage these three aspects is critical to ensure the stability and reliability of the system. In view of this requirement, the requirements for reasonably dividing the topology of an information system and providing an update flow for canonical automation are becoming higher and higher:
(1) Along with the change of the system service scene, the topology nodes of the nanotubes can be changed continuously;
(2) After the service is expanded, a new service system is brought into the management range after being brought on line;
(3) According to the split micro-service condition of the service system, the dependence needs to be automatically calculated among deliverables during updating;
(4) The enterprise is unavoidably provided with personnel flowing and adjusting, and the authority of the topological node of the user needs to be adjusted accordingly;
(5) With the expansion of the scale of the business system, faster system update speed and automatic update task execution are required;
(6) The service system is high in availability and does not stop the scene, and the system update is required to realize gray level update.
Disclosure of Invention
In view of the above, an object of the embodiments of the present invention is to provide a method, an apparatus, an electronic device, and a computer readable storage medium for managing an enterprise-level system, which can effectively manage topology, deliverables, and update flows, and has advantages of automatic management and cross-platform applicability, thereby being beneficial to improving efficiency and reliability of enterprise-level system management, reducing management cost, and having wide application prospects.
Based on the above objects, an aspect of an embodiment of the present invention provides a method for managing an enterprise-level system, including the steps of: defining relationships and hierarchies among the nodes to form a topological structure; determining deliverables involved in the development and operation processes, and submitting the deliverables to a public warehouse for management; calculating an updating flow required in the operation and maintenance process, and establishing association among the topological structure, the deliverables and the updating flow; and arranging the topological structure and the update sequence of the delivery object to realize system update.
In some embodiments, the method further comprises: the authority of the topology node which can be managed by the user is determined based on the grade and the service type of the user.
In some embodiments, the step of arranging the topology and the update order of the deliveries to achieve a system update comprises: the update tasks are divided into a plurality of subgroups, and the update tasks of each subgroup are carried out in batches, so that the update can be completed under the condition that the system is not stopped.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: the system is divided into a development environment, a test environment, a quasi-production environment and a production environment, and corresponding micro services are associated with each environment.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: and associating the micro services with the corresponding databases and application nodes, and grouping the micro services according to the deployment updating mode.
In some embodiments, the method further comprises: responding to the update, calculating the micro-service related to the update, and determining the delivery to be updated under the micro-service; and arranging the update sequence of the micro-service and arranging the update sequence of the deliverables in the micro-service to form the update instruction.
In some embodiments, the step of submitting the deliverables to a public warehouse for management comprises: the deliverables are divided into a plurality of steps according to the business scene, and each step corresponds to a different level.
In another aspect of an embodiment of the present invention, there is provided an apparatus for managing an enterprise-level system, including: the topology module is used for defining the relation and the hierarchical structure among the nodes to form a topology structure; the delivery module is used for determining delivery matters involved in the development and operation and maintenance processes and submitting the delivery matters to a public warehouse for management; the association module is used for calculating an update flow required in the operation and maintenance process and establishing association among the topological structure, the deliverables and the update flow; and the updating module is used for arranging the topological structure and the updating sequence of the delivery object so as to realize system updating.
In still another aspect of the embodiment of the present invention, there is also provided an electronic device, including: at least one processor; and a memory storing computer instructions executable on the processor, which when executed by the processor, perform the steps of the method as above.
In yet another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements the method steps as described above.
The invention has the following beneficial technical effects: the system can effectively manage topology, deliverables and update flows, has the advantages of automatic management and cross-platform applicability, is beneficial to improving the efficiency and reliability of enterprise-level system management, reduces management cost, and has wide application prospect.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention and that other embodiments may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an embodiment of a method of managing an enterprise-level system provided by the present invention;
FIG. 2a is a schematic diagram of server information defining a topology structure according to the present invention;
FIG. 2b is a schematic diagram of system information defining a topology according to the present invention;
FIG. 2c is a schematic diagram of defining a micro-service topology according to the present invention;
FIG. 3a is a schematic diagram of an arrangement update task provided by the present invention;
FIG. 3b is a schematic view of a patch application approval provided by the present invention;
FIG. 3c is a schematic diagram of a patch installation record provided by the present invention;
FIG. 4a is a schematic diagram illustrating a local patch management scheme according to the present invention;
FIG. 4b is a schematic illustration of a micro-service help provided by the present invention;
FIG. 4c is a tool update schematic diagram according to the present invention;
FIG. 5 is a schematic diagram of an embodiment of a system for managing enterprise-level systems provided by the present invention;
FIG. 6 is a schematic diagram of a hardware architecture of an embodiment of an electronic device for managing an enterprise-level system according to the present invention;
FIG. 7 is a schematic diagram of an embodiment of a computer storage medium for managing an enterprise-level system in accordance with the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention will be described in further detail with reference to the accompanying drawings.
It should be noted that, in the embodiments of the present invention, all the expressions "first" and "second" are used to distinguish two entities with the same name but different entities or different parameters, and it is noted that the "first" and "second" are only used for convenience of expression, and should not be construed as limiting the embodiments of the present invention, and the following embodiments are not described one by one.
In a first aspect of embodiments of the present invention, an embodiment of a method of managing an enterprise-level system is presented. FIG. 1 is a schematic diagram illustrating one embodiment of a method of managing an enterprise-level system provided by the present invention. As shown in fig. 1, the embodiment of the present invention includes the following steps:
s1, defining a relation and a hierarchical structure among nodes to form a topological structure;
s2, determining deliverables involved in the development and operation processes, and submitting the deliverables to a public warehouse for management;
s3, calculating an updating flow required in the operation and maintenance process, and establishing association among the topological structure, the deliverables and the updating flow; and
s4, arranging the topological structure and the update sequence of the delivery object to realize system update.
The embodiment of the invention comprises the steps of defining a topological structure, delivering objects and updating flows, establishing association among the topological structure, delivering objects and updating flows, realizing automatic management, realizing cross-platform applicability and the like. The embodiment of the invention can effectively manage the topological structure, the delivery and the updating flow, has the advantages of automatic management and cross-platform applicability, is beneficial to improving the efficiency and reliability of enterprise-level system management, reduces the management cost and has wide application prospect.
Relationships and hierarchies between the various nodes are defined to form a topology. Relationships and hierarchies between nodes are defined in the system, including information on the type, name, IP address, associated microservices, application nodes, databases, etc. of the system. Such information may be entered manually, automatically discovered, or otherwise obtained. Through the topological association relationship, the expandability and maintainability of the system are ensured, so that the topological structure can be quickly adjusted when the service changes.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: the system is divided into a development environment, a test environment, a quasi-production environment and a production environment, and corresponding micro services are associated with each environment. Configuration of system topology: the system consists of one or more micro-services, and is characterized in that development environments, test environments, quasi-production environments and production environments are distinguished, and the corresponding micro-services are associated after the system definition is finished.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: and associating the micro services with the corresponding databases and application nodes, and grouping the micro services according to the deployment updating mode. Configuration of micro service topology: the micro-service definition is used for managing micro-services in the system, describing the associated database and application nodes, and grouping the micro-services according to different deployment updating modes.
Configuration of server nodes: the service node management function is mainly used for managing server information, an ip of a server to be maintained, a communication port (a starting port of a client) and an operating system type.
The deliverables involved in the development and operation process are determined and submitted to a public warehouse for management. In the process of system development and operation and maintenance, related software, configuration files, documents and other contents need to be managed, including information such as the type, name and version of the deliverables. The developer submits the deliveries to a common warehouse for administration. When the delivery is managed, the quality and reliability of the delivery are ensured through problems such as flow version, upgrading strategy, testing and the like. The embodiment of the invention provides the management capability of various delivery articles such as installation discs, patches, tool kits, mirror images and the like, and standardizes the management flow of the articles. The embodiment of the invention provides full life cycle management of delivery materials from production, uploading, testing, verification and release, and the process covers multiple roles of developers, testers, operation and maintenance personnel and the like. And the deployment center is opened, so that the automation and standardization of the whole process from the product library to the deployment are realized, and the project falling quality management system is assisted.
In some embodiments, the step of submitting the deliverables to a public warehouse for management comprises: the deliverables are divided into a plurality of steps according to the business scene, and each step corresponds to a different level.
In some embodiments, the method further comprises: the authority of the topology node which can be managed by the user is determined based on the grade and the service type of the user. User data authority configuration: different topology node rights possessed by the user are configured. In an enterprise-level system, different users may have different topology node rights. The method can realize the topology authority management based on the user, so that the user authority can be quickly adjusted when the personnel flow or adjust, and the safety and stability of the system are ensured.
In some embodiments, the method further comprises: responding to the update, calculating the micro-service related to the update, and determining the delivery to be updated under the micro-service; and arranging the update sequence of the micro-service and arranging the update sequence of the deliverables in the micro-service to form the update instruction. Updating task arrangement: each time of updating needs to create a task, a delivery to be updated under a micro-service is selected by taking the micro-service as granularity, the micro-service related to the updating of the current time is automatically calculated, the updating sequence of the micro-service is arranged, and finally, an updating instruction in the task is formed.
And calculating an updating flow required in the operation and maintenance process, and establishing the association among the topological structure, the delivery object and the updating flow. In the operation and maintenance process of the system, updating operations including software updating, configuration updating and the like are required. By automatically calculating the update operation required in the operation and maintenance process of the system, the association among the topology, the deliverables and the update flow is established. By automatically arranging the topological nodes and the updating sequence of the contents of the deliveries, the automatic updating of the system is realized. Meanwhile, the task can be automatically updated at regular time through the configuration of the planning task, so that the updating efficiency is improved.
And arranging the topological structure and the updating sequence of the delivery objects to realize system updating.
In some embodiments, the step of arranging the topology and the update order of the deliveries to achieve a system update comprises: the update tasks are divided into a plurality of subgroups, and the update tasks of each subgroup are carried out in batches, so that the update can be completed under the condition that the system is not stopped.
In the high availability non-stop scene of the service system, the stability of the system needs to be ensured. And the updating tasks are batched in a mode of shunting, defining an updating group and the like, so that the gray level updating of the service system is realized. Meanwhile, various indexes in the updating process need to be monitored in real time so as to discover and solve the problems in time.
Topology table design:
topological association relation:
| fields | Type(s) | Description of the invention |
| id | varchar | Main key |
| childid | varchar | Associated sub-level primary key |
| childtype | varchar | Associated sub-level types |
| parentid | varchar | Parent primary key |
Updating the task table structure:
FIG. 2a is a schematic diagram of server information defining a topology structure according to the present invention; FIG. 2b is a schematic diagram of system information defining a topology according to the present invention; FIG. 2c is a schematic diagram of defining a micro-service topology according to the present invention; referring to fig. 2a, 2b and 2c, the defined topology in the embodiment of the present invention includes: newly creating a server node and filling in basic information; newly building a system topology, filling topology basic information, associating micro-services, associating server nodes and the like; newly creating a micro service, filling topology basic information, and associating application nodes and a database.
FIG. 3a is a schematic diagram of an arrangement update task provided by the present invention; FIG. 3b is a schematic view of a patch application approval provided by the present invention; FIG. 3c is a schematic diagram of a patch installation record provided by the present invention; referring to fig. 3a, 3b and 3c, the update task orchestration in an embodiment of the present invention comprises: creating an update task, an update flow approval and an update progress result.
FIG. 4a is a schematic diagram illustrating a local patch management scheme according to the present invention; FIG. 4b is a schematic illustration of a micro-service help provided by the present invention; FIG. 4c is a tool update schematic diagram according to the present invention; referring to fig. 4a, 4b and 4c, the delivery management in the embodiment of the present invention includes: the user divides the collected monitoring data into a plurality of steps according to the specific scene of the user, and each step corresponds to different corresponding levels.
It should be noted that, the steps in the embodiments of the method for managing an enterprise-level system may be intersected, replaced, added and deleted, so that the method for managing an enterprise-level system by using these reasonable permutation and combination changes shall also fall within the scope of the present invention, and shall not limit the scope of the present invention to the embodiments.
With the above object in view, in a second aspect, an apparatus for managing an enterprise-level system is provided. As shown in fig. 5, the apparatus 200 includes the following modules: the topology module is used for defining the relation and the hierarchical structure among the nodes to form a topology structure; the delivery module is used for determining delivery matters involved in the development and operation and maintenance processes and submitting the delivery matters to a public warehouse for management; the association module is used for calculating an update flow required in the operation and maintenance process and establishing association among the topological structure, the deliverables and the update flow; and the updating module is used for arranging the topological structure and the updating sequence of the delivery object so as to realize system updating.
In some embodiments, the apparatus further comprises a rights module for: the authority of the topology node which can be managed by the user is determined based on the grade and the service type of the user.
In some embodiments, the update module is further to: the update tasks are divided into a plurality of subgroups, and the update tasks of each subgroup are carried out in batches, so that the update can be completed under the condition that the system is not stopped.
In some embodiments, the topology module is further to: the system is divided into a development environment, a test environment, a quasi-production environment and a production environment, and corresponding micro services are associated with each environment.
In some embodiments, the topology module is further to: and associating the micro services with the corresponding databases and application nodes, and grouping the micro services according to the deployment updating mode.
In some embodiments, the apparatus further comprises an instruction module for: responding to the update, calculating the micro-service related to the update, and determining the delivery to be updated under the micro-service; and arranging the update sequence of the micro-service and arranging the update sequence of the deliverables in the micro-service to form the update instruction.
In some embodiments, the delivery module is to: the deliverables are divided into a plurality of steps according to the business scene, and each step corresponds to a different level.
In view of the above object, a third aspect of an embodiment of the present invention provides an electronic device, including: at least one processor; and a memory storing computer instructions executable on the processor, the instructions being executable by the processor to perform the steps of: s1, defining a relation and a hierarchical structure among nodes to form a topological structure; s2, determining deliverables involved in the development and operation processes, and submitting the deliverables to a public warehouse for management; s3, calculating an updating flow required in the operation and maintenance process, and establishing association among the topological structure, the deliverables and the updating flow; and S4, arranging the topological structure and the update sequence of the delivery object to realize system update.
In some embodiments, the steps further comprise: the authority of the topology node which can be managed by the user is determined based on the grade and the service type of the user.
In some embodiments, the step of arranging the topology and the update order of the deliveries to achieve a system update comprises: the update tasks are divided into a plurality of subgroups, and the update tasks of each subgroup are carried out in batches, so that the update can be completed under the condition that the system is not stopped.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: the system is divided into a development environment, a test environment, a quasi-production environment and a production environment, and corresponding micro services are associated with each environment.
In some embodiments, the step of defining relationships and hierarchies between the various nodes to form a topology includes: and associating the micro services with the corresponding databases and application nodes, and grouping the micro services according to the deployment updating mode.
In some embodiments, the steps further comprise: responding to the update, calculating the micro-service related to the update, and determining the delivery to be updated under the micro-service; and arranging the update sequence of the micro-service and arranging the update sequence of the deliverables in the micro-service to form the update instruction.
In some embodiments, the step of submitting the deliverables to a public warehouse for management comprises: the deliverables are divided into a plurality of steps according to the business scene, and each step corresponds to a different level.
As shown in fig. 6, a hardware structure of an embodiment of the electronic device for managing an enterprise-level system according to the present invention is shown.
Taking the example of the apparatus shown in fig. 6, a processor 301 and a memory 302 are included in the apparatus.
The processor 301 and the memory 302 may be connected by a bus or otherwise, for example in fig. 6.
The memory 302 serves as a non-volatile computer readable storage medium, and may be used to store non-volatile software programs, non-volatile computer executable programs, and modules, such as program instructions/modules corresponding to the methods of managing enterprise-level systems in embodiments of the present application. Processor 301 performs various functional applications of the server and data processing, i.e., a method of managing the enterprise-level system, by running non-volatile software programs, instructions, and modules stored in memory 302.
Memory 302 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of a method of managing an enterprise-level system, etc. In addition, memory 302 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 302 may optionally include memory located remotely from processor 301, which may be connected to the local module via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more computer instructions 303 corresponding to a method of managing an enterprise-level system are stored in memory 302 that, when executed by processor 301, perform the method of managing an enterprise-level system in any of the method embodiments described above.
Any of the embodiments of an electronic device that performs the above-described method of managing an enterprise-level system may achieve the same or similar effects as any of the previously-described method embodiments that correspond thereto.
The present invention also provides a computer readable storage medium storing a computer program which when executed by a processor performs a method of managing an enterprise-level system.
FIG. 7 is a schematic diagram illustrating one embodiment of a computer storage medium for managing an enterprise-level system as described above. Taking a computer storage medium as shown in fig. 7 as an example, the computer readable storage medium 401 stores a computer program 402 that when executed by a processor performs the above method.
Finally, it should be noted that, as will be appreciated by those skilled in the art, implementing all or part of the above-described methods in the embodiments, the program for managing the method of the enterprise-level system may be stored in a computer-readable storage medium, and the program, when executed, may include the steps of the embodiments of the methods described above. The storage medium of the program may be a magnetic disk, an optical disk, a read-only memory (ROM), a random-access memory (RAM), or the like. The computer program embodiments described above may achieve the same or similar effects as any of the method embodiments described above.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The foregoing embodiment of the present invention has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, where the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the invention, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the invention, and many other variations of the different aspects of the embodiments of the invention as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present invention.
Claims (10)
1. A method of managing an enterprise-level system, comprising the steps of:
defining relationships and hierarchies among the nodes to form a topological structure;
determining deliverables involved in the development and operation processes, and submitting the deliverables to a public warehouse for management;
calculating an updating flow required in the operation and maintenance process, and establishing association among the topological structure, the deliverables and the updating flow; and
and arranging the topological structure and the updating sequence of the delivery objects to realize system updating.
2. The method of managing an enterprise-level system of claim 1, further comprising:
the authority of the topology node which can be managed by the user is determined based on the grade and the service type of the user.
3. The method of managing an enterprise-level system of claim 1, wherein the step of orchestrating the order of updating of the topology and the deliveries to achieve a system update comprises:
the update tasks are divided into a plurality of subgroups, and the update tasks of each subgroup are carried out in batches, so that the update can be completed under the condition that the system is not stopped.
4. The method of managing an enterprise-level system of claim 1, wherein the step of defining relationships and hierarchies between the individual nodes to form a topology comprises:
the system is divided into a development environment, a test environment, a quasi-production environment and a production environment, and corresponding micro services are associated with each environment.
5. The method of managing an enterprise-level system of claim 1, wherein the step of defining relationships and hierarchies between the individual nodes to form a topology comprises:
and associating the micro services with the corresponding databases and application nodes, and grouping the micro services according to the deployment updating mode.
6. The method of managing an enterprise-level system of claim 1, further comprising:
responding to the update, calculating the micro-service related to the update, and determining the delivery to be updated under the micro-service; and
and arranging the update sequence of the micro-service and arranging the update sequence of the deliverables in the micro-service to form the update instruction.
7. The method of managing an enterprise-level system of claim 1, wherein the step of submitting the deliverables to a public warehouse for management comprises:
the deliverables are divided into a plurality of steps according to the business scene, and each step corresponds to a different level.
8. An apparatus for managing an enterprise-level system, comprising:
the topology module is used for defining the relation and the hierarchical structure among the nodes to form a topology structure;
the delivery module is used for determining delivery matters involved in the development and operation and maintenance processes and submitting the delivery matters to a public warehouse for management;
the association module is used for calculating an update flow required in the operation and maintenance process and establishing association among the topological structure, the deliverables and the update flow; and
and the updating module is used for arranging the topological structure and the updating sequence of the delivery object so as to realize system updating.
9. A computer device, comprising:
at least one processor; and
a memory storing computer instructions executable on the processor, which when executed by the processor, perform the steps of the method of any one of claims 1-7.
10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311308920.5A CN117251192A (en) | 2023-10-11 | 2023-10-11 | Method, device, equipment and storage medium for managing enterprise-level system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311308920.5A CN117251192A (en) | 2023-10-11 | 2023-10-11 | Method, device, equipment and storage medium for managing enterprise-level system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117251192A true CN117251192A (en) | 2023-12-19 |
Family
ID=89129209
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311308920.5A Pending CN117251192A (en) | 2023-10-11 | 2023-10-11 | Method, device, equipment and storage medium for managing enterprise-level system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117251192A (en) |
-
2023
- 2023-10-11 CN CN202311308920.5A patent/CN117251192A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4429908B2 (en) | Central master data management | |
| US11636092B2 (en) | General, flexible, resilent ticketing interface between a device management system and ticketing systems | |
| CN112600891B (en) | Information physical fusion-based edge cloud cooperative system and working method | |
| US20050055357A1 (en) | Method, system and article of manufacture for data preservation and automated electronic software distribution across an enterprise system | |
| WO2012167267A2 (en) | Building information tracking system and method of use | |
| US11411830B2 (en) | Systems and methods for determining entry points for mapping a network | |
| US8892557B2 (en) | Optimal persistence of a business process | |
| US8433730B2 (en) | Dynamic data access and storage | |
| CN106101213A (en) | Information-distribution type storage method | |
| US20150269511A1 (en) | Extensible framework for resource provider service and quota management | |
| CN108280178A (en) | A kind of multi-platform space information resource cooperated sharing method | |
| CN106101212A (en) | Big data access method under cloud platform | |
| US20080320011A1 (en) | Increasing file storage scale using federated repositories | |
| CN114968739A (en) | Operation and maintenance task management method, operation and maintenance method, device, equipment and medium | |
| CN101046822B (en) | Centralized management of data nodes | |
| CN106254452A (en) | The big data access method of medical treatment under cloud platform | |
| Scholl et al. | Implementation of a simulation-based short-term lot arrival forecast in a mature 200mm semiconductor FAB | |
| CN109388668B (en) | Method for exchanging data between engineering tools of engineering system and engineering system | |
| CN117251192A (en) | Method, device, equipment and storage medium for managing enterprise-level system | |
| CN106302656A (en) | The Medical Data processing method of cloud storage platform | |
| CN112099803B (en) | Incremental deployment method and system of ERP system | |
| CN110896358A (en) | Dynamic updating method and device for resource data in NFV | |
| US20240223446A1 (en) | Multi-tiered reconciliation of network functions | |
| WO2024144882A1 (en) | Multi-tiered reconciliation of network functions | |
| CN115426356A (en) | Distributed timed task lock update control execution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |