CN113805965B - Method, device, equipment and readable medium for installing external plug-in - Google Patents
Method, device, equipment and readable medium for installing external plug-in Download PDFInfo
- Publication number
- CN113805965B CN113805965B CN202111065218.1A CN202111065218A CN113805965B CN 113805965 B CN113805965 B CN 113805965B CN 202111065218 A CN202111065218 A CN 202111065218A CN 113805965 B CN113805965 B CN 113805965B
- Authority
- CN
- China
- Prior art keywords
- plug
- external plug
- external
- container platform
- parameters
- 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
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000013515 script Methods 0.000 claims description 39
- 230000004044 response Effects 0.000 claims description 37
- 238000004590 computer program Methods 0.000 claims description 11
- 238000009434 installation Methods 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 abstract description 23
- 238000011161 development Methods 0.000 abstract description 5
- 230000003044 adaptive effect Effects 0.000 abstract description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 33
- 238000002347 injection Methods 0.000 description 12
- 239000007924 injection Substances 0.000 description 12
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 239000000243 solution Substances 0.000 description 3
- 241000380131 Ammophila arenaria Species 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 241000109539 Conchita Species 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device, equipment and a readable medium for installing an external plug-in based on a container platform, wherein the method comprises the following steps: carrying out API access authentication on the information and parameters of the external plug-in based on the container platform; responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct; responding to the correctness of the parameters of the external plug-in, synchronizing the data of the external plug-in into a plug-in management module in the container platform, and writing the data of the external plug-in into a cache of the plug-in management module; the plug-in templates of the external plug-ins are executed in the container platform to run the external plug-ins. By using the scheme of the invention, the container platform can support external plug-ins, the application range of the plug-ins is improved, the development time of the adaptive plug-ins is saved, the plug-in adaptability of the container platform is enhanced, the functions of plug-in application, plug-in upgrading and the like are enhanced, and the supportable plug-in range of the container platform is greatly improved.
Description
Technical Field
The present invention relates to the field of computers, and more particularly to a method, apparatus, device, and readable medium for container platform based external plug-in installation.
Background
In the container platform, the insert is the basic function. The plug-in is realized by Helm, which is a package management tool of Kubernates, and the package management tool is similar to yum tools used in centros, can quickly search, download and install software packages, can package and uniformly manage a group of K8S resources, and is the best mode of searching, sharing, using and constructing software of Kubernetes.
The packing format of Helm is called Chart, which is a series of files that describe a set of related k8s cluster resources. We call Chart plugin. Chart deployed in a Kubernetes cluster using the palm install command is called Release, and we call plug-in instances.
After the container platform is deployed, the built-in plugins supported by the platform by default are limited, and the built-in plugins are all arranged in plugin management of the container platform after being adapted, so long as the container platform is used and corresponding systems are available, the built-in plugins such as g2, g5, cic and service-mesh can be used, and the systems can be integrated into the container platform through plugin management and used by the container platform. The built-in plug-in can meet most application scenes, however, in the implementation process, a client often has own plug-ins, and the plug-ins of the client also want to be added into the container platform and are on the deployed container platform. If adapted individually to each customer, it is necessary to reissue an item and to re-modify the code to fit, which is obviously impractical in the customer's field. It is not possible for a customer to again wait for a new project to be released while using the container platform. And the mirroring and configuration of the customer's plug-in, etc. are highly adapted to their applications. It is therefore necessary to meet the customer's application scenario, to access the customer's external plug-ins directly into the container platform and to access it on the existing container platform.
Disclosure of Invention
In view of the above, an object of the embodiments of the present invention is to provide a method, an apparatus, a device, and a readable medium for installing an external plug-in based on a container platform, by using the technical solution of the present invention, the container platform can support the external plug-in, increase the application range of the plug-in, save the development time of the adapting plug-in, enhance the plug-in adaptability of the container platform, enhance the functions of plug-in application, plug-in upgrade, etc., and greatly increase the supportable plug-in range of the container platform.
Based on the above object, the present invention provides a method for installing an external plug-in based on a container platform, comprising the steps of:
carrying out API access authentication on the information and parameters of the external plug-in based on the container platform;
responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct;
responding to the correctness of the parameters of the external plug-in, synchronizing the data of the external plug-in into a plug-in management module in the container platform, and writing the data of the external plug-in into a cache of the plug-in management module;
the plug-in templates of the external plug-ins are executed in the container platform to run the external plug-ins.
According to one embodiment of the invention, the API access authentication based on the information and parameters of the external plug-in by the container platform comprises:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
According to one embodiment of the invention, executing an add-in template of an external add-in a container platform to run the external add-in includes:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully.
According to one embodiment of the present invention, further comprising:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
In another aspect of an embodiment of the present invention, there is also provided an apparatus for external plug-in mounting based on a container platform, the apparatus comprising:
the authentication module is configured to carry out API access authentication on the information and parameters of the external plug-in based on the container platform;
the verification module is configured to respond to the success of API access authentication and verify whether the parameters of the external plug-in are correct or not;
the synchronization module is configured to synchronize the data of the external plug-in into the plug-in management module in the container platform and write the data of the external plug-in into the cache of the plug-in management module in response to the correctness of the parameters of the external plug-in;
and an execution module configured to execute the plug-in template of the external plug-in the container platform to run the external plug-in.
According to one embodiment of the invention, the authentication module is further configured to:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
According to one embodiment of the invention, the execution module is further configured to:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully.
According to one embodiment of the invention, the system further comprises an unloading module configured to:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
In another aspect of the embodiments of the present invention, there is also provided a computer apparatus including:
at least one processor; and
and a memory storing computer instructions executable on the processor, the instructions when executed by the processor performing the steps of any of the methods described above.
In another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of any of the methods described above.
The invention has the following beneficial technical effects: according to the method for installing the external plug-in based on the container platform, the API access authentication is carried out on the information and the parameters of the external plug-in based on the container platform; responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct; responding to the correctness of the parameters of the external plug-in, synchronizing the data of the external plug-in into a plug-in management module in the container platform, and writing the data of the external plug-in into a cache of the plug-in management module; the technical scheme of executing the plug-in module of the external plug-in module in the container platform to run the external plug-in module can enable the container platform to support the external plug-in module, improve the application range of the plug-in module, save the development time of the adaptive plug-in module, enhance the plug-in module adaptability of the container platform, enhance the functions of plug-in application, plug-in module upgrading and the like, and greatly improve the supportable plug-in module range of the container platform.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention and that other embodiments may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a method of container platform based external plug-in installation according to one embodiment of the invention;
FIG. 2 is a schematic illustration of an apparatus for container platform based external plug-in installation according to one embodiment of the invention;
FIG. 3 is a schematic diagram of a computer device according to one embodiment of the invention;
fig. 4 is a schematic diagram of a computer-readable storage medium according to one embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention will be described in further detail with reference to the accompanying drawings.
With the above object in view, in a first aspect, embodiments of the present invention provide an embodiment of a method for external plug-in installation based on a container platform. Fig. 1 shows a schematic flow chart of the method.
As shown in fig. 1, the method may include the steps of:
and S1, carrying out API access authentication on the information and parameters of the external plug-in based on the container platform.
The information and parameters of the external plug-in can be written into an external plug-in injection script, and the external plug-in injection script further comprises a parameter injection script, a mirror image injection script and a plug-in template injection script. The function of injecting the script is to add an external plug-in to the container platform, and because the external plug-in comprises a mirror image and a plug-in template, the external plug-in needs to be written into a warehouse of the container platform by two scripts, and the parameters are values which need to be written into the templates when the plug-in is deployed, and if the plug-in template needs some parameters, the external plug-in can be realized by the parameter injection script. Injection scripts are functions outside the container platform that require the token to be acquired first if the token authentication function that relies on the container platform is to be properly executed, and data is to be written to the container platform. The token is fetched from the container platform, the token can be fetched from the UI of the container platform, then written into the injection script, mirror image information and template information are required to be configured in the script, mirror image addresses, template content, description information and the like are written into the script, if the mirror image and the template exist in a physical form, the mirror image and the template can be placed under the same catalog as the script, and then the script is executed. The parameter injection script mainly writes each configuration parameter of the plugin written in the script into a database of the container platform, and the parameters can include a plugin name, plugin description, plugin architecture information, component information (demoyment, demonSet or StatefulSet, etc.) of the plugin, a plugin cleaning command, etc., and the required information can be configured in one time. The mirror injection script and the template injection script require the use of a Harbor upload API function through which the mirror and template located in the same location can be imported into the container platform. After script execution is completed, the plug-in can be seen through a plug-in management module of the container platform, if the plug-in can be seen from the UI, the plug-in script execution is successful, that is, the API access authentication is passed, parameters of an external plug-in can be written into a database managed by the plug-in of the container platform after script execution, and a template and a mirror image which are positioned at the same position are uploaded into a template warehouse and a mirror image warehouse of the container platform.
S2, responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct.
Before the external plug-in is deployed, whether the parameters are correct or not needs to be checked, after the external plug-in enters the container platform, before the external plug-in is deployed, the parameters injected into the database need to be checked, the parameters are ensured to be correct, if abnormal parameters exist, a user is prompted to re-inject the parameters, and the position of the parameter error is pointed out. Because the parameters written into the database by the external plug-in injection script are not necessarily accurate, the user may miss when writing the parameters in the script, and in order to avoid the wrong parameters affecting the plug-in use, the parameters need to be checked before deployment.
And S3, responding to the correctness of the parameters of the external plugin, synchronizing the data of the external plugin to a plugin management module in the container platform, and writing the data of the external plugin into a cache of the plugin management module.
If the parameters of the external plug-in are correct, the plug-in repository and the image repository need to be synchronized in order to synchronize the images and templates injected into the container platform into the plug-in management. The Harbor of the container platform has the function of synchronizing the mirror image and the plug-in template, but after the mirror image and the plug-in template are uploaded to the container platform through the API, the plug-in management module needs to execute one-time synchronization, so that the plug-in management module can find the newly added mirror image and the newly added template. And in the synchronization process, the latest information of the template and the mirror image is written into a cache managed by the plug-in unit so as to be convenient for the next use. The synchronization method is to add a template and a mirror image of the plug-in logic to judge whether the template and the mirror image of the plug-in exist or not, and execute a synchronization command if the template and the mirror image do not exist.
S4, executing the plug-in template of the external plug-in the container platform to run the external plug-in.
After the external plug-in enters the container platform, the external plug-in cannot be guaranteed to be used on the container platform, and a plug-in instance needs to be truly created to prove that the external plug-in is compatible with the container platform. There is a need to use the deployment instance functionality of the container platform to execute templates of external plug-ins, which if plug-in instances can be generated normally, illustrate that the external plug-ins are available and compatible with the container platform. After instance generation, the container platform may run the corresponding application using this instance. It is also necessary to verify the offloading of the instance in order to ensure that all the functions of the external plug-in are available, and if the offloading can be normal, the basic functions of the external plug-in are complete.
After the above steps, an external insert may be used in the container platform. The container platform may use this external plug-in for a range of uses, such as creating applications, creating various types of resources, etc. The external plug-in improves the usability of the container platform, expands the application range of the plug-in, and can enable the container platform to support more plug-ins. Especially when the problems of field plug-in upgrading, image upgrading and the like are encountered, the upgraded plug-in can be directly added into the container platform for use by an external plug-in installation method without depending on a mode of modifying the platform code, and the field plug-in upgrading is greatly improved.
According to the technical scheme, the external plug-in unit can be supported by the container platform, the application range of the plug-in unit is improved, the development time of the adaptive plug-in unit is saved, the plug-in unit adaptability of the container platform is enhanced, the functions of plug-in unit application, plug-in unit upgrading and the like are enhanced, and the supportable plug-in unit range of the container platform is greatly improved.
In a preferred embodiment of the present invention, the API access authentication based on the information and parameters of the external plug-in by the container platform comprises:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
In a preferred embodiment of the present invention, executing the plug-in template of the external plug-in the container platform to run the external plug-in comprises:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully. Executing the plug-in template with the external plug-in injected into the container platform, pulling the corresponding mirror image after the template is executed, and generating a plug-in instance, wherein if the instance operates normally, the external plug-in is already available in the container platform.
In a preferred embodiment of the present invention, further comprising:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available. The case can be normally run and then the uninstallation of the case needs to be verified, so as to ensure that all functions of the external plug-in are available, and if the case can be normally uninstalled, the basic functions of the external plug-in are complete.
The technical scheme of the invention needs to make some improvements for plug-in management of the container platform, so that the plug-in management system not only can support built-in plug-ins, but also can be identified and used when external plug-ins are accessed. The built-in plugin can consider that both the mirror image and the plugin template exist by default, the mirror image warehouse and the plugin template warehouse can expose the mirror image and the plugin template warehouse, the mirror image warehouse and the plugin template warehouse are managed by a Harbor, however, the mirror image and the plugin template of the external plugin may not exist in the container platform, therefore, mirror image synchronization and plugin template synchronization functions need to be added in the plugin management of the container platform, the basic principle is that when the plugin is deployed, if one non-existing mirror image or plugin template exists in the deployment parameters, the mirror image warehouse and the plugin template warehouse are not withdrawn, whether the mirror image warehouse and the plugin template warehouse are updated or not is checked during synchronization, if the mirror image list and the plugin template list are updated synchronously, and the latest mirror image list and plugin template list are updated in the cache at the same time for the next direct use. The method has the greatest characteristic that the built-in plug-in and the external plug-in can be distinguished, the plug-in can be realized by setting a flag bit for the plug-in, and the plug-in finally has corresponding data in a database, so that the flag bit can be set in the database, the value of the flag bit is designed according to the requirement, for example, the flag bit of the built-in plug-in can be set to be 1, and the flag bit of the external plug-in is set to be 0. When the deployed plug-in is a built-in plug-in, the synchronization process is not needed, so that the former logic can be kept, the synchronization time is saved, and when the deployed plug-in is an external plug-in, the synchronization process is executed first, and then other processes of plug-in deployment are executed. The plug-in template execution and plug-in instance uninstallation are original functions of plug-in management, the template execution is to execute the plug-in template in the cluster according to the parameter information and generate a plug-in instance, the plug-in instance can be used for representing the application after running, the plug-in instance uninstallation is to delete the plug-in instance, but the uninstalled instance is not to delete the plug-in template.
According to the technical scheme, the external plug-in unit can be supported by the container platform, the application range of the plug-in unit is improved, the development time of the adaptive plug-in unit is saved, the plug-in unit adaptability of the container platform is enhanced, the functions of plug-in unit application, plug-in unit upgrading and the like are enhanced, and the supportable plug-in unit range of the container platform is greatly improved.
It should be noted that, it will be understood by those skilled in the art that all or part of the procedures in implementing the methods of the above embodiments may be implemented by a computer program to instruct related hardware, and the above program may be stored in a computer readable storage medium, and the program may include the procedures of the embodiments of the above methods when executed. Wherein the storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like. The computer program embodiments described above may achieve the same or similar effects as any of the method embodiments described above.
Furthermore, the method disclosed according to the embodiment of the present invention may also be implemented as a computer program executed by a CPU, which may be stored in a computer-readable storage medium. When executed by a CPU, performs the functions defined above in the methods disclosed in the embodiments of the present invention.
With the above object in mind, in a second aspect of the embodiments of the present invention, there is provided a device for external plug-in mounting based on a container platform, as shown in fig. 2, the device 200 includes:
the authentication module 201, the authentication module 201 is configured to perform API access authentication on the information and parameters of the external plug-in based on the container platform;
the verification module 202, the verification module 202 is configured to respond to the success of the API access authentication, and verify whether the parameters of the external plug-in are correct;
the synchronization module 203 is configured to synchronize the data of the external plug-in into the plug-in management module in the container platform and write the data of the external plug-in into the cache of the plug-in management module in response to the correctness of the parameters of the external plug-in;
an execution module 204, the execution module 204 configured to execute a plug-in template of an external plug-in the container platform to run the external plug-in.
In a preferred embodiment of the invention, the authentication module 201 is further configured to:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
In a preferred embodiment of the present invention, the execution module 204 is further configured to:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully.
In a preferred embodiment of the invention, the system further comprises an unloading module configured to:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
Based on the above object, a third aspect of the embodiments of the present invention proposes a computer device. Fig. 3 is a schematic diagram of an embodiment of a computer device provided by the present invention. As shown in fig. 3, an embodiment of the present invention includes the following means: at least one processor 21; and a memory 22, the memory 22 storing computer instructions 23 executable on the processor, the instructions when executed by the processor performing the method of:
carrying out API access authentication on the information and parameters of the external plug-in based on the container platform;
responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct;
responding to the correctness of the parameters of the external plug-in, synchronizing the data of the external plug-in into a plug-in management module in the container platform, and writing the data of the external plug-in into a cache of the plug-in management module;
the plug-in templates of the external plug-ins are executed in the container platform to run the external plug-ins.
In a preferred embodiment of the present invention, the API access authentication based on the information and parameters of the external plug-in by the container platform comprises:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
In a preferred embodiment of the present invention, executing the plug-in template of the external plug-in the container platform to run the external plug-in comprises:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully.
In a preferred embodiment of the present invention, further comprising:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
Based on the above object, a fourth aspect of the embodiments of the present invention proposes a computer-readable storage medium. Fig. 4 is a schematic diagram of an embodiment of a computer-readable storage medium provided by the present invention. As shown in fig. 4, the computer-readable storage medium 31 stores a computer program 32 that, when executed by a processor, performs the following method:
carrying out API access authentication on the information and parameters of the external plug-in based on the container platform;
responding to the success of API access authentication, and verifying whether the parameters of the external plug-in are correct;
responding to the correctness of the parameters of the external plug-in, synchronizing the data of the external plug-in into a plug-in management module in the container platform, and writing the data of the external plug-in into a cache of the plug-in management module;
the plug-in templates of the external plug-ins are executed in the container platform to run the external plug-ins.
In a preferred embodiment of the present invention, the API access authentication based on the information and parameters of the external plug-in by the container platform comprises:
acquiring a token required by API access authentication from a container platform;
writing the acquired token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and in response to the external plugin being checked in the UI of the container platform, determining that the API access authentication of the information and the parameters of the external plugin is successful.
In a preferred embodiment of the present invention, executing the plug-in template of the external plug-in the container platform to run the external plug-in comprises:
executing the template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after executing the template;
in response to the instance of the external plug-in being able to be generated after execution of the template, it is determined that the external plug-in was installed successfully.
In a preferred embodiment of the present invention, further comprising:
in response to generating the instance of the external plug-in the container platform, uninstalling the instance of the external plug-in;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
Furthermore, the method disclosed according to the embodiment of the present invention may also be implemented as a computer program executed by a processor, which may be stored in a computer-readable storage medium. The above-described functions defined in the methods disclosed in the embodiments of the present invention are performed when the computer program is executed by a processor.
Furthermore, the above-described method steps and system units may also be implemented using a controller and a computer-readable storage medium storing a computer program for causing the controller to implement the above-described steps or unit functions.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or general purpose or special purpose processor. Further, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk, blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The foregoing embodiment of the present invention has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, where the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the invention, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the invention, and many other variations of the different aspects of the embodiments of the invention as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present invention.
Claims (6)
1. A method of external plug-in installation based on a container platform, comprising the steps of:
performing API access authentication on the information and parameters of the external plug-in based on the container platform, wherein performing API access authentication on the information and parameters of the external plug-in based on the container platform includes: acquiring a token required by the API access authentication in the container platform, writing the acquired token into a script with information and parameters of the external plugin, executing the script in the container platform, and determining that the API access authentication of the information and parameters of the external plugin is successful in response to the external plugin being seen through the UI of the container platform;
responding to the success of the API access authentication, and verifying whether the parameters of the external plug-in are correct;
synchronizing the data of the external plug-in into a plug-in management module in the container platform in response to the correctness of the parameters of the external plug-in, and writing the data of the external plug-in into a cache of the plug-in management module, wherein the data of the external plug-in comprises a mirror image and a template of the external plug-in;
executing the plug-in template of the external plug-in the container platform to run the external plug-in, wherein executing the plug-in template of the external plug-in the container platform to run the external plug-in comprises: executing the template of the external plug-in the container platform, judging whether the instance of the external plug-in can be generated after the template is executed, and determining that the external plug-in is successfully installed in response to the instance of the external plug-in can be generated after the template is executed.
2. The method as recited in claim 1, further comprising:
unloading the instance of the external plug-in response to generating the instance of the external plug-in the container platform;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
3. An apparatus for external package installation based on a container platform, the apparatus comprising:
an authentication module configured to perform API access authentication based on information and parameters of the external plug-in on the container platform, the authentication module further configured to: acquiring a token required by the API access authentication in the container platform, writing the acquired token into a script with information and parameters of the external plugin, executing the script in the container platform, and determining that the API access authentication of the information and parameters of the external plugin is successful in response to the external plugin being seen through the UI of the container platform;
a verification module configured to verify whether parameters of the external plug-in are correct in response to the API access authentication being successful;
the synchronization module is configured to synchronize the data of the external plug-in into a plug-in management module in the container platform and write the data of the external plug-in into a cache of the plug-in management module in response to the correctness of the parameters of the external plug-in, wherein the data of the external plug-in comprises a mirror image and a template of the external plug-in;
an execution module configured to execute a plug-in template of the external plug-in the container platform to run the external plug-in, the execution module further configured to: executing the template of the external plug-in the container platform, judging whether the instance of the external plug-in can be generated after the template is executed, and determining that the external plug-in is successfully installed in response to the instance of the external plug-in can be generated after the template is executed.
4. The apparatus of claim 3, further comprising an offloading module configured to:
unloading the instance of the external plug-in response to generating the instance of the external plug-in the container platform;
in response to an instance of the external plug-in being unloaded successfully, it is determined that all functionality of the external plug-in is available.
5. A computer device, comprising:
at least one processor; and
a memory storing computer instructions executable on the processor, which when executed by the processor, perform the steps of the method of any one of claims 1-2.
6. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method of any one of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111065218.1A CN113805965B (en) | 2021-09-11 | 2021-09-11 | Method, device, equipment and readable medium for installing external plug-in |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111065218.1A CN113805965B (en) | 2021-09-11 | 2021-09-11 | Method, device, equipment and readable medium for installing external plug-in |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113805965A CN113805965A (en) | 2021-12-17 |
| CN113805965B true CN113805965B (en) | 2023-12-29 |
Family
ID=78895051
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111065218.1A Active CN113805965B (en) | 2021-09-11 | 2021-09-11 | Method, device, equipment and readable medium for installing external plug-in |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113805965B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114968406B (en) * | 2022-05-27 | 2023-10-13 | 北京青云科技股份有限公司 | Plug-in management method and device, electronic equipment and storage medium |
| CN115061741B (en) * | 2022-05-31 | 2024-06-14 | 北京奇艺世纪科技有限公司 | Target plug-in operation method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1493975A (en) * | 2002-11-01 | 2004-05-05 | 尹启凤 | Active layout method of computer external equipment |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| CN104679572A (en) * | 2015-03-26 | 2015-06-03 | 北京神舟航天软件技术有限公司 | Plug-in support method based on preloading mechanism |
| CN105933322A (en) * | 2016-05-31 | 2016-09-07 | 北京小米移动软件有限公司 | Plug-in service obtaining method, and plug-in service providing method and device |
| CN108632329A (en) * | 2017-03-24 | 2018-10-09 | 华为技术有限公司 | A kind of access method and device of third side plug |
| CN110569089A (en) * | 2019-09-11 | 2019-12-13 | 苏州浪潮智能科技有限公司 | Plug-in expansion method, device and storage medium for management platform |
| CN110826049A (en) * | 2019-11-14 | 2020-02-21 | 北京京航计算通讯研究所 | Single sign-on implementation system based on intelligent enterprise portal |
| CN112328362A (en) * | 2020-11-03 | 2021-02-05 | 浪潮云信息技术股份公司 | Method for realizing function calculation service based on container technology |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9900317B2 (en) * | 2016-02-25 | 2018-02-20 | Red Hat, Inc. | Access guards for multi-tenant logging |
| US20190129734A1 (en) * | 2017-10-31 | 2019-05-02 | Ca, Inc. | Data collection workflow extension |
| US20200379781A1 (en) * | 2019-05-28 | 2020-12-03 | Netapp, Inc. | Methods and systems for plugin development in a networked computing environment |
| US11153295B2 (en) * | 2019-08-28 | 2021-10-19 | Vmware, Inc. | Authentication of plugins in a virtualized computing environment |
-
2021
- 2021-09-11 CN CN202111065218.1A patent/CN113805965B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1493975A (en) * | 2002-11-01 | 2004-05-05 | 尹启凤 | Active layout method of computer external equipment |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| CN104679572A (en) * | 2015-03-26 | 2015-06-03 | 北京神舟航天软件技术有限公司 | Plug-in support method based on preloading mechanism |
| CN105933322A (en) * | 2016-05-31 | 2016-09-07 | 北京小米移动软件有限公司 | Plug-in service obtaining method, and plug-in service providing method and device |
| CN108632329A (en) * | 2017-03-24 | 2018-10-09 | 华为技术有限公司 | A kind of access method and device of third side plug |
| CN110569089A (en) * | 2019-09-11 | 2019-12-13 | 苏州浪潮智能科技有限公司 | Plug-in expansion method, device and storage medium for management platform |
| CN110826049A (en) * | 2019-11-14 | 2020-02-21 | 北京京航计算通讯研究所 | Single sign-on implementation system based on intelligent enterprise portal |
| CN112328362A (en) * | 2020-11-03 | 2021-02-05 | 浪潮云信息技术股份公司 | Method for realizing function calculation service based on container technology |
Non-Patent Citations (1)
| Title |
|---|
| OpenStack身份认证安全性分析与改进;吴玉宁;王欢;苏伟;严晔;秦雪;;长春理工大学学报(自然科学版)(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113805965A (en) | 2021-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107506221B (en) | Application program upgrading method, device and equipment | |
| CN113805965B (en) | Method, device, equipment and readable medium for installing external plug-in | |
| US10216510B2 (en) | Silent upgrade of software with dependencies | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN111309336B (en) | Deployment method and device of distributed application | |
| CN107368331B (en) | Configuration file updating method and device for application program | |
| CN105302563A (en) | Plug-in method and system for mobile application service | |
| CN103714287A (en) | Method and device for obtaining temporary Root authority | |
| CN104932887B (en) | The plug-in management method and plateform system of a kind of plateform system | |
| WO2017166448A1 (en) | Kernel vulnerability repair method and device | |
| WO2016082450A1 (en) | Method for upgrading user terminal, and user terminal | |
| AU2021204593A1 (en) | Methods and apparatuses for installing device application | |
| CN104461621A (en) | Attribute information updating method and device | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| US9703848B2 (en) | Caching linked queries for optimized compliance management | |
| CN111813379A (en) | Application deployment method and device, electronic equipment and computer readable storage medium | |
| US20170199733A1 (en) | Method for terminal to update operating system, terminal and system | |
| CN112181467A (en) | Method and device for upgrading memory firmware of terminal, terminal and storage medium | |
| CN117008934A (en) | Method, device, equipment and medium for automatically making mirror image of information creation operating system | |
| CN116048476A (en) | Command line tool execution method, device, medium and equipment | |
| CN110502251A (en) | Using installation method and device | |
| CN114398155A (en) | Method and system for configuring automatic deployment pipeline of application program | |
| CN113886008A (en) | Virtual machine management method, system, device and medium | |
| CN110362320B (en) | Command implementation method and device of application development platform | |
| CN111625225A (en) | Program specified data output method and device |
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 |