Browse Prior Art Database

Method and System for Progressively Migrating Application Program Interface (APIs) in Software Defined Environment (SDE) Disclosure Number: IPCOM000245017D
Publication Date: 2016-Feb-06
Document File: 6 page(s) / 188K

Publishing Venue

The Prior Art Database


A method and system is disclosed for progressively migrating application program interface (APIs) in software defined environment (SDE).

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

Page 01 of 6

Method and System for Progressively Migrating Application Program Interface (APIs) in Software Defined Environment (SDE)

In software defined environment (SDE), entire IT infrastructure is visualized and delivered as a service. Management of networking, storage, compute, or data center is controlled by intelligent software rather than hardware component of the infrastructure. SDE enables abstraction and virtualization of IT resources through various application program interface

APIs. Open-source cloud-computing software platform controls and manages large pools of compute, storage, and networking resources throughout a data center through dashboard and web interfaces. In SDE, one such software platform may consist of hundreds or thousands of APIs, supporting core business applications for a huge number of organizations. Therefore, it is non-trivial to migrate from one system to another such as, for example, many enterprises have invested substantially on legacy storage management systems. It is critical for the system administrator and migration developers to know the order and priority of API migration in order to have a successful transformation with minimal cost. There is a need for a system and method to migrate the API supported services from a legacy storage management system to software defined storage (SDS).

Disclosed is a method and system for progressively migrating APIs in software defined environment. The method and system utilizes a recommender that recommends order and priority of API migration by considering the popularity, function importance, business importance, and dependency relationship. The recommender helps in deciding the order and priority of API migration based on popularity of the APIs as well as their importance in terms of functionality, business and the dependencies with other APIs.

In accordance with the method and system, as illustrated in figure 1, popularity of API can be measured by the number of accounts (i.e., clients) by referencing the API, such as, but not limited to, number of successful service requests per a predetermined time window, number of errors thrown by the API (or submitted ticket issues) per a predetermined time

window, and the API usage information (number of method invocations and annotations) from source code files. The first three metrics can be collected from log files while the last one, API usage information, can be identified from source code files using text matching based or compilation based approach. Subsequently, the collected statistics are summarized and computed for a final popularity ranking.


Page 02 of 6

Figure 1

As shown in figure 1, the APIs along each dimension are sorted and a ranking score 1, 2, ..., n, is assigned. Thereafter, the popularity score is computed which is a weighted sum of the ranking score along each dimension. The weights can be adjusted by users based on importance of each dimension in the score computation, such as, for example, the