CN113225576B - Service migration system and method based on live broadcast platform edge computing scene - Google Patents
Service migration system and method based on live broadcast platform edge computing scene Download PDFInfo
- Publication number
- CN113225576B CN113225576B CN202110482788.4A CN202110482788A CN113225576B CN 113225576 B CN113225576 B CN 113225576B CN 202110482788 A CN202110482788 A CN 202110482788A CN 113225576 B CN113225576 B CN 113225576B
- Authority
- CN
- China
- Prior art keywords
- task
- target
- module
- service
- application deployment
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
- H04N21/2187—Live feed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
- H04N21/2405—Monitoring of the internal components or processes of the server, e.g. server load
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
Abstract
The embodiment of the invention discloses a service migration system and method based on a live broadcast platform edge computing scene. The system comprises: the task triggering module is used for responding to task triggering operation to generate a target task; the task management module is used for carrying out traffic shielding processing on an initial server corresponding to the target task and sending the target task to the task execution module if the target task is judged to belong to the service migration task; the task execution module is used for acquiring service metadata corresponding to the target task on the initial server and performing starting and application deployment processing on a target server corresponding to the target task; and the checking module is used for carrying out consistency checking on the application deployment information on the initial server and the target server so as to realize service migration. According to the technical scheme of the embodiment of the invention, the service migration can be automatically carried out in the edge computing scene of the live broadcast platform, the time spent on the service migration is reduced, and the service migration efficiency is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a service migration system and method based on a live broadcast platform edge computing scene.
Background
At present, service migration in the industry generally aims at a short connection service scene, that is, obvious service influence cannot be generated by instant start-stop switching of flow, application deployment is generally central, and service deployment management follows a unified specification, so migration operation only needs to manually deploy peer standard service directly in a new central machine room, and then load balancing scheduling is switched.
However, in the live broadcast platform edge computing scenario, application deployment is changed from an original central type to a distributed type, each edge service node integrates computing power of a class center, live broadcast applications are closer to users, more stable and guaranteed services can be provided, and corresponding service deployment becomes scattered. For example, the original services are uniformly deployed in the same central machine room, and are now distributed to edge single-line machine rooms of a plurality of different manufacturers, and the applications deployed on different nodes in different machine rooms are different. Therefore, when service migration is required, there is a great risk of operation in implementing large-scale service change by manual operation. Moreover, the live application service is basically a long connection service, and if the service is roughly unloaded, a great amount of problems of blockage, screen blackness and the like are caused to the live user. Therefore, service migration in the live platform edge computing scene becomes an important problem to be solved urgently.
Disclosure of Invention
The embodiment of the invention provides a service migration system and method based on a live broadcast platform edge computing scene, which are used for realizing automatic service migration under the live broadcast platform edge computing scene, reducing the time spent on service migration and improving the service migration efficiency.
In a first aspect, an embodiment of the present invention provides a service migration system based on a live platform edge computing scenario, including: the system comprises a task triggering module, a task management module, a flow scheduling module, a task execution module and a verification module;
the task triggering module is used for responding to task triggering operation to generate a target task and sending the target task to the task management module;
the task management module is used for carrying out traffic shielding processing on an initial server corresponding to the target task and sending the target task to the task execution module if the target task is judged to belong to the service migration task;
the task execution module is used for acquiring service metadata corresponding to the target task on the initial server and performing starting and application deployment processing on a target server corresponding to the target task according to the service metadata;
and the checking module is used for carrying out consistency checking on the application deployment information on the initial server and the target server so as to realize service migration.
Optionally, the task triggering module is specifically configured to:
generating a target task in response to the operation of submitting business requirements by a system background; and/or
Responding to the trigger operation of an API authentication interface provided externally, and generating a target task; and/or
Responding to a timed task triggering operation of a task management module in a specific scene to generate a target task;
when the target task is a service migration task, the target task comprises migration range information; the migration range information includes a designated machine room, a designated service, or a designated IP address.
Optionally, the task execution module is specifically configured to:
according to the service metadata corresponding to the target task, starting up a target server corresponding to the target task, and determining whether each target server is started up successfully;
carrying out application deployment operation on the target server which is started successfully, and calling a verification module to carry out consistency verification on the deployed application;
and if the target server with the failed boot-up exists, generating a boot-up failure record, and triggering the target server with the failed boot-up to carry out the boot-up operation again.
Optionally, the task execution module performs parallel application deployment operation on the multiple destination servers by constructing a parallel pool.
Optionally, the task execution module sets the number of concurrent deployment tasks and the task timeout time, and is specifically configured to:
when the parallel application deployment operation is carried out on the target servers with the quantity of the concurrent deployment tasks according to the parallel pool, the state query is carried out on the application deployment tasks of the target servers at intervals of first preset time;
if the target application deployment task which fails to be deployed is inquired, triggering the retry operation of the target application deployment task;
if the application deployment task which is successfully deployed is inquired, triggering to process the application deployment task which is not processed;
and the first preset time is less than the task timeout time.
Optionally, the verification module is specifically configured to:
carrying out consistency check on the application deployment information of the initial server and the target server;
if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server;
carrying out consistency check on the new application deployment information of the target server, and triggering secondary data check operation on the target server if the check result is inconsistent;
if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server at intervals of preset duration;
and if the verification result is consistent, calling the flow scheduling module to start the application deployed on the target server, and triggering the application task corresponding to the initial server to exit at fixed time.
Optionally, the method further includes:
and the storage module is used for acquiring the service metadata corresponding to the target task from the task execution module, converting the service metadata into corresponding protocol data and performing local storage and/or remote Redis storage.
Optionally, the task management module is further configured to:
if the target task belongs to the task of quitting the application service, calling a task execution module to carry out application unloading and shutdown operations on the initial server corresponding to the target task;
and if the target task belongs to the deployment retry task, calling the task execution module to perform application deployment retry operation on the target server corresponding to the target task.
Optionally, the method further includes:
the notification module is used for generating a corresponding abnormal starting-up notification message according to the starting-up failure record;
generating a corresponding deployment abnormity notification message according to the failed application deployment information;
generating corresponding scheduling exception notification messages according to the flow shielding failure information or the application starting failure information;
and sending the abnormal notification message to a manager.
In a second aspect, an embodiment of the present invention further provides a service migration method based on a live platform edge computing scenario, which is applied to a service migration system based on a live platform edge computing scenario provided in any embodiment of the present invention, and includes:
generating a target task in response to task triggering operation through a task triggering module, and sending the target task to a task management module;
through the task management module, if the target task is judged to belong to the service migration task, the scheduling flow scheduling module performs flow shielding processing on an initial server corresponding to the target task and sends the target task to the task execution module;
acquiring service metadata corresponding to a target task on an initial server through a task execution module, and starting and deploying applications of a target server corresponding to the target task according to the service metadata;
and carrying out consistency check on the application deployment information on the initial server and the target server through a check module so as to realize service migration.
According to the technical scheme of the embodiment of the invention, a task trigger module of the system responds to task trigger operation to generate a target task; if the task management module judges that the target task belongs to the service migration task, the scheduling flow scheduling module performs flow shielding processing on an initial server corresponding to the target task and sends the target task to the task execution module; the task execution module acquires service metadata corresponding to the target task on the initial server, and performs starting and application deployment processing on a target server corresponding to the target task according to the service metadata; the verification module is used for carrying out consistency verification on the application deployment information on the initial server and the target server to realize service migration, the problem that operation risk hidden danger exists in service migration in a live broadcast platform edge computing scene through manual operation in the prior art is solved, automatic service migration in the live broadcast platform edge computing scene is realized, time spent in service migration is reduced, and service migration efficiency is improved.
Drawings
Fig. 1a is a schematic structural diagram of a service migration system based on a live platform edge computing scenario in an embodiment of the present invention;
FIG. 1b is a basic architecture diagram of a service migration system according to a first embodiment of the present invention;
fig. 2a is a schematic structural diagram of a service migration system based on a live platform edge computing scenario according to a second embodiment of the present invention;
fig. 2b is a flow chart of service migration based on a live platform edge computing scenario in the second embodiment of the present invention;
fig. 3 is a flowchart of a service migration method based on a live platform edge computing scenario in the third embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1a is a schematic structural diagram of a service migration system based on a live broadcast platform edge computing scenario in an embodiment of the present invention, which may be applied to a case of automatically performing service migration in a live broadcast platform edge computing scenario, and the system may be integrated in a device providing service migration, for example, a central control server. As shown in fig. 1a, the system comprises: a task triggering module 110, a task management module 120, a traffic scheduling module 130, a task execution module 140, and a verification module 150;
the task triggering module 110 is configured to generate a target task in response to a task triggering operation, and send the target task to the task management module 120;
the task management module 120 is configured to, if it is determined that the target task belongs to the service migration task, perform traffic shielding processing on the initial server corresponding to the target task by the scheduling traffic scheduling module 130, and send the target task to the task execution module 140;
the task execution module 140 is configured to obtain service metadata corresponding to the target task on the initial server, and perform startup and application deployment processing on the target server corresponding to the target task according to the service metadata;
the verification module 150 is configured to perform consistency verification on the application deployment information on the initial server and the destination server, so as to implement service migration.
In this embodiment, since service deployment in the edge computing scenario of the live broadcast platform is relatively dispersed, the service operation management cost of operation and maintenance is also high. Service migration may be triggered for a variety of reasons throughout the life of the service. For example, edge room manufacturer share adjustment triggered by cost optimization, same/cross room service migration triggered by network transformation and upgrade, single/multipoint service shielding migration triggered by problem and fault, room service migration triggered by manufacturer model upgrade, and the like.
Optionally, the task triggering module 110 is specifically configured to: generating a target task in response to the operation of submitting business requirements by a system background; and/or generating a target task in response to a trigger operation on an externally provided API authentication interface; and/or generating a target task in response to a timed task triggering operation of the task management module in a specific scene; when the target task is a service migration task, the target task comprises migration range information; the migration range information includes a designated machine room, a designated service, or a designated IP address.
In this embodiment, the task triggering module 110 is a task producer, and can issue tasks such as service migration and service exit as required. As shown in fig. 1b, the task triggering module 110 can support three types of task issuing, wherein, in one of the three types of task issuing, a system background submits a service requirement to trigger task issuing; for example, a user clicks a corresponding service migration option on a provided service management page, a service migration request is submitted to a system background, and a task triggering module generates a target task corresponding to the request. Secondly, the task can be triggered and issued through an externally provided API authentication interface; for example, when other departments or enterprises call an externally provided API authentication interface to request for specified service migration, the task triggering module may generate a corresponding target task. Thirdly, a task is triggered and issued by the task management module 120 at a fixed time under a specific scene; for example, if the task management module 120 is preset in the time period with a small flow rate at 1-3 am, and the task is triggered to be issued by submitting a service requirement through a system background or by triggering the task to be issued through an externally provided API authentication interface, the task triggering module may generate a corresponding target task in response to the task triggering operation.
In this embodiment, the task triggering module 110 may support highly customized task triggering according to migration requirements of a machine room, a service module, an IP address, and the like. That is, the migration range information of the service may be included in the service migration task according to the relevant selection when the service migration is triggered, so as to instruct to perform service migration on all servers of a certain computer room, or to perform migration on the service related to a certain service, or to perform server migration on the server corresponding to a certain IP address, and so on, thereby satisfying the personalized scenario of service application and migration on the edge computing line.
In this embodiment, the task management module 120 is a core function module of service migration, is a consumer of a task, that is, a function execution module, and is an organization tandem person of the whole migration process, and basically has an interactive behavior with each of the other modules, and receives state feedback information from each module, so as to decide a next step behavior according to the feedback information and trigger an exception notification message as needed, as shown in fig. 1 b.
In this embodiment, the task management module 120 may receive, in real time, tasks such as service migration, service deployment retry, service exit and the like sent by the task trigger module 110, and because the processing flow of each task is different, the task management module 120 needs to determine the type of the task first. If the task belongs to the service migration type, the scheduling traffic scheduling module 130 performs traffic shielding processing on an initial server corresponding to the task, that is, a server to be subjected to service migration, and sends the task to the task execution module 140 for processing.
The flow masking means stopping accessing new flow and waiting for the current flow to be cleared. Migration operations generally involve multiple processes of power-on, power-off, deployment, uninstallation, verification, rollback, and recovery observation.
In this embodiment, considering that the live broadcast service is basically a long connection service, in order to reduce the influence caused by offline of the initial server to be migrated, as shown in fig. 1b, the traffic scheduling module 130 may perform shielding operation of traffic scheduling in advance, that is, "graceful exit", and meanwhile, to avoid waiting for the traffic to be completely cleared indefinitely, the maximum time of the traffic shielding processing may be set to be 8 hours.
In this embodiment, as shown in fig. 1b, the task execution module 140 has two functions, namely, acquiring application basic metadata of the service to be migrated, and performing boot/application deployment of the destination server and application uninstallation/logoff of the initial server. The primary work of service migration is to acquire and store metadata of a service to be migrated. The service metadata is a reference standard for creating and deploying the new service and is also a bottom-of-pocket guarantee during abnormal rollback of the process. Therefore, the task execution module 140 needs to obtain and store complete and accurate service metadata corresponding to the target task on the initial server, and then perform startup and application deployment on the target server to which the target task is to be migrated according to the service metadata.
If the task execution module 140 is abnormal during the process of booting the destination server or deploying the application, the task management module 120 decides to perform the next service booting application deployment operation, and the task execution module 140 executes the operation.
In this embodiment, the check module 150 is also a very important functional module, and how to apply peer-to-peer to the initial server and the destination server in the elastic capacity marginal scenario is ensured by the check module. By carrying out consistency check on the application package versions, the configuration versions and the environment variables of the initial server and the target server, whether the application deployment of the target server is missed or not is judged, so that the service is successfully migrated to the target server, and the service can be directly used on the target server.
According to the technical scheme of the embodiment of the invention, a task trigger module of the system responds to task trigger operation to generate a target task; if the task management module judges that the target task belongs to the service migration task, the scheduling flow scheduling module performs flow shielding processing on an initial server corresponding to the target task and sends the target task to the task execution module; the task execution module acquires service metadata corresponding to the target task on the initial server, and performs starting and application deployment processing on a target server corresponding to the target task according to the service metadata; the verification module is used for carrying out consistency verification on the application deployment information on the initial server and the target server to realize service migration, the problem that operation risk hidden danger exists in service migration in a live broadcast platform edge computing scene through manual operation in the prior art is solved, automatic service migration in the live broadcast platform edge computing scene is realized, time spent in service migration is reduced, and service migration efficiency is improved.
Example two
Fig. 2a is a schematic structural diagram of a service migration system based on a live broadcast platform edge computing scenario in a second embodiment of the present invention, and this embodiment further explains modules in the service migration system based on the live broadcast platform edge computing scenario on the basis of the above embodiment. As shown in fig. 2a, the system comprises: a task triggering module 210, a task management module 220, a traffic scheduling module 230, a task execution module 240 and a verification module 250;
the task triggering module 210 is configured to generate a target task in response to a task triggering operation, and send the target task to the task management module 220;
the task management module 220 is configured to, if it is determined that the target task belongs to the service migration task, perform traffic shielding processing on the initial server corresponding to the target task by the traffic scheduling module 230, and send the target task to the task execution module 240;
the task execution module 240 is configured to obtain service metadata corresponding to the target task on the initial server, and perform startup and application deployment processing on the target server corresponding to the target task according to the service metadata;
the checking module 250 is configured to perform consistency checking on the application deployment information on the initial server and the destination server to implement service migration.
Optionally, the task execution module 240 is specifically configured to: according to the service metadata corresponding to the target task, starting up the target servers corresponding to the target task, and determining whether each target server is started up successfully; carrying out application deployment operation on the target server which is successfully started, and calling a verification module to carry out consistency verification on the deployed application; and if the target server with the failed boot-up exists, generating a boot-up failure record, and triggering the target server with the failed boot-up to carry out the boot-up operation again.
In this embodiment, as shown in fig. 2b, after receiving the service migration task sent by the task management module 220, the task execution module 240 determines metadata related to the service migration task, for example, an IP address, a process version, a service data packet of a specified version, and the like, through a management page provided by the task execution module. And then executing the starting task of each destination server according to the service metadata, and detecting whether all the destination servers corresponding to each task are started successfully. The application deployment can be directly performed on the destination server which is successfully started, and consistency check is performed on the application deployment which is deployed on the initial server and the destination server through the check module 250, so as to determine whether the application deployment of the destination server is missed or not. And if the target server fails to start, generating and storing a corresponding start-up failure record, and triggering the target server which fails to start up again according to the start-up failure record after manual access troubleshooting recovery.
Optionally, the task execution module 240 performs parallel application deployment operations on multiple destination servers by constructing a parallel pool.
In this embodiment, considering that service migration of a machine room granularity involves deployment of hundreds of application services, and actually, an application deployment request cannot be completed in a short time due to network fluctuation and the like on line, in order to complete, reliably and quickly perform service application migration operation, the task execution module 240 performs parallel deployment on package lists of different server granularities by constructing a parallel pool, i.e., a ThreadPool thread pool, so that deployment requirements of multiple applications can be completed simultaneously within a timeout period, and the deployment efficiency is greatly improved.
Optionally, the task execution module 240 sets the number of concurrent deployment tasks and the task timeout time, and is specifically configured to: when the parallel application deployment operation is carried out on the target servers with the quantity of the concurrent deployment tasks according to the parallel pool, the state query is carried out on the application deployment tasks of the target servers at intervals of first preset time; if the target application deployment task which fails to be deployed is inquired, triggering the retry operation of the target application deployment task; if the application deployment task which is successfully deployed is inquired, triggering the application deployment task which is not processed to be processed; and the first preset time is less than the task timeout time.
In this embodiment, in order to avoid repeated application deployment, the task execution module 240 sets the number of concurrent deployment tasks and sets the lock mechanism within the task timeout period, but the lock mechanism may cause application deployment failure to occur and then retry the application deployment after the task timeout period is exceeded. Based on the method, reasonable cycle result judgment time and overtime retry time can be set according to the task overtime time, so that the deployment efficiency of the protection limit of the task execution module is improved. Wherein, the cycle result judgment time is a first preset time.
Exemplarily, the task timeout time is set to 120s, if the task is not finished within the task timeout time, the same task cannot be performed due to a locking mechanism, and at this time, the first preset time may be set to 45 seconds, that is, the state query may be performed on the application deployment task of each destination server once every 45 s. If the application deployment failure task is finished through inquiry, the application deployment task can be directly retried through triggering; if the application is successfully deployed through inquiry, the application which is not yet deployed due to the limitation of the number of concurrent tasks can be directly triggered; if the task timeout time is exceeded for 135s and the deployment failure ends, the corresponding application deployment task retry is performed and will not be locked.
The first preset time needs to be less than the task timeout time, but is not limited to 45s and 45s, which are preferred values selected by experiments, and 40s or other values may be selected.
Optionally, the checking module 250 is specifically configured to: carrying out consistency check on the application deployment information of the initial server and the target server; if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server; carrying out consistency check on the new application deployment information of the target server, and triggering secondary data check operation on the target server if the check result is inconsistent; if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server at intervals of preset duration; and if the verification result is consistent, calling the flow scheduling module to start the application deployed on the target server, and triggering the application task corresponding to the initial server to exit at fixed time.
In this embodiment, the checking module 250 may perform consistency check on the application package versions, the configuration versions, and the environment variables of the initial server and the destination server, and determine whether the application deployment of the destination server is faulty or not. As shown in fig. 2b, if the verification result is inconsistent, that is, the task execution module 240 makes an error in the application deployment of the destination server, the task execution module needs to be triggered to retry the application deployment task and perform consistency verification again. If the verification result is not consistent after a plurality of retries, a secondary data verification operation can be triggered, and the application deployment task is reprocessed. And if the verification results are not consistent after the secondary verification, reprocessing the application deployment task after a preset time interval. If the verification result is consistent in the process, the traffic scheduling module 230 is directly called to start the application on the corresponding destination server, and the application is unloaded and quitted from the corresponding initial server after a specified time interval.
In this embodiment, as found in an actual scenario, the application deployment retries of the task execution module 240 are often all failed due to a network problem in a short time of the machine room, and therefore, the verification module 250 increases the capability of secondary verification. Due to the fact that time deviation exists between the triggering time of the secondary verification and the first application deployment time of the target server, the migration process can be automatically completed as far as possible.
In addition, due to the complex actual network environment, sometimes after a plurality of times of loop retries, the complete packet cannot be downloaded within the task timeout time due to network abnormality, and further the task fails to end. Therefore, a mode of a timing deployment retry mechanism is introduced, retry deployment is carried out after timing task triggering is delayed for a certain time, and the automation deployment completion degree is improved. Therefore, if the secondary verification fails, the task retry requirement can be further triggered at regular time, namely, the flow is triggered again as the bottom of the pocket after the preset time length.
Optionally, the method may further include: and the storage module is used for acquiring the service metadata corresponding to the target task from the task execution module, converting the service metadata into corresponding protocol data and performing local storage and/or remote Redis storage.
In this embodiment, the storage module is currently divided into two forms, namely local storage and remote Redis storage, the metadata related to each target task is acquired and updated by the Redis service by default, and the local storage is triggered only by an exception. Illustratively, when the target server is abnormally started, task information related to an abnormal machine needs to be recorded and stored in a remote Redis, and after a manufacturer solves the starting problem of the server, the target server is restarted by triggering a starting task to pull a starting failure record from the Redis to start again.
Optionally, the task management module 220 may be further configured to: if the target task belongs to the task of quitting the application service, calling a task execution module to carry out application unloading and shutdown operations on the initial server corresponding to the target task; and if the target task belongs to the deployment retry task, calling the task execution module to perform application deployment retry operation on the target server corresponding to the target task.
In this embodiment, as shown in fig. 2b, after receiving the target task sent by the task triggering module 210, if it is determined that the target task is an application service exiting task triggered after completing application deployment, the task management module 220 invokes the task execution module to perform application uninstalling and shutdown operations on an initial server corresponding to the target task. And if the target task is judged to be the application deployment retry task triggered by the application deployment failure, directly calling the task execution module to perform application deployment again on the corresponding target server.
Optionally, the method may further include: the notification module is used for generating a corresponding abnormal starting-up notification message according to the starting-up failure record; generating a corresponding deployment abnormity notification message according to the failed application deployment information; generating corresponding scheduling exception notification messages according to the flow shielding failure information or the application starting failure information; and sending the abnormal notification message to a manager.
The service migration system in this embodiment is an automated/semi-automated system, and some abnormal boot/deployment failure scenarios must be resolved only by intervention of manual interference, so a notification mechanism is introduced to facilitate re-triggering the service migration process to continue after manual timely intervention processing.
In this embodiment, by setting the notification module, the notification module can be responsible for the notification of the start-stop state of the whole process and the feedback of the abnormal state of the intermediate link, so as to improve the process of service migration and the result perception capability. Illustratively, when the task execution module fails to start the destination server, the notification module may generate a corresponding abnormal starting notification message according to the starting failure record, and send the abnormal starting notification message to the relevant service manager; when the consistency check of the application deployment information of the destination server by the check module fails, the notification module may generate a corresponding deployment exception notification message according to the failed application deployment information, for example, a primary deployment exception message, a retry deployment exception message, a secondary check exception message, a timing retry exception message, and the like, and send the deployment exception notification message to a related service manager; when the traffic scheduling module fails to shield traffic or fails to open the application, the notification module may generate a corresponding scheduling exception notification message according to the traffic shielding failure information or the application opening failure information, and send the scheduling exception notification message to a relevant service manager.
According to the technical scheme of the embodiment of the invention, a task trigger module of the system responds to task trigger operation to generate a target task; if the task management module judges that the target task belongs to the service migration task, the scheduling flow scheduling module performs flow shielding processing on an initial server corresponding to the target task and sends the target task to the task execution module; the task execution module acquires service metadata corresponding to the target task on the initial server, and performs starting and application deployment processing on a target server corresponding to the target task according to the service metadata; the verification module is used for carrying out consistency verification on the application deployment information on the initial server and the target server to realize service migration, the problem that operation risk hidden danger exists in service migration in a live broadcast platform edge computing scene through manual operation in the prior art is solved, automatic service migration in the live broadcast platform edge computing scene is realized, time spent in service migration is reduced, and service migration efficiency is improved.
EXAMPLE III
Fig. 3 is a flowchart of a service migration method based on a live broadcast platform edge computing scenario in a third embodiment of the present invention, where this embodiment is applicable to a case of automatically performing service migration in a live broadcast platform edge computing scenario, and the method may be executed by a service migration system based on a live broadcast platform edge computing scenario, where the system may be implemented by hardware and/or software, and may generally be integrated in a device providing service migration, for example, a central control server. As shown in fig. 3, the method includes:
and 310, generating a target task in response to the task triggering operation through the task triggering module, and sending the target task to the task management module.
Optionally, the generating, by the task triggering module, the target task in response to the task triggering operation may include: generating a target task in response to the operation of submitting business requirements by a system background; and/or generating a target task in response to a trigger operation on an externally provided API authentication interface; and/or generating a target task in response to a timed task triggering operation of the task management module in a specific scene; when the target task is a service migration task, the target task comprises migration range information; the migration range information includes a designated machine room, a designated service, or a designated IP address.
And 320, by the task management module, if the target task belongs to the service migration task, the scheduling traffic scheduling module performs traffic shielding processing on the initial server corresponding to the target task and sends the target task to the task execution module.
Optionally, the method may further include: when the flow shielding of the flow scheduling module fails, a corresponding scheduling exception notification message is generated through the notification module according to the flow shielding failure information and is sent to relevant service management personnel.
Optionally, the method may further include: through the task management module, if the target task is judged to belong to the task of quitting the application service, the task execution module is called to carry out application unloading and shutdown operations on the initial server corresponding to the target task; and if the target task belongs to the deployment retry task, calling the task execution module to perform application deployment retry operation on the target server corresponding to the target task.
And 330, acquiring service metadata corresponding to the target task on the initial server through the task execution module, and starting and deploying applications of the target server corresponding to the target task according to the service metadata.
Optionally, the starting and application deployment processing of the destination server corresponding to the target task according to the service metadata may include: according to the service metadata corresponding to the target task, starting up the target servers corresponding to the target task, and determining whether each target server is started up successfully; carrying out application deployment operation on the target server which is successfully started, and calling a verification module to carry out consistency verification on the deployed application; and if the target server with the failed boot-up exists, generating a boot-up failure record, and triggering the target server with the failed boot-up to carry out the boot-up operation again.
Optionally, the method may further include: when the task execution module fails to start the target server, a corresponding abnormal starting notification message can be generated by the notification module according to the starting failure record and is sent to the related service management personnel.
Optionally, the task execution module performs parallel application deployment operation on the multiple destination servers by constructing a parallel pool.
Optionally, the task execution module sets the number of concurrent deployment tasks and the task timeout time; the parallel application deployment operation on the multiple destination servers by constructing the parallel pool may include: when the parallel application deployment operation is carried out on the target servers with the quantity of the concurrent deployment tasks according to the parallel pool, the state query is carried out on the application deployment tasks of the target servers at intervals of first preset time; if the target application deployment task which fails to be deployed is inquired, triggering the retry operation of the target application deployment task; if the application deployment task which is successfully deployed is inquired, triggering the application deployment task which is not processed to be processed; and the first preset time is less than the task timeout time.
Optionally, after the task execution module obtains the service metadata corresponding to the target task on the initial server, the method may further include: and acquiring service metadata corresponding to the target task from the task execution module through the storage module, and converting the service metadata into corresponding protocol data for local storage and/or remote Redis storage.
And 340, performing consistency check on the application deployment information on the initial server and the target server through a check module to realize service migration.
Optionally, the consistency check is performed on the application deployment information on the initial server and the destination server through a check module to implement service migration, and the method may include: carrying out consistency check on the application deployment information of the initial server and the target server; if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server; carrying out consistency check on the new application deployment information of the target server, and triggering secondary data check operation on the target server if the check result is inconsistent; if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server at intervals of preset duration; and if the verification result is consistent, calling the flow scheduling module to start the application deployed on the target server, and triggering the application task corresponding to the initial server to exit at fixed time.
Optionally, the method may further include: when the consistency check of the application deployment information of the destination server by the check module fails, a corresponding deployment exception notification message, such as a primary deployment exception message, a retry deployment exception message, a secondary check exception message, a timing retry exception message and the like, can be generated by the notification module according to the failed application deployment information, and is sent to a relevant service manager. When the traffic scheduling module fails to start the application, a corresponding scheduling exception notification message can be generated by the notification module according to the application start failure information and sent to the relevant service management personnel.
The technical scheme of the embodiment can solve the problem of uncertainty of the service migration process in the edge computing scene, and a full-automatic/semi-automatic service migration system is created by means of system engineering, so that on one hand, the time cost of operation and maintenance manual operation is reduced, and the risk potential generated by manual uncertainty operation can be avoided, thereby ensuring that stable and reliable service is provided for the outside.
According to the technical scheme of the embodiment of the invention, a task trigger module of the system responds to task trigger operation to generate a target task; if the task management module judges that the target task belongs to the service migration task, the scheduling flow scheduling module performs flow shielding processing on an initial server corresponding to the target task and sends the target task to the task execution module; the task execution module acquires service metadata corresponding to the target task on the initial server, and performs starting and application deployment processing on a target server corresponding to the target task according to the service metadata; the verification module is used for carrying out consistency verification on the application deployment information on the initial server and the target server to realize service migration, the problem that operation risk hidden danger exists in service migration in a live broadcast platform edge computing scene through manual operation in the prior art is solved, automatic service migration in the live broadcast platform edge computing scene is realized, time spent in service migration is reduced, and service migration efficiency is improved.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (8)
1. A service migration system based on a live platform edge computing scene is characterized by comprising: the system comprises a task triggering module, a task management module, a flow scheduling module, a task execution module and a verification module;
the task triggering module is used for responding to task triggering operation to generate a target task and sending the target task to the task management module;
the task management module is used for scheduling the traffic scheduling module to perform traffic shielding processing on an initial server corresponding to the target task and sending the target task to the task execution module if the target task is judged to belong to the service migration task;
the task execution module is used for acquiring service metadata corresponding to the target task on the initial server, and performing starting and application deployment processing on a target server corresponding to the target task according to the service metadata;
the verification module is used for performing consistency verification on the application deployment information on the initial server and the target server to realize service migration; the application deployment information includes: an application package version, a configuration version and an environment variable;
the task execution module performs parallel application deployment operation on a plurality of destination servers by constructing a parallel pool;
the task execution module sets the quantity of the concurrent deployment tasks and the task timeout time, and is specifically configured to:
when parallel application deployment operation is carried out on the target servers with the quantity of the concurrent deployment tasks according to the parallel pool, state query is carried out on the application deployment tasks of the target servers at intervals of first preset time;
if the target application deployment task which fails to be deployed is inquired, triggering the retry operation of the target application deployment task;
if the application deployment task which is successfully deployed is inquired, triggering the application deployment task which is not processed to be processed;
and the first preset time is less than the task timeout time.
2. The system of claim 1, wherein the task triggering module is specifically configured to:
generating a target task in response to the operation of submitting business requirements by a system background; and/or
Responding to the trigger operation of an API authentication interface provided externally, and generating a target task; and/or
Responding to the timed task triggering operation of the task management module in a specific scene to generate a target task;
when the target task is a service migration task, the target task comprises migration range information; the migration range information comprises a designated machine room, a designated service or a designated IP address.
3. The system of claim 1, wherein the task execution module is specifically configured to:
according to the service metadata corresponding to the target task, starting up the target servers corresponding to the target task, and determining whether each target server is started up successfully;
carrying out application deployment operation on the target server which is successfully started, and calling the verification module to carry out consistency verification on the deployed application;
and if the target server with the failed boot-up exists, generating a boot-up failure record, and triggering the target server with the failed boot-up to carry out the boot-up operation again.
4. The system of claim 1, wherein the verification module is specifically configured to:
carrying out consistency check on the application deployment information of the initial server and the target server;
if the verification result is inconsistent, triggering the task execution module to perform application deployment retry operation on the target server;
and carrying out consistency check on the new application deployment information of the destination server.
5. The system of claim 1, further comprising:
and the storage module is used for acquiring the service metadata corresponding to the target task from the task execution module, converting the service metadata into corresponding protocol data and performing local storage and/or remote Redis storage.
6. The system of claim 1, wherein the task management module is further configured to:
if the target task belongs to the task of quitting the application service, calling the task execution module to carry out application unloading and shutdown operations on the initial server corresponding to the target task;
and if the target task belongs to the deployment retry task, calling the task execution module to perform application deployment retry operation on a target server corresponding to the target task.
7. The system of claim 3, further comprising:
the notification module is used for generating a corresponding abnormal starting-up notification message according to the starting-up failure record and sending the abnormal starting-up notification message to a manager;
when the consistency check fails, generating a corresponding deployment abnormity notification message according to the failed application deployment information, and sending the deployment abnormity notification message to a manager;
and when the flow shielding fails or the application opening fails, generating a corresponding scheduling exception notification message according to the flow shielding failure message or the application opening failure message, and sending the scheduling exception notification message to a manager.
8. A service migration method based on a live platform edge computing scene is applied to the service migration system based on the live platform edge computing scene in any one of claims 1-7, and comprises the following steps:
generating a target task in response to task triggering operation through a task triggering module, and sending the target task to a task management module;
through a task management module, if the target task belongs to a service migration task, a traffic scheduling module is scheduled to perform traffic shielding processing on an initial server corresponding to the target task and send the target task to a task execution module;
acquiring service metadata corresponding to the target task on the initial server through a task execution module, and starting and applying deployment processing to a target server corresponding to the target task according to the service metadata;
through a checking module, carrying out consistency checking on the application deployment information on the initial server and the target server to realize service migration; the application deployment information includes: an application package version, a configuration version and an environment variable;
the task execution module performs parallel application deployment operation on a plurality of destination servers by constructing a parallel pool; the task execution module sets the quantity of the concurrent deployment tasks and the task timeout time;
the method for carrying out parallel application deployment operation on a plurality of destination servers by constructing a parallel pool comprises the following steps: when the parallel application deployment operation is carried out on the target servers with the quantity of the concurrent deployment tasks according to the parallel pool, the state query is carried out on the application deployment tasks of the target servers at intervals of first preset time; if the target application deployment task which fails to be deployed is inquired, triggering the retry operation of the target application deployment task; if the application deployment task which is successfully deployed is inquired, triggering to process the application deployment task which is not processed; and the first preset time is less than the task timeout time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110482788.4A CN113225576B (en) | 2021-04-30 | 2021-04-30 | Service migration system and method based on live broadcast platform edge computing scene |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110482788.4A CN113225576B (en) | 2021-04-30 | 2021-04-30 | Service migration system and method based on live broadcast platform edge computing scene |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113225576A CN113225576A (en) | 2021-08-06 |
| CN113225576B true CN113225576B (en) | 2023-03-21 |
Family
ID=77090553
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110482788.4A Active CN113225576B (en) | 2021-04-30 | 2021-04-30 | Service migration system and method based on live broadcast platform edge computing scene |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113225576B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7392302B2 (en) * | 2002-02-21 | 2008-06-24 | Bea Systems, Inc. | Systems and methods for automated service migration |
| CN104615598B (en) * | 2013-11-04 | 2019-07-09 | 南京中兴新软件有限责任公司 | The emigration processing method and device of meta data server |
| CN106034080A (en) * | 2015-03-10 | 2016-10-19 | 中兴通讯股份有限公司 | Metadata migration method and metadata migration device in distributed system |
| CN108228672B (en) * | 2016-12-22 | 2022-05-03 | 阿里巴巴集团控股有限公司 | Metadata migration method, device, system and equipment |
| CN110324184B (en) * | 2019-06-26 | 2021-06-25 | 深圳前海微众银行股份有限公司 | Service capacity expansion and migration method, device, system, equipment and readable storage medium |
-
2021
- 2021-04-30 CN CN202110482788.4A patent/CN113225576B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN113225576A (en) | 2021-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111290834B (en) | Method, device and equipment for realizing high service availability based on cloud management platform | |
| CN110389900B (en) | Distributed database cluster testing method and device and storage medium | |
| CN108683516B (en) | Application instance upgrading method, device and system | |
| US7451201B2 (en) | Policy driven autonomic computing-specifying relationships | |
| US20070083588A1 (en) | Systems and methods for automated provisioning of managed computing resources | |
| US9485151B2 (en) | Centralized system management on endpoints of a distributed data processing system | |
| CN107844343B (en) | Upgrading system and method for complex server application system | |
| CN112799786A (en) | Exit method, device, equipment and storage medium of micro-service instance | |
| US10942831B2 (en) | Automating and monitoring rolling cluster reboots | |
| CN109697078B (en) | Repairing method of non-high-availability component, big data cluster and container service platform | |
| CN113312153A (en) | Cluster deployment method and device, electronic equipment and storage medium | |
| CN114168179A (en) | Micro-service management method, device, computer equipment and storage medium | |
| CA3129985A1 (en) | Abnormal operation environment restoration method and device, computer equipment and storage medium | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN113225576B (en) | Service migration system and method based on live broadcast platform edge computing scene | |
| CN109002263B (en) | Method and device for adjusting storage capacity | |
| CN115357198B (en) | Mounting method and device of storage volume, storage medium and electronic equipment | |
| CN113934711B (en) | Method for automatically deploying gbase8s cluster | |
| CN115941739A (en) | Inspection system and inspection method for Internet of things equipment | |
| US20210373868A1 (en) | Automated Deployment And Management Of Network Intensive Applications | |
| CN115543491A (en) | Microservice processing method and device | |
| CN114816662A (en) | Container arrangement method and system applied to Kubernetes | |
| CN111176959B (en) | Early warning method, system and storage medium of cross-domain application server | |
| CN110188008B (en) | Job scheduling master-slave switching method and device, computer equipment and storage medium | |
| CN109921940B (en) | System and method for realizing off-line arrangement processing of network service based on SDWAN scene |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |