IP Library Granted Patent US 10,127,296
Granted Patent B2
US 10,127,296 · App. 13/082,194 · Granted Nov 13, 2018

Cooperative naming for configuration items in a distributed configuration management database environment

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,127,296
App. No.
13/082,194
Granted
Nov 13, 2018
Kind
B2
Abstract

Disclosed are methods and systems to provide coordinated identification of data items across a plurality of distributed data storage repositories (datastores). In one disclosed embodiment, a single configuration management database (CMDB) controls identification rights for all CIs as they are first identified in a master/slave relationship with all other CMDBs in the distributed environment. In a second embodiment, a plurality of CMDBs divide identification rights based upon coordination identification rules where certain CMDBs are assigned authoritative identification rights for CIs matching the rules of a particular CMDB in the distributed environment. In a third embodiment, one or more of the plurality of CMDBs may also have advisory identification rights for CIs which do not already have an identifiable unique identity and can coordinate with an authoritative CMDB to establish an identity for CIs.

Claims (28)

1. A method for improving distributed configuration management databases (CMDBs) that include a plurality of communicatively-coupled datastores, the method comprising:

establishing an authoritative and absolute identification of a configuration item (CI), the authoritative and absolute identification being an identification that is persistent in the distributed CMDBs irrespective of any configuration status of the CI, the establishing by:

receiving, for a first time at a first communicatively-coupled datastore, an indication of a presence of the CI on a network, the CI not having a recognizable unique identifier across the distributed CMDBs, the first communicatively-coupled datastore having no advisory or authoritative and absolute identification rights for the CI;

applying rules to the indication received at the first communicatively-coupled datastore to select a second communicatively-coupled datastore, the second communicatively-coupled datastore having authoritative and absolute identification rights for the CI,

sending information regarding the CI from the first communicatively-coupled datastore to the second communicatively-coupled datastore;

determining, by the second datastore, an identifier for the CI as being the recognizable unique identifier of the CI across the distributed CMDBs and being the persistent, authoritative and absolute identification of the CI in the distributed CMDBs irrespective of any configuration status of the configuration item;

receiving, at the first communicatively-coupled datastore the unique identifier for the CI as determined by the second communicatively-coupled datastore; and

populating the first communicatively-coupled datastore with the unique identifier as the persistent, authoritative and absolute identification of the CI in the distributed CMDBs irrespective of any configuration status of the CI.

2. The method of claim 1 , wherein the first communicatively-coupled datastore and the second communicatively-coupled datastore comprise a CMDB.

3. The method of claim 1 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on a class of the CI.

4. The method of claim 3 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore further comprises applying rules for selecting the second communicatively-coupled datastore based on a subclass of the class of the CI.

5. The method of claim 1 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on logical, physical, or geographical location of the CI.

6. The method of claim 1 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on an attribute of a class of the CI.

7. A computer network linking distributed configuration management databases (CMDBs) that include a plurality of communicatively-coupled datastores, the computer network comprising:

a plurality of processing units; and

at least one memory storing instructions that, when executed by at least one of the plurality of processing units, causes the computer network to:

establish an authoritative and absolute identification of a configuration item (CI), the authoritative and absolute identification being an identification that is persistent in the distributed CMDBs irrespective of any configuration status of the CI, by:

receiving for a first time an indication of the CI at a first communicatively-coupled datastore, the CI not having a recognizable unique identifier across the distributed CMDBs, the first communicatively-coupled datastore having no advisory or authoritative and absolute identification rights for the CI;

applying rules to the indication received at the first communicatively-coupled datastore to select a second communicatively-coupled datastore, the second datastore having authoritative and absolute identification rights for the CI as determined by the applied rules;

sending information regarding the CI from the first communicatively-coupled datastore to the second communicatively-coupled datastore;

determining, by the second communicatively-coupled datastore, an identifier for the CI as being the recognizable unique identifier of the CI across the distributed CMDBs and being the persistent, authoritative and absolute identification of the CI in the distributed CMDBs irrespective of any configuration status of the CI;

receiving, at the first communicatively-coupled datastore the unique identifier for the CI as determined by the second communicatively-coupled datastore; and

populating the first communicatively-coupled datastore with the unique identifier as the persistent, authoritative and absolute identification of the CI in the distributed CMDBs irrespective of any configuration status of the CI.

8. The computer network of claim 7 , wherein the first communicatively-coupled datastore and the second communicatively-coupled datastore comprise a CMDB.

9. The computer network of claim 7 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on a class of the CI.

10. The computer network of claim 9 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore further comprises applying rules for selecting the second communicatively-coupled datastore based on a subclass of the class of the CI.

11. The computer network of claim 7 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on logical, physical, or geographical location of the CI.

12. The computer network of claim 7 , wherein the act of applying rules to the indication received at the first communicatively-coupled datastore comprises applying rules for selecting the second communicatively-coupled datastore based on an attribute of a class of the CI.

Assignments (16)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2025
From: BMC SOFTWARE, INC.
To: BMC HELIX, INC.
Reel/Frame 070442/0197 →
GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0628 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0568 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052854/0139) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0617 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052844/0646) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0408 →
OMNIBUS ASSIGNMENT OF SECURITY INTERESTS IN PATENT COLLATERAL Recorded Mar 4, 2024
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING COLLATERAL AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR COLLATERAL AGENT
Reel/Frame 066729/0889 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 1, 2024
From: ALTER DOMUS (US) LLC
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 066567/0283 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Sep 30, 2021
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 057683/0582 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052854/0139 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052844/0646 →
SECURITY INTEREST Recorded Sep 10, 2019
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 050327/0634 →
RELEASE OF PATENTS Recorded Oct 5, 2018
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.; BMC ACQUISITION L.L.C.
Reel/Frame 047198/0468 →
SECURITY INTEREST Recorded Oct 2, 2018
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047185/0744 →
SECURITY AGREEMENT Recorded Sep 11, 2013
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 031204/0225 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY DATA TO ADD AN OMITTED ASSIGNOR PREVIOUSLY RECORDED ON REEL 026094 FRAME 0252. ASSIGNOR(S) HEREBY CONFIRMS THE THE CONVEYING PARTY DATA SHOULD INCLUDE MATTHEW CONNORS AS AN ASSIGNOR. Recorded Aug 27, 2013
From: RANGARAJAN, GOVINDARAJAN; KUMAR, NARAYAN; MUELLER, DOUGLAS; KUMAR, AJOY; WALLACE, DARIUS; CONNORS, MATTHEW
To: BMC SOFTWARE, INC.
Reel/Frame 031095/0597 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 7, 2011
From: RANGARAJAN, GOVINDARAJAN; KUMAR, NARAYAN; MUELLER, DOUGLAS; KUMAR, AJOY; WALLACE, DARIUS
To: BMC SOFTWARE,INC.
Reel/Frame 026094/0252 →