Cloud Service Topology Policy Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud service management systems face challenges in designing, provisioning, deploying, and managing cloud services due to the lack of intuitive association of policies with physical topologies, making it difficult to describe infrastructure architecture and application models, leading to inefficient resource utilization and potential mistakes.

Innovation Solution

The implementation of architecture-descriptive topologies that define the physical architecture of a cloud service, allowing for the association of policies and lifecycle management actions with nodes, groups, and the entire topology, enabling a policy-based framework for provisioning, deployment, monitoring, and remediation processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual deployment methods are used for cloud services, then flexibility in deployment is maintained, but administrative time and resource consumption increase significantly

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidadministrative time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service deployment through automated topology templates that self-provision infrastructure resources. The topology model automatically discovers and configures infrastructure components without requiring manual administrative intervention, allowing the cloud service to deploy itself while maintaining flexibility through template-based customization.

Inventive Principle:
Principle #25Self-service

2Loss of time

If automated deployment tools are used, then administrative time is reduced, but the association between policies and physical topology becomes unclear

Engineering Contradiction:
Improveadministrative timeVSAvoidtopology-policy association
Core Design Contradiction:
Loss of timeVSLoss of information

Solution Approach 1:

The system segments the cloud service model into distinct topology components (infrastructure, platform, application layers) with explicit relationships between them. Each component is represented as a separate node in the topology graph, allowing policies to be clearly associated with specific physical infrastructure elements while maintaining automated deployment capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The topology model serves as an intermediary layer between automated deployment tools and policy management. It provides a structured representation that connects infrastructure resources with application requirements, enabling both automated provisioning and clear policy-to-topology associations through the topology's explicit relationship definitions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If comprehensive policy management is implemented across the cloud service lifecycle, then deployment accuracy improves, but system complexity increases

Engineering Contradiction:
Improvedeployment accuracyVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system applies local quality by associating specific policies with specific topology nodes rather than applying uniform policies across the entire system. Each infrastructure component, platform layer, and application can have its own tailored policies, improving deployment accuracy for each component while managing complexity through localized policy scope.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If manual linking of applications to infrastructure is performed, then customization flexibility is maintained, but resource utilization efficiency decreases

Engineering Contradiction:
Improvecustomization flexibilityVSAvoidresource utilization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary action by pre-defining topology templates with established best practices and optimal configurations. These templates provide a head start for deployment, automatically linking applications to appropriate infrastructure resources based on predefined relationships, which improves resource utilization efficiency while maintaining customization flexibility through template parameters.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10284427B2Managing the lifecycle of a cloud service modeled as topology decorated by a number of policies
Publication Date: 2019.05.07 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10284427B2 patent drawing
  • US10284427B2 patent drawing
  • US10284427B2 patent drawing

AI summary

Managing the lifecycle of a cloud service modeled as a topology decorated by a number of policies includes with a processor, generating a topology or the realized topology, the topology or the realized topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology or the realized topology, and with a lifecycle management engine, updating the topology or the realized topology by associating a number of policies with the number of nodes within the topology or the realized topology.