Nutanix, Inc.

Pernixdata, Inc.

Akhilesh Joshi

Satyam B Vaghani

Gaurav Poothia

Naorem Khogendro Singh

Bryan Jeffrey Crowe

Heiko Friedrich Koehler

Shyan-Ming Perng

Pranav Desai

Deepak Muley

Amit Jain

Michal Ostrowski

Sanika Nitin Mokashi

Shankar Vilayannur Natarajan

Kevin Thomas

Anuraag Deepak Advani

Sanika Mokashi

A platform-as-a-service (PaaS) manager abstracts deployment of PaaS software stacks to different computing platforms such that the PaaS software stacks provide a common platform to host an application despite differences in the underlying architectures of the computing platforms. Each PaaS software stack is hosted on a service domain installed on a respective one of the computing platforms, and includes an operating system and provides access to a set of services for execution of applications. The some examples, the different computing platforms include multiple different cloud architectures.

Platform-as-a-service deployment including service domains

A platform-as-a-service infrastructure and application lifecycle manager is configured to implement a common services model to deploy selected services from a common set of services to service domains hosted on multiple different cloud platforms by abstracting dependence on availability of various additional supporting services, such as services that are platform-specific. The platform-as-a-service infrastructure and application lifecycle manager may also manage a lifecycle of available services, such as managing upgrades and/or patches to services.

Common services model for multi-cloud platform

Applications or Agents or Administrators can communicate with services and/or applications at hosted and/or remote locations via proxy service or application endpoints. Proxy Services described here may, in examples, manage the life cycle of communication channels, or tunnels to ensure guaranteed access to hosted services and applications regardless of their location. Examples of proxy services may create one or more tunnels, each in accordance with a particular tunneling protocol. The tunneling protocol used may be selected in accordance with a request, including information parameters&#x2014;in this manner, proxy services described herein may be quite flexible in supporting tunneling connections to multiple and variable types of services and tunneling protocols.

Generic proxy endpoints using protocol tunnels including life cycle management and examples for distributed cloud native services and applications

Non-transitory computer readable media are encoded with instructions which, when executed by one or more processors of a central computing system, cause the central computing system to connect with multiple service domains and determine that at least one service domain of the multiple service domains is eligible for upgrade. The instructions further cause the central computing system to store an upgrade package for the at least one service domain at a storage service separate from the central computing system and communicate access credentials to the storage service to the at least one service domain. The central computing system receives a communication from the at least one service domain indicative of upgrade status responsive to the at least one service domain having accessed the upgrade package at the storage service and updates a state management database based on the communication.

Upgrade systems for service domains

Example distributed caching systems and methods are described. In one implementation, a system has multiple host systems, each of which includes a cache resource that is accessed by one or more consumers. A management server is coupled to the multiple host systems and presents available cache resources and resources associated with available host systems to a user. The management server receives a user selection of at least one available cache resource and at least one host system. The selected host system is then configured to share the selected cache resource.

Distributed caching systems and methods

Fault domains are defined which reflect, either physically or virtually, the topology of a networked computing environment. These defined fault domains are then used to control where cached data is replicated when running in a write back cache mode. Unlike known replication approaches, the present approach replicates such data according to a user's defined data policy and based on the defined fault domains thereby avoiding the user having to keep track of changes in computing system configurations or update their data policy when virtual machines migrate from one host computing system to another.

Management and utilization of fault domains in distributed cache systems

Growing community of inventors

San Jose, CA, United States of America

Akhilesh Joshi