Server Stack Deployment Engine Cross-Server Dependency Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing server stack deployment methods face challenges in managing cross-server dependencies, particularly in multi-tier architectures, where servers of different types rely on each other for services and data, leading to complexities in provisioning and configuration management.

Innovation Solution

A server stack deployment engine is introduced that uses a recursive testing and provisioning methodology to manage cross-server dependencies by determining and modifying configurations of requisite and dependent servers, ensuring operational requirements are met without user intervention through a deployment script.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional deployment methods are used for server stacks with cross-server dependencies, then deployment process becomes complex and error-prone, but automated deployment scripts increase automation extent

Engineering Contradiction:
Improvedeployment automationVSAvoiddeployment process complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The deployment process is segmented into distinct phases: provisioning requisite servers first, then provisioning dependent servers that rely on the requisite servers. This segmentation allows automated deployment scripts to handle complex cross-server dependencies by breaking them into manageable, sequential steps, reducing errors while increasing automation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The deployment script performs preliminary actions by provisioning requisite servers before provisioning dependent servers. This preliminary setup ensures that when dependent servers are deployed, their required services and configurations are already in place, automating the dependency management process and reducing deployment complexity.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If manual configuration management is used for cross-server dependencies, then configuration accuracy may be maintained, but deployment time increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiddeployment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The deployment script implements self-service by automatically determining the provisioning sequence of servers based on their dependency relationships. The script autonomously identifies which servers are requisite and which are dependent, then configures them in the correct order without manual intervention, maintaining configuration accuracy while significantly reducing deployment time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The deployment process incorporates feedback mechanisms where the script monitors the provisioning status of servers and automatically adjusts the deployment sequence. This feedback loop ensures that servers are configured in the correct dependency order, maintaining precision while automating the time-consuming aspects of configuration management.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If servers are provisioned in arbitrary order, then deployment simplicity is maintained, but operational requirements may not be satisfied

Engineering Contradiction:
Improvedeployment simplicityVSAvoidoperational requirement satisfaction
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The deployment script implements dynamic provisioning by automatically adapting the provisioning sequence based on the specific dependency relationships between servers. Rather than using a fixed arbitrary order, the script dynamically determines the correct sequence by analyzing which servers are requisite and which are dependent, ensuring operational requirements are met while maintaining ease of operation through automation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11606251B2Deploying a server stack having a cross-server dependency
Publication Date: 2023.03.14 ORACLE INT CORP
  • US11606251B2 patent drawing
  • US11606251B2 patent drawing
  • US11606251B2 patent drawing

AI summary

Techniques for deploying a server stack having a cross-server dependency are disclosed. A deployment engine initiates a deployment process for a server stack. The deployment engine provisions servers of one server type (“requisite servers”). The deployment engine attempts to provision servers of another server type (“dependent servers”). The deployment engine executes a test that requires the dependent servers to invoke a service executed by the requisite servers. Based on the test results, the deployment engine determines that an operational requirement of the dependent servers is not satisfied. The deployment engine modifies a configuration for the requisite servers to satisfy the operational requirement of the dependent servers. The deployment engine re-provisions the requisite servers using the modified configuration. The deployment engine completes the deployment process for the server stack.