Abstract: 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.

Abstract: 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.

Abstract: An Application Programming Interface (API) exchange located within a data center is configured to receive, from a customer, a request for access to one or more APIs corresponding to respective service provider networks and to which the API exchange provides access. Based on the request for access, the API exchange bundles the one or more APIs into an API bundle, generates a unique subscription key for accessing the API bundle, and sends the unique subscription key to the customer. The API exchange receives, from the customer, a service request for invoking a requested API of the API bundle, the service request including the unique subscription key. Upon authorizing the service request to access the API bundle based on the unique subscription key, the API exchange sends the service request to the service provider network corresponding to the requested API.

Abstract: 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.

Abstract: 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.

Abstract: In some examples, a method includes obtaining, by a data center infrastructure monitoring (DCIM) agent executing on a computing device deployed by a data center provider within a first data center of a plurality of geographically-distributed data centers, an infrastructure asset data object comprising infrastructure asset data for a physical infrastructure asset of a second data center of the plurality of geographically-distributed data centers; translating, by the DCIM agent using an asset mapping table, the infrastructure asset data object to formatted infrastructure asset data, wherein the asset mapping table maps one or more properties of infrastructure asset data objects to management protocol objects or control protocol objects for one of a management protocol or control protocol; and sending, by the DCIM agent to customer equipment co-located within the first data center, the formatted infrastructure asset data in a communication that conforms to one of the management protocol or control protocol.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A messaging service is disclosed that provides access to data center event data for physical infrastructure assets via dynamically configurable custom tags defined by customers. For example, a network services exchange provider or co-location provider deploys a data center monitoring system that monitors physical infrastructure assets that enable system operation within a data center for events. The system implements an API which applies custom tags defined by customers to the assets, wherein each custom tag defines attributes of the assets. The system receives subscription requests that describe events and custom tags applied to the assets. The data center infrastructure monitoring system publishes a subscription of event data related to the events for the assets to which the custom tags are applied. Further, a feed manager receives updates to asset equipment and changes to metadata describing the assets and automatically updates the subscription to account for the changes.

Abstract: 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.

Abstract: 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.

Abstract: In one example, an application development framework system comprises a microservice platform for developing and executing a plurality of microservices, wherein each microservice of the microservices comprises an independently-deployable service configured to execute one or more functions to fulfill an interface contract for an interface for the microservice; and an orchestration platform for developing and executing an orchestrator to orchestrate the microservices to execute an interconnection platform for a cloud-based services exchange configured to interconnect, using one or more virtual circuits, customers of the cloud-based services exchange.

Abstract: 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.

Abstract: In some examples, a cloud-based services exchange comprises a plurality of interconnection assets configured to connect at least one customer of the cloud-based services exchange to a plurality of cloud service providers; and an orchestration engine configured to modify the plurality of interconnection assets by receiving an indication of a client request for cloud exchange services offered by the cloud-based services exchange; selecting a workflow for providing the cloud exchange services, wherein the workflow specifies a set of tasks to be performed to fulfill the client request for the cloud exchange services; call one or more microservices to perform the tasks of the set of tasks as specified by the selected workflow; consolidate responses received from the microservices after performing the tasks; and send a response to the client request for the cloud exchange services based on the consolidated responses.

Abstract: A central infrastructure monitoring system includes an asset configurator; and a plurality of data center infrastructure monitoring systems each associated with a respective data center of a plurality of geographically distributed data centers that include one or more physical infrastructure assets of a plurality of physical infrastructure assets for enabling system operation within the respective data center. The data center infrastructure monitoring systems are coupled to the central infrastructure monitoring system.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: In some examples, a cloud-based services exchange comprises a plurality of interconnection assets configured to connect at least one customer of the cloud-based services exchange to a plurality of cloud service providers; and an orchestration engine configured to modify the plurality of interconnection assets by receiving an indication of a client request for cloud exchange services offered by the cloud-based services exchange; selecting a workflow for providing the cloud exchange services, wherein the workflow specifies a set of tasks to be performed to fulfill the client request for the cloud exchange services; call one or more microservices to perform the tasks of the set of tasks as specified by the selected workflow; consolidate responses received from the microservices after performing the tasks; and send a response to the client request for the cloud exchange services based on the consolidated responses.