International Business Machines Corporation

Oracle International Corporation

Hewlett Packard Enterprise Development LP

Micro Focus Lcc

Nuance Communications, Inc.

Entit Software LLC

Vasu Networks Corporation

Suse LLC

Stephane Herman Maes

Dimitri Kanevsky

Abraham P Ittycheriah

Ponani S Gopalakrishnan

Prashant Gupte

Upendra V Chaudhari

Jiri Navratil

Jan Sedivy

Jeffrey Scott Sorensen

Keith Kuchler

Matthew Simon Newman

Rafah A Hosn

Jan Kleindienst

Thiruvilwamalai Venkatraman Raman

Paul Andrew Moskowitz

David Nahamoo

Liam David Comerford

Chalapathy Venkata Neti

Daniel Mark Coffman

Rajeev Bharadhwaj

Sankar Basu

Andrew William Senior

Alexander Zlatsin

Ganesh Nachiappa Ramaswamy

Srikanth Natarajan

Travis Scott Tripp

Edward Adam Epstein

Christopher William Johnson

Lars Rossen

Homayoon S M Beigi

Steven V DeGennaro

Jan Vana

Michael Yang

Petr Fiedler

Woong Joseph Kim

Thomas Goepel

Thiruvilvama Lai V Raman

Ankit Ashok Desai

Clifford A Pickover

Thomas Mario Cipolla

Wlodek Wlodzimierz Zadrozny

Ramesh Ambat Gopinath

James Campbell Colson

Mukund Padmanabhan

Vasudevan Ganesan

Neal J Alewine

John M Green

Martin Labsky

Jacob Christen Christfort

Mark Perreira

Bryan P Murray

John M Lucassen

Jean Sini

Alpana Tiwari

John Christopher Dolan

Ladislav Seredi

Peter S Poon

Ivan Pasqualini

Philippe Christian De Cuetos

Carl Prochilo

Jennifer A Healey

Robin Sabi Rajan Bejgum

Gaurav Kuchhal

Timothy Joseph Chainer

James Robert Lewis

Charles Philippe Tresser

Kerry Alan Ortega

Arthur R Zingher

David M Lubensky

Shai Halevi

Lalit R Bahl

Raimo Bakis

Huifang Wang

Marco Martens

Rosario Gennaro

Joseph D Rutledge

Michael Daniel Monkowski

Terje Strand

Ronald E Vanbuskirk

Lazaros Polymenakos

Tal D Rabin

Tomas Macek

Rheid Schloss

Andrzej Sakrajda

Frank Vosseler

Geoffrey G Zweig

Kevin Lee Wilson

Wenchao Sun

Lakshminarayana Mandaleeka

Bruce P Kitchens

Serdar Badem

Benoit Emmanuel Ghislain Maison

David R Boloker

Mukund Panmanabhan

Induprakas Kodukula

Ramachandran Varadharajan

Jaroslav Gergic

Roy Ritthaler

Karan Singh Chhina

Photina Jaeyun Jang

In some examples, a system migrates, responsive to a request, a workload comprising components and relationships among the components as represented by a topology model, the migrating comprising migrating the workload from the source infrastructure to a target infrastructure, and migrating components of the workload from the source infrastructure to the target infrastructure.

Workload migration

A technique includes providing at least one service blueprint to orchestrate application programming interfaces to manage the lifecycle of at least one cloud service.

Managing a cloud service

A method of executing a topology includes deriving executable logic from the topology. The method of executing the topology further includes, with an LCM engine, executing the topology based on the executable logic.

Execution of a topology

An application managed by a provider is configured to run according to a selected usage scenario of a group of usage scenarios. The group of usage scenarios include a hard-partitioned usage scenario in which instances of the application are hard partitioned in correspondence with tenants of the provider. The group of usage scenarios include a soft-partitioned usage scenario in which the instances of the application are soft partitioned in correspondence with the tenants of the provider. The configured application is executed.

Application configuration

A method of updating and editing realized topologies, comprising presenting a realized topology to a user, receiving input indicating modification of portions of the realized topology, and with a processor, executing logic associated with the modified portions based on a number of lifecycle management actions (LCMAs) of the realized topology. A system to update and edit a realized topology, comprising a processor and a graphical user interface (GUI) communicatively coupled to the processor, in which the GUI presents to a user a graphical representation of the realized topology, and in which the system receives input indicating modification of portions of the realized topology, and with a processor, executes logic associated with the modified portions based on a number of lifecycle management actions (LCMAs) of the realized topology.

Modifying realized topologies

In some examples, a marketplace system receives information from multiple service providers as part of onboarding of the multiple service providers with the marketplace system. Responsive to the onboarding, a cloud service created by the respective service provider is synchronized with the marketplace system. A marketplace catalog is linked with catalogs of the service providers, the linking including aggregating content of the catalogs into the marketplace catalog. Responsive to a request from a requester received through a portal of the marketplace system, at least one cloud service is identified using the marketplace catalog based on at least one search criterion of the request.

Fulfillment of cloud service using marketplace system

In one implementation, a method for topology based management with stage and version policies can include associating a topology of an application under development, determining a number of policies, wherein the number of policies include stage and version policies that define a number of available infrastructures for a given stage and version of the application, associating the number of policies to a number of nodes of the topology, and provisioning the topology with the associated number of policies.

Topology based management with stage and version policies

In one implementation, a method for topology based management of second day operations can include identifying a cloud service operating on a second system, discovering, via a first system, an existing realized topology of the second system as an inferred realized topology for the first system, wherein the existing realized topology is provisioned by the second system, defining a management process to be performed within the cloud service, via the first system, upon the instantiation of the inferred realized topology by the first system, and executing the management process utilizing the first system.

Topology based management of second day operations

Catalogs that describe respective offerings for fulfillment by respective applications, are aggregated to form an aggregate catalog. A request relating to at least one of the offerings is received based on content presented from the aggregate catalog. In response to the request, an orchestrated execution of an end-to-end process is performed to fulfill the request relating to the at least one offering, the executing of the end-to-end process comprising calling at least one of the applications.

Fulfilling a request based on catalog aggregation and orchestrated execution of an end-to-end process

A technique includes receiving, by a computer, data representing a task to be automated in association with a computing environment. The technique includes applying, by the computer, natural language processing to the data to generate a sequence of statements describing operations to be executed to perform the task. The sequence of statements is associated with a predetermined orchestration workflow language.

Natural language translation-based orchestration workflow generation

According to an example, a system may include an instance controller to manage service instances deployed on an infrastructure that facilitates data segregation and performance level compliance. The instance controller deploys a service instance of the service instances in a container and terminates the service instances in response to determining the service suite instance is idle based on the notification. Additionally, the system may deploy a component from the service instance from outside the container.

Service management and provisioning for tenant service instances

A method of managing the lifecycle of cloud service modeled as a topology includes, with a processor, generating a topology, the topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, associating a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes, and with a lifecycle management engine, executing the topology.

Management of the lifecycle of a cloud service modeled as a topology

Selecting resources for a cloud service can include defining a specific resource provider constraint parameter, determining a parameter value for the specific resource provider constraint parameter, analyzing a plurality of specific resource providers and selecting a specific resource provider from the plurality of available specific resource providers based on the analysis and using a best-fit model.

Policy based selection of resources for a cloud service

Managing the lifecycle of a cloud service modeled as a topology decorated by a number of policies includes with a processor, generating a topology or the realized topology, the topology or the realized topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology or the realized topology, and with a lifecycle management engine, updating the topology or the realized topology by associating a number of policies with the number of nodes within the topology or the realized topology.

Managing the lifecycle of a cloud service modeled as topology decorated by a number of policies

Growing community of inventors

Fremont, CA, United States of America

Stephane Herman Maes