Abstract: Redirecting message flows to bypass load balancers. A destination intermediary receives a source-side message that includes a virtual address of a load balancer as a destination, and that is augmented to include a network address of a destination machine as a destination. The destination intermediary determines that a source intermediary should address subsequent network messages that originate from a source machine and that are associated with the same multi-message flow to the destination machine while bypassing the load balancer. The destination intermediary modifies the source-side message so the destination for the source-side message addresses the destination machine, and passes the modified source-side message to the destination machine.

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: 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: The obtaining of a lease on a resource in a circumstance in which multiple lease servers are capable of granting a lease to the resource. A computing entity attempts to obtain the lease on the resource by causing a lease request to be sent to each of at least most (and perhaps all) of the lease servers. In response, the computing entity receives one or more responses to the lease requests. If the computing entity receives grants of a lease from a majority of the lease servers that are capable of granting a lease to the resource, then it is determined that the computing entity acquired a lease on the resource. On the other hand, if the computing entity receives grants of a lease from less than a majority of the lease servers, it is determined that the computing entity failed to acquire the lease on the resource.

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: 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: The present disclosure relates to system(s) and method(s) for generating test data for testing an Internet of Things (IOT) network. Initially, the system is configured for receiving sensor ontology data of at least one sensor to be simulated for testing an Internet of things (IOT) network. The sensor ontology data may include a range of operation of the sensor and a frequency of operation of the sensor. Further, the system is configured for accepting a set of test scenarios for testing the IOT network. Furthermore, the system is configured for generating master test data for testing the IOT network, wherein the master test data comprises a set of test packages corresponding to the set of test scenario and the sensor ontology data.

Abstract: Embodiments are directed to routing requests with different protocols to the same destination. In one scenario, a computer system receives a request that uses a specified protocol. The request includes a request source identifier and a request destination identifier. The computer system identifies, based on both the request source identifier and the request destination identifier, a destination to send the request to and generates a routing entry for the request that indicates which destination the first request was sent to. The computer system receives another request that uses a different protocol. This request includes a request source identifier and a request destination identifier of its own. The computer system determines that the request source identifier and request destination identifier of the subsequent request match those of the generated routing entry, and routes the subsequent request to the destination indicated in the routing entry.

Abstract: A method of many-to-one auto-discovery between modules includes: a source (sender) module sends the same source-ID on all its connected ports (many). The module may not know on which port the ID is sent. A sink (receiver) module is capable of receiving IDs on its port (one). The sink port identifies the association-ID (AID) of one end of the association (between sender and receiver). The association may be established based on each module discovering the sink AID of the sender in both directions (bi-directional). Both directions may be required for the source signal to get received on a respective sink. The source signal may be sent asynchronously in each direction.

Abstract: A multi-gateway virtual machine that operates multiple gateways. Each gateway acts as an interface between a virtual network and entities outside of the virtual network. Each virtual network has its own address space, which may be overlapping with the address space of other virtual networks, even if the gateways of those virtual networks are operating on the same virtual machine. Accordingly, the principles described herein relate to a virtual machine that can operate thereon multiple gateways, and thus to a multi-gateway virtual machine that services multiple virtual networks.

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

Abstract: A method, integrated system and Active Poster for processing mobile touch transactions. The integration consists of an RFID or other near field communication enabled device which may be standalone, affixed to, or part of a mobile or hand held portable wireless communication device (optionally using a Contact Less (CL) SIM with near field communication capability), a touch sensitive Active Poster also with near field communication capability, an issuer's or mobile network provider's system and application and a host computer with networking capability.

Abstract: Disclosed is Extensible Messaging and Presence Protocol (XMPP) server for sharing and controlling electronic devices located at remote locations. XMPP server receives request notification from client device for establishing communication with host device. XMPP server authenticates client device and host device using XMPP credentials and sends request notification to host device and receive an acceptance notification from the host device for establishing communication with the client device. XMPP server establishes bidirectional secured communication channel between the client device and the host device using an XMPP protocol or a network protocol, over a secured layer protocol and facilitates communication between the client device and the host device over the bidirectional secured communication channel. Client device and host device are connected under secured network and restricted to access each other through firewall restricted boundaries.

Abstract: Disclosed is a method and system for provisioning a device over an Internet of Things (IoT) platform for establishing a bidirectional communication between the device and a system (IoT server). The system may identify a device based on device identification (ID) of the device. The system may further determine whether the device is communicating with the system for the first time or has previously communicated with the system. The system may automatically generate a username and a password for the device for authenticating the user. Post generating the username and the password, the system may transmit the username and the password to the device and an external device. Further, the external device may provide a connection between the device and other devices connected over the IoT based on the username and the password. The device may also create a buddy list by storing the usernames of the other devices.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: A method, integrated system and Active Poster for processing mobile touch transactions. The integration consists of an RFID or other near field communication enabled device which may be standalone, affixed to, or part of a mobile or hand held portable wireless communication device (optionally using a Contact Less (CL) SIM with near field communication capability), a touch sensitive Active Poster also with near field communication capability, an issuer's or mobile network provider's system and application and a host computer with networking capability.

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

Abstract: Redirecting message flows to bypass load balancers. A destination intermediary receives a source-side message that includes a virtual address of a load balancer as a destination, and that is augmented to include a network address of a destination machine as a destination. The destination intermediary determines that a source intermediary should address subsequent network messages that originate from a source machine and that are associated with the same multi-message flow to the destination machine while bypassing the load balancer. The destination intermediary modifies the source-side message so the destination for the source-side message addresses the source machine, and passes the modified source-side message to the destination machine.