CMDB-Driven Computing Infrastructure Deployment for Unprovisioned Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods for deploying and managing datacenters, especially offsite, face challenges such as manual configuration errors, inconsistencies, extended downtime, and lack of support for LLDP discovery and infrastructure management capabilities in existing solutions like Cisco APIC, OpenStack Ironic, and Microsoft Azure Stack.
Innovation Solution
A computer-implemented method for automated deployment of computing infrastructure using a CMDB module to manage inventory data, a DNS module for network services, a communication module for seamless interaction, a NOG module for switch provisioning, and a deployment module for automated network stack provisioning, reducing manual intervention and ensuring consistent configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration methods are used for deploying datacenter infrastructure, then flexibility and adaptability are maintained, but errors, inconsistencies, and extended downtime occur
Solution Approach 1:
The system enables self-service through automated discovery where the infrastructure automatically detects and configures itself. The discovery module autonomously identifies network devices, servers, and storage components without manual intervention, and the configuration module automatically generates and applies appropriate settings, eliminating the need for manual configuration while ensuring consistency and reducing errors.
Solution Approach 2:
The system performs preliminary actions by pre-defining configuration templates and discovery rules before deployment. The configuration module prepares configuration data in advance based on discovered infrastructure components, and the deployment module pre-stages provisioning actions. This preliminary preparation ensures consistent configurations are applied immediately upon discovery, reducing downtime and eliminating manual configuration errors.
2Adaptability or versatility
If existing solutions like Cisco APIC, OpenStack Ironic, or Microsoft Azure Stack are used, then specific management capabilities are provided, but they require pre-existing infrastructure or multiple controllers making them unsuitable for initial deployments
Solution Approach 1:
The system segments the infrastructure management functionality into independent modular components: a discovery module for detecting devices, a configuration module for generating settings, and a deployment module for provisioning. This segmentation allows each module to operate independently with minimal infrastructure requirements, enabling initial deployments without needing pre-existing complex infrastructure or multiple controllers. Each module can be deployed separately and scales as needed.
3Productivity
If traditional deployment methods are used, then existing infrastructure can be managed, but errors and inconsistencies lead to extended downtime
Solution Approach 1:
The system implements feedback through the discovery module that continuously monitors and detects infrastructure components and their states. The configuration module receives feedback from discovered devices about their current configurations and automatically generates appropriate configuration data. The deployment module receives feedback on provisioning status and adjusts accordingly. This closed-loop feedback mechanism ensures configuration accuracy while maintaining rapid deployment speed by automatically correcting inconsistencies without manual intervention.
Data Source
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.