Ticket-Based Cloud Provisioning With IaC Service Catalog Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise cloud computing (ECC) companies struggle to build cloud infrastructure in a repeatable and versioned way, lacking a system that allows app developers to request services without knowing infrastructure details and automates provisioning using infrastructure as code.
Innovation Solution
A ticket-based provisioning system that integrates with a service catalog, using infrastructure-as-code (IaC) modules to automate cloud infrastructure provisioning based on tickets, bridging the gap between manual actions and dynamic cloud deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual ticket-driven provisioning is used, then developers can request services without infrastructure knowledge, but the provisioning process is slow and not repeatable
Solution Approach 1:
The patent introduces a ticketing system as an intermediary layer between developers and infrastructure provisioning. The ticketing system receives service requests from developers, translates them into automated provisioning tasks, and coordinates with infrastructure teams. This mediator enables developers to request services without needing infrastructure knowledge while triggering automated workflows that speed up the actual provisioning process.
Solution Approach 2:
The patent implements self-service capabilities through automated provisioning workflows that can execute without continuous human intervention. Once a ticket is created with the necessary service parameters, the system automatically provisions the required infrastructure resources, reducing manual effort and accelerating delivery while maintaining policy compliance through embedded governance rules.
2Productivity
If developers directly provision infrastructure, then provisioning speed increases, but infrastructure knowledge and policy compliance become problematic
Solution Approach 1:
The ticketing system serves as an intermediary that shields developers from infrastructure complexity. Developers submit standardized service requests through the ticketing system without needing to understand underlying infrastructure details. The system translates these high-level requests into technical provisioning tasks, managing the complexity internally while maintaining simple interfaces for developers.
Solution Approach 2:
The patent creates universal service templates and standardized request formats that work across different infrastructure types and scenarios. These templates encapsulate complex infrastructure knowledge and policy requirements, allowing developers to provision various services using the same simplified interface regardless of the underlying infrastructure complexity.
3Reliability
If automated infrastructure as code is used, then provisioning becomes repeatable and versioned, but integration with existing ticketing systems is challenging
Solution Approach 1:
The patent merges the ticketing system with infrastructure as code workflows by creating integrated automation pipelines. The ticketing system is combined with version-controlled infrastructure templates, policy engines, and automated provisioning tools into a unified system. This integration allows service requests to flow seamlessly from ticket creation through automated infrastructure deployment while maintaining repeatability and version control.
Solution Approach 2:
The patent implements preliminary configuration of infrastructure templates, policies, and provisioning workflows before actual service requests are processed. Service blueprints, resource templates, and compliance rules are pre-defined and versioned in advance. When tickets are created, these pre-configured templates are automatically applied, ensuring consistent and repeatable provisioning without requiring complex real-time decision-making.
4Stability of the object's composition
If manual provisioning processes are maintained, then existing workflows are preserved, but the system cannot adapt to dynamic cloud-based infrastructure
Solution Approach 1:
The patent introduces dynamic capabilities into the provisioning system by implementing automated workflows that can adapt to different service requirements and infrastructure states. The system uses configurable templates, conditional logic, and real-time resource allocation that allow it to dynamically respond to varying cloud infrastructure scenarios while maintaining stable core processes through version-controlled templates and standardized workflows.
Data Source
AI summary
Systems and methods for ticket-based provisioning of cloud infrastructure from one or more cloud providers to build one or more computing workspaces of an enterprise. A provisioning platform provides a module catalog having one or more infrastructure-as-code (IAC) modules, each including code that is executable to provision cloud computing resources for the cloud infrastructure from the cloud providers to build the computing workspaces of the enterprise. A service catalog has one or more electronic entries mapped to and corresponding with the IAC modules of the module catalog. The service catalog receives one or more tickets that each specify at least one of the electronic entries in the service catalog, to bind each specified electronic entry with a corresponding LAC module, causing the provisioning platform to instantiate on the more cloud providers the computing resources for the cloud infrastructure corresponding to the ticket.