CN113641454B - A business application deployment method, device, electronic equipment and storage medium - Google Patents

Abstract

The application provides a service application deployment method, a service application deployment device, electronic equipment and a storage medium. The method comprises the following steps: acquiring demand information and use area information of a target service application; generating a container mirror image of the target business application according to the demand information; determining first cloud equipment from a preset network system according to the using area information, wherein the preset network system comprises a plurality of cloud equipment; determining cloud equipment adjacent to the first cloud equipment in the preset network system as second cloud equipment; deploying the container image in the second cloud device. According to the method and the device for the cloud service application, the target service application can be deployed to cloud equipment which is used by a user in advance, so that the problem that service interruption time is long due to temporary migration of the service application when the user moves is avoided, and user experience is improved.

Description

A business application deployment method, device, electronic equipment and storage medium

technical field

The present application relates to communication technologies, and in particular to a service application deployment method, device, electronic equipment and storage medium.

Background technique

At present, the scale of business applications has become larger and larger, and many business applications need to cover the whole world, the whole country, and the whole domain. In order to improve the experience of using business applications, most business applications are deployed on cloud platforms that are relatively close to users, and are deployed in different domains according to the domain of the user's network.

However, the edge cloud has limited capabilities and cannot complete all computing power tasks, or due to the movement of users, computing power tasks need to be migrated from one location to a closer location after the user moves.

In related technologies, the solution to the above problems is usually solved by migration, but this method will cause service interruption for a long time.

Contents of the invention

The present application provides a service application deployment method, device, electronic equipment and storage medium to solve the problem of long service interruption caused by temporary relocation of service applications when users move.

In the first aspect, the embodiment of the present application provides a business application deployment method, the method includes:

Obtain the demand information and usage area information of the target business application;

generating a container image of the target business application according to the requirement information;

determining a first cloud device from a preset network system according to the use area information, where the preset network system includes a plurality of cloud devices;

determining a cloud device adjacent to the first cloud device in the preset network system as a second cloud device;

Deploy the container image on the second cloud device.

In an optional implementation manner, the plurality of cloud devices include fog cloud devices and edge cloud devices, and the generating the container image of the target business application according to the demand information includes:

A first container image of a type corresponding to the fog cloud device and a second container image of a type corresponding to the edge cloud device are generated according to the requirement information.

In an optional implementation manner, deploying the container image in the second cloud device includes:

If the second cloud device is a fog cloud device, deploying the first container image to the second cloud device;

If the second cloud device is an edge cloud device, deploying the second container image to the second cloud device.

In an optional implementation manner, the preset network system further includes a central cloud device connected to the second cloud device, and the method further includes:

storing the first container image and the second container image in an image library of the central cloud device.

In an optional implementation manner, the first container image is a docker type container image, and the second container image is a k8s type container image.

In an optional embodiment, the method also includes:

If it is detected that the target service application is transferred out from the second cloud device, the container image in the second cloud device is destroyed.

In an optional implementation manner, the requirement information includes container requirement information and container arrangement information.

In the second aspect, the embodiment of the present application provides a service application deployment device, the device includes:

An information acquisition module, configured to acquire demand information and use area information of target business applications;

A container image generating module, configured to generate a container image of the target business application according to the requirement information;

A first cloud device determining module, configured to determine a first cloud device from a preset network system according to the use area information, and the preset network system includes a plurality of cloud devices;

The second cloud device determination module determines a cloud device adjacent to the first cloud device in the preset network system as a second cloud device;

A deployment module, configured to deploy the container image in the second cloud device.

In an optional implementation manner, the container image generation module is specifically used for:

A first container image of a type corresponding to the fog cloud device and a second container image of a type corresponding to the edge cloud device are generated according to the requirement information.

In an optional implementation manner, the deployment module includes:

A first deployment unit, configured to deploy the first container image to the second cloud device if the second cloud device is a fog cloud device;

The second deployment unit is configured to deploy the second container image to the second cloud device if the second cloud device is an edge cloud device.

In an optional implementation manner, the preset network system further includes a central cloud device connected to the second cloud device, and the device further includes:

A storage module, configured to store the first container image and the second container image in an image library of the central cloud device.

In an optional implementation manner, the first container image is a docker type container image, and the second container image is a k8s type container image.

In an optional embodiment, the device also includes:

A destroying module, configured to destroy the container image in the second cloud device if it is detected that the target business application is transferred out from the second cloud device.

In an optional implementation manner, the requirement information includes container requirement information and container arrangement information.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor;

a memory for storing said processor-executable instructions;

Wherein, the processor is configured to execute the method provided in the foregoing embodiments.

In a fourth aspect, the embodiments of the present application provide a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when executed by a processor, the computer-executable instructions are used to implement the methods provided in the foregoing embodiments.

In a fifth aspect, the embodiments of the present application provide a computer program product, where the computer program product includes a computer program, and when the computer program is executed by a processor, the method provided in the foregoing embodiments is implemented.

The business application deployment method, device, electronic device, and storage medium provided by the present application acquire the demand information and use area information of the target business application, generate a container image of the target business application according to the demand information, and then determine the first cloud device from a preset network system according to the use area information. The preset network system includes a plurality of cloud devices, so that the cloud device being used by the user can be accurately determined according to the area where the user is located. Then, the cloud device adjacent to the first cloud device in the preset network system is determined as the second cloud device, and the container image is deployed on the second cloud device. Since the second cloud device is adjacent to the first cloud device, when the user moves and the target business application cannot be used on the first cloud device, the container image of the target business application deployed in advance in the second cloud device can be directly used, which ensures that the target business will not be interrupted for a long time during the user's movement, and effectively improves user experience.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

FIG. 1 is a schematic diagram of an application environment of a service application deployment method provided in an embodiment of the present application;

FIG. 2 is a schematic flow diagram of a service application deployment method provided in an embodiment of the present application;

FIG. 3 is a schematic flowchart of another service application deployment method provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of another application environment of the service application deployment method provided by the embodiment of the present application;

FIG. 5 is a schematic structural diagram of a service application deployment device provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

By means of the above drawings, specific embodiments of the present application have been shown, which will be described in more detail hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of the application in any way, but to illustrate the concept of the application for those skilled in the art by referring to specific embodiments.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

At present, the scale of business applications has become larger and larger, and many business applications need to cover the whole world, the whole country, and the whole domain. In order to improve the user experience of business applications, most business applications are deployed on the cloud or edge that is relatively close to the user, and are deployed in different domains according to the domain of the user's network.

However, after all, the edge cloud has limited capabilities, and it is impossible to complete the computing power tasks for all business applications. Moreover, due to the movement of users, the computing power tasks for business applications need to be migrated from one location to a location closer to the user after moving.

In related technologies, most of the current solutions are to deploy a set of business applications in the target area where the user moves, but the edge cloud has limited capabilities and it is impossible to deploy them all. Or it can be solved by migration. Although there are many migration methods, the migration takes a certain amount of time to complete, so the migration process may cause business interruption for a long time.

The embodiment of the present application provides a service application deployment method, device, electronic device, and storage medium, aiming to solve the above technical problems in the prior art. The service application deployment method, device, electronic device, and storage medium provided in the embodiment of the present application can deploy the target service application to the cloud device that the user will use in advance, avoiding the long service interruption time caused by the temporary migration of the service application when the user moves, and improving the user experience.

The technical terms involved in the embodiment of this application are explained below:

Image: Image is a collection of read-only layers. It is a unified perspective of a bunch of read-only layers. Except for the bottom layer, each layer points to its parent layer. It is equivalent to a root file system. Mirroring is a special file system. In addition to providing programs, libraries, resources, configuration and other files required for container runtime, it also contains some configuration parameters (such as anonymous volumes, environment variables, users, etc.) prepared for runtime. Images do not contain any dynamic data, and their contents are not changed after they are built.

Container: A container is a running instance of an image, the difference is that it has an additional writable layer. The relationship between the image (Image) and the container (Container) is like the class and instance in object-oriented programming. The image is a static definition, and the container is the entity of the image runtime. Containers can be created, started, stopped, deleted, paused, etc. The process in the container runs in an isolated environment, and when used, it seems to be operating under a system independent of the host. This feature makes container-encapsulated applications more secure than running directly on the host.

Repository: It is used to store images. After the image is built, it can be easily run on the current host machine. However, if we need to use this image on other servers, we need a centralized storage and distribution image service. DockerRegistry is such a service.

A Docker Registry can contain multiple warehouses (Repository); each warehouse can contain multiple tags (Tag); each tag corresponds to a mirror image.

Tag (Tag): Mark the local image and put it into a certain warehouse.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below in conjunction with the accompanying drawings.

FIG. 1 is an application environment of a service application deployment method provided by an embodiment of the present application. As shown in FIG. 1 , the application environment may include: a user service system, a drift management system, and a network system. Wherein, the network system may include multiple cloud devices (hereinafter referred to as clouds), and the multiple cloud devices may be multiple central clouds (such as central cloud 1, central cloud n, etc.), multiple fog clouds (such as fog cloud 1, fog cloud n, etc.), and multiple edge clouds (such as edge cloud 1, edge cloud m, edge cloud n, etc.).

Among them, the user service system can establish communication links with the drift management system, the drift management system can respectively establish communication links with multiple central clouds, each central cloud can establish communication links with multiple fog clouds, and each fog cloud can respectively establish communication links with multiple edge clouds.

Wherein, the user service system is used to receive the task information for the target service submitted by the user, and process the task information submitted by the user and send it to the drift management system.

Among them, the drift management system is used to receive task information processed by the user service system, and send drift tasks to cloud devices (such as central cloud, fog cloud, and edge cloud) according to the task information, so as to deploy tasks corresponding to target applications in corresponding cloud devices.

Wherein, multiple cloud devices in the network system may be pre-divided into multiple different areas. Each of the multiple regions may correspond to at least one cloud device.

Optionally, the user service system and drift management system may be server equipment, electronic equipment, terminal equipment, and the like.

Fig. 2 is a schematic flow diagram of a service application deployment method provided in the embodiment of the present application. As shown in Fig. 2, the method provided in the present embodiment includes:

101. Obtain demand information and usage area information of a target business application.

Exemplarily, the subject of execution of this embodiment may be an electronic device, or a terminal device, or other apparatuses or devices capable of executing this embodiment, without limitation. In this embodiment, the execution subject is described as an electronic device, which may specifically be the user service system in FIG. 1 .

In some embodiments, the user can access the user service system through the user terminal, and submit the demand information and the use area information about the target business application to the user service system, and when the customer service system receives the demand information and the user use area information, the demand information and the use area information of the target business application are obtained.

Wherein, the use area information may refer to the use area range of the target service application.

In some implementations, the user terminal can detect the location information of the user when the user uses the target service application, and upload the detected location information to the user service system, and the user service system can determine the use area information of the target service application according to the location information.

Wherein, the requirement information may include container requirement information, container orchestration information, and the like. Wherein, the container requirement information may include parameter information for establishing a container image, such as required parameters of nginx, mysql, tomcat, postgres, and debian images. As an example, container requirement information may be shown in Table 1:

Table 1

REPOSITORY TAG size nginx latest 359MB mysql 5.7 448MB Tomcat latest 647MB Postgres latest 313MB Debian latest 114MB

According to Table 1, it can be seen that the parameters of the image may include a warehouse (REPOSITORY), a tag (TAG), a size (size), and so on.

As an example, the orchestration information is as follows:

It can be seen that the orchestration information may include hostname (hostname), mapped ports (ports), network (networks) and other information.

102. Generate a container image of the target business application according to the requirement information.

In some implementations, the customer service system can generate the container image of the target business application according to the generated container requirement information and container orchestration information of the target business application.

Following the above example, the user service system can process the requirement information, and extract the general field information of container requirement information and container orchestration information from the requirement information. Then use the extracted general information to generate docker and k8s type container images, and put the container images in the image library of the central cloud, so that when the demand is generated, the image can be directly pulled.

Exemplarily, the image parameters required for extraction are mysql and tomcat. The general information of the extracted arrangement information is as follows:

webapp

-1216:80

-1217:443

103. Determine a first cloud device from a preset network system according to the use area information, where the preset network system includes multiple cloud devices.

In some implementations, the mapping relationship between multiple regions and multiple cloud devices is pre-stored in the user service system, wherein each region can correspond to at least one cloud device. Exemplarily, the mapping relationship between multiple regions and multiple cloud devices can be as shown in Table 2:

Table 2

It can be seen from Table 2 that after the use area information is determined, the corresponding cloud device can be found according to Table 2. For example, when the user service system determines that the use area information is the area range b, fog cloud n can be determined from the preset network system as the first cloud device.

104. Determine a cloud device adjacent to the first cloud device in the preset network system as the second cloud device.

In some implementations, the network topology corresponding to the preset network system may be pre-stored in the user service system, and the distribution of multiple cloud devices in the preset network system may be determined according to the network topology. Exemplarily, the specific distribution of multiple cloud devices may be as shown in FIG. 1 . The user service system may determine a cloud device adjacent to the first cloud device in the network topology as the second cloud device. Optionally, a cloud device closest to the first cloud device in the preset network system may be determined as a cloud device adjacent to the first cloud device.

As an example, please refer to Figure 1 again. For example, the first cloud device is fog cloud n, and the user service system can deploy the container image of the target business application in fog cloud n. After the deployment of fog cloud n is completed, the user service system checks the usage area information submitted by the user. Specifically, it can be the application area.

105. Deploy the container image on the second cloud device.

In some implementations, if the user switches to the area corresponding to the first cloud device, the user service system can issue a drift task to the drift management system to deploy the container image of the target business application required by the user in the second cloud device adjacent to the first cloud device. So that the second cloud device is ready to meet the computing power task related to the target business.

In this embodiment, by acquiring demand information and usage area information of the target business application, generating a container image of the target business application according to the demand information, and then determining the first cloud device from a preset network system according to the usage area information, the preset network system includes multiple cloud devices, so that the cloud device being used by the user can be accurately determined according to the area where the user is located. Then, determine the cloud device adjacent to the first cloud device in the preset network system as the second cloud device, and deploy the container image on the second cloud device. Since the second cloud device is adjacent to the first cloud device, when the user moves and the target business application cannot be used on the first cloud device, the container image of the target business application deployed in advance in the second cloud device can be directly used, which ensures that the target business will not be interrupted for a long time during the user's movement, and effectively improves user experience.

Fig. 3 is a schematic flow chart of another business application deployment method provided in the embodiment of the present application. As shown in Fig. 3, the method provided in the present embodiment includes:

201. Acquire demand information and usage area information of a target service application.

202. Generate a container image of the target service application according to the requirement information.

Wherein, for specific implementation manners of steps 201 to 202, reference may be made to steps 101 to 102, so details are not repeated here.

In some implementations, the multiple cloud devices include fog cloud devices and edge cloud devices, and the specific implementation of step 102 includes: generating a first container image corresponding to the fog cloud device and a second container image corresponding to the edge cloud device according to the demand information.

Optionally, the first container image is a docker type container image, and the second container image is a k8s type container image.

Among them, the docker type container image is used to deploy on the fog cloud device, and the k8s type container image is used to deploy on the edge cloud device.

In some implementations, the method further includes: storing the first container image and the second container image in an image library of the central cloud device.

As an example, for example, the user service system can deploy the container image required by the user to the edge cloud or the fog cloud according to the container requirement information (also referred to as image information hereinafter) according to the user's business requirements. At the same time, if the image library of the central cloud device does not have this version of the container image, the container image deployed by the user can be stored in the image library.

203. Determine a first cloud device from a preset network system according to the use area information, where the preset network system includes multiple cloud devices.

204. Determine a cloud device adjacent to the first cloud device in the preset network system as the second cloud device.

In some implementations, the user service system may determine, according to the network topology of the preset network system, a cloud device whose distance from the first cloud device in the preset network system does not exceed a specified distance as a cloud device adjacent to the first cloud device, and as a second cloud device.

In some other implementations, the user service system may determine, according to the network topology of the preset network system, a specified number of cloud devices in the preset network system that are closest to the first cloud device as cloud devices adjacent to the first cloud device, and as the second cloud device. In order to determine the second cloud device more flexibly.

205. Deploy the container image on the second cloud device.

In some implementations, the specific implementation of step 205 includes: if the second cloud device is a fog cloud device, deploying the first container image to the second cloud device. If the second cloud device is an edge cloud device, deploy the second container image to the second cloud device, so as to ensure that when deploying the container image, an appropriate container image can be deployed according to the type of the cloud device.

206. If it is detected that the target business application is transferred out from the second cloud device, destroy the container image in the second cloud device.

As an example, for example, if the second cloud device is a fog cloud n, then the container image of the target business application can be deployed on the fog cloud n, and the fog cloud n is a docker container, and the docker container required by the user is deployed. Due to the small scale of the edge cloud, there are few deployment services and it can only be deployed when needed. Therefore, when the user switches out of the fog cloud n, for example, the user moves outside the area corresponding to the fog cloud n, and the fog cloud n is no longer the adjacent cloud of the user's current cloud, the fog cloud n can destroy the container just deployed, because this computing power task will not come for the time being. Wherein, the adjacent cloud of the cloud where the user is currently located refers to a cloud device adjacent to the cloud device where the user is currently located.

As another example, as shown in FIG. 4, the container image of the target business application can be transferred as the user moves. For example, when the user just uses the container image of the target business application in the fog cloud n, the container image can be deployed in advance in the adjacent edge cloud n of the fog cloud n. When the user now transfers to use the container image of the target business application in the edge cloud n, the container image of the target business application can be destroyed from the fog cloud n, and the container image can be deployed in advance in the edge cloud m adjacent to the edge cloud n, so as to prepare for the computing tasks of the cloud equipment that the user may use. Thus avoiding the interruption of target business use due to temporary migration.

In this embodiment, if it is detected that the target business application is transferred from the second cloud device, the container image in the second cloud device is destroyed, so that the space of the second cloud device can be automatically cleared, so that it can receive and deploy normally in the future.

Fig. 5 is a schematic structural diagram of a service application deployment device provided in an embodiment of the present application. As shown in Fig. 5, the device includes:

The information acquisition module 31 is configured to acquire demand information and usage area information of the target business application.

The container image generating module 32 is configured to generate a container image of a target business application according to requirement information.

The first cloud device determining module 33 is configured to determine the first cloud device from a preset network system according to the use area information, and the preset network system includes a plurality of cloud devices.

The second cloud device determining module 34 determines a cloud device adjacent to the first cloud device in the preset network system as the second cloud device.

The deployment module 35 is configured to deploy the container image in the second cloud device.

In some implementations, the container image generation module 32 is specifically used for:

Generate the first container image corresponding to the fog cloud device and the second container image corresponding to the edge cloud device according to the demand information.

In some embodiments, the deployment module 35 includes:

The first deployment unit is configured to deploy the first container image to the second cloud device if the second cloud device is a fog cloud device.

The second deployment unit is configured to deploy the second container image to the second cloud device if the second cloud device is an edge cloud device.

In some implementations, the preset network system also includes a central cloud device connected to the second cloud device, and the device also includes:

The storage module is configured to store the first container image and the second container image in the image repository of the central cloud device.

In some implementations, the first container image is a docker-type container image, and the second container image is a k8s-type container image.

In some embodiments, the device also includes:

The destruction module is used to destroy the container image in the second cloud device if it is detected that the target business application is transferred out from the second cloud device.

In some implementations, the requirement information includes container requirement information and container orchestration information.

Exemplarily, this embodiment may refer to the foregoing method embodiment, and its principles and technical effects are similar, so details are not repeated here.

FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As shown in FIG. 6 , the electronic device includes a memory 43 and a processor 42 .

The memory 43 is used for storing instructions executable by the processor 42 .

The processor 42 is configured to execute the methods provided in the foregoing embodiments.

The electronic device also includes a receiver 40 and a transmitter 41 . The receiver 40 is used to receive instructions and data sent by the external device, and the transmitter 41 is used to send instructions and data to the external device.

Wherein, the electronic device may be a mobile terminal, a computer, a tablet computer or the like.

Specifically, the electronic device may further include one or more of the following components: a processing component, a power supply component, a multimedia component, and an input/output (I/O) interface. The processing component may be equivalent to the processor 42 of the above-mentioned embodiment,

The processing components typically control the overall operations of the electronic device, such as those associated with display and recording operations. The processing component may include one or more processors to execute instructions to complete all or part of the steps of the above method. Additionally, a processing component may include one or more modules to facilitate interaction between the processing component and other components. For example, the processing component may include a multimedia module to facilitate interaction between the multimedia component and the processing component.

The memory is configured to store various types of data to support operations at the electronic device. Examples of such data include, among other things, instructions for any application or method operating on the electronic device. The memory can be implemented by any type of volatile or non-volatile memory devices or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, etc.

Power components provide power to various components of electronic equipment. Power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic devices.

The multimedia component includes a screen providing an output interface between said electronic device and a user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action.

The I/O interface provides an interface between the processing component and the peripheral interface module, and the above peripheral interface module can be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as a memory including instructions, which can be executed by a processor of an electronic device to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the methods provided in the foregoing embodiments when executed by a processor.

An embodiment of the present application provides a computer program product, and the computer program product includes: a computer program, the computer program is stored in a readable storage medium, at least one processor of the electronic device can read the computer program from the readable storage medium, and at least one processor executes the computer program so that the electronic device executes the solution provided by any of the above embodiments.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application intends to cover any modification, use or adaptation of the application, and these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application. The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A business application deployment method, characterized in that, comprising: Obtain the demand information and usage area information of the target business application; generating a container image of the target business application according to the requirement information; determining a first cloud device from a preset network system according to the use area information, where the preset network system includes a plurality of cloud devices; determining a cloud device adjacent to the first cloud device in the preset network system as a second cloud device; Deploying the container image in the second cloud device; When the user moves and the target service application cannot be used on the first cloud device, the container image of the target service application deployed in advance in the second cloud device is used. 2. The method according to claim 1, wherein the multiple cloud devices include fog cloud devices and edge cloud devices, and generating the container image of the target business application according to the demand information includes: A first container image of a type corresponding to the fog cloud device and a second container image of a type corresponding to the edge cloud device are generated according to the demand information. 3. The method according to claim 2, wherein deploying the container image in the second cloud device comprises: If the second cloud device is a fog cloud device, deploying the first container image to the second cloud device; If the second cloud device is an edge cloud device, deploying the second container image to the second cloud device. 4. The method according to claim 2, wherein the preset network system further comprises a central cloud device connected to the second cloud device, and the method further comprises: storing the first container image and the second container image in an image library of the central cloud device. 5. The method according to claim 2, wherein the first container image is a docker type container image, and the second container image is a k8s type container image. 6. The method according to any one of claims 1-5, wherein the method further comprises: If it is detected that the target service application is transferred out from the second cloud device, the container image in the second cloud device is destroyed. 7. The method according to any one of claims 1-5, wherein the requirement information includes container requirement information and container arrangement information. 8. A service application deployment device, characterized in that the device comprises: An information acquisition module, configured to acquire demand information and use area information of target business applications; A container image generating module, configured to generate a container image of the target business application according to the requirement information; A first cloud device determining module, configured to determine a first cloud device from a preset network system according to the use area information, and the preset network system includes a plurality of cloud devices; The second cloud device determination module determines a cloud device adjacent to the first cloud device in the preset network system as a second cloud device; a deployment module, configured to deploy the container image in the second cloud device; When the user moves and the target service application cannot be used on the first cloud device, the container image of the target service application deployed in advance in the second cloud device is used. 9. An electronic device, comprising: a memory and a processor; a memory for storing said processor-executable instructions; Wherein, the processor is configured to execute the method according to any one of claims 1-7. 10. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the method according to any one of claims 1-7 when executed by a processor.