CN112187753B - Data updating method, device, equipment and readable storage medium - Google Patents

Data updating method, device, equipment and readable storage medium Download PDF

Info

Publication number
CN112187753B
CN112187753B CN202010986611.3A CN202010986611A CN112187753B CN 112187753 B CN112187753 B CN 112187753B CN 202010986611 A CN202010986611 A CN 202010986611A CN 112187753 B CN112187753 B CN 112187753B
Authority
CN
China
Prior art keywords
token
cloud service
container cloud
container
update notification
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
Application number
CN202010986611.3A
Other languages
Chinese (zh)
Other versions
CN112187753A (en
Inventor
王洪泉
黄吉旺
吴栋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Inspur Data Technology Co Ltd
Original Assignee
Beijing Inspur Data Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Inspur Data Technology Co Ltd filed Critical Beijing Inspur Data Technology Co Ltd
Priority to CN202010986611.3A priority Critical patent/CN112187753B/en
Publication of CN112187753A publication Critical patent/CN112187753A/en
Application granted granted Critical
Publication of CN112187753B publication Critical patent/CN112187753B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/068—Network architectures or network communication protocols for network security for supporting key management in a packet data network using time-dependent keys, e.g. periodically changing keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention discloses a data updating method, a device, equipment and a readable storage medium, wherein the method comprises the following steps: the first container cloud service generates a new Token; transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism; and providing a new Token to the second container cloud service under the condition that the second container cloud service calls the Token acquisition interface of the first container cloud service. In the method, the first container cloud service does not need to set complex starting logic, and under the condition of short starting time, the second container cloud service not only can timely call a new Token, but also can ensure the reliability of the inter-application call.

Description

Data updating method, device, equipment and readable storage medium
Technical Field
The present invention relates to the field of computer application technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for updating data.
Background
The container cloud platform is mostly based on a Kubernetes framework and provides a functional system with application management as a core for users. More and more enterprises or individual users deploy applications on container cloud platforms. In a production environment, inter-calling among applications is a ubiquitous scenario, and especially under a micro-service architecture, inter-calling among applications is more used for guaranteeing the integrity of services.
To prevent malicious programs from stealing data or performing dangerous operations, there is a security mechanism generally called between applications, wherein one common mechanism is Token verification, and the implementation principle is approximately as follows: the service A is used as a core service, generates Token and provides a Token acquisition interface, and other services can call the interface to acquire Token by providing authentication information such as user name, password and the like; when the service B accesses the service A, token information is required to be attached, and data processing and other operations can be performed after verification is passed. Typically, service B typically invokes a Token acquisition interface once and saves it as its own data, which is subsequently used when accessing service a. However, if the Token in the service a is updated, then the service B reuses the saved Token to access, and the Token information is wrong, so that the access cannot be performed.
The Token update problem, the solutions currently in common use include: 1. the service B calls the service A to acquire Token at regular time; 2. and when the service A generates the Token in the upgrading and restarting process, actively informing the service B to acquire the Token again through an interface. For scheme 1, since the timing task has a time interval, it cannot be guaranteed that the timing task can be initiated in time to obtain a new Token after the service a is upgraded and restarted, and if the service a has no operation of upgrading and restarting for a long time, the result of each invocation of the timing task may be the same, which may cause unnecessary consumption of resources. For scheme 2, performance problems such as more complex start-up logic, longer start-up time, coupling of notification function with core service logic of service a, etc. are caused.
In summary, how to effectively solve the problems of Token update and the like is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The invention aims to provide a data updating method, a device, equipment and a readable storage medium, which can effectively update Token in time and ensure normal calling among applications.
In order to solve the technical problems, the invention provides the following technical scheme:
a Token updating method, comprising:
the first container cloud service generates a new Token;
transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism;
and providing the new Token for the second container cloud service under the condition that the second container cloud service calls a Token acquisition interface of the first container cloud service.
Preferably, the sending, by using a lifecycle management mechanism, a Token update notification to the second container cloud service includes:
and sending the Token update notification to the second container cloud service by using the life cycle management mechanism under the condition of starting the target container corresponding to the new Token.
Preferably, sending the Token update notification to the second container cloud service includes:
and sending the Token update notification to the second container cloud service by automatically triggering a Token update notification script by using a PostStart mode in the life cycle management mechanism.
Preferably, sending the Token update notification to the second container cloud service includes:
and sending the Token update notification to the second container cloud service by calling a Token update notification interface of the second container cloud service.
Preferably, in a case where the second container cloud service invokes a Token acquisition interface of the first container cloud service, providing the new Token to the second container cloud service includes:
and under the condition that the second container cloud service calls the Token acquisition interface by using the verification information, providing the new Token for the second container cloud service by using the Token acquisition interface.
Preferably, the sending, by using a lifecycle management mechanism, a Token update notification to the second container cloud service includes:
acquiring a call service list corresponding to the new Token;
and sending the Token update notification to each container cloud service corresponding to the call service list by using the life cycle management mechanism.
Preferably, the first container cloud service generates a new Token, including:
and generating the new Token corresponding to the target application in the process of starting the target application.
A data updating apparatus comprising:
the container creation module is used for generating a new Token by the first container cloud service;
the update notification module is used for sending Token update notification to the second container cloud service by utilizing a life cycle management mechanism;
the Token providing module is configured to provide the new Token to the second container cloud service when the second container cloud service invokes the Token acquisition interface of the first container cloud service.
A data updating apparatus comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the data updating method when executing the computer program.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the data updating method described above.
By applying the method provided by the embodiment of the invention, the first container cloud service generates a new Token; transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism; and providing a new Token to the second container cloud service under the condition that the second container cloud service calls the Token acquisition interface of the first container cloud service.
In the method, after the first container cloud service generates a new Token, a Token update notification is sent to the second container cloud service by using a lifecycle management mechanism. After the second container cloud service receives the Token notification, the Token acquisition interface of the first container cloud service is actively called, and finally the second container cloud service can be enabled to obtain a new Token. It can be seen that, in the method, the second container cloud service does not need to acquire a new Token periodically, the first container cloud service does not need to actively send the new Token to the second container cloud service, but based on a life cycle management mechanism, after determining that the new Token appears, the second container cloud service sends a Token update notification, and the second container cloud service actively acquires the new Token. In other words, in the method, the first container cloud service does not need to set complex starting logic, and under the condition that the time for starting is short, the second container cloud service can timely acquire a new Token, so that the reliability of the inter-application call can be ensured.
Correspondingly, the embodiment of the invention also provides a data updating device, equipment and a readable storage medium corresponding to the data updating method, which have the technical effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the related art, the drawings that are required to be used in the embodiments or the related technical descriptions will be briefly described, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is a flowchart of a data update method according to an embodiment of the present invention;
FIG. 2 is a block diagram of a data update method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a data updating apparatus according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a data update apparatus according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a specific structure of a data updating device according to an embodiment of the present invention.
Detailed Description
In order to better understand the aspects of the present invention, the present invention will be described in further detail with reference to the accompanying drawings and detailed description. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, fig. 1 is a flowchart of a data updating method according to an embodiment of the invention, the method includes the following steps:
s101, the first container cloud service generates a new Token.
The first container cloud service may correspond to a core service, that is, an application that needs to be invoked by other container cloud services in the first container cloud service.
And generating a new Token under the conditions of newly creating an application, or upgrading the service, or restarting the service and the like in the first container cloud service. It should be noted that the new Token may correspond to a new application, or may correspond to an updated Token for an existing application.
Specifically, in the case of newly-built applications, or service upgrades, or service restarts, etc., it is desirable that an application start-up procedure exists for the validation, and a new Token is generated during the application start-up procedure.
The Token has a corresponding relationship with the application. Based on this, in a specific embodiment of the present invention, step S101 may specifically include generating a new Token corresponding to the target application during the process of starting the target application. That is, the generation of a new Token will necessarily initiate the application process.
S102, sending Token update notification to the second container cloud service by using a life cycle management mechanism.
In general, kubernetes is a container orchestration engine of a container cloud platform that is capable of providing a Lifecycle management mechanism when deploying an application. The lifecycle management mechanism supports application services to complete relevant processing logic through custom scripts or interfaces during deployment or deletion.
Based on this, in the present embodiment, sending Token update notification to the second container cloud service is achieved using a lifecycle management mechanism.
The second container cloud service is a container cloud service which needs to call an application in the first container cloud service. In particular, in the present embodiment, the number of the second container cloud services is not limited, that is, the number of the second container cloud services may be 1, or may be 2, or more than 2.
Wherein, token update notification, i.e. notifying that a new Token exists, so that the second container cloud service takes the initiative to acquire the new Token.
Specifically, the Token update notification is sent to the second container cloud service by using the lifecycle management mechanism, and may specifically be sent to the second container cloud service by using the lifecycle management mechanism when the target container corresponding to the new Token is started. Because the lifecycle management mechanism may be triggered by the initiation of the target container to which the target Token corresponds, sending a Token update notification to the second container cloud service is performed in the event that the new target container to which the Token corresponds is initiated.
Lifecycle contains two forms, postStart, which is automatically triggered to execute after the container of the application service is successfully created, and PreStop, which is automatically triggered to execute before the application container is deleted. Thus, in a specific embodiment of the present invention, sending a Token update notification to the second container cloud service may specifically be: and sending the Token update notification to the second container cloud service by automatically triggering the Token update notification script by using a PostStart mode in the life cycle management mechanism. That is, a Token update notification script may be pre-written and automatically triggered by the PostStart method, so that the Token update notification may be sent to the second container cloud service. The Token update notification script may be a separate program or may be in Linux shell format.
In a specific embodiment of the present invention, sending a Token update notification to the second container cloud service may specifically be: and sending Token update notification to the second container cloud service by calling a Token update notification interface of the second container cloud service. That is, the second container cloud service has a Token update notification interface, and by calling the Token update notification interface, a Token update notification can be sent to the second container cloud service.
In a specific embodiment of the present invention, sending, by using a lifecycle management mechanism, a Token update notification to a second container cloud service may specifically include:
step one, acquiring a call service list corresponding to a new Token;
and step two, sending Token update notification to each container cloud service corresponding to the call service list by using a life cycle management mechanism.
For convenience of description, the two steps are described in combination.
In this embodiment, a call service list corresponding to each application may be stored in advance. After an application has a new Token, the call service list can be obtained, and then based on a life cycle management mechanism, each container cloud service corresponding to the call service list is wanted to send Token update notification.
S103, when the second container cloud service calls the Token acquisition interface of the first container cloud service, providing a new Token for the second container cloud service.
After receiving the Token update notification, the second container cloud service can actively call a Token acquisition interface of the first container cloud service. The Token acquisition interface of the first container cloud service provides an interface of the new Token. I.e. the first container cloud service has a Token acquisition interface.
In a specific embodiment of the present invention, step S103 provides a new Token to the second container cloud service when the second container cloud service invokes the Token acquisition interface of the first container cloud service, specifically includes: and under the condition that the second container cloud service calls the Token acquisition interface by using the verification information, providing a new Token for the second container cloud service by using the Token acquisition interface. That is, the second container cloud service invokes this Token acquisition interface to acquire a new Token using authentication information such as a user name, password, etc. The first container cloud service verifies the verification information, and the verification provides feedback of the new Token to the second container cloud service.
By applying the method provided by the embodiment of the invention, the first container cloud service generates a new Token; transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism; and providing a new Token to the second container cloud service under the condition that the second container cloud service calls the Token acquisition interface of the first container cloud service.
In the method, after the first container cloud service generates a new Token, a Token update notification is sent to the second container cloud service by using a lifecycle management mechanism. After the second container cloud service receives the Token notification, the Token acquisition interface of the first container cloud service is actively called, and finally the second container cloud service can be enabled to obtain a new Token. It can be seen that, in the method, the second container cloud service does not need to acquire a new Token periodically, the first container cloud service does not need to actively send the new Token to the second container cloud service, but based on a life cycle management mechanism, after determining that the new Token appears, the second container cloud service sends a Token update notification, and the second container cloud service actively acquires the new Token. In other words, in the method, the first container cloud service does not need to set complex starting logic, and under the condition that the time for starting is short, the second container cloud service can timely acquire a new Token, so that the reliability of the inter-application call can be ensured.
In order to facilitate a better understanding of the data updating method provided by the embodiments of the present invention, the following describes the data updating method in detail with reference to related technologies and specific application scenarios as examples.
The user of the container cloud platform does not need to manually apply or allocate physical resources of the bottom layer, and only needs to set information such as mirror image addresses, instance numbers, CPU/memory resource requirements and the like on a visual interface provided by the container cloud platform, so that the cloud platform can automatically finish tasks such as deployment, update, intelligent operation and maintenance of the application, and the like, thereby greatly simplifying the online and maintenance processes of the application, and the container cloud platform is receiving more and more attention.
In the production environment, if the service B needs to call the application in the service A, if the service A performs upgrading or other restarting operations, token regeneration occurs, and then the problem that Token information is wrong and cannot be accessed when the service B reuses the previously stored Token for access occurs.
Solutions currently in common use for Token update problems include: the service B calls the service A to acquire the Token at regular time, and actively informs the service B to acquire the Token again through the interface when the service A generates the Token in the upgrading restarting process. For the scheme of acquiring Token by timing call, since the timing task has a time interval, it cannot be guaranteed that the timing task can be initiated in time to acquire a new Token after the service a is upgraded and restarted, and if the service a has no operation of upgrading and restarting for a long time, the result of each call of the timing task may be the same, which may cause unnecessary consumption of resources. The scheme of actively notifying the service B through the interface in the starting process of the service A can avoid unnecessary consumption of resources, but can also cause performance problems of more complex starting logic, longer starting time, coupling of a notification function and core business logic of the service A, and the like.
Based on the above, in the embodiment of the invention, a Token update acquisition mechanism capable of avoiding resource consumption, ensuring performance and being effective in time is provided. Specifically, as can be seen from the above, the data updating method provided by the embodiment of the present invention proposes a Token updating mechanism between container cloud services based on life cycle, which aims at the problem that after the core service is updated and restarted and the Token is regenerated, other services need to effectively obtain a new Token in time on the premise of ensuring performance and reducing resource consumption.
The realization core is as follows: for Token update requirements, after the container of the core service a is successfully started, a Token update notification interface of the service B is called through a custom script in the PostStart process, and then the service B actively calls the interface of the service a to acquire a new Token. The custom script is decoupled with the business logic of the core service A, so that the starting of the service A is not influenced; the occupied resources are very few, and meanwhile, the service B can be automatically completed after being notified, so that the resources are not occupied continuously; triggering each time of restarting the service A can realize timely and effective notification.
Referring to fig. 2, the implementation process is as follows:
preconditions are: service a (corresponding to the first container cloud service above) provides a Token acquisition interface, and service B (corresponding to the second container cloud service above) provides a Token update notification interface in which the Token acquisition interface of service a is invoked to acquire and update a Token.
Custom notification scripts are written. The script form can be in a Linux shell format, and the main function is to call a Token update notification interface provided by the service B. After the writing is completed, the script is packed into a container mirror image of the service A.
The postStart execution method is added in the deployment configuration of the service a. For example, the execution method:
lifecycle:
postStart:
exec:
command: ["/bin/sh", "-c", "token.sh"]
and updating or redeploying the service A according to the normal upgrading flow.
And in the deployment process, after the application container is successfully started, the service A automatically triggers postStart and executes the custom script. The custom script calls a Token update notification interface of the service B, the service B starts a Token update flow after receiving the Token update notification interface, calls a related interface of the service A, acquires a new Token and stores the new Token, and completes the Token update flow.
The data updating method provided by the embodiment of the invention has the technical effects in practical application: the user-defined script is decoupled with the business logic of the core service, so that the starting of the service A is not influenced; the custom script occupies little resources, and can be automatically completed after the service is notified, so that the resources are not continuously occupied; the whole flow is executed when the core service container is started, so that timely and effective notification can be realized, and Token update can be performed in time.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a data updating device, where the data updating device described below and the data updating method described above can be referred to correspondingly.
Referring to fig. 3, the apparatus includes the following modules:
a container creation module 101, configured to generate a new Token by using a first container cloud service;
an update notification module 102, configured to send a Token update notification to the second container cloud service using a lifecycle management mechanism;
the Token providing module 103 is configured to provide a new Token to the second container cloud service when the second container cloud service invokes the Token acquisition interface of the first container cloud service.
By applying the device provided by the embodiment of the invention, the first container cloud service generates a new Token; transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism; and providing a new Token to the second container cloud service under the condition that the second container cloud service calls the Token acquisition interface of the first container cloud service.
In the device, after the first container cloud service generates a new Token, a Token update notification is sent to the second container cloud service by using a life cycle management mechanism. After the second container cloud service receives the Token notification, the Token acquisition interface of the first container cloud service is actively called, and finally the second container cloud service can be enabled to obtain a new Token. It can be seen that, in the device, the second container cloud service does not need to acquire a new Token regularly, the first container cloud service does not need to actively send the new Token to the second container cloud service, but based on a life cycle management mechanism, after determining that the new Token appears, a Token update notification is sent to the second container cloud service, and the second container cloud service actively acquires the new Token. In other words, in the device, the first container cloud service does not need to set complex starting logic, and under the condition that the time for starting is short, the second container cloud service can timely acquire a new Token, so that the reliability of the inter-application call can be ensured.
In one embodiment of the present invention, the update notification module 102 is specifically configured to send a Token update notification to the second container cloud service when a target container corresponding to a new Token is started by using a lifecycle management mechanism.
In a specific embodiment of the present invention, the update notification module 102 is specifically configured to send a Token update notification to the second container cloud service by automatically triggering a Token update notification script according to a PostStart method in the lifecycle management mechanism.
In one embodiment of the present invention, the update notification module 102 is specifically configured to send a Token update notification to the second container cloud service by calling a Token update notification interface of the second container cloud service.
In a specific embodiment of the present invention, the Token providing module 103 is specifically configured to provide a new Token to the second container cloud service using the Token acquisition interface if the second container cloud service invokes the Token acquisition interface using the verification information.
In one embodiment of the present invention, the update notification module 102 is specifically configured to obtain a call service list corresponding to a new Token; and sending Token update notification to each container cloud service corresponding to the call service list by using a life cycle management mechanism.
In one embodiment of the present invention, the container creation module 101 is specifically configured to generate a new Token corresponding to the target application during the process of starting the target application.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a data updating device, where a data updating device described below and a data updating method described above may be referred to correspondingly to each other.
Referring to fig. 4, the data updating apparatus includes:
a memory 332 for storing a computer program;
a processor 322 for implementing the steps of the data updating method of the above-described method embodiment when executing the computer program.
Specifically, referring to fig. 5, fig. 5 is a schematic diagram of a specific structure of a data updating apparatus according to the present embodiment, where the data updating apparatus may have a relatively large difference due to different configurations or performances, and may include one or more processors (central processing units, CPU) 322 (e.g., one or more processors) and a memory 332, where the memory 332 stores one or more computer applications 342 or data 344. Wherein the memory 332 may be transient storage or persistent storage. The program stored in memory 332 may include one or more modules (not shown), each of which may include a series of instruction operations in the data processing apparatus. Still further, the central processor 322 may be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the data updating device 301.
The data update device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input/output interfaces 358, and/or one or more operating systems 341.
The steps in the data updating method described above may be implemented by the structure of the data updating apparatus.
Corresponding to the above method embodiments, the embodiments of the present invention further provide a readable storage medium, where a readable storage medium described below and a data updating method described above may be referred to correspondingly.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the data update method of the above-described method embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, and the like.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not intended to be limiting.

Claims (8)

1. A method of updating data, comprising:
the first container cloud service generates a new Token;
transmitting Token update notifications to the second container cloud service using a lifecycle management mechanism;
providing the new Token to the second container cloud service under the condition that the second container cloud service calls a Token acquisition interface of the first container cloud service;
the sending, by using a lifecycle management mechanism, a Token update notification to a second container cloud service includes:
and under the condition that the target container corresponding to the new Token is started, sending the Token update notification to the second container cloud service by automatically triggering a Token update notification script by using a PostStart mode in the life cycle management mechanism.
2. The data updating method according to claim 1, wherein transmitting the Token update notification to the second container cloud service comprises:
and sending the Token update notification to the second container cloud service by calling a Token update notification interface of the second container cloud service.
3. The method for updating data according to claim 1, wherein in a case where the second container cloud service invokes a Token acquisition interface of the first container cloud service, providing the new Token to the second container cloud service comprises:
and under the condition that the second container cloud service calls the Token acquisition interface by using the verification information, providing the new Token for the second container cloud service by using the Token acquisition interface.
4. The method for updating data according to claim 1, wherein the sending Token update notification to the second container cloud service using the lifecycle management mechanism comprises:
acquiring a call service list corresponding to the new Token;
and sending the Token update notification to each container cloud service corresponding to the call service list by using the life cycle management mechanism.
5. The data updating method of claim 1, wherein the first container cloud service generates a new Token, comprising:
and generating the new Token corresponding to the target application in the process of starting the target application.
6. A data updating apparatus, comprising:
the container creation module is used for generating a new Token by the first container cloud service;
the update notification module is used for sending Token update notification to the second container cloud service by utilizing a life cycle management mechanism;
a Token providing module, configured to provide the new Token to the second container cloud service when the second container cloud service invokes a Token acquisition interface of the first container cloud service;
the update notification module is specifically configured to send, when the target container corresponding to the new Token is started, the Token update notification to the second container cloud service by automatically triggering a Token update notification script according to a PostStart mode in the lifecycle management mechanism.
7. A data updating apparatus, comprising:
a memory for storing a computer program;
processor for implementing the steps of the data updating method according to any of claims 1 to 5 when executing said computer program.
8. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the data updating method according to any of claims 1 to 5.
CN202010986611.3A 2020-09-18 2020-09-18 Data updating method, device, equipment and readable storage medium Active CN112187753B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010986611.3A CN112187753B (en) 2020-09-18 2020-09-18 Data updating method, device, equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010986611.3A CN112187753B (en) 2020-09-18 2020-09-18 Data updating method, device, equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN112187753A CN112187753A (en) 2021-01-05
CN112187753B true CN112187753B (en) 2023-07-14

Family

ID=73920198

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010986611.3A Active CN112187753B (en) 2020-09-18 2020-09-18 Data updating method, device, equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN112187753B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109063457A (en) * 2018-06-22 2018-12-21 杭州才云科技有限公司 The cross-platform login unified certification interconnection method of one kind, storage medium, electronic equipment

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8468585B2 (en) * 2009-01-05 2013-06-18 International Business Machines Corporation Management of credentials used by software applications
US20180082053A1 (en) * 2016-09-21 2018-03-22 Telefonaktiebolaget Lm Ericsson (Publ) Application token through associated container
CN108848173A (en) * 2018-06-25 2018-11-20 郑州云海信息技术有限公司 A kind of data-updating method, device, equipment and readable storage medium storing program for executing
CN108810029B (en) * 2018-07-23 2021-08-31 宏桥高科技集团有限公司 Authentication system and optimization method between micro-service architecture services
WO2020047710A1 (en) * 2018-09-03 2020-03-12 华为技术有限公司 Login method, token sending method, and device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109063457A (en) * 2018-06-22 2018-12-21 杭州才云科技有限公司 The cross-platform login unified certification interconnection method of one kind, storage medium, electronic equipment

Also Published As

Publication number Publication date
CN112187753A (en) 2021-01-05

Similar Documents

Publication Publication Date Title
US8910138B2 (en) Hot pluggable extensions for access management system
US7370322B1 (en) Method and apparatus for performing online application upgrades in a java platform
CN113032085A (en) Management method, device, server, management system and medium of cloud operating system
CN113190282A (en) Android operating environment construction method and device
US9983988B1 (en) Resuming testing after a destructive event
CN114741233A (en) Quick start method
CN113448686A (en) Resource deployment method and device, electronic equipment and storage medium
CN110008004B (en) Electric power system calculation analysis application virtualization method, device and equipment
US7177934B2 (en) Method and apparatus for providing application specific strategies to a JAVA platform including start and stop policies
CN110569104A (en) Management method and computer storage medium for task training in deep learning system
CN114443239A (en) Method and device for filling container
CN112187753B (en) Data updating method, device, equipment and readable storage medium
WO2015184902A1 (en) Concurrent processing method for intelligent split-screen and corresponding intelligent terminal
CN106972963B (en) Service module starting control method and starting control method after crash restart
CN115562807A (en) Method and system for mounting dynamic equipment for android container in kubernets environment
CN115617459A (en) Method, device and equipment for resource scheduling
CN107885574B (en) Deployment method of virtual machine, service node, control device and control node
CN115113975A (en) Cluster management method and device, electronic equipment and storage medium
CN114610446A (en) Method, device and system for automatically injecting probe
CN114816662A (en) Container arrangement method and system applied to Kubernetes
CN111158783B (en) Environment variable modification method, device and equipment and readable storage medium
CN112711444A (en) Virtualization method and system for power grid monitoring service unit
CN111597021A (en) Method, device and system for realizing application program operation and related equipment
CN111858234A (en) Task execution method, device, equipment and medium
WO2023050947A1 (en) Network upgrade method, electronic device and storage medium

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