US 12,254,356 B2
Techniques for managing drift in a deployment orchestrator
Eric Tyler Barsalou, Seattle, WA (US); and Nathaniel Martin Glass, Bellevue, WA (US)
Assigned to ORACLE INTERNATIONAL CORPORATION, Redwood Shores, CA (US)
Filed by Oracle International Corporation, Redwood Shores, CA (US)
Filed on Sep. 27, 2023, as Appl. No. 18/373,743.
Application 18/373,743 is a continuation of application No. 17/027,507, filed on Sep. 21, 2020, granted, now 11,816,507.
Claims priority of provisional application 62/963,491, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,413, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,477, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,486, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,478, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,456, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,489, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,335, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,452, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,480, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,481, filed on Jan. 20, 2020.
Prior Publication US 2024/0020175 A1, Jan. 18, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 9/50 (2006.01); G06F 3/0484 (2022.01); G06F 8/60 (2018.01); G06F 8/71 (2018.01); G06F 9/38 (2018.01); G06F 9/4401 (2018.01); G06F 9/445 (2018.01); G06F 9/451 (2018.01); G06F 9/48 (2006.01); G06F 11/07 (2006.01); G06F 11/14 (2006.01); G06F 11/32 (2006.01); G06F 11/36 (2006.01); G06F 11/3668 (2025.01); G06F 16/901 (2019.01); H04L 41/0806 (2022.01); H04L 41/0816 (2022.01); H04L 41/50 (2022.01); H04L 41/5041 (2022.01); H04L 41/5054 (2022.01); H04L 67/00 (2022.01); H04L 67/10 (2022.01); H04L 67/1008 (2022.01); H04L 67/1031 (2022.01); H04L 67/566 (2022.01); G06F 8/61 (2018.01)
CPC G06F 9/5061 (2013.01) [G06F 3/0484 (2013.01); G06F 8/60 (2013.01); G06F 8/71 (2013.01); G06F 9/3836 (2013.01); G06F 9/4411 (2013.01); G06F 9/44505 (2013.01); G06F 9/451 (2018.02); G06F 9/485 (2013.01); G06F 9/4856 (2013.01); G06F 9/5011 (2013.01); G06F 9/5022 (2013.01); G06F 9/5027 (2013.01); G06F 9/5038 (2013.01); G06F 9/505 (2013.01); G06F 9/5072 (2013.01); G06F 9/5077 (2013.01); G06F 11/0757 (2013.01); G06F 11/1469 (2013.01); G06F 11/327 (2013.01); G06F 11/3664 (2013.01); G06F 11/3684 (2013.01); G06F 16/9024 (2019.01); H04L 41/0806 (2013.01); H04L 41/0816 (2013.01); H04L 41/5041 (2013.01); H04L 41/5048 (2013.01); H04L 41/5054 (2013.01); H04L 41/5096 (2013.01); H04L 67/10 (2013.01); H04L 67/1008 (2013.01); H04L 67/1031 (2013.01); H04L 67/34 (2013.01); H04L 67/566 (2022.05); G06F 8/61 (2013.01); G06F 11/0709 (2013.01); G06F 11/0751 (2013.01); G06F 11/0793 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
receiving, by at least one of a plurality of computer processors, a first configuration file for a deployment of a first set of cloud infrastructure resources to a first execution target in a first region of a cloud infrastructure orchestration service, the first execution target representing a first service of a plurality of services provided by the cloud infrastructure orchestration service;
receiving, by at least one of the plurality of computer processors, a second configuration file for a deployment of a second set of cloud infrastructure resources to a second execution target in a second region of the cloud infrastructure orchestration service, the second execution target representing a second service of the plurality of services provided by the cloud infrastructure orchestration service;
generating, by at least one of the plurality of computer processors, a first safety plan for deployment at the first execution target based at least in part on the first configuration file;
generating, by at least one of the plurality of computer processors, a second safety plan for deployment at the second execution target based at least in part on the second configuration file;
determining, by at least one of the plurality of computer processors, whether the second safety plan is a subset of the first safety plan;
in accordance with a determination that the second safety plan is the subset of the first safety plan:
automatically approving, by at least one of the plurality of computer processors, the second safety plan based at least in part on an approval of the first safety plan;
transmitting, by at least one of the plurality of computer processors, the automatically approved second safety plan to the second execution target; and
transmitting, by at least one of the plurality of computer processors, a set of deployment instructions for deploying the second set of cloud infrastructure resources at the second execution target; and
in accordance with a determination that the second safety plan is not the subset of the first safety plan:
providing, in a user interface, the second set of cloud infrastructure resources for deployment at the second execution target;
providing, in the user interface, a notification that particular resources from the second set of cloud infrastructure resources that are scheduled to be deployed at the second execution target are not listed in the first safety plan; and
halting the deployment of the second set of cloud infrastructure resources at the second execution target.