CN114625347A

CN114625347A - Storage system SDK docking method, device, equipment and storage medium

Info

Publication number: CN114625347A
Application number: CN202210327779.2A
Authority: CN
Inventors: 武文斌; 巫春梅; 黄海鹏; 李晓萌
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-03-29
Filing date: 2022-03-29
Publication date: 2022-06-14

Abstract

The utility model provides a method, a device, equipment, a storage medium and a program product for the butt joint of a storage system SDK, which relate to the technical field of cloud computing, and the butt joint method of the storage system SDK comprises the following steps: acquiring an interface class of a performance monitoring system; traversing preset interface classes in a preset configuration file according to the interface classes, and acquiring preset implementation class information corresponding to the preset interface classes when the interface classes are matched with the preset interface classes; acquiring an interface docking method according to the preset implementation class information instantiation object; and according to the interface docking method, docking with the performance monitoring system.

Description

Storage system SDK docking method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to a method, an apparatus, a device, a storage medium, and a program product for docking an SDK in a storage system.

Background

With diversification of a distributed system, complexity of service capability and importance of full-link monitoring of service processing, different monitoring systems have different data acquisition modes, when acquisition logic of the monitoring systems is changed or the monitoring systems are replaced, an application layer needs to be modified in a matched mode, so that the difficulty of changing and popularizing the monitoring systems is high, a new and old alternative process exists for a long time, and meanwhile, the application cannot be concentrated on service development and is interfered by change of infrastructure.

Disclosure of Invention

In view of the above problems, the present disclosure provides a method, an apparatus, a device, a storage medium, and a program product for docking a storage system SDK, which aim to solve the problem of difficulty in data acquisition and docking.

According to a first aspect of the present disclosure, there is provided a method for interfacing a storage system SDK, including:

acquiring an interface class of a performance monitoring system;

traversing preset interface classes in a preset configuration file according to the interface classes, and acquiring preset implementation class information corresponding to the preset interface classes when the interface classes are matched with the preset interface classes;

and according to the interface docking method, docking with the performance monitoring system.

According to the embodiment of the disclosure, the step of traversing the preset interface class in the preset configuration file according to the interface class includes:

acquiring a corresponding thread class loader according to the interface class;

and traversing the preset interface class in the preset configuration file through the thread class loader.

According to the embodiment of the present disclosure, traversing the preset interface class in the preset configuration file according to the interface class further includes:

when the interface class cannot be matched with the preset interface class, constructing a new interface class and corresponding new implementation class information corresponding to the interface class;

and caching the new interface class and the new implementation class information to a preset configuration file.

According to the embodiment of the disclosure, a plurality of preset configuration files are provided;

according to the interface class, the step of traversing the preset interface class in the preset configuration file further comprises:

when the interface class cannot be matched with the preset interface class, switching the preset configuration file;

traversing the preset interface class in the switched preset configuration file until the interface class is matched with the preset interface class, and otherwise, continuing to switch the preset configuration file.

According to the embodiment of the present disclosure, the step of interfacing with the performance monitoring system further includes:

provided is a cache interface docking method.

acquiring a data acquisition requirement of a performance monitoring system;

the storage system is accessed according to the data acquisition requirements.

A second aspect of the present disclosure provides a docking apparatus for a storage system SDK, including:

the transmission module is used for acquiring the interface class of the performance monitoring system;

the configuration file module is used for traversing the preset interface class according to the interface class and acquiring preset implementation class information corresponding to the preset interface class when the interface class is matched with the preset interface class;

the service discovery module acquires an interface docking method according to a preset implementation class information instantiation object, and performs docking acquisition with the performance monitoring system according to the interface docking method; and the number of the first and second groups,

and the service provider interface module is used for carrying out butt joint with the performance monitoring system according to the interface butt joint method.

A third aspect of the present disclosure provides an electronic device comprising one or more processors; a storage device for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the above-described method for interfacing to a storage system SDK.

A third aspect of the present disclosure provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method of interfacing a storage system SDK.

A fourth aspect of the present disclosure provides a computer program product comprising a computer program for execution by a processor of the above-described method of interfacing a storage system SDK.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an application scenario diagram of a method, apparatus, device, medium and program product for interfacing a storage system SDK according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a method of interfacing a storage system SDK according to an embodiment of the present disclosure;

FIG. 3 schematically shows a flowchart of an embodiment of step S20 in FIG. 2;

fig. 4 schematically shows a flowchart of a first embodiment of step S20 in fig. 2;

FIG. 5 schematically shows a flowchart of a second embodiment of step S20 in FIG. 2;

FIG. 6 schematically illustrates a flow chart of a method of interfacing a storage system SDK according to another embodiment of the present disclosure;

FIG. 7 schematically illustrates a flowchart of one embodiment of step S40 in FIG. 2;

fig. 8 is a block diagram schematically illustrating a configuration of a docking apparatus of the storage system SDK according to an embodiment of the present disclosure;

fig. 9 is a block diagram schematically showing a specific example of the docking apparatus of the storage system SDK;

fig. 10 schematically shows a flowchart of a specific embodiment of the docking method for the storage system SDK.

Fig. 11 schematically shows a block diagram of an electronic device adapted to implement the docking method of the storage system SDK according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.

The present disclosure provides a method for interfacing a storage system SDK, comprising:

acquiring an interface class of a performance monitoring system;

acquiring an interface docking method according to a preset implementation class information instantiation object;

Fig. 1 schematically shows an application scenario diagram of a docking method and apparatus for a storage system SDK according to an embodiment of the present disclosure.

As shown in fig. 1, the application scenario according to this embodiment may include a financial service field. Network 102 is the medium used to provide communication links between terminal devices 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use terminal device 101 to interact with server 103 over network 102 to receive or send messages and the like. Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (for example only) may be installed on the terminal device 101.

The terminal device 101 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 103 may be a server that provides various services, such as a background management server (for example only) that provides support for websites browsed by users using the terminal devices 101. The backend management server may analyze and process the received data such as the user request, and feed back a processing result (for example, a web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the docking method of the storage system SDK provided by the embodiment of the present disclosure may be generally executed by the server 103. Accordingly, the information prompting device provided by the embodiment of the present disclosure may be generally disposed in the server 103. The docking method of the storage system SDK provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 103 and is capable of communicating with the terminal device 101 and/or the server 103. Accordingly, the information prompting device provided in the embodiment of the present disclosure may also be disposed in a server or a server cluster that is different from the server 103 and is capable of communicating with the terminal device 101 and/or the server 103.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The docking method of the storage system SDK of the disclosed embodiment will be described in detail below with fig. 2 to 8 based on the scenario described in fig. 1.

Fig. 2 schematically shows a flowchart of a docking method of a storage system SDK according to an embodiment of the present disclosure.

As shown in fig. 2, the docking method of the storage system SDK of this embodiment includes steps S10 to S30, and the docking method of the storage system SDK may be executed by the docking device of the storage system SDK.

In operation S10, an interface class of the performance monitoring system is acquired;

in operation S20, traversing a preset interface class in the preset configuration file according to the interface class, and acquiring preset implementation class information corresponding to the preset interface class when the interface class matches the preset interface class;

in operation S30, an interface docking method is acquired according to the preset implementation class information instantiation object;

in operation S40, a performance monitoring system is interfaced according to an interface interfacing method.

In the technical scheme provided by the disclosure, the implementation class of the interface is defined in a preset configuration file, when the interface is in butt joint with a monitoring system, the implementation class of the interface is obtained from the configuration file according to the interface class, and is instantiated through class loading, so that a server providing mechanism is formed, namely, only one key (namely the interface class) needs to be input to obtain an instance of the corresponding class, the logical decoupling of an application layer and the performance data acquisition of the monitoring system is realized, when the monitoring system is subjected to logical change or system replacement, no business application matching program transformation is needed, so that the application layer has elegant expansion or change capability, and the interference brought to the application layer by basic architecture change is reduced.

It should be noted that an SDK (software development kit) is generally a set of development tools used by some software engineers to establish application software for a specific software package, a software framework, a hardware platform, an operating system, and the like, and an SDK refers to a set of related documents, paradigms, and tools used to assist in developing a certain type of software in a broad sense. In addition, instantiation refers to a process of creating an object by using a class in object-oriented programming, which is called instantiation, and is a process of embodying an abstract conceptual class to a class real object, and in the present disclosure, a specific interface docking method for acquiring an interface through an interface class.

It should be noted that, in this embodiment, the implementation class information of the interface class is acquired in the configuration file in a class. Furthermore, in order to facilitate searching and loading of the preset configuration file, the preset configuration file is loaded through the full-limited name of the loading interface class.

Further, referring to fig. 3, step S20 includes:

s21, acquiring a corresponding thread class loader according to the interface class;

and S22, traversing the preset interface classes in the preset configuration file through the thread class loader.

When interfaced with a monitoring system, the monitoring system provides a number of interfaces that allow third parties to provide implementations for the interfaces. The implementation code for these interfaces is contained in the class path, needs to load a specific implementation class, and cannot be delegated to the system class loader because it is the ancestor class loader of the system class loader. Therefore, in this embodiment, a thread class loader is provided to facilitate successful loading of the interface class.

In addition, referring to fig. 4, in an embodiment provided by the present disclosure, step S20 further includes:

s201, when the interface class cannot be matched with a preset interface class, constructing a new interface class and corresponding new implementation class information corresponding to the interface class;

s202, caching the new interface class and the new implementation class information to a preset configuration file.

In order to adapt to more systems, in this embodiment, for interface classes that are not cached in the preset configuration file, when the preset configuration file cannot be matched in a traversal manner, new interface classes and corresponding implementation class information are constructed and cached in the preset configuration file, so that the data acquisition system can be docked into the monitoring system, an application layer does not need to be modified, the applicability is improved, and improvement for different systems is facilitated.

In another embodiment provided by the present disclosure, please refer to fig. 5, a plurality of preset configuration files are provided;

step S20 further includes:

s203, when the interface class cannot be matched with the preset interface class, switching a preset configuration file;

s204, traversing the preset interface class in the switched preset configuration file until the interface class is matched with the preset interface class, and otherwise, continuing to switch the preset configuration file.

The system is provided with a plurality of preset configuration files, different interface types and implementation type information are stored in each preset configuration file, and the preset configuration files are directly switched according to different systems, so that the corresponding interface types can be found conveniently, and the applicability is improved.

In addition, it should be noted that, in the embodiment provided by the present disclosure, the two interface classes may exist simultaneously in the matching method, so as to increase the applicability of the data acquisition system to the docking method.

Furthermore, a fully qualified name is set for the storage position of the configuration file, and different configuration files are loaded correspondingly through the fully qualified name of the loading interface. The configuration files with requirements can be conveniently found from the plurality of configuration files, the query is not required to be carried out one by one, and the processing speed is improved.

In order to facilitate subsequent multiple interfaces with the performance monitoring system, referring to fig. 6, step S40 further includes:

s50, cache interface docking method.

Since the docking with the monitoring system usually needs to be continued for a period of time, but the connection is usually limited, in order to avoid generating with the monitoring system each time, the interface docking method is cached in the memory so as to facilitate the next docking without calling the configuration file again.

On the other hand, referring to fig. 7, after step S40, the method further includes:

s41, acquiring the data acquisition requirement of the performance monitoring system;

and S42, accessing the storage system according to the data acquisition requirement.

After the performance monitoring system is completely connected, the data acquisition requirement needing to be acquired is obtained from the performance monitoring system, and the storage system is accessed according to the data acquisition requirement so as to facilitate data transmission.

Based on the above docking method for the storage system SDK, the present disclosure also provides a docking device for the storage system SDK, which will be described in detail below with reference to fig. 8.

Fig. 8 schematically shows a block diagram of a docking apparatus of the storage system SDK according to an embodiment of the present disclosure.

As shown in fig. 8, the docking apparatus 200 of the storage system SDK of this embodiment includes a transmission module 1, a profile module 2, a service discovery module 3, and a service provider interface module 4; the transmission module 1 is used for acquiring the interface class of the performance monitoring system; the configuration file module 2 is used for traversing the preset interface class according to the interface class, and acquiring preset implementation class information corresponding to the preset interface class when the interface class is matched with the preset interface class; the service discovery module 3 acquires an interface docking method according to a preset implementation class information instantiation object, and performs docking acquisition with the performance monitoring system according to the interface docking method; the service provider interface module 4 is used for interfacing with the performance monitoring system according to the interface interfacing method.

It should be noted that the docking device 200 of the storage system SDK further includes a service module and a performance acquisition module; the service module is used for acquiring the data acquisition requirement of the performance monitoring system; the performance acquisition module is used for accessing the storage system according to the data acquisition requirement.

Referring to fig. 9, in an embodiment provided by the present disclosure, a storage system SDK in the present embodiment includes a service provider interface, a ServiceDiscover module, and a performance acquisition module. The storage system SDK is used for accessing a remote storage medium; the service provider interface is an interface or an abstract class, wherein functions needing to be expanded and realized are defined; the ServiceDiscover is used for loading and instantiating the java class of the service and providing an interface for acquiring the service object; wherein LazyIter is a private internal class of the ServiceDiscover, and is responsible for loading, instantiating, and caching all classes of service. The storage system SDK acquires a specific service provider iterator through an externally exposed interface of the ServiceDiscover, and traverses and calls the ServiceDiscover; and a configuration file is arranged in the performance acquisition module, and related information of a service provider, including a full name of the implementation class, is configured in the configuration file.

Based on the above specific embodiment, the present disclosure further provides a docking method for the SDK of the specific storage system.

Referring to fig. 10, in the present embodiment, the storage system SDK remotely accesses the storage medium and accesses the monitoring system;

1. the storage system SDK acquires a parameter API.class, namely an interface class connected with the monitoring system;

2. according to the current interface class, the storage system SDK acquires a corresponding thread class loader so as to load the interface class;

3. constructing a ServiceDiscover so as to construct implementation class information corresponding to the interface class in service discovery;

4. and constructing a LazyIter, and loading, instantiating and caching the class of the ServiceDiscover.

5. And the performance acquisition module is internally provided with a configuration file, and the configuration file corresponding to the API full-limit name under the class path is loaded.

6. Using a method class.forName () to acquire the implementation class information of an interface;

7. instantiating the implementation class of the interface and caching.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

Fig. 11 schematically shows a block diagram of an electronic device adapted for a docking method of a storage system SDK according to an embodiment of the present disclosure.

As shown in fig. 11, an electronic device 300 according to an embodiment of the present disclosure includes a processor 3001, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)3002 or a program loaded from a storage section 3008 into a Random Access Memory (RAM) 3003. The processor 3001 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 3001 may also include on-board memory for caching purposes. The processor 3001 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 3003, various programs and data necessary for the operation of the electronic apparatus 300 are stored. The processor 3001, the ROM 3002, and the RAM 3003 are connected to each other by a bus 3004. The processor 3001 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 3002 and/or the RAM 3003. Note that the program may also be stored in one or more memories other than the ROM 3002 and the RAM 3003. The processor 3001 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in one or more memories.

According to an embodiment of the present disclosure, electronic device 300 may also include an input/output (I/O) interface 3005, input/output (I/O) interface 3005 also connected to bus 3004. The electronic device 300 may also include one or more of the following components connected to the I/O interface 3005: an input portion 3006 including a keyboard, a mouse, and the like; an output section 3007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 3008 including a hard disk and the like; and a communication section 3009 including a network interface card such as a LAN card, a modem, or the like. The communication section 3009 performs communication processing via a network such as the internet. Drivers 3010 are also connected to I/O interface 3005 as needed. A removable medium 3011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 3010 as necessary, so that a computer program read out therefrom is mounted in the storage section 3008 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than the ROM 3002 and/or the RAM 3003 and/or the ROM 3002 and the RAM 3003 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the interfacing method of the storage system SDK provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 3001. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication section 3009, and/or installed from the removable medium 3011. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 3009, and/or installed from the removable medium 3011. The computer program performs the above-described functions defined in the system of the embodiment of the present disclosure when executed by the processor 3001. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

The above-mentioned embodiments are intended to illustrate the objects, aspects and advantages of the present disclosure in further detail, and it should be understood that the above-mentioned embodiments are only illustrative of the present disclosure and are not intended to limit the present disclosure, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A method for interfacing a storage System (SDK) is characterized by comprising the following steps:

acquiring an interface class of a performance monitoring system;

acquiring an interface docking method according to the preset implementation class information instantiation object;

2. The docking method for the storage system SDK according to claim 1, wherein traversing the preset interface class in the preset configuration file according to the interface class comprises:

acquiring a corresponding thread class loader according to the interface class;

traversing the preset interface class in the preset configuration file through the thread class loader.

3. The method for interfacing a storage system SDK according to claim 1, wherein traversing the preset interface class in the preset configuration file according to the interface class further comprises:

and caching the new interface class and the new implementation class information to the preset configuration file.

4. The docking method for the storage system SDK according to claim 1, wherein the preset configuration file is provided in plurality;

the step of traversing the preset interface class in the preset configuration file according to the interface class further comprises:

traversing the preset interface class in the preset configuration file after switching until the interface class is matched with the preset interface class, and if not, continuing switching the preset configuration file.

5. The method of interfacing a storage system SDK according to claim 1, further comprising, after the step of interfacing with the performance monitoring system:

and caching the interface docking method.

6. The method of interfacing a storage system SDK according to claim 1, further comprising, after the step of interfacing with the performance monitoring system:

acquiring data acquisition requirements of the performance monitoring system;

and accessing a storage system according to the data acquisition requirement.

7. A docking device for a storage System (SDK), comprising:

the configuration file module is used for traversing a preset interface class according to the interface class and acquiring preset implementation class information corresponding to the preset interface class when the interface class is matched with the preset interface class;

the service discovery module is used for acquiring an interface docking method according to the preset implementation class information instantiation object and performing docking acquisition with the performance monitoring system according to the interface docking method; and the number of the first and second groups,

8. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-6.

9. A computer-readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

10. A computer program product, characterized in that it comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.