US11182139B2ActiveUtilityA1

System and method for production readiness verification and monitoring

66
Assignee: WALMART APOLLO LLCPriority: Jan 11, 2019Filed: Jan 11, 2019Granted: Nov 23, 2021
Est. expiryJan 11, 2039(~12.5 yrs left)· nominal 20-yr term from priority
H04L 67/75G06F 8/61H04L 43/0817H04L 43/10H04L 41/5083H04L 41/5096H04L 67/34H04L 67/10H04L 41/5012H04L 67/1012H04L 67/36
66
PatentIndex Score
2
Cited by
30
References
17
Claims

Abstract

Systems and methods for production readiness verification and monitoring are disclosed. A set of compliance requirements including one or more required-asset identifiers and a set of minimum deployment requirements for each required-asset identifier is received. Each of the one or more required-asset identifiers are associated with a cloud asset required for deployment of a target application. One or more probing messages are generated to determine an availability of each cloud asset associated with the one or more required-asset identifiers, at least one probing response is received from at least one cloud, and the cloud environment is identified as one of compliant or non-compliant for application deployment. The cloud environment is identified as compliant when each cloud asset meets each of minimum deployment requirements and non-compliant when a cloud asset fails to meet one of the minimum deployment requirements. The target application is deployed when the cloud environment is compliant.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A system, comprising:
 a non-transitory memory having instructions stored thereon, and a processor configured to read the instructions to: 
 receive a set of compliance requirements including one or more required-asset identifiers and a set of minimum deployment requirements for each required-asset identifier, wherein each of the one or more required-asset identifiers are associated with a cloud asset required for deployment of a target application, wherein the set of compliance requirements include a first set of compliance requirements for a private cloud and a second set of compliance requirements for a public cloud, and wherein the first set of compliance requirements and the second set of compliance requirements are different; 
 generate one or more first level probing messages to determine an availability of a respective cloud asset associated with the one or more required-asset identifiers within a cloud environment; 
 receive at least one first level probing response from at least one cloud within the cloud environment; 
 in response to the at least one first level probing response indicating that the respective cloud asset is available, wherein the respective cloud asset is a first cloud asset when the at least one cloud is the public cloud and a second cloud asset when the at least one cloud is the private cloud:
 generate one or more second level probing messages to determine whether traffic to the at least one cloud is arriving at an application of the respective cloud asset within the at least one cloud; 
 receive at least one second level probing response from the at least one cloud within the cloud environment in response to the one or more second level probing messages, the at least one second level probing response indicates that the traffic to the at least one cloud is arriving at the application of the respective cloud asset within the at least one cloud; 
 
 in response to receiving the at least one second level probing response from the at least one cloud, identify the cloud environment as one of compliant or non-compliant for application deployment, wherein the cloud environment is identified as compliant when each cloud asset meets the set of minimum deployment requirements and non-compliant when at least one cloud asset fails to meet at least one of the set of minimum deployment requirements; 
 deploy the target application to the cloud environment when the cloud environment is identified as compliant; and 
 implement a correction process to deploy at least one instance of at least one cloud asset to correct the cloud environment when the cloud environment is identified as non-compliant. 
 
     
     
       2. The system of  claim 1 , wherein generating the one or more first level probing messages comprises generating a probing message configured to identify availability of a first cloud asset associated with a first one of the one or more required-asset identifiers on any cloud within the cloud environment. 
     
     
       3. The system of  claim 1 , wherein generating the one or more first level probing messages comprises generating a plurality of probing messages configured to identify a load-balancing status of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       4. The system of  claim 1 , wherein generating the one or more second level probing messages comprises generating a plurality of probing messages configured to identify a status of one or more specific instances of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       5. The system of  claim 1 , wherein the set of minimum deployment requirements include a high-availability requirement, a disaster recovery requirement, or a combination thereof. 
     
     
       6. The system of  claim 1 , wherein the set of minimum deployment requirements includes at least one load-balancing requirement. 
     
     
       7. A non-transitory computer readable medium having instructions stored thereon, wherein the instructions, when executed by a processor cause a device to perform operations comprising:
 receiving a set of compliance requirements including one or more required-asset identifiers and a set of minimum deployment requirements for each required-asset identifier, wherein each of the one or more required-asset identifiers are associated with a cloud asset required for deployment of a target application, wherein the set of compliance requirements include a first set of compliance requirements for a private cloud and a second set of compliance requirements for a public cloud, and wherein the first set of compliance requirements and the second set of compliance requirements are different; 
 generating one or more first level probing messages to determine an availability of a respective cloud asset associated with the one or more required-asset identifiers within a cloud environment, wherein the respective cloud asset is a first cloud asset when the at least one cloud is a public cloud and the second cloud asset when the at least one cloud is the private cloud; 
 receiving at least one first level probing response from at least one cloud within the cloud environment; 
 in response to the at least one first level probing response indicating that the respective cloud asset is available:
 generating one or more second level probing messages to determine whether traffic to the at least one cloud is arriving at an application of the respective cloud asset within the at least one cloud; 
 receiving at least one second level probing response from the at least one cloud within the cloud environment in response to the one or more second level probing messages, the at least one second level probing response indicates that the traffic to the at least one cloud is arriving at the application of the respective cloud asset within the at least one cloud; 
 
 in response to receiving the at least one second level probing response from the at least one cloud, identifying the cloud environment as one of compliant or non-compliant for application deployment, wherein the cloud environment is identified as compliant when each cloud asset meets the set of minimum deployment requirements and non-compliant when at least one cloud asset fails to meet at least one of the set of minimum deployment requirements; 
 deploying the target application to the cloud environment when the cloud environment is identified as compliant; and 
 implementing a correction process to deploy at least one instance of at least one cloud asset to correct the cloud environment when the cloud environment is identified as non-compliant. 
 
     
     
       8. The non-transitory computer readable medium of  claim 7 , wherein generating the one or more first level probing messages comprises generating a probing message configured to identify availability of a first cloud asset associated with a first one of the one or more required-asset identifiers on any cloud within the cloud environment. 
     
     
       9. The non-transitory computer readable medium of  claim 7 , wherein generating the one or more first level probing messages comprises generating a plurality of probing messages configured to identify a load-balancing status of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       10. The non-transitory computer readable medium of  claim 7 , wherein generating the one or more second probing messages comprises generating a plurality of probing messages configured to identify a status of a one or more specific instances of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       11. The non-transitory computer readable medium of  claim 7 , wherein the set of minimum deployment requirements include a high-availability requirement, a disaster recovery requirement, or a combination thereof. 
     
     
       12. The non-transitory computer readable medium of  claim 7 , wherein the set of minimum deployment requirements includes at least one load-balancing requirement. 
     
     
       13. A method, comprising:
 receiving a set of compliance requirements including one or more required-asset identifiers and a set of minimum deployment requirements for each required-asset identifier, wherein each of the one or more required-asset identifiers are associated with a cloud asset required for deployment of a target application, wherein the set of compliance requirements include a first set of compliance requirements for a private cloud and a second set of compliance requirements for a public cloud, and wherein the first set of compliance requirements and the second set of compliance requirements are different; 
 generating one or more first level probing messages to determine an availability of a respective cloud asset associated with the one or more required-asset identifiers within a cloud environment, wherein the respective cloud asset is a first cloud asset when the at least one cloud is the public cloud and a second cloud asset when the at least one cloud is the private cloud; 
 receiving at least one first level probing response from at least one cloud within the cloud environment; 
 in response to the at least one first level probing response indicating that the respective cloud asset is available:
 generating one or more second level probing messages to determine whether traffic to the at least one cloud is arriving at an application of the respective cloud asset within the at least one cloud; 
 receiving at least one second level probing response from the at least one cloud within the cloud environment in response to the one or more second level probing messages, the at least one second level probing response indicates that the traffic to the at least one cloud is arriving at the application of the respective cloud asset within the at least one cloud; 
 
 in response to receiving the at least one second level probing response from the at least one cloud, identifying the cloud environment as one of compliant or non-compliant for application deployment, wherein the cloud environment is identified as compliant when each cloud asset meets the set of minimum deployment requirements and non-compliant when at least one cloud asset fails to meet at least one of the set of minimum deployment requirements; 
 deploying the target application to the cloud environment when the cloud environment is identified as compliant; and 
 implementing a correction process to deploy at least one instance of at least one cloud asset to correct the cloud environment when the cloud environment is identified as non-compliant. 
 
     
     
       14. The method of  claim 13 , wherein generating the one or more first level probing messages comprises generating a probing message configured to identify availability of a first cloud asset associated with a first one of the one or more required-asset identifiers on any cloud within the cloud environment. 
     
     
       15. The method of  claim 13 , wherein generating the one or more first level probing messages comprises generating a plurality of probing messages configured to identify a load-balancing status of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       16. The method of  claim 13 , wherein generating the one or more second level probing messages comprises generating a plurality of probing messages configured to identify a status of a one or more specific instances of a first cloud asset within a selected cloud in the cloud environment. 
     
     
       17. The method of  claim 13 , wherein the set of minimum deployment requirements include a high-availability requirement, a disaster recovery requirement, or a combination thereof.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.