Automated Computing Infrastructure Deployment Without Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data centre deployment methods involve manual configuration, leading to errors, inconsistencies, and extended downtime, and existing solutions like Cisco APIC, OpenStack Ironic, and Microsoft Azure Stack require multiple controllers or pre-existing infrastructure, making them unsuitable for initial deployments.
Innovation Solution
A computer-implemented method for automated deployment of computing infrastructure using a CMDB module to manage and store inventory data, a deployment module to automate infrastructure setup, a communication module for seamless component interaction, a NOG module for switch configuration, and a DNS module for network management, all integrated to streamline the deployment process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration methods are used for deploying data centres, then deployment can be performed with simple tools, but errors, inconsistencies, and extended downtime occur
Solution Approach 1:
The deployment system performs self-configuration by automatically discovering infrastructure components, generating configurations, and provisioning services without requiring manual intervention. The system discovers switches and servers, calculates IP addresses, and configures network stacks autonomously, eliminating human error while maintaining simple deployment processes
Solution Approach 2:
The system pre-calculates IP addresses and pre-generates configuration files before actual deployment occurs. By performing these preparatory actions in advance, the system ensures configuration consistency and eliminates timing-related errors that occur during manual deployment
2Extent of automation
If Cisco APIC is used for managing network infrastructure, then manual provisioning is eliminated, but three controllers are required for deployment
Solution Approach 1:
The patent combines multiple functions (discovery, configuration calculation, service provisioning, and infrastructure management) into a single integrated system. This consolidation eliminates the need for multiple separate controllers while maintaining automated network management capabilities, making the solution suitable for initial deployments with limited resources
Solution Approach 2:
The deployment system performs multiple functions including infrastructure discovery, IP address calculation, configuration generation, service provisioning, and ongoing management. This multi-functional approach replaces the need for specialized separate controllers, providing comprehensive automation with a single system
3Adaptability or versatility
If OpenStack Ironic is used for managing BareMetal servers, then complete lifecycle management is provided, but pre-existing infrastructure is required
Solution Approach 1:
The system performs preliminary discovery and configuration of BareMetal servers and network infrastructure before lifecycle management begins. By automatically discovering components and pre-configuring network stacks, the system creates the necessary infrastructure prerequisites automatically, eliminating the need for manual setup before using lifecycle management features
4Productivity
If automated deployment is implemented, then deployment speed and consistency are improved, but system complexity increases
Solution Approach 1:
The automated deployment system is divided into distinct functional modules: discovery module for infrastructure detection, calculation module for IP address generation, configuration module for config file creation, and provisioning module for service deployment. This segmentation allows each module to perform its specific function efficiently while keeping the overall system manageable and understandable
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for deploying a computing infrastructure (10) with an un-provisioned server (11) and switch (12) involves accessing instructions that initiate software components, including a configuration management database (CMDB), deployment module, communication module, and network operations gateway. The CMDB is initialized with information about the server and switch, and the communication module manages DHCP interfaces and allows communication between the CMDB and deployment module. The method calculates data for initializing the CMDB, configures DNS services, determines configurations for communication and switches, provisions network stacks, synchronizes the deployment module with the CMDB to start a server discovery process, and boots the un-provisioned server.