CN116233240A

CN116233240A - Method and device for realizing Paas cloud registry service and electronic equipment

Info

Publication number: CN116233240A
Application number: CN202211738180.4A
Authority: CN
Inventors: 杨猛; 周书橙; 于灏; 康东杰; 孙飚; 张娜; 马南; 乔兰
Original assignee: Picc Information Technology Co ltd
Current assignee: Picc Information Technology Co ltd
Priority date: 2022-12-31
Filing date: 2022-12-31
Publication date: 2023-06-06

Abstract

The application discloses a realization method of Paas cloud registry service, which aims to solve the problem that the deployment requirement of a registry cloud service scene cannot be met because a consul registry used in the prior art does not provide a cloud platform multi-tenant isolation model or a multi-service isolation scheme. The method comprises the following steps: and creating a Paas cloud registry for the target tenant according to the data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant. The application also discloses a device for realizing the Paas cloud registry service, electronic equipment and a computer readable storage medium.

Description

Method and device for realizing Paas cloud registry service and electronic equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for implementing Paas cloud registry service, and an electronic device.

Background

In a self-built PaaS cloud, a registry providing business system micro-service operations is typically required for service registration and service discovery. In a scenario of providing a registry cloud service, on one hand, in order to avoid security problems caused by network connectivity, a cloud platform multi-tenant, multi-IaaS and multi-network area environment have physical isolation instance deployment requirements; on the other hand, in order to avoid the problem of wasting resources by deploying a set of instances for each service, there is a logic isolation requirement that the multi-service system share a single instance.

However, the condul registry used by comparing and selecting multiple aspects at present does not provide a cloud platform multi-tenant isolation model or a multi-service isolation scheme, so that the deployment requirement of the cloud service scene of the registry cannot be met.

Disclosure of Invention

The embodiment of the application provides a realization method of Paas cloud registry service, which is used for solving the problem that in the prior art, as a used condul registry does not provide a cloud platform multi-tenant isolation model or a multi-service isolation scheme, the deployment requirement of a registry cloud service scene cannot be met.

The embodiment of the application also provides a device for realizing the Paas cloud registry service, an electronic device and a computer readable storage medium.

The embodiment of the application adopts the following technical scheme:

a method for realizing Paas cloud registration center service comprises the following steps:

and creating a Paas cloud registry for the target tenant according to the data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant.

Optionally, creating a Paas cloud registry for the target tenant according to data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant includes:

acquiring data center information, cloud environment type information, VPC network information and cluster information of the target tenant;

if any appointed information in the data center information, cloud environment type information, VPC network information and cluster information of the target tenant is different from tenant information corresponding to the any appointed information in the other tenants, the Paas cloud registry is created for the target user.

Optionally, the method further comprises:

acquiring service information of micro services corresponding to the target user; wherein the service information comprises a namespace of the micro service, version information of the micro service and application information of the micro service;

and storing the registration information of the micro services with the same service information into the same metadata of the Paas cloud registration center.

Optionally, the method further comprises:

and registering the micro-service corresponding to the target tenant to the Paas cloud registration center through a byte code enhancement technology.

Optionally, registering the micro-service corresponding to the target tenant to the Paas cloud registry through a bytecode enhancement technology includes:

determining target dimension information to be isolated when registering the micro service;

and adding the target dimension information into metadata of the Paas cloud registry by a byte code enhancement technology.

Optionally, the method further comprises:

checking a service state of the micro service registered to the Paas cloud registry;

and judging whether to re-register the micro service according to the service state.

Optionally, determining whether to re-register the micro service according to the service state includes:

if the service status of the micro service is a health status and the micro service is not present in the Paas cloud registry, determining to re-register the micro service.

if the service state of the micro service is a health state and the micro service exists in the Paas cloud registry, determining not to re-register the micro service; or alternatively, the first and second heat exchangers may be,

if the service state of the micro service is an unhealthy state and the micro service exists in the Paas cloud registry, determining not to re-register the micro service; or alternatively, the first and second heat exchangers may be,

if the service status of the micro-service is unhealthy and the micro-service is not present in the Paas cloud registry, determining not to re-register the micro-service.

An implementation device of Paas cloud registry service comprises a creation module, wherein:

the creating module is used for creating a Paas cloud registration center for a target tenant according to data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant.

Optionally, the creating module is configured to:

Optionally, the device is further configured to:

Optionally, the apparatus further includes:

and the registration module is used for registering the micro-service corresponding to the target tenant to the Paas cloud registration center through a byte code enhancement technology.

Optionally, the registration module is configured to:

Optionally, the apparatus further includes:

the checking module is used for checking the service state of the micro service registered in the Paas cloud registration center;

and the judging module is used for judging whether to re-register the micro service according to the service state.

Optionally, the judging module is configured to:

An electronic device, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of a method of implementing a Paas cloud registry service as described above.

A computer readable storage medium, wherein a computer program is stored on the computer readable storage medium, which when executed by a processor, implements the steps of a method of implementing a Paas cloud registry service as described above.

The above-mentioned at least one technical scheme that this application embodiment adopted can reach following beneficial effect:

by adopting the method provided by the embodiment of the application, the Paas cloud registry can be created for the target tenant according to the data center information, cloud environment type information and VPC network information and cluster information of the target tenant in the multi-tenant, so that the problem that the deployment requirement of the cloud service scene of the registry cannot be met because the used consul registry does not provide a cloud platform multi-tenant isolation model in the prior art is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

fig. 1a is a schematic implementation flow diagram of an implementation method of Paas cloud registry service provided in an embodiment of the present application;

fig. 1b is a schematic implementation flow diagram of a specific implementation method of Paas cloud registry service provided in an embodiment of the present application;

fig. 1c is a schematic architecture diagram of a multi-tenant Paas cloud registry according to an embodiment of the present disclosure;

fig. 1d is a schematic implementation flow diagram of a method for implementing multi-service isolation of a target user according to an embodiment of the present application;

fig. 2 is a schematic specific structure diagram of an implementation device of Paas cloud registry service according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Example 1

In order to solve the problem that the deployment requirements of a registry cloud service scene cannot be met because a consul registry is used in the prior art and a cloud platform multi-tenant isolation model and a multi-service isolation scheme are not provided, the embodiment of the application provides a method for realizing Paas cloud registry service.

The method may be performed by various types of computing devices, or may be an Application or Application (APP) installed on a computing device. The computing device can be a user terminal such as a mobile phone, a tablet computer, an intelligent wearable device and the like, and also can be a server and the like.

For convenience of description, the embodiment of the application takes an execution subject of the method as a server as an example, and introduces the method. It will be appreciated by those skilled in the art that the embodiment of the present application describes the method using the server as an example, which is only an exemplary illustration, and does not limit the scope of protection of the claims corresponding to the present solution.

Specifically, the implementation flow of the method provided in the embodiment of the present application is shown in fig. 1a, and includes the following steps:

and 11, creating a Paas cloud registry for the target tenant according to the data center information, the cloud environment type information, the VPC network information and the cluster information of the target tenant in the multi-tenant.

As shown in fig. 1b, in the embodiment of the present application, the following implementation steps 111 to 112 may be used to implement the above step 11:

step 111, obtaining data center information, cloud environment type information, VPC network information and cluster information of the target tenant.

Wherein the cluster information comprises virtual machine cluster information or K8S cluster information.

Step 112, if any specific information in the data center information, cloud environment type information, VPC network information and cluster information of the target tenant is different from tenant information corresponding to any specific information in other tenants, creating a Paas cloud registry for the target user.

The Paas cloud registry may be, for example, a condul cluster.

In this embodiment of the present invention, according to data center information, cloud environment type information, VPC network information, and cluster information of a target tenant, the data center information, cloud environment type information, VPC network information, and cluster information of other tenants may be compared, and if the data center information of the target tenant is different from the data center information of other tenants, or the cloud environment type information of the target tenant is different from the cloud environment type information of other tenants, or the VPC network information of the target tenant is different from the VPC network information of other tenants, or the cluster information of the target tenant is different from the cluster information of other tenants, a set of Paas cloud registration centers is created for the target tenant separately.

Fig. 1c is a schematic architecture diagram of a Paas cloud registry with multiple tenants according to an embodiment of the present application. In the embodiment of the present application, paas cloud registration centers may be created for each tenant according to information such as data center information, cloud environment type information, VPC network information, and cluster information of each tenant in the group tenant, the technology tenant, the life tenant, and the health tenant.

In an optional implementation manner, in order to further realize multi-service isolation of the target user, service information of the micro service corresponding to the target user may also be obtained; the service information comprises a naming space of the micro service, version information of the micro service and application information of the micro service; and then, storing the registration information of the micro-services with the same service information into the same metadata of the Paas cloud registry, so that the micro-services can be filtered and selected through the api filtering characteristic of the Paas cloud registry when the micro-services are called later, and multi-service isolation of the target user is realized. For example, assuming that the Paas cloud registry is a condul cluster, filtering selection can be performed through Consul api filtering characteristics, so that multi-service isolation of the target user is achieved.

In practical application, as shown in fig. 1d, metadata of registration information in the registry control may store application logic information, define meta.naspace and meta.project and meta.version, and perform filtering selection through consul api filtering characteristics when in use. For example, where there is a need to deploy the underwriting, claims and underwriting, claims in Henan under different nasspace, the registration information meta of Henan underwriting service 1 should be: the registration information meta of meta.nasspace= "northside" and meta.project= "underwriting" and meta.version= "V1", the registration information meta of the henna underwriting service 1 should be: meta.nasspace= "henna" and meta.project= "underwriting" and meta.version= "V1".

Secondly, in order to realize automatic registration of micro services without adding codes, so as to reduce code development workload, in the embodiment of the application, when registering services, the micro services corresponding to the target tenant can be registered to the Paas cloud registration center through a byte code enhancement technology. Specifically, the target dimension information to be isolated when registering the micro service can be determined first; then, the target dimension information is added to metadata of the Paas cloud registry through a bytecode enhancement technology.

In practical application, the byte code enhancement technology can be utilized, through enhancing the condul registration and the service information interface logic, the dimension (project+nalsphere) needing to be isolated is added to the metadata (metadata) of the service when the service is registered, so that the filtering function of condul can be utilized to screen the target service according to the isolated dimension when the service is called.

Further, in the case where the health check is adopted in the related art, the following may occur: the service is judged to be unavailable because of other factors such as a database, and the registry can automatically reject the service at the moment, but when the service is in a normal state, the registry cannot sense if the service is not restarted, and the service cannot be automatically registered in the registry, so that the service cannot be called later. To avoid this problem, in an alternative embodiment, the service status of the micro-service registered to the Paas cloud registry may be checked; then, it is determined whether to re-register the micro service according to the service status.

Specifically, if the service state of the micro-service is a health state and the micro-service is not present in the Paas cloud registry, it is determined to re-register the micro-service.

Alternatively, if the service state of the micro-service is a health state and there is a micro-service in the Paas cloud registry, it is determined that the micro-service is not re-registered.

Alternatively, if the service state of the micro-service is unhealthy and there is a micro-service in the Paas cloud registry, it is determined that the micro-service is not re-registered.

Alternatively, if the service state of the micro-service is unhealthy and there is no micro-service in the Paas cloud registry, it is determined that the micro-service is not re-registered.

By the service detection method provided by the embodiment of the application, the state monitoring and automatic registration under the condition of micro service starting can be realized by establishing the checking mechanism.

Example 2

In order to solve the problem that in the prior art, as the consul registry is used, a cloud platform multi-tenant isolation model is not provided, and a multi-service isolation scheme is not provided, so that deployment requirements of a registry cloud service scene cannot be met, the embodiment of the application provides a Paas cloud registry service implementation device 20, and a specific structural schematic diagram of the device 20 is shown in fig. 2, including a creation module 21, wherein:

the creating module 21 is configured to create a Paas cloud registry for a target tenant according to data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant.

Optionally, the creating module 21 is configured to:

Optionally, the device is further configured to:

Optionally, the apparatus further includes:

Optionally, the registration module is configured to:

Optionally, the apparatus further includes:

Optionally, the judging module is configured to:

With the device provided in the embodiments of the present application,

the Paas cloud registry can be created for the target tenant according to the data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant, so that the problem that the deployment requirement of a cloud service scene of the registry cannot be met because the used condul registry in the prior art is not provided with a cloud platform multi-tenant isolation model is solved.

Example 3

Fig. 3 is a schematic hardware structure of an electronic device implementing various embodiments of the present application, where the electronic device 300 includes, but is not limited to: radio frequency unit 301, network module 302, audio output unit 303, input unit 304, sensor 305, display unit 306, user input unit 307, interface unit 308, memory 309, processor 310, and power supply 311. Those skilled in the art will appreciate that the electronic device structure shown in fig. 3 does not constitute a limitation of the electronic device, and the electronic device may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components. In the embodiment of the application, the electronic device includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.

The processor 310 is configured to create a Paas cloud registry for a target tenant according to data center information, cloud environment type information, VPC network information and cluster information of the target tenant in the multi-tenant.

Optionally, the method further comprises:

Memory 309 is used to store a computer program executable on processor 310, which when executed by processor 310, implements the functions described above as being implemented by processor 310.

It should be understood that, in the embodiment of the present application, the radio frequency unit 301 may be configured to receive and send information or signals during a call, specifically, receive downlink data from a base station, and then process the received downlink data with the processor 310; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 301 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 301 may also communicate with networks and other devices through a wireless communication system.

The electronic device provides wireless broadband internet access to the user through the network module 302, such as helping the user to send and receive e-mail, browse web pages, and access streaming media, etc.

The audio output unit 303 may convert audio data received by the radio frequency unit 301 or the network module 302 or stored in the memory 309 into an audio signal and output as sound. Also, the audio output unit 303 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the electronic device 300. The audio output unit 303 includes a speaker, a buzzer, a receiver, and the like.

The input unit 303 is for receiving an audio or video signal. The input unit 304 may include a graphics processor (Graphics Processing Unit, GPU) 3041 and a microphone 3042, the graphics processor 3041 processing image data of still pictures or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 306. The image frames processed by the graphics processor 3041 may be stored in the memory 309 (or other storage medium) or transmitted via the radio frequency unit 301 or the network module 302. The microphone 3042 may receive sound, and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 301 in the case of a telephone call mode.

The electronic device 300 further comprises at least one sensor 305, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 3061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 3061 and/or the backlight when the electronic device 300 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for recognizing the gesture of the electronic equipment (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 305 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which are not described herein.

The display unit 306 is used to display information input by a user or information provided to the user. The display unit 306 may include a display panel 3061, and the display panel 3061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 307 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the electronic device. Specifically, the user input unit 307 includes a touch panel 3071 and other input devices 3072. The touch panel 3071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 3071 or thereabout the touch panel 3071 using any suitable object or accessory such as a finger, stylus, or the like). The touch panel 3071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 310, and receives and executes commands sent by the processor 310. In addition, the touch panel 3071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 307 may include other input devices 3072 in addition to the touch panel 3071. Specifically, other input devices 3072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 3071 may be overlaid on the display panel 3061, and when the touch panel 3071 detects a touch operation thereon or thereabout, the touch operation is transmitted to the processor 310 to determine a type of touch event, and then the processor 310 provides a corresponding visual output on the display panel 3061 according to the type of touch event. Although in fig. 3, the touch panel 3071 and the display panel 3061 are two independent components for implementing the input and output functions of the electronic device, in some embodiments, the touch panel 3071 and the display panel 3061 may be integrated to implement the input and output functions of the electronic device, which is not limited herein.

The interface unit 308 is an interface to which an external device is connected to the electronic apparatus 300. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 308 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the electronic apparatus 300 or may be used to transmit data between the electronic apparatus 300 and an external device.

Memory 309 may be used to store software programs as well as various data. The memory 309 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 309 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 310 is a control center of the electronic device, connects various parts of the entire electronic device using various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 309, and calling data stored in the memory 309, thereby performing overall monitoring of the electronic device. Processor 310 may include one or more processing units; preferably, the processor 310 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 310.

The electronic device 300 may also include a power supply 311 (e.g., a battery) for powering the various components, and preferably the power supply 311 may be logically coupled to the processor 310 via a power management system that performs functions such as managing charge, discharge, and power consumption.

In addition, the electronic device 300 includes some functional modules, which are not shown, and will not be described herein.

Preferably, the embodiment of the present application further provides an electronic device, including a processor 310, a memory 309, and a computer program stored in the memory 309 and capable of running on the processor 310, where the computer program when executed by the processor 310 implements each process of the foregoing embodiment of a method for implementing Paas cloud registry service, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein.

The embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of the foregoing embodiment of the implementation method of Paas cloud registry service, and the same technical effect can be achieved, so that repetition is avoided, and no further description is given here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. The method for realizing the Paas cloud registration center service is characterized by comprising the following steps of:

2. The method of claim 1, wherein creating a Paas cloud registry for a target tenant of the multi-tenants based on data center information, cloud environment type information, VPC network information, and cluster information of the target tenant comprises:

3. The method of claim 1, wherein the method further comprises:

4. The method of claim 1, wherein the method further comprises:

5. The method of claim 4, wherein registering the micro-service corresponding to the target tenant with the Paas cloud registry by a bytecode enhancement technique comprises:

6. The method of claim 4, wherein the method further comprises:

7. The method of claim 6, wherein determining whether to re-register the micro-service based on the service status comprises:

8. The method of claim 6, wherein determining whether to re-register the micro-service based on the service status comprises:

9. An implementation device of Paas cloud registry service is characterized by comprising a creation module, wherein:

10. An electronic device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method of implementing the Paas cloud registry service of any one of claims 1 to 8.