Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method and System for effectively migrating Applications to the Cloud

IP.com Disclosure Number: IPCOM000247295D
Publication Date: 2016-Aug-19
Document File: 2 page(s) / 154K

Publishing Venue

The IP.com Prior Art Database

Abstract

Public Cloud PaaS are becoming very popular because they provide an ecosystem of code and services, interacting with each other. Public Cloud PaaS are perfect to speed-up the developing and testing activities but there are some concerns to use Public Cloud PaaS for production like for example: o Customers are worried that building an application for a specific PaaS forces them to be linked to a specific technology, infrastructure and vendor o Customers needs more security requirements for Production Environment o Customers needs specific performance configurations For this reason one of the Customer Challenge is how to migrate an application available in the Public Cloud to a Private Cloud. This can be done today manually but it has several drawbacks and limitations. What is proposed here is a procedure to automatically migrate/onboard an application from the Public Cloud to a Private Cloud: o calculating the best topology to be deployed in the Cloud o connecting it to the services available in the Cloud Environment o mapping the Application Service Plan/SLA to the most effective Cloud Resource Allocation and Configuration.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method and System for effectively migrating Applications to the Cloud

This section describes the architecture and the procedure used in this innovative approach for migrating the workload into the Cloud.

The system architecture proposed is described in the next picture and is based on:


• A Cloud Manager that is responsible to manage Virtual Images in the Cloud Environment


• a repository, called Virtual Image Catalog (VIR), that contains information about the available virtual image templates


• a repository, called Virtual Service Catalog (VSR), that contains information about the Services available in the Environment


• a repository, called Application Repository (AR), that contains the Application binaries and data


• a repository, called Runtime Repository (AR), that contains the Runtime binaries and data

• a SW entity called Advisor for Migrating Cloud Application (AMCA) that has the logic to:
o determine the topology for deploying the Application in the Cloud through Virtual Images


o discovering the services needed by the Application


o map the Application service plan/SLA with a proper configuration in the Cloud

7

App A

10

 Virtual Machine 1

Service k

7

 Virtual Machine 2

Cloud Manager

2

1

10

 Advisor can be a Bluemix application and /or Process

Manager workflow

9

Advisor for Migrating Cloud Applications

8

4 5

3

8

6

9

Runtime Libraries

Image Catalog

Application Repository

Service Catalog

The procedure for performing the cloud migration is highlighted with the following main steps, as described also in the above picture:

1. Retrieve the list of Applications running in the Public Cloud Environment and select the Application to be migrated in the Private Cloud

1


Page 02 of 2

2. Download Application information, like: a. Application code and binaries b. Application configuration c. list of services that the Application uses d. list of runtime environments that the Application needs (this can be retrie...