CN114741155A - Front-end containerization method of individual insurance sales system and related equipment - Google Patents
Front-end containerization method of individual insurance sales system and related equipment Download PDFInfo
- Publication number
- CN114741155A CN114741155A CN202210228701.5A CN202210228701A CN114741155A CN 114741155 A CN114741155 A CN 114741155A CN 202210228701 A CN202210228701 A CN 202210228701A CN 114741155 A CN114741155 A CN 114741155A
- Authority
- CN
- China
- Prior art keywords
- mirror image
- file
- containerization
- sales system
- image
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
According to the method, a basic mirror image is generated in the risk sale system, a front-end file is obtained, the front-end file is containerized and a description file is generated, a new mirror image layer is built on the outer layer of the basic mirror image according to the description file, the basic mirror image and the new mirror image layer jointly form a service mirror image, and then the service mirror image is deployed to a container platform, so that the front-end containerization of the risk sale system is completed. According to the method, the resources with different functions are isolated in a containerization mode, decoupling among the resources is achieved, and therefore the front-end research and development process and the deployment mode are unified, the front-end research and development process can be brought into an automatic system, the front-end research and development process is guaranteed to run stably, and research and development are convenient and fast.
Description
Technical Field
The application relates to the technical field of system construction, in particular to a front-end containerization method and related equipment for an individual insurance sales system.
Background
In the related art, an individual insurance sales system stores a front-end static resource file separated from a back end on a server where a centralized agent cluster is located in a compiled file manner, and a configuration file path directs a request to the file where the request is located in the agent cluster configuration. Since the files are converted from the traditional integration service, the files are simply grouped according to functions and are placed in a plurality of directories such as styles, scripts, web pages and the like.
In the research and development process of the risk sale system, if a part of functions are newly added, front-end resource files of the functions are copied into corresponding directories in a classified manner, if the functions are modified, the corresponding files are modified, and the modified files are issued as products in an incremental manner, so that the problems that a front-end deployment mode cannot be unified, a plurality of static resources are mixed together, full change cannot be realized, cost is increased due to different front-end and rear-end maintenance modes, the front-end research and development processes cannot be brought into an automatic system and the like are caused.
Disclosure of Invention
In view of the above, the present application provides a front-end containerization method for an insurance sales system and related devices.
Based on the above purpose, the present application provides a front-end containerization method for an individual insurance sales system, comprising: generating a base image in the individual insurance sales system; acquiring a front-end file, and containerizing the front-end file to generate a description file; according to the description file, a new mirror image layer is built on the outer layer of the basic mirror image, and the basic mirror image and the new mirror image layer jointly form a service mirror image; and deploying the service mirror image to a container platform to finish the front-end containerization of the individual insurance sales system.
Optionally, the containerizing the front-end file includes: and splitting the front-end file according to different functions and packaging the front-end file into a plurality of front-end containers, wherein each front-end container is isolated from each other.
Optionally, the containerizing the front-end file and generating the description file includes: and generating a plurality of description files which are in one-to-one correspondence with the plurality of front-end containers according to the attribute information and the description information of the plurality of front-end containers, wherein the description files comprise the association information of each front-end container and the basic mirror image.
Optionally, the constructing a new image layer on the outer layer of the base image according to the description file includes: and constructing a plurality of sub-mirror image layers on the outer layer of the basic mirror image according to the description file, wherein all the sub-mirror image layers jointly form the new mirror image layer.
Optionally, the generating a base image in the individual insurance sales system includes: and generating the base image in the system image of the individual insurance sales system by using image generation software.
Optionally, after the front-end file is containerized and before the description file is generated, the method further includes: pre-processing the front-end vessel, the pre-processing comprising adding a health check tool to the front-end vessel.
Optionally, the containerizing the front-end file and generating the description file further includes: containerizing the front-end file and generating a boot command file configured to be utilized by the service image to perform a boot.
Based on the above object, the present application further provides a front-end containerization apparatus for an individual insurance sales system, comprising: a generation module configured to generate a base image in the individual insurance sales system; the containerization module is used for acquiring the front-end file, containerizing the front-end file and generating a description file; the construction module is configured to construct a new mirror image layer on the outer layer of the basic mirror image according to the description file, and the basic mirror image and the new mirror image layer jointly form a service mirror image; a deployment module configured to deploy the service image to a container platform to complete front-end containerization of the individual insurance sales system.
In view of the foregoing, the present application further provides an electronic device, which includes a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes any one of the methods for front-end containerization of risk sale systems.
In view of the above, the present application further provides a non-transitory computer readable storage medium storing computer instructions, wherein the computer instructions are configured to cause a computer to execute any one of the individual insurance sales system front-end containerization methods.
As can be seen from the above, according to the front-end containerization method and the related device for the individual insurance sales system, a basic mirror image is generated in the individual insurance sales system, a front-end file is acquired, the front-end file is containerized and a description file is generated, a new mirror image layer is built on the outer layer of the basic mirror image according to the description file, the basic mirror image and the new mirror image layer jointly form a service mirror image, and the service mirror image is deployed to a container platform to complete the front-end containerization of the individual insurance sales system. According to the method, the resources with different functions are isolated in a containerization mode, decoupling among the resources is achieved, and therefore the front-end research and development process and the deployment mode are unified, the front-end research and development process can be brought into an automatic system, the front-end research and development process is guaranteed to run stably, and research and development are convenient and fast.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the related art, the drawings needed to be used in the description of the embodiments or the related art will be briefly introduced below, and it is obvious that the drawings in the following description are only embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating the steps of a front-end containerization integrated method of an insurance sales system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a method step of a front-end containerization part of an insurance sales system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a front-end containerization apparatus of the insurance sales system of an embodiment of the present application;
fig. 4 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in detail below with reference to the accompanying drawings in combination with specific embodiments.
It should be noted that technical terms or scientific terms used in the embodiments of the present application should have a general meaning as understood by those having ordinary skill in the art to which the present application belongs, unless otherwise defined. The use of "first," "second," and similar terms in the embodiments of the present application is not intended to indicate any order, quantity, or importance, but rather is used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used only to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.
In the related art, the front-end research and development of the individual risk system have the following problems: because the software package paths deployed in the gateway file directory are different, and because the software package paths cannot be standardized, the efficiency is difficult to improve by using an automation tool, and the front-end deployment modes cannot be unified; most of the related technologies are evolved from the traditional integrated system, so that part of resources are definitely divided in function, but are mixed and mutually called in research and development of products, and the problems that a plurality of system static resources are mixed and seriously coupled exist; because a plurality of resources are mixed together, when a certain function needs to be updated, only files related to the function can be updated, and the change of the files can cause the abnormity of other functions, so that the full change cannot be realized; the front-end resources cannot be managed by using a uniform framework due to the large difference between the maintenance mode and the rear end, and the additional management mode brings higher management cost; finally, because application products are mixed together, the deployment modes cannot be unified, and the unified management capability is lacked, the front-end research and development process cannot be brought into an automatic system and can be dissociated outside a continuous delivery integrated system for a long time, so that a front-end page of the individual insurance sales system always has higher deployment risk.
In view of this, an embodiment of the present application provides a front-end containerization method for an individual risk sale system, as shown in fig. 1, including:
step S101, generating a basic mirror image in the individual insurance sales system;
step S102, front-end files are obtained, containerized and description files are generated;
step S103, according to the description file, a new mirror image layer is built on the outer layer of the basic mirror image, and the basic mirror image and the new mirror image layer jointly form a service mirror image;
and step S104, deploying the service mirror image to a container platform to finish the front-end containerization of the individual insurance sales system. The service mirror image is deployed on a container platform, the container platform registers to the existing grid management service registration center, and after the registration is successful, a user request agent can automatically forward the service to the corresponding service and acquire the corresponding static resource file.
It should be noted that, specifically, containerization is a technology for isolating different processes running on a host through a virtualization technology, so as to achieve mutual isolation and mutual non-influence between processes, processes and a host operating system. In embodiments of the present application, container technology is used to achieve isolation and decoupling between resources and between artifacts.
The Image (Image) is a file storage form, similar to the ZIP compressed package, and makes a specific series of files into a single file according to a certain format, so as to facilitate the downloading and use of a user. The basic mirror image described in this embodiment is an operating environment of the front-end file, and may be instantiated as an operating service, and the service is a medium that converts static resources of the front-end file into a microservice and manages the microservice.
According to the method, a basic mirror image is generated in the risk sale system, a front-end file is obtained, the front-end file is containerized and a description file is generated, a new mirror image layer is built on the outer layer of the basic mirror image according to the description file, the basic mirror image and the new mirror image layer jointly form a service mirror image, and then the service mirror image is deployed to a container platform, so that the front-end containerization of the risk sale system is completed. According to the method, the resources with different functions are isolated in a containerization mode, decoupling among the resources is achieved, and therefore the front-end research and development process and the deployment mode are unified, the front-end research and development process can be brought into an automatic system, the front-end research and development process is guaranteed to run stably, and research and development are convenient and fast.
According to the method provided by the embodiment of the application, the service mirror image is issued as a product, deployment personnel do not need to transmit files, deployment work of front-end resources can be completed on the container platform only by receiving the address of the service mirror image, and deployment convenience is guaranteed. The containerized front-end service files and the containerized back-end service files can be accessed into the grid for management in the same way without separate configuration.
In some embodiments, the step S101 includes: and generating the base image in the system image of the individual insurance sales system by using image generation software.
In some embodiments, as shown in fig. 2, the containerizing the front-end file in step S102 includes: step S201, splitting the front-end file according to different functions and packaging the front-end file into a plurality of front-end containers, wherein the front-end containers are isolated from each other. The front-end file after decoupling is completed through containerization can be disassembled into a plurality of different functional projects, each project independently shares independent metadata, configuration information, pipeline tasks, product warehouse areas and the like in the following continuous delivery integrated management system, research and development flows of front-end source codes, resource products, verification products, service mirroring, running services and the like are independently completed, and each functional project can perform version iteration in respective function, so that the front-end research and development process is more free.
In some embodiments, as shown in fig. 2, after the containerizing the front-end file and before the generating the description file, the method further includes: step S202, preprocessing the front-end container, wherein the preprocessing comprises adding a health examination tool into the front-end container. In the continuous delivery integration tool chain, the script execution logic of step S202 is: and detecting a required branch version from the version control system, and preprocessing the source code in the front-end container, wherein the preprocessing can be the modification of the unified logic of the front-end container, such as adding a unified health check function or adding a detection tool.
In specific implementation, the step S202 is implemented by a script in a continuous delivery integrated tool chain, where the continuous delivery integrated tool chain includes a code version control system, a continuous delivery integrated management system, and a product warehouse, that is, a series of interface tools for data collection, statistics, and display; in the continuous delivery integrated management system, the system can form a specific executed task according to a preset template and configuration information of each project, the task can sequentially execute a plurality of stages, each stage comprises a set of scripts, and the conversion from a basic mirror image to a service mirror image is completed by executing script logic. During the in-service use, the configuration information is only input to the system by research and development personnel during research and development, the later execution process is implemented through the rendering of the preset template, the research and development personnel do not need to carry out additional operation, if the content needs to be newly added, only the modification and submission in the script project are needed, the operation stability of the front-end research and development process is further ensured, and the research and development are convenient and fast.
In some embodiments, as shown in fig. 2, the generating the description file in step S102 includes: step S203, generating a plurality of description files and a starting command file which are in one-to-one correspondence with the plurality of front-end containers according to the attribute information and the description information of the plurality of front-end containers, wherein the description files comprise the association information of each front-end container and the basic mirror image; the launch command file is configured to be utilized by the service image to perform a launch. The step S203 is implemented by the same script in the continuous delivery integration tool chain as the step S202, in which the script execution logic of the step S203 is: installing and compiling the front-end container source code, wherein the front-end framework environment control parameters are used to select the corresponding configuration information in the source code to be packaged into the same, so that the generated final product can correctly access the corresponding parameters which will control the front-end logic to use the resources of the corresponding environment, and this step generates an intermediate container which is ready for each base image but isolated from the base image. The script executes the logic and produces description file and starting command file, the said description file is the basis of associating front end container and basic mirror image, the said starting command file is the content that the service mirror image is executed when starting, the script inquires about attribute data and description information of the front end container from the metadata system, combine with the template preserved and produce the description file different because of the service function, and produce the description file in the working directory of the integrated management system of the continuous delivery, prepare for the preparation of the service mirror image finally.
In some embodiments, the step S103 includes: step S301, according to the description file, a plurality of sub-image layers are built on the outer layer of the basic image, and all the sub-image layers jointly form the new image layer. In some embodiments, the step S103 further comprises: and constructing a new mirror image layer on the basic mirror image outer layer by utilizing a continuous delivery integration tool chain. The step S301 is implemented by the same script in the continuous delivery integration tool chain as the step S202, in which the script execution logic of the step S301 is: the system can carry out mirror image construction according to the prepared description file by executing the container packing action, the system can operate according to the description file, a sub-mirror image layer is generated by each operation and accumulated on the upper layer of the basic mirror image, after all layers are completed, the system can construct a service mirror image carrying the content of the front-end container, and the service mirror image can be used for being deployed to a container platform and providing service outwards.
It should be noted that the method of the embodiment of the present application may be executed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene and completed by the mutual cooperation of a plurality of devices. In this distributed scenario, one device of the multiple devices may only perform one or more steps of the method of the embodiment of the present application, and the multiple devices interact with each other to complete the method.
It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments described above and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Based on the same inventive concept, corresponding to the method of any embodiment, the application also provides a front-end containerization device of the individual insurance sales system.
As shown in fig. 3, the front-end containerization apparatus of an insurance sales system comprises:
a generating module 10 configured to generate a base image in the individual insurance sales system;
the containerization module 20 is used for acquiring the front-end file, containerizing the front-end file and generating a description file;
a building module 30 configured to build a new mirror image layer on the outer layer of the base mirror image according to the description file, wherein the base mirror image and the new mirror image layer together form a service mirror image;
a deployment module 40 configured to deploy the service image to a container platform to complete front-end containerization of the individual insurance sales system.
According to the device provided by the embodiment of the application, the basic mirror image is generated in the risk sale system, the front-end file is obtained, the front-end file is containerized and the description file is generated, the new mirror image layer is constructed on the outer layer of the basic mirror image according to the description file, the basic mirror image and the new mirror image layer jointly form the service mirror image, and then the service mirror image is deployed to the container platform so as to complete the front-end containerization of the risk sale system. According to the method, the resources with different functions are isolated in a containerization mode, decoupling among the resources is achieved, and therefore the front-end research and development process and the deployment mode are unified, the front-end research and development process can be brought into an automatic system, the front-end research and development process is guaranteed to run stably, and research and development are convenient and fast.
In some embodiments, the containerization module is further configured to split and package the front-end file into a plurality of front-end containers according to different functions, each of the front-end containers being isolated from each other.
In some embodiments, the containerization module is further configured to generate a plurality of description files corresponding to the plurality of front-end containers one to one according to the attribute information and the description information of the plurality of front-end containers, where the description files include association information of each front-end container and the base image.
In some embodiments, the build module is further configured to build a plurality of sub-image layers on the base image according to the description file, all of the sub-image layers together constituting the new image layer.
In some embodiments, the generation module is further configured to generate the base image in a system image of the individual insurance sales system using image generation software.
In some embodiments, the containerization module is further configured to pre-process the front-end container, the pre-processing including adding a health check tool to the front-end container.
In some embodiments, the containerization module is further configured to containerize the front-end file and generate a boot command file configured to be utilized by the service image to perform a boot.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, the functionality of the various modules may be implemented in the same one or more software and/or hardware implementations as the present application.
The apparatus of the foregoing embodiment is used to implement the corresponding front-end containerization method of the individual insurance sales system in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Based on the same inventive concept, corresponding to any embodiment of the method, the application further provides an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, the method for realizing the individual risk sale system front-end containerization described in any embodiment of the method is implemented.
Fig. 4 is a schematic diagram illustrating a more specific hardware structure of an electronic device according to this embodiment, where the electronic device may include: a processor 410, a memory 420, an input/output interface 430, a communication interface 440, and a bus 450. Wherein processor 410, memory 420, input/output interface 430, and communication interface 440 are communicatively coupled to each other within the device via bus 450.
The processor 410 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.
The Memory 420 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 420 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 420 and called to be executed by the processor 410.
The input/output interface 430 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 440 is used for connecting a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 410, the memory 420, the input/output interface 430, the communication interface 440 and the bus 450, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
The electronic device of the above embodiment is used for implementing the corresponding front-end containerization method of the individual insurance sales system in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Based on the same inventive concept, corresponding to any of the above embodiments, the present application further provides a non-transitory computer readable storage medium storing computer instructions for causing the computer to execute the individual insurance sales system front-end containerization method according to any of the above embodiments.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, for storing information may be implemented in any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the front-end containerization method of the individual insurance sales system according to any of the above embodiments, and have the beneficial effects of corresponding method embodiments, which are not described herein again.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the context of the present application, features from the above embodiments or from different embodiments may also be combined, steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of brevity.
In addition, well-known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown in the provided figures for simplicity of illustration and discussion, and so as not to obscure the embodiments of the application. Furthermore, devices may be shown in block diagram form in order to avoid obscuring embodiments of the application, and this also takes into account the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform within which the embodiments of the application are to be implemented (i.e., specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the application, it should be apparent to one skilled in the art that the embodiments of the application can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative instead of restrictive.
While the present application has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures (e.g., dynamic ram (dram)) may use the discussed embodiments.
The present embodiments are intended to embrace all such alternatives, modifications and variances which fall within the broad scope of the appended claims. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present application are intended to be included within the scope of the present application.
Claims (10)
1. A method for front-end containerization of an individual insurance sales system, comprising:
generating a base image in the individual insurance sales system;
acquiring a front-end file, and containerizing the front-end file to generate a description file;
according to the description file, a new mirror image layer is built on the outer layer of the basic mirror image, and the basic mirror image and the new mirror image layer jointly form a service mirror image;
and deploying the service mirror image to a container platform to finish the front-end containerization of the individual insurance sales system.
2. The front-end containerization method of claim 1, wherein said containerizing said front-end document comprises:
and splitting the front-end file according to different functions and packaging the front-end file into a plurality of front-end containers, wherein each front-end container is isolated from each other.
3. The front-end containerization method of claim 2, wherein the containerizing the front-end file and generating the description file comprises:
and generating a plurality of description files which are in one-to-one correspondence with the plurality of front-end containers according to the attribute information and the description information of the plurality of front-end containers, wherein the description files comprise the association information of each front-end container and the basic mirror image.
4. The front-end containerization method of claim 3, wherein said building a new mirror layer outside said base mirror according to said description file comprises:
and constructing a plurality of sub-mirror image layers on the outer layer of the basic mirror image according to the description file, wherein all the sub-mirror image layers jointly form the new mirror image layer.
5. The individual insurance sales system front-end containerization method of claim 1, wherein generating a base image in the individual insurance sales system comprises:
and generating the base image in the system image of the individual insurance sales system by using image generation software.
6. The front-end containerization method of claim 2, further comprising, after containerizing the front-end file and before generating the description file:
pre-processing the front-end vessel, the pre-processing comprising adding a health check tool to the front-end vessel.
7. The front-end containerization method of claim 1, wherein said containerizing the front-end document and generating the description document further comprises:
containerizing the front-end file and generating a boot command file configured to be utilized by the service image to perform a boot.
8. An individual insurance sales system front-end containerization apparatus, comprising:
a generation module configured to generate a base image in the individual insurance sales system;
the containerization module is used for acquiring the front-end file, containerizing the front-end file and generating a description file;
the construction module is configured to construct a new mirror image layer on the outer layer of the basic mirror image according to the description file, and the basic mirror image and the new mirror image layer jointly form a service mirror image;
a deployment module configured to deploy the service image to a container platform to complete front-end containerization of the individual insurance sales system.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the program.
10. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210228701.5A CN114741155A (en) | 2022-03-09 | 2022-03-09 | Front-end containerization method of individual insurance sales system and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210228701.5A CN114741155A (en) | 2022-03-09 | 2022-03-09 | Front-end containerization method of individual insurance sales system and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114741155A true CN114741155A (en) | 2022-07-12 |
Family
ID=82276152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210228701.5A Pending CN114741155A (en) | 2022-03-09 | 2022-03-09 | Front-end containerization method of individual insurance sales system and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114741155A (en) |
-
2022
- 2022-03-09 CN CN202210228701.5A patent/CN114741155A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101314949B1 (en) | Integration environment generator | |
| CN108279892B (en) | Method, device and equipment for splitting large-scale application service into micro-service | |
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| US20100162230A1 (en) | Distributed computing system for large-scale data handling | |
| CN106610839B (en) | Method for issuing upgrade package, lightweight upgrade method, device and system | |
| CN110780853A (en) | Front end framework, development method, storage medium and electronic device | |
| WO2012000759A1 (en) | Runtime dynamic selection of an application server classloader | |
| CN112256321A (en) | Static library packaging method and device, computer equipment and storage medium | |
| CN111026634A (en) | Interface automation test system, method, device and storage medium | |
| CN100511140C (en) | Method for script language calling multiple output parameter interface by component software system | |
| CN111399840A (en) | Module development method and device | |
| CN113504902A (en) | Industrial APP integrated development system and related equipment | |
| KR20150061203A (en) | Method for providing embedded software development tools for supporting embedded software development environment based on native building and apparatus thereof | |
| CN103678098A (en) | HADOOP program testing method and system | |
| CN111651219A (en) | Method and equipment for managing multi-module project configuration file | |
| CN112379969A (en) | Continuous integrated delivery method based on containerized application and related equipment | |
| CN108334784A (en) | A kind of vulnerability scanning method and apparatus | |
| CN113127136B (en) | Docker mirror image generation method and device, storage medium and electronic equipment | |
| CN115576699A (en) | Data processing method, data processing device, AI chip, electronic device and storage medium | |
| CN110795143B (en) | Method, apparatus, computing device, and medium for processing functional modules | |
| CN112835587B (en) | Compiling integration method and device | |
| CN110851211A (en) | Method, apparatus, electronic device, and medium for displaying application information | |
| CN111324395B (en) | Calling method, device and computer readable storage medium | |
| CN116227625A (en) | Intelligent model development method, medium and equipment | |
| CN114741155A (en) | Front-end containerization method of individual insurance sales system and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |