Implementation Method, Device and Electronic Device for a Paas Cloud Registration Center Service

Abstract

The present application discloses a method for implementing a Paas cloud registry service, so as to solve the problem that the consul registry used in the prior art does not provide a multi-tenant isolation model for the cloud platform nor a multi-service isolation solution, resulting in the inability to meet the deployment requirements of the registry cloud service scenario. The method includes: 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 present application also discloses an apparatus, an electronic device, and a computer-readable storage medium for implementing the Paas cloud registry service.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular, to a method, device, and electronic device for implementing a Paas cloud registry service. Background Art

[0002] In a self-built PaaS cloud, it is usually necessary to provide a registry for the microservices of the business system to run, for service registration and service discovery. Among them, in the scenario of providing registry cloud services, on the one hand, in order to avoid security problems caused by network connectivity, there is a need for physically isolated instance deployment in the cloud platform's multi-tenant, multi-IaaS, and multi-network area environments; on the other hand, in order to avoid wasting resources by deploying a set of instances for each business, there is also a need for logical isolation of multiple business systems sharing a single instance.

[0003] However, the currently selected consul registry after multi-faceted comparison does not provide a multi-tenant isolation model for the cloud platform, nor does it provide a multi-business isolation solution. Therefore, it cannot meet the deployment requirements of the registry cloud service scenario. Summary of the Invention

[0004] An embodiment of the present application provides a method for implementing a Paas cloud registry service, which is used to solve the problem in the prior art that because the used consul registry does not provide a multi-tenant isolation model for the cloud platform, nor does it provide a multi-business isolation solution, it cannot meet the deployment requirements of the registry cloud service scenario.

[0005] An embodiment of the present application also provides an apparatus for implementing a Paas cloud registry service, an electronic device, and a computer-readable storage medium.

[0006] The embodiments of the present application adopt the following technical solutions:

[0007] A method for implementing a Paas cloud registry service includes:

[0008] Create 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.

[0009] Optionally, 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 includes:

[0010] Obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant;

[0011] If any specified information among the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to the any specified information among the other tenants, create the Paas cloud registry for the target user.

[0012] Optionally, the method further includes:

[0013] Obtain the service information of the microservices corresponding to the target user; wherein, the service information includes the namespace of the microservices, the version information of the microservices, and the application information of the microservices;

[0014] Store the registration information of the microservices with the same service information in the same metadata of the Paas cloud registry.

[0015] Optionally, the method further includes:

[0016] Register the microservices corresponding to the target tenant to the Paas cloud registry through bytecode enhancement technology.

[0017] Optionally, registering the microservices corresponding to the target tenant to the Paas cloud registry through bytecode enhancement technology includes:

[0018] Determine the target dimension information to be isolated when registering the microservices;

[0019] Add the target dimension information to the metadata of the Paas cloud registry through bytecode enhancement technology.

[0020] Optionally, the method further includes:

[0021] Check the service status of the microservices registered to the Paas cloud registry;

[0022] Judge whether to re-register the microservices according to the service status.

[0023] Optionally, judging whether to re-register the microservices according to the service status includes:

[0024] If the service status of the microservices is in a healthy state and the microservices do not exist in the Paas cloud registry, determine to re-register the microservices.

[0025] Optionally, judging whether to re-register the microservices according to the service status includes:

[0026] If the service status of the microservice is healthy and the microservice exists in the Paas cloud registry, it is determined not to re-register the microservice; or,

[0027] If the service status of the microservice is unhealthy and the microservice exists in the Paas cloud registry, it is determined not to re-register the microservice; or,

[0028] If the service status of the microservice is unhealthy and the microservice does not exist in the Paas cloud registry, it is determined not to re-register the microservice.

[0029] An implementation device for a Paas cloud registry service includes a creation module, where:

[0030] The creation module is used to create a Paas cloud registry for the target tenant according to the data center information, cloud environment type information, VPC network information, and cluster information in the multi-tenant.

[0031] Optionally, the creation module is used to:

[0032] Obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant;

[0033] If any specified information in the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to the same specified information in other tenants, create the Paas cloud registry for the target user.

[0034] Optionally, the device is further used to:

[0035] Obtain the service information of the microservice corresponding to the target user; where the service information includes the namespace of the microservice, the version information of the microservice, and the application information of the microservice;

[0036] Store the registration information of the microservices with the same service information in the same metadata of the Paas cloud registry.

[0037] Optionally, the device further includes:

[0038] The registration module is used to register the microservice corresponding to the target tenant to the Paas cloud registry through bytecode enhancement technology.

[0039] Optionally, the registration module is used to:

[0040] Determine the target dimension information to be isolated when registering the microservice;

[0041] By means of bytecode enhancement technology, add the target dimension information to the metadata in the PaaS cloud registry.

[0042] Optionally, the device further includes:

[0043] An inspection module, configured to inspect the service status of the microservices registered in the PaaS cloud registry;

[0044] A judgment module, configured to judge whether to re-register the microservice according to the service status.

[0045] Optionally, the judgment module is configured to:

[0046] If the service status of the microservice is in a healthy state and the microservice does not exist in the PaaS cloud registry, determine to re-register the microservice.

[0047] Optionally, the judgment module is configured to:

[0048] If the service status of the microservice is in a healthy state and the microservice exists in the PaaS cloud registry, determine not to re-register the microservice; or,

[0049] If the service status of the microservice is in an unhealthy state and the microservice exists in the PaaS cloud registry, determine not to re-register the microservice; or,

[0050] If the service status of the microservice is in an unhealthy state and the microservice does not exist in the PaaS cloud registry, determine not to re-register the microservice.

[0051] An electronic device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, the steps of the method for implementing the PaaS cloud registry service as described above are implemented.

[0052] A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method for implementing the PaaS cloud registry service as described above are implemented.

[0053] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0054] By using the method provided in the embodiments of the present application, a 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 in the multi-tenant, thus solving the problem in the prior art that since the used consul registry does not provide a multi-tenant isolation model for the cloud platform, the deployment requirements of the registry cloud service scenario cannot be met. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments and descriptions thereof of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0056] Figure 1a It is a schematic flowchart of the implementation method of a Paas cloud registry service provided by an embodiment of the present application;

[0057] Figure 1b It is a schematic flowchart of the implementation method of a specific implementation method of a Paas cloud registry service provided by an embodiment of the present application;

[0058] Figure 1c It is a schematic architecture diagram of a multi-tenant Paas cloud registry provided by an embodiment of the present application;

[0059] Figure 1d It is a schematic flowchart of the implementation method of multi-service isolation of a target user provided by an embodiment of the present application;

[0060] Figure 2 It is a schematic diagram of the specific structure of an implementation device of a Paas cloud registry service provided by an embodiment of the present application;

[0061] Figure 3 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0062] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.

[0063] The technical solutions provided by each embodiment of the present application will be described in detail below in conjunction with the drawings.

[0064] Embodiment 1

[0065] In a self-built PaaS cloud, it is usually necessary to provide a registration center for the microservices of the business system to run, which is used for service registration and service discovery. Among them, in the scenario of providing registration center cloud services, on the one hand, in order to avoid security problems caused by network connectivity, there is a need for physically isolated instance deployment in the multi-tenant, multi-IaaS, and multi-network area environment of the cloud platform; on the other hand, in order to avoid wasting resources by deploying a set of instances for each business, there is also a need for logical isolation of multiple business systems sharing a single instance.

[0066] However, the currently selected Consul registration center after multi-faceted comparison does not provide a multi-tenant isolation model for the cloud platform, nor does it provide a multi-business isolation solution. Therefore, it cannot meet the deployment requirements of the registration center cloud service scenario.

[0067] To solve the problem in the prior art that the Consul registration center used does not provide a multi-tenant isolation model for the cloud platform and does not provide a multi-business isolation solution, resulting in the inability to meet the deployment requirements of the registration center cloud service scenario, the embodiments of this application provide a method for implementing a Paas cloud registration center service.

[0068] The execution subject of this method can be various types of computing devices, or it can be an application or an app (Application, APP) installed on a computing device. The computing device can be, for example, a user terminal such as a mobile phone, a tablet computer, a smart wearable device, etc., or it can be a server, etc.

[0069] For ease of description, in the embodiments of this application, the execution subject of this method is taken as an example of a server to introduce this method. Those skilled in the art can understand that taking this server as an example to introduce the method in the embodiments of this application is only an exemplary illustration and does not limit the protection scope of the corresponding claims of this solution.

[0070] Specifically, the implementation process of the method provided in the embodiments of this application is as Figure 1a shown, including the following steps:

[0071] Step 11, create a Paas cloud registration center for the target tenant according to the data center information, cloud environment type information, VPC network information, and cluster information in the multi-tenant.

[0072] As Figure 1b shown, in the embodiments of this application, the above step 11 can be implemented by the following implementation steps 111 to 112:

[0073] Step 111, obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant.

[0074] Among them, the cluster information includes virtual machine cluster information or K8S cluster information.

[0075] Step 112: If any specified information among the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to any specified information in other tenants, create a Paas cloud registry for the target user.

[0076] Among them, the Paas cloud registry can be, for example, a Consul cluster.

[0077] In the embodiments of the present application, the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant can be respectively compared with the data center information, cloud environment type information, VPC network information, and cluster information of other tenants. 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, then a set of Paas cloud registries is created separately for the target tenant.

[0078] As Figure 1c shown, it is a schematic diagram of the architecture of a multi-tenant Paas cloud registry provided by the embodiments of the present application. Figure 1c The multi-tenants respectively include group tenants, technology tenants, life insurance tenants, and health insurance tenants. In the embodiments of the present application, Paas cloud registries can be created for each tenant according to the data center information, cloud environment type information, VPC network information, and cluster information of each tenant among the group tenants, technology tenants, life insurance tenants, and health insurance tenants.

[0079] By using the method provided by the embodiments of the present application, a 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-tenants, thereby solving the problem in the prior art that because the used consul registry does not provide a multi-tenant isolation model for the cloud platform, the deployment requirements of the registry cloud service scenario cannot be met.

[0080] In an alternative embodiment, to further implement multi-service isolation for the target user, service information of the microservices corresponding to the target user may also be obtained. The service information includes the namespace of the microservice, the version information of the microservice, and the application information of the microservice. Then, the registration information of the microservices with the same service information is stored in the same metadata of the Paas cloud registry. In this way, when the microservice is called subsequently, the microservice can be filtered and selected through the api filtering feature of the Paas cloud registry, thereby implementing multi-service isolation for the target user. For example, assuming the Paas cloud registry is a Consul cluster, the filtering and selection can be achieved through the consul api filtering feature, thereby implementing multi-service isolation for the target user.

[0081] As Figure 1d shown, in practical applications, application logic information can be stored based on the metadata of the registration information in the Consul registry, and meta.namespace and meta.project and meta.version can be defined. When used, filtering and selection are performed through the consul api filtering feature. For example, if the underwriting and claims in Hebei and the underwriting and claims in Henan need to be deployed in different namespaces, the registration information meta of the underwriting service 1 in Hebei should be: meta.namespace = "Hebei" and meta.project = "Underwriting" and meta.version = "V1", and the registration information meta of the underwriting service 1 in Henan should be: meta.namespace = "Henan" and meta.project = "Underwriting" and meta.version = "V1".

[0082] Secondly, in order to achieve automatic registration of microservices without adding code, thereby reducing the workload of code development, in the embodiment of the present application, when registering the service, the microservice corresponding to the target tenant can be registered in the Paas cloud registry through bytecode enhancement technology. Specifically, the target dimension information to be isolated when registering the microservice can be determined first. Then, through bytecode enhancement technology, the target dimension information is added to the metadata of the Paas cloud registry.

[0083] In practical applications, bytecode enhancement technology can be used to add the dimensions to be isolated (project + namespace) to the service metadata when registering the service by enhancing the consul registration and service information interface logic. In this way, when the service is called later, the target service can be filtered according to the isolated dimensions using the filtering function of consul.

[0084] In addition, considering the following situation that may occur when health checks are used in related technologies: the service is determined to be unavailable due to other factors such as the database. At this time, the registration center will automatically remove the service. However, when the service status is normal, if the service is not restarted, the registration center cannot perceive it, and the service will not be automatically registered in the registration center. In this way, the service cannot be called later. To avoid this problem, in an alternative embodiment, the service status of the microservices registered in the Paas cloud registration center can be checked; then, according to the service status, it can be determined whether to re-register the microservices.

[0085] Specifically, if the service status of the microservice is healthy and the microservice does not exist in the Paas cloud registration center, it is determined to re-register the microservice.

[0086] Or, if the service status of the microservice is healthy and the microservice exists in the Paas cloud registration center, it is determined not to re-register the microservice.

[0087] Or, if the service status of the microservice is unhealthy and the microservice exists in the Paas cloud registration center, it is determined not to re-register the microservice.

[0088] Or, if the service status of the microservice is unhealthy and the microservice does not exist in the Paas cloud registration center, it is determined not to re-register the microservice.

[0089] Through the above service detection method provided by the embodiments of the present application, a check mechanism can be established to realize the status monitoring and automatic registration of microservices when they are started.

[0090] Embodiment 2

[0091] To solve the problem in the prior art that the consul registration center used does not provide a multi-tenant isolation model for the cloud platform nor a multi-service isolation solution, resulting in the inability to meet the deployment requirements of the registration center cloud service scenario, the embodiments of the present application provide an implementation device 20 for Paas cloud registration center services. The specific structural schematic diagram of the device 20 is as Figure 2 shown, including a creation module 21, where:

[0092] A creation module 21, configured to create a PaaS cloud registry for a target tenant according to the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant in a multi-tenant environment.

[0093] Optionally, the creation module 21 is configured to:

[0094] Obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant;

[0095] If any specified information among the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to the same specified information of other tenants, create the PaaS cloud registry for the target user.

[0096] Optionally, the apparatus is further configured to:

[0097] Obtain the service information of the microservices corresponding to the target user; wherein the service information includes the namespace of the microservices, the version information of the microservices, and the application information of the microservices;

[0098] Store the registration information of the microservices with the same service information in the same metadata of the PaaS cloud registry.

[0099] Optionally, the apparatus further includes:

[0100] A registration module, configured to register the microservices corresponding to the target tenant to the PaaS cloud registry through bytecode enhancement technology.

[0101] Optionally, the registration module is configured to:

[0102] Determine the target dimension information to be isolated when registering the microservices;

[0103] Add the target dimension information to the metadata of the PaaS cloud registry through bytecode enhancement technology.

[0104] Optionally, the apparatus further includes:

[0105] An inspection module, configured to inspect the service status of the microservices registered to the PaaS cloud registry;

[0106] A judgment module, configured to judge whether to re-register the microservices according to the service status.

[0107] Optionally, the judgment module is configured to:

[0108] If the service status of the microservice is healthy and the microservice does not exist in the Paas cloud registry, it is determined to re-register the microservice.

[0109] Optionally, a judgment module is used for:

[0110] If the service status of the microservice is healthy and the microservice exists in the Paas cloud registry, it is determined not to re-register the microservice; or,

[0111] If the service status of the microservice is unhealthy and the microservice exists in the Paas cloud registry, it is determined not to re-register the microservice; or,

[0112] If the service status of the microservice is unhealthy and the microservice does not exist in the Paas cloud registry, it is determined not to re-register the microservice.

[0113] Using the device provided in the embodiments of the present application,

[0114] A 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, thereby solving the problem in the prior art that since the used consul registry does not provide a multi-tenant isolation model for the cloud platform, the deployment requirements of the registry cloud service scenario cannot be met.

[0115] Embodiment 3

[0116] Figure 3 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present application. The electronic device 300 includes, but is not limited to: a radio frequency unit 301, a network module 302, an audio output unit 303, an input unit 304, a sensor 305, a display unit 306, a user input unit 307, an interface unit 308, a memory 309, a processor 310, and a power supply 311, etc. Those skilled in the art can understand that Figure 3 The structure of the electronic device shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements. In the embodiments of the present application, the electronic device includes, but is not limited to, mobile phones, tablet computers, laptop computers, palm computers, vehicle-mounted terminals, wearable devices, and pedometers, etc.

[0117] Among them, the processor 310 is used to create 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.

[0118] Optionally, create a PaaS cloud registry for the target tenant according to the data center information, cloud environment type information, VPC network information, and cluster information in multi-tenancy, including:

[0119] Obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant;

[0120] If any specified information in the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to the same specified information in other tenants, create the PaaS cloud registry for the target user.

[0121] Optionally, the method further includes:

[0122] Obtain the service information of the microservices corresponding to the target user; wherein, the service information includes the namespace of the microservice, the version information of the microservice, and the application information of the microservice;

[0123] Store the registration information of the microservices with the same service information in the same metadata of the PaaS cloud registry.

[0124] Optionally, the method further includes:

[0125] Register the microservices corresponding to the target tenant to the PaaS cloud registry through bytecode enhancement technology.

[0126] Optionally, registering the microservices corresponding to the target tenant to the PaaS cloud registry through bytecode enhancement technology includes:

[0127] Determine the target dimension information to be isolated when registering the microservice;

[0128] Add the target dimension information to the metadata of the PaaS cloud registry through bytecode enhancement technology.

[0129] Optionally, the method further includes:

[0130] Check the service status of the microservices registered to the PaaS cloud registry;

[0131] Judge whether to re-register the microservice according to the service status.

[0132] Optionally, judging whether to re-register the microservice according to the service status includes:

[0133] If the service status of the microservice is healthy and the microservice does not exist in the Paas cloud registration center, it is determined to re-register the microservice.

[0134] Optionally, determining whether to re-register the microservice according to the service status includes:

[0135] If the service status of the microservice is healthy and the microservice exists in the Paas cloud registration center, it is determined not to re-register the microservice; or,

[0136] If the service status of the microservice is unhealthy and the microservice exists in the Paas cloud registration center, it is determined not to re-register the microservice; or,

[0137] If the service status of the microservice is unhealthy and the microservice does not exist in the Paas cloud registration center, it is determined not to re-register the microservice.

[0138] A memory 309 is used to store a computer program that can run on a processor 310. When the computer program is executed by the processor 310, the above functions implemented by the processor 310 are realized.

[0139] It should be understood that in the embodiments of the present application, the radio frequency unit 301 can be used for receiving and sending signals during information reception or call processes. Specifically, after receiving downlink data from a base station, it is given to the processor 310 for processing; in addition, uplink data is sent to the base station. Usually, 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, etc. In addition, the radio frequency unit 301 can also communicate with a network and other devices through a wireless communication system.

[0140] The electronic device provides wireless broadband Internet access for users through the network module 302, such as helping users receive and send emails, browse web pages, and access streaming media, etc.

[0141] The audio output unit 303 can 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 it as sound. Moreover, the audio output unit 303 can also provide audio output related to specific functions executed by the electronic device 300 (for example, call signal reception sound, message reception sound, etc.). The audio output unit 303 includes a speaker, a buzzer, and a receiver, etc.

[0142] The input unit 304 is used to receive audio or video signals. The input unit 304 may include a Graphics Processing Unit (GPU) 3041 and a microphone 3042. The GPU 3041 processes the image data of static pictures or videos obtained by an image capture device (such as a camera) in the video capture mode or the image capture mode. The processed image frames can be displayed on the display unit 306. The image frames processed by the GPU 3041 can be stored in the memory 309 (or other storage media) or transmitted via the radio frequency unit 301 or the network module 302. The microphone 3042 can receive sounds and process such sounds into audio data. The processed audio data can be output in a format that can be transmitted to a mobile communication base station via the radio frequency unit 301 in the case of a phone call mode.

[0143] The electronic device 300 further includes 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 and a proximity sensor. Among them, the ambient light sensor can adjust the brightness of the display panel 3061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 3061 and / or the backlight when the electronic device 300 is moved to the ear. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of the electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; the sensor 305 can also 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 will not be elaborated here.

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

[0145] The user input unit 307 can be used to receive input numerical or character information and generate key signal inputs related to the 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 known as a touch screen, can collect touch operations of the user thereon or nearby (such as operations of the user using a finger, a stylus, or any suitable object or accessory on or near the touch panel 3071). The touch panel 3071 can include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the touch position of the user and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 310, and receives and executes the command sent by the processor 310. In addition, the touch panel 3071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 3071, the user input unit 307 can also include other input devices 3072. Specifically, the other input devices 3072 can include but are not limited to a physical keyboard, function keys (such as volume control keys, power on / off keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0146] Further, the touch panel 3071 can cover the display panel 3061. After the touch panel 3071 detects a touch operation thereon or nearby, it transmits the operation to the processor 310 to determine the type of touch event. Subsequently, the processor 310 provides a corresponding visual output on the display panel 3061 according to the type of touch event. Although in Figure 3 the touch panel 3071 and the display panel 3061 are implemented as two independent components to realize the input and output functions of the electronic device, in some embodiments, the touch panel 3071 and the display panel 3061 can be integrated to realize the input and output functions of the electronic device, and the specific implementation here is not limited.

[0147] The interface unit 308 is an interface for connecting an external device to the electronic device 300. For example, the external device can include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headset port, and so on. The interface unit 308 can be used to receive inputs from an external device (such as data information, power, etc.) and transmit the received inputs to one or more components within the electronic device 300 or can be used to transmit data between the electronic device 300 and the external device.

[0148] The memory 309 can be used to store software programs and various data. The memory 309 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.); the data storage area can store data created according to the use of the mobile phone (such as audio data, phone book, etc.). In addition, the memory 309 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0149] The processor 310 is the control center of the electronic device, connecting various parts of the entire electronic device through various interfaces and circuits. By running or executing the software programs and / or modules stored in the memory 309, and calling the data stored in the memory 309, it executes various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. The processor 310 may include one or more processing units; preferably, the processor 310 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor may not be integrated into the processor 310.

[0150] The electronic device 300 may also include a power supply 311 (such as a battery) for supplying power to each component. Preferably, the power supply 311 can be logically connected to the processor 310 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system.

[0151] In addition, the electronic device 300 includes some functional modules not shown here, which will not be elaborated here.

[0152] Preferably, an embodiment of the present application further provides an electronic device, including a processor 310, a memory 309, and a computer program stored on the memory 309 and operable on the processor 310. When the computer program is executed by the processor 310, it implements each process of the embodiment of the method for implementing the Paas cloud registration center service described above, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0153] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements each process of the above-mentioned method embodiments for implementing the Paas cloud registration center service and can achieve the same technical effects. To avoid repetition, details are not described herein again. Among them, the computer-readable storage medium includes, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.

[0154] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0155] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of the processes and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram.

[0156] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram.

[0157] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram.

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

[0159] Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0160] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0161] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0162] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for implementing a Paas cloud registration center service, characterized in that, Including: Create 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 a multi-tenant environment. 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 a multi-tenant environment includes: Obtain the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant. If any specified information among the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the corresponding tenant information of other tenants, create the PaaS cloud registry for the target tenant.

2. The method according to claim 1, characterized in that The method further includes: Obtain the service information of the microservices corresponding to the target tenant; wherein, the service information includes the namespace of the microservice, the version information of the microservice, and the application information of the microservice. Store the registration information of the microservices with the same service information in the same metadata of the PaaS cloud registry.

3. The method according to claim 1, characterized in that The method further includes: Register the microservices corresponding to the target tenant to the PaaS cloud registry through bytecode enhancement technology.

4. The method according to claim 3, characterized in that, Registering the microservices corresponding to the target tenant to the PaaS cloud registry through bytecode enhancement technology includes: Determine the target dimension information to be isolated when registering the microservice. Add the target dimension information to the metadata of the PaaS cloud registry through bytecode enhancement technology.

5. The method according to claim 3, wherein The method further includes: Check the service status of the microservices registered to the PaaS cloud registry. Judge whether to re-register the microservice according to the service status.

6. The method according to claim 5, characterized in that, Judging whether to re-register the microservice according to the service status includes: If the service status of the microservice is healthy and the microservice does not exist in the PaaS cloud registry, determine to re-register the microservice.

7. The method according to claim 5, wherein Judging whether to re-register the microservice according to the service status includes: If the service status of the microservice is healthy and the microservice exists in the PaaS cloud registry, determine not to re-register the microservice; or, If the service status of the microservice is unhealthy and the microservice exists in the PaaS cloud registry, determine not to re-register the microservice; or, If the service status of the microservice is unhealthy and the microservice does not exist in the PaaS cloud registry, determine not to re-register the microservice.

8. An implementation device for a Paas cloud registration center service, characterized in that, Including a creation module, where: The creation module is used to create 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 a multi-tenant environment. In the creation module, according to the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant in the multi-tenant environment, creating a Paas cloud registry for the target tenant, including: Obtaining the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant; If any specified information among the data center information, cloud environment type information, VPC network information, and cluster information of the target tenant is different from the tenant information corresponding to the any specified information in other tenants, creating the Paas cloud registry for the target tenant.

9. An electronic device, characterized in that, Including: A memory, a processor, and a computer program stored on the memory and executable on the processor, where when the computer program is executed by the processor, it implements the steps of the method for implementing the Paas cloud registry service according to any one of claims 1 to 7.

Images