IP Library › Granted Patent US 12712800

Granted Patent B2

US 12712800 · App. 18/419,903 · Granted Aug 18, 2026

System and method to dynamically maintain a distributed testing environment

Inventors: Maneesh Kumar Sethia (Hyderabad, IN); Abhijit Behera (Hyderabad, IN); Manimaran Sundaravel (Chennai, IN); Sivashalini Sivajothi (Chennai, IN); Shailendra Singh (Thane West, IN)

Assignee: Bank of America Corporation

H04L43/50 H04L43/06

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 12712800
App. No.: 18/419,903
Granted: Aug 18, 2026
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

An apparatus comprises a memory communicatively coupled to a processor. The memory is configured to store multiple deployment operations configured to control access to one or more portions of application data. The processor is configured to determine a deployment operation associated with a portion of the application data, perform multiple collected testing operations for the portion of the application data based at least in part upon the deployment operation, and determine pod data indicating multiple role parameters based at least in part upon the deployment operation. The role parameters are configured to indicate multiple testing operations on the portion of the application data. Further, the processor is configured to identify a pod that at least partially matches the pod data and trigger one or more distributed testing operations at the pod.

Claims (180)

1 . An apparatus, comprising:

a memory configured to store:

a plurality of deployment operations configured to control access to one or more portions of application data; and

a processor communicatively coupled to the memory and configured to:

receive a request to release testing operations to one or more managed servers;

identify a source of the request;

obtain one or more server profiles from a role directory;

determine whether the source at least partially matches at least one server profile of the one or more server profiles;

in response to determining that the source does not at least partially match the at least one server profile, generate a report indicating that the request cannot be authenticated; and

in response to determining that the source at least partially matches the at least one server profile:

determine a first deployment operation associated with a first portion of the application data;

perform a first plurality of collected testing operations for the first portion of the application data based at least in part upon the first deployment operation;

determine first pod data indicating a first plurality of role parameters based at least in part upon the first deployment operation, the first plurality of role parameters being configured to indicate a first plurality of testing operations on the first portion of the application data;

associate a first pod out of a plurality of distributed pods in a network that at least partially matches the first pod data with the first portion of the application data, wherein the first pod comprises a first name-space;

determine a first configuration mapping associated with the first deployment operation for the first portion of the application data, wherein:

the first configuration mapping indicates access to a specific directory of the first pod and is configured to control access to the first portion of the application data;

the first deployment operation comprises a first control signal that triggers execution of a first test script associated with the first plurality of distributed testing operations;

create a first secret parameter based at least in part upon the first configuration mapping;

generate a first verification block based at least in part upon the first secret parameter and the first configuration mapping, the first verification block comprising verification information to enable the first pod to access the first portion of the application data;

provide the first verification block to the first pod;

perform a first role binding operation to bind the first pod to one or more application roles corresponding to the first portion of the application data, the first role binding operation enables runtime reconfiguration of an executing service to trigger alternating between the first plurality of distributed testing operations and the first plurality of collected testing operations;

trigger a first plurality of distributed testing operations at the first pod by providing the first verification block to the first pod;

determine a second deployment operation associated with a second portion of the application data;

perform a second plurality of collected testing operations for the second portion of the application data based at least in part upon the second deployment operation;

determine second pod data indicating a second plurality of role parameters based at least in part upon the second deployment operation, the second plurality of role parameters being configured to indicate a second plurality of testing operations on the second portion of the application data;

associate a second pod out of the plurality of distributed pods in the network that at least partially matches the second pod data with the second portion of the application data;

determine a second configuration mapping associated with the second deployment operation for the second portion of the application data, wherein:

the second configuration mapping indicates access to a specific directory of the second pod and is configured to control access to the second portion of the application data;

the second deployment operation comprises a second control signal that triggers execution of a second test script associated with the second plurality of distributed testing operations;

create a second secret parameter based at least in part upon the second configuration mapping;

generate a second verification block based at least in part upon the second secret parameter and the second configuration mapping, the second verification block comprising verification information to enable the second pod to access the second portion of the application data;

provide the second verification block to the second pod;

perform a second role binding operation to bind the second pod to one or more application roles corresponding to the second portion of the application data, the second role binding operation enables runtime reconfiguration of an executing service to trigger alternating between the second plurality of distributed testing operations and the second plurality of collected testing operations, wherein:

the second pod comprises a second name-space; and

the second name-space is different from the first name-space; and

trigger a second plurality of distributed testing operations at the second pod by providing the second verification block to the second pod, wherein:

the first pod is associated with a first container and a first plurality of resources;

the second pod is associated with a second container and a second plurality of resources;

the first plurality of distributed testing operations is different from the second plurality of distributed testing operations;

the first pod comprises a first container, first shared storage, and first network resources, the first shared storage and the first network resources being co-located and co-scheduled; and

the second pod comprises a second container, second shared storage, and second network resources, the second shared storage and the second network resources being co-located and co-scheduled.

2 . The apparatus of claim 1 , wherein the processor is further configured to:

determine a third deployment operation associated with a third portion of the application data;

determine third pod data indicating a third plurality of role parameters based at least in part upon the third deployment operation, the third plurality of role parameters being configured to indicate a third plurality of testing operations on the third portion of the application data;

identify a third pod that at least partially matches the third pod data; and

trigger a third plurality of distributed testing operations at the third pod.

3 . The apparatus of claim 1 , wherein the processor is further configured to:

determine a third deployment operation associated with a third portion of the application data;

identify a third pod that at least partially matches the third pod data; and

trigger a third plurality of distributed testing operations at the third pod.

4 . The apparatus of claim 3 , wherein:

the first pod is configured to enable access between the first portion of the application data and a first plurality of users;

the second pod is configured to enable access between the second portion of the application data and a second plurality of users; and

the third pod is configured to enable access between the third portion of the application data and a third plurality of users.

5 . The apparatus of claim 4 , wherein the processor is further configured to:

receive a first report indicating a first plurality of responses from the first plurality of users associated with the first pod;

receive a second report indicating a second plurality of responses from the second plurality of users associated with the second pod; and

receive a third report indicating a third plurality of responses from the third plurality of users associated with the third pod.

6 . The apparatus of claim 1 , wherein the processor is further configured to perform one or more instructing node operations in a communication network.

7 . The apparatus of claim 1 , wherein the first pod is in a managed server configured to perform one or more worker node operations in a communication network.

8 . A method, comprising:

receiving a request to release testing operations to one or more managed servers;

identifying a source of the request;

obtaining one or more server profiles from a role directory;

determining whether the source at least partially matches at least one server profile of the one or more server profiles;

in response to determining that the source does not at least partially match the at least one server profile, generating a report indicating that the request cannot be authenticated; and

in response to determining that the source at least partially matches the at least one server profile:

determining a first deployment operation associated with a first portion of one or more portions of application data;

performing a first plurality of collected testing operations for the first portion of the application data based at least in part upon the first deployment operation;

determining first pod data indicating a first plurality of role parameters based at least in part upon the first deployment operation, the first plurality of role parameters being configured to indicate a first plurality of testing operations on the first portion of the application data;

associating a first pod out of a plurality of distributed pods in a network that at least partially matches the first pod data with the first portion of the application data, wherein the first pod comprises a first name-space;

determining a first configuration mapping associated with the first deployment operation for the first portion of the application data, wherein:

the first configuration mapping indicates access to a specific directory of the first pod and is configured to control access to the first portion of the application data;

the first deployment operation comprises a first control signal that triggers execution of a first test script associated with the first plurality of distributed testing operations;

creating a first secret parameter based at least in part upon the first configuration mapping;

generating a first verification block based at least in part upon the first secret parameter and the first configuration mapping, the first verification block comprising verification information to enable the first pod to access the first portion of the application data;

providing the first verification block to the first pod;

performing a first role binding operation to bind the first pod to one or more application roles corresponding to the first portion of the application data, the first role binding operation enables runtime reconfiguration of an executing service to trigger alternating between the first plurality of distributed testing operations and the first plurality of collected testing operations;

triggering a first plurality of distributed testing operations at the first pod by providing the first verification block to the first pod;

determining a second deployment operation associated with a second portion of the application data;

performing a second plurality of collected testing operations for the second portion of the application data based at least in part upon the second deployment operation;

determining second pod data indicating a second plurality of role parameters based at least in part upon the second deployment operation, the second plurality of role parameters being configured to indicate a second plurality of testing operations on the second portion of the application data;

associating a second pod out of the plurality of distributed pods in the network that at least partially matches the second pod data with the second portion of the application data;

determining a second configuration mapping associated with the second deployment operation for the second portion of the application data, wherein:

the second configuration mapping indicates access to a specific directory of the second pod and is configured to control access to the second portion of the application data;

the second deployment operation comprises a second control signal that triggers execution of a second test script associated with the second plurality of distributed testing operations;

creating a second secret parameter based at least in part upon the second configuration mapping;

generating a second verification block based at least in part upon the second secret parameter and the second configuration mapping, the second verification block comprising verification information to enable the second pod to access the second portion of the application data;

providing the second verification block to the second pod;

performing a second role binding operation to bind the second pod to one or more application roles corresponding to the second portion of the application data, the second role binding operation enables runtime reconfiguration of an executing service to trigger alternating between the second plurality of distributed testing operations and the second plurality of collected testing operations, wherein:

the second pod comprises a second name-space; and

the second name-space is different from the first name-space; and

triggering a second plurality of distributed testing operations at the second pod by providing the second verification block to the second pod, and

wherein:

the first pod is associated with a first container and a first plurality of resources;

the second pod is associated with a second container and a second plurality of resources;

the first plurality of distributed testing operations is different from the second plurality of distributed testing operations;

the first pod comprises a first container, first shared storage, and first network resources, the first shared storage and the first network resources being co-located and co-scheduled; and

the second pod comprises a second container, second shared storage, and second network resources, the second shared storage and the second network resources being co-located and co-scheduled.

9 . The method of claim 8 , further comprising:

determining a third deployment operation associated with a second portion of the application data;

determining second pod data indicating a second plurality of role parameters based at least in part upon the third deployment operation, the second plurality of role parameters being configured to indicate a second plurality of testing operations on the second portion of the application data;

identifying a second pod that at least partially matches the second pod data; and

triggering a second plurality of distributed testing operations at the second pod.

10 . The method of claim 8 , further comprising:

determining a third deployment operation associated with a third portion of the application data;

determining third pod data indicating a third plurality of role parameters based at least in part upon the third deployment operation, the third plurality of role parameters being configured to indicate a third plurality of testing operations on the third portion of the application data;

identifying a third pod that at least partially matches the third pod data; and

triggering a third plurality of distributed testing operations at the third pod.

11 . The method of claim 10 , wherein:

the first pod is configured to enable access between the first portion of the application data and a first plurality of users;

the second pod is configured to enable access between the second portion of the application data and a second plurality of users; and

the third pod is configured to enable access between the third portion of the application data and a third plurality of users.

12 . The method of claim 11 , further comprising:

receiving a first report indicating a first plurality of responses from the first plurality of users associated with the first pod;

receiving a second report indicating a second plurality of responses from the second plurality of users associated with the second pod; and

receiving a third report indicating a third plurality of responses from the third plurality of users associated with the third pod.

13 . The method of claim 8 , further comprising:

performing one or more instructing node operations in a communication network.

14 . The method of claim 8 , wherein the first pod is in a managed server configured to perform one or more worker node operations in a communication network.

15 . A non-transitory computer readable medium storing instructions that when executed by a processor cause the processor to:

receive a request to release testing operations to one or more managed servers;

identify a source of the request;

obtain one or more server profiles from a role directory;

determine whether the source at least partially matches at least one server profile of the one or more server profiles;

in response to determining that the source does not at least partially match the at least one server profile, generate a report indicating that the request cannot be authenticated; and

in response to determining that the source at least partially matches the at least one server profile:

determine a first deployment operation associated with a first portion of one or more portions of application data;