Configuration drift prevention across multiple systems using blockchain

Patent metadata

Field	Value
Publication number	US-10997150-B2
Application number	US-201815980284-A
Country	US
Kind code	B2
Filing date	May 15, 2018
Priority date	May 15, 2018
Publication date	May 4, 2021
Grant date	May 4, 2021

Abstract

An example operation may include one or more of creating a child ledger for each new environment that is setup, updating a master ledger when a smart contract condition is met, and when the master ledger is updated, initiating deployment of an update to a plurality of managed environments.

First claim

What is claimed is:

1. A method, comprising:
creating, via a processor, a plurality of child ledgers for a plurality of managed computing environments, respectively, each child ledger comprising a respective sequence of hash-linked blocks storing configuration content of a different respective managed computing environment;
updating, via the processor, a configuration of the plurality of managed computing environments via a master ledger when a smart contract condition is met; and
when the master ledger is updated, deploying, via the processor, the update of the configuration of the plurality of managed computing environments to the plurality of child ledgers of the plurality of managed computing environments, respectively.

2. The method of claim 1 , wherein the creating of the respective child ledger comprises associating the respective child ledger with its respective managed computing environment.

3. The method of claim 1 , wherein the creating of the respective child ledger comprises linking the respective child ledger with the master ledger.

4. The method of claim 1 , wherein the smart contract condition is met when a child ledger complies with code defined under the smart contract condition.

5. The method of claim 1 , further comprising:
submitting the update for the master ledger to a develop operations tooling module.

6. The method of claim 1 , further comprising:
scheduling updates, and requesting approval of the scheduled updates for one or more of the master ledger and a respective child ledger.

7. The method of claim 1 , wherein the updating of the master ledger deploys corresponding changes to the plurality of child ledgers.

8. A system, comprising:
a processor configured to
receive a plurality of child ledgers corresponding to a plurality of managed computing environments, respectively, each child ledger comprising a respective sequence of hash-linked blocks storing configuration content of a different respective managed computing environment,
update a configuration of the plurality of managed computing environments via a master ledger when a smart contract condition is met, and
when the master ledger is updated, deploy the update of the configuration of the plurality of managed computing environments to the plurality of child ledgers of the plurality of managed computing environments, respectively.

9. The system of claim 8 , further comprising:
a user device configured to associate a child ledger with a managed computing environment.

10. The system of claim 8 , further comprising:
a user device configured to link a child ledger with the master ledger.

11. The system of claim 8 , wherein the smart contract condition is met when a child ledger complies with code defined under the smart contract condition.

12. The system of claim 8 , wherein the processor is further configured to submit the update for the master ledger to a develop operations tooling module.

13. The system of claim 8 , wherein the processor is further configured to schedule updates, and request approval of the scheduled updates for one or more of the master ledger and the child ledger.

14. The system of claim 8 , wherein the processor is further configured to deploy corresponding changes to the plurality of child ledgers.

15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:
creating a plurality of child ledgers for a plurality of managed computing environments, each child ledger comprising a respective sequence of hash-linked blocks storing configuration content of a different respective managed computing environment;
updating a configuration of the plurality of managed computing environments via a master ledger when a smart contract condition is met; and
when the master ledger is updated, deploying the update of the configuration of the plurality of managed computing environments to the plurality of child ledgers of the plurality of managed computing environments, respectively.

16. The non-transitory computer readable medium of claim 15 , wherein the creating of the respective child ledger comprises associating the respective child ledger with its respective managed computing environment.

17. The non-transitory computer readable medium of claim 15 , wherein the creating of the respective child ledger comprises linking the respective child ledger with the master ledger.

18. The non-transitory computer readable medium of claim 15 , further comprising:
submitting the update for the master ledger to a develop operations tooling module.

19. The non-transitory computer readable medium of claim 15 , further comprising:
scheduling updates, and requesting approval of the updates for one or more of the master ledger and the child ledger.

20. The non-transitory computer readable medium of claim 15 , wherein the updating of the master ledger deploys corresponding changes to the plurality of child ledgers.

Assignees

• IBM

Inventors

• Chui Hin Ting
• Stein Jarett
• Herrin Bradley C
• Zhu Xianjun

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/0891

  Revocation or update of secret information, e.g. encryption key update or rekeying · CPC title

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F21/64

  Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title