H04L47/781

Allocating additional bandwidth to resources in a datacenter through deployment of dedicated gateways

Some embodiments provide policy-driven methods for deploying edge forwarding elements in a public or private SDDC for tenants or applications. For instance, the method of some embodiments allows administrators to create different traffic groups for different applications and/or tenants, deploys edge forwarding elements for the different traffic groups, and configures forwarding elements in the SDDC to direct data message flows of the applications and/or tenants through the edge forwarding elements deployed for them. The policy-driven method of some embodiments also dynamically deploys edge forwarding elements in the SDDC for applications and/or tenants after detecting the need for the edge forwarding elements based on monitored traffic flow conditions.

Systems and methods for integrating network switch management with computing resource management

A networking system may include a switch coupled to a computing resource. A resource management system may control the computing resource. A controller may be coupled to the switch. The controller may include a resource management interface that is coupled to the resource management system via a communications link. The resource management interface may receive computing resource information for the computing resource via the communications link. The controller may provide control data to the switch to update a cloud network for the computing resource based on the received computing resource information.

Adaptive throughput for user equipment communicating via a managed Wi-Fi service network

A managed Wi-Fi service network device can receive, from a cellular network device, an allowable throughput rate at which a user equipment is authorized to communicate via a managed Wi-Fi service network. Based on the allowable throughput rate, the managed Wi-Fi service network device can monitor a communication rate of the user equipment via the managed Wi-Fi service network. In response to the user equipment communicating via the managed Wi-Fi service network at a rate that exceeds the allowable throughput rate, the managed Wi-Fi service network device can facilitate reducing the communication rate of the user equipment. Also, a user equipment can receive from a cellular network device an allowable throughput rate at which the user equipment is authorized to communicate via the managed Wi-Fi service network. The UE can communicate via the managed Wi-Fi service network at a communication rate that does not exceed the allowable throughput rate.

CLUSTER CAPACITY MANAGEMENT FOR HYPER CONVERGED INFRASTRUCTURE UPDATES

Disclosed are various implementations of cluster capacity management for infrastructure updates. In some examples, cluster hosts for a cluster can be scheduled for an update. A component of a datacenter level resource scheduler can analyze cluster specific resource usage data to identify a cluster scaling decision for the cluster. The datacenter level resource scheduler transmits an indication that the resource scheduler is successfully invoked. Cluster hosts can then be updated.

Multi-tier resource, subsystem, and load orchestration

Electronic communications received via a network from a plurality of electronic devices may include signals of device interactions or data changes that correspond to process performances by process-performing resources, signals of conditions of loads, or signals of processes associated with the process-performing resources and the loads. Data composites may be formed from the electronic communications, with data portions collected and mapped to resource profile records and load profile records that may be updated with the collected data portions. For each load, at least one of the one or more resource profile records and/or the one or more load profile records may be used to map the process-performing resources to the load. Content nodes may be linked in a network of content nodes, including respective linked content, resource specifications or load specifications. Access to the network of content nodes may be allowed via a control interface.

System for automated cross-network monitoring of computing hardware and software resources

A system is provided for automated cross-network monitoring of computing hardware and software status. In particular, the system may track the status of various computing resources using process automation-based operations to simulate calls made by users to the various resources that the users are authorized to access. Based on said operations, the system may assess whether the authorized pathways to the resources and/or their respective components are properly functioning by capturing information regarding the resource, its associated components, and the current status of the resource. The results of these operations may be aggregated to provide an overview of which resources and/or systems are functioning and which are not. In this way, the system may provide a detailed view of the statuses of the individual resources and components within an entity's complex computing network.

Cluster capacity management for hyper converged infrastructure updates

Disclosed are various implementations of cluster capacity management for infrastructure updates. In some examples, cluster hosts for a cluster can be scheduled for an update. A component of a datacenter level resource scheduler can analyze cluster specific resource usage data to identify a cluster scaling decision for the cluster. The datacenter level resource scheduler transmits an indication that the resource scheduler is successfully invoked. Cluster hosts can then be updated.

CENTRALIZED LOAD BALANCER WITH WEIGHTED HASH FUNCTION
20180007126 · 2018-01-04 ·

A method, apparatus, and machine readable storage medium is disclosed for balancing loads among a plurality of virtual machines (VMs) from a central dispatcher, wherein the dispatcher receives data packets and maps the data packets to VMs selected from the plurality of VMs, using a weighted hash function, having an associated weighting for each VM and forwarding each packet to a VM accordingly, wherein a load balancer decrements a weighting for a VM, responsive to an indication of the load on the VM exceeding a first load threshold. Weightings can correspond to a number of bins associated with each VM. Weightings are adjusted in response to receiving invite and disinvite messages from the VMs, representing their respective loads.

Grouping resource metadata tags
11711314 · 2023-07-25 · ·

A system for applying metadata tags based on metadata tag groups is described. The system includes a plurality of compute nodes configured to provide a plurality of computing resources for clients of a provider network and a resource tag manager for the provider network. The resource tag manager is configured to receive, from a first client of an account of the provider network, a creation request to establish a resource attribute group comprising a plurality of resource keys and a plurality of resource values, wherein respective metadata keys correspond to respective resource values. The resource tag manager may receive, from a second client of the account, an application request to apply the resource attribute group to a computing resource and apply the plurality of resource keys and the plurality of resource values to metadata maintained for the computing resource.

Dynamic endpoint resources discovery in Kubernetes clusters via stable URI locator for workflow services
11711315 · 2023-07-25 · ·

A method of performing resource discovery includes receiving, by a processing device, a resource identifier describing a resource of a computing cluster to be accessed by a workflow application. The method also includes sending the resource identifier to a container orchestration API to determine whether an endpoint exists for the resource. The method also includes, in response to an indication from the container orchestration API that the endpoint exists, receiving, from the container orchestration API, endpoint details used to access the resource, identifying an endpoint address based on the endpoint details, and binding the endpoint address to the resource in a runtime version of the workflow application to enable the workflow application to access the resource.