CN113076130A - General counter system operation and maintenance method based on SHELL script - Google Patents
General counter system operation and maintenance method based on SHELL script Download PDFInfo
- Publication number
- CN113076130A CN113076130A CN202110308663.XA CN202110308663A CN113076130A CN 113076130 A CN113076130 A CN 113076130A CN 202110308663 A CN202110308663 A CN 202110308663A CN 113076130 A CN113076130 A CN 113076130A
- Authority
- CN
- China
- Prior art keywords
- script
- automatic
- management
- maintenance
- batch
- 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 163
- 238000013515 script Methods 0.000 title claims abstract description 148
- 238000012423 maintenance Methods 0.000 title claims abstract description 70
- 238000012545 processing Methods 0.000 claims abstract description 26
- 230000006870 function Effects 0.000 claims description 17
- 238000005096 rolling process Methods 0.000 claims description 15
- 238000007689 inspection Methods 0.000 claims description 12
- 238000007906 compression Methods 0.000 claims description 9
- 230000006835 compression Effects 0.000 claims description 9
- 238000009826 distribution Methods 0.000 claims description 7
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 6
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 238000011084 recovery Methods 0.000 claims description 5
- 230000010076 replication Effects 0.000 claims description 4
- 238000003860 storage Methods 0.000 description 11
- 238000009434 installation Methods 0.000 description 5
- BQCADISMDOOEFD-UHFFFAOYSA-N Silver Chemical compound [Ag] BQCADISMDOOEFD-UHFFFAOYSA-N 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 229910052709 silver Inorganic materials 0.000 description 2
- 239000004332 silver Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
-
- 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/44568—Immediately runnable code
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
Abstract
The invention discloses a general counter system operation and maintenance method based on a SHELL script, which solves the operation and maintenance problems of an open counter on one hand and the start-stop, configuration and release problems of services of a distributed multi-center deployment structure on the other hand. The technical scheme is as follows: the method comprises an application start-stop processing flow and a batch operation and maintenance processing flow, wherein the application start-stop processing flow is used for adding a multi-computer trust relationship for the operation and maintenance to operate a first server to log in and connect other target servers without secret, and the batch operation and maintenance processing flow is used for executing a specified instruction on a specified target server.
Description
Technical Field
The invention relates to an operation and maintenance method of a general counter system, in particular to an operation and maintenance method of a general counter system based on SHELL scripts.
Background
The trading counter system is the most important application software system of the futures brokerage company, integrates functions of customer trading, hierarchical settlement, unified wind control, customer account opening, fund management and bank account transfer, and has the characteristics of multiple systems and dispersed modules.
Generally, a trading counter system is composed of a plurality of subsystems, such as a trading system, a settlement system, a wind control system, a banking system, an account opening service, and the like, and each subsystem is composed of different functional modules.
The transaction system mainly comprises the following processes:
the wind control system mainly comprises the following processes:
| name of process | Number of | Function(s) |
| rmskernel | 1 | Wind control core |
| rmskfront | 1 | Wind control front-mounted |
| rmstinit | 1 | Wind control data field module |
| rmstmdb | 1 | Wind control data field module |
| rmsprediction | N | Trial calculation module |
The clearing system mainly comprises the following processes:
| name of process | Number of | Function(s) |
| SettlementService | 1 | Clearing service |
| queryservice | 1 | Data query service |
| Get_Gen_settlementfile | 1 | Service for inquiring statement of account |
The silver period system mainly comprises the following processes:
| name of process | Number of | Function(s) |
| moneyserver | 2 | Core of silver phase |
| bfmtvcsoffer | 2 | Yixiantong newspaper disc |
| bfmtabcoffer | 1 | Agricultural running newspaper disk |
| bfmt...offer | N | Newspaper disk for each bank |
In the aspect of deployment, in order to ensure continuity and stability of services, a counter system is generally deployed in a distributed manner and multiple centers, and a set of counter system generally includes more than 20 servers, and service names of the servers are different.
In maintenance, different subsystem service functions are mainly effective at different time points, so that the start-stop time and the start-stop frequency of different systems and different processes are different.
In summary, for the counter system, it is necessary to develop an operation and maintenance method, which can perform operation and maintenance management on all subsystems uniformly, and also can perform management on servers, users and processes separately.
Disclosure of Invention
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The invention aims to solve the problems and provides a SHELL script-based general counter system operation and maintenance method, which solves the operation and maintenance problems of an open counter on one hand and the start-stop, configuration and release problems of services of a distributed multi-center deployment structure on the other hand.
The technical scheme of the invention is as follows: the invention discloses a general counter system operation and maintenance method based on a SHELL script, which comprises an application start-stop processing flow and a batch operation and maintenance processing flow, wherein the application start-stop processing flow is used for adding a multi-computer trust relationship for an operation and maintenance operation first server to log in and connect other target servers without a secret, and the batch operation and maintenance processing flow is used for realizing the execution of a specified instruction on a specified target server;
wherein the application start-stop processing flow further comprises: the method comprises the steps that a management user on a first server remotely manages scripts and services of a target server through a running management script, a process configuration file and a running basic instruction script, wherein the running management script, the process configuration file and the running basic instruction script form a script calling framework of running management, and the running basic instruction script containing specific instructions is added into the running management script to realize the execution of specified instructions on any process;
wherein the batch operation and maintenance processing flow further comprises: the method comprises the steps that a management user on a first server realizes batch operation including file distribution, configuration distribution, log backup and flow clearing on the server through issuing a management script, a process configuration file and an operation and maintenance basic instruction script, wherein the issuing management script, the process configuration file and the operation and maintenance basic instruction script form a script calling frame of issuing management, the operation and maintenance basic instruction script containing specific instructions is added into the issuing management script, and the specified instructions are executed on a specified server.
According to an embodiment of the method for operating and maintaining the universal counter system based on the SHELL script, the function of executing the specified instruction on any process by applying the start-stop processing flow includes but is not limited to: process inspection, process connection number inspection, process port inspection, process log inspection, process compression and process configuration modification.
According to an embodiment of the SHELL script-based general counter system operation and maintenance method, the operation management script is composed of two methods, and the two methods are used for respectively realizing the analysis of the process configuration file and the calling of specific instructions in the operation basic instruction script.
According to an embodiment of the general counter system operation and maintenance method based on the SHELL script, the batch operation and maintenance processing flow implements functions of executing a specified instruction on a specified server, including but not limited to: batch compression, batch replication, batch recovery, batch copying.
According to an embodiment of the method for operating and maintaining the universal counter system based on the SHELL script, the method further comprises the step of setting a set of installation directory structures and release directory structures to support a script calling framework for operation management and release management.
According to an embodiment of the general counter system operation and maintenance method based on the SHELL script, automatic deployment is defined in a script calling framework of release management, wherein the automatic deployment comprises the following steps: automatic creation of directories, automatic copying of scripts, automatic copying of initialization files, automatic copying of executable files, automatic copying of library files, automatic copying of configuration files, automatic configuration encryption, creation of file links.
According to an embodiment of the method for the operation and maintenance of the general counter system based on the SHELL script, the automatic upgrade is defined in a script calling framework of release management, wherein the automatic upgrade comprises the following steps: the method comprises the steps of putting an upgrade package with a standard structure under an automatic upgrade directory, automatically updating a script, automatically updating an initialization file, automatically updating an executable file, automatically updating a library file, and automatically updating and encrypting a configuration file.
According to an embodiment of the general counter system operation and maintenance method based on the SHELL script, an automatic backup is defined in a script calling frame of release management, wherein the automatic backup comprises the following steps: automatic creation of directories, automatic backup scripts, automatic backup of initialization files, automatic backup of executable files, automatic backup of running water, automatic backup of logs, automatic backup of configuration files.
According to an embodiment of the method for the operation and maintenance of the general counter system based on the SHELL script, an automatic rollback is defined in a script calling frame of the release management, wherein the automatic rollback comprises the following steps: selecting backup version information needing to be rolled back, automatically generating md5 codes of all files of the existing versions, automatically rolling back an initialization file, automatically rolling back an executable file, automatically rolling back a library file, automatically rolling back and encrypting a configuration file, automatically logging and running water, and automatically rolling back a script.
Compared with the prior art, the invention has the following beneficial effects: the invention solves the problem that the futures company using the open counter system lacks a unified tool in the aspect of deploying operation and maintenance, greatly reduces manual operation and provides possibility for automatic operation and maintenance. On the other hand, a set of script calling framework is set and realized in the method, so that the set of operation and maintenance scripts has expandability on the system. In detail, relevant batch operations based on processes, including but not limited to process check, process connection number check, process port check, process log check, process compression, process configuration modification, and the like, may be implemented by writing scripts of corresponding functions based on a unified run management script run _ batch. The unified release management script default _ batch can be set, and relevant batch operations based on the server, including but not limited to batch compression, batch replication, batch recovery, batch copy and the like, can be realized by writing scripts with corresponding functions. On the other hand, the invention defines a standard structure (a standard release directory format and a standard installation directory format) of system deployment, so that the set of operation and maintenance scripts has universality, and the standard structure basically covers several types of files required by software operation. All software products related to the open counter system can be classified and packaged according to a standard release format established by the standard, and can be directly deployed, operated and maintained by using the script related to the method.
Drawings
The above features and advantages of the present disclosure will be better understood upon reading the detailed description of embodiments of the disclosure in conjunction with the following drawings. In the drawings, components are not necessarily drawn to scale, and components having similar relative characteristics or features may have the same or similar reference numerals.
Fig. 1 is a flowchart illustrating an application start-stop process in an embodiment of the SHELL script-based general counter system operation and maintenance method of the present invention.
Fig. 2 is a schematic flow chart illustrating a batch operation and maintenance process in an embodiment of the SHELL script-based general counter system operation and maintenance method of the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments. It is noted that the aspects described below in connection with the figures and the specific embodiments are only exemplary and should not be construed as imposing any limitation on the scope of the present invention.
One embodiment of the general counter system operation and maintenance method based on the SHELL script comprises two parts of processing: the application start-stop process flow shown in fig. 1, and the batch operation and maintenance process flow shown in fig. 2. The specific processing modes of the two flows are described in detail below.
Fig. 1 shows a flow of an application start-stop process in an embodiment of the SHELL script-based general counter system operation and maintenance method of the present invention.
In the process of application start-stop processing, a mode of adding management to a multi-computer trust relationship and connection without secret login is involved. An operator connects and manages a plurality of application servers (namely target servers, hereinafter referred to as B servers) through an operation and maintenance operation server (hereinafter referred to as a server a), and directly jumps to the server B corresponding to the process by executing a ssh [ process & no ] command, such as ssh uskernel1, on the server a.
As shown in fig. 1, the specific steps of the secure login-free connection method are as follows.
Step 11: creating an account deploy on the server A, logging in by using the deploy account, and generating id _ rsa.pub (public key file) by using an ssh-keygen command (a command carried by a Linux system and with a format of ssh-keygen-t rsa).
Step 12: pub public key files on the A server are distributed to each B server through ssh-copy-id (command carried by the Linux system).
ssh-copy-id command format:
ssh-copy-id trade@1.1.1.1
ssh-copy-id trade@2.2.2.2
step 13: adding a process name and IP corresponding relation in an/etc/hosts file of an operating system, for example:
1.1.1.1uskernel1
2.2.2.2uskernel2
step 14: the registered account and IP are added in a-/. ssh/config configuration file, for example:
Host 2.2.2.2
Hostname uskernel2
User trade
after the operation is finished, the trust relationship is added, and the operation and maintenance operation server A can log in and connect each application server B without secret.
Fig. 1 shows a method for unified start and stop, where a dashed box in fig. 1 represents a server, and a frame for implementing the method represents a process or a script, where the method of the present invention is based on the foregoing secret-free login connection manner, and a management user deployment on a server a remotely manages related scripts and services of a target server by running a management script run _ batch, a process configuration file list. The operation management script, the process configuration file and the operation basic instruction script form a set of script calling framework for operation management, and support the addition of the operation basic instruction script containing specific instructions in the operation management script run _ batch, so that the function of executing specified instructions on any process is realized, including but not limited to process inspection, process connection number inspection, process port inspection, process log inspection, process compression and process configuration modification.
The run management script run _ batch is mainly composed of callall and callImpl methods. The running management script firstly realizes the analysis of the process configuration file through a callall method, and then realizes the calling of the specific instruction in the running basic instruction script through a callImpl method.
Run is configured in [ process ] [ no ], for example:
uskernel 1
uskernel 2
the basic instruction script can be executed according to the functional requirements, and the calling process of the basic instruction script based on the script calling framework of the set of running management is as follows, taking startall script as an example for explanation (the script calling framework of the running management in this embodiment has the meaning that the processing steps of all the basic instruction scripts are the same, so that only the service needs to be realized without paying attention to the process):
step a 1: a, a server executes a running basic instruction script startall;
step a 2: running a basic instruction script to call a run _ batch script;
step a 3: run _ batch script loads the list run file;
step a 4: a run _ batch script calls a callall () method, and callImpl () is sequentially used for calling a corresponding functional method startservice according to process configuration;
step a 5: the startservice executes the server where the secret-free connection process is located, and calls a start script of the server where the process is located;
step a 6: the start script completes the process start.
Fig. 2 shows a flow of batch operation and maintenance processing in an embodiment of the SHELL script-based general counter system operation and maintenance method of the present invention.
In fig. 2, a dashed line frame represents a server, and a solid line frame represents a process or a script, and the method is based on the foregoing login-free connection manner, where the management user, on the server a, implements a series of batch operations such as file distribution, configuration distribution, log backup, and streaming cleaning by issuing a management script, a process configuration file, list, run, and an operation and maintenance basic instruction script (backlog, clearlog), and the like.
The issuing management script, the process configuration file and the operation and maintenance basic instruction script form a set of script calling framework for issuing management, the operation and maintenance basic instruction script containing specific instructions is supported to be added in the issuing management script default _ batch, and the function of executing the specified instructions on the specified server is realized, wherein the function comprises server-based related batch operations including but not limited to batch compression, batch replication, batch recovery and batch copying.
Taking a backlog script as an example, a backlog script calling process is as follows (the meaning of the script calling framework for issuing management in this embodiment is that processing steps of all operation and maintenance basic instruction scripts are the same, and calling of other operation and maintenance basic instruction scripts only needs to be replaced correspondingly in the following processes):
step b 1: the a server executes the release management script,/deployment _ batch backlog.
Step b 2: run file run is loaded by the deployment _ batch script.
Step b 3: the run _ batch script calls a callall () method, and calls a corresponding functional method backlog according to the process configuration by using callImpl () in sequence.
Step b 4: and the backlog method executes the server where the secret-free connection process is located and calls a backlog.
Step b 5: sh script completes process log backup.
Examples of these batch operations are where cp starts with copy, backup starts with backup/copy, restore starts with investment in restore, and batch compression is in the backup approach.
Restoration executable file for/demand _ batch restoreobj
Restoring ini process configuration file
Restoring the functionality/system configuration file by/functionality _ batch restorecconfig
/restore stream file
Restoration operation and maintenance script for/deployment _ batch restorebase
Restoration of backup logs by/demand _ batch restorellog
/default _ batch backupobj backup executable
/deployment _ batch backupini backup ini process configuration file
Duplicate _ batch backup duplicate/system configuration file
/delete _ batch backup stream file
Duplicate _ base backup operation and maintenance script
Duplicate _ batch backuplog backup log
The method defines a set of standard structure of the installation directory and the release directory to support the script calling frame of the operation management and the release management in the method, and the standard structure of the directory is as follows:
under the administrative user deployment, the standard release directory format is as follows:
under the application user trade, the standard installation directory format is as follows:
the method is based on a deployment _ batch release management script calling framework and comprises the following steps of automatic deployment, automatic upgrading, automatic backup and automatic rollback.
Auto deploy,/deploy _ batch auto:
1. automatically creating a catalog, and automatically creating an operation catalog of a standard installation catalog structure under an application user by using make _ deployment _ dir;
2. automatically copying the script, and automatically copying the basic script under the run directory of the management user to the root directory of the application user by cpbase;
3. automatically copying initialization files, wherein the cpii automatically copies the initialization files under each process directory under the run directory of the management user to the bin of the process name folder corresponding to the application user;
4. automatically copying executable files, and automatically copying the executable files under each process directory under a run directory of a management user to bins of a process name folder corresponding to an application user by virtue of cpobj;
5. automatically copying library files, and automatically copying public library files under a lib directory of a management user to a standard lib folder of an application user by a cpcomlib;
6. automatically copying a configuration file, wherein a public configuration file in a config directory of a management user is automatically copied to a standard config folder of an application user by the cpconfig;
7. automatically configuring encryption, wherein the gmconfig automatically encrypts a configuration file under an application user;
8. and creating a file link, and automatically associating the configuration files of all processes under the application user to the configuration files under the unified config directory by linkconfig to realize the unified management of configuration.
Auto upgrade,/deployment _ batch update:
1. putting the upgrade package with the standard structure into an automatic upgrade directory;
2. automatically updating the script, and automatically copying the basic script under the updating catalog of the management user to the root catalog of the application user by the upscale base;
3. automatically updating the initialization file, and automatically copying and publishing the ini file under the upgrade directory of the management user to the bin of the process name folder corresponding to the application user by the upgrade file;
4. automatically updating the executable file, and automatically copying and releasing the executable file under each process directory under the upgrade directory of the management user to the bin of the process name folder corresponding to the application user;
5. automatically updating library files, and automatically copying public library files under an upgrade directory of a management user to a standard lib folder of an application user by upsgradelib;
6. and automatically updating and encrypting the configuration file, and automatically copying the public configuration file in the upgrade directory of the management user to the standard config folder of the application user.
Auto backup,/deployment _ batch backup:
1. automatically creating a catalog, and automatically creating a standard backup catalog under a management user by using make _ deployment _ dir;
2. automatically copying and compressing the specified script under the application user root directory to the standard backup directory by the backup base, and storing according to date and time;
3. automatically backing up an initialization file, automatically copying and compressing an ini file under an application user process directory to a standard backup directory by backini, and storing according to date and time;
4. automatically backing up executable files, and automatically copying and compressing the executable files in the application user process directory to be in the standard backup directory by backbj, and storing the executable files according to date and time;
5. automatically backing up the running water, automatically copying and compressing the running water files under a flow folder under the application user process directory to be under a standard backup directory by backing flow, and storing according to date and time;
6. automatically backing up the log, and automatically copying and compressing log files under a log folder under an application user process directory to be under a standard backup directory by backlog, and storing according to date and time;
7. and automatically backing up the configuration file, and automatically copying and compressing the log file under the config folder under the application user process directory to a standard backup directory by backconfig, and storing according to date and time.
Auto rollback/default _ batch restore:
1. selecting backup version information needing to be rolled back;
2. automatically generating md5 codes of all files of the existing version;
3. automatically rolling back the initialization file, and automatically decompressing and issuing an ini file under a management user backup directory to a bin of a process name folder corresponding to an application user by using restoreini;
4. automatically rolling back the executable file, and automatically decompressing and releasing the executable file under each process directory under the backup directory of the management user to the bin of the process name folder corresponding to the application user by the restoreobj;
5. automatically rolling back the library files, and automatically decompressing and distributing the public library files under the backup catalog of the management user to the standard lib folder of the application user by using the restorelib;
6. automatically rolling back and encrypting the configuration files, and automatically decompressing and issuing the public configuration files under the backup directory of the management user to the standard config folder of the application user;
7. automatic log streaming, wherein the restoreflow automatically decompresses and distributes the managed user backup directory downloading streaming files to the flow folder where each process of the application user is located;
8. and automatically rolling back the script, and automatically decompressing and distributing the basic script under the management user backup directory to the application user root directory by using the restorebase.
For the embodiments described above, the user profile and the application user trade involved in the management may be changed and replaced. The directory names run, bin, config, tools, commlib, apilinux, which relate to the standard distribution package format described above, may be changed.
Other basic methods that can be implemented are based on the unified run management script run _ batch and the release management script default _ batch.
Issuing a management script based on the deployment _ batch, wherein the management script comprises automatic deployment, automatic upgrade, automatic backup and automatic rollback, and the respective processing steps are as follows:
auto deploy/deploy _ batch auto
Automatic upgrade/upgrade _ batch upgrade
Automatic backup/default _ batch backup
Automatic rollback/default _ batch restore
Backup and recovery:
restoration executable file for/demand _ batch restoreobj
Restoring ini process configuration file
Restoring the functionality/system configuration file by/functionality _ batch restorecconfig
/restore stream file
Restoration operation and maintenance script for/deployment _ batch restorebase
Restoration of backup logs by/demand _ batch restorellog
/default _ batch backupobj backup executable
/deployment _ batch backupini backup ini process configuration file
Duplicate _ batch backup duplicate/system configuration file
/delete _ batch backup stream file
Duplicate _ base backup operation and maintenance script
Duplicate _ batch backuplog backup log
Custom deployment:
creating folder for/delete _ batch make _ delete _ dir
Copy operation and maintenance script for/deployment _ batch cpbase
Copy ini process configuration file for/default _ batch cpii
/default _ batch cpobj copy executable file
The/deployment _ batch cpconfig copy deployment/system configuration file
/deployment _ batch gmconfig encrypted deployment/system profile
The/deployment _ batch linkconfig connects the deployment/system configuration file
./deploy_batch cpall copy base ini obj config
/default _ batch cmpini alignment ini configuration file
/default _ batch cmpconfig to default/system configuration file
/default _ batch cmpobj alignment executable file
Copy/delete _ batch loadobj from ~/update _ pack to run
Basic checking:
/deployment _ batch chkvversion script version number
The currently defined usage of run _ batch is as follows:
./run_batch startservice
./run_batch stopservice
./run_batch showservice
while, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein, as would be understood by one skilled in the art.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. 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 ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A general counter system operation and maintenance method based on SHELL scripts is characterized by comprising an application start-stop processing flow and a batch operation and maintenance processing flow, wherein the application start-stop processing flow is used for adding a multi-machine trust relationship to allow an operation and maintenance to operate a first server to log in and connect other target servers without secret, and the batch operation and maintenance processing flow is used for executing a specified instruction on a specified target server;
wherein the application start-stop processing flow further comprises: the method comprises the steps that a management user on a first server remotely manages scripts and services of a target server through a running management script, a process configuration file and a running basic instruction script, wherein the running management script, the process configuration file and the running basic instruction script form a script calling framework of running management, and the running basic instruction script containing specific instructions is added into the running management script to realize the execution of specified instructions on any process;
wherein the batch operation and maintenance processing flow further comprises: the method comprises the steps that a management user on a first server realizes batch operation including file distribution, configuration distribution, log backup and flow clearing on the server through issuing a management script, a process configuration file and an operation and maintenance basic instruction script, wherein the issuing management script, the process configuration file and the operation and maintenance basic instruction script form a script calling frame of issuing management, the operation and maintenance basic instruction script containing specific instructions is added into the issuing management script, and the specified instructions are executed on a specified server.
2. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein the function of executing the specified instruction on any process by using the start-stop process flow includes but is not limited to: process inspection, process connection number inspection, process port inspection, process log inspection, process compression and process configuration modification.
3. The SHELL script-based general counter system operation and maintenance method as claimed in claim 1, wherein the operation management script is composed of two methods, which respectively implement parsing of the process configuration file and invoking of specific instructions in the operation basic instruction script.
4. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein the batch operation and maintenance processing flow implements functions of executing specified instructions on a specified server including but not limited to: batch compression, batch replication, batch recovery, batch copying.
5. The SHELL script-based universal counter system operation and maintenance method according to claim 1, further comprising setting a set of install directory structure and publish directory structure to support script calling framework for operation management and publish management.
6. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein an automatic deployment is defined in a script call framework of release management, wherein the automatic deployment comprises: automatic creation of directories, automatic copying of scripts, automatic copying of initialization files, automatic copying of executable files, automatic copying of library files, automatic copying of configuration files, automatic configuration encryption, creation of file links.
7. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein an automatic upgrade is defined in a release-managed script calling framework, wherein the automatic upgrade comprises: the method comprises the steps of putting an upgrade package with a standard structure under an automatic upgrade directory, automatically updating a script, automatically updating an initialization file, automatically updating an executable file, automatically updating a library file, and automatically updating and encrypting a configuration file.
8. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein an automatic backup is defined in a script calling framework for release management, wherein the automatic backup comprises: automatic creation of directories, automatic backup scripts, automatic backup of initialization files, automatic backup of executable files, automatic backup of running water, automatic backup of logs, automatic backup of configuration files.
9. The SHELL script-based universal counter system operation and maintenance method according to claim 1, wherein an automatic rollback is defined in a script call framework for release management, wherein the automatic rollback comprises: selecting backup version information needing to be rolled back, automatically generating md5 codes of all files of the existing versions, automatically rolling back an initialization file, automatically rolling back an executable file, automatically rolling back a library file, automatically rolling back and encrypting a configuration file, automatically logging and running water, and automatically rolling back a script.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110308663.XA CN113076130A (en) | 2021-03-23 | 2021-03-23 | General counter system operation and maintenance method based on SHELL script |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110308663.XA CN113076130A (en) | 2021-03-23 | 2021-03-23 | General counter system operation and maintenance method based on SHELL script |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113076130A true CN113076130A (en) | 2021-07-06 |
Family
ID=76613581
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110308663.XA Pending CN113076130A (en) | 2021-03-23 | 2021-03-23 | General counter system operation and maintenance method based on SHELL script |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113076130A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050080801A1 (en) * | 2000-05-17 | 2005-04-14 | Vijayakumar Kothandaraman | System for transactionally deploying content across multiple machines |
| CN101902357A (en) * | 2010-06-29 | 2010-12-01 | 中兴通讯股份有限公司 | Method and system for dispatching business server |
| CN102480749A (en) * | 2010-11-25 | 2012-05-30 | 中国移动通信集团浙江有限公司 | Method, device and system for remotely collecting host process information |
| CN104063287A (en) * | 2013-03-22 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Process management method and device |
| US9053236B1 (en) * | 2013-12-23 | 2015-06-09 | Emc Corporation | Automated directory services test setup utility |
| CN107193712A (en) * | 2017-06-01 | 2017-09-22 | 北京匡恩网络科技有限责任公司 | A kind of method and apparatus for management of process |
| US20180278724A1 (en) * | 2017-03-22 | 2018-09-27 | Mastercard International Incorporated | Systems and methods for automated application deployment management |
| CN110673858A (en) * | 2019-08-30 | 2020-01-10 | 四川新网银行股份有限公司 | Lightweight deployment method based on ssh secret-free login protocol |
| CN110912754A (en) * | 2019-12-12 | 2020-03-24 | 广州西麦科技股份有限公司 | Method and management system for batch operation and maintenance remote hosts |
| CN111506476A (en) * | 2020-04-15 | 2020-08-07 | 北京邮电大学 | Terminal authentication and process management system and control method thereof |
-
2021
- 2021-03-23 CN CN202110308663.XA patent/CN113076130A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050080801A1 (en) * | 2000-05-17 | 2005-04-14 | Vijayakumar Kothandaraman | System for transactionally deploying content across multiple machines |
| CN101902357A (en) * | 2010-06-29 | 2010-12-01 | 中兴通讯股份有限公司 | Method and system for dispatching business server |
| CN102480749A (en) * | 2010-11-25 | 2012-05-30 | 中国移动通信集团浙江有限公司 | Method, device and system for remotely collecting host process information |
| CN104063287A (en) * | 2013-03-22 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Process management method and device |
| US9053236B1 (en) * | 2013-12-23 | 2015-06-09 | Emc Corporation | Automated directory services test setup utility |
| US20180278724A1 (en) * | 2017-03-22 | 2018-09-27 | Mastercard International Incorporated | Systems and methods for automated application deployment management |
| CN107193712A (en) * | 2017-06-01 | 2017-09-22 | 北京匡恩网络科技有限责任公司 | A kind of method and apparatus for management of process |
| CN110673858A (en) * | 2019-08-30 | 2020-01-10 | 四川新网银行股份有限公司 | Lightweight deployment method based on ssh secret-free login protocol |
| CN110912754A (en) * | 2019-12-12 | 2020-03-24 | 广州西麦科技股份有限公司 | Method and management system for batch operation and maintenance remote hosts |
| CN111506476A (en) * | 2020-04-15 | 2020-08-07 | 北京邮电大学 | Terminal authentication and process management system and control method thereof |
Non-Patent Citations (1)
| Title |
|---|
| CODERCHENHAO: "部署-shell脚本实现远程部署", Retrieved from the Internet <URL:https://blog.csdn.net/qq_24295577/article/details/108018815?> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6026438A (en) | Dynamic workstation configuration processor | |
| US20030009752A1 (en) | Automated content and software distribution system | |
| JP4159394B2 (en) | Method and recording medium for copying source file between networked resources | |
| US7809949B2 (en) | Configuration of a computing device in a secure manner | |
| US9606787B1 (en) | Method and system for restoring software | |
| US7664834B2 (en) | Distributed operating system management | |
| US7802247B1 (en) | Method and system for restoring software | |
| US7831968B1 (en) | Method and system for restoring software | |
| US20080276234A1 (en) | Data center edition system and method | |
| US8645672B2 (en) | Configuring a computer system for a software package installation | |
| US20010042112A1 (en) | Methods and systems for obtaining computer software via a network | |
| US20110145810A1 (en) | Method in a network of the delivery of files | |
| US20070283343A1 (en) | Installation of a Bootable Image for Modifying the Operational Environment of a Computing System | |
| US8799890B2 (en) | Generating a version identifier for a computing system based on software packages installed on the computing system | |
| US20080040714A1 (en) | Method and system for automatic computer and user migration | |
| US20060080653A1 (en) | Methods and systems for patch distribution | |
| US20110055544A1 (en) | Systems and methods for tracking a history of changes associated with software packages and configuration management in a computing system | |
| US8887143B1 (en) | System and services for handling computing environments as documents | |
| CN101802807A (en) | Software deployment in the large-scale networked systems | |
| US8523056B1 (en) | Card activated cash dispensing automated banking machine customization system and method | |
| WO2008124181A1 (en) | Data center edition system and method | |
| US8984101B1 (en) | System and method for model-based configuration of a server cluster | |
| CN113076130A (en) | General counter system operation and maintenance method based on SHELL script | |
| US11748211B2 (en) | Automatic update of network assets using gold images | |
| US20210334396A1 (en) | Creating vendor-neutral data protection operations for vendors' application resources |
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 |