Automated Service Catalog Entry Generation for Legacy VM Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud-computing management platforms face challenges in automatically generating service catalog entries for virtual machines provisioned in non-cloud environments, as these machines often do not conform to cloud standards, leading to manual, error-prone, and resource-intensive migration processes during integration into cloud environments.

Innovation Solution

A method utilizing infrastructure-discovery and application-discovery tools to automatically generate service catalog entries by receiving and correlating information about virtualized computing infrastructure and applications, enabling the creation of standardized entries that conform to cloud standards.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual entry-generation procedure is used to create service catalog entries for non-cloud virtual machines, then the entries can be created with attention to detail, but the process becomes cumbersome, error-prone, and time-consuming

Engineering Contradiction:
Improveaccuracy of service catalog entriesVSAvoidtime required for entry generation
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system automatically copies information from existing virtual machine configurations, infrastructure data, and application metadata to generate service catalog entries. This copying approach eliminates manual transcription while maintaining accuracy through automated data extraction and transformation processes.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The service catalog entry generation process performs self-service by automatically discovering virtual machine attributes, inferring service requirements, and populating catalog entries without human intervention. The system uses built-in discovery mechanisms to gather necessary information and generate entries autonomously.

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If manual entry-generation procedure is used to create service catalog entries for non-cloud virtual machines, then the entries can be customized accurately, but the process becomes vulnerable to errors

Engineering Contradiction:
Improveaccuracy of service catalog entriesVSAvoiderror susceptibility of entry generation
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

By copying data directly from source systems through automated discovery tools, the system eliminates manual transcription errors. The automated copying process maintains data integrity through structured extraction and validation mechanisms, reducing human error susceptibility.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system incorporates feedback loops that validate discovered information against expected formats and constraints, automatically correcting errors and flagging anomalies. This feedback mechanism ensures high reliability by continuously verifying data accuracy throughout the entry generation process.

Inventive Principle:
Principle #23Feedback

3Productivity

If automated means are used to generate service catalog entries, then the process becomes efficient and scalable, but the virtual machine must conform to cloud environment characteristics and standards

Engineering Contradiction:
Improvespeed of entry generationVSAvoidcompatibility with cloud standards
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system automatically adjusts virtual machine parameters and configurations to conform to cloud environment standards during the discovery and entry generation process. This includes transforming non-cloud VM attributes into cloud-compatible service catalog formats while maintaining the essential characteristics of the original virtual machines.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The service catalog entry acts as an intermediary representation that bridges non-cloud virtual machines and cloud environment requirements. The automated generation process creates this intermediate format that satisfies both the original VM characteristics and cloud platform standards, enabling seamless integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Manufacturing precision

If manual entry-generation procedure is used for thousands of non-cloud virtual machines, then each entry can be carefully verified, but the resource consumption becomes extraordinarily high

Engineering Contradiction:
Improvequality control of service catalog entriesVSAvoidcomputational resources required
Core Design Contradiction:
Manufacturing precisionVSLoss of energy

Solution Approach 1:

The automated copying mechanism efficiently replicates VM information across thousands of entries without requiring proportional human resources. This bulk copying approach maintains quality through template-based generation and automated validation, dramatically reducing resource consumption compared to manual verification of each entry.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system uses universal templates and standardized processes that can generate and verify service catalog entries across thousands of virtual machines using the same automated logic. This multi-functional approach allows a single automated process to handle diverse VM configurations efficiently, maintaining quality without increasing resources proportionally.

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

Data Source

PatentUS10250461B2Migrating legacy non-cloud applications into a cloud-computing environment
Publication Date: 2019.04.02 KYNDRYL INC
  • US10250461B2 patent drawing
  • US10250461B2 patent drawing
  • US10250461B2 patent drawing

AI summary

A method and associated system automatically migrates a non-cloud service from a legacy non-cloud virtualized computing environment into a cloud-computing environment. These methods and systems enhance standard cloud-management systems with the introduction of independent infrastructure-discovery and application-discovery tools. By autonomously examining the legacy non-cloud environment, these tools can produce information describing characteristics of the legacy service in sufficient detail to enable the cloud-management system to generate and automatically insert an entry for the legacy service into the cloud-computing environment's service catalog. When a user of the cloud-computing environment subsequently requests the non-cloud service, the cloud-management platform may then use the new entry to provision the legacy service as though it had been a standard cloud service.