Detailed Description
The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first", "second" and "third" in this application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any indication of the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of the feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specified otherwise. All directional indications (such as up, down, left, right, front, and rear … …) in the embodiments of the present application are only used to explain the relative positional relationship between the components, the movement, and the like in a specific posture (as shown in the drawings), and if the specific posture is changed, the directional indication is changed accordingly. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The cloud computing product of the embodiment of the invention comprises: the system comprises resources and services, and a unified operation and maintenance platform manages and monitors the resources and the services, wherein the resources generally refer to IaaS layer infrastructure, specifically to physical servers or other infrastructures (such as containers, virtual machines and the like), the services generally refer to Paas layer open source cloud computing framework services, Saas layer business services and new cloud computing products formed by freely combining the Paas layer open source cloud computing framework services and the Saas layer business services, and the services are configured on the resources.
Fig. 1 is a schematic flowchart of a unified operation and maintenance method for cloud computing products according to a first embodiment of the present invention. It should be noted that the method of the present invention is not limited to the flow sequence shown in fig. 1 if the results are substantially the same. As shown in fig. 1, the method comprises the steps of:
step S101: and constructing a cascaded multi-stage operation and maintenance platform.
In step S101, the multi-stage operation and maintenance platform may be two stages or more. Step S101 includes the steps of: the method comprises the steps of monitoring an operation and maintenance platform of a current level in real time, generating an operation and maintenance platform of a previous level of the operation and maintenance platform of the current level when the operation and maintenance platform of the current level needs to be added with a new operation and maintenance platform, and cascading the operation and maintenance platform of the previous level with the operation and maintenance platform of the current level. At this time, each operation and maintenance platform at the previous level manages one or more operation and maintenance platforms at the current level, and the operation and maintenance platform at the previous level monitors and manages the operation and maintenance platform at the next level managed by the operation and maintenance platform at the previous level.
Step S102: the operation and maintenance platform of the current level receives a first call instruction of resources or/and services issued by the operation and maintenance platform of the previous level, so that the operation and maintenance platform of the current level operates the resources or/and services according to the first call instruction to form a target operation and maintenance platform of the current level.
In step S102, the operation and maintenance platform at the previous level supports adding, modifying or deleting the operation and maintenance platform at the previous level, and the operation and maintenance platform at the current level supports adding, modifying or deleting the operation and maintenance platform at the current level. Each operation and maintenance platform of the current level is configured with a unique request address, when the operation and maintenance platform of the previous level issues a first call instruction, the operation and maintenance platforms of the current level can be switched randomly according to different request addresses, and the corresponding operation and maintenance platform of the current level selects the configured resources or/and services to operate according to the first call instruction, so as to form a target operation and maintenance platform of the current level.
According to the cloud computing product-oriented unified operation and maintenance method, resources and services can be conveniently and effectively managed and monitored through the cascaded multi-stage operation and maintenance platforms, the operation and maintenance platforms in all regions are integrated, a large data cluster environment is simply and efficiently established, and data sharing among the multi-stage operation and maintenance platforms is achieved.
Fig. 2 is a flowchart illustrating a cloud computing product-oriented unified operation and maintenance method according to a second embodiment of the present invention. It should be noted that the method of the present invention is not limited to the flow sequence shown in fig. 2 if the results are substantially the same. As shown in fig. 2, the method comprises the steps of:
step S201: and constructing a cascaded multi-stage operation and maintenance platform.
Step S201 in this embodiment is similar to step S101 in fig. 1, and is not described in detail here.
Step S202: and reporting the data information of the operation and maintenance platform of the current level to the operation and maintenance platform of the previous level in real time by the operation and maintenance platform of the current level.
In step S202, the operation and maintenance platform at the previous level receives and views the data information of the operation and maintenance platform at the current level reported by the operation and maintenance platform at the current level in real time, generates a first call instruction according to the data information of the operation and maintenance platform at the current level, and executes step S203.
In this embodiment, referring to fig. 3, step S202 further includes the following steps:
step S2021: and monitoring resources and services in the operation and maintenance platform of the current level, and acquiring monitoring data.
In step S2021, newly added resources in the operation and maintenance platform of the current level and services configured on the newly added resources are monitored in real time; and deploying an Agent module on the newly added resource to acquire the newly added resource and monitoring data of the service configured on the newly added resource. In the embodiment, when new resources exist, the Agent module is deployed on the new resources, the Agent module is allowed to be expanded on the management node, the Agent module deployed on the new resources is managed on the management node, and the Agent module is allowed to be deleted by the management node.
Step S2022: and reporting the monitoring data to a first database and storing the monitoring data in the first database.
In step S2022, data integration is performed before the monitoring data is reported to the first database.
In step S2022, before the monitoring data is stored in the first database, a matching rule preset by a user is received, and a storage condition of the first database is obtained; judging whether the storage condition of the first database meets the matching rule or not; and when the storage condition of the first database meets the matching rule, sending an alarm message.
Step S2023: and managing the resources and/or the services according to the monitoring data to form a new service product, and acquiring the management data of the resources and/or the services.
In step S2023, the service product is configured and managed, and the service product information is configured, for example: access an IP address, username, and login password.
Step S2024: the management data is stored in a second database.
Step S2025: and reporting the monitoring data and/or the management data to the previous operation and maintenance platform in real time by the operation and maintenance platform of the current level.
Step S203: the operation and maintenance platform of the current level receives a first call instruction of resources or/and services issued by the operation and maintenance platform of the previous level.
Step S204: the operation and maintenance platform of the current level sends a request authentication instruction and receives an authentication result; when the authentication result is that the first call instruction meets the authentication requirement of the operation and maintenance platform of the current hierarchy, step S205 is executed.
In step S204, the operation and maintenance platform at the previous level may call one or more operation and maintenance platforms in the operation and maintenance platform at the current level, the operation and maintenance platform at the current level receives a first call instruction to start the operation and maintenance platform at the current level to execute an authentication service so as to check whether the operation and maintenance platform at the previous level has a right for the operation and maintenance platform at the current level requested to be called, if so, step S205 is executed, otherwise, the first call instruction is not executed.
Step S205: and operating the resources or/and services of the operation and maintenance platform of the current level according to the first calling instruction to form a target operation and maintenance platform of the current level.
In step S205, step S205 in this embodiment is similar to step S102 in fig. 1, and is not repeated here.
The cloud computing product-oriented unified operation and maintenance method in the second embodiment of the invention supports dynamic resource expansion and dynamic Agent module expansion on the basis of the first embodiment, directly deploys the Agent module on the expanded resource, gets rid of the complex and complicated process of cloud computing product installation and deployment, builds a big data cluster environment simply and efficiently, and realizes data sharing.
Fig. 4 is a flowchart illustrating a cloud computing product-oriented unified operation and maintenance method according to a third embodiment of the present invention. It should be noted that the method of the present invention is not limited to the flow sequence shown in fig. 4 if the results are substantially the same. As shown in fig. 4, the method includes the steps of:
step S401: and constructing a cascaded multi-stage operation and maintenance platform.
In step S401, the multi-stage operation and maintenance platform has more than two stages. Step S401 includes the steps of:
monitoring an operation and maintenance platform of a current level in real time, and generating an operation and maintenance platform of a previous level of the operation and maintenance platform of the current level when the operation and maintenance platform of the current level needs to be added with a new operation and maintenance platform, wherein the operation and maintenance platform of the previous level is cascaded with the operation and maintenance platform of the current level;
monitoring the next-level operation and maintenance platform of the current-level operation and maintenance platform in real time; and when monitoring that a next-level operation platform needs to be added with a new operation platform, generating the operation platform of the current level, and cascading the operation platform of the current level and the operation platform of the next level.
At this time, when the multi-level operation and maintenance platform is of three levels, the operation and maintenance platform of the current level is the operation and maintenance platform of the middle level, and the multi-level operation and maintenance platform includes the operation and maintenance platform of the next level (i.e., the operation and maintenance platform of the bottom level), the operation and maintenance platform of the current level (i.e., the operation and maintenance platform of the middle level), and the operation and maintenance platform of the previous level. Each upper-level operation and maintenance platform manages one or more current-level operation and maintenance platforms, the upper-level operation and maintenance platform monitors and manages the current-level operation and maintenance platform managed by the upper-level operation and maintenance platform, each current-level operation and maintenance platform manages one or more next-level operation and maintenance platforms, and the current-level operation and maintenance platform monitors and manages the next-level operation and maintenance platform managed by the current-level operation and maintenance platform. The operation and maintenance platform of the previous level, the operation and maintenance platform of the current level and the operation and maintenance platform of the next level all support the addition, modification or deletion of the operation and maintenance platform in the current level.
Step S402: the operation and maintenance platform of the current level receives a first call instruction of resources or/and services issued by the operation and maintenance platform of the previous level, so that the operation and maintenance platform of the current level operates the resources or/and services according to the first call instruction to form a target operation and maintenance platform of the current level; and the current-level operation and maintenance platform issues a second calling instruction of the resource or/and the service to the next-level operation and maintenance platform, so that the next-level operation and maintenance platform operates the resource or/and the service according to the second calling instruction to form a next-level target operation and maintenance platform.
In step S402, each operation and maintenance platform of the current level is configured with a unique request address, when the operation and maintenance platform of the previous level issues a first call instruction, the operation and maintenance platform of the current level may be switched randomly according to different request addresses, and the corresponding operation and maintenance platform of the current level selects a resource or/and a service that has been configured according to the first call instruction to perform an operation, so as to form a target operation and maintenance platform of the current level. Similarly, each next-level operation and maintenance platform is configured with a unique request address, when the current-level operation and maintenance platform issues a second call instruction, the next-level operation and maintenance platform can be switched randomly according to different request addresses, and the corresponding next-level operation and maintenance platform selects the configured resources or/and services to operate according to the second call instruction, so as to form a next-level target operation and maintenance platform.
In this embodiment, after the cascaded multi-stage operation and maintenance platform is constructed, the following steps may be implemented between the operation and maintenance platform of the current level and the operation and maintenance platform of the next level: the operation and maintenance platform of the current level receives the data information of the operation and maintenance platform of the next level reported by the operation and maintenance platform of the next level in real time; the operation and maintenance platform of the current level generates a second call instruction according to the data information of the operation and maintenance platform of the next level and issues the second call instruction of resources or/and services to the operation and maintenance platform of the next level; after receiving the second call instruction, the operation and maintenance platform of the next level sends an authentication request instruction and receives an authentication result; and when the authentication result is that the second call instruction meets the authentication requirement of the next-level operation and maintenance platform, executing the second call instruction, and forming the next-level target operation and maintenance platform by the resources or/and the services of the next-level operation and maintenance platform.
The method can be realized between the current-level operation and maintenance platform and the previous-level operation and maintenance platform: reporting data information of the operation and maintenance platform of the current level to an operation and maintenance platform of an upper level in real time by the operation and maintenance platform of the current level; the operation and maintenance platform at the upper level generates a first call instruction according to the data information of the operation and maintenance platform at the current level and issues the first call instruction of resources or/and services to the operation and maintenance platform at the current level, and after receiving the first call instruction, the operation and maintenance platform at the current level sends a request authentication instruction and receives an authentication result; and when the authentication result is that the first calling instruction meets the authentication requirement of the operation and maintenance platform of the current level, executing the first calling instruction, and forming the target operation and maintenance platform of the current level by the resources or/and the services of the operation and maintenance platform of the current level.
The cloud computing product-oriented unified operation and maintenance method of the third embodiment of the present invention can conveniently and effectively manage resources and services through the cascaded multi-stage operation and maintenance platforms on the basis of the first embodiment, so as to enable the higher-level operation and maintenance platform to directly check and operate the data information of the lower-level operation and maintenance platform, and meanwhile, the lower-level operation and maintenance platform reports the data information to the higher-level operation and maintenance platform in real time, thereby implementing data sharing between the multi-stage operation and maintenance platforms.
Fig. 5 is a unified operation and maintenance platform system for cloud computing products according to a first embodiment of the present invention, where the unified operation andmaintenance platform system 50 includes two levels, where the two levels are: the operation andmaintenance platform 51 at the upper level and the operation andmaintenance platform 52 at the bottom level, and the operation andmaintenance platform 51 at the upper level cascades the operation andmaintenance platform 52 at the bottom level for nanotube management.
In this embodiment, referring to fig. 6, the operation andmaintenance platform 52 at the bottom level includes: theAgent module 520, thedata integration module 521, thefirst database 522, theresource management module 523, theservice management module 524, thesecond database 525 and theRegion interface module 526 are configured for each resource, each resource is configured with oneAgent module 520, the operation andmaintenance platform 52 at the bottom level supports adding and deleting resources, and when a new resource is added, theAgent modules 520 are deployed on the new resource.
Further, the Agent module 520 mainly functions as: (1) resource discovery, allowing a user to discover resources; (2) resource management, which allows the operations of starting up, shutting down, restarting, modifying node configuration (such as system name, network card IP and the like) and the like of resources to be executed after the resources are managed; (3) service management, allowing a user to call a service script to execute operations such as installation, starting, restarting and upgrading according to a template provided by the service; (4) service discovery, which allows a user to discover services existing in resources after the user manages the resources; (5) the command transparent transmission allows a user to send a command to a specified node to execute according to a template provided by the service; (6) file transmission, allowing a user to send or receive files through the Agent module 520; collecting server general information such as: system information such as a CPU, a memory, a network and the like is reported to the first database 522 for storage; (7) collecting service runtime occupied resource information, such as: the service occupies information such as a CPU and a memory, and reports the information to the first database 522 for storage; (8) the method comprises the steps that specific information of the service is collected, the collection method requires the service to provide a user-defined collection template, and after the collection is carried out by the Agent module 520, the front end calls relevant collection indexes according to the service template and finally presents the collection indexes in a front end page module.
Further, theAgent module 520 includes an AFM (Agent For management) sub-module and an AFS (Agent For super provider) sub-module, the AFM sub-module is used For monitoring and managing resources and services, acquiring monitoring data, and mainly implementing functions of automatic resource discovery, resource management, service discovery, command transparent transmission, and the AFS sub-module is used For collecting, summarizing, and reporting the monitoring data, and mainly implementing functions of file transmission, collecting general information of a server, collecting resource information occupied when the service operates, collecting specific information of the service, and the like. Thedata integration module 521 is configured to receive the monitoring data reported by the AFS submodule and integrate the monitoring data to obtain integrated data; afirst database 522 for storing the integration data and providing a query service; theresource management module 523 is configured to query the integration data, issue a first request instruction for invoking the AFM sub-module according to a query result, and operate a resource and a service; theservice management module 524 is configured to query the integrated data in thefirst database 522, issue a second request instruction for calling the AFM sub-module according to a query result, assemble the service, and form a new service product; theRegion interface module 526 is responsible for system configuration related settings and all platform interface calls, and directly calls thefirst database 522, theresource management module 523, and theservice management module 524.
In this embodiment, theAgent modules 520 may be dynamically expanded, themultiple Agent modules 520 are managed and monitored by the operation and maintenance management node, and the operation and maintenance management node supports a request to call eachAgent module 520, for example: the infrastructure is started and shut down, the service is started and stopped, and eachAgent module 520 reports monitoring data to the operation and maintenance management node. In the operation andmaintenance platform 52 of the bottom layer level, theAgent module 520 is deployed on the resources needing to be managed, and has expandability. The operation andmaintenance platform 52 of the bottom hierarchy level is newly added with a resource, as long as theAgent module 520 is deployed in the resource, the node is managed through the operation and maintenance management node, and meanwhile, the operation andmaintenance platform 52 of the bottom hierarchy level also supports deletion of the node.
Optionally, the operation andmaintenance platform 52 at the bottom level further includes alog service module 527, and thelog service module 527 is configured to issue a third request instruction for calling the AFM sub-module, so as to build an elk log analysis system and provide a log service query.
Optionally, the operation andmaintenance platform 52 of the bottom layer further includes aconfiguration management module 528, and theconfiguration management module 528 is configured to configure ID information of theresource management module 523, theservice management module 524, and thelog service module 527, where the ID information includes an access IP address, a user name, and a login password.
Optionally, the operation andmaintenance platform 52 of the bottom hierarchy level further includes asecond database 525, and thesecond database 525 is configured to store data information of theresource management module 523, theservice management module 524, and thelog service module 527.
Optionally, the operation andmaintenance platform 52 at the bottom level further includes: the rule matchingalarm service module 529 receives a matching rule preset by a user through theRegion interface module 526, and when the storage condition of thefirst database 522 meets the matching rule, an alarm message is sent. The rule matchingalarm service module 529 of this embodiment pushes the alarm message through a message subscription.
Optionally, the operation andmaintenance platform 52 at the bottom level further includes: theauthentication service module 530 is configured to control an access right of theRegion interface module 526, when theRegion interface module 526 receives a first call instruction issued by the operation andmaintenance platform 51 of the upper stage, theauthentication service module 530 receives an authentication request and determines whether the first call instruction is full of an authentication requirement of the operation andmaintenance platform 52 of the sole level, and feeds back an authentication result, and when the first call instruction is full of the authentication requirement of the operation andmaintenance platform 52 of the sole level, theRegion interface module 526 allows the operation andmaintenance platform 51 of the upper stage to call the operation andmaintenance platform 52 of the sole level and execute the first call instruction.
The operation and maintenance platform at the bottom level of the embodiment of the invention can provide state management and monitoring of infrastructure as a service (IaaS) layer infrastructure, a platform as a service (PaaS) layer open source cloud computing framework service and a service at a software as a service (SaaS) layer, semi-automatically repair abnormal services, support dynamic expansion of resources and dynamic expansion of anAgent module 520, directly deploy theAgent module 520 on the expanded resources, and get rid of the complicated and complicated process of installation and deployment of cloud computing products.
In this embodiment, each operation andmaintenance platform 52 at the bottom level reports data information to the operation andmaintenance platform 51 at the upper level in real time, each operation andmaintenance platform 52 at the bottom level configures a corresponding request address, and the operation andmaintenance platform 51 at the upper level issues a first call instruction to the operation andmaintenance platform 52 at the corresponding bottom level through the request address, so as to operate resources or/and services in the operation andmaintenance platform 52 at the bottom level, and form a target operation and maintenance platform at the bottom level.
In this embodiment, theRegion interface module 526 of each bottom-level operation andmaintenance platform 52 sets a unique request address, and each time the operation andmaintenance platform 51 at the previous level newly adds one bottom-level operation andmaintenance platform 52 for nanotube, the newly added request address of theRegion interface module 526 is stored, and in an actual working process, the operation andmaintenance platform 51 at the previous level may be switched to theRegion interface module 526 of any one bottom-level operation andmaintenance platform 52 for nanotube.
When the operation andmaintenance platform 51 at the upper level issues the first call instruction to the operation andmaintenance platform 52 at the corresponding lower level through the request address, authentication service needs to be performed through theauthentication service module 530, when the operation andmaintenance platform 52 at the lower level receives the first call instruction issued by the operation andmaintenance platform 51 at the upper level, theauthentication service module 530 receives the authentication request of the operation andmaintenance platform 52 at the lower level and judges whether the first call instruction is full of the authentication requirement of the operation andmaintenance platform 52 at the lower level, and feeds back the authentication result, and when the first call instruction is full of the authentication requirement of the operation andmaintenance platform 52 at the lower level, the operation andmaintenance platform 52 at the lower level executes the first call instruction, so that the target operation and maintenance platform at the lower level is formed.
The cloud computing product-oriented unified operation and maintenance platform system provides a cascading mode to integrate operation and maintenance platforms of all areas, and an upper operation and maintenance platform directly checks and operates data information of a lower operation and maintenance platform; meanwhile, the lower operation and maintenance platform reports data to the upper operation and maintenance platform in real time, and data sharing is achieved.
Fig. 7 is a unified operation and maintenance platform system for cloud computing products according to a second embodiment of the present invention, where the unified operation andmaintenance platform system 70 includes three levels, where the three levels are: the operation andmaintenance platform 71 at the bottom level, the operation andmaintenance platform 72 at the middle level and the operation andmaintenance platform 73 at the upper level, wherein the operation andmaintenance platform 72 at the middle level is equivalent to the lower level of the operation andmaintenance platform 73 at the upper level and is equivalent to the upper level of the operation andmaintenance platform 71 at the bottom level, the operation andmaintenance platform 73 at the upper level cascades the operation andmaintenance platform 72 at the middle level of the nano tubes, and the operation andmaintenance platform 72 at the middle level cascades the operation andmaintenance platform 71 at the bottom level of the nano tubes.
The middle-level operation platform 72 and the bottom-level operation platform 71 in this embodiment are similar to the bottom-level operation platform 52 in fig. 5, and are not described in detail here.
In this embodiment, each bottom-level operation and maintenance platform 71 is configured with a corresponding first request address, the bottom-level operation and maintenance platform 71 reports data information of the bottom-level operation and maintenance platform 71 to the cascaded middle-level operation and maintenance platform 72 in real time, the middle-level operation and maintenance platform 72 issues a second call instruction to the corresponding bottom-level operation and maintenance platform 71 through the first request address, and operates resources or/and services in the bottom-level operation and maintenance platform 71 to form a bottom-level target operation and maintenance platform, and simultaneously reports data information of the middle-level operation and maintenance platform 72 to the cascaded upper-level operation and maintenance platform 73 in real time, each middle-level operation and maintenance platform 72 is configured with a corresponding second request address, the upper-level operation and maintenance platform 73 issues a first call instruction to the corresponding middle-level operation and maintenance platform 72 through the second request address, and operates resources or/and services in the middle-level operation and maintenance platform 72, to form a middle-level target operation and maintenance platform, and meanwhile, receive the data information of the cascaded middle-level operation and maintenance platform 72 and display the data information in the front-end page module 74.
Further, the operation andmaintenance platform 71 at the bottom level is provided with a firstauthentication service module 710, the firstauthentication service module 710 is used for controlling the access right of the operation andmaintenance platform 71 at the bottom level, the firstauthentication service module 710 receives the authentication request and judges whether the second call instruction is full of the authentication requirement of the operation andmaintenance platform 71 at the sole level, the authentication result is fed back, and when the second call instruction is full of the authentication requirement of the operation andmaintenance platform 71 at the sole level, the operation andmaintenance platform 71 at the bottom level executes the second call instruction.
Further, the middle-level operation andmaintenance platform 72 is provided with a secondauthentication service module 720, the secondauthentication service module 720 is used for controlling the access right of the middle-level operation andmaintenance platform 72, the secondauthentication service module 720 receives the authentication request and judges whether the first call instruction meets the authentication requirement of the middle-level operation andmaintenance platform 72, the authentication result is fed back, and when the first call instruction meets the authentication requirement of the middle-level operation andmaintenance platform 72, the middle-level operation andmaintenance platform 72 executes the first call instruction.
On the basis of the first embodiment of the invention, the cloud computing product-oriented unified operation and maintenance platform system of the second embodiment of the invention is provided with a plurality of levels, a cascade mode is provided to integrate operation and maintenance platforms of various regions, and an upper operation and maintenance platform directly checks and operates data information of a lower operation and maintenance platform managed by the upper operation and maintenance platform; meanwhile, the lower-level operation and maintenance platform reports data to the upper-level operation and maintenance platform in real time, and data sharing is achieved.
In other embodiments, the multi-level operation and maintenance platform has more than three levels, and the cascade connection manner between the levels and the unified operation and maintenance method are similar to those described above, and are not described in detail herein.
The above are only embodiments of the present application, and not intended to limit the scope of the present application, and all equivalent structures or equivalent processes performed by the present application and the contents of the attached drawings, which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.