CN117992115A

CN117992115A - System configuration processing method, device, equipment, medium and program product

Info

Publication number: CN117992115A
Application number: CN202410389385.9A
Authority: CN
Inventors: 刘健; 杨艳光; 张涛; 张同虎
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2024-04-02
Filing date: 2024-04-02
Publication date: 2024-05-07

Abstract

The application provides a system configuration processing method, a device, equipment, a medium and a program product, which relate to the technical field of big data, wherein the method comprises the following steps: acquiring at least one predefined basic model; responding to a configuration request initiated by a user, and extracting a corresponding basic model from the at least one basic model; generating a resource service configuration list aiming at various resources and services according to the basic model and the configuration environment of the target application; and converting the resource service configuration list into a configuration file in a target format, and transmitting the configuration file to the target application. The application can realize the automatic generation and issuing process of the full life cycle of the configuration file without the need of manual participation of a user in configuration definition and modification, so that the system configuration is more accurate and convenient, and compared with the existing configuration mode, the configuration error occurrence situation is less, and thus, the reliability requirement of a financial institution on the system configuration can be effectively met.

Description

System configuration processing method, device, equipment, medium and program product

Technical Field

The present application relates to the field of big data technologies, and in particular, to a system configuration processing method, apparatus, device, medium, and program product.

Background

Internet technology (Internet Technology, IT) deployment modes based on distributed deployment and centralized configuration management have gradually become a form of configuration management for standards in the financial domain. Due to the industry characteristics of the financial field, financial institutions are also increasingly focusing on the reliability requirements of system configuration management.

The current system configuration mode of the financial institution depends on the configuration center and the processing operation of the user on the configuration file, specifically, the user submits or modifies the configuration file in the configuration center, then the configuration center issues the related configuration file, and the target application executes the related configuration based on the configuration file.

In the above process, the processing procedure of the configuration file is manual operation, which means that the configuration item is generally defined on a grammar level, when the application scale is large, the probability of configuration file errors is obviously increased, which cannot meet the reliability requirement of a financial institution; in addition, based on the manual operation form, the configuration file is difficult to embody configuration differences on different deployment examples, so that the differential deployment of the application cannot be met based on the configuration file.

Disclosure of Invention

The present application provides a system configuration processing method, apparatus, device, medium and program product to solve at least one of the above technical problems.

In a first aspect, the present application provides a method for obtaining at least one predefined basic model, where the basic model is defined based on resource data and service information of various applications, and the at least one basic model is used to describe corresponding configuration rules respectively;

Responding to a configuration request initiated by a user, wherein the configuration request carries basic information of a target application, and extracting a corresponding basic model from at least one basic model according to the basic information;

Generating a resource service configuration list aiming at various resources and services according to the basic model and the configuration environment of the target application;

And converting the resource service configuration list into a configuration file in a target format, and issuing the configuration file to the target application, so that the target application executes corresponding resource and service configuration operation based on the configuration file.

In one embodiment, the at least one basic model carries respective corresponding configuration conversion templates, and the configuration conversion templates include configuration identifiers for identifying configuration conversion rules;

The converting the resource service configuration list into a configuration file in a target format comprises the following steps: and converting the resource service configuration list into a configuration file in a target format according to the configuration conversion template carried by the resource service configuration list.

In one embodiment, the resource data includes at least one of: server address, resource size and storage type, the business information including transaction time and/or processing time; the method further comprises the steps of:

acquiring resource data and service information of various applications from an external system; the external system comprises a configuration management database and/or a preset application system;

Determining resource service attribute information according to the resource data and the service information, and defining the basic model according to the attribute information; wherein the attribute information is an attribute object set with items to be filled.

In one embodiment, the configuration environment is determined based on at least one deployment instance of the target application and its deployment location;

The generating a resource service configuration list for various resources and services according to the basic model and the configuration environment of the target application comprises the following steps:

Determining a differentiated configuration item of the at least one deployment instance according to the basic model, the at least one deployment instance and the deployment position of the at least one deployment instance, and generating the resource service configuration list according to the differentiated configuration item; wherein the differentiated configuration item comprises a physical interface configuration.

In one embodiment, the issuing the configuration file to the target application includes:

and issuing the configuration file to the configuration center, and issuing the configuration file to the target application through the configuration center.

In one embodiment, the configuration center includes at least one of: an Apollo configuration center, a service registration configuration center, and a transaction framework configuration center.

In one embodiment, after generating the resource service configuration list, the method further includes:

Carrying out semantic verification on the resource service configuration list according to the resource data and the service information;

and when the semantic verification of the resource service configuration list is passed, converting the resource service configuration list into a configuration file in a target format.

In one embodiment, the resource service configuration list is added with data source information and approval process information, and the method further includes:

performing flow verification on the data source and the approval flow information according to preset data source information and preset approval flow information;

And when the data source, the flow verification of the approval flow information and the semantic verification of the resource service configuration list pass, converting the resource service configuration list into a configuration file in a target format.

In a second aspect, the present application provides a system configuration processing apparatus, including:

The model management component is used for acquiring at least one predefined basic model, wherein the at least one basic model is defined according to resource data and business information of various applications, and the at least one basic model is respectively used for describing corresponding configuration rules;

The interaction component is used for responding to a configuration request of a user, wherein the configuration request carries basic information of a target application, and a corresponding basic model is extracted from the model management component according to the basic information;

the configuration generation module is used for generating resource service configuration lists of various resources and services according to the basic model and the configuration environment of the target application;

The configuration conversion component is used for converting the resource service configuration list into a configuration file in a target format;

and the configuration issuing component is used for issuing the configuration file to the target application, so that the target application executes corresponding resource and service configuration operation based on the configuration file.

The configuration conversion component is specifically configured to convert the resource service configuration list into a configuration file in a target format according to the configuration conversion template carried by the resource service configuration list.

In one embodiment, the resource data includes at least one of: server address, resource size and storage type, the business information including transaction time and/or processing time;

The model management component is also used for acquiring resource data and service information of various applications from an external system, determining resource service attribute information according to the resource data and the service information, and defining the basic model according to the attribute information; the external system comprises a configuration management database and/or a preset application system, and the attribute information is an attribute object set with items to be filled.

In a third aspect, the present application also provides an electronic device, including: a processor, and a memory communicatively coupled to the processor;

The memory includes computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory to implement the system configuration processing method provided in the first aspect.

In a fourth aspect, the present application also provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are configured to implement the system configuration processing method provided in the first aspect.

In a fifth aspect, the present application also provides a computer program product, which comprises a computer program, the computer program implementing the system configuration processing method provided in the first aspect when being executed by a processor.

The system configuration processing method, the device, the equipment, the medium and the program product provided by the application are characterized in that at least one basic model defined based on resource data and service information is obtained, the at least one basic model is respectively used for describing corresponding configuration rules, the corresponding basic model is extracted from the at least one basic model according to basic information of a target application, a resource service configuration list aiming at various resources and services is generated according to the basic model and the configuration environment of the target application, the resource service configuration list is converted into a configuration file in a target format, and the configuration file is issued to the target application by utilizing a configuration issuing component, so that the target application executes resource and service configuration operation based on the configuration file. In the whole configuration process, a basic model is defined and acquired according to the existing configuration information, a configuration file aiming at a target application is generated by utilizing the basic model and is issued, so that the automatic generation and issuing process of the full life cycle of the configuration file can be realized, a user does not need to manually participate in configuration definition and modification, in addition, in the configuration file generation process, a differential configuration list is generated by combining an application configuration environment, the differential deployment of the application can be realized, the problem of system errors which are difficult to check due to the fact that the configuration items of partial deployment examples are wrong in individual scenes is avoided, the system configuration is more accurate and convenient, compared with the configuration mode of the related art, the situation that the configuration errors occur is fewer, and the reliability requirement of a financial institution on the system configuration can be met.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is one of the application scenario diagrams in the related art;

FIG. 2 is a second application scenario diagram of the related art;

FIG. 3 is a schematic diagram of a system configuration processing device according to an embodiment of the present application;

FIG. 4 is a second schematic diagram of a system configuration processing device according to an embodiment of the present application;

FIG. 5 is one of the possible application scenario diagrams provided by the embodiment of the present application;

FIG. 6 is a second possible application scenario diagram according to an embodiment of the present application;

FIG. 7 is a schematic flow chart of a system configuration processing method according to an embodiment of the present application;

FIG. 8 is a second flowchart of a system configuration method according to an embodiment of the present application;

Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

Fig. 1 is an application scenario diagram of a system configuration in the related art. As shown in fig. 1, the application scenario includes: a user, a configuration center (configuration server) 11, and an application (configuration client) 12; the configuration center may be a centralized configuration management component such as open-source Apollo (apollo), service registration and configuration (nacos), transaction framework configuration (spring-closed-config), and the like. In this scenario, the user modifies/publishes the configuration at the configuration center 11, the configuration center 11 sends a configuration update notification to the application 12, the application 12 obtains the latest configuration file from the configuration center 11, and performs the relevant configuration operation.

System configuration, which refers to the collection of hardware and software components required by a computer system to support specific functions and operational requirements, forms the basis of the computer system and determines the performance and functionality of the system. The application 12, i.e. an application server or an application system, performs related configuration operations by receiving a configuration file issued by a configuration center, so as to support related functions and operation requirements, such as a financial transaction system of a bank, and needs to configure related business information (such as transaction time, etc.) and resource information, etc. to implement a financial transaction function.

Fig. 2 shows an application scenario diagram based on apollo framework in the related art, which is further described in connection with apollo framework, as shown in fig. 2, apollo framework includes: a configuration Service (Config Service) provides functions of reading, pushing and the like of configuration, and a Service object is an Apollo Client (Client, namely, application 12); the management service (ADMIN SERVICE) provides functions of configuration modification, release and the like, and the service object is a management interface (Apollo Portal); the Service discovery framework (Eureka) provides Service registration and discovery, which is currently deployed at the time of deployment and Config Service in a IAVA virtual machine (JVM) process for simplicity; both Config Service and ADMIN SERVICE are multi-instance, stateless deployments that typically require registering themselves in Eureka and maintaining heartbeats; a layer META SERVER is set up on top of the Eureka for encapsulating the service discovery interface of the Eureka; the Client accesses a metadata server (META SERVER) through a domain name to obtain a Config Service list (which can be in the form of IP+Port), then directly accesses the Service through the IP+Port, and simultaneously performs load balancing and error retry on the Client side; portal obtains ADMIN SERVICE service list (IP+Port) through domain name access META SERVER, then directly accesses service through IP+Port, and at the same time, load service and error retry are performed on Portal side; to simplify deployment, three logical roles, config Service, eureka, and META SERVER, are deployed in the same JVM process.

Specifically, after Apollo is started, config/ADMIN SERVICE automatically registers in a Eureka service registration center and periodically sends keep-alive heartbeats; the Apollo Client and Portal management end distribute to one META SERVER after load balance is carried out by a software load balancer through the configured META SERVER domain name address; META SERVER obtain the Service information of Config Service and ADMIN SERVICE from Eureka, which is equivalent to a Eureka Client; META SERVER retries after failure in acquiring Config Service and ADMIN SERVICE (IP+Port); after obtaining the correct Config Service and ADMIN SERVICE Service information, the Apollo Client (i.e. the application 12) provides functions such as configuration obtaining, real-time updating, etc. for the application through the Config Service (read from the configuration database ConfigDB) based on the remote access interface (remotecallAPI); the Apollo Portal management side provides functionality for configuration additions, modifications, releases, etc. based on remotecallAPI through ADMIN SERVICE (read from configuration database ConfigDB).

It can be seen that, in the configuration modification/release process, the user relies on the configuration center to directly define (add, modify and release) through interface configuration, and the user definition is usually based on grammar level definition, the configuration center can only verify the format or other forms of the configuration items at grammar level, so that the configuration items are difficult to ensure in correct forms but internal fault tolerance, and when the application scale is large, the probability of configuration file errors is significantly increased, which cannot meet the reliability requirement of the financial institution. In addition, in the configuration modification/release process, a user generally does not submit configuration items for different deployment examples (workload is large), configuration files are difficult to embody configuration differences for different deployment examples, and system errors which are difficult to be checked due to errors of the configuration items of part of deployment examples in individual scenes are easy to cause, in other words, the configuration modification/release process cannot meet the differentiated deployment of applications.

In view of the above technical problems, embodiments of the present application provide a system configuration processing method, apparatus, device, medium, and program product, which acquire resource data and service information of various applications from an external system through a model management component, define and store at least one basic model based on the resource data and service information, where the at least one basic model is used to describe corresponding configuration rules, implement automatic semantic level definition of a basic model based on existing configuration information of the external system, respond to a configuration request of a user through the interaction component, the configuration request carries basic information of a target application, extract a corresponding basic model from the model management component according to the basic information, generate a resource service configuration list for various resources and services according to the basic model and a configuration environment of the target application, implement automatic generation of a differentiated configuration list for the application in the configuration environment, and further convert the resource service configuration list into a configuration file in the target format through a configuration conversion component, and send the configuration file to the target application by using a configuration issuing component, so that the target application executes resource and service configuration operation based on the configuration file. The whole configuration process depends on a basic model component, an interaction component, a configuration generation component, a configuration conversion component and a configuration issuing component to realize the automatic generation and issuing process of the whole life cycle of the configuration file without manual participation of a user in configuration definition and modification, and in addition, a differential configuration list is generated by utilizing the basic model and an application configuration environment, so that the differential deployment of the application can be realized, the problem of system errors which are difficult to check due to the fact that the configuration items of the partially deployed examples are wrong in individual scenes is avoided, the system configuration is more accurate and convenient, the configuration errors are fewer compared with the configuration mode in the related technology, and the reliability requirement of a financial institution on the system configuration can be met more effectively.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 3 is a schematic structural diagram of a system configuration processing device 30 according to an embodiment of the present application. As shown in fig. 3, the apparatus includes an interaction component 31, a model management component 32 and a configuration generation component 33 electrically connected to the interaction component 31, respectively, a configuration conversion component 34 electrically connected to the configuration generation component 33, and a configuration issuing component 35 electrically connected to the configuration conversion component 34; the model management component 31 is configured to obtain at least one predefined basic model, where the at least one basic model is defined according to resource data and service information of various applications, and the at least one basic model is used to describe corresponding configuration rules respectively; the interaction component 32 is configured to respond to a configuration request of a user, where the configuration request carries basic information of a target application, and extract a corresponding basic model from the model management component according to the basic information; the configuration generating component 33 is configured to generate a resource service configuration list for various resources and services according to the basic model and the configuration environment of the target application; the configuration conversion component 34 is configured to convert the resource service configuration list into a configuration file in the target format; and a configuration issuing component 35, configured to issue the configuration file to the target application, so that the target application performs resource and service configuration operations based on the configuration file.

In this embodiment, the configuration request may be a request for configuration modification or configuration release. The interaction component may be an interaction interface, in the related technology, a user interacts with the configuration center by using the interaction interface and modifies/issues the configuration of the configuration center, in this embodiment, the interaction component is configured to receive a configuration request of the user, and after receiving the configuration request, the interaction component extracts a corresponding basic model from the model management component by using basic information (may be an application name or main function information or description information or other information of the application) of the target application, and interacts with other components in the device, so as to implement semantic definition and a full life cycle of issuing of configuration automation.

In this embodiment, the model management component may implement management such as definition and storage of the base model through interaction with external systems (e.g., a configuration management database and/or other application systems), and the base model may include resource types and/or service types for different external systems. In some embodiments, to facilitate partitioning each base model, it may include a type name/unique identification, model type, set of attribute definitions, other descriptive information, etc. attribute features. The type name/unique identifier is used for identifying the mark characteristic of the basic type and can be globally unique in type configuration; a set of attribute definitions is a set of attribute objects. Such as "MySQL database server attribute definition set"; each attribute object may contain a system ID, configuration identifier, type, constraint, description information, etc.; the system ID is used for uniquely marking the attribute value in the system; a configuration identifier, which is defined as a key or yaml-key representation after being converted into a configuration file or a configuration item, or other format representations defined based on a configuration file distribution service, wherein the configuration identifier needs to be converted by a configuration conversion service according to a rule and a target open source configuration center and a target configuration storage type adopted; the format definition of the type definition configuration information value can be characters, time and numerical values; the constraint is further limitation in the legal input value range of the type after the data type is specified, such as enumeration value limitation, time range limitation, numerical value range limitation, character length limitation, character range limitation and the like; and the description information is used for describing the business meaning of the basic type, such as database server addresses. In some embodiments, the definition and storage management of the base model may also be performed in other devices from which the model management component obtains the base model by interfacing with the other devices.

In this embodiment, the resource type (i.e., resource information) is used to define the server or standard component type. Such as: database server type resources including server IP address or domain name, port, access authorized user, password, etc. attribute types, remote dictionary service (Remote Dictionary Server, REDIS) resource types: the method comprises REDIS deployment forms, wherein enumeration types are a sentinel mode and a cluster mode; in addition, according to different cluster types, deployment configuration information of the cluster is different, such as a sentinel mode, sentinel node information, master node information and slave node information are required to be configured. Cluster mode requires deployment of peer-to-peer information for multiple nodes. Thus, the whistle subtype and cluster subtype of REDIS resource type can also be established;

Service type (i.e. service information): conventional configuration attributes used to identify financial transactions may define, for example, credit transaction accounting attributes such as: run time. The basic model is defined by configuration information (resource/service information) of the existing application system, and configuration items of the basic model are logically defined at a semantic level compared with a grammar level defined by a user modification.

In this embodiment, the configuration generating component combines the basic model and the configuration environment of the application to generate a resource service list of various resources and services for the target application, that is, a data resource pool constructing the basic model includes a (resource/service) configuration item file for each application instance under different configuration environments, where the file is in an internal data format, for example, may be a JSON definition format based on the basic model. When the configuration is issued, for example, after the approval of a specific application configuration file is completed, the configuration conversion component is utilized to convert the configuration file into a target format which can be identified by an application server or a target format defined by a target open source configuration center. The target format here may be of various types, one possible way being a combination of attribute-pair pairs of key-value pairs (key-value). Specifically, all attributes of the initial configuration format JSON object are traversed, and its full path definition name is recorded and converted into the following format name1.Name2. Name3=value 1, one possible example is as follows: { "name1": { "name2": { "name3": "value1" } } }, converting the target format: name1.name2.name3=value 1, in some embodiments, may also be converted to yaml format files or other format files.

In this embodiment, the process of executing configuration by the target application based on the configuration file may refer to the prior art, and will not be described herein again.

It will be appreciated that the target application in this embodiment may be an application server (such as a Web server of a financial institution) that needs to be configured, and may be constructed by using high-end hardware and software, so as to run a complex application program.

It will be appreciated that in response to a condition or state being relied upon to represent an operation being performed, one or more operations being performed may be in real time or with a set delay when the dependent condition or state is satisfied; without being specifically described, there is no limitation in the execution sequence of the plurality of operations performed.

According to the technical scheme, through interaction among the interaction component, the model management component, the configuration generation component, the configuration conversion component and the configuration issuing component, the automatic generation and issuing process of the full life cycle of the configuration file can be realized, and users do not need to manually participate in configuration definition and modification, so that the system configuration is more accurate and convenient, and compared with the existing configuration mode, the situation that configuration errors occur is fewer, and therefore the reliability requirement of a financial institution on the system configuration can be met.

In some embodiments, by carrying the configuration conversion template in the base model, format conversion efficiency and accuracy are improved to reduce the situation of configuration errors due to format problems. Specifically, the at least one basic model carries respective corresponding configuration conversion templates, so that a resource service configuration list generated according to the basic model carries the configuration conversion templates, and the configuration conversion templates comprise configuration identifiers for identifying configuration conversion rules; the configuration conversion component 33 is specifically configured to convert the resource service configuration list into a configuration file in the target format according to the configuration conversion template carried by the resource service configuration list.

In this embodiment, the configuration identifier may take the form of a placeholder identifier, and may take the form of multiple placeholders, converting the location where the change was made. Illustratively, when a certain configuration is enabled, the configuration conversion component reads the base model and records all placeholders in the model, parses the placeholders (as may be understood by those skilled in the art according to existing rules), and in the example of configuration modification, reads the corresponding information from the previous configuration information and populates it. When the configuration management component receives a data change event corresponding to a specific placeholder, the configuration file of the application level can be dynamically regenerated according to the rule.

In some embodiments, the accuracy and the identifiability of the basic model are improved by acquiring the existing configuration information from an external system and determining the attribute information to define the basic model according to the existing configuration information, so that the efficient generation of the follow-up configuration list is facilitated. Specifically, the resource data includes at least one of: server address, resource size and storage type, the business information including transaction time and/or processing time; the model management component 32 is specifically configured to obtain resource data and service information of various applications from an external system, determine resource service attribute information according to the resource data and the service information, and define the basic model according to the attribute information; wherein the attribute information is an attribute object set with items to be filled; the external system includes a configuration management database and/or a preset application system. Wherein, one or more of the above-mentioned resource data and service information are merely examples of embodiments of the present application, and not limited thereto, other resource data or service information may be included in addition to the above-mentioned resource data and service information, for example, the resource data may include information such as capacity, the service information may include information such as transaction number, which may be adaptively adjusted according to practical applications, and the embodiment is not limited thereto in particular,

IT will be appreciated that the configuration management database (Configuration Management Database, CMDB), which is a logical database containing information about the full lifecycle of configuration items and relationships between configuration items (including physical relationships, real-time communications relationships, non-real-time communications relationships, and dependencies), stores and manages various configuration information for devices in the enterprise IT architecture, is tightly coupled to all service support and service delivery flows, supports the operation of these flows, develops the value of the configuration information, and relies on the related flows to ensure the accuracy of the data. The preset application system may be an application system related to (or having the same function as) the target application, and the embodiment obtains corresponding existing configuration information from the CMDB or the preset application system, so that accuracy of data can be effectively ensured.

For example, take a bank account transaction system (i.e. a target application) as an example: the manager executes configuration based on the system configuration processing device, builds a logic application configuration item, namely generates a configuration list, wherein service information is derived from other service or approval systems, similar system trigger change exists, server resources are derived from the CMDB, and the CMDB triggers the configuration change. The service information described in the logic configuration item below may include the total amount of service information transferred by the external system, and may be irrelevant to the configuration of the target deployment application.

Illustratively, the logical application configuration items (i.e., resource service configuration listings) may include resource configuration items and service configuration items (determined from existing service information and resource data), as well as base configuration items (including global information, such as configuration identifier, name, etc. information). Specifically, taking the financial transaction system as an example, the global information may include a configuration identifier: a, A is as follows; name: an online transaction system; the service configuration items may include: transaction date: time zone: +8:00 region; day cutting time is 00:00:00; batch processing time: 22:00:00; the resource configuration items (e.g., server information) may include: interface service: (peer-to-peer deployment) (OnLine); unified grant open port a [ service interface ] server 1: IP is XX.X.X.X; CPU _G; the storage comprises the following types: NAS; capacity: 500G; application deployment location: an app; the server 2: IP is XX.X.X.X; CPU: g8; the storage comprises the following types: NAS; capacity: XX; application deployment location: an app; server 3: IP is XX.X.X.X; CPU: g8; the storage comprises the following types: NAS; capacity: g; application deployment location: an app; interface service: (active-standby deployment) (Batch); server 1: IP is XX.X.X.X; CPU to strength 2.5G 8; the storage comprises the following types: NAS; capacity: g; application deployment location: an app; the server 2: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: 500G; application deployment location: an app; static service: (peer-to-peer deployment) (Static); server 1: IP is XX.X.X.X; CPU to strong_G; the storage comprises the following types: NAS; capacity: 500G; application deployment location: an app; the server 2: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: g; application deployment location: an app; server 3: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: 500G; application deployment location: an app; data service: (RAC Deployment) (DB); the authorization mode is as follows: a user/password; account information: xxxxx; password information: * The following are all the following; transaction service 1: IP is XX.X.X.X; PORT: b; CPU to strength 2.5G 8; the storage comprises the following types: NAS; capacity: g; application deployment location: /db; transaction service 2: IP is XX.X.X.X; PORT: c; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: g; application deployment location: /db; storage service 1: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: g; application deployment location: /db; storage service 2: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: 500G; application deployment location: /db; storage service 3: IP is XX.X.X.X; CPU to strong_Gx 8; the storage comprises the following types: NAS; capacity: g; application deployment location: and/db.

In the above example, the content before the semicolon refers to the attribute object, the content after the semicolon refers to the item to be filled (for example, the batch processing time in the service information is 22:00:00, the batch processing time is the attribute object, 22:00:00 is the item to be filled), the item to be filled may be a default value or a value to be defined, each attribute object may be mapped to global information, and the global information may include the system ID, the configuration identifier, the type, the constraint, the description information, and the like, which is not limited in this embodiment.

In some embodiments, the configuration environment is determined based on at least one deployment instance of the target application and its deployment location; generating a resource service configuration list for various resources and services according to the basic model and the configuration environment of the target application, wherein the resource service configuration list specifically comprises the following steps: determining a differential configuration item of the at least one deployment instance according to the basic model, the at least one deployment instance and the deployment position thereof, and generating the resource service configuration list according to the differential configuration item; wherein the differentiated configuration item comprises a physical interface configuration.

It will be appreciated that an application generally refers to a stand-alone deployment package that runs based on a JVM, but may be other deployment packages that are capable of dynamically acquiring configuration in connection with the present device or configuration center. In some embodiments, the information that an application needs to configure its configuration file may include: the profile identification, including the contained base model or a portion of its data items, may also contain non-base model-wide configuration items of simple key-value pair (k, v) structure. When the plurality of deployment examples or part of deployment examples of the application do not adopt unified application configuration, a specific deployment configuration file of the application configuration can be additionally configured, the specific deployment configuration file adopts a configuration template of the application configuration file, and the change of the part attribute values within a limited range is allowed. The non-uniform configuration may set an independent profile identification and record the application and profile identification.

Continuing to combine the above examples, besides the basic model information, the method further comprises the content of the application deployment position, and by determining the differentiated configuration items, a corresponding configuration list is generated for different deployment examples and deployment positions so as to facilitate the differentiated deployment of the application.

In this embodiment, each application deployment instance needs to define its deployment coordinates, which may be a server address, a container address, or other deployment coordinates supported inside the enterprise. Meanwhile, a configuration file identifier corresponding to the deployment instance can be defined. If the configuration file identification is allowed, the configuration identification is driven into the construction product when the application product pipeline of the enterprise constructs the deployment product, so that the configuration error probability can be further reduced.

Wherein, physical interface configuration, take interface service as an example: adding an interface template configuration to the interface service physical application configuration of the above example: the template fill is first set to peer-to-peer mode, i.e., each server node deployment configuration item is consistent. In the case of a master-slave configuration, it is necessary to determine which is the master by default and which is the slave, or the master-slave is determined by the system.

In some embodiments, the device can directly issue configuration files, and can complete the issuing of configuration by means of the existing configuration center, so that the defect that the existing configuration center is poor in configuration accuracy based on manual submission is overcome, meanwhile, the clustered management advantage of the configuration center can be drawn, and the rapid configuration in a large-scale application scene is realized. Specifically, the configuration issuing component 34 is further electrically connected to an external configuration center, and is configured to issue the configuration file to the configuration center, and issue the configuration file to the target application through the configuration center.

In this embodiment, the configuration center includes at least one of: apollo configuration center, service registration and configuration center and transaction framework configuration center. The Apollo configuration center, namely the Apollo distributed configuration management center is a reliable distributed configuration management center, is born in a carrying-path framework research and development part, can intensively manage the configuration of different environments and different clusters, can be pushed to an application end in real time after configuration modification, has the characteristics of normative authority, flow management and the like, and is suitable for a micro-service configuration management scene. In some embodiments, other configuration centers besides those described above are possible, as the present application is not particularly limited in this regard.

In some embodiments, in order to further improve the correctness of the configuration file, the embodiment further sets a verification component, and issues the configuration after verification passes. As shown in fig. 4, a verification component 41 may be further included and electrically connected to the configuration generation component 33, the configuration conversion component 34, and the model management component 32, respectively; the verification component 41 is configured to obtain, from the model management component 31, resource data and service information corresponding to the resource service configuration list after the configuration generation component 31 generates the resource service configuration list, and perform semantic verification on the resource service configuration list according to the resource data and service information. Optionally, after the verification component 41 verifies that the resource service configuration list passes, a verification pass instruction is sent to the configuration generating component 33, so that the configuration generating component 33 sends the resource service configuration list verified by the verification component 41 to the configuration converting component 34 to convert the resource service configuration list into the configuration file in the target format.

In the related art, in connection with the application scenario shown in fig. 1, in order to improve the configuration accuracy, in the process of interaction between a user and a configuration center, that is, when the user submits configuration modification/release, the configuration center or other devices perform a grammar level check on configuration information submitted by the user, for example, a text format check, so that it is difficult to identify whether the content of the configuration item is wrong (for example, whether the information such as a server interface is wrong). In the embodiment of the application, the configuration generating process is automatically realized by the whole life cycle of the system configuration processing device, after the configuration generating component generates the resource service configuration list, the verification component is arranged, the existing configuration logic of the model management component is combined, and the consistency between the verification list and the existing configuration logic can be used for efficiently realizing the verification of the semantic level of the resource service configuration list, so that whether the content of the configuration item is wrong or not is rapidly analyzed, and the issuing operation of wrong configuration can be effectively avoided.

Further, the configuration generating component 33 is further configured to add data source information and approval process information in the resource service configuration list; the verification component 41 is further configured to perform a flow verification on the data source and the approval flow information according to preset data source information and preset approval flow information. Optionally, after the flow verification of the data source and the approval flow information and the semantic verification of the resource service configuration list pass, the verification component 41 sends the verification pass instruction to the configuration generating component, and the configuration generating component sends the resource service configuration list to the configuration conversion component, so that the configuration conversion component converts the resource service configuration list into the configuration file in the target format.

In this embodiment, in order to further improve the accuracy of configuration, the application configuration and deployment instance configuration file needs to use an approval process to approve the full configuration item, and by adding data source information and approval process information in the manifest, compliance of configuration is achieved.

In some implementations, each type of data source and approval process may be defined during the definition phase of the base model, and automatically added during the manifest generation phase. Specifically, the source and approval process of the data instance of each basic model can be defined according to the existing process control technology and server control technology. And if the database type resource is derived from the CMDB server database, defining an underwriter xx person, and writing the underwriter xx person into the configuration application after approval. After configuration is completed, resource configuration item data based on a basic model is generally generated: such as xx systems database, { id:1, ip: xxx.xxx.0.1, port: xx06 service configuration items are required to be written into the configuration application after approval confirmation of related service responsible persons through the service configuration items. Such as xx system batch time, { id:2, time:00 00 00/* }.

Fig. 5 and fig. 6 are an exemplary first diagram and an exemplary second diagram of a possible application scenario provided by an embodiment of the present application, where a combination of a system configuration processing device and a configuration center is combined to complete configuration delivery. As shown in fig. 5, the present embodiment uses an Apollo base application component (configuration center) 10 as a system configuration processing device and is applied to a configuration management device, so as to realize docking with most of applications compatible with an Apollo client. In addition, the configuration center can also be other types of basic configuration storage distribution components such as Spring-closed-config, nacos, eureka and the like; the system configuration processing device 30, which may be also referred to as a custom service-based configuration service management component, is configured to perform semantic level configuration management and user interaction. The Apollo configuration center 10 includes a configuration Service (Config Service) and a configuration database (Config DB), the principles of which are described in detail in the architecture shown in fig. 2, and will not be described again here.

As shown in fig. 6, the configuration service management component 20 includes an interaction component, a model management component (which may include basic model management, application configuration management, deployment instance management), a configuration conversion component, and a configuration delivery component (not shown), and so forth. An interaction component: providing a man-machine interaction page for a configuration management user, and providing an operability inlet and a result display outlet for the configuration management user; model management component: a basic model management for managing a configuration model based on semantic definition; application configuration management for managing configuration of applications. An application refers to a set of deployment instances that use the same configuration manifest template that applies to multiple clustered deployments of one financial business application. In particular, when a high availability deployment of a particular resource type requires rules specifying a series of sub-components, the application contains multiple deployment instance configurations that differ in configuration; deployment instance management, which is used to manage specific deployment of applications, typically in the JAVA background area, represents an independent process started based on JVM. The process occupies a certain application server resource and can be recorded in the CMDB. But may be various types of standard database resources, cache resources, or other resources. A configuration conversion component: the semantic level configuration list generated based on the basic model is converted into a required configuration item/file format of a target configuration management server (i.e. a configuration center, in some embodiments, the required configuration item/file format can also be directly converted into a required configuration item/file format of a target application), and finally, the configuration is issued to various target applications. In addition, the present embodiment may also rely on a configuration database commonly used by enterprises such as CMDB for server resource management, as it is closely related to environmental resource configuration.

Based on the system frames shown in fig. 5 and fig. 6, the technical solution of the present embodiment may include the following procedures:

In the configuration stage: configuration 1, defining a basic model: the method comprises the steps of including a resource basic type and a service type; the base model includes a type name/unique identifier, a model type, a set of attribute definitions, other attribute features such as descriptive information, and the like. The type name/unique identification is a signature feature used in this embodiment to identify the underlying type (resource or service), and needs to be globally unique in the type configuration. An attribute definition set is a set of attribute objects, such as a "MySQL database server attribute definition set". Each attribute object may contain a system ID for uniquely marking the attribute value in the system, a configuration identifier, a type, a constraint, description information, etc.; a configuration identifier defining a key or yaml-key representation after it is converted into a configuration file or configuration item. Or other format representations defined based on the profile distribution service. The configuration identifier needs to be converted by the configuration conversion service according to the rule and the target open source configuration center and the adopted target configuration storage type. The format definitions of the type definition configuration information values may be characters, time, numerical values, etc. Constraints are further limitations within the legal input value range of the type after the data type is specified, such as limitations by means of enumerated values, limitations of time ranges, limitations of numerical ranges, limitations of character lengths, limitations of character ranges, and the like. And the description information is used for describing the business meaning of the basic type, such as database server addresses.

Wherein the resource type: server or standard component types are defined. Such as: the database server type resources comprise server IP addresses or domain names, ports, access authorized users, passwords and other attribute types. REDIS resource type: including REDIS deployment form, enumeration type is sentinel mode and cluster mode

Meanwhile, due to different cluster types, deployment configuration information of the clusters is different, such as a sentinel mode, sentinel node information, master node information and slave node information are required to be configured. Cluster mode requires deployment of peer-to-peer information for multiple nodes. The whistle subtype and cluster subtype of REDIS resource type will be established; service type: to identify conventional configuration attributes of financial transactions. For example, credit business accounting period attributes may be defined, such as: run time.

Configuration 2: defining the data source and approval flow of each type. The source and approval process of the data instance of each basic model can be defined according to the existing process control technology and server control technology. And if the database type resource is derived from the CMDB server database, defining an xx person, and writing the xx person into the configuration application after approval of xx leaders. After configuration is completed, resource configuration item data based on a basic model is generally generated: such as xx systems database, { id:1, ip: xxx.xx.0.1, port: xx06}; the service configuration item is required to be written into the configuration application after being approved and confirmed by a relevant service responsible person and from a service approval process. Such as xx system batch time, { id:2, time:00 00 00/* }.

Configuration 3: defining an application: application refers generally to what we said to be a separate deployment package running based on JVM, but of course, other deployment packages that can dynamically acquire configuration in connection with a configuration center are also possible. The application needs information to configure its configuration file: the profile identification, including the contained underlying model or a portion of its data items, may also contain configuration items for non-underlying model scope for simple k, v structures. When the plurality of deployment examples or part of deployment examples of the application do not adopt unified application configuration, a specific deployment configuration file of the application configuration can be additionally configured, the specific deployment configuration file adopts a configuration template of the application configuration file, and the change of the part attribute values within a limited range is allowed. The non-uniform configuration requires its own independent profile identification and records the application and profile identification.

Configuration 4: application deployment instance definition: each application deployment instance needs to define its deployment coordinates, which may be a server address, a container address, or other deployment coordinates supported inside the enterprise. Meanwhile, a configuration file identifier corresponding to the deployment instance needs to be defined. If the configuration file identification is allowed, the configuration identification is driven into the construction product when the application product pipeline of the enterprise constructs the deployment product, so that the configuration error probability can be further reduced.

The application configuration and deployment instance configuration file can be subjected to full configuration item approval by utilizing an approval process, and meanwhile, the configuration of the deployment instance level can be additionally highlighted in the approval process, so that the configuration accuracy is improved.

In the configuration conversion phase: in the configuration stage described above, a data resource pool of the base model has been constructed based on the base model and the associated approval configuration data, and for each application, a configuration item file is typically in an internal data format, for example, a JSON definition format based on the base model. After the approval of the specific application configuration file is completed, the configuration conversion service is required to convert the specific application configuration file into a target format defined by a target open source configuration center (Apollo configuration center). The target format may be of various types, one possible way being a combination of attribute pairs of key=value. The configuration conversion component traverses all the attributes of the JSON object in the initial configuration format, records its full path definition name and converts it to the following format name1.Name2. Name3=value 1, one possible example is as follows: an initial configuration model { "name1": "name2": { "name3": "value1" } } }, converting the target format: name1.name2.name3=value 1

Can also be converted into yaml format files: name1: name2: name3: value1.

After the configuration conversion component completes the conversion of the full application, the format file is pushed to an Apollo configuration center by using the existing interfaces of Apollo and the like.

In the application running stage: after the application is started, the submitted configuration file can be read from applications such as Apollo by using a corresponding client according to the configuration file identifier which is input during the construction of the pipeline or the configuration file identifier which is issued by a configuration center in other deployment modes. And realizing the complete issuing flow of the configuration and executing the configuration.

Based on an open source configuration management framework of Apollo, the embodiment adds new service model definition and service at a configuration management input end, and realizes the semantic-level configuration definition, verification and configuration distribution functions by connecting with other resource management systems (CMDB or other application systems). Compared with the configuration mode in the related art, the standard configuration items related to the configuration scheme provided by the embodiment are specific mode configuration items based on the basic model, and the configuration data used in the basic model are directly issued based on the authoritative database and the related approval process, so that errors caused by manual filling are greatly reduced. And based on the service configuration and resource configuration of the basic model, the configuration difference of the clearly defined application-level configuration files on different deployment examples effectively avoids the system errors which are difficult to check and are caused by the configuration item errors of part of deployment examples of individual scenes.

It should be noted that, the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into one physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the configuration conversion component may be a processing element which is set up separately, may be implemented in a chip of the above apparatus, or may be stored in a memory of the above apparatus in the form of program codes, and the functions of the above configuration conversion component may be invoked and executed by a processing element of the above apparatus. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element here may be an integrated circuit with signal processing capabilities.

Fig. 7 is a flowchart of a system configuration processing method provided in the present application, as shown in fig. 7, the method includes steps S701-S704.

Step S701, acquiring at least one predefined basic model, wherein the basic model is defined based on resource data and business information of various applications, and the at least one basic model is respectively used for describing corresponding configuration rules;

Step S702, responding to a configuration request initiated by a user, wherein the configuration request carries basic information of a target application, and extracting a corresponding basic model from at least one basic model according to the basic information;

step S703, generating a resource service configuration list aiming at various resources and services according to the basic model and the configuration environment of the target application;

Step S704, the resource service configuration list is converted into a configuration file in a target format, and the configuration file is issued to the target application, so that the target application executes corresponding resource and service configuration operation based on the configuration file.

According to the method, the basic model is defined and acquired according to the existing configuration information, the configuration file aiming at the target application is generated by utilizing the basic model and issued, so that the automatic generation and issuing process of the full life cycle of the configuration file can be realized, the user does not need to manually participate in configuration definition and modification, in addition, in the configuration file generation process, the application configuration environment is combined to generate a differential configuration list, the differential deployment of the application can be realized, the problem of system errors which are difficult to check due to the fact that the configuration items of some deployment examples are wrong in individual scenes is avoided, the system configuration is more accurate and convenient, compared with the configuration mode of the related art, the situation that the configuration errors occur is fewer, and the reliability requirement of a financial institution on the system configuration can be met.

In some embodiments, the at least one base model carries respective corresponding configuration conversion templates, the configuration conversion templates including configuration identifiers for identifying configuration conversion rules;

The method for converting the resource service configuration list into the configuration file in the target format comprises the following steps: and converting the resource service configuration list into a configuration file in a target format according to the configuration conversion template carried by the resource service configuration list.

In this embodiment, by carrying the configuration conversion template in the base model, the format conversion efficiency and accuracy can be improved, thereby reducing the situation of configuration errors due to format problems.

Fig. 8 is a second flow chart of a system configuration processing method provided by the embodiment of the present application, on the basis of the above-mentioned scheme, the present embodiment obtains resource data and service information of various applications from an external system, and defines a basic model according to the resource data and service information, so as to implement semantic definition of the basic model, and facilitate efficient generation of configuration files. In this embodiment, the resource data includes at least one of: the server address, the resource size, and the storage type, the service information includes a transaction time and/or a processing time, as shown in fig. 8, and specifically, in addition to the above steps S701 to S704, the present embodiment may further include steps S801 and S802:

Step S801, resource data and business information of various applications are obtained from an external system; the external system comprises a configuration management database and/or a preset application system;

Step S802, determining resource business attribute information according to the resource data and business information, and defining the basic model according to the attribute information; wherein the attribute information is a set of attribute objects having items to be filled.

In this embodiment, through interaction with an external system (for example, a configuration management database and/or other application systems), management such as definition and storage of a basic model is implemented, and for different external systems, the basic model may include a resource type and/or a service type, and compared with a manual configuration error, the configuration rule of existing resource data and service information is used, so that a powerful support is provided for implementing automatic generation and issuing of a configuration file.

In some embodiments, the configuration environment is determined based on at least one deployment instance of the target application and its deployment location; step S703 generates a resource service configuration list for various resources and services according to the basic model and the configuration environment of the target application, and may include the following steps: determining a differential configuration item of the at least one deployment instance according to the basic model, the at least one deployment instance and the deployment position thereof, and generating the resource service configuration list according to the differential configuration item; wherein the differentiated configuration item comprises a physical interface configuration.

In some embodiments, step S704 includes: and issuing the configuration file to the configuration center, and issuing the configuration file to the target application through the configuration center.

In some embodiments, the configuration center includes at least one of: an Apollo configuration center, a service registration configuration center, and a transaction framework configuration center.

In some embodiments, after the generating the resource service configuration list in the step S703, the method may further include the following steps: carrying out semantic verification on the resource service configuration list according to the resource data and the service information; when the semantic verification of the resource service configuration list passes, step S704 is performed to convert the resource service configuration list into a configuration file in a target format.

In some embodiments, the method may further include the steps of: performing flow verification on the data source and the approval flow information according to preset data source information and preset approval flow information; when the data source, the flow verification of the approval flow information, and the semantic verification of the resource service configuration list pass, step S704 is executed to convert the resource service configuration list into a configuration file in a target format.

It should be noted that, the implementation principle and technical effects of the method provided by the embodiment of the present application are similar to those of the embodiment of the system configuration processing device, and are not described herein again.

Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 9, the electronic device may include: a transceiver 91, a processor 92, a memory 93.

The processor 92 executes computer-executable instructions stored in the memory, so that the processor 92 executes the system configuration processing method in the above-described embodiment. The processor 92 may be a general-purpose processor including a central processing unit CPU, a network processor (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

The memory 93 is coupled to the processor 92 via a system bus and communicates with each other, and the memory 93 is adapted to store computer program instructions.

The transceiver 91 may be used to obtain configuration request information, etc.

The system bus may be a peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The transceiver is used to enable communication between the database access device and other computers (e.g., clients, read-write libraries, and read-only libraries). The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (non-volatile memory).

The embodiment of the application also provides a chip for running the instruction, which is used for executing the technical scheme of the system configuration processing method in the embodiment.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer is caused to execute the technical scheme of the system configuration processing method in the embodiment.

The embodiment of the application also provides a computer program product, which comprises a computer program stored in a computer readable storage medium, wherein at least one processor can read the computer program from the computer readable storage medium, and the technical scheme of the system configuration processing method in the embodiment can be realized when the at least one processor executes the computer program.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

In addition, each functional module in the embodiments of the present application may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit. The units formed by the modules can be realized in a form of hardware or a form of hardware and software functional units.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform some of the steps of the methods of the various embodiments of the application.

It should be appreciated that the Processor may be a central processing unit (Central Processing Unit, abbreviated as CPU), or may be other general purpose Processor, digital signal Processor (DIGITAL SIGNAL Processor, abbreviated as DSP), application SPECIFIC INTEGRATED Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an Application SPECIFIC INTEGRATED Circuits (ASIC). Of course, the processor and the storage medium may reside as discrete components in an electronic control unit or master control device.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A system configuration processing method, comprising:

Acquiring at least one predefined basic model, wherein the basic model is defined based on resource data and business information of various applications, and the at least one basic model is respectively used for describing corresponding configuration rules;

2. The method of claim 1, wherein the at least one base model carries respective corresponding configuration conversion templates, the configuration conversion templates including configuration identifiers for identifying configuration conversion rules;

3. The method of claim 1, wherein the resource data comprises at least one of: server address, resource size and storage type, the business information including transaction time and/or processing time; the method further comprises the steps of:

4. The method of claim 1, wherein the configuration environment is determined based on at least one deployment instance of the target application and its deployment location;

5. The method according to any one of claims 1-4, wherein said issuing the configuration file into the target application comprises:

And issuing the configuration file to a configuration center, and issuing the configuration file to the target application through the configuration center.

6. The method of claim 5, wherein the configuration center comprises at least one of: an Apollo configuration center, a service registration configuration center, and a transaction framework configuration center.

7. The method according to any one of claims 1-4, further comprising, after generating the resource service configuration list:

8. The method of claim 7, wherein data source information and approval process information are added to the resource service configuration list, the method further comprising:

9. A system configuration processing apparatus, comprising:

10. The apparatus of claim 9, wherein the at least one base model carries respective corresponding configuration conversion templates, the configuration conversion templates including configuration identifiers for identifying configuration conversion rules;

11. The apparatus of claim 9, wherein the resource data comprises at least one of: server address, resource size and storage type, the business information including transaction time and/or processing time;

12. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

The memory includes computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the system configuration processing method of any one of claims 1-8.

13. A computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, which when executed by a processor is configured to implement the system configuration processing method according to any one of claims 1-8.

14. A computer program product comprising a computer program which, when executed by a processor, implements the system configuration processing method of any one of claims 1-8.