CN116991535A - Method for node deployment based on atomic soft facilities - Google Patents
Method for node deployment based on atomic soft facilities Download PDFInfo
- Publication number
- CN116991535A CN116991535A CN202310994153.1A CN202310994153A CN116991535A CN 116991535 A CN116991535 A CN 116991535A CN 202310994153 A CN202310994153 A CN 202310994153A CN 116991535 A CN116991535 A CN 116991535A
- Authority
- CN
- China
- Prior art keywords
- atomic
- soft
- facility
- node
- operating system
- 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 40
- 238000009434 installation Methods 0.000 claims abstract description 68
- 238000004519 manufacturing process Methods 0.000 claims abstract description 19
- 238000005192 partition Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 15
- 238000013515 script Methods 0.000 claims description 11
- 238000005516 engineering process Methods 0.000 claims description 10
- 230000003287 optical effect Effects 0.000 claims description 6
- 238000005096 rolling process Methods 0.000 claims description 5
- 230000001419 dependent effect Effects 0.000 claims description 4
- 238000007726 management method Methods 0.000 claims description 4
- 238000013461 design Methods 0.000 claims description 2
- 230000003044 adaptive effect Effects 0.000 claims 1
- 238000011084 recovery Methods 0.000 abstract description 12
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000008439 repair process Effects 0.000 abstract description 3
- 238000011900 installation process Methods 0.000 abstract description 2
- 230000004048 modification Effects 0.000 description 12
- 238000012986 modification Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 8
- 238000010276 construction Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005553 drilling Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method for node deployment based on an atomic soft facility. The method comprises the following steps: s1, manufacturing an atomic soft facility, and integrating an operating system, a virtualization layer and a service application into an atomic soft facility installation package according to an atomic soft facility description file; s2, deploying an atomic soft facility, wherein one node uses a set of installation packages of the atomic soft facility, and the atomic soft facility installation packages are started on the node to install an operating system, configure network and host parameters, automatically install a virtualization layer and automatically install service applications; s3, updating the atomic soft facilities; s4, backing up and recovering the atomic soft facilities. The deployment method of the application greatly simplifies the installation process, changes the fault recovery process into reinstallation without repair, shields complex technical details, reduces the technical threshold of users, and enables first-line staff to use the device for installation and maintenance, thereby saving labor cost without a large number of second-line support engineers.
Description
Technical Field
The application relates to a containerization technology, in particular to a method for node deployment based on an atomic soft facility, which belongs to the technical field of operating system layer virtualization.
Background
Virtualization technologies (e.g., KVM, xen, hyper-v, etc.) and containerization technologies (e.g., LXC, LXD, docker, kubernetes, K S, etc.) are currently employed as running carriers for business applications, and have been largely validated and applied in data centers, edge computing, etc., but face the following problems:
1) At present, the construction of data center nodes and edge nodes (physical machines and virtual machines) adopts a layer-by-layer construction mode, namely, a server, an operating system, a virtualization layer and service application are respectively constructed. The construction of each layer has higher technical threshold and extremely strong professional, and the first-line user basically does not have the capability of complete construction, especially when encountering faults, the method cannot solve the problems by itself, so that the technical requirements on the first-line user are reduced in a simple and effective mode, and the installation and management operation flow is simplified.
2) In the process of building the data center node and the edge node, each layer needs to be continuously modified, and the modification of each layer is often independent, for example: system upgrades, configuration modifications, patch updates, etc. Temporary repairs and adjustments may also occur when problems occur. Continued modification can make the configuration of the nodes more and more different and difficult to replicate. During operation, the node is also modified, and the last modification is difficult to completely consider the previous modification, which may cause unexpected side effects in subsequent modification. Eventually, the node will be in an "unknown state," unique and fragile.
3) In the event of a disaster, it is difficult to quickly reconstruct equivalent nodes due to the uniqueness of the nodes. Even in the best case, the nodes have all the modifications recorded, but since the configuration of the nodes is determined after being online and may continuously change, it is difficult to perform a previous fault exercise. Therefore, a scheme which has certain fault self-healing capability and can perform advanced fault drilling and quick replacement is needed, so that the node can be recovered for use in a short time, and the whole service is not interrupted.
The container technology is a virtualization technology, and does not need to virtualize the whole operating system, only needs to virtualize a small-scale environment, has high starting speed, and basically does not need to consume extra system resources except for running applications in the environment.
The K8S technology is a technology for scheduling and arranging containers, the service application is in the form of a container, and the service discovery and scheduling, load balancing, service fault self-healing and service elastic capacity expansion advanced characteristics of the service application can be realized by utilizing the technical characteristics of the K8S. But the K8S is composed of a management node and a service node, the core processes of the K8S are etcd, apiserver, kube-controller-manager and kube-scheduler, kubelet, kube-proxy, each process operates independently, and a user needs to maintain all the processes.
The layering technical scheme adopted in the data center at present, namely, the server, the operating system, the virtualization layer and the business application are completely layered and maintained by different personnel. The logic structure is as shown in figure 1.
The deployment mode is stepwise installation, namely, an operating system, a virtualization layer and business applications are respectively installed by professional engineers, and the installation and deployment of the whole system can be completed only by cooperation of multiple engineers in each field, and the specific steps are as follows:
(1) the preparation server prepares the server hardware, for example, by a hardware engineer, accesses a power line, a network line, a storage line, and the like, and makes the hardware have a condition for startup.
(2) The operating system is prepared, for example, by a system engineer installing the operating system on a server, configuring a network, mounting a storage disk, and partitioning a file system, so that the operating system has conditions for use.
(3) The virtualization layer is prepared, for example, when a container engineer installs a container on an operating system to run (e.g., dock), K8S is installed, and software parameters are adjusted to make the virtualization environment have running conditions.
(4) The service application is deployed, the application engineer adjusts various deployment parameters of the service application according to the basic condition of the existing environment, the service data is imported, the service application is confirmed to run normally, and finally the service application is delivered to the user for use.
The disadvantages of the current deployment approach are:
1) High technical threshold
The ability of hardware, operating systems, K8S and business applications, where any layer presents problems, even with specialized operating instruction manuals, makes it difficult for first-line personnel to address according to the instruction manuals because of their expertise and complexity. In many cases, different layers are mutually influenced before, the problems are comprehensively generated, and the deployment and maintenance difficulties are increased. There is a need for an integrated solution.
2) Frequent updating of nodes is difficult to be effectively compatible and recorded, and finally independence and vulnerability of the nodes are caused. There is a need to maintain node replicability and state certainty.
3) The prior art scheme is difficult to quickly construct an equivalent environment, is difficult to exercise in advance, is difficult to form an emergency plan, and is difficult to ensure business continuity. Service continuity needs to be ensured during update and failure.
4) Slow delivery and failure recovery
By adopting the existing layered structure and the step-by-step installation scheme, technicians of each level are required to be matched with each other to perform installation and deployment step by step during delivery, and the technicians of each level are required to perform layer-by-layer recovery when faults occur; the failure recovery time is the same as this.
Disclosure of Invention
Aiming at the technical problems, the technical scheme of the application takes the operating system, the virtualization layer and the business application as a whole, and the operating system, the virtualization layer and the business application are uniformly installed, updated and recovered to form an atomic soft facility. The main flow comprises the following steps: the method comprises the steps of manufacturing an atomic soft facility, deploying the atomic soft facility, updating the atomic soft facility, and backing up and recovering the atomic soft facility. The atomic hard facilities can be formed by adding hardware on the basis of the atomic soft facilities.
The application provides a method for node deployment based on an atomic soft facility, which comprises the following steps:
s1, manufacturing an atomic soft facility, and integrating an operating system, a virtualization layer and a service application into an atomic soft facility installation package according to an atomic soft facility description file;
s2, deploying an atomic soft facility, wherein one node uses a set of installation packages of the atomic soft facility, and the atomic soft facility installation packages are started on the node to install an operating system, configure network and host parameters, automatically install a virtualization layer and automatically install service applications;
s3, updating the atomic soft facilities;
s4, backing up and recovering the atomic soft facilities.
Further, the atomic soft facility description file is used for describing the technology, version, architecture and characteristics adopted by an operating system, a virtualization layer and business application in an installation package.
Further, the atomic soft plant installation package structure includes: operating system, virtualization layer, business applications and other dependent software as needed.
Further, the virtualization layer may be installed automatically when the operating system is installed, including but not limited to script, operating system preassembly; the business application layer can be automatically installed and configured based on the virtualization layer, including but not limited to scripts and snapshot modes.
Further, the S1 atomic soft facility installation package is manufactured by acquiring a process of forming an atomic soft facility installation package corresponding to software according to requirements of the atomic soft facility description file, pulling the description file from the atomic soft facility description file in the atomic soft facility installation package manufacturing process, pulling dependent software from a software library, and finally manufacturing the atomic soft facility installation package.
Further, the atomic soft facility installation package should be manufactured with the following technical characteristics:
1) Supporting setting the read-only of the file system partition;
2) The file system snapshot supports snapshot of the partition, and system rollback can be carried out through the snapshot to recover data;
3) Thing update operation: the transaction update does not affect the currently running operating system, and a new snapshot can be entered after restarting.
Further, the deployment of the S2 atomic soft facility specifically includes:
when the data center node and the edge node are built, atomic soft facility deployment can be carried out by first-line personnel, and a professional engineer does not need to go to the site to carry out second-line guidance; the deployment mode of the atomic soft facility installation package includes, but is not limited to, the deployment of the optical disc on a physical machine, the deployment of the optical disc on a virtual machine and a cloud host as a virtual mirror image.
Furthermore, the updating of the S3 atomic soft facilities needs to reinstall the installation packages of the atomic soft facilities, and rolling updating and upgrading can be performed according to the cluster deployment mode, so that normal access of the service is not affected.
Further, the backup of the S4 atomic soft facility specifically includes:
backup can be divided into three layers: backup of operating system, virtualization layer, business data.
Further, the backup of the operating system mainly deals with repairable faults at the operating system level, the backup of the virtualization layer mainly comprises metadata of all service applications deployed in the cluster, and the deployed service applications are mainly handled to be deleted by misoperation, so that the configuration of the service applications is changed, or the fault of the virtualization layer is caused; the backup of the service data is mainly the data required by the normal operation of the backup service application, including but not limited to database backup.
The application has the advantages compared with the prior art that:
1) Higher consistency and reliability in data center and edge node construction, and simpler, more predictable deployment process.
2) The node can be replaced strongly, and single-point influence is avoided, so that the overall stability is ensured.
3) It is easier to seamlessly add more identical nodes to the infrastructure to simplify horizontal expansion.
4) And labor cost is saved.
The installation process is simplified greatly, the fault recovery process is changed into reinstallation without repair, complex technical details are shielded, the technical threshold of a user is reduced, and the installation and maintenance of the first-line personnel are possible by using the fault recovery process, so that a large number of second-line support engineers are not required to be equipped for the fault recovery process, and the labor cost is saved.
5) And service continuity is improved.
By means of the isolation mechanism provided by the virtualization layer, the same business application can have multiple copies running at the same time, the multiple copies provide services at the same time, and the business application has the functions of high availability and load balancing, wherein when one copy fails, the functions of an application module are not affected. By means of the fault self-healing characteristic of the virtualization layer, the fault copy can perform self-healing operation at the first time without manual intervention.
Rollback may be performed by snapshot with file system snapshot and transaction update mechanisms to recover data.
By means of the rolling update mode of the atomic soft facility, service continuity during update and recovery can be guaranteed.
6) And (5) convenient transportation and recovery.
By means of the read-only characteristic and the object updating characteristic, the defects that a system is not available due to misoperation and tampering can be avoided, and a plurality of troubles such as version control and the like are omitted in the operation and maintenance process of the system. The system has problems, and the available snapshot can be restored through convenient restoration operation; if the system fails completely, the atomic soft installation package can be quickly reinstalled and the system is restored integrally.
7) And (5) quick delivery.
The time and difficulty of personnel on-site implementation are greatly reduced, the delivery period is shortened, and even the atomic soft facilities can be directly delivered and deployed by users.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a prior art data center employing a hierarchical scheme;
FIG. 2 is a schematic illustration of an atomic soft plant installation package structure provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of an atomic soft facility installation package manufacturing process provided by an embodiment of the present application;
FIG. 4 is a schematic diagram of a deployment flow of an atomic soft facility provided by an embodiment of the present application;
FIG. 5 is a schematic diagram of an architecture prior to an atomic soft plant upgrade provided by an embodiment of the present application;
FIG. 6 is a schematic diagram of an atomic soft-plant upgrade first node architecture provided by an embodiment of the present application;
FIG. 7 is a schematic diagram of an architecture of an atomic soft plant after upgrading a first node according to an embodiment of the present application;
FIG. 8 is a schematic diagram of an atomic soft facility upgrade second third node architecture provided by an embodiment of the present application;
fig. 9 is a schematic diagram of an architecture of an atomic soft facility after upgrading a second third node according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The technical scheme of the application mainly comprises the following steps: the method comprises the steps of manufacturing an atomic soft facility, deploying the atomic soft facility, updating the atomic soft facility, and backing up and recovering the atomic soft facility. The atomic hard facilities can be formed by adding hardware on the basis of the atomic soft facilities.
1. Fabrication of atomic soft facilities
The atomic soft facilities are manufactured by integrating an operating system, a virtualization layer and a business application into an installation package according to an atomic soft facility description file, and the format of the installation package comprises but is not limited to ISO.
1) Atomic soft plant description file
The atomic soft facility description file is used to describe the technology, version, architecture, features, etc. employed by the operating system, virtualization layer, business application in the installation package.
2) Atomic soft facility installation package structure
The atomic soft plant installation package composition structure is shown in fig. 2 below.
The atomic soft-facility installation contains the operating system, virtualization layers (including but not limited to KVM, xen, hyper-v, LXC, LXD, docker, kubernetes, K3S, etc.), business applications, and other dependent software as needed. The virtualization layer can be automatically installed when the operating system is installed, and the method comprises the modes of script, operating system preassembly and the like. The business application layer can be automatically installed and configured based on the virtualization layer, and the method comprises the modes of script, snapshot and the like.
3) Atomic soft facility installation package manufacturing
As shown in fig. 3, the process of obtaining the corresponding software to form the atomic soft facility installation package according to the requirements of the atomic soft facility description file is divided into 3 steps:
the first step: the atomic soft-plant description file is pulled. The description file is a formatted expression of the content of one-time installation and deployment, if a certain installation and deployment needs to use a micro operating system, and a dock and K3S are used as a container virtualization base to carry a certain service software app, the formatted expression is shown as an atomic soft facility description file on the right of fig. 3. The description file describes information such as names, types, versions, and adaptation configurations of the components.
And a second step of: and pulling corresponding software from the software library according to the requirements of the atomic soft facility description file. The software library uses a modularized design to perform modularized management on the software of each component so as to realize rapid software assembly. The modules in the software library include software run program files, configuration files, deployment scripts, and the like. And pulling corresponding software from the software library according to the atomic description file. If K3S is pulled as container scheduling software, the K3S module contains binary deployment files, configuration files, deployment scripts and the like of the K3S.
And a third step of: and manufacturing and assembling the atomic soft facility installation package according to the atomic soft facility description file and the pulled software. And assembling all the modules in the pulled software library, wherein the modules comprise software of different levels such as an operating system, a virtualization layer, a business application and the like. In the manufacturing process, deployment scripts of all modules are connected in series, so that the installation of the whole atomic soft facility can be completed through one operation. Meanwhile, in the process of serial assembly, a file system read-only partition is set, and a file system snapshot function is started. The assembled atomic soft facility installation package is an archived compressed file, and as shown in the atomic soft facility installation package in fig. 3, the assembled atomic soft facility installation package contains information such as the name, version, installation environment architecture and the like of the deployment task.
The atomic soft facility installation package manufacturing method has the following technical characteristics:
(1) file system read-only: all files under the root partition (/) of the operating system are read only, and a user or a program cannot modify any file under the directory during running, so that the file tampering or misoperation of the root partition can be prevented; the partition copy-on-write mode is supported, e.g., user modifications to/etc are limited to the current snapshot.
(2) File system snapshot: and the snapshot is supported to be made on the partition, the first snapshot is obtained after the system is installed, and the snapshot can be triggered manually or automatically later. When the system fails, such as a human mishandling modifies or deletes files in the/etc partition, the system rollback may be performed through the snapshot to recover the data.
(3) Thing update operation: the modification of the root partition of the operating system, such as installing a new software package, modifying a file, etc., must be performed in a transaction update manner, and cannot be directly operated. The transaction update is atomic, either all successful or all failed, and triggers a snapshot. The transaction update does not affect the currently running operating system, and a new snapshot can be entered after restarting.
2. Deployment of atomic soft facilities
When the data center node and the edge node are built, atomic soft facility deployment can be carried out by first-line personnel, and a professional engineer does not need to go to the site to carry out second-line guidance.
The deployment mode of the atomic soft facility installation package includes, but is not limited to, the deployment of the optical disc on a physical machine, the deployment of the optical disc on a virtual machine and a cloud host as a virtual mirror image.
Fig. 4 shows a deployment flow of an atomic soft facility, which specifically includes: installing an operating system, configuring network and host parameters, automatically installing a virtualization layer, and automatically installing business applications.
3. Updating of atomic soft facilities
All configurations have been cured after the deployment of the atomic soft plant and should not be modified. If the installation package needs to be modified, the installation package of the new version of the atomic soft facility needs to be manufactured again to update the atomic soft facility.
The update of the atomic soft facilities requires reinstallation of the installation packages of the atomic soft facilities, and service shutdown is brought to the situation of single-node deployment. Aiming at the cluster deployment mode, rolling update and upgrading can be carried out without influencing the normal access of the service.
Taking a three-node cluster deployment mode as an example, the process of updating an atomic soft facility from a v1 version to a v2 version is described:
1) Before upgrading, all three nodes provide v1 version of service, and the architecture is shown in fig. 5.
2) The binding between the service application and the node is shielded by the virtualization layer, so that the service on the first node can be adjusted to run on the second and third nodes, and the second and third nodes provide v1 version service to stop the first node, and the architecture is shown in fig. 6.
3) Updating the atomic soft facility of the first node: a new atomic soft installation package is installed on the first node, upon completion of which the business application will be automatically launched. At this time, the first node is an independent cluster and operates v2 version service; the second three nodes are an independent cluster and run v1 version services. The architecture is shown in fig. 7.
4) Updating an atomic soft facility by two and three nodes: the second and third nodes are stopped, and a new atomic soft facility installation package is installed on the second and third nodes, and the architecture of the new atomic soft facility installation package is shown in fig. 8.
5) And the second node and the third node are updated and added into the cluster of the first node. At this time, all three nodes are in the new cluster, and all provide v2 version service, and the architecture is shown in fig. 9.
4. Backup and recovery of atomic soft facilities
Backup of an atomic soft facility can be divided into three layers: backup of operating system, virtualization layer, business data.
Backup of the operating system mainly handles repairable failures at the operating system level, such as mishandling of software that deleted the operating system, or changing to a wrong configuration.
The backup of the virtualization layer mainly comprises metadata of all service applications deployed in the cluster, and mainly aims at misoperation, deleting the deployed service applications, changing the configuration of the service applications or causing the failure of the virtualization layer.
The backup of the service data is mainly the data required by the normal operation of the backup service application, including but not limited to database backup.
When the atomic soft facility encounters a repairable fault, the atomic soft facility can be recovered by using backup; when an unrepairable fault is encountered, the node needs to be reinstalled or replaced with a new node for recovery. The process is similar to the update process, except that the atomic soft facilities are installed, which are still the original versions.
By utilizing the atomic soft facilities, the production environment can be quickly simulated and built, and disaster recovery exercise in advance can be performed to form a plan.
The key points of the technical scheme of the application are as follows:
1) And the operating system, the virtualization layer and the business application are integrally installed, updated and restored uniformly to form an atomic soft facility.
2) The atomic soft facility description file can be flexibly manufactured and adapted to different architectures, and the atomic soft facility with different technical options is adopted.
3) The atomic soft facility installation package manufacturing method has the following technical characteristics:
(1) file system read-only: all files under the root partition (/) of the operating system are read only, and a user or a program cannot modify any file under the directory during running, so that the file tampering or misoperation of the root partition can be prevented; the partition copy-on-write mode is supported, e.g., user modifications to/etc are limited to the current snapshot.
(2) File system snapshot: and the snapshot is supported to be made on the partition, the first snapshot is obtained after the system is installed, and the snapshot can be triggered manually or automatically later. When the system fails, such as a human mishandling modifies or deletes files in the/etc partition, the system rollback may be performed through the snapshot to recover the data.
(3) Thing update operation: the modification of the root partition of the operating system, such as installing a new software package, modifying a file, etc., must be performed in a transaction update manner, and cannot be directly operated. The transaction update is atomic, either all successful or all failed, and triggers a snapshot. The transaction update does not affect the currently running operating system, and a new snapshot can be entered after restarting.
4) The existing hierarchical architecture and step-by-step installation mode do not provide a relatively simplified installation and deployment mode, and the deployment of the atomic soft facilities greatly simplifies the deployment process. And deployment of the atomic soft facilities is performed based on the installation packages of verification and version control, and deployment does not depend on the previous state, so that the deployment does not fail.
5) The update of the atomic soft facility keeps the state of the node to be always known and reproducible, and the node is not in an unknown state due to frequent changes. The clustered update mode can easily implement a blue-green deployment or a rolling update, which means that the business application does not need to be interrupted.
6) The atomic soft facilities can be backed up, have certain fault self-healing capability, and can perform advanced fault exercise to form an emergency plan, so that the nodes can be recovered for use in a short time, and the overall service is stable.
It will be readily appreciated by those skilled in the art that the foregoing description is merely a preferred embodiment of the application and is not intended to limit the application, but any modifications, equivalents, improvements or alternatives falling within the spirit and principles of the application are intended to be included within the scope of the application.
Claims (13)
1. A method for node deployment based on an atomic soft facility, comprising the steps of:
s1, manufacturing an atomic soft facility, and integrating an operating system, a virtualization layer and a service application into an atomic soft facility installation package according to an atomic soft facility description file;
s2, deploying an atomic soft facility, wherein one node uses a set of installation packages of the atomic soft facility, and the atomic soft facility installation packages are started on the node to install an operating system, configure network and host parameters, automatically install a virtualization layer and automatically install service applications;
s3, updating the atomic soft facilities;
s4, backing up and recovering the atomic soft facilities.
2. The method for node deployment based on an atomic soft facility according to claim 1, wherein,
the atomic soft facility description file is used for describing the technology, version, architecture and characteristics adopted by an operating system, a virtualization layer and business application in an installation package.
3. The method for node deployment based on an atomic soft facility according to claim 1, wherein,
the atomic soft facility installation package structure comprises: operating system, virtualization layer, business applications and other dependent software as needed.
4. The method for node deployment based on an atomic soft facility according to claim 3, wherein,
the virtualization layer automatically installs when the operating system is installed, including but not limited to scripts and operating system preassembling modes; the business application layer is based on the virtualization layer and automatically performs installation and configuration, including but not limited to script and snapshot modes.
5. The method for node deployment based on an atomic soft facility according to claim 1, wherein,
the S1 atomic soft facility installation package is manufactured by acquiring a process of forming the atomic soft facility installation package by corresponding software according to the requirement of an atomic soft facility description file, and specifically comprises the following steps:
(1) Pulling an atomic soft facility description file from the atomic soft facility description file in the manufacturing process of the atomic soft facility installation package;
(2) Pulling corresponding software from a software library according to the requirements of the atomic soft facility description file;
(3) And manufacturing and assembling the atomic soft facility installation package according to the atomic soft facility description file and the pulled software.
6. The method for node deployment based on an atomic soft facility according to claim 5, wherein,
the description file is a formatted expression of the content of one-time installation deployment, and describes names, types, versions and adaptive architecture information of each component.
7. The method for node deployment based on an atomic soft facility according to claim 5, wherein,
the software library uses a modularized design to perform modularized management on software of each component so as to realize rapid software assembly; modules in the software library include, but are not limited to, software runtime files, configuration files, deployment scripts.
8. The method for node deployment based on an atomic soft facility according to claim 5, wherein,
assembling all the modules in the pulled software library, wherein the modules comprise software of different levels of an operating system, a virtualization layer and business application; in the manufacturing process, deployment scripts of all modules are connected in series, so that the installation of the whole atomic soft facility can be completed through one-time operation; meanwhile, in the process of serial assembly, a file system read-only partition is set, and a file system snapshot function is started.
9. The method for node deployment based on an atomic soft facility according to claim 1, wherein,
the atomic soft facility installation package manufacturing method has the following technical characteristics:
1) Supporting setting the read-only of the file system partition;
2) The file system snapshot supports snapshot of the partition, and system rollback can be carried out through the snapshot to recover data;
3) Thing update operation: the transaction update does not affect the currently running operating system, and a new snapshot can be entered after restarting.
10. The method for node deployment based on the atomic soft facility according to claim 1, wherein the deployment of the S2 atomic soft facility specifically comprises:
when the data center node and the edge node are built, first-line personnel are used for carrying out atomic soft facility deployment, and professional engineers do not need to go to the site to carry out second-line guidance; the deployment mode of the atomic soft facility installation package includes, but is not limited to, the deployment of the optical disc on a physical machine, the deployment of the optical disc on a virtual machine and a cloud host as a virtual mirror image.
11. The method for node deployment based on an atomic soft facility according to claim 1, wherein,
the updating of the S3 atomic soft facilities needs to reinstall the installation packages of the atomic soft facilities, and rolling updating and upgrading are carried out according to the cluster deployment mode, so that the normal access of the service is not affected.
12. The method for node deployment based on the atomic soft facility according to claim 1, wherein the backup of the S4 atomic soft facility specifically comprises:
backup is divided into three layers: backup of operating system, virtualization layer, business data.
13. The method for node deployment based on an atomic soft facility according to claim 12, wherein,
the backup of the operating system mainly aims at repairing faults of the operating system level, the backup of the virtualization layer mainly comprises metadata of all service applications deployed in the cluster, and the deployed service applications are mainly deleted by misoperation, or the configuration of the service applications is changed, or the fault of the virtualization layer is caused; the backup of the service data is mainly the data required by the normal operation of the backup service application, including but not limited to database backup.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310994153.1A CN116991535A (en) | 2023-08-08 | 2023-08-08 | Method for node deployment based on atomic soft facilities |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310994153.1A CN116991535A (en) | 2023-08-08 | 2023-08-08 | Method for node deployment based on atomic soft facilities |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116991535A true CN116991535A (en) | 2023-11-03 |
Family
ID=88528107
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310994153.1A Pending CN116991535A (en) | 2023-08-08 | 2023-08-08 | Method for node deployment based on atomic soft facilities |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116991535A (en) |
-
2023
- 2023-08-08 CN CN202310994153.1A patent/CN116991535A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230153210A1 (en) | Application migration between environments | |
| CN107515776B (en) | Method for upgrading service continuously, node to be upgraded and readable storage medium | |
| US9734019B2 (en) | Systems and methods for host image transfer | |
| US20200110675A1 (en) | Data backup and disaster recovery between environments | |
| CN102782656B (en) | Systems and methods for failing over cluster unaware applications in a clustered system | |
| EP2372555B1 (en) | Repurposable recovery environment | |
| US8676762B2 (en) | Efficient backup and restore of a cluster aware virtual input/output server (VIOS) within a VIOS cluster | |
| US8886995B1 (en) | Fault tolerant state machine for configuring software in a digital computer | |
| US7716517B2 (en) | Distributed platform management for high availability systems | |
| CN102207879B (en) | Hot-updating method and hot-updating system of Lua script | |
| EP2545450A1 (en) | System and method to define, visualize and manage a composite service group in a high-availability disaster recovery environment | |
| WO2009012132A1 (en) | Maintaining availability of a data center | |
| WO2007141180A2 (en) | Apparatus and method for cluster recovery | |
| EP2156286A1 (en) | Dynamic cli mapping for clustered software entities | |
| US20060123018A1 (en) | Algorithm for maximizing application availability during automated enterprise deployments | |
| CN112434008A (en) | Distributed database upgrading method, device and medium | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| US11757697B2 (en) | System and method of distributed edge configuration management | |
| CN116991535A (en) | Method for node deployment based on atomic soft facilities | |
| CN106850598A (en) | Uniform resource management system and method for whole-ship computing environment | |
| CN116360834A (en) | Kubernetes cluster in-situ upgrading method and system based on OSTree | |
| CN115426370A (en) | Heterogeneous container cloud platform and edge manufacturing service subscription implementation method thereof | |
| EP2490122A2 (en) | Hardware turnkey mobility | |
| CN109995560A (en) | Cloud resource pond management system and method | |
| Masetti et al. | Increasing Availability by Implementing Software Redundancy in the CMS Detector Control System |
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 |