Abstract: Discussed herein is a framework that provisions for customized processing for different classes of traffic. A network device in a communication path between a source host machine and a destination host machine extracts a tag from a packet received by the network device. The packet originates at a source executing on the source host machine and whose destination is the destination host machine. The tag set by the source and indicative of a first traffic class to be associated with the packet, the first traffic class being selected by the source from a plurality of traffic classes. The network device determines, based on the tag, that the first traffic class corresponds to a latency sensitive traffic and processes the packet using one or more settings configured at the network device for processing packets associated with the first traffic class.

Abstract: Techniques discussed herein relate to providing in-memory workflow management at an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate as a computing node in a computing cluster of edge devices and implement a hosting environment (e.g., a distributed data plane). A work request can be obtained by an in-memory workflow manager of the edge device. The work request may include an intended state of a data plane resource (e.g., a computing cluster, a virtual machine, etc.). The in-memory workflow manager can determine the work request has not commenced and initialize an in-memory execution thread to execute orchestration tasks to configure a data plane of the computing cluster according to the intended state. Current state data corresponding to the configured data plane may be provided to the user device and eventually displayed.

Abstract: Techniques discussed herein relate to updating an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can execute a first operating system (OS). A manifest specifying files of a second OS to be provisioned to the edge device may be obtained. The manifest may further specify a set of services to be provisioned at the edge device. One or more data files corresponding to a difference between a first set of data files associated with the first OS and a second set of data files associated with the second OS may be identified. A snapshot of the first OS may be generated, modified, and stored in memory of the edge device to configure the edge device with the second OS. The booting order of the edge device may be modified to boot utilizing the second OS.

Abstract: Discussed herein is a framework that provisions for customized processing for different classes of traffic. A network device in a communication path between a source host machine and 5 a destination host machine extracts a tag from a packet received by the network device. The packet originates at a source executing on the source host machine and whose destination is the destination host machine. The tag set by the source and indicative of a first traffic class to be associated with the packet, the first traffic class being selected by the source from a plurality of traffic classes. The network device determines the first traffic class based on the tag extracted from the packet and 10 processes the packet based on the first traffic class.

Abstract: Discussed herein is a framework that provisions for customized processing for different classes of traffic. A network device in a communication path between a source host machine and a destination host machine extracts a tag from a packet received by the network device. The packet originates at a source executing on the source host machine and whose destination is the destination host machine. The tag set by the source and indicative of a first traffic class to be associated with the packet, the first traffic class being selected by the source from a plurality of traffic classes. The network device determines, based on the tag, that the first traffic class corresponds to a bandwidth sensitive traffic and processes the packet using one or more settings configured at the network device for processing packets associated with the first traffic class.

Abstract: Techniques discussed herein relate to providing in-memory workflow management at an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate as a computing node in a computing cluster of edge devices and implement a hosting environment (e.g., a distributed data plane). A work request can be obtained by an in-memory workflow manager of the edge device. The work request may include an intended state of a data plane resource (e.g., a computing cluster, a virtual machine, etc.). The in-memory workflow manager can determine the work request has not commenced and initialize an in-memory execution thread to execute orchestration tasks to configure a data plane of the computing cluster according to the intended state. Current state data corresponding to the configured data plane may be provided to the user device and eventually displayed.

Abstract: Discussed herein are techniques that utilize locality information of host machines included in a cluster network for the execution of graphical processing unit based workloads. For each host machine of a plurality of host machines, locality information for the host machine is stored therein. The locality information for a host machine identifies a rack comprising the host machine. Responsive to receiving a request requesting execution of a workload, one or more host machines of the plurality of host machines are identified as being available for executing the workload. For each of the one or more host machines, the locality information for the host machine is obtained. Further, linkage information of the one or more host machines is identified. The locality information and the linkage information of the one or more host machines is provided in response to the request.

Abstract: Discussed herein are techniques that utilize hierarchical locality information of host machines included in a cluster network for the execution of general workloads. Hierarchical locality information for each host machine of a plurality of host machines is stored. The hierarchical locality information for a host machine identifying, for each locality of a plurality of localities, location information for the locality. Responsive to receiving a request requesting execution of a workload, the hierarchical locality information for the plurality of host machines is obtained and provided (e.g., to a customer) in response to the request.

Abstract: Techniques discussed herein relate to providing in-memory workflow management at an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate as a computing node in a computing cluster of edge devices and implement a hosting environment (e.g., a distributed data plane). A work request can be obtained by an in-memory workflow manager of the edge device. The work request may include an intended state of a data plane resource (e.g., a computing cluster, a virtual machine, etc.). The in-memory workflow manager can determine the work request has not commenced and initialize an in-memory execution thread to execute orchestration tasks to configure a data plane of the computing cluster according to the intended state. Current state data corresponding to the configured data plane may be provided to the user device and eventually displayed.

Abstract: Techniques discussed herein relate to providing composable edge devices. In some embodiments, a user request specifying a set of services to be executed at a cloud-computing edge device may be received by a computing device operated by a cloud computing provider. A manifest may be generated in accordance with the user request. The manifest may specify a configuration for the cloud-computing edge device. Another request can be received specifying the same or a different set of services to be executed at another edge device. Another manifest which specifies the configuration for that edge device may be generated and subsequently used to provision the request set of services on that device. In this manner, manifests can be used to compose the platform to be utilized at any given edge device.

Abstract: Discussed herein is a routing mechanism for graphical processing units (GPUs) that are hosted on several host machines in a cloud environment. For a packet transmitted by a GPU of a host machine and received by a network device, the network device determines an incoming port-link of the network device on which the packet was received. The network devices identifies, based on a GPU routing policy, an outgoing port-link of the network device that corresponds to the incoming port-link. The GPU routing policy is preconfigured prior to receiving the packet and establishes a mapping of each incoming port-link of the network device to a unique outgoing port-link of the network device. The packet is forwarded on the outgoing port-link of the network device.

Abstract: Discussed herein is a routing mechanism for graphical processing units (GPUs) that are hosted on several host machines in a cloud environment. For a packet transmitted by a GPU of a host machine and received by a network device, the network device determines an incoming port-link of the network device on which the packet was received. The network device obtains a flow information associated with the packet, and computes, based on the flow information, an outgoing port-link of the network device in accordance with a hashing algorithm. The hashing algorithm is configured to hash packets received on a particular incoming port-link of the network device to be transmitted on a same outgoing port-link of the network device. The network device forwards the packet on the outgoing port-link of the network device.

Abstract: Techniques discussed herein relate to providing in-memory workflow management at an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate as a computing node in a computing cluster of edge devices and implement a hosting environment (e.g., a distributed data plane). A work request can be obtained by an in-memory workflow manager of the edge device. The work request may include an intended state of a data plane resource (e.g., a computing cluster, a virtual machine, etc.). The in-memory workflow manager can determine the work request has not commenced and initialize an in-memory execution thread to execute orchestration tasks to configure a data plane of the computing cluster according to the intended state. Current state data corresponding to the configured data plane may be provided to the user device and eventually displayed.

Abstract: Techniques are described for implementing a virtual smart network interface card to facilitate data transmission in an edge device providing cloud-computing operations. An edge device can implement a private virtual network that includes a private virtual network data plane. The edge device can execute a virtual machine to be connected to the private virtual network. To establish the connection, the edge device can generate a virtual network interface that includes a first endpoint and a second endpoint and is hosted within the private virtual network data plane. The edge device can associate the first endpoint with the virtual machine and associate the second endpoint with an orchestration module of the private virtual network data plane. The virtual machine can then send a data packet to the orchestration module via the virtual network interface.

Abstract: Techniques discussed herein relate to updating an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate execute a first operating system (OS). A manifest specifying files a second OS to be provisioned to the edge device may be obtained. One or more data files corresponding to a difference between a first set of data files associated with the first OS and a second set of data files associated with the second OS may be identified. A snapshot of the first OS may be generated and stored in memory of the edge device. The edge device can then be configured with the second OS by modifying the snapshot. The booting order of the edge device may be modified to boot utilizing the second OS.

Abstract: Techniques discussed herein relate to providing composable edge devices. In some embodiments, a user request specifying a set of services to be executed at a cloud-computing edge device may be received by a computing device operated by a cloud computing provider. A manifest may be generated in accordance with the user request. The manifest may specify a configuration for the cloud-computing edge device. Another request can be received specifying the same or a different set of services to be executed at another edge device. Another manifest which specifies the configuration for that edge device may be generated and subsequently used to provision the request set of services on that device. In this manner, manifests can be used to compose the platform to be utilized at any given edge device.

Abstract: Techniques are disclosed for migrating one or more services from an edge device to a cloud computing environment. In one example, a migration service receives a request to migrate a first set of services from the edge device to the cloud computing environment. The migration service identifies a hardware profile of a computing device (or devices) of the cloud computing environment that matches the edge device, and then configures the computing device to execute a second set of services that corresponds to the first set of services. The migration service establishes a communication channel between the edge device and the computing device, and then executes a set of migration operations such that the second set of services is configured to execute as the first set of services. The computing device may operate in a virtual bootstrap environment or dedicated region of the cloud computing environment.

Abstract: Techniques are described for implementing a secure enclave within an edge device (e.g., an edge device of a computing cluster of edge devices). In some embodiments, a service enclave comprising a plurality of services can be implemented. The plurality of services can be implemented within respective containers and communicatively connected to one another via a virtual substrate network of the cloud-computing edge device. The virtual substrate network may be dedicated to network traffic between services of the plurality of services. A first service of the enclave may generate and transmit a message to a second service of the enclave for processing. One or more operations may be executed by the second service based on reception of the message.

Abstract: Techniques and apparatus for data networking are described. In one example, a method of queuing Remote Direct Memory Access (RDMA) packets includes receiving a first RDMA packet having a first quality-of-service (QoS) data field; based on a value of the first QoS data field, queueing the first RDMA packet in a first queue of a plurality of queues; receiving a second RDMA packet having a second QoS data field; and based on a value of the second QoS data field, queueing the second RDMA packet in a second queue of the plurality of the queues, the second queue being different than the first queue.

Abstract: Techniques and apparatus for data networking are described. In one example, a method includes receiving a first Layer-2 Remote Direct Memory Access (RDMA) packet which includes a virtual local area network (VLAN) tag and a quality-of-service (QoS) data field; converting the first Layer-2 RDMA packet to a first Layer-3 encapsulated packet; and forwarding the first Layer-3 encapsulated packet to a switch fabric. In this method, the converting includes adding at least one header to the first Layer-2 RDMA packet, where the at least one header includes: a virtual network identifier that is based on information from the VLAN tag, and a QoS value that is based on information from the QoS data field.