Platform-independent interface for generating virtualized multi-service hardware systems and infrastructure
View Patent ↗Systems and methods for implementing a platform-independent interface for generating virtualized multi-service hardware systems are provided. For example, the system may generate “Infrastructure as Code” (IaC) and/or “Infrastructure as a Service” (IaaS) using various services and tools (e.g., provided by third parties) and programmatic calls to those services and tools. The system may also generate “Functions as a Service” (FaaS) to provide systems and services that are available perpetually. The system may automatically isolate and resolve bugs or other computational issues without the need for human intervention.
1. A method for implementing an instance of computer infrastructure, the method comprising:
receiving a configuration parameters for a template defining the computer infrastructure, wherein the template corresponds with infrastructure as code (IaC) implemented on a plurality of infrastructure as a service (IaaS) or cloud provider equipment and services;
building the template defining the computer infrastructure using the configuration parameters, wherein the template translates the configuration parameters to a plurality of expected formats of the plurality of IaaS or cloud provider equipment and services;
when a deployment request is received, launching the computer infrastructure, including tools, services, and management capabilities, in accordance with the template, the configuration parameters, and constrained by governance standards to create a new instance of the computer infrastructure, wherein the computer infrastructure relies on the plurality of IaaS or cloud provider equipment and services to create the new instance of computer infrastructure;
embedding ChatOps functionality, wherein the ChatOps functionality comprises Internet Control Message Protocol (ICMP), Functions as a Service (FaaS), Chat Operations alerting, logging, and stateful management of compute for continuous monitoring; and
providing stateful hardened, monitored, managed, and self-healing Service and Infrastructure Provisioning at runtime;
wherein the configuration parameters define logical configuration parameters for deployment including regionality availability zones, identity access management, Classless Inter-Domain Routing (CIDR) management, boundary and security configurations including firewalls, internet gateways, virtual private networks, demilitarized zones (DMZs), and other logical constraints of a secured infrastructure deployment; and
wherein launching the computer infrastructure comprises identifying and codifying a build file of artifacts implementing one or more operating systems and defining parameters of a virtualized operating system or container in accordance with the configuration parameters and pre-defined constraints of a given organization.
2. The method of claim 1 , wherein the configuration parameters corresponds with an operating system of a virtualized device included with the computer infrastructure.
3. The method of claim 1 , wherein the configuration parameters corresponds with an infrastructure as a service or cloud provider providing at least a portion of the computer infrastructure.
4. The method of claim 1 , wherein the deployment request is based on automated testing and monitoring.
5. The method of claim 1 , wherein the deployment request is initiated based on a hardened, deployed infrastructure component being identified as unhealthy.
6. The method of claim 1 , wherein the deployment is initiated by a load balancer to distribute network traffic across multiple servers.
7. A system for implementing an instance of computer infrastructure, the system comprising:
a memory; and
one or more processors configured to execute computer-readable instructions stored in the memory to perform the method comprising:
receiving a configuration parameters for a template defining the computer infrastructure, wherein the template corresponds with infrastructure as code (IaC) implemented on a plurality of infrastructure as a service (IaaS) or cloud provider equipment and services;
build the template defining the computer infrastructure using the configuration parameters, wherein the template translates the configuration parameters to a plurality of expected formats of the plurality of IaaS or cloud provider equipment and services;
when a deployment request is received, launch the computer infrastructure, including tools, services, and management capabilities, in accordance with the template, the configuration parameters, and constrained by governance standards to create a new instance of the computer infrastructure, wherein the computer infrastructure relies on the plurality of IaaS or cloud provider equipment and services to create the new instance of computer infrastructure;
embed ChatOps functionality, wherein the ChatOps functionality comprises Internet Control Message Protocol (ICMP), Functions as a Service (FaaS), Chat Operations alerting, logging, and stateful management of compute for continuous monitoring; and
provide stateful hardened, monitored, managed, and self-healing Service and Infrastructure Provisioning at runtime;
wherein the configuration parameters define logical configuration parameters for deployment including regionality availability zones, identity access management, Classless Inter-Domain Routing (CIDR) management, boundary and security configurations including firewalls, internet gateways, virtual private networks, demilitarized zones (DMZs), and other logical constraints of a secured infrastructure deployment; and
wherein launching the computer infrastructure comprises identifying and codifying a build file of artifacts implementing one or more operating systems and defining parameters of a virtualized operating system or container in accordance with the configuration parameters and pre-defined constraints of a given organization.
8. The system of claim 7 , wherein the configuration parameters corresponds with an operating system of a virtualized device included with the computer infrastructure.
9. The system of claim 7 , wherein the configuration parameters corresponds with an infrastructure as a service or cloud provider providing at least a portion of the computer infrastructure.
10. The system of claim 7 , wherein the deployment request is based on automated testing and monitoring.
11. The system of claim 7 , wherein the deployment request is initiated based on a hardened, deployed infrastructure component being identified as unhealthy.
12. The system of claim 7 , wherein the deployment is initiated by a load balancer to distribute network traffic across multiple servers.
13. A non-transitory computer-readable storage medium storing a plurality of instructions executable by one or more processors, the plurality of instructions when executed by the one or more processors cause the one or more processors to:
receiving a configuration parameters for a template defining the computer infrastructure, wherein the template corresponds with infrastructure as code (IaC) implemented on a plurality of infrastructure as a service (IaaS) or cloud provider equipment and services;
building the template defining the computer infrastructure using the configuration parameters, wherein the template translates the configuration parameters to a plurality of expected formats of the plurality of IaaS or cloud provider equipment and services;
when a deployment request is received, launching the computer infrastructure, including tools, services, and management capabilities, in accordance with the template, the configuration parameters, and constrained by governance standards to create a new instance of the computer infrastructure, wherein the computer infrastructure relies on the plurality of IaaS or cloud provider equipment and services to create the new instance of computer infrastructure;
embedding ChatOps functionality, wherein the ChatOps functionality comprises Internet Control Message Protocol (ICMP), Functions as a Service (FaaS), Chat Operations alerting, logging, and stateful management of compute for continuous monitoring; and
providing stateful hardened, monitored, managed, and self-healing Service and Infrastructure Provisioning at runtime;
wherein the configuration parameters define logical configuration parameters for deployment including regionality availability zones, identity access management, Classless Inter-Domain Routing (CIDR) management, boundary and security configurations including firewalls, internet gateways, virtual private networks, demilitarized zones (DMZs), and other logical constraints of a secured infrastructure deployment; and
wherein launching the computer infrastructure comprises identifying and codifying a build file of artifacts implementing one or more operating systems and defining parameters of a virtualized operating system or container in accordance with the configuration parameters and pre-defined constraints of a given organization.
14. The non-transitory computer-readable storage medium of claim 13 , wherein the configuration parameters corresponds with an operating system of a virtualized device included with the computer infrastructure.
15. The non-transitory computer-readable storage medium of claim 13 , wherein the configuration parameters corresponds with an infrastructure as a service or cloud provider providing at least a portion of the computer infrastructure.
16. The non-transitory computer-readable storage medium of claim 13 , wherein the deployment request is based on automated testing and monitoring.
17. The non-transitory computer-readable storage medium of claim 13 , wherein the deployment request is initiated based on a hardened, deployed infrastructure component being identified as unhealthy.