Abstract: Bootstrapping a microservices container registry. A computing system node receives an installation package. The receiving computing system node bootstraps an initial invocation of the microservice by first installing a local container registry from the installation package and then by installing the microservice from the installation package. The installation package contains additional components that can be extracted, installed and invoked by executing the microservice at the computing system node after extracting from the local container registry. The installation package is generated by any node of the computing system and contains code corresponding to infrastructure microservices that are installed before invoking microservices that depend on the infrastructure. Temporary domain name services are installed from the installation package at a node-local IP address. The temporary domain name services are switched over to a different domain name service at a different IP address.

Abstract: Bootstrapping a microservices container registry. A computing system node receives an installation package. The receiving computing system node bootstraps an initial invocation of the microservice by first installing a local container registry from the installation package and then by installing the microservice from the installation package. The installation package contains additional components that can be extracted, installed and invoked by executing the microservice at the computing system node after extracting from the local container registry. The installation package is generated by any node of the computing system and contains code corresponding to infrastructure microservices that are installed before invoking microservices that depend on the infrastructure. Temporary domain name services are installed from the installation package at a node-local IP address. The temporary domain name services are switched over to a different domain name service at a different IP address.

Abstract: Methods, systems and computer program products for configuring microservices platforms in one or more computing clusters. In one of the computing clusters, a request to instantiate a microservice platform is received, wherein the request is received in a computing cluster having a first node and a second node, and wherein the first node and second node comprise a first virtualized storage controller and a second virtualized storage controller, respectively. The storage controllers each manage their respective storage pools comprising local storage devices. A first microservice manager is deployed on the first node and a second microservice manager is deployed on the second node.

Abstract: Methods, systems and computer program products for distributed computing systems. Techniques for dynamic service location discovery operate in environments having a first computing system that hosts a client and a second computing system that hosts a service. A service discovery request is transmitted from the first computing system to access a service that is hosted at the second computing system. An IP address corresponding a next IP hop on a route to the IP address of the service is resolved. After traversing the next IP hop, the second computing system that hosts the service receives the service discovery request and responds with an IP address of the service. In accordance with these techniques, the determination of the IP address of the service is performed at a computing system that is different from the first computing system.

Abstract: The present disclosure is directed towards systems and methods of maintaining a session via an intermediary device. A first device intermediary to a client and a plurality of servers receives a packet of a session. The packet of the session includes application protocol data and application session metadata used to maintain a state of an application accessed via the session. The first device marks a session state of the session to an update state. The first device determines that a second device intermediary to the client and the plurality of servers is in a ready state and the session state of the session is in the update state. The first device forwards the application protocol data and the application session metadata of the packet to the second device to maintain, on the second device, the same state of the application accessed via the session provided by the first device.

Abstract: Methods, systems and computer program products for configuring microservices platforms in one or more computing clusters. In one of the computing clusters, a request to instantiate a microservice platform is received, wherein the request is received in a computing cluster having a first node and a second node, and wherein the first node and second node comprise a first virtualized storage controller and a second virtualized storage controller, respectively. The storage controllers each manage their respective storage pools comprising local storage devices. A first microservice manager is deployed on the first node and a second microservice manager is deployed on the second node.

Abstract: Bootstrapping a microservices container registry. A computing system node receives an installation package. The receiving computing system node bootstraps an initial invocation of the microservice by first installing a local container registry from the installation package and then by installing the microservice from the installation package. The installation package contains additional components that can be extracted, installed and invoked by executing the microservice at the computing system node after extracting from the local container registry. The installation package is generated by any node of the computing system and contains code corresponding to infrastructure microservices that are installed before invoking microservices that depend on the infrastructure. Temporary domain name services are installed from the installation package at a node-local IP address. The temporary domain name services are switched over to a different domain name service at a different IP address.

Abstract: Methods, systems and computer program products for configuring microservices platforms in one or more computing clusters. In one of the computing clusters, a request to instantiate a microservice platform is received, wherein the request is received in a computing cluster having a first node and a second node, and wherein the first node and second node comprise a first virtualized storage controller and a second virtualized storage controller, respectively. The storage controllers each manage their respective storage pools comprising local storage devices. A first microservice manager is deployed on the first node and a second microservice manager is deployed on the second node.

Abstract: Methods, systems and computer program products for distributed computing systems. Techniques for dynamic service location discovery operate in environments having a first computing system that hosts a client and a second computing system that hosts a service. A service discovery request is transmitted from the first computing system to access a service that is hosted at the second computing system. An IP address corresponding a next IP hop on a route to the IP address of the service is resolved. After traversing the next IP hop, the second computing system that hosts the service receives the service discovery request and responds with an IP address of the service. In accordance with these techniques, the determination of the IP address of the service is performed at a computing system that is different from the first computing system.

Abstract: The present disclosure is directed towards systems and methods of maintaining a session via an intermediary device. A first device intermediary to a client and a plurality of servers receives a packet of a session. The packet of the session includes application protocol data and application session metadata used to maintain a state of an application accessed via the session. The first device marks a session state of the session to an update state. The first device determines that a second device intermediary to the client and the plurality of servers is in a ready state and the session state of the session is in the update state. The first device forwards the application protocol data and the application session metadata of the packet to the second device to maintain, on the second device, the same state of the application accessed via the session provided by the first device.

Abstract: The present disclosure is directed towards systems and methods of maintaining a session via an intermediary device. A first device intermediary to a client and a plurality of servers receives a packet of a session. The packet of the session includes application protocol data and application session metadata used to maintain a state of an application accessed via the session. The first device marks a session state of the session to an update state. The first device determines that a second device intermediary to the client and the plurality of servers is in a ready state and the session state of the session is in the update state. The first device forwards the application protocol data and the application session metadata of the packet to the second device to maintain, on the second device, the same state of the application accessed via the session provided by the first device.

Abstract: The present disclosure is directed towards systems and methods for measuring round trip time (RTT) in network devices between the device and an endpoint. A network device may be deployed as an intermediary to provide many security and visibility functions. For measuring the server side RTT between the network device and host, the intermediary device identifies the packet that has been sent by the client when it initiated the RTT measurement. The network device remembers the moment T1 when it sees this packet. The host (e.g., the server) will respond to this with a packet that contains the response. The intermediary device remembers the moment T2 when it sees this response. Server side RTT is calculated by the network device as T2?T1. For measuring the client side RTT the network device and client, the intermediary device identifies the packet that the host sends to initiate measurement of RTT.

Abstract: The present disclosure is directed to systems and methods for controlling delivery of a resource. An intermediary device may establish a connection to deliver a resource hosted on at least one server to a client using a remoting protocol. The remoting protocol may define one or more channels in the connection for delivering or enabling one or more features of the resource to the client. The device may identify the one or more channels, and may identify the one or more features of the resource. The device may determine a policy for controlling access of the client to at least a first feature of the resource. The device may control access of the client to the first feature by modifying a first channel of the one or more channels according to the determined policy.

Abstract: The present disclosure is directed towards systems and methods routing network packets between multi-core intermediaries. A processor of a plurality of processors on a client-side intermediary device may receive a packet from a client device. The processor may be identified by a core identifier. The processor may calculate a first set of source port addresses based on a first key and the core identifier. The processor may identify a target server-side intermediary device and a target processor based on data received with the packet or metadata received from the target server-side intermediary device. The processor may calculate a second set of port addresses based on a second key and the target core identifier. The processor may identify a port address common to both the first set and second set of port addresses. The processor may replace the original source port address in the packet with the identified port address.

Abstract: The present disclosure is directed to systems and methods for controlling delivery of a resource. An intermediary device may establish a connection to deliver a resource hosted on at least one server to a client using a remoting protocol. The remoting protocol may define one or more channels in the connection for delivering or enabling one or more features of the resource to the client. The device may identify the one or more channels, and may identify the one or more features of the resource. The device may determine a policy for controlling access of the client to at least a first feature of the resource. The device may control access of the client to the first feature by modifying a first channel of the one or more channels according to the determined policy.

Abstract: The present disclosure is directed to systems and methods for controlling delivery of a resource. An intermediary device may establish a connection to deliver a resource hosted on at least one server to a client using a remoting protocol. The remoting protocol may define one or more channels in the connection for delivering or enabling one or more features of the resource to the client. The device may identify the one or more channels, and may identify the one or more features of the resource. The device may determine a policy for controlling access of the client to at least a first feature of the resource. The device may control access of the client to the first feature by modifying a first channel of the one or more channels according to the determined policy.

Abstract: The present disclosure is directed towards systems and methods for associating multiple transport layer hops between a client and a server. A first intermediary device may receive a request for a transport layer connection between the client and the server. The first intermediary device may generate a unique identifier to identify a connection chain between the client and the server across a plurality of transport layer connections via the plurality of devices. The first intermediary device may set a hop count to a number of hops that the first device is between the client and the server. The first intermediary device may forward information about the unique identifier and the hop count to a next device of the plurality of devices.

Abstract: The present disclosure is directed towards systems and methods routing network packets between multi-core intermediaries. A processor of a plurality of processors on a client-side intermediary device may receive a packet from a client device. The processor may be identified by a core identifier. The processor may calculate a first set of source port addresses based on a first key and the core identifier. The processor may identify a target server-side intermediary device and a target processor based on data received with the packet or metadata received from the target server-side intermediary device. The processor may calculate a second set of port addresses based on a second key and the target core identifier. The processor may identify a port address common to both the first set and second set of port addresses. The processor may replace the original source port address in the packet with the identified port address.

Abstract: The present disclosure is directed towards systems and methods of maintaining a session via an intermediary device. A first device intermediary to a client and a plurality of servers receives a packet of a session. The packet of the session includes application protocol data and application session metadata used to maintain a state of an application accessed via the session. The first device marks a session state of the session to an update state. The first device determines that a second device intermediary to the client and the plurality of servers is in a ready state and the session state of the session is in the update state. The first device forwards the application protocol data and the application session metadata of the packet to the second device to maintain, on the second device, the same state of the application accessed via the session provided by the first device.

Abstract: The present disclosure is directed towards systems and methods for associating multiple transport layer hops between a client and a server. A first intermediary device may receive a request for a transport layer connection between the client and the server. The first intermediary device may generate a unique identifier to identify a connection chain between the client and the server across a plurality of transport layer connections via the plurality of devices. The first intermediary device may set a hop count to a number of hops that the first device is between the client and the server. The first intermediary device may forward information about the unique identifier and the hop count to a next device of the plurality of devices.