CN113805965A - Method, device and equipment for installing external plug-in and readable medium - Google Patents
Method, device and equipment for installing external plug-in and readable medium Download PDFInfo
- Publication number
- CN113805965A CN113805965A CN202111065218.1A CN202111065218A CN113805965A CN 113805965 A CN113805965 A CN 113805965A CN 202111065218 A CN202111065218 A CN 202111065218A CN 113805965 A CN113805965 A CN 113805965A
- Authority
- CN
- China
- Prior art keywords
- plug
- external plug
- external
- container platform
- template
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000004044 response Effects 0.000 claims abstract description 41
- 238000013515 script Methods 0.000 claims description 39
- 238000009434 installation Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 11
- 238000012795 verification Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 abstract description 24
- 238000011161 development Methods 0.000 abstract description 5
- 239000008186 active pharmaceutical agent Substances 0.000 description 34
- 238000002347 injection Methods 0.000 description 11
- 239000007924 injection Substances 0.000 description 11
- 230000008569 process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 241000380131 Ammophila arenaria Species 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 239000000243 solution Substances 0.000 description 3
- 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
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000003044 adaptive 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
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/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: performing 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 or not; in response to the correct parameters of the external plug-in, synchronizing the data of the external plug-in to 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; an insert template of the external insert is executed in the container platform to run the external insert. By using the scheme of the invention, the container platform can support the external plug-in, the application range of the plug-in is improved, the development time of adapting the plug-in 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 plug-in range which can be supported by 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 a basic function. The plug-in is realized through Helm, the Helm is a package management tool of Kubernates, the package management tool is similar to an yum tool used in Centos, a software package can be quickly searched, downloaded and installed, the Helm can package and uniformly manage a group of K8S resources, and the plug-in is an optimal mode for searching, sharing, using and constructing software of Kubernees.
Helm's packaging format is called Chart, which is a series of files that describe a set of related k8s cluster resources. We call Chart plug-in. Chart deployed in a Kubernets cluster using the helm install command is called Release, and we call a plug-in instance.
After the container platform is deployed, the built-in plug-ins supported by the platform by default are limited, the built-in plug-ins are built into the plug-in management of the container platform after being adapted, as long as the container platform is used and corresponding systems exist, the built-in plug-ins can be used, such as g2, g5, cic, service-mesh and the like, and the systems can be integrated into the container platform through the plug-in management and can be used by the container platform. The built-in plug-ins can satisfy most application scenarios, however, in the implementation process, a client often has its own plug-ins, and the client's plug-ins also want to join the container platform and are on the deployed container platform. If each client is individually adapted, it is obviously impractical on the client site to reissue a project and re-modify the code to adapt. The customer is already using the container platform and cannot wait again for a new project to be released. And the mirroring, configuration, etc. of the customer's plug-ins are highly compatible with their applications. Therefore, the application scenarios of the client need to be satisfied, and the external plug-ins of the client are directly accessed into the container platform and are accessed on the existing container platform.
Disclosure of Invention
In view of this, an embodiment of the present invention provides a method, an apparatus, a device, and a readable medium for installing an external plug-in based on a container platform, and by using the technical solution of the present invention, the container platform can support the external plug-in, the application range of the plug-in is increased, the development time of an adaptive plug-in is saved, the plug-in adaptability of the container platform is enhanced, the functions of plug-in application, plug-in upgrade, and the like are enhanced, and the range of the plug-ins that can be supported by the container platform is greatly increased.
In view of the above, the present invention provides a method for external plug-in installation based on a container platform, comprising the following steps:
performing 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 or not;
in response to the correct parameters of the external plug-in, synchronizing the data of the external plug-in to 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;
an insert template of the external insert is executed in the container platform to run the external insert.
According to one embodiment of the invention, the API access authentication of the information and the parameters of the external plug-in based on the container platform comprises the following steps:
acquiring a token required by API access authentication in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
According to one embodiment of the present invention, executing an insert template of an external insert in a container platform to run the external insert comprises:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template.
According to an embodiment of the present invention, further comprising:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full 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 perform API access authentication on the information and the 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 respond to the correct parameters of the external plug-in, synchronize the data of the external plug-in to 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;
an execution module configured to execute a plug-in template of an 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 in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
According to one embodiment of the invention, the execution module is further configured to:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template.
According to an embodiment of the invention, further comprising an offload module configured to:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full functionality of the external plug-in is available.
In another aspect of an embodiment of the present invention, there is also provided a computer apparatus including:
at least one processor; and
a memory storing computer instructions executable on the processor, the instructions when executed by the processor implementing 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 one of the above-mentioned methods.
The invention has the following beneficial technical effects: according to the method for installing the external plug-in based on the container platform, API access authentication is carried out 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 or not; in response to the correct parameters of the external plug-in, synchronizing the data of the external plug-in to 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 that the plug-in template of the external plug-in is executed in the container platform to operate the external plug-in can enable the container platform to support the external plug-in, improve the application range of the plug-in, save the development time of adapting the plug-in, enhance the plug-in adaptability of the container platform, enhance the functions of plug-in application, plug-in upgrading and the like, and greatly improve the plug-in range which can be supported by the container platform.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
FIG. 1 is a schematic flow chart diagram of a method of container platform based external add-on installation in accordance with one embodiment of the present invention;
FIG. 2 is a schematic view of an apparatus for external card installation based on a container platform according to one embodiment of the present invention;
FIG. 3 is a schematic diagram of a computer device according to one embodiment of the present invention;
fig. 4 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present 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 are described in further detail with reference to the accompanying drawings.
In view of the above objects, a first aspect of embodiments of the present invention proposes an embodiment of a method for external plug-in mounting based on a container platform. Fig. 1 shows a schematic flow diagram of the method.
As shown in fig. 1, the method may include the steps of:
s1 carries 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 the external plug-in injection script, and the external plug-in injection script 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, because the external plug-in includes a mirror image and a plug-in template, two scripts are needed to write the external plug-in into a warehouse of the container platform, the parameter is a value which needs to be written into the template when the plug-in is deployed, and if the plug-in template needs some parameters, the parameter injection script can be used for realizing. The injection script is a function outside the container platform, and if the correct operation needs to depend on the token authentication function of the container platform, data is written into the container platform, and the token needs to be acquired first. The token is taken from the container platform firstly, the token can be taken from a UI of the container platform, then the token is written into the injection script, mirror image information and template information are also required to be configured in the script, mirror image addresses, template contents, description information and the like are written into the script, if the mirror image and the template exist in an entity form, the mirror image and the template can be placed in the same directory as the script, and then the script is executed. The parameter injection script mainly writes each configuration parameter of the plug-in written in the script into a database of the container platform, the parameter may include a plug-in name, a plug-in description, plug-in architecture information, component information (Deployment, DemonSet or stateful set, etc.) of the plug-in, a plug-in cleaning command, and the like, and may configure the required information in one time. The image injection script and the template injection script need to use an uploading API function of the Harbor, and the image and the template in the same position can be transmitted to the container platform through the uploading API. After the script is executed, the plug-in can be seen through the plug-in management module of the container platform, if the plug-in can be seen from the UI, the plug-in script is successfully executed, that is, the API access authentication is passed, after the script is executed, the parameters of the external plug-in can be written into a database managed by the plug-in of the container platform, and the template and the 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 responds to the API access authentication success, and whether the parameters of the external plug-in are correct or not is verified.
Before the external plug-in is deployed, whether the parameters are correct needs to be checked, after the external plug-in enters the container platform, the parameters injected into the database need to be checked before the deployment is started, the parameters are ensured to be correct, if abnormal parameters exist, a user is prompted to inject the parameters again, and the position of the parameter error is pointed out. Because the parameters written into the database by the script injected by the external plug-in are not necessarily accurate, the user may make a mistake when writing the parameters into the script, and in order to avoid the wrong parameters from affecting the use of the plug-in, the parameters need to be checked before deployment.
S3 responds to the correct parameters of the external plug-in, synchronizes the data of the external plug-in to the plug-in management module in the container platform, and writes the data of the external plug-in into the cache of the plug-in management module.
If the parameters of the external plug-in are correct, the plug-in repository and the mirror repository need to be synchronized in order to synchronize the mirror and the template 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, synchronization is required to be executed once at the plug-in management module, so that the plug-in management module can find the newly added mirror image and the newly added plug-in template, and in the plug-in management, the built-in plug-in acquires the mirror image and the newly added plug-in template through cache, and because the system runs, the mirror image and the template information are written into the cache, the data can be directly taken from the cache, but the newly added data are not cached again, and the logic of one-step synchronization needs to be added. 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 so as to be convenient for the next use. The synchronization method is to add a template and a mirror image of a judgment plug-in the logic of the built-in plug-in, and if the template and the mirror image do not exist, the synchronization command is executed.
S4 executes 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, it cannot be guaranteed to be used on the container platform, and an instance of the plug-in needs to be really created to prove that the external plug-in is compatible with the container platform. The template for executing the external plug-in using the deployment instance function of the container platform is required, and if the plug-in instance can be normally generated, the plug-in is indicated to be available and compatible with the container platform. After the instance is generated, the container platform may use the instance to run the corresponding application. It is also necessary to verify that the offload of the instance is to ensure that all functions of the external plug-in are available, and if normal offload is possible, 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 resources of various types, and so forth. The external plug-in improves the usability of the container platform, expands the application range of the plug-in and enables the container platform to support more plug-ins. Particularly, when the problems of field plug-in upgrading, mirror image upgrading and the like occur, the upgraded plug-in can be added into the container platform for use directly through an external plug-in installation method without depending on a mode of modifying a platform code, and the field plug-in upgrading is greatly improved.
By the technical scheme, the container platform can support the external plug-in, the application range of the plug-in is enlarged, the development time of adapting the plug-in 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 plug-in range which can be supported by the container platform is greatly enlarged.
In a preferred embodiment of the present invention, the API access authentication of the information and parameters of the external plug-in based on the container platform comprises:
acquiring a token required by API access authentication in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
In a preferred embodiment of the present invention, executing an insert template of an external insert in a container platform to run the external insert comprises:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template. And executing the plug-in template on the external plug-in which is 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 runs normally, the case shows that the external plug-in is available in the container platform.
In a preferred embodiment of the present invention, the method further comprises:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full functionality of the external plug-in is available. The uninstalling of the instance is also verified after the instance can normally run, in order to ensure that all functions of the external plug-in are available, and if the uninstalling is normally possible, the basic functions of the external plug-in are complete.
According to the technical scheme, some transformation needs to be carried out on the plug-in management of the container platform, so that the container platform can support the built-in plug-in and can be identified and used when an external plug-in is accessed. The built-in plug-in may consider that its mirror and plug-in template are both present by default and may be exposed by both a mirror repository and a plug-in template repository, which are managed by Harbor, however, the mirror and plug-in template of the external plug-in may not exist in the container platform, and for this reason, mirror synchronization and plug-in template synchronization functions need to be added in the plug-in management of the container platform, the basic principle is that when the plug-in is deployed, if a non-existent mirror image or plug-in template exists in the deployment parameters, the plug-in is not quitted first, but synchronizes the mirror repository and the plug-in template repository, checks if both repositories are updated during synchronization, and if the image list and the plug-in template list are updated, the latest image list and the latest plug-in template list are synchronized, and the latest image list and the latest plug-in template list are updated into a cache for the next direct use. The biggest characteristic of the synchronization is that the built-in plug-in and the external plug-in can be distinguished by setting a flag bit for the plug-in, and the plug-in finally has a corresponding data in the database, so that the flag bit can be set in the database, the value of the flag bit is designed according to requirements, for example, the flag bit of the built-in plug-in is set to be 1, and the flag bit of the external plug-in is set to be 0. When the deployed plug-in is the built-in plug-in, the synchronization process is not needed, so that the previous logic can be maintained, the synchronization time is saved, and when the deployed plug-in is the external plug-in, the synchronization process is executed first, and then other processes of the plug-in deployment are executed. The plug-in template execution and plug-in instance unloading are original functions of plug-in management, the plug-in template execution is to execute the plug-in template in a cluster according to parameter information and generate a plug-in instance, the plug-in instance can be used after running, the plug-in instance unloading is to delete the plug-in instance, but the unloading instance is not to delete the plug-in template.
By the technical scheme, the container platform can support the external plug-in, the application range of the plug-in is enlarged, the development time of adapting the plug-in 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 plug-in range which can be supported by the container platform is greatly enlarged.
It should be noted that, as will be understood by those skilled in the art, all or part of the processes in the methods of the above embodiments may be implemented by instructing relevant hardware through a computer program, and the above programs may be stored in a computer-readable storage medium, and when executed, the programs may include the processes of the embodiments of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described method embodiments.
Furthermore, the method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU, and the computer program may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention.
In view of the above objects, a second aspect of an embodiment of the present invention proposes an apparatus for external card installation based on a container platform, as shown in fig. 2, the apparatus 200 comprising:
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, the synchronization module 203 is configured to respond to the parameter correctness of the external plug-in, synchronize the data of the external plug-in to 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;
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 present invention, the authentication module 201 is further configured to:
acquiring a token required by API access authentication in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
In a preferred embodiment of the present invention, the execution module 204 is further configured to:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template.
In a preferred embodiment of the present invention, the apparatus further comprises an unloading module configured to:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full functionality of the external plug-in is available.
In view of the above object, a third aspect of the embodiments of the present invention provides 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 implementing the method of:
performing 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 or not;
in response to the correct parameters of the external plug-in, synchronizing the data of the external plug-in to 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;
an insert template of the external insert is executed in the container platform to run the external insert.
In a preferred embodiment of the present invention, the API access authentication of the information and parameters of the external plug-in based on the container platform comprises:
acquiring a token required by API access authentication in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
In a preferred embodiment of the present invention, executing an insert template of an external insert in a container platform to run the external insert comprises:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template.
In a preferred embodiment of the present invention, the method further comprises:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full functionality of the external plug-in is available.
In view of 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 illustrating 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 method of:
performing 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 or not;
in response to the correct parameters of the external plug-in, synchronizing the data of the external plug-in to 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;
an insert template of the external insert is executed in the container platform to run the external insert.
In a preferred embodiment of the present invention, the API access authentication of the information and parameters of the external plug-in based on the container platform comprises:
acquiring a token required by API access authentication in a container platform;
writing the obtained token into a script with information and parameters of an external plug-in, and executing the script in a container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed in the UI of the container platform.
In a preferred embodiment of the present invention, executing an insert template of an external insert in a container platform to run the external insert comprises:
executing a template of the external plug-in the container platform, and judging whether an instance of the external plug-in can be generated after the template is executed;
the external plug-in installation is determined to be successful in response to an instance of the external plug-in being able to be generated after execution of the template.
In a preferred embodiment of the present invention, the method further comprises:
in response to generating an instance of an external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance of the external plug-in being successfully uninstalled, it is determined that full functionality of the external plug-in is available.
Furthermore, the methods disclosed according to embodiments 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. Which when executed by a processor performs the above-described functions defined in the methods disclosed in embodiments of the invention.
Further, the above method steps and system elements may also be implemented using a controller and a computer readable storage medium for storing a computer program for causing the controller to implement the functions of the above steps or elements.
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 disclosed embodiments of the present invention.
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 place 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 a general-purpose or special-purpose processor. Also, 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 present 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 of the invention 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 numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits 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 instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A method of external card 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;
in response to the API access authentication being successful, verifying whether the parameters of the external plug-in are correct;
in response to the parameter of the external plug-in is correct, synchronizing the data of the external plug-in to 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;
executing a plug-in template of the external plug-in the container platform to run the external plug-in.
2. The method of claim 1, wherein performing API access authentication for the information and parameters of the external plug-in based on the container platform comprises:
acquiring a token required by the API access authentication in the container platform;
writing the obtained token into a script with information and parameters of the external plug-in, and executing the script in the container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed through the UI of the container platform.
3. The method of claim 1, wherein executing a 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 the instance of the external plug-in can be generated after the template is executed;
determining that the external plugin installation is successful in response to being able to generate an instance of the external plugin after execution of a template.
4. The method of claim 3, further comprising:
in response to generating the instance of the external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance offload of the external plug-in being successful, determining that full functionality of the external plug-in is available.
5. An apparatus for external package installation based on a container platform, the apparatus comprising:
the authentication module is configured to perform API access authentication on the information and parameters of the external plug-in based on 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;
a synchronization module configured to synchronize data of the external plug-in to a plug-in management module in the container platform and write the data of the external plug-in to a cache of the plug-in management module in response to a parameter of the external plug-in being correct;
an execution module configured to execute a plug-in template of the external plug-in the container platform to run the external plug-in.
6. The apparatus of claim 5, wherein the authentication module is further configured to:
acquiring a token required by the API access authentication in the container platform;
writing the obtained token into a script with information and parameters of the external plug-in, and executing the script in the container platform;
and determining that the API access authentication of the information and the parameters of the external plug-in is successful in response to the external plug-in being viewed through the UI of the container platform.
7. The apparatus of claim 5, wherein the execution module is further configured to:
executing the template of the external plug-in the container platform, and judging whether the instance of the external plug-in can be generated after the template is executed;
determining that the external plugin installation is successful in response to being able to generate an instance of the external plugin after execution of a template.
8. The apparatus of claim 7, further comprising an offload module configured to:
in response to generating the instance of the external plug-in the container platform, offloading the instance of the external plug-in;
in response to the instance offload of the external plug-in being successful, determining that full functionality of the external plug-in is available.
9. A computer device, comprising:
at least one processor; and
a memory storing computer instructions executable on the processor, the instructions when executed by the processor implementing the steps of the method of any one of claims 1 to 4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
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 true CN113805965A (en) | 2021-12-17 |
| CN113805965B 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) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114968406A (en) * | 2022-05-27 | 2022-08-30 | 北京青云科技股份有限公司 | Plug-in management method and device, electronic equipment and storage medium |
| CN115061741A (en) * | 2022-05-31 | 2022-09-16 | 北京奇艺世纪科技有限公司 | Target plug-in operation method and device, electronic equipment and storage medium |
Citations (12)
| 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 |
| US20170250988A1 (en) * | 2016-02-25 | 2017-08-31 | Red Hat, Inc. | Access guards for multi-tenant logging |
| CN108632329A (en) * | 2017-03-24 | 2018-10-09 | 华为技术有限公司 | A kind of access method and device of third side plug |
| US20190129734A1 (en) * | 2017-10-31 | 2019-05-02 | Ca, Inc. | Data collection workflow extension |
| 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 |
| US20200379781A1 (en) * | 2019-05-28 | 2020-12-03 | Netapp, Inc. | Methods and systems for plugin development in a networked computing environment |
| CN112328362A (en) * | 2020-11-03 | 2021-02-05 | 浪潮云信息技术股份公司 | Method for realizing function calculation service based on container technology |
| US20210067504A1 (en) * | 2019-08-28 | 2021-03-04 | Vmware, Inc. | Authentication of plugins in a virtualized computing environment |
-
2021
- 2021-09-11 CN CN202111065218.1A patent/CN113805965B/en active Active
Patent Citations (12)
| 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 |
| US20170250988A1 (en) * | 2016-02-25 | 2017-08-31 | Red Hat, Inc. | Access guards for multi-tenant logging |
| 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 |
| 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 |
| US20210067504A1 (en) * | 2019-08-28 | 2021-03-04 | Vmware, Inc. | Authentication of plugins in a virtualized computing environment |
| 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身份认证安全性分析与改进", 长春理工大学学报(自然科学版), no. 05 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114968406A (en) * | 2022-05-27 | 2022-08-30 | 北京青云科技股份有限公司 | Plug-in management method and device, electronic equipment and storage medium |
| CN114968406B (en) * | 2022-05-27 | 2023-10-13 | 北京青云科技股份有限公司 | Plug-in management method and device, electronic equipment and storage medium |
| CN115061741A (en) * | 2022-05-31 | 2022-09-16 | 北京奇艺世纪科技有限公司 | Target plug-in operation method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113805965B (en) | 2023-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107506221B (en) | Application program upgrading method, device and equipment | |
| CN108845812B (en) | Plug-in updating method, device, computer equipment and storage medium | |
| JP3385590B2 (en) | Computer-readable recording medium recording a software update program for use when updating a computer program through a computer network | |
| US6202207B1 (en) | Method and a mechanism for synchronized updating of interoperating software | |
| US10216510B2 (en) | Silent upgrade of software with dependencies | |
| CN113805965B (en) | Method, device, equipment and readable medium for installing external plug-in | |
| CN111309336B (en) | Deployment method and device of distributed application | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| US20130318512A1 (en) | Hot Pluggable Extensions for Access Management System | |
| 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 | |
| CN113721914A (en) | Parallel compiling method, device and equipment based on container and readable medium | |
| CN104932887A (en) | Plug-in management method of platform system and platform system | |
| US8161520B1 (en) | Methods and systems for securing a system in an adaptive computer environment | |
| CN111880828B (en) | Method for upgrading multi-board driver in batch in Secure Boot environment | |
| CN113608831A (en) | Plug-in instance management method, system, storage medium and equipment | |
| CN111857744A (en) | Installation method, system, equipment and medium of super-fusion system | |
| CN112114837B (en) | Firmware updating method and camera | |
| CN110955440B (en) | Screen locking application separation upgrading method, device, equipment and computer readable medium | |
| CN116339786A (en) | Method, device and equipment for starting baseline firmware upgrade | |
| CN108762771B (en) | Plug-in unloading method and electronic terminal | |
| CN113568649A (en) | Software product upgrading method, device, equipment and readable medium | |
| CN113886218A (en) | Method, device and equipment for verifying BIOS refreshing and readable medium | |
| CN116643728A (en) | Software construction method, computer readable storage medium and electronic 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 |