Automating Service Deployment via Hosting Environment Constraints

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for configuring underlying elements of software applications in distributed computing environments are labor-intensive and error-prone, especially in large-scale data centers with diverse hardware components, requiring manual setup and ad hoc configurations.

Innovation Solution

Automating the deployment of service applications by exposing hosting environment constraints in a service model, allowing developers to define environmental dependencies as APIs, which are then used to automatically configure and refine hosting environments through map constructs, enabling efficient allocation and instantiation of roles across distributed nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration of underlying elements is used, then flexibility in setup is maintained, but labor intensity and error rate increase significantly

Engineering Contradiction:
Improvemanual configuration flexibilityVSAvoiddeployment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system enables self-service deployment by automatically configuring underlying elements based on service application requirements. The platform autonomously performs resource allocation, configuration generation, and element setup without requiring manual curator intervention, thereby eliminating labor-intensive operations while maintaining proper system configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary configuration actions by pre-defining templates and patterns for underlying elements. Before actual deployment, the system prepares configuration blueprints that automatically adapt to specific service requirements, enabling rapid and error-free deployment without manual setup for each new service.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual configuration by curators is used, then individual element setup can be customized, but the process becomes labor-intensive and error-prone

Engineering Contradiction:
Improveelement configuration customizationVSAvoidconfiguration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system maintains adaptability by dynamically adjusting configuration parameters based on service application requirements. Instead of fixed manual configurations, the system automatically modifies parameters such as resource allocation, networking settings, and security policies to match each service's specific needs while ensuring consistency and accuracy through automated validation.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system improves reliability by implementing feedback mechanisms that validate configuration accuracy. Automated checks verify that configured elements meet service requirements and platform standards, providing immediate feedback on configuration errors and enabling corrective actions before deployment, thereby eliminating the error-prone nature of manual configuration.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If ad hoc configuration solutions are used, then immediate setup is possible, but scalability to large platforms is severely limited

Engineering Contradiction:
Improveconfiguration speedVSAvoidplatform scalability
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system achieves scalability through universal configuration templates that can be applied across diverse platform environments. A single template system serves multiple functions by adapting to different service types, hardware configurations, and deployment scenarios, enabling consistent automated configuration whether deploying to a single node or an expansive distributed platform.

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

Solution Approach 2:

The system enables scalability by segmenting the configuration process into modular, independently manageable units. Each underlying element is configured through discrete, standardized steps that can be executed in parallel across multiple platforms, allowing the system to scale from small to large deployments without increasing complexity or manual intervention requirements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9300532B2Automating deployment of service applications by exposing hosting environment constraints
Publication Date: 2016.03.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9300532B2 patent drawing
  • US9300532B2 patent drawing
  • US9300532B2 patent drawing

AI summary

Methods, systems, and computer-readable media for automating deployment of service applications by exposing environmental constraints in a service model are provided. In general, the methods are performed in the context of a general purpose platform configured as a server cloud to run various service applications distributed thereon. Accordingly, the general purpose platform may be flexibly configured to manage varying degrees of characteristics associated with each of the various service applications. Typically, these characteristics are provided in the service model that governs the environmental constraints under which each component program of the service application operates. As such, hosting environments are selected and adapted to satisfy the environmental constraints associated with each component program. Adapting the hosting environments includes installing parameters transformed from configuration settings of each component program via map constructs, thereby refining the hosting environment to support operation of the component program.