Automated Server Provisioning Using Master Image Copying

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual provisioning of servers and other computing devices for web sites is time-consuming and prone to human error, lacking repeatability, especially in environments with varied hardware and software configurations, making it difficult to scale or recover from failures.

Innovation Solution

An automated provisioning system that communicates with agents on each device, using a central file system and database to manage software installation and configuration, ensuring consistency and security through authentication and encryption, and employing a role-based approach to accommodate different site requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual provisioning is used to install and configure software on servers, then flexibility in handling varied hardware and software configurations is maintained, but the process becomes time-consuming and prone to human error

Engineering Contradiction:
Improveflexibility in handling varied configurationsVSAvoidprovisioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates a master image containing the complete software stack and configuration for a server. This master image can be copied and deployed to multiple servers automatically, eliminating manual provisioning while maintaining consistency across diverse hardware configurations. The master image serves as a template that can be adapted to different server types through automated detection and configuration.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-configuring a complete software environment in the master image before deployment. All necessary software components, dependencies, and configurations are prepared in advance, allowing automated installation and reducing on-site provisioning time while handling varied configurations through automated detection.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual provisioning is used, then custom configuration for each server is possible, but repeatability and consistency across servers are compromised

Engineering Contradiction:
Improvecustom configuration capabilityVSAvoidrepeatability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The master image is copied identically to multiple servers, ensuring that each server receives the exact same software configuration. This copying process guarantees repeatability and consistency across all servers while the automated detection and configuration components allow for necessary customizations based on specific server hardware or software requirements.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system incorporates feedback mechanisms where the provisioning process detects the actual state of each server and automatically adjusts the deployment accordingly. This feedback loop ensures that the master image is applied correctly while accommodating variations in server configurations, maintaining both repeatability and adaptability.

Inventive Principle:
Principle #23Feedback

3Productivity

If automated provisioning is implemented, then provisioning speed and consistency are improved, but security risks increase due to remote access requirements

Engineering Contradiction:
Improveprovisioning speedVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

Security measures are implemented preliminarily through authentication and encryption mechanisms built into the provisioning system before any remote access occurs. The system establishes secure communication channels and verifies credentials in advance, allowing automated provisioning to proceed at high speed while security risks are mitigated by pre-configured protective measures.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If comprehensive software stacks are deployed to support diverse site requirements, then adaptability to different configurations is achieved, but device complexity increases

Engineering Contradiction:
Improvesupport for diverse site requirementsVSAvoidsoftware configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The comprehensive software stack is segmented into modular components within the master image, organized by function and dependency. This segmentation allows the automated provisioning system to selectively deploy only the necessary components for each specific server role, reducing the effective complexity on individual devices while maintaining the ability to support diverse site requirements through combination of modules.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The master image is designed as a universal template that can serve multiple server types and configurations through automated detection and role assignment. Rather than creating separate configuration sets for each server type, the system uses a single multi-functional master image that adapts to different requirements, reducing the complexity of managing multiple configurations while maintaining broad adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7743147B2Automated provisioning of computing networks using a network database data model
Publication Date: 2010.06.22 HEWLETT PACKARD ENTERPRISE DEV LP
  • US7743147B2 patent drawing
  • US7743147B2 patent drawing
  • US7743147B2 patent drawing

AI summary

A framework for automatically provisioning computing devices includes a central database system and a central file system. Information stored in the database comprises a model of the individual devices, as well as the interconnections of the devices. The central file system stores the software components to be installed on the devices. When provisioning is carried out, the database sends commands to agents located on each device which cause them to retrieve and install the software components from the file system, and to configure the components according to the stored model.