Standardized product deployment operation and maintenance method based on offline environment and computer equipment

Abstract

The invention discloses a standardized product deployment operation and maintenance method based on an off-line environment, computer equipment and a computer readable storage medium, and the method comprises the steps: S1, executing a one-key initialization process, rapidly building a visual platform with an Ansible Semaphore as a core through an off-line medium and an automatic script, and achieving zero-threshold starting; s2, a visual deployment process is executed, deployment is completed in a visual mode at an Ansible Semaphore webpage end on the basis of a platform built by a one-key initialization process, and a multi-scene Ansible Playbook is built in the platform; s3, a visual operation and maintenance process is executed, a'modular script visual platform 'is taken as a core, a monitoring alarm scene, a log query scene, a component upgrading scene and a version rollback scene are covered, and all operations are based on offline preset resources; and S4, executing a visual publishing process, and adopting a closed-loop system in which an offline medium is taken as a carrier, canary publishing is taken as verification and rolling updating is taken as execution, so as to ensure that services are published without interruption in an offline environment.

Description

Technical Field

[0001] This invention relates to the field of software deployment technology, and more specifically, to a standardized product deployment and maintenance method, computer equipment, and computer-readable storage medium based on an offline environment. Background Technology

[0002] With the steady progress of large-scale digitalization projects, the functional modules of enterprise-level systems continue to expand, broadly covering multiple areas such as core business, data management, and risk control. Enterprises' demands for system deployment flexibility, operational efficiency, and data security are increasing daily.

[0003] From a network environment perspective, in industries with extremely high data confidentiality requirements, such as energy, finance, and military, many core business systems need to run in physically isolated offline environments. Traditional manual deployment methods are inefficient and prone to configuration errors due to human error. In complex systems containing hundreds of microservices, a complete deployment often takes days or even weeks.

[0004] Meanwhile, the IT infrastructure of enterprises of different sizes varies significantly. Large enterprise groups tend to prefer on-premises deployment to ensure the security of core data, while SMEs prefer the SaaS model to reduce operating costs. Against this backdrop, hybrid cloud deployment is gradually becoming the industry mainstream.

[0005] In complex scenarios such as peak traffic surges and cross-departmental data collaboration, traditional operation and maintenance (O&M) models struggle to respond quickly to changes, placing higher demands on system scalability and stability. Against this backdrop, offline automated deployment and O&M solutions based on containerization technology and orchestration tools have emerged. By building standardized image repositories and automated pipelines, system deployment and updates can be achieved in minutes in offline environments, significantly improving resource utilization and fault recovery speed. Building a standardized and highly secure offline automated O&M deployment system that adapts to various business scenarios has become a key support for driving enterprise digital transformation.

[0006] In current system operation and maintenance deployment practices, traditional models are gradually revealing many drawbacks and are unable to meet the needs of modern management:

[0007] 1. Poor architecture design and environment adaptability.

[0008] Traditional systems mostly adopt a monolithic architecture, with high coupling between functional modules, making flexible deployment impossible and leading to resource waste or functional redundancy. Furthermore, their fixed deployment patterns make them incompatible with various operating environments, failing to meet the diverse needs of different users. Some systems have even been forced to abandon core functionality iterations due to environmental incompatibility.

[0009] 2. Weak operational response and scalability.

[0010] When faced with peak usage periods and traffic spikes, traditional deployments lack automatic scaling mechanisms, making them prone to system lag and even crashes. Maintenance relies on manual operations, resulting in long average work order processing times and delayed fault response. Furthermore, monitoring systems are fragmented, covering only the infrastructure level and lacking integrated monitoring of business health and application performance, making it difficult to provide early warnings of risks.

[0011] 3. Insufficient technology stack and security compliance

[0012] The system's technology selection is fragmented, with a lack of unified standards for front-end and back-end frameworks, databases, and middleware, resulting in high maintenance costs and difficulties in troubleshooting. Security protection largely adopts a "device stacking" model, leading to a disjointed protection system and insufficient encryption for data transmission and storage. This fails to meet security specifications and is ill-equipped to counter advanced cyberattacks. Furthermore, the inadequate backup mechanism poses a risk of data loss.

[0013] The above issues directly constrain the system's operational efficiency and security controllability. Only through a systematic approach that integrates modular architecture, multi-environment adaptability, standardized technology stacks, and automated operation and maintenance can the dual goals of improving operational efficiency and ensuring security compliance be achieved, providing solid support for the system's digital transformation. Summary of the Invention

[0014] This invention provides a standardized product deployment and maintenance method, computer equipment, and computer-readable storage medium based on an offline environment to solve the technical problems existing in the prior art.

[0015] To achieve the above objectives, this invention provides a standardized product deployment and maintenance method based on an offline environment, comprising:

[0016] S1: Execute the one-click initialization process

[0017] Quickly build a visualization platform centered on Ansible Semaphore using "offline media + automated scripts" to achieve zero-barrier start-up;

[0018] S2: Execute the visual deployment process

[0019] The platform is built on a one-click initialization process and can be deployed in a visual way on the Ansible Semaphore web interface. It has built-in Ansible Playbooks for multiple scenarios.

[0020] S3: Execute visual operation and maintenance processes

[0021] Centered on a "modular script visualization platform," it covers monitoring and alarm scenarios, log query scenarios, component upgrade scenarios, and version rollback scenarios, with all operations based on offline pre-built resources.

[0022] S4: Execute the visual release process

[0023] A closed-loop system is adopted, which uses "offline media as the carrier, canary release as verification, and rolling updates as execution" to ensure uninterrupted business release in offline environments.

[0024] In one embodiment of the present invention, step S1 includes:

[0025] S11: In a network environment, prepare an image file, basic dependency packages, and configuration and script files. The image file contains the front-end, back-end, middleware, and dependency images. The basic dependency packages contain rpm / deb packages and core component installation packages. The configuration and script files contain cluster information and initialization scripts.

[0026] S12: Configure the main startup script, which can automatically load offline media resources;

[0027] S13: Execute the main startup script;

[0028] S14: Basic Environment Preparation: Automatically verify the server OS version, hardware resources, and port usage; set up a private offline repository for YUM / Docker; and install basic Docker and Containerd tools.

[0029] S15: Core Component Deployment: Automated deployment of Ansible, K3S cluster, KubePi visualization platform, MySQL database, and Ansible Semaphore via scripts;

[0030] S16: Platform Verification: Automatically verifies KubePi login and K3S cluster status. If verification fails, it outputs the log path and reason for failure for quick troubleshooting.

[0031] In one embodiment of the present invention, step S2 includes:

[0032] S21: Trigger entry point: User logs in to the platform → selects the service to be deployed → clicks "Execute Script";

[0033] S22: Environment check and preparation: Verify server resources, system compatibility, port status, automatically supplement missing dependencies, and configure system parameters;

[0034] S23: Component dependency installation: Install the dependencies required for compiling / running core components;

[0035] S24: Middleware and Service Deployment: Deploy databases, Redis, Nginx, and front-end and back-end services in parallel / serial within a K3S cluster;

[0036] S25: Service Startup and Verification: Unified management of service startup and shutdown, automatic verification of process and port availability, automatic retry if verification fails and output of troubleshooting guidance.

[0037] In one embodiment of the present invention, step S3 includes:

[0038] S31: Preparatory work: Prepare the new version image and data backup script in advance;

[0039] S32: Data Backup: Perform Redis data backup via Playbook;

[0040] S33: Image and Configuration Update: Load the new version image, modify the StatefulSet configuration, and set "upgrade from slave nodes first";

[0041] S34: Rolling upgrade: Stop each slave node Pod one by one → Start the new version → Verify the health status, and upgrade the master node after all slave nodes have been upgraded;

[0042] S35: Verification and Rollback: Verify the cluster status. If verification fails, restore the old version image, configuration, and backup data.

[0043] In one embodiment of the present invention, step S4 includes:

[0044] Backend deployment process:

[0045] S41: Offline Media Preparation: Includes new image, Deployment configuration, and application configuration;

[0046] S42: Resource loading: Import the image to the private repository and update the configuration;

[0047] S43: Rolling Update: Replace Pods in batches, and perform API health checks after each batch is completed;

[0048] S44: Rollback mechanism: If verification fails, the configuration and Deployment will be automatically rolled back, and the old version of the Pod will be rebuilt;

[0049] Front-end deployment process:

[0050] S45: Resource preparation: Includes new static files, ConfigMap configuration, and Ingress rules;

[0051] S46: Canary Deployment: Create new versions of instances while keeping the old versions coexisting, gradually switching traffic;

[0052] S47: Monitoring and Verification: Track page loading speed and API call success rate;

[0053] S48: Rollback mechanism: If an exception occurs, the configuration will be rolled back, the Ingress rules will be modified, and a full switch back to the old version will be performed.

[0054] In one embodiment of the present invention, step S134 requires that the hardware resources meet the requirements of CPU ≥ 4 cores and memory ≥ 8G.

[0055] In one embodiment of the present invention, in step S15, the K3S cluster includes master-slave node configuration and network plugins.

[0056] In one embodiment of the present invention, the method adopts a layered architecture design, which includes a resource layer, an execution layer, and a management and control layer. Each layer works together to achieve standardized deployment and operation and maintenance in an offline environment.

[0057] Resource layer: Includes offline media and offline dependency repository, providing offline resource support for the entire process. Offline media includes image files, basic dependency packages, and configuration and script files;

[0058] Execution layer: Responsible for basic environment preparation, offline repository construction, and core component deployment. It uses Ansible orchestration and K3S clusters to host containerized components and execute automated operations.

[0059] Management layer: Centered on Ansible Semaphore, it provides a visual operation interface, supports one-click triggering of deployment, operation and maintenance, and release processes, and realizes real-time monitoring and log traceability.

[0060] The present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.

[0061] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the above-described method.

[0062] The standardized product deployment and maintenance method, computer equipment, and computer-readable storage medium based on an offline environment provided by this invention have the following beneficial technical effects:

[0063] 1. Strong adaptability to special environments: It is completely independent of the public network and adapts to scenarios such as network isolation and domestic systems (such as Kylin OS), meeting the needs of industries involving classified information;

[0064] 2. Significantly improved operation and maintenance efficiency: Automated orchestration replaces manual operation, reducing deployment and maintenance time from several days / hours to minutes / hours, and non-professional operation and maintenance personnel can complete the operation by clicking on the interface;

[0065] 3. Controllable security and compliance risks: Built-in resource verification, log auditing, data backup, and one-click rollback mechanisms meet security requirements, with fault recovery time ≤ 5 minutes;

[0066] 4. High standardization and reusability: Unified technology stack and process specifications avoid the randomness of manual operation, modules can be reused, and long-term maintenance costs are reduced;

[0067] 5. Flexible scalability: Supports hybrid cloud deployment, automatic scaling up and down, adapts to business growth and traffic fluctuations, and has disaster recovery and emergency response capabilities. Attached Figure Description

[0068] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0069] Figure 1 To initialize the process architecture diagram, clearly illustrate the layered logic of the resource layer, execution layer, and control layer, as well as the personnel collaboration relationships;

[0070] Figure 2 To upgrade the process architecture diagram, present the entire process of offline media import, visual operation, and component upgrade;

[0071] Figure 3 A flowchart for the one-click initialization solution (clearly defining the execution order of each step, verification logic, and exception handling path);

[0072] Figure 4 To visualize the deployment solution flowchart, the steps related to environment checks, dependency installation, middleware deployment, and service verification are detailed.

[0073] Figure 5 To visualize the operation and maintenance solution flowchart, taking Redis as an example, we will show the complete logic of backup, upgrade, verification, and rollback;

[0074] Figure 6 To visualize the release process, distinguish between front-end and back-end release paths, and clarify traffic switching and rollback mechanisms. Detailed Implementation

[0075] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0076] The key technical points of this invention are as follows:

[0077] 1. Focusing on core needs in offline scenarios: Adapting to special scenarios such as network isolation, compliance auditing, and domestic substitution, eliminating reliance on the public network, and achieving full-process operation by relying on pre-built resources on the internal network;

[0078] 2. Layered and decoupled architecture design: The resource layer stores offline media packages and local repositories and performs verification; the execution layer uses Ansible orchestration and K3S to host containerized components; and the management and control layer uses Ansible Semaphore to achieve visualization, auditing, and rollback.

[0079] 3. Four efficient closed-loop processes: one-click initialization (platform setup in 30 minutes), visual deployment (complex deployment completed in 1 hour), visual operation and maintenance (modular upgrade and rollback), and visual release (seamless switching).

[0080] 4. Complete offline adaptation delivery: Includes offline resources, deployment tools, documentation, and service guarantees, achieving standardized deployment and maintenance with low barriers to entry.

[0081] Figure 1 To initialize the process architecture diagram, clearly show the layered logic of the resource layer, execution layer, and control layer, as well as the personnel collaboration relationships; Figure 2 To upgrade the process architecture diagram, present the entire process of offline media import, visual operation, and component upgrade; Figure 3 A flowchart for the one-click initialization solution (clearly defining the execution order of each step, verification logic, and exception handling path); Figure 4 To visualize the deployment solution flowchart, the steps related to environment checks, dependency installation, middleware deployment, and service verification are detailed. Figure 5 To visualize the operation and maintenance solution flowchart, taking Redis as an example, we will show the complete logic of backup, upgrade, verification, and rollback; Figure 6 To visualize the deployment process, distinguish between front-end and back-end deployment paths, and clarify traffic switching and rollback mechanisms. For example... Figures 1-6 As shown, to address the technical problems existing in the prior art and achieve standardized, secure, and convenient system construction and subsequent operation and maintenance from scratch, this invention provides a standardized product deployment and operation and maintenance method based on an offline environment, which includes:

[0082] S1: Execute the one-click initialization process

[0083] Quickly build a visualization platform centered on Ansible Semaphore using "offline media + automated scripts" to achieve zero-barrier start-up;

[0084] Step S1 adapts to brand-new servers without a foundational environment, solving the problems of error-prone and time-consuming manual configuration; non-professional operation and maintenance personnel only need to execute one startup script to complete the setup; providing a visual operation foundation for subsequent deployment and operation and maintenance.

[0085] S2: Execute the visual deployment process

[0086] The platform is built on a one-click initialization process and can be deployed in a visual way on the Ansible Semaphore web interface. It has built-in Ansible Playbooks for multiple scenarios.

[0087] In step S2, the Playbook and Role collaborate in a layered manner. The Playbook serves as the overall framework, while the Role atomically encapsulates the operation scripts to collaboratively complete the deployment.

[0088] S3: Execute visual operation and maintenance processes

[0089] Centered on a "modular script visualization platform," it covers monitoring and alarm scenarios, log query scenarios, component upgrade scenarios, and version rollback scenarios, with all operations based on offline pre-built resources.

[0090] In step S3, the operation and maintenance actions are broken down into Ansible Roles, and Ansible Semaphores are used to enable one-click triggering, log viewing, and version management.

[0091] S4: Execute the visual release process

[0092] A closed-loop system is adopted, which uses "offline media as the carrier, canary release as verification, and rolling updates as execution" to ensure uninterrupted business release in offline environments.

[0093] Step S4 follows the order of "upgrade the backend first, then switch the frontend," and combines the strategy of "rolling update (backend) + canary release (frontend)" to monitor the entire process and quickly roll back in case of anomalies.

[0094] In one embodiment of the present invention, step S1 includes:

[0095] S11: In a network environment, prepare an image file, basic dependency packages, and configuration and script files. The image file contains the front-end, back-end, middleware, and dependency images. The basic dependency packages contain rpm / deb packages and core component installation packages. The configuration and script files contain cluster information and initialization scripts.

[0096] S12: Configure the main startup script (e.g., . / init.sh), which can automatically load offline media resources;

[0097] S13: Execute the main startup script;

[0098] S14: Basic Environment Preparation: Automatically verify the server OS version, hardware resources, and port usage; set up a private offline repository for YUM / Docker; and install basic Docker and Containerd tools.

[0099] S15: Core Component Deployment: Automated deployment of Ansible, K3S cluster, KubePi visualization platform, MySQL database, and Ansible Semaphore via scripts;

[0100] S16: Platform Verification: Automatically verifies KubePi login and K3S cluster status. If verification fails, it outputs the log path and reason for failure for quick troubleshooting.

[0101] In one embodiment of the present invention, step S2 includes:

[0102] S21: Trigger entry point: User logs in to the platform → selects the service to be deployed → clicks "Execute Script";

[0103] S22: Environment check and preparation: Verify server resources, system compatibility, port status, automatically supplement missing dependencies, and configure system parameters;

[0104] S23: Component dependency installation: Install the dependencies required for compiling / running core components (such as Nginx's dependency pcre-devel);

[0105] S24: Middleware and Service Deployment: Deploy databases (MySQL / PgSQL, etc.), Redis, Nginx, and front-end and back-end services in parallel / serial within the K3S cluster;

[0106] S25: Service Startup and Verification: Unified management of service startup and shutdown, automatic verification of process and port availability, automatic retry if verification fails and output of troubleshooting guidance.

[0107] In a typical scenario (upgrading a containerized stateful service, taking Redis as an example), in one embodiment of the present invention, step S3 includes:

[0108] S31: Preparatory work: Prepare the new version image and data backup script in advance;

[0109] S32: Data Backup: Perform Redis data backup via Playbook (e.g., generate an RDB file using bgsave).

[0110] S33: Image and Configuration Update: Load the new version image, modify the StatefulSet configuration, and set "upgrade from slave nodes first";

[0111] S34: Rolling upgrade: Stop each slave node Pod one by one → Start the new version → Verify the health status, and upgrade the master node after all slave nodes have been upgraded;

[0112] S35: Verification and Rollback: Verify the cluster status. If verification fails, restore the old version image, configuration, and backup data.

[0113] The above steps demonstrate S3's strong offline adaptability, visualized and automated operation and maintenance, and built-in backup and rollback mechanisms, ensuring controllable risks.

[0114] In one embodiment of the present invention, step S4 includes:

[0115] Backend deployment process:

[0116] S41: Offline Media Preparation: Includes new image, Deployment configuration, and application configuration;

[0117] S42: Resource loading: Import the image to the private repository and update the configuration;

[0118] S43: Rolling Update: Replace Pods in batches (e.g., 20% / batch), and perform API health checks after each batch is completed;

[0119] S44: Rollback mechanism: If verification fails, the configuration and Deployment will be automatically rolled back, and the old version of the Pod will be rebuilt;

[0120] Front-end deployment process:

[0121] S45: Resource preparation: Includes new static files, ConfigMap configuration, and Ingress rules;

[0122] S46: Canary Deployment: Create new versions of instances and coexist with the old versions, gradually switching traffic (5%→20%→50%→100%).

[0123] S47: Monitoring and Verification: Track page loading speed and API call success rate;

[0124] S48: Rollback mechanism: If an exception occurs, the configuration will be rolled back, the Ingress rules will be modified, and a full switch back to the old version will be performed.

[0125] In one embodiment of the present invention, step S134 requires that the hardware resources meet the requirements of CPU ≥ 4 cores and memory ≥ 8G.

[0126] In one embodiment of the present invention, in step S15, the K3S cluster includes master-slave node configuration and network plugins.

[0127] In one embodiment of the present invention, the method adopts a layered architecture design, which includes a resource layer, an execution layer, and a management and control layer. Each layer works together to achieve standardized deployment and operation and maintenance in an offline environment.

[0128] Resource layer: Includes offline media and offline dependency repository, providing offline resource support for the entire process. Offline media includes image files, basic dependency packages, and configuration and script files;

[0129] Execution layer: Responsible for basic environment preparation, offline repository construction, and core component deployment. It uses Ansible orchestration and K3S clusters to host containerized components and execute automated operations.

[0130] Management layer: Centered on Ansible Semaphore, it provides a visual operation interface, supports one-click triggering of deployment, operation and maintenance, and release processes, and realizes real-time monitoring and log traceability.

[0131] The present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.

[0132] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the above-described method.

[0133] In this invention, the core visualization capabilities of Ansible Semaphore are introduced as follows:

[0134] As the central hub for end-to-end management and control, it achieves efficient operation and maintenance through modular design and visualized operation:

[0135] (1) Modular script: Playbook is divided into functions (such as initialization, upgrade, release), and the Role is atomically encapsulated into operation scripts, which has strong reusability.

[0136] (2) One-click automation: a single click can trigger the entire process from resource loading to service verification.

[0137] (3) Real-time monitoring: Graphical display of task status (not started / running / completed / failed), supporting parallel monitoring of multiple tasks.

[0138] (4) Log traceability: Completely records the operation process, supports retrieval by version and time, and quickly locates faults.

[0139] The standardized product deployment and maintenance method, computer equipment, and computer-readable storage medium based on an offline environment provided by this invention have the following beneficial technical effects:

[0140] 1. Strong adaptability to special environments: It is completely independent of the public network and adapts to scenarios such as network isolation and domestic systems (such as Kylin OS), meeting the needs of industries involving classified information;

[0141] 2. Significantly improved operation and maintenance efficiency: Automated orchestration replaces manual operation, reducing deployment and maintenance time from several days / hours to minutes / hours, and non-professional operation and maintenance personnel can complete the operation by clicking on the interface;

[0142] 3. Controllable security and compliance risks: Built-in resource verification, log auditing, data backup, and one-click rollback mechanisms meet security requirements, with fault recovery time ≤ 5 minutes;

[0143] 4. High standardization and reusability: Unified technology stack and process specifications avoid the randomness of manual operation, modules can be reused, and long-term maintenance costs are reduced;

[0144] 5. Flexible scalability: Supports hybrid cloud deployment, automatic scaling up and down, adapts to business growth and traffic fluctuations, and has disaster recovery and emergency response capabilities.

[0145] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of one embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing the present invention.

[0146] Those skilled in the art will understand that the modules in the apparatus of the embodiments can be distributed in the apparatus of the embodiments as described in the embodiments, or they can be located in one or more devices different from this embodiment with corresponding changes. The modules of the above embodiments can be combined into one module, or they can be further divided into multiple sub-modules.

[0147] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A standardized product deployment and maintenance method based on an offline environment, characterized in that, include: S1: Execute the one-click initialization process Quickly build a visualization platform centered on Ansible Semaphore using "offline media + automated scripts" to achieve zero-threshold startup; S2: Execute the visual deployment process The platform is built on a one-click initialization process and can be deployed in a visual way on the Ansible Semaphore web interface. It has built-in Ansible Playbooks for multiple scenarios. S3: Execute visual operation and maintenance processes Centered on a "modular script visualization platform," it covers monitoring and alarm scenarios, log query scenarios, component upgrade scenarios, and version rollback scenarios, with all operations based on offline pre-built resources. S4: Execute the visual release process A closed-loop system is adopted, which uses "offline media as carrier, canary release as verification, and rolling update as execution" to ensure uninterrupted business release in offline environments.

2. The standardized product deployment and maintenance method based on an offline environment according to claim 1, characterized in that, Step S1 includes: S11: In a network environment, prepare an image file, basic dependency packages, and configuration and script files. The image file contains the front-end, back-end, middleware, and dependency images. The basic dependency packages contain rpm / deb packages and core component installation packages. The configuration and script files contain cluster information and initialization scripts. S12: Configure the main startup script, which can automatically load offline media resources; S13: Execute the main startup script; S14: Basic Environment Preparation: Automatically verify the server OS version, hardware resources, and port usage; set up a private offline repository for YUM / Docker; and install basic Docker and Containerd tools. S15: Core Component Deployment: Automated deployment of Ansible, K3S cluster, KubePi visualization platform, MySQL database, and Ansible Semaphore via scripts; S16: Platform Verification: Automatically verifies KubePi login and K3S cluster status. If verification fails, it outputs the log path and reason for failure for quick troubleshooting.

3. The standardized product deployment and maintenance method based on an offline environment according to claim 1, characterized in that, Step S2 includes: S21: Trigger entry point: User logs in to the platform → selects the service to be deployed → clicks "Execute Script"; S22: Environment check and preparation: Verify server resources, system compatibility, port status, automatically supplement missing dependencies, and configure system parameters; S23: Component dependency installation: Install the dependencies required for compiling / running core components; S24: Middleware and Service Deployment: Deploy databases, Redis, Nginx, and front-end and back-end services in parallel / serial within a K3S cluster; S25: Service Startup and Verification: Unified management of service startup and shutdown, automatic verification of process and port availability, automatic retry if verification fails and output of troubleshooting guidance.

4. The standardized product deployment and maintenance method based on an offline environment according to claim 1, characterized in that, Step S3 includes: S31: Preparatory work: Prepare the new version image and data backup script in advance; S32: Data Backup: Perform Redis data backup via Playbook; S33: Image and Configuration Update: Load the new version image, modify the StatefulSet configuration, and set "upgrade from slave nodes first"; S34: Rolling upgrade: Stop each slave node Pod one by one → Start the new version → Verify the health status, and upgrade the master node after all slave nodes have been upgraded; S35: Verification and Rollback: Verify the cluster status. If verification fails, restore the old version image, configuration, and backup data.

5. The standardized product deployment and maintenance method based on an offline environment according to claim 1, characterized in that, Step S4 includes: Backend deployment process: S41: Offline Media Preparation: Includes new image, Deployment configuration, and application configuration; S42: Resource loading: Import the image to the private repository and update the configuration; S43: Rolling Update: Replace Pods in batches, and perform API health checks after each batch is completed; S44: Rollback mechanism: If verification fails, the configuration and Deployment will be automatically rolled back, and the old version of the Pod will be rebuilt; Front-end deployment process: S45: Resource preparation: Includes new static files, ConfigMap configuration, and Ingress rules; S46: Canary Deployment: Create new versions of instances while keeping the old versions coexisting, gradually switching traffic; S47: Monitoring and Verification: Track page loading speed and API call success rate; S48: Rollback mechanism: If an exception occurs, the configuration will be rolled back, the Ingress rules will be modified, and a full switch back to the old version will be performed.

6. The standardized product deployment and maintenance method based on an offline environment according to claim 2, characterized in that, In step S14, the hardware resources must meet the requirements of CPU ≥ 4 cores and memory ≥ 8G.

7. The standardized product deployment and maintenance method based on an offline environment according to claim 2, characterized in that, In step S15, the K3S cluster includes master-slave node configuration and network plugins.

8. The standardized product deployment and maintenance method based on an offline environment according to claim 1, characterized in that, This method employs a layered architecture design, comprising a resource layer, an execution layer, and a management and control layer. These layers collaborate to achieve standardized deployment and maintenance in offline environments. Resource layer: Includes offline media and offline dependency repository, providing offline resource support for the entire process. Offline media includes image files, basic dependency packages, and configuration and script files; Execution layer: Responsible for basic environment preparation, offline repository construction, and core component deployment. It uses Ansible orchestration and K3S clusters to host containerized components and execute automated operations. Management layer: Centered on Ansible Semaphore, it provides a visual operation interface, supports one-click triggering of deployment, operation and maintenance, and release processes, and realizes real-time monitoring and log traceability.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

Images