Provisioning Server Replication for Configuration Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software provisioning systems lack adequate tools for integrating and automating tasks across dispersed systems, leading to inconsistencies and increased administrative complexity, particularly in large networks where multiple installer servers are required to manage software provisioning across wide geographic areas.

Innovation Solution

The system replicates provisioning server configurations to maintain consistency, utilizing metadata and inventory transfers between servers through standard provisioning protocols, enabling centralized management, backup, and load-balancing, as well as simplifying the addition of new servers and propagation of updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple dispersed installer servers are maintained to support software provisioning across wide geographic areas, then coverage and capacity are improved, but inconsistency between servers and administrative complexity increase

Engineering Contradiction:
Improvesoftware provisioning capacityVSAvoidprovisioning system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements server-to-server replication where a source provisioning server automatically copies its configuration, metadata, and inventory to target provisioning servers. This creates consistent replicas across dispersed locations, eliminating manual configuration efforts and ensuring all servers maintain identical provisioning capabilities without requiring complex administrative oversight.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent combines multiple provisioning server functions into a unified replication system where configuration management, metadata synchronization, and inventory transfer are integrated into a single automated process. This merges what would otherwise be separate administrative tasks into one cohesive replication operation, reducing overall system complexity.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of manufacture

If manual configuration of each installer server is performed, then initial setup is possible, but time consumption and potential for inconsistency increase

Engineering Contradiction:
Improveserver setup easeVSAvoidserver configuration time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the source provisioning server pre-configure all necessary settings, metadata, and inventory information before replication occurs. This preliminary preparation allows target servers to be automatically populated with complete configurations, eliminating the need for time-consuming manual setup at each location.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying to transfer the complete configuration state from the source server to target servers automatically. This copying mechanism reproduces the source server's exact configuration state, eliminating manual configuration efforts and ensuring consistency across all provisioning servers in the network.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If changes are made to dispersed installer servers manually, then local customization is possible, but inconsistency between servers arises

Engineering Contradiction:
Improveserver customization capabilityVSAvoidconfiguration consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements feedback through the replication mechanism where the source provisioning server continuously synchronizes its configuration state to target servers. This feedback loop ensures that any changes made at the source are automatically propagated to all targets, maintaining configuration consistency while still allowing the system to adapt to changing requirements through centralized updates.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies universality by creating a standardized replication framework that can serve multiple provisioning servers across different geographic locations with the same configuration template. This universal approach allows the system to maintain consistency across diverse locations while adapting to local network conditions and requirements through the same core configuration set.

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

4Reliability

If an installer server fails, then service disruption occurs, but recovery time determines impact severity

Engineering Contradiction:
Improveprovisioning service reliabilityVSAvoidserver recovery ease
Core Design Contradiction:
ReliabilityVSEase of repair

Solution Approach 1:

The patent implements beforehand cushioning by maintaining replicated provisioning servers that serve as pre-prepared backups. When a source server fails, the replicated target servers are already configured and ready to immediately take over provisioning services, providing a cushion against service disruption without requiring time-consuming recovery procedures.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The patent uses copying to create standby replicas of the provisioning server configuration and data. These copies serve as immediate replacements when the original server fails, eliminating the need for manual reinstallation and reconfiguration during recovery, thereby dramatically reducing repair time and improving reliability.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9727320B2Configuration of provisioning servers in virtualized systems
Publication Date: 2017.08.08 RED HAT INC
  • US9727320B2 patent drawing
  • US9727320B2 patent drawing
  • US9727320B2 patent drawing

AI summary

A software provisioning environment can include several provisioning servers for providing software provisioning to one or more target machines. In the environment, one of the provisioning servers can initiate a replication action. The replication action can transfer and apply the metadata from one provisioning server to another provisioning server. Additionally, the replication action can transfer and apply portions of an inventory of provisioning objects from one provisioning server to another provisioning server. During the replication action, the provisioning server can utilize the interfaces and protocols of standard provisioning processes to transfer the metadata and portions of the inventory.