Private deployment method and device for collaborative document application and storage medium

Abstract

The invention provides a private deployment method and device for collaborative document applications and a storage medium. The private deployment method for the collaborative document application comprises the following steps: acquiring a deployment source file of the collaborative document application; acquiring deployment environment information when the collaborative document application is deployed in the target private cloud, and running the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to a plurality of services of the collaborative document application; determining a plurality of target configuration file templates based on the target system component, and generating a configuration file corresponding to the target system component according to the deployment environment information, the rule file and the target configuration file templates; storing the configuration file to a specified storage area; and when the collaborative document application is operated in the target private cloud, reading the configuration file, and providing a system function corresponding to the target system component. According to the method, the efficiency of privatization of the collaborative document application can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud computing technology, and particularly to a method, apparatus, and storage medium for private deployment of a collaborative document application. Background Art

[0002] A collaborative document application is a shared document application that enables collaborative editing and real-time collaboration among multiple users, supporting functions such as real-time editing, version control, commenting, and permission management. It is widely used in team cooperation, remote work, and decentralized team environments, and has advantages such as improving team cooperation efficiency, work efficiency, and reducing communication barriers.

[0003] The collaborative document application is specifically a cloud-native application. Cloud-native applications are a method of application development and deployment based on cloud computing principles and services, with characteristics such as containerization, microservices architecture, and service mesh. They make full use of the elasticity, scalability, and flexibility of the cloud computing environment to more effectively build, deploy, and manage applications.

[0004] When the collaborative document application is deployed in a public cloud system, an enterprise's data is hosted on the infrastructure of a third-party cloud provider, which makes the enterprise somewhat dependent on the cloud service provider to a certain extent. In addition, storing sensitive data in a public cloud system may cause security and privacy leakage problems. In order to be able to deploy the collaborative document application on an internal server or a private cloud environment, it is necessary to perform private deployment of the collaborative document application. However, in the related art, the process of privatizing the collaborative document application is very inefficient. Summary of the Invention

[0005] Embodiments of the present disclosure provide a method, apparatus, and storage medium for private deployment of a collaborative document application. This method can automatically deploy a cloud-native application base platform and execute the private deployment process of the collaborative document application, improving the efficiency of private deployment of the collaborative document application.

[0006] According to one aspect of the present disclosure, a method for private deployment of a collaborative document application is provided, including:

[0007] Obtain the deployment source file of the collaborative document application, where the deployment source file includes a deployment execution program file and a rule file. The deployment execution program file is used to generate system components of a cloud-native application, and the rule file is generated based on the configuration file when the collaborative document application is deployed in a public cloud and configuration file templates corresponding to multiple private cloud scenarios;

[0008] Obtain the deployment environment information when the collaborative document application is deployed in a target private cloud, and run the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application;

[0009] Determine multiple target configuration file templates from the configuration file templates corresponding to the multiple private cloud scenarios for the target system components, and generate a configuration file corresponding to each target system component based on the deployment environment information, the rule file, and the target configuration file templates;

[0010] Store each configuration file in the storage area specified by the corresponding target system component;

[0011] When running the collaborative document application in the target private cloud, read the configuration file from the corresponding storage area based on the target system component to provide the system functions corresponding to the target system component.

[0012] According to one aspect of the present disclosure, there is provided a privatization deployment device for a collaborative document application, including:

[0013] A first acquisition unit for acquiring the deployment source file of the collaborative document application, where the deployment source file includes a deployment execution program file and a rule file; wherein, the deployment execution program file is used to generate system components of a cloud-native application, and the rule file is generated based on the configuration file when the collaborative document application is deployed in a public cloud and the configuration file templates corresponding to multiple private cloud scenarios;

[0014] A second acquisition unit for acquiring the deployment environment information when the collaborative document application is deployed in the target private cloud, and running the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application;

[0015] A generation unit for determining multiple target configuration file templates from the configuration file templates corresponding to the multiple private cloud scenarios based on the deployment environment information, and generating a configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file templates;

[0016] A storage unit for storing each configuration file in the storage area specified by the corresponding target system component;

[0017] A reading unit for reading the configuration file from the corresponding storage area based on the target system component when running the collaborative document application in the target private cloud to provide the system functions corresponding to the target system component.

[0018] Optionally, in some embodiments, the second acquisition unit includes:

[0019] A deployment subunit, configured to run the deployment execution program file according to deployment environment information to deploy a cloud-native application base platform, where the cloud-native application base platform is used to provide generation suites required for the cloud-native application generation process;

[0020] A determination subunit, configured to determine multiple target services corresponding to the collaborative document application according to the deployment environment information and the rule file;

[0021] A generation subunit, configured to generate multiple target system components corresponding to the multiple target services based on the cloud-native application base platform.

[0022] Optionally, in some embodiments, the determination subunit includes:

[0023] A determination module, configured to determine the functional requirements corresponding to the collaborative document application according to the deployment environment information;

[0024] The determination subunit is further configured to:

[0025] Determine multiple target services from multiple service templates provided in the rule file based on the functional requirements.

[0026] Optionally, in some embodiments, the determination module includes:

[0027] A determination sub-module, configured to determine multiple functional services corresponding to the functional requirements;

[0028] An identification sub-module, configured to identify the dependency relationships between the multiple functional services and the basic services;

[0029] The determination module is further configured to:

[0030] Determine multiple target services from multiple service templates provided in the rule file according to the dependency relationships.

[0031] Optionally, in some embodiments, the private deployment device for the collaborative document application further includes a rule file generation unit, and the rule file generation unit further includes:

[0032] A first acquisition sub-unit, configured to acquire a public cloud configuration file corresponding to each service when the collaborative document application is deployed in a public cloud, where the public cloud configuration file includes an unmodifiable first sub-configuration file and a modifiable second sub-configuration file;

[0033] An update sub-unit, configured to perform a generalization update on the second sub-configuration file in the public cloud configuration file to obtain a general configuration file of the collaborative document;

[0034] The first generation subunit is used to obtain configuration file templates under multiple private cloud scenarios and generate rule files based on the configuration file templates and the general configuration file generation rules.

[0035] Optionally, in some embodiments, the update subunit includes:

[0036] An identification module for identifying modifiable content in the second configuration file;

[0037] A generation module for replacing the modifiable content with a preset marker and determining a general configuration file based on the second sub-configuration file after content replacement and the first sub-configuration file.

[0038] Optionally, in some embodiments, the generation unit includes:

[0039] An acquisition module for acquiring communication endpoint information of the support system;

[0040] A replacement module for replacing the preset marker in the general configuration file based on the communication endpoint information and the deployment environment information to obtain a privatized configuration file;

[0041] A generation sub-module for generating a configuration file corresponding to each target system component according to the privatized configuration file and the target configuration file template.

[0042] Optionally, in some embodiments, the privatized deployment device of the collaborative document application further includes a deployment execution program file generation unit, and the deployment execution program file generation unit further includes:

[0043] An orchestration subunit for orchestrating the privatized deployment process of the collaborative document application;

[0044] A second acquisition subunit for acquiring execution files and support files required in the privatized deployment process;

[0045] A second generation subunit for generating a deployment execution program file based on the privatized deployment process, the execution files, and the support files.

[0046] Optionally, in some embodiments, the storage unit includes:

[0047] A second determination subunit for determining a storage area corresponding to each target system component based on the cloud-native application base platform;

[0048] The storage unit is further used for:

[0049] Storing the configuration file corresponding to each target system component in the corresponding storage area.

[0050] According to one aspect of the present disclosure, a computer device is provided, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the privatized deployment method of the collaborative document application as described above is implemented.

[0051] According to one aspect of the present disclosure, a storage medium is provided. The storage medium stores a computer program, and when the computer program is executed by a processor, the privatized deployment method of the collaborative document application as described above is implemented.

[0052] According to one aspect of the present disclosure, a computer program product is provided. The computer program product includes a computer program, and the computer program is read and executed by a processor of a computer device, so that the computer device executes the privatized deployment method of the collaborative document application as described above.

[0053] The privatized deployment method of the collaborative document application provided by the embodiments of the present disclosure includes: obtaining a deployment source file of the collaborative document application, where the deployment source file includes a deployment execution program file for generating system components of a cloud-native application, and the rule file is generated based on a configuration file when the collaborative document application is deployed in a public cloud and configuration file templates corresponding to multiple private cloud scenarios; obtaining deployment environment information when the collaborative document application is deployed in a target private cloud, and running the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application; determining multiple target configuration file templates from the configuration file templates corresponding to multiple private cloud scenarios based on the target system components, and generating a configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file templates; storing each configuration file in a storage area specified by the corresponding target system component; when the collaborative document application is running in the target private cloud, reading the configuration file from the corresponding storage area based on the target system component to provide system functions corresponding to the target system component.

[0054] In this way, by obtaining the deployment execution program file, the rule file, and the deployment environment information of the target private cloud of the collaborative document application, then automatically building a cloud-native application base platform according to the deployment execution program file, and then automatically generating system components and configuration files corresponding to multiple services of the collaborative document application in the target private cloud scenario in the cloud-native application base platform according to the deployment environment information, the deployment execution program file, and the rule file, and associating the generated system components and configuration files, the automated deployment of the collaborative document application in the target private cloud is realized. In this way, the efficiency of the privatized deployment of the collaborative document application can be improved.

[0055] Other features and advantages of the present disclosure will be set forth in the following description, and in part will be obvious from the description, or may be learned by practice of the present disclosure. The objectives and other advantages of the present disclosure may be realized and attained by the structure particularly pointed out in the specification, the claims as well as the drawings. Description of the Drawings

[0056] The drawings are used to provide a further understanding of the technical solutions of the present disclosure, and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solutions of the present disclosure, and do not constitute a limitation to the technical solutions of the present disclosure.

[0057] Figure 1 It is a system architecture diagram of the private deployment method of the collaborative document application according to an embodiment of the present disclosure;

[0058] Figure 2 It is a schematic flowchart of the private deployment method of the collaborative document application according to an embodiment of the present disclosure;

[0059] Figure 3 It is a schematic diagram of the operation logic of the collaborative document service in the present disclosure;

[0060] Figure 4 It is a schematic flowchart of the private deployment process of the collaborative document application according to another embodiment of the present disclosure;

[0061] Figure 5 It is a schematic flowchart of a process in the deployment preparation stage of the private deployment method of the collaborative document application provided by the present disclosure;

[0062] Figure 6 It is a schematic flowchart of a process in the deployment implementation stage of the private deployment method of the collaborative document application provided by the present disclosure;

[0063] Figure 7 It is a schematic structural diagram of the private deployment device of the collaborative document application provided by the embodiments of the present disclosure;

[0064] Figure 8 It is a terminal structure diagram of the methods according to an embodiment of the present disclosure;

[0065] Figure 9 It is a server structure diagram of the methods according to an embodiment of the present disclosure. Detailed Embodiments

[0066] In order to make the objectives, technical solutions and advantages of the present disclosure clearer and more understandable, the present disclosure will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure, and are not used to limit the present disclosure.

[0067] Before further elaborating on the embodiments of the present disclosure, the nouns and terms involved in the embodiments of the present disclosure are described. The nouns and terms involved in the embodiments of the present disclosure are applicable to the following explanations:

[0068] Cloud Native: Cloud Native is a general term for a class of technologies. Through Cloud Native technologies, more easily elastic scalable applications can be built. It generally includes containers, service meshes, microservices architecture, immutable infrastructure, and declarative APIs. The goal of Cloud Native is to leverage the advantages of cloud computing to make applications more flexible, reliable, and maintainable, thus better meeting the rapidly changing business needs; Cloud Native applications are designed to fully utilize the cloud computing model.

[0069] The application programs built through Cloud Native technologies are called Cloud Native applications. The coupling of the underlying infrastructure is relatively loose, so they are easy to migrate. They can fully utilize the capabilities provided by the cloud. Therefore, the development, deployment, and management of Cloud Native applications are more efficient and convenient compared to traditional application programs. These applications can be run in different environments, such as private clouds, public clouds, hybrid clouds, and multi-cloud scenarios.

[0070] Public Cloud: A public cloud is a cloud computing service model. A third-party cloud service provider directly provides computing resources, storage, and other services to external users through its own infrastructure. External users access and use the services through the Internet and do not own the cloud computing resources. Public cloud services provide computing resources to multiple users through a common infrastructure, and users do not need to own or maintain their own physical hardware and devices. The public cloud provides a way to obtain computing resources on demand, elastically, and in a shared manner.

[0071] Private Cloud: A private cloud is a cloud computing service model. The infrastructure of a private cloud service is dedicated to a single organization, and application programs are deployed in the internal servers or private cloud environment of an enterprise or organization. Different from the public cloud, the resources of a private cloud are not publicly available but are deployed and maintained within the organization.

[0072] Cloud Native Application Components: A component is a modular unit that can be independently designed, implemented, tested, and deployed. A component can be a library, a module, an object, or a service. Cloud Native components include containers, orchestration systems (such as Kubernetes, abbreviated as K8s, which is responsible for scheduling and managing the lifecycle of containers), microservices (Cloud Native applications usually adopt a microservices architecture, splitting the application into small, independent services, and each microservice is responsible for a specific business function and can be independently developed, deployed, and scaled), service meshes (the infrastructure layer for managing communication between microservices, making the communication between microservices more reliable and efficient), and a series of elements based on Cloud Native computing and microservices architecture required to build application programs on the Cloud Native base platform.

[0073] Cloud Native Container: A cloud native container is a lightweight and portable computing unit used for packaging, deploying, and running applications. Containers can package and isolate applications and all their dependencies, allowing applications to run in the same way across different environments, supporting the construction and deployment of scalable and elastic applications across multiple environments. Each container typically runs a small, independent service.

[0074] A container itself is a more lightweight resource isolation unit than a virtual machine. A virtual machine exclusively uses a specific operating system, while a container is built on top of an operating system, and multiple containers can share the operating system. This is the biggest difference between containers and virtual machines. A container itself is part of the Infrastructure-as-a-Service (IaaS) layer, so it is necessary to combine with K8s for container resource scheduling and orchestration to provide the service capabilities of the Platform-as-a-Service (PaaS) layer to the upper layer. When talking about containers together with container orchestration and scheduling, it becomes a PaaS concept. PaaS is a PaaS container scheduling platform formed based on k8s and Docker (container engine). A container itself shares the underlying operating system and can better isolate resources such as CPU, memory, and network.

[0075] Mounting: Usually, mounting refers to a process by which an operating system makes a storage device, such as a hard disk, a Compact Disc-Read Only Memory (CD-ROM), or computer files and directories on a shared resource, accessible to users through the computer's file system.

[0076] In a cloud native environment, mounting refers to attaching (mount) storage resources to a container so that the application can access the storage resources. It is a method of separating persistent data (such as configuration files, database files, logs, etc.) from the container for easier data management, backup, and persistence.

[0077] Cloud Native Application Base Platform: The cloud native application base platform refers to a platform that provides cloud native computing infrastructure, tools, and services, building containerized and serverless infrastructure for users, supporting cloud native applications and microservices architectures. In the cloud native application base platform, cloud native applications can be built, deployed, managed, and extended, and cloud native applications can be built with higher efficiency and lower risk.

[0078] Pod: A Pod is the basic scheduling and management unit in Kubernetes. It is the smallest deployment unit of containers, supporting multiple containers in a Pod to share the network and file system, and can complete services through the simple and efficient way of inter - process communication and file sharing. In a cloud - native environment, a Pod contains one or more closely related containers, and these containers share the same network and storage resources. The Pod is scheduled and managed by Kubernetes, enabling the containers in the entire Pod to be deployed and migrated together.

[0079] ConfigMap: A ConfigMap is a resource object in Kubernetes used to store and manage non - sensitive configuration information, such as application configuration files, command - line parameters, etc. The ConfigMap allows configuration data to be separated from the application, enabling the application to more flexibly adapt to different environments; decoupling the configuration information from the container image, increasing the portability and flexibility of the application.

[0080] A ConfigMap is an API object used to store plain - text (non - confidential) data in key - value pairs and can be applied to a Pod in the form of environment variables, command - line parameters, or storage volumes (Volumes). The ConfigMap is equivalent to the configuration file of the program in the Pod, and the program's configuration can be modified by changing the content of the ConfigMap. After a Pod in k8s is started, it is mapped to a specified directory inside the container in the form of a Volume. The application in the container reads the configuration file in the specific directory of the container in the original way; in the view of the container, the configuration file seems to be packaged in a specific directory inside the container, and the whole process has no intrusion on the application.

[0081] In related technologies, it depends on implementers to operate according to the process of deploying a collaborative document application in a public cloud, deploying and configuring the supporting software and hardware dependencies required by the application in advance. After the dependencies are ready, the corresponding configuration files are adjusted, and finally the collaborative document service is deployed. However, the collaborative document system involves a large amount of data processing and analysis, with significant differences in software and hardware environments, requiring a large number of manual operations during the deployment process, resulting in a long deployment cycle. It is easy to make mistakes or lose configurations during the deployment process, ultimately causing the problem of low efficiency in the private deployment of the collaborative document application. To solve the problem of low efficiency in the private deployment of the collaborative document application in related technologies, the present disclosure provides a method for the private deployment of a collaborative document application, hoping to improve the efficiency of the private deployment of the collaborative document application to a certain extent.

[0082] System Architecture and Scenario Description of the Embodiments of the Present Disclosure

[0083] Figure 1It is a system architecture diagram applied to the privatized deployment method of a collaborative document application according to an embodiment of the present disclosure. It includes a terminal 140, the Internet 130, a gateway 120, a server 110, etc.

[0084] The terminal 140 includes various forms such as a desktop computer, a laptop computer, a PDA (Personal Digital Assistant), a mobile phone, a vehicle-mounted terminal, a home theater terminal, a dedicated terminal, etc. Additionally, it can be a single device or a collection of multiple devices. The terminal 140 can communicate with the Internet 130 in a wired or wireless manner to exchange data.

[0085] The server 110 refers to a computer system that can provide certain services to the terminal 140. Compared with an ordinary terminal 140, the server 110 has higher requirements in terms of stability, security, performance, etc. The server 110 can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a part (such as a virtual machine) allocated from a high-performance computer, a combination of parts (such as virtual machines) allocated from multiple high-performance computers, etc.

[0086] The gateway 120 is also called an internetwork connector and a protocol converter. The gateway realizes network interconnection at the transport layer and is a computer system or device that acts as a conversion function. Between two systems using different communication protocols, data formats, or languages, and even with completely different architectures, the gateway is a translator. At the same time, the gateway can also provide filtering and security functions. The message sent by the terminal 140 to the server 110 needs to be sent to the corresponding server 110 through the gateway 120. The message sent by the server 110 to the terminal 140 also needs to be sent to the corresponding terminal 140 through the gateway 120.

[0087] The privatized deployment method of the collaborative document application according to the embodiment of the present disclosure can be executed in the server 110. Specifically, the server 110 can be a private server corresponding to a private cloud and is the deployment machine in the privatized deployment process. After deploying the collaborative document application in the private server of an enterprise or organization, the privatized collaborative document application provides functional services of the privatized collaborative document application to the internal terminals (specifically, the aforementioned terminal 140) of the enterprise or organization through the gateway 120 and the Internet 130.

[0088] When the private deployment method of the collaborative document application is executed in the server 110 of an enterprise or organization, the server 110 can obtain the deployment source file of the collaborative document application. The deployment source file includes a deployment execution program file and a rule file. The deployment execution program file is used to generate system components of the cloud-native application, and the rule file is generated based on the configuration file when the collaborative document application is deployed in the public cloud and the configuration file templates corresponding to multiple private cloud scenarios. Then, obtain the deployment environment information when the collaborative document application is deployed in the private cloud environment of the enterprise or organization, and save the deployment environment information on the server 110. Based on the deployment environment information and the rule file, the server 110 runs the deployment execution program file to generate target system components corresponding to multiple services of the collaborative document application. The server 110 determines multiple target configuration file templates according to the configuration file templates corresponding to multiple private cloud scenarios for the target system components, and generates a configuration file corresponding to each target system component according to the rule file and the target configuration template; stores each configuration file in the storage area specified by the target system component. After the server 110 completes the private deployment of the collaborative document application, when the internal terminal 140 of the enterprise or organization needs to obtain the function service corresponding to the collaborative document application, the server 110 reads the configuration file from the storage area corresponding to the target system component, and then the server 110 communicates with the internal terminal of the enterprise or organization through the gateway 120 and the Internet 130, and provides the system function corresponding to the target system component to the internal terminal of the enterprise or organization, finally realizing the private deployment of the collaborative document application.

[0089] The embodiments of the present disclosure can be applied to a variety of private cloud scenarios, such as deploying a collaborative document application in the private cloud environment of a government agency, deploying a collaborative document application in the private cloud environment of a financial institution, and deploying a collaborative document application in the private cloud scenario of a medical institution, etc.

[0090] (1) Scenario of deploying a collaborative document application in the private cloud environment of a government agency

[0091] Government agencies usually handle a large number of sensitive confidential documents, including personal identity information, health records, financial information, etc., and these data can be stored in collaborative documents for convenient real-time editing and viewing. To ensure the privacy and security of these data, government agencies tend to deploy collaborative document applications in internal servers or private cloud environments to better control the cloud infrastructure within the agency and implement more strict and secure management measures. Through the private deployment of collaborative documents, more strict confidentiality work can be carried out on the data, ensuring that the internal data of government agencies is not accessed without authorization, and meeting the strict requirements of regulations for data privacy.

[0092] (2) Scenario of deploying a collaborative document application in the private cloud environment of a financial institution

[0093] Financial institutions need to process a large amount of sensitive customer financial data, including personal identity information, financial transaction records, investment and savings management information, and risk management of insurance products. All these data can be stored in collaborative documents for convenient financial information management. Therefore, financial institutions usually require more stringent data security protection measures and need to obtain the characteristic functions of collaborative documents, such as management panels, etc., to improve the efficiency of financial services. Thus, there are special deployment requirements. Deploying the collaborative document application in the private cloud environment of financial institutions can provide better data privacy and security management. And for some special business requirements of financial institutions, specific functional services may be needed. Private deployment provides a more flexible solution and can plan various resources according to business needs.

[0094] (III) Scenarios of deploying the collaborative document application in the private cloud scenario of medical institutions

[0095] Medical institutions are subject to strict regulations and compliance requirements. These regulations require the secure storage and processing of patient data and ensure that only authorized personnel can access sensitive information. For example, a patient's medical information is recorded through collaborative documents, and only the attending physician and the patient's family members with viewing permissions can view the relevant information. Unauthorized persons cannot access the patient's medical information at will; in addition, medical institutions conduct genomics research and a large number of clinical trials, which require large-scale data analysis. Therefore, medical institutions may need to obtain characteristic functions of collaborative documents such as fast large document loading. Multiple experimental results and data analysis results can be saved through collaborative documents for easy statistics and research by the editing team. Especially for some research data that needs to be kept confidential, it is necessary to ensure that the internal data of medical institutions is not accessed without authorization, meeting the strict requirements of regulations for data privacy. Therefore, it is necessary to deploy the collaborative document application in the private cloud environment within medical institutions.

[0096] General description of the embodiments of the present disclosure

[0097] According to an embodiment of the present disclosure, a method for private deployment of a collaborative document application is provided. This method can be used to deploy the collaborative document application in the private clouds of the above-mentioned government agencies, financial institutions, and medical institutions, and can also be applied to scenarios of deploying the collaborative document application in other private clouds.

[0098] As Figure 2 shown, it is a schematic flowchart of a method for private deployment of a collaborative document application provided by the present disclosure. This method can be applied to a device for private deployment of a collaborative document application, and this device for private deployment of a collaborative document application can be integrated in a computer device, and the computer device can be a terminal or a server. The method for private deployment of a collaborative document application can include:

[0099] Step 210, obtain the deployment source file of the collaborative document application.

[0100] As Figure 3 shown, it is a schematic diagram of the operation logic of the collaborative document service. Specifically, the collaborative document application in the public cloud system consists of hundreds of collaborative document containers of different categories. Each collaborative document container has a corresponding collaborative document service. The collaborative document service obtains the communication endpoint information of other support systems through configuration, and the communication endpoint information of the support system is saved in the configuration file corresponding to the service. The collaborative document container contains the Linux Process 1, usually referring to the init process, which is the first process after the system starts and is automatically created during the system boot process. When running the collaborative document application in the cloud environment, the collaborative document container starts Process 1, and Process 1 starts the business process, that is, starts the collaborative document service process. The collaborative document service reads the configuration from the specified storage area of the configuration and supports the interaction between components corresponding to different services. The interaction between cloud-native components corresponding to different collaborative document services means that in a cloud-native application, each component calls each other through open interfaces and standardized protocols and runs in a containerized environment. In a cloud-native architecture, the collaborative document application usually consists of multiple microservices, each service is responsible for different functions, and the system functions corresponding to the services can be realized only through the interaction between components. The collaborative document service provides corresponding collaborative document functions with the support of the support system by obtaining the communication endpoint information of the support system stored in the configuration file, the database used by the service, the message queue used by the service, the service registration component, and the communication endpoints of other PaaS services, thus completing the deployment process of the collaborative document application in the cloud environment.

[0101] In the related art, privatization deployment and configuration are carried out without changing the basic design and structure of the collaborative document application. This method requires pre-configuring and deploying all possible software and hardware facilities, such as databases, caches, etc. On this basis, the collaborative document application is deployed, which consumes a large amount of resources and has a long deployment cycle. Implementers need to perform a large number of manual operations for deployment, manual testing, and adjusting configuration files. The configuration cannot be automatically adapted to the functional requirements, resulting in low efficiency of the privatization deployment of the collaborative document application.

[0102] To solve the problems existing in the related art, the present disclosure provides a method for privatization deployment of a collaborative document application. This method realizes flexible configuration in the deployment environment through multiple configuration file templates in the rule file, and an execution program for generating a large number of system components is written in advance. The entire deployment process is executed by an automated tool, avoiding reliance on a large number of manual operations, thereby improving the efficiency of the privatization of the collaborative document application.

[0103] Specifically, the collaborative document application is a cloud-native application. In the embodiments of the present disclosure, the deployment source file for the privatized deployment of the collaborative document application can be obtained first. The deployment source file is used for the privatized deployment of the collaborative document application in a private server. The method for obtaining the deployment source file can be that the implementer manually writes it on the server, or downloads the pre-written program from the web page, or uses a solid-state storage hard drive to copy and import it into the private server corresponding to the private cloud. No restrictions are imposed on the obtaining method here. The deployment source file specifically includes a deployment execution program file, which not only includes the generated files of the components corresponding to multiple services when the collaborative document application is deployed in the public cloud, but also includes the generated files of the components corresponding to multiple private cloud scenario services. For example, there are a total of one thousand generated files of the components corresponding to multiple services when the collaborative document application is deployed in the public cloud and the generated files of the components corresponding to multiple private cloud scenario services in the deployment execution program file. The deployment environment information of the target private cloud is obtained to determine the target generated files of twenty target components, and the twenty corresponding target components are generated according to these twenty target generated files.

[0104] The execution programs corresponding to the system components required for building the cloud-native application base platform and generating the services of the cloud-native application are pre-written in the deployment execution program file. The system components required for the cloud-native application mainly include containers, microservice architecture, and service mesh. Among them, the container is the core component of the cloud-native application, which can package the application program together with the deployment resources on which the application program depends for deployment and cross-environment transplantation in the cloud environment. The collaborative document application in the public cloud is composed of many different types of collaborative document containers, and there is a corresponding collaborative document service in each collaborative document container; the microservice architecture in cloud-native can split the collaborative document application, separating different functional business modules into multiple tiny independently deployable services. Each microservice has an independent code library, development process, running environment, and data storage, and can be independently extended, deployed, maintained, and replaced; the service mesh is also an important component of the cloud-native application, which can be used to coordinate the communication and data flow between multiple services in the collaborative document application. Through the deployment execution program file of this embodiment, the cloud-native application base platform can be built, providing the environment for container operation and the underlying infrastructure to support the operation of the cloud-native application; the cloud-native system components corresponding to each service of the collaborative document application can be generated according to user requirements in the private cloud environment, thus supporting the construction and deployment of the cloud-native application.

[0105] The rule file includes a public cloud collaboration document configuration file and multiple private cloud collaboration document configuration file templates. The configuration file for the collaboration document when deployed in the public cloud can be the configuration file for the basic services and the necessary services applied to the collaboration document, which is used to ensure that users in the target private cloud can obtain the most basic functional services in the collaboration document application; the configuration file templates corresponding to multiple private cloud scenarios included in the rule file can determine the required personalized services according to the deployment environment of different private clouds and the deployment requirements of users, and generate the configuration file corresponding to each personalized service. The rule file has flexible configuration and supports dynamic transformation in different private cloud deployment environments, and can adapt to the following situations: for different user scales, the number of required services, and resource configurations, these configuration files can be used as templates in the rule file, and the corresponding number of services, service processors, and service memory can be set according to the on-site user scale during deployment, so that a single deployment package supports multiple user scales; for different user environments, the required servers are inconsistent, and there are differences in CPU architectures and operating systems. The rule file can perform targeted configuration for this, support CPU architectures such as x86, Advanced Reduced Instruction Set Computing Machine (ARM), Microprocessror without Interlocked PipelineStages (MIPS), Scalable Processor Architecture (SPARC), etc., and be compatible with multiple operating systems such as linux, Unified Operating System (UOS), and Kylin operating system, so that a single deployment package supports different CPU architectures and different types of operating systems; for different users' network architectures and network resources, differential configuration can also be performed in the rule file. Different network architectures include physical architectures and logical architectures. Some users' networks distinguish between internal and external networks and need to set different access policies, which can be prefabricated and logically set in the rule file. Some users do not have domain name resources, and all these scenarios can be automatically adapted according to the rule file; the rule file also supports adjusting the core business function switches. There are some important features in the collaboration document application, such as functions like fast loading of hot documents / large documents, gateway filtering, and management panels. These functions can be deployed according to actual deployment requirements.

[0106] In some embodiments of the present disclosure, the generation process of the rule file includes the following steps:

[0107] Obtain the public cloud configuration file corresponding to each service when the collaborative document application is deployed on the public cloud. The public cloud configuration file includes an unmodifiable first sub-configuration file and a modifiable second sub-configuration file;

[0108] Perform a generalization update on the second sub-configuration file in the public cloud configuration file to obtain the general configuration file of the collaborative document;

[0109] Obtain configuration file templates under multiple private cloud scenarios, and generate rule files based on the configuration file templates and the general configuration file.

[0110] In an embodiment of the present disclosure, the public cloud configuration file corresponding to each service when the collaborative document application is deployed on the public cloud system is divided into an unmodifiable first sub-configuration file and a modifiable second sub-configuration file. The public cloud configuration file is the configuration file corresponding to the basic services required for deploying the collaborative document application in the cloud environment, which can ensure obtaining the basic services of the collaborative document application in the private cloud environment and ensure the basic running state of the system. The unmodifiable first sub-configuration file is the fixed configuration parameters in the collaborative document application that do not need to change with the deployment environment, and are relatively stable parameters during the deployment and operation of the collaborative document application, including some authentication keys and credentials, basic system settings, environment variables, etc. The modifiable second sub-configuration file contains configuration parameters that need to be adjusted according to the deployment requirements and specific private cloud scenarios, such as the port number corresponding to the service, database connection information, log level, etc., and can be flexibly adjusted according to multiple private cloud scenarios. In the related art, all configurations are deployed together according to the deployment environment information, and the fixed configuration file and the updatable configuration file are mixed together, making the configuration management and subsequent upgrade and maintenance of the system difficult; in addition, the undivided configuration file lacks flexibility and cannot be flexibly changed according to the change of the deployment environment. If the configuration file containing sensitive information and security settings is mixed with other configuration files, it will increase the risk of leakage and tampering of sensitive information, resulting in a reduction in the security of the system. The rule file provided in this embodiment includes the public cloud configuration file corresponding to each service when deployed on the public cloud, and divides the public cloud configuration file into an unmodifiable first sub-configuration file and a modifiable second sub-configuration file, achieving the technical effect of separating the configuration parameters corresponding to the basic services of the collaborative document, ensuring the basic running state of the system and ensuring the flexibility of the system to be adjusted, facilitating configuration management and system maintenance, and avoiding the leakage of sensitive information.

[0111] In another embodiment of the present disclosure, the aforementioned modifiable second sub-profile is generalized and updated to obtain a general profile of the collaborative document. The general profile can uniformly manage and maintain the configuration parameters corresponding to the basic services in the collaborative document application. When there are special deployment requirements or specific environmental information in a certain private cloud scenario and it is necessary to update the configuration parameters of a certain basic service, only by changing the general profile can the configuration of multiple applications or environments be updated, improving the flexibility and maintainability of the configuration. Therefore, the general profile can support the deployment and testing of the collaborative document application in different private cloud scenarios, simplify the deployment process, and improve the deployment efficiency. After generating the general profile of the collaborative document, import the configuration file templates in multiple private cloud scenarios. The general profile and the configuration file templates in multiple private cloud scenarios together constitute the rule files required for deploying the collaborative document application in the private cloud. Generalizing and updating the modifiable second sub-profile requires determining the content to be replaced according to the specific deployment environment information, updating the configuration parameters in the second sub-profile according to certain replacement rules, and then obtaining the general profile corresponding to the basic service of the collaborative document application based on the non-modifiable first sub-profile and the second sub-profile after replacement and update. For this purpose, in the embodiments of the present disclosure, a method for generalizing and updating the non-modifiable second sub-profile is provided.

[0112] In some embodiments, the process of generalizing and updating the second sub-profile in the public cloud configuration file includes the following steps:

[0113] Identify the modifiable content in the second sub-profile;

[0114] Replace the modifiable content with a preset marker, and determine the general profile based on the second sub-profile after content replacement and the first sub-profile.

[0115] In one embodiment of the present disclosure, the modifiable content in the second sub-profile is the configuration parameters corresponding to each collaborative document service that can be dynamically modified according to the deployment environment information when deploying a collaborative document application in a public cloud system. The modifiable content can include various configuration parameters. For example, network information is a necessary configuration for deploying and running a collaborative document application and is also a necessary parameter for providing the functional service of the collaborative document to internal terminals in a private cloud. It can support configurations in different environments through replaceable Internet Protocol (IP) addresses, server ports, domain name resources, etc. The modifiable content also includes database connection information. A collaborative document application usually needs to connect to a database for data reading and writing, and can be configured between different environments through replaceable database connection strings, usernames, and passwords. The modifiable content can also include: communication endpoint information between different services. A certain service in a collaborative document application usually depends on other services to complete specific tasks, or the personalized services required when the collaborative document application is deployed in a private cloud environment may require the support of some basic services of the collaborative document application to complete the functions provided by the personalized services. Therefore, the multiple target services in the collaborative document application in different private cloud environments can be configured through the replaceable communication endpoint information between services, such as Uniform Resource Locator (URL) and Application Programming Interface (API) keys. In addition, the replaceable content in the second sub-profile should also include: system environment variables and file path information. Because a collaborative document application needs to access specific environment variables of the operating system, such as server addresses, ports, directories, etc., and the collaborative document accesses the corresponding configuration files through different paths, which also needs to be updated accordingly in different private cloud deployment environments.

[0116] In another embodiment of the present disclosure, to replace the modifiable content identified in the second sub-profile, first, the modifiable content needs to be marked, and the modifiable content is replaced with a preset identifier to obtain a second sub-profile containing the preset identifier. The second sub-profile after content replacement and the first sub-profile are combined to obtain a general configuration file. When deploying the configuration file, the content that can be replaced can be identified according to the preset identifier, and then the content identified by the identifier is replaced according to the private cloud environment information.

[0117] The preset identifier can be some specific tags. Some specific tags can be defined in the second sub - configuration file to mark the content that needs to be replaced. For example, in the configuration file, the ${xxx} tag is used, and the variable name is placed inside the parentheses to mark the content that can be replaced; preset placeholders such as {}, <> are used. In {}, <> corresponding configuration parameters and variable names can be filled according to the actual deployment requirements, such as environment variables, IP addresses, ports, etc., and the content is replaced according to the placeholders; or comments can be used to mark the content that needs to be modified in the comments, and the replaceable content is identified through the comments.

[0118] Through the method provided by the embodiments of the present disclosure, the second sub - configuration file in the public cloud configuration file is generally updated to obtain the general configuration file of the collaboration document in the foregoing steps. After obtaining the general configuration file of the collaboration document, continue to obtain configuration file templates under multiple private cloud scenarios. There are many ways to obtain configuration file templates under multiple private cloud scenarios. For example, download from the template library provided by the private cloud platform. Many private clouds will provide configuration file templates for internal use. When deploying the collaboration document application, according to the deployment requirements and deployment environment information, the configuration file template that meets the requirements can be found in the template library, and the selected configuration file template is downloaded and modified according to the actual requirements. Configuration file templates under multiple private cloud scenarios can also be obtained from open - source code repositories. Many open - source applications provide configuration file templates, which can be obtained from open - source code libraries, such as code hosting platforms like the Web - based Git code hosting service platform Github. Search for the configuration file template that suits your needs in it and obtain it by downloading the ZIP file package. Configuration file templates under multiple private cloud scenarios can also be downloaded from official websites or official documents. In official websites or official documents, some manufacturers or application providers provide downloadable configuration file templates, and the required templates can be obtained by accessing the official website or querying the official document. Here, there is no restriction on the way to obtain the configuration file template. After obtaining the configuration file templates under multiple private cloud scenarios, they are packaged and integrated with the general configuration file of the foregoing collaboration document to finally obtain the rule file.

[0119] In some embodiments of the present disclosure, the process of obtaining the deployment execution program file includes the following steps:

[0120] Orchestrate the privatization deployment process of the collaboration document application;

[0121] Obtain the execution files and support files required in the privatization deployment process;

[0122] Generate the deployment execution program file based on the privatization deployment process, execution files, and support files.

[0123] In one embodiment of the present disclosure, before generating the deployment execution program file, the privatization deployment process of the collaborative document application can be orchestrated first. The way to orchestrate the deployment process can be to manually plan the deployment process and then write the program file for executing the deployment process, or it can be that an automated tool automatically orchestrates and executes the entire privatization deployment process. Specifically, orchestrating the privatization deployment process of the collaborative document application can be to obtain the deployment environment information of the target private cloud, analyze the dependencies between the basic services and personalized services of the collaborative document application according to the rule file generated in the foregoing steps, as well as the dependencies between the system components corresponding to the services and the communication information between the services; after analyzing the dependencies between the system components, create the cloud-native system components corresponding to each service; obtain the system component information corresponding to the service, and obtain the configuration file corresponding to the system component according to the configuration file template in the rule file; mount the configuration files corresponding to all services into the cloud-native environment; run the collaborative document application in the target private cloud to provide the corresponding functions and achieve the privatization deployment of the collaborative document. The privatization deployment process is orchestrated into the deployment execution program file, and the entire deployment process is completed by an automated tool.

[0124] In another embodiment of the present disclosure, the execution file of the privatization deployment process is responsible for executing the entire privatization deployment process. The support file is used to create the support system on which the service depends. The support file contains the creation parameters of the support system and the communication endpoint information between the support system and the service configuration. The service obtains the communication endpoints of other support systems through configuration; the support file also contains the files required for deploying the cloud-native application base platform, as well as the service generation file for creating the cloud-native application and the creation file for the system component corresponding to the service. By running the deployment execution program file, the cloud-native application base platform can be built, the cloud-native application services and their corresponding system components can be created, and the support system required for the service can be created. The orchestrated privatization deployment process, execution file, and support file are jointly stored in the deployment execution program file.

[0125] The deployment execution program file and the rule file obtained in the foregoing steps are packaged into one file, and finally the deployment source file required for deploying the collaborative document application in the private cloud environment is formed.

[0126] Step 220: Obtain the deployment environment information when the collaborative document application is deployed in the target private cloud, and run the deployment execution program file based on the deployment environment information and the rule file to generate the target system components corresponding to multiple services of the collaborative document application.

[0127] To give full play to the advantages of cloud-native management and deployment of applications, in the actual deployment stage, it is necessary to create a cloud-native application base platform to provide an environment for the operation of cloud-native system components. Creating the system components corresponding to the cloud-native application is a key step in the actual deployment stage. Specifically, obtain the deployment environment information of the collaborative document application when deployed in the target private cloud, and run the deployment execution program file on the private server according to the deployment environment information and the rule file obtained in the foregoing steps to generate the target system components corresponding to multiple services of the collaborative document application.

[0128] In an embodiment of the present disclosure, the process of obtaining the deployment environment information of the collaborative document application when deployed in the target private cloud and running the deployment execution program file based on the deployment environment information and the rule file to generate the target system components corresponding to multiple services of the collaborative document application includes the following steps:

[0129] Run the deployment execution program file according to the deployment environment information to deploy the cloud-native application base platform;

[0130] Determine multiple target services corresponding to the collaborative document application according to the deployment environment information and the rule file;

[0131] Generate multiple target system components corresponding to multiple target services based on the cloud-native application base platform.

[0132] In an embodiment of the present disclosure, the deployed cloud-native base platform is used to provide a generation kit required for the cloud-native application generation process. The cloud-native base platform builds an environment for container operation and provides a microservices architecture, dividing multiple services of the collaborative document application into multiple independent service units. There is a corresponding collaborative document service in each collaborative document container. According to the rule file, the dependency relationship between each service can be automatically analyzed, and the corresponding system components are generated from the dependency relationship. In addition, according to the service resource generation mechanism of the cloud-native application base platform, a support system on which each collaborative document application service depends is created. After the configuration files of all services are prepared, all the configuration files are applied to the cloud-native base platform, and the corresponding collaborative document service can be obtained in the target private cloud environment. Run the deployment execution program file to automatically deploy the cloud-native application base platform.

[0133] After the cloud-native application base platform is built, determine the multiple target services corresponding to the collaborative document application in the target private cloud environment according to the foregoing steps. The process of determining the multiple target services of the collaborative document application is specifically as follows. According to user requirements, it is possible to know which personalized services of the collaborative document application the user needs, so as to obtain some characteristic functions of the collaborative document. For example, in the private cloud environment of government agencies, it may be necessary to obtain the gateway filtering function to prevent malicious attacks. Through gateway filtering, some malicious websites, viruses, Trojans, etc. can be filtered out to prevent their attacks and damage to the document system. Through gateway filtering, privacy can also be protected. By blocking some dangerous websites and resources, the leakage of personal information by users can be avoided. When conducting medical research in medical institutions, such as genomic sequence research, a large amount of research data may need to be saved and analyzed in the document, so it is necessary to obtain the fast large-document loading function to record, analyze, and edit the results of multiple clinical trials and genomic sequence analysis. In financial institutions, the management panel can perform statistics and analysis on the data in the document system, such as user access volume, document usage, user activity, etc., to provide data analysis support for system administrators, thereby improving data security, simplifying data management, achieving real-time detection and early warning, enhancing data analysis and statistical capabilities, improving work efficiency and management effectiveness, and enhancing the informatization level of financial operations.

[0134] In addition to some personalized services, some basic services of the collaborative document application also need to be obtained in the private cloud environment, such as document editing, file storage, social collaboration, security and permission management, etc. These basic services can all be obtained according to the rule file.

[0135] In some embodiments of the present disclosure, the process of determining the multiple target services corresponding to the collaborative document application according to the deployment environment information and the rule file includes the following steps:

[0136] Determine the functional requirements corresponding to the collaborative document application according to the deployment environment information;

[0137] Determine multiple target services from multiple service templates provided by the rule file based on the functional requirements.

[0138] In an embodiment of the present disclosure, in the target private cloud, the functional requirements corresponding to the collaborative document application include basic functional requirements and personalized functional requirements. The basic functions are provided by the basic services corresponding to the collaborative document application in the public cloud system, and the personalized functions are provided by some personalized services of the collaborative document.

[0139] In another embodiment of the present disclosure, the service templates provided by the rule file include the basic service templates corresponding to the basic services required for deploying a collaborative document application in a public cloud system. The rule file also provides personalized service templates corresponding to the personalized services required for deploying the collaborative document application in multiple private cloud scenarios. According to the service templates provided in the rule file, it is clear which basic services and functional services can be deployed in a private cloud environment, and it is necessary to consider what services are required in the target private cloud scenario, what functions the services provide, and whether the operating environment required for the services can be provided in the target private cloud. After determining which services can provide the functions required by the user, multiple target services of the collaborative document application required in the target private cloud can be determined from the multiple service templates provided by the rule file.

[0140] After determining the multiple target services corresponding to the collaborative document application in the target private cloud environment, based on the cloud-native application base platform deployed in the foregoing steps, run the deployment execution program file to generate multiple target system components corresponding to the multiple target services. The target system components include multiple target services of the collaborative document application in the target private cloud environment, containers corresponding to each service, and storage areas for each service configuration file.

[0141] In some embodiments of the present disclosure, the process of determining multiple target services from the multiple service templates provided by the rule file based on functional requirements includes the following steps:

[0142] Determine multiple functional services corresponding to the functional requirements;

[0143] Identify the dependency relationships between the multiple functional services and the basic services;

[0144] Determine multiple target services from the multiple service templates provided by the rule file according to the dependency relationships.

[0145] In one embodiment of the present disclosure, obtain the functional requirements in the target private cloud scenario, and different functions are provided by different functional services.

[0146] In another embodiment of the present disclosure, after determining the functional services required in the target private cloud, automatically identify the dependency relationships between the required functional services and the basic services required for deploying the collaborative document application in the public cloud system according to the rule file, and determine which basic services each functional service needs to depend on to complete specific business functions. While identifying the dependency relationships between the multiple functional services and the basic services through the method provided in this embodiment, the dependency relationships between the target system components corresponding to the basic services and the target system components corresponding to the functional services are also determined.

[0147] Determining multiple target services from multiple service templates provided in the rule file according to the dependency relationship means determining multiple target services required for deploying the collaborative document application in the target private cloud from multiple basic service templates and functional service templates provided in the rule file based on the service dependency relationship in the target private cloud. And after determining the dependency relationship between the target system components corresponding to each target service, based on the cloud-native application base platform, run the deployment execution program file to generate the target system components corresponding to each target service.

[0148] Step 230: Determine multiple target configuration file templates from the configuration file templates corresponding to multiple private cloud scenarios based on the target system components, and generate a configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file templates.

[0149] In some embodiments of the present disclosure, the process of generating a configuration file corresponding to each target system component includes the following steps:

[0150] Obtain the communication endpoint information of the support system;

[0151] Replace the preset identifiers in the general configuration file based on the communication endpoint information and the deployment environment information to obtain a privatized configuration file;

[0152] Generate a configuration file corresponding to each target system component according to the privatized configuration file and the target configuration file templates.

[0153] Specifically, in an embodiment of the present disclosure, the support system is a system for supporting the operation of target system components and is an important infrastructure in a cloud-native system that supports a microservices architecture and container operation. Services can provide corresponding system functions only through configuration files in combination with the corresponding support system. The support system includes a database, a message queue, and a service registration component. Services store and access data with the help of the database, providing reliable data support for the collaborative document application; the message queue is used to decouple the communication between services. When a service needs to interact with other services, it does not need to directly call the other service, but encapsulates the request into a message and sends it to the message queue; other services can obtain the message from the message queue and process it, and then return the result to the message queue after completion, making the communication efficiency between services higher. The service registration component can register the information of service instances into the service registry and dynamically update the status of the instances, such as the health status, load condition, etc. The service registry is a centralized database that stores the information of service instances. It is used to coordinate the communication between service providers and users and supports functions such as dynamic service discovery and load balancing. Users can obtain the information of available service instances from the registry and schedule according to the status and load condition of the instances, ensuring better availability and elasticity of the system. The support system can ensure the reliability and stability of running the collaborative document application in a private cloud environment.

[0154] In an embodiment of the present disclosure, a generalized configuration file corresponding to the basic functions of the collaborative document application and communication endpoint information of the support system are deployed in the target private cloud environment according to the deployment environment information. The generalized configuration file provides a storage field for the communication endpoints of the corresponding support system, and the storage field is identified by a preset identifier. The preset identifier in the generalized configuration file is replaced according to the communication endpoint information in the target private cloud, and the generalized configuration file is associated with the corresponding support system in the target private cloud environment to obtain a privatized configuration file corresponding to the basic collaborative document function service in the target private cloud environment. The target configuration file template also contains the communication endpoint information of the corresponding support system and can be associated with the corresponding support system to obtain a configuration file corresponding to the personalized collaborative document function service in the target private cloud environment. The privatized configuration file corresponding to the basic collaborative document function service and the target configuration file template corresponding to the collaborative document personalized service required when deploying the collaborative document application in the target private cloud are combined to obtain a configuration file corresponding to each target system component in the target private cloud.

[0155] In some embodiments of the present disclosure, the process of generating a configuration file corresponding to each target system component according to the communication endpoint information, deployment environment information, rule file, and target configuration file template includes the following steps:

[0156] Determine the association relationship between communication endpoint information and each target system component based on a rule file;

[0157] Render based on the association relationship, deployment environment information, rule file, and target configuration file template to obtain the configuration file corresponding to each target system component.

[0158] In an embodiment of the present disclosure, determining the association relationship between communication endpoint information and each target system component based on a rule file specifically means that the rule file provides the storage fields of the communication endpoint information of the support system in the configuration file corresponding to each target system component, that is, the association relationship between the communication endpoint information of the support system and each target system component can be determined according to the rule file. Determine multiple target configuration file templates according to the deployment environment information, update the configuration information of the general configuration file in the rule file to obtain a configuration file that has not been communicatively associated with the support system. According to the determined association relationship, associate the service configuration file and the support system, and finally render the configuration file through the rule file to obtain the configuration file corresponding to each target system component. The target system component reads the corresponding communication endpoint information of the support system in the configuration file and provides the system functions corresponding to the target service through the support system.

[0159] Step 240, store each configuration file in the storage area specified by the corresponding target system component.

[0160] Generate the target configuration files corresponding to all target system components, run the deployment execution program file to apply all target configuration files to the cloud native application base platform, and store the configuration information in the form of key-value pairs in the ConfigMap. The cloud native application base platform mounts the ConfigMap containing the configuration information to the specified path in the Pod in the form of a file, and each container corresponding to the service reads the mounted configuration file from the specified path to obtain the service configuration information stored in the ConfigMap.

[0161] In some embodiments of the present disclosure, the process of storing each configuration file in the storage area specified by the corresponding target system component includes the following steps:

[0162] Determine the storage area corresponding to each target system component based on the cloud native application base platform;

[0163] Store the configuration file corresponding to each target system component in the corresponding storage area.

[0164] In one embodiment of the present disclosure, the cloud-native application base platform automatically orchestrates the storage areas of the configuration files of each system component. Applying all the configuration files to the cloud-native application base platform means storing the configuration files in the configuration management center of the cloud-native platform, such as in the highly available distributed reliable key-value store (Etcd) of K8s. Etcd is used to store and manage various resource objects in the K8s cluster, among which the configuration files can be shared by multiple services. Then, all the configuration information is saved through ConfigMap, and all the configuration files are mounted in the form of ConfigMap to the running environment of each service. The configuration file of each service is encapsulated into a container image, and the cloud-native base platform mounts the ConfigMap containing the service configuration information to the specified path in the POD in the form of a file.

[0165] Step 250, when running the collaborative document application in the target private cloud, read the configuration file from the corresponding storage area based on the target system component to provide the system function corresponding to the target system component, so as to realize the privatized deployment of the collaborative document application.

[0166] Register the network address and metadata information corresponding to the collaborative document service instance to the service registry. Registering the collaborative document service in the internal terminal of the target private cloud means that the service instance registers the user's network address and metadata information to the service registry when starting up. The metadata information includes descriptive information such as the type, format, and update date of the data. The metadata information can also include data management information such as the source and security of the data. The user terminal can directly obtain the service instance information from the service provider without the intervention of the middle layer. After the collaborative document registration is completed, the corresponding collaborative document service can be obtained through the Internet. Since one service depends on other services to implement specific functions, each service is started in the form of one or more Pods. When the containers in the Pod are started, the first collaborative document service process after the collaborative document application starts running is enabled. The collaborative document service reads the configuration files of the corresponding system components from the specified path in each Pod, establishes a communication connection relationship with the support system corresponding to the system component through the communication endpoint information in the configuration file, obtains the support of the support system, and provides the system function corresponding to the system component to the users in the target private cloud through the Internet, so as to realize the privatized deployment of the collaborative document application.

[0167] In some embodiments of the present disclosure, such as Figure 4The following is a schematic diagram of the overall process of the private deployment method of the collaborative document application provided by the present disclosure. Specifically, the entire private deployment process of the collaborative document application can be summarized as follows: obtaining the deployment environment information of the target private cloud; running an automated tool on Server 110, that is, executing the deployment source file on the server to start automatically deploying the collaborative document application in the target private cloud; determining multiple target services in the target private cloud according to the deployment environment information and the rule file, and analyzing the dependencies between the services and the dependencies between the system components corresponding to each service; according to the analyzed service component dependencies, running the deployment execution program file to generate the system components corresponding to each service; obtaining the target system component information, and generating the target configuration file corresponding to each system component according to the target configuration file template, the deployment environment information, the deployment execution program file, and the rule file; mounting the target configuration file into the service running environment and storing it in the storage area corresponding to each system component; starting the collaborative document service process, the service reads the corresponding configuration file, establishes a communication connection with the support system, and provides the corresponding system functions, thus completing the deployment of the collaborative document application in the target private cloud.

[0168] In summary, by using the private deployment method of the collaborative document application provided by the present disclosure, that is, obtaining the deployment source file of the collaborative document application, the deployment source file includes the deployment execution program file and the rule file, the deployment execution program file is used to generate the system components of the cloud-native application, and the rule file is generated based on the configuration file when the collaborative document application is deployed in the public cloud and the configuration file templates corresponding to multiple private cloud scenarios; obtaining the deployment environment information when the collaborative document application is deployed in the target private cloud, and running the deployment execution program file based on the deployment environment information and the rule file to generate the target system components corresponding to multiple services of the collaborative document application;

[0169] Determine multiple target configuration file templates from the configuration file templates corresponding to multiple private cloud scenarios for the target system components, and generate a configuration file for each target system component based on the deployment environment information, the rule file, and the target configuration file templates; store each configuration file in the storage area specified by the corresponding target system component; when running the collaborative document application in the target private cloud, read the configuration file from the corresponding storage area based on the target system component to provide the system functions corresponding to the target system component, so as to realize the privatized deployment of the collaborative document application. In this way, the generation speed of the configuration file in the target private cloud scenario is improved by the configuration file templates in multiple private cloud scenarios in the rule file, and the automated deployment tool is orchestrated in advance to execute the entire privatized deployment process. The efficiency of privatizing the collaborative document application is improved. Compared with the related art that relies on implementers to operate according to the process of deploying the collaborative document application in the public cloud, it is possible to avoid a large number of manual operations during the deployment process, a long deployment cycle, and problems of errors or loss of configuration during the deployment process. Therefore, by adopting the method for privatized deployment of the collaborative document application provided by the present disclosure, the privatization efficiency of the collaborative document application can be improved without changing the distributed configuration management architecture.

[0170] Detailed description of the embodiments of the present disclosure in combination with specific application scenarios

[0171] In some embodiments of the present disclosure, taking the method for privatized deployment of the collaborative document application provided by the present disclosure applied to a certain private cloud scenario as an example, the method for privatized deployment of the collaborative document application provided by the present disclosure will be introduced in detail. As Figure 5 shown, it is a schematic flowchart of a deployment preparation stage of the method for privatized deployment of the collaborative document application provided by the present disclosure. The method specifically includes the following steps:

[0172] Step 510, the deployment preparation terminal writes a rule file.

[0173] In the embodiments of the present disclosure, a rule file is provided, and the configuration files of each collaborative document service are written into a rule file according to a certain logic. The rule file can improve the speed of deploying the configuration file in the target private cloud. In the related art, it depends on implementers to deploy the supporting software and hardware, then correspondingly adjust the configuration file for docking with the supporting software and hardware, and finally deploy the collaborative document service. Due to the differences in software and hardware facilities in different private cloud environments, problems such as a long deployment cycle, easy loss of configuration during the deployment process, and inconvenient management occur. The rule file provided by the present disclosure can well avoid the problem of slow deployment configuration speed caused by software and hardware environment differences, thereby effectively improving the efficiency of privatized deployment of collaborative documents.

[0174] Specifically, the deployment preparation terminal compiles the configuration files of each collaborative document service according to the prefabricated target, and the compilation process is as described in the foregoing steps, which will not be elaborated here. The deployment preparation terminal obtains the configurations of each service for deploying the collaborative document application in the public cloud, and divides these configurations into unmodifiable fixed configurations and modifiable variable configurations. The variable configuration area is identified by placeholder marks. The fixed configurations reuse the configuration information during deployment in the public cloud to obtain the general configuration file of the collaborative document, that is, the configuration file corresponding to the basic service of the collaborative document; obtains configuration file templates in multiple private cloud scenarios. The configuration file templates are configuration file templates corresponding to the collaborative document function service, and can support dynamic adjustment in different deployment environments to meet user needs. The deployment preparation terminal packages the general configuration file of the collaborative document and multiple configuration file templates in multiple private cloud scenarios into a rule file.

[0175] Step 520: The deployment preparation terminal orchestrates the entire privatization deployment process and compiles a deployment execution program file to automatically execute the privatization deployment process.

[0176] The present disclosure provides an automated tool for executing the privatization deployment process, which can automatically execute the entire deployment process, avoiding the problems of long deployment cycles and easy errors in the deployment process caused by relying on a large number of manual operations in the related art, thereby improving the efficiency of the actual privatization deployment of collaborative documents. In addition, the privatization deployment method provided by the present disclosure does not require modification of the distributed configuration management architecture, which can effectively reduce the deployment implementation cost.

[0177] Specifically, after generating the rule file, the deployment preparation terminal can compile a deployment execution program file according to the implementation personnel for the orchestrated privatization deployment process. The specific process of generating the deployment execution program file is as described in the foregoing steps. The execution file is used to execute the deployment process, and the support file can build a cloud-native base platform, create system components and service support systems, and can apply the prepared service configuration file to the cloud-native base platform, so that the deployed collaborative document application can run normally.

[0178] Step 530: The deployment preparation terminal packages the rule file and the deployment execution program file to generate a deployment source file.

[0179] In the embodiment of the present disclosure, a deployment source file for deploying a collaborative document application in a private cloud environment is provided, and the privatization deployment is performed depending on the deployment source file. The deployment execution program file not only includes the generated files of the components corresponding to multiple services during the deployment of the collaborative document application in the public cloud, but also includes the generated file templates of the components corresponding to multiple private cloud scenario services.

[0180] Specifically, the implementer imports the prepared deployment source file into the private server. After communicating with the user to determine the deployment requirements and obtaining the deployment environment information, the private deployment of the collaborative document application can be started on the server.

[0181] Through the private deployment method of the collaborative document application provided by this embodiment of the disclosure, it is possible to avoid the problems in the related art where implementers need to deploy the supporting software and hardware in advance and then manually test and adjust the corresponding configuration files, resulting in low deployment efficiency and difficult system upgrade and maintenance. Thus, the private deployment efficiency of the collaborative document can be effectively improved.

[0182] As Figure 6 shown, it is a schematic flowchart of a process in the deployment implementation stage of the private deployment method of the collaborative document application provided by this disclosure. The method specifically includes the following steps:

[0183] Step 610: The deployment execution terminal obtains the deployment source file.

[0184] In this embodiment of the disclosure, the deployment source file prepared by the deployment preparation terminal can be imported into the deployment execution terminal. The deployment source file can be copied to the deployment execution terminal through a USB flash drive, or directly obtained from the web page. The file import method is not restricted.

[0185] Step 620: The deployment execution terminal obtains the deployment environment information and stores the deployment environment information in the meta-configuration file.

[0186] In this embodiment of the disclosure, after the implementer communicates with the operation and maintenance personnel of the private cloud, the relevant information of the deployment environment is obtained, including: user scale, network architecture, domain name situation, server configuration, etc. The implementer records these environment information in a single configuration meta-configuration file. Different variables in the meta-configuration file represent the corresponding deployment environment information. After all the environment information is updated, the meta-configuration file is saved to the server, that is, the deployment execution terminal. The deployment execution terminal automatically launches the deployment process of the collaborative document application according to the meta-configuration file and the deployment source file imported in the previous step, without other manual deployment operations.

[0187] Step 630: The deployment execution terminal runs the deployment execution program file to deploy the cloud native application base platform.

[0188] In the embodiments of the present disclosure, the deployment execution terminal runs the deployment execution program file, and can determine the number of services according to the on-site user scale collected in the meta-configuration file, and automatically complete the deployment of the cloud-native application base platform. During the deployment of the cloud-native base platform, the deployment execution terminal is standardized, including: clock alignment, Secure Shell (SSH) key distribution, Domain Name System (DNS) resolution configuration, etc.

[0189] Step 640: The deployment execution terminal analyzes the service dependency information according to the meta-configuration file and the rule file, and determines multiple target services required in the target private cloud.

[0190] In the embodiments of the present disclosure, the specific process of analyzing the service dependency information and determining multiple target services in the target private cloud is as shown in the foregoing steps. The deployment execution terminal detects the software and hardware information of the user according to the meta-configuration file, including CPU architecture, clock frequency, user scale, operating system version, disk Input / Output Operations Per Second (IOPS), network architecture, and analyzes the dependency relationship between the collaborative document basic service and the functional service according to this private cloud environment information and the rule file. In the private cloud environment, due to the change of the deployment environment information, the dependency relationship between the collaborative document basic service and the functional service will also change, and the corresponding configuration information of the service will also change. After determining the service dependency relationship, the dependency relationship between the cloud-native system components corresponding to each service is also determined, and multiple service templates in the rule file determine multiple target services of the target private cloud.

[0191] Step 650: The deployment execution terminal runs the deployment execution program file on the cloud-native base platform according to the service dependency information and the rule file to generate cloud-native system components corresponding to each target service.

[0192] In the embodiments of the present disclosure, after determining the service dependency relationship in the private cloud environment according to the foregoing steps, the dependency relationship between multiple system components can be determined. According to the deployment environment information and the dependency relationship between multiple target system components, determine the target generation files of multiple target components in the generation files of the components corresponding to multiple services when the collaborative document application in the deployment execution program file is deployed in the public cloud and the generation files of the components corresponding to multiple private cloud scenario services, and execute multiple target generation files in the cloud-native base platform to generate corresponding target components, that is, cloud-native containers corresponding to each service.

[0193] Step 660: The deployment execution terminal runs the deployment execution program file on the cloud-native application base platform according to the rule file and the cloud-native system component information to create a support system corresponding to each system component.

[0194] In an embodiment of the present disclosure, according to the description of the support system for service dependencies in the rule file, a support system required for each service is created, that is, the support system on which each system component depends for operation. The collaborative document service in the container obtains the communication endpoint information of the support system through corresponding configurations, so that the support system can support the stable operation of the system components. The support system includes: the database used by the service, the message queue used by the service, the service registration component, and also includes some functional PaaS services. The creation parameters of the support system are stored in the rule file. The deployment execution terminal runs the support file in the deployment execution program file, and uses the service generation mechanism of the cloud native base platform to create the support system required for each system component. By creating the support system in the cloud native base platform, the problem in the related art that various support systems need to be provided by the user network when deploying the collaborative document application in the private cloud scenario, resulting in difficulties in subsequent system upgrade and maintenance, is solved, and the system operation and maintenance efficiency is improved.

[0195] Step 670: The deployment execution terminal obtains the association relationship between the communication information of the support system and the target system component according to the rule file, and renders the configuration file in the target private cloud based on the meta-configuration file, the rule file, the configuration file template, and the association relationship.

[0196] In an embodiment of the present disclosure, the system components corresponding to each service are created according to the foregoing steps, and the support system on which each system component depends is created according to the foregoing steps. The rule file describes the corresponding storage fields in the configuration file of each service for the communication endpoint information of the support system on which each system component depends. The underlying rendering engine of the cloud native application base platform can associate the communication information of the support system with the service configuration file according to the logic in the rule file. According to the deployment environment information, the configuration parameters in the generalized configuration file in the rule file can be updated, and the target configuration file templates of multiple functional services required in the target private cloud are determined. The deployment execution terminal runs the deployment execution program file, and renders and generates the final configuration file of each target system component according to the association relationship, the updated generalized configuration file, and multiple target configuration file templates.

[0197] Step 680: The deployment execution terminal stores all the configuration files in the specified storage area in the cloud native application base platform, and creates multiple target services in the cloud native base platform in the form of workloads.

[0198] In the embodiments of the present disclosure, all service configuration files in the target private cloud have been prepared. The deployment execution terminal applies all the configuration files to the cloud-native application base platform, that is, stores them in the configuration management center of the cloud-native platform, such as etcd of Kubernetes, where the configuration files can be shared by multiple services. Then, all configuration information is saved through ConfigMap, and all configuration files are mounted in the running environment of each service in the form of ConfigMap. The configuration file of each service is encapsulated into a container image, and the cloud-native base platform mounts the ConfigMap containing the service configuration information to the specified path in the POD. When running the collaborative document application in the target private cloud, ConfigMap decouples the configuration file and the container image, enabling the collaborative document service in the container to use the corresponding configuration file.

[0199] After the configuration files of all services are prepared, the deployment execution terminal also creates the collaborative document service in the cloud-native base platform in the form of a workload.

[0200] Step 690, the deployment execution terminal starts the collaborative document application, provides corresponding services to the internal terminals of the target private cloud through the Internet, and completes the privatization deployment of the collaborative document application.

[0201] In the embodiments of the present disclosure, the deployment execution terminal registers the network address and metadata information corresponding to the collaborative document service instance to the service registry. After the registration of the collaborative document service is completed, the user terminal can obtain the corresponding collaborative document service through the Internet. After the deployment execution terminal deploys the collaborative document application in the target private cloud environment, the user terminal obtains the collaborative document application service through the Internet. Each collaborative document service is started in the form of one or more Pods. The collaborative document container starts the first process, and the No. 1 process starts the collaborative document service process. The collaborative document service reads the corresponding configuration file, establishes a communication connection with the support system, provides corresponding collaborative document functions to the user terminal, and realizes the privatization deployment of the collaborative document.

[0202] The privatization deployment method of the collaborative document application provided by the embodiments of the present disclosure improves the generation speed of configuration files in the target private cloud scenario and pre-arranges the automated deployment tool to execute the entire privatization deployment process through the configuration file templates in multiple private cloud scenarios in the rule file, which can avoid a large number of manual operations in the deployment process, long deployment cycles, and the problem of low privatization deployment efficiency caused by errors or loss of configurations during the deployment process, and improves the efficiency of privatization of the collaborative document application.

[0203] Description of the device and equipment of the embodiments of the present disclosure

[0204] It can be understood that although the steps in each of the above flowcharts are sequentially shown according to the representation of the arrows, these steps are not necessarily executed sequentially in the order represented by the arrows. Unless there is a clear description in this embodiment, the execution of these steps has no strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the above flowchart may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of the steps or stages in other steps or other steps.

[0205] Figure 7 FIG. 4 is a schematic structural diagram of a private deployment device 700 for a collaborative document application provided by an embodiment of the present disclosure. The private deployment device 700 for the collaborative document application includes:

[0206] A first acquisition unit 710, configured to acquire a deployment source file of the collaborative document application, where the deployment source file includes a deployment execution program file and a rule file; wherein, the deployment execution program file is used to generate system components of a cloud-native application, and the rule file is generated based on a configuration file when the collaborative document application is deployed in a public cloud and configuration file templates corresponding to multiple private cloud scenarios;

[0207] A second acquisition unit 720, configured to acquire deployment environment information when the collaborative document application is deployed in a target private cloud, and run the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application;

[0208] A generation unit 730, configured to determine multiple target configuration file templates from the configuration file templates corresponding to multiple private cloud scenarios based on the deployment environment information, and generate a configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file templates;

[0209] A storage unit 740, configured to store each configuration file in a storage area specified by the corresponding target system component;

[0210] A reading unit 750, configured to, when running the collaborative document application in the target private cloud, read the configuration file from the corresponding storage area based on the target system component to provide system functions corresponding to the target system component, and implement private deployment of the collaborative document application.

[0211] Optionally, in some embodiments, the second acquisition unit 720 includes:

[0212] A deployment subunit, configured to run a deployment execution program file according to deployment environment information to deploy a cloud native application base platform, where the cloud native application base platform is used to provide a generation kit required for the cloud native application generation process;

[0213] A determination subunit, configured to determine multiple target services corresponding to a collaborative document application according to deployment environment information and a rule file;

[0214] A generation subunit, configured to generate multiple target system components corresponding to multiple target services based on the cloud native application base platform.

[0215] Optionally, in some embodiments, the determination subunit includes:

[0216] A determination module, configured to determine the functional requirements corresponding to the collaborative document application according to deployment environment information;

[0217] The determination subunit is further configured to:

[0218] Determine multiple target services from multiple service templates provided in the rule file based on the functional requirements.

[0219] Optionally, in some embodiments, the determination module includes:

[0220] A determination sub-module, configured to determine multiple functional services corresponding to the functional requirements;

[0221] An identification sub-module, configured to identify the dependency relationships between multiple functional services and basic services;

[0222] The determination module is further configured to:

[0223] Determine multiple target services from multiple service templates provided in the rule file according to the dependency relationships.

[0224] Optionally, in some embodiments, the private deployment device for the collaborative document application further includes a rule file generation unit, and the rule file generation unit further includes:

[0225] A first acquisition sub-unit, configured to acquire a public cloud configuration file corresponding to each service when the collaborative document application is deployed in a public cloud, where the public cloud configuration file includes an unmodifiable first sub-configuration file and a modifiable second sub-configuration file;

[0226] An update sub-unit, configured to perform generalization update on the second sub-configuration file in the public cloud configuration file to obtain a general configuration file for the collaborative document;

[0227] A first generation sub-unit, configured to acquire configuration file templates in multiple private cloud scenarios, and generate a rule file based on the configuration file templates and the general configuration file.

[0228] Optionally, in some embodiments, the update subunit includes:

[0229] An identification module, configured to identify modifiable content in the second configuration file;

[0230] A generation module, configured to replace the modifiable content with a preset marker, and determine a general configuration file according to the second sub-configuration file and the first sub-configuration file after the content replacement.

[0231] Optionally, in some embodiments, the generation unit 730 includes:

[0232] An acquisition module, configured to acquire communication endpoint information of the support system;

[0233] A replacement module, configured to replace preset markers in the general configuration file based on the communication endpoint information and the deployment environment information to obtain a privatized configuration file;

[0234] A generation sub-module, configured to generate a configuration file corresponding to each target system component according to the privatized configuration file and the target configuration file template.

[0235] Optionally, in some embodiments, the privatized deployment device of the collaborative document application further includes a deployment execution program file generation unit, and the deployment execution program file generation unit further includes:

[0236] An orchestration sub-unit, configured to orchestrate the privatized deployment process of the collaborative document application;

[0237] A second acquisition sub-unit, configured to acquire execution files and support files required in the privatized deployment process;

[0238] A second generation sub-unit, configured to generate a deployment execution program file based on the privatized deployment process, the execution files, and the support files.

[0239] Optionally, in some embodiments, the storage unit 740 includes:

[0240] A second determination sub-unit, configured to determine a storage area corresponding to each target system component based on the cloud-native application base platform;

[0241] The storage unit 740 is further configured to:

[0242] Store the configuration file corresponding to each target system component in the corresponding storage area.

[0243] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the function of the module or unit.

[0244] Referring to Figure 8 , Figure 8 FIG. 7 is a block diagram of a part of the structure of the terminal 140 according to an embodiment of the present disclosure. The terminal 140 includes components such as a radio frequency (RF) circuit 810, a memory 815, an input unit 830, a display unit 840, a sensor 850, an audio circuit 860, a wireless fidelity (WiFi) module 870, a processor 880, and a power supply 890. Those skilled in the art can understand that Figure 8 the structure of the terminal 140 shown does not limit the mobile phone or computer, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0245] The RF circuit 810 can be used to receive and transmit information or signals during a call. Specifically, after receiving the downlink information from the base station, it is given to the processor 880 for processing; in addition, the uplink data designed is sent to the base station.

[0246] The memory 815 can be used to store software programs and modules. The processor 880 executes various functional applications and model training of the terminal by running the software programs and modules stored in the memory 815.

[0247] The input unit 830 can be used to receive input digital or character information, and generate key signal inputs related to the settings and function controls of the terminal. Specifically, the input unit 830 may include a touch panel 831 and other input devices 832.

[0248] The display unit 840 can be used to display the input information or the provided information and various menus of the terminal. The display unit 840 may include a display panel 841.

[0249] The audio circuit 860, the speaker 861, and the microphone 862 can provide an audio interface.

[0250] In this embodiment, the processor 880 included in the terminal 140 can execute the privatized deployment method of the collaborative document application in the previous embodiment.

[0251] The terminal 140 in the embodiments of the present disclosure includes, but is not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc. The embodiments of the present invention can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, intelligent transportation, assisted driving, etc.

[0252] Figure 9 FIG. is a block diagram of a part of the server 110 for implementing the embodiments of the present disclosure. The server 110 may vary greatly due to configuration or performance, and may include one or more central processing units (CPUs) 922 (for example, one or more processors) and a storage device 932, and one or more storage media 930 (for example, one or more mass storage devices) for storing application programs 942 or data 944. Among them, the storage device 932 and the storage media 930 may be transient storage or persistent storage. The program stored in the storage media 930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server 110. Further, the central processing unit 922 may be configured to communicate with the storage media 930 and execute a series of instruction operations in the storage media 930 on the server 110.

[0253] The server 110 may further include one or more power supplies 926, one or more wired or wireless network interfaces 950, one or more input / output interfaces 958, and / or one or more operating systems 941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0254] The central processing unit 922 in the server 110 may be used to execute the privatized deployment method of the collaborative document application in the embodiments of the present disclosure.

[0255] The embodiments of the present disclosure further provide a storage medium for storing program code for executing the privatized deployment method of the collaborative document application in the foregoing respective embodiments.

[0256] The embodiments of the present disclosure further provide a computer program product, which includes a computer program. The processor of the computer device reads and executes the computer program, so that the computer device executes the privatized deployment method of the collaborative document application as described above.

[0257] In the description of the present disclosure and the above-mentioned accompanying drawings, terms such as "first", "second", "third", "fourth", etc. (if any) are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of the present disclosure described herein can be implemented in an order different from those illustrated or described herein. In addition, the terms "comprising" and "including" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not necessarily limit to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0258] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects and indicates that three relationships may exist. For example, "A and / or B" may mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or a similar expression means any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (one) of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0259] It should be understood that in the description of the embodiments of the present disclosure, the meaning of "a plurality (or multiple items)" is more than two. Understandings such as greater than, less than, exceeding, etc. do not include the present number, and understandings such as above, below, within, etc. include the present number.

[0260] In several embodiments provided by the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of devices or units can be in electrical, mechanical or other forms.

[0261] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0262] In addition, the functional units in various embodiments of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0263] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present disclosure, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of the present disclosure. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs that can store program codes.

[0264] It should also be understood that the various embodiments provided in the present disclosure can be combined arbitrarily to achieve different technical effects.

[0265] The above is a specific description of the embodiments of the present disclosure, but the present disclosure is not limited to the above embodiments. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of the present disclosure, and these equivalent deformations or substitutions are all included within the scope defined by the claims of the present disclosure.

Claims

1. A method for private deployment of a collaborative document application, characterized in that, The method includes: Obtain the deployment source file of the collaborative document application. The deployment source file includes a deployment execution program file and a rule file. The deployment execution program file is used to generate system components of a cloud-native application. The rule file is generated based on the configuration file when the collaborative document application is deployed in a public cloud and configuration file templates corresponding to multiple private cloud scenarios. Obtain the deployment environment information when the collaborative document application is deployed in the target private cloud, and run the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application. Determine multiple target configuration file templates from the configuration file templates corresponding to the multiple private cloud scenarios based on the target system components, and generate a configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file templates. Store each configuration file in the storage area specified by the corresponding target system component. When running the collaborative document application in the target private cloud, read the configuration file from the corresponding storage area based on the target system component to provide the system function corresponding to the target system component.

2. The method according to claim 1, characterized in that, The running of the deployment execution program file based on the deployment environment information and the rule file to generate target system components corresponding to multiple services of the collaborative document application includes: Run the deployment execution program file according to the deployment environment information to deploy a cloud-native application base platform, and the cloud-native application base platform provides a generation kit required for the cloud-native application generation process. Determine multiple target services corresponding to the collaborative document application according to the deployment environment information and the rule file. Generate multiple target system components corresponding to the multiple target services based on the cloud-native application base platform.

3. The method according to claim 2, characterized in that, The determining of multiple target services corresponding to the writing document application according to the deployment environment information and the rule file includes: Determine the functional requirements corresponding to the collaborative document application according to the deployment environment information. Determine multiple target services from multiple service templates provided in the rule file based on the functional requirements.

4. The method according to claim 3, wherein The determining of multiple target services from multiple service templates provided in the rule file based on the functional requirements includes: Determine multiple functional services corresponding to the functional requirements. Identify the dependency relationships between the multiple functional services and the basic services. Determine multiple target services from multiple service templates provided in the rule file according to the dependency relationships.

5. The method according to claim 1, characterized in that, The generation process of the rule file includes the following steps: Obtain the public cloud configuration file corresponding to each service when the collaborative document application is deployed in the public cloud. The public cloud configuration file includes an unmodifiable first sub-configuration file and a modifiable second sub-configuration file. Perform a generalization update on the second sub-configuration file in the public cloud configuration file to obtain the general configuration file of the collaborative document. Obtain configuration file templates under multiple private cloud scenarios, and generate a rule file based on the configuration file templates and the general configuration file.

6. The method according to claim 5, wherein Generalizing and updating the second sub - configuration file in the public cloud configuration file to obtain the general configuration file of the collaboration document, including: Identifying the modifiable content in the second sub - configuration file; Replacing the modifiable content with a preset marker, and determining the general configuration file based on the second sub - configuration file after content replacement and the first sub - configuration file.

7. The method according to claim 6, wherein Generating the configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file template, including: Obtaining the communication endpoint information of the support system, where the support system is a system created based on the cloud - native application base platform to support the operation of the target system component, and the support system includes a database, a message queue, and a service registration component; Replacing the preset marker in the general configuration file based on the communication endpoint information and the deployment environment information to obtain a privatized configuration file; Generating the configuration file corresponding to each target system component according to the privatized configuration file and the target configuration file template.

8. The method according to claim 1, characterized in that The generation process of the deployment execution program file includes the following steps: Orchestrating the privatized deployment process of the collaboration document application; Obtaining the execution files and support files required in the privatized deployment process; Generating a deployment execution program file based on the privatized deployment process, the execution files, and the support files.

9. The method according to claim 2, wherein Storing each configuration file in the storage area specified for the corresponding target system component, including: Determining the storage area corresponding to each target system component based on the cloud - native application base platform; Storing the configuration file corresponding to each target system component in the corresponding storage area.

10. A private deployment device for a collaborative document application, characterized in that, Including: A first acquisition unit for acquiring the deployment source files of the collaboration document application, where the deployment source files include a deployment execution program file and a rule file; wherein, the deployment execution program file is used to generate the system components of the cloud - native application, and the rule file is generated based on the configuration file when the collaboration document application is deployed in the public cloud and the configuration file templates corresponding to multiple private cloud scenarios; A second acquisition unit for acquiring the deployment environment information when the collaboration document application is deployed in the target private cloud, and running the deployment execution program file based on the deployment environment information and the rule file to generate the target system components corresponding to multiple services of the collaboration document application; A generation unit for determining multiple target configuration file templates from the configuration file templates corresponding to the multiple private cloud scenarios based on the deployment environment information, and generating the configuration file corresponding to each target system component according to the deployment environment information, the rule file, and the target configuration file template; A storage unit for storing each configuration file in the storage area specified for the corresponding target system component; A reading unit for, when running the collaboration document application in the target private cloud, reading the configuration file from the corresponding storage area based on the target system component to provide the system function corresponding to the target system component, and realizing the privatized deployment of the collaboration document application.

11. An electronic device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the private deployment method of the collaborative document application according to any one of claims 1 to 9.

12. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the private deployment method of the collaborative document application according to any one of claims 1 to 9.

13. A computer program product, which includes a computer program that is read and executed by a processor of a computer device, so that the computer device executes the private deployment method of the collaborative document application according to any one of claims 1 to 9.

Images