Virtual Machine Sizing by Removing Unused Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Virtual machines are often installed with a full technology stack, including a physical host, operating system, container, application, and services, leading to unnecessary overhead in terms of increased main memory consumption and disk storage, which hinders their efficient use.

Innovation Solution

A method and apparatus for sizing virtual machines by determining and deinstalling or disabling unused aspects of the extended application layer and container infrastructure, using agents to monitor resource usage and a configurator to initiate the removal of unnecessary components, thereby optimizing the technology stack.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If virtual machines are installed with a full technology stack including physical host, operating system, container, application, and services, then the virtual machine can operate reliably and perform all required functions, but the main memory consumption and disk storage increase unnecessarily

Engineering Contradiction:
Improvevirtual machine operation reliabilityVSAvoidmain memory consumption and disk storage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and removes unnecessary components from the full technology stack by identifying unused services, applications, containers, and operating system features. The system selectively deinstalls or disables components that are not required for the virtual machine's intended function, thereby reducing resource consumption while maintaining only the essential elements needed for reliable operation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The technology stack is segmented into essential components and optional components. The system distinguishes between core elements required for virtual machine operation (hypervisor, basic operating system functions) and optional elements (specific applications, services, containers). This segmentation enables selective installation and removal of components based on actual needs, reducing overall resource consumption.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If virtual machines are installed with a full technology stack, then all possible functions and services are available, but the device complexity increases

Engineering Contradiction:
Improvefunctional capabilityVSAvoidtechnology stack complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system extracts and removes unnecessary complexity from the technology stack by identifying and removing unused services, applications, and configurations. This simplifies the virtual machine environment while preserving the essential functional capabilities needed for the intended purpose, thereby reducing device complexity without sacrificing adaptability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The technology stack is made dynamic and adjustable rather than static and fixed. The system enables dynamic configuration where components can be added or removed based on actual usage requirements. This dynamic approach allows the virtual machine to maintain functionality while reducing complexity by only installing what is currently needed.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If virtual machines are installed with a full technology stack, then the virtual machine can support all applications and services, but the productivity decreases due to unnecessary overhead

Engineering Contradiction:
Improveapplication and service supportVSAvoidresource utilization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system extracts and removes unnecessary overhead components that do not contribute to productivity. By identifying and removing unused services, applications, and system features, the virtual machine achieves better resource utilization efficiency while maintaining the capability to support required applications and services through selective component installation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the configuration parameters of the virtual machine by adjusting which components are installed, enabled, or disabled. This parameter adjustment optimizes resource allocation and improves productivity by ensuring that only necessary components consume system resources, while maintaining the flexibility to support required applications and services.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8683459B2Automated virtual appliance sizing
Publication Date: 2014.03.25 SAP SE
  • US8683459B2 patent drawing
  • US8683459B2 patent drawing
  • US8683459B2 patent drawing

AI summary

Methods and apparatus are provided for sizing the operating system of a virtual machine. The computer-implemented method includes receiving information representative of an extended application layer and a container, both of which operate at a virtual machine at a host. A determination is made regarding whether one or more aspects of the extended application and the container may be deinstalled by testing at the virtual appliance preconfigured sets of extended application layers and container infrastructure layers, the testing of preconfigured sets performed in order from a smallest preconfigured set having a smallest number of components to a lamest preconfigured set having a lamest number of components. The extended application and the container are implemented without the deinstalled aspects.