Equinix, Inc.

Oracle International Corporation

Jaganathan Jeyapaul

Brian James Lillie

Parveen Kumar

Venkatachalam Rangasamy

Vijaay Doraiswamy

Gagan Maheshwari

Purvish Purohit

Mohan Navaratna

Ramchandra Jayateerth Koty

Prabhakar Gundugola

Nathan Joseph Janken

Sriharsha Mukundappa Sathyavathi

Tsunyen Weng

Krithika Bharathi Sundaram

Parvathy Unnikrishnan

Senthil Kumar Balakrishnan

Harshith Bhaskar Vakkaligara

Pragnesh Shashikant Panchal

Jeffrey Trent

Swayambhu Raparti

Ashwin Kamath

Vijay Bhasker Mula

Esha Sharma

Kalidas Ganesan

Balasubramaniyan Kannan

Manikandan Vasu

Divesh Kumar

Ramnath Anantharaman

Srinivasa Rao Yedluri

Kumar Pratik

Narayanan Selvam

Jayadev Hiremath

Jay Hiremath

Senthilkumar Somasundaram

Instances of an application pod may be deployed to many different computing environments spanning native cloud installations, SaaS providers, and on-premise data centers. In order to make uniform changes to a distribution of an application pod, a lock manager may receive and schedule lock requests from many different types of utilities. These utilities may schedule exclusive locks on the application pod throughout the different computing environments, such that patches, updates, security protocols, and other changes may be instituted without interference from changes made concurrently by other utilities. The lock manager may schedule immediate and future locks, with lock extensions and lock overrides available for flexibility.

Lock management for distributed application pods

In one example, a cloud-based services exchange comprises a plurality of interconnection assets configured to connect a customer of the cloud-based services exchange to one or more cloud service providers, the plurality of interconnection assets including a virtual circuit by which the customer accesses a cloud service from the one or more cloud service providers; and an orchestration engine configured to modify the plurality of interconnection assets.

Interconnection platform for real-time configuration and management of a cloud-based services exchange

Techniques for self-service orchestration are disclosed. A system deploys instances of a self-service orchestration agent to tenant-specific software-as-a-service (SaaS) environments operating in a multi-tenant SaaS environment, without reconfiguring existing software in the tenant-specific SaaS environments. Each self-service orchestration agent includes functionality to configure one or more components. Each tenant-specific SaaS environment includes a dedicated set of software operating on a dedicated logical partition of hardware infrastructure. The system receives, via a self-service orchestration interface, a request to configure a component across the tenant-specific SaaS environments. The system: transmits the request to a self-service orchestration module that is operating in the multi-tenant SaaS environment and configured to communicate with each instance of the self-service orchestration agent; dispatches, by the self-service orchestration module, the request to each instance of the self-service orchestration agent; configures, by each of the self-service orchestration agents in a corresponding tenant-specific SaaS environment, the component.

Self-service orchestration platform

In some examples, a method includes receiving, by a data center infrastructure monitoring system, a registration request that indicates a method of a subscription application programming interface and specifies one or more event subjects of events describing a system operation of a data center; storing, by the data center infrastructure monitoring system to a data-topic map, respective mappings for the one or more event subjects to a topic of a cloud-based publication platform; monitoring, by a data center infrastructure monitoring system, a plurality of physical infrastructure assets that enable system operation within the data center to obtain an event that describes one of the event subjects; and publishing, by the data center infrastructure monitoring system, the event to the topic.

Near real-time messaging service for data center infrastructure monitoring data

In general, this disclosure describes techniques for coordinating, with a cloud exchange, automated cloud-based disaster recovery across containers from a failed cloud service to a backup cloud service. In some examples, an orchestration engine for a cloud exchange is configured to: detect an indication of a disruption in a first cloud service provided by a first cloud service provider network coupled to the cloud exchange to send and receive data packets via the cloud exchange; provision, in response to detecting the indication of the disruption in the first cloud service, disaster recovery infrastructure layers in containers of a second cloud service provided by a second cloud service provider network coupled to the cloud exchange; obtain code and state from containers of the first cloud service; and communicate the code and state to the disaster recovery infrastructure layers in the containers of the second cloud service.

Container-based cloud exchange disaster recovery

In some examples, a customer churn risk engine is configured to query at least one of co-location data indicating co-location facility usage by a particular co-location facility customer and telemetry data indicating interconnections established between the particular co-location facility customer and at least one additional co-location facility customer within at least one co-location facility operated by a co-location facility provider. The customer churn risk engine is further configured to generate, based at least in part on at least one of the co-location data and the telemetry data, a churn risk score for the particular co-location facility customer. The customer churn risk engine is configured to output the churn risk score for the particular co-location facility customer.

Customer churn risk engine for a co-location facility

Interconnection platform for real-time configuration and management of a cloud-based services exhange

A method includes receiving, by an asset privacy system, an input video feed that includes images of one or more assets located within a data center, identifying, by the asset privacy system, one or more corresponding assets for the images of the one or more assets, determining, by the asset privacy system, an asset of the one or more assets a customer is not authorized to view, and generating, from the input video feed, by the asset privacy system based at least on the determining, an output video feed that does not include images of the asset the customer is not authorized to view and that does include images of at least one other asset of the one or more assets.

Data center viewing system

In one example, a cloud exchange comprises an interconnection platform of a network data center to configure a plurality of interconnection assets of the network data center to interconnect customer networks of a plurality of customer networks co-located in the network data center, the interconnection platform comprising: a network event unit controller configured to receive an indication of a network event of an interconnection asset of the plurality of interconnection assets; generate, in response to the network device report message, one or more network event messages based on the network event, wherein each of the network event messages includes an indication of the network event; and send the one or more network event messages to one or more customer systems for respective customer networks of the plurality of customer networks, wherein the one or more customer systems are affected by the network event.

Event-driven notification and network service bus for a cloud exchange

In some examples, a method includes querying, by a magnetic score engine executing at a computing device, first telemetry data indicating one or more interconnections established between a first co-location facility customer and at least one additional co-location facility customer within at least one co-location facility operated by a co-location facility provider. The method further includes generating, by the magnetic score engine and based at least in part on the first telemetry data, a magnetic score for the first co-location facility customer, the magnetic score indicating an importance of the first co-location facility customer to the least one additional co-location facility customer being co-located at the at least one co-location facility. The method further includes outputting, by the magnetic score engine and for display at a display device, the magnetic score for the first co-location facility customer.

Magnetic score engine for a co-location facility

Techniques for hot swapping and hot scaling containers between cloud services are disclosed. In one example, a method includes storing, with a cloud exchange, data indicating an association of a first container of a first private network with a second container of a second private network, wherein the first private network and the second private network are coupled to the cloud exchange to send and receive data packets via the cloud exchange. The method further includes sending, with the cloud exchange based on the association, state of the first container to the second container.

Hot swapping and hot scaling containers

In one example, described herein is an interconnection platform for dynamically configuring and managing a cloud-based services exchange, or 'cloud exchange,' to facilitate virtual interconnections ('virtual circuits') for cloud services delivery from cloud service providers to one or more cloud customers. As described herein, the interconnection platform facilitates event-driven notification to push virtual circuit configuration status updates to customer systems of customers of the cloud exchange provider that interface with the interconnection platform.

Interconnection platform with event-driven notification for a cloud exchange

Techniques are disclosed for facilitating inter-container communications, via a cloud exchange, for containers executing at logically isolated networks. In one example, the techniques of the disclosure provide a method including sending, by a container to a cloud exchange via an application programming interface exposed by an interconnection platform of the cloud exchange, container registration data for the container, the container registration data including a network address for a host that executes the container and a container identifier for the container.

Virtual network inter-container communication

Growing community of inventors

San Jose, CA, United States of America

Jaganathan Jeyapaul