Patent Application
20240396800
The present disclosure pertains generally to monitoring data centers and more particularly to systems and methods for configuring a tenant management view for a tenant of a multi-tenant data center.
A data center typically includes a number of computer servers in close proximity to each other arranged in server racks. Some data servers are setup by a business to serve just that business. However, many data centers serve a number of different colocation tenants, each assigned to particular computer servers within the data center. A data center may be divided into a number of server racks, with each server rack having a number of computer servers. In some cases, each colocation tenant may be assigned to one or more server racks within the data center. A need remains for improved systems and methods for quickly and easily configuring a tenant management view that provides a particular colocation tenant of a multiple-tenant data center with data center information that is related to the particular colocation tenant without providing unwanted information that pertains to other colocation tenants of the multiple-tenant data center.
This disclosure relates generally to monitoring data centers and more particularly to systems and methods for configuring a tenant management view for a colocation tenant of a multi-tenant data center. An example may be found in a computer implemented method for configuring a tenant management view that displays one or more operating characteristics of one or more data center resources that are associated with a colocation tenant of a data center, the one or more data center resources of the data center managed through a data center management supervisor that references a data center management database. The method includes storing in a memory a tag template that is associated with the colocation tenant of the data center. The tag template includes a query for identifying in the data center management database one or more data center resources that are associated with the colocation tenant. One or more processors apply the query of the tag template to the data center management database to identify the one or more data center resources associated with the colocation tenant. The one or more processors tag the identified one or more data center resources that are associated with the colocation tenant in the data center management database and report a value of one or more points associated with one or more of the data center resources that are tagged in the data center management database. The method includes displaying the reported value of one or more of the points in the tenant management view created for the colocation tenant.
Another example may be found in a system for configuring a tenant management view that displays one or more operating characteristics of one or more data center resources that are associated with a colocation tenant of a data center. The system includes a data center management supervisor that references a data center management database. The data center management supervisor is configured to manage the one or more data center resources of the data center. The system includes a tenant management supervisor and a message broker, wherein the data center management supervisor and the tenant management supervisor communicate via the message broker. The tenant management supervisor is configured to receive user input that defines at least in part a tag template that is associated with the colocation tenant of the data center. The tag template includes a query for identifying one or more data center resources associated with the colocation tenant of the data center in the data center management database and to publish the tag template to the message broker. The data center management supervisor is configured to subscribe to and receive the tag template via the message broker and to apply the query of the tag template to the data center management database to identify the one or more data center resources associated with the colocation tenant of the data center. The data center management supervisor is configured to tag the identified one or more data center resources that are associated with the colocation tenant of the data center and to publish a value of one or more points associated with one or more of the tagged data center resources to the message broker. The tenant management supervisor is configured to subscribe to and receive the value of one or more points associated with one or more of the tagged data center resources via the message broker and to display on a display the published value of one or more of the points in the tenant management view of the colocation tenant.
Another example may be found in a computer implemented method for configuring a tenant management view that displays one or more operating characteristics of one or more data center resources that are associated with a colocation tenant of a data center. The one or more data center resources of the data center are managed through a data center management supervisor that references a data center management database. The method includes storing in a memory a tag template that is associated with the colocation tenant of the data center. The tag template identifies one or more data center resources associated with the colocation tenant of the data center. One or more processors identify the one or more data center resources associated with the colocation tenant of the data center in the data center management database and tag the identified one or more data center resources that are associated with the colocation tenant of the data center. The one or more processors report a value of one or more points associated with one or more of the tagged data center resources and display the reported value of one or more of the points in the tenant management view of the colocation tenant.
The preceding summary is provided to facilitate an understanding of some of the features of the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments of the disclosure in connection with the accompanying drawings, in which:
While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit aspects of the disclosure to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
The following description should be read with reference to the drawings wherein like reference numerals indicate like elements. The drawings, which are not necessarily to scale, are not intended to limit the scope of the disclosure. In some of the figures, elements not believed necessary to an understanding of relationships among illustrated components may have been omitted for clarity.
All numbers are herein assumed to be modified by the term “about”, unless the content clearly dictates otherwise. The recitation of numerical ranges by endpoints includes all numbers subsumed within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).
As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include the plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.
It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that the feature, structure, or characteristic may be applied to other embodiments whether or not explicitly described unless clearly stated to the contrary.
To initially configuring the tenant management view for a particular colocation tenant of a data center, the tenant management supervisor 16 is configured to receive user input that defines at least in part a tag template for the particular colocation tenant. In some instances, the tag template includes a query for identifying one or more of the data center resources that are associated with the colocation tenant of the data center in the data center management database 14. In some instances, the data center resources include both data center resources and their respective points. In one example, the tenant management supervisor 16 is configured to publish the tag template to the message broker 18. The data center management supervisor 12 is configured to subscribe to and receive the tag template from the tenant management supervisor 16 via the message broker 18. The data center management supervisor 12 is configured to apply the query of the tag template to the data center management database 14 to identify the one or more data center resources associated with the colocation tenant and to tag the identified one or more data center resources that are associated with the colocation tenant. Subsequently, the data center management supervisor 12 is configured to publish a value of one or more points associated with one or more of the tagged data center resources to the message broker 18. In some cases, the data center management supervisor 12 is configured to repeatedly publish the value of one or more points associated with one or more of the tagged data center resources at predetermined intervals, upon a detected change in the value (COV), and/or at any other suitable time. In this example, the tenant management supervisor 16 is configured to subscribe to and receive the value of one or more points associated with one or more of the tagged data center resources via the message broker 18 as well as to display on a display the published value of one or more of the points in the tenant management view of the corresponding colocation tenant. In some instances, this may include publishing a model of tagged resources and points to the message broker 18.
In some instances, the tenant management supervisor 16 may be configured to receive user input that defines at least in part an updated tag template that is associated with the colocation tenant of the data center. The updated tag template may include an updated query for identifying one or more data center resources associated with the colocation tenant of the data center in the data center management database 14. The tenant management supervisor 16 may be configured to publish the updated tag template to the message broker 18. The data center management supervisor 12 may be configured to subscribe to and receive the updated tag template via the message broker and to apply the updated query of the updated tag template to the data center management database 14 to identify one or more updated data center resources associated with the colocation tenant of the data center. The data center management supervisor 12 may be configured to tag the identified one or more updated data center resources that are associated with the colocation tenant of the data center and to publish the value of one or more points associated with one or more of the tagged updated data center resources to the message broker 18. In some instances, this may include publishing a model of tagged resources and points to the message broker 18. The tenant management supervisor 16 may be configured to subscribe to and receive the value of one or more points associated with one or more of the tagged updated data center resources via the message broker 18 and to display on the display the published value of one or more of the points associated with one or more of the tagged updated data center resources in the tenant management view.
In some instances, the query of the tag template may include a plurality of queries for identifying the one or more data center resources associated with the colocation tenant of the data center. In some instances, the data center management supervisor 12 may be configured to publish a site registration to the message broker 18, wherein the site registration identifies the data center from a plurality of different data center sites. The tenant management supervisor 16 may be configured to subscribe and receive the site registration from the message broker 18 and to publish the tag template to the message broker 18 in response to receiving the site registration from the message broker 18. In some instances, the tenant management supervisor 16 may be configured to publish the tag template when the site registration from the message broker 18 corresponds to the data center that includes the one or more data resources associated with the colocation tenant.
In some instances, the tenant management supervisor may be configured to receive user input that defines at least in part a tag template for each of the plurality of colocation tenants of the data center. Each tag template may include a query for identifying one or more data center resources associated with the respective colocation tenant of the data center. In some instances, the data center management supervisor 12 may be configured to subscribe to and receive each tag template via the message broker 18, apply the query of each tag template to the data center management database 14 to identify the one or more data center resources associated with each of the respective colocation tenants of the data center, tag the identified one or more data center resources that are associated with each of the respective colocation tenant of the data center, and publish the value of one or more points associated with the one or more of the tagged data center resources associated with each of the respective colocation tenants to the message broker 18. In some instances, the model is published first. In some instances, the tenant management supervisor 16 may be configured to subscribe to and receive the value of one or more points associated with one or more of the tagged data center resources associated with each of the colocation tenants from the message broker 18 and to display a tenant management view for each of the colocation tenants, wherein the tenant management view includes the published value of one or more of the points associated with one or more of the tagged data center resources associated with the respective colocation tenant.
In some cases, rather than including a query, each tag template may provide a number of tag identifiers that identifies each of the one or more data center resources associated with the respective colocation tenant of the data center. The data center management supervisor 12 may be configured to subscribe to and receive each tag template via the message broker 18, use the tag identifiers of each tag template to identify the one or more data center resources associated with each of the respective colocation tenants of the data center, and publish the value of one or more points associated with the one or more of the tagged data center resources associated with each of the respective colocation tenants to the message broker 18. In some instances, the tenant management supervisor 16 may be configured to subscribe to and receive the value of one or more points associated with one or more of the tagged data center resources associated with each of the colocation tenants from the message broker 18 and to display a tenant management view for each of the colocation tenants, wherein the tenant management view includes the published value of one or more of the points associated with one or more of the tagged data center resources associated with the respective colocation tenant.
In this example method, one or more processors apply the query of the tag template to the data center management database to identify the one or more data center resources associated with the colocation tenant of the data center, as indicated at block 24. The one or more processors tag the identified one or more data center resources that are associated with the colocation tenant of the data center in the data center management database, as indicated at block 26. The one or more processors report a value of one or more points associated with one or more of the data center resources that are tagged in the data center management database, as indicated at block 28. The reported value of one or more of the points are displayed in the tenant management view of the corresponding colocation tenant of the data center, as indicated at block 30.
In some instances, the method 20 may further include updating the tag template, such as updating the query of the tag template, as indicated at block 32. In some instances, the one or more processors may apply the updated query of the tag template to the data center management database 14 to identify one or more updated data center resources associated with the colocation tenant of the data center, as indicated at block 34.
The method 20 continues in
In some instances, the method 20 may include the one or more processors detecting a change in value (COV) of one or more points associated with one or more of the data center resources that are tagged in the data center management database, as indicated at block 42. The one or more processors may report the value of one or more points associated with one or more of the data center resources that are tagged in the data center management database when a corresponding change in value (COV) is detected, as indicated at block 44. The reported value of one or more of the points associated with one or more of the data center resources may be displayed in the tenant management view of the corresponding colocation tenant of the data center subsequent to the model being published.
In some instances, the configuration of the tenant management view may be controlled through a tenant management supervisor. In some cases, the tag template is defined using the tenant management supervisor. The tenant management supervisor and the data center management supervisor may be operatively coupled via a message broker.
In the example shown, the tenant management supervisor publishes the tag template to a message broker, as indicated at block 50. One or more processors apply the query of the tag template to the data center management database to identify the one or more data center resources associated with the colocation tenant of the data center, as indicated at block 52. A data center management supervisor subscribes to and receives the tag template from the tenant management supervisor via the message broker, as indicated at block 54. The data center management supervisor applies the query of the tag template to the data center management database in order to identify the one or more data center resources that are associated with the colocation tenant of the data center, as indicated at block 56. In some cases, the data center management supervisor tags in the data center management database the identified one or more data center resources that are associated with the particular colocation tenant of the data center, as indicated at block 58.
The data center management supervisor publishes the value of one or more points associated with one or more of the data center resources that are tagged in the data center management database, as indicated at block 60. The tenant management supervisor subscribes to and receives the value of one or more points associated with the one or more of the data center resources that are tagged in the data center management database via the message broker, as indicated at block 62. The tenant management supervisor displays the reported value of one or more of the points in the tenant management view of the particular colocation tenant of the data center, as indicated at block 64. In some cases, the data center management supervisor monitors and detects a change in value (COV) of one or more points associated with one or more of the data center resources that are tagged in the data center management database, as indicated at block 66. The data center management supervisor publishes the updated value of one or more points associated with one or more of the data center resources that are tagged in the data center management database when a corresponding change in value (COV) is detected, as indicated at block 68. The tenant management supervisor receives the updated value of one or more points associated with the one or more of the data center resources that are tagged in the data center management database via the message broker, and displays the updated value of one or more of the points in the tenant management view of the particular colocation tenant of the data center.
In some instances, the tenant management view may be controlled by a tenant management supervisor (such as the tenant management supervisor 16) and the tenant management supervisor and the data center management supervisor may be operatively coupled via a message broker (such as the message broker 18). In some instances, the tag template may be defined and stored via the tenant management supervisor, and the tenant management supervisor may publish the tag template to the message broker. In some instances, the data center management supervisor subscribes to and receives the tag template via the message broker, and may identify the one or more data center resources associated with the particular colocation tenant in the data center management database. In some instances, the data center management supervisor may tag the identified one or more data center resources that are associated with the colocation tenant. The data center management supervisor may publish the value of one or more points associated with one or more of the data center resources to the message broker. The tenant management supervisor may subscribe to and receive the value of one or more points associated with one or more of the tagged data center resources via the message broker, and may display the published value of one or more of the points in the tenant management view of the particular colocation tenant of the data center.
The architecture 104 includes a tenant management supervisor 110. In some instances, the tenant management supervisor 110 may be considered as being an example of, or including, the tenant management server 90 shown in
The Tenant Management Supervisor 110 includes a Site Registration Subscriber Service 130 that subscribes to the site registration via the Registration block 128. The Site Registration Subscriber Service 130 allows for setting up the MQTT broker connection, subscribing to the Site Registration Topic, getting site details, and persisting a model database. Whenever a new site is received, the Site Registration Subscriber Service 130 evokes a Template Publish Service block 132, which is a service that reads tag templates from the database and publishes the tag templates. The Template Publish Service Block 132 communicates with a Tag Template block 134 that is part of the Tenant Management Broker 88. In some instances, publishing the Tag Template includes a tag rule that is used to identify the devices and point data from a site. As an example, this may include TagName, which is the name of the tag, Tags, which are the applicable devices that need to be tagged, and BqlQueries, which are the BWL queries that are used to search the devices. In one example, to tag all racks of the data center, the Tag Template may take the form of:
The DCM Supervisor 122 includes a Tag Change Subscriber Service block 136, which is a service that allows subscribing to a tag template and saving locally. If a previous tag template is found, they are compared to find any changes in the tag template. If any changes are found (including the creation of a new tag template), a Tag Change Event is raised. The TAG Change Subscriber Service block 136 subscribes to the Tag Template block 134. The DCM Supervisor 122 includes a Tagging Service block 138, which listens to Tag Change Events, scans the data center management database and tags the one or more data center resources and points by applying a Tag Rule. The Tag Rule may implement the query expressed in the tag template. Once complete, a Tagging Completed Event is raised. The DCM Supervisor 122 includes a Model Sync Service block 140, which listens to the Tagging Completed Event and uses the Tag Template to get the Tagged elements and points and generates a model. The Model sync Service block 140 publishes the model for the particular colocation tenant to a Model block 144 within the Tenant Management Broker 88. The DCM Supervisor 122 includes a Property Sync Service block 142 that listens for COV events for a point and publishes the value to the Tenant Management Broker 88 for display on the tenant management view of the particular colocation tenant of the data center.
The Tenant Management Broker 88 includes a Property block 146 that subscribes to the Model block 144 in order to obtain updated information from the model. The Tenant Management Broker 88 also includes a Model Sync Subscriber Service block 148 that allows for subscribing to the model topics and saving to the database 94. Publishing the model includes publishing the tagged devices and points from the published model 144. This may include a SiteID, which is a site unique identifier, a Name, which is the name of the device, and one or more PropertyEntities, which may be a list of points associated with the device. Publishing Property Details includes publishing a change of value for a point. This may include a LastUpdated value, which is the date and time the data was recorded, a Points listing, which is a listing of points data, an ID value, which is the point unique site identifier, and a Value, which is the value for that point at that time.
The Tenant Management Supervisor 110 includes both a Tag Template Service block 112a and a Tenant Service block 112b. The colocation admin 102 may initially configure a new colocation tenant via the tenant service block 112b and create and/or update a colocation tenant entry in the database 94. The colocation admin 102 may also configure (e.g. create and/or update) the tag template for the particular colocation tenant via the tag template service 112a. Once configured, the tag template service 112a may provide the tag template to the template publish service 132, which may publish the tag template to the tenant manager broker 88 as described above.
The following table provides an illustrative listing of available tags that may be referenced in the tag template and/or used to identify and tag points in the data center management database 14. The illustrative listing includes a listing of points, a listing of corresponding equipment types and corresponding tags that correspond to the particular point and the particular equipment types. These tags may be referenced in the tag template (e.g. in the blqquery) and/or used to identify and tag points in the data center management database.
Those skilled in the art will recognize that the present disclosure may be manifested in a variety of forms other than the specific embodiments described and contemplated herein. Accordingly, departure in form and detail may be made without departing from the scope and spirit of the present disclosure as described in the appended claims.
