Multi-tenant Cloud Node Selection via Application Attribute Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud-based PaaS offerings face inefficiencies and high costs due to the need for significant expertise and resources in managing web applications across different hypervisors and cloud providers, with idle virtual machines wasting resources and requiring separate instances for each customer's application, leading to security and resource sharing concerns when deploying multiple customers' applications on a single VM.

Innovation Solution

A method for selecting the most capable node in a multi-tenant cloud environment to host new applications by calculating the capacity of available nodes based on software repositories, active applications, and resource pools, allowing for efficient resource utilization and transparent idling and restarting of applications to conserve resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a separate VM is deployed for each customer's application, then security and isolation are improved, but resource utilization deteriorates and costs increase

Engineering Contradiction:
Improvesecurity isolationVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple customer applications into a single shared VM environment, allowing multiple applications to coexist on the same virtual machine. This consolidation improves resource utilization by eliminating idle VMs while maintaining security through sandboxing techniques that isolate each application's execution environment.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared VM infrastructure provides universal hosting capability for multiple customer applications simultaneously. The VM acts as a multi-functional platform that can accommodate different applications from different customers, reducing the need for dedicated single-purpose VMs and improving overall resource efficiency.

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

2Loss of energy

If multiple customers' applications are deployed on a single VM, then resource utilization improves, but security concerns and resource sharing conflicts worsen

Engineering Contradiction:
Improveresource utilizationVSAvoidsecurity isolation
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent segments the shared VM environment into isolated execution contexts for each customer application. Through sandboxing techniques, each application operates in its own secure container within the VM, preventing interference between applications while sharing the underlying hardware resources efficiently.

Inventive Principle:
Principle #1Segmentation

3Reliability

If VM capacity is sized for peak load, then service reliability is improved, but resource waste during low utilization periods worsens

Engineering Contradiction:
Improveservice availabilityVSAvoididle resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

By combining multiple applications on shared VMs, the system aggregates their resource requirements and utilization patterns. This allows the infrastructure to serve multiple workloads simultaneously, reducing the need to provision capacity for individual peak loads and minimizing idle resources when any single application is underutilized.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10255110B2Node selection for a new application in a multi-tenant cloud hosting environment
Publication Date: 2019.04.09 RED HAT INC
  • US10255110B2 patent drawing
  • US10255110B2 patent drawing
  • US10255110B2 patent drawing

AI summary

A method includes instantiating a first web application for a first application owner on a virtual machine and instantiating a second web application for a second application owner. The second application owner is different than the first application owner. Instantiating the second web application includes determining that the second web application is associated with an attribute. The first web application is also associated with the attribute, and the attribute comprises an implementation related property of the first web application and the second web application. Instantiating the second web application also includes identifying the virtual machine as configured to host web applications having the attribute, responsive to identifying the virtual machine, instantiating the second web application on the virtual machine hosting the first web application. The second web application is prevented from accessing the first web application and the first web application is prevented from accessing the second web application.