Patent classifications
H04L41/122
Methods, systems and apparatus for dynamically extending a cloud management system by adding endpoint adapter types
Methods, apparatus and articles of manufacture for dynamically extending a cloud management system by adding endpoint adapter types are disclosed. An example cloud management system includes: an interface to communicate with an external device; a host to manage requests and allocate resources through one or more virtual machines; and an endpoint registry to include an endpoint adapter and metadata defining the endpoint adapter, the endpoint adapter to specify communication between at least one of the host or the external device and an endpoint. In the example cloud management system, the host is to at least enable, via the interface, the external device to access the endpoint registry a) to register an endpoint adapter configuration with the endpoint registry and b) to retrieve the endpoint adapter configuration from the endpoint registry.
Methods, systems and apparatus for dynamically extending a cloud management system by adding endpoint adapter types
Methods, apparatus and articles of manufacture for dynamically extending a cloud management system by adding endpoint adapter types are disclosed. An example cloud management system includes: an interface to communicate with an external device; a host to manage requests and allocate resources through one or more virtual machines; and an endpoint registry to include an endpoint adapter and metadata defining the endpoint adapter, the endpoint adapter to specify communication between at least one of the host or the external device and an endpoint. In the example cloud management system, the host is to at least enable, via the interface, the external device to access the endpoint registry a) to register an endpoint adapter configuration with the endpoint registry and b) to retrieve the endpoint adapter configuration from the endpoint registry.
Creating a global Reinforcement Learning (RL) model from subnetwork RL agents
Methods are provided for recommending actions to improve operability of a network. In one implementation, a method includes acknowledging a plurality of subnetworks in a whole network, each subnetwork including multiple nodes and being represented by a tunnel group having multiple end-to-end tunnels through the subnetwork. The method also includes selecting a first group of subnetworks from the plurality of subnetworks and generating a Reinforcement Learning (RL) agent for each subnetwork of the first group. Each RL agent is based on observations of end-to-end metrics of the end-to-end tunnels of the respective subnetwork. The observations are independent of specific topology information of the subnetwork. Also, the method includes training a global model based on the RL agents of the first group of subnetworks and applying the global model to an Action Recommendation Engine (ARE) configured for recommending actions that can be taken to improve a state of the whole network.
DISTRIBUTED SOFTWARE-DEFINED NETWORKING (SDN) CONTROL PLANE FRAMEWORK
A system includes a network of multiple network domains, each network domain includes a software defined network (SDN) controller. Each SDN controller includes a network interface circuitry, a processor and a memory. The network interface circuitry provides a communicative coupling with at least one domain of the multiple network domains. The memory includes instructions that when executed by the processor, performs a network update comprising adding links, subtracting links or reporting a status of links in at least one network domain upon receiving a network update request, and performs sending and receiving the network update request to a second SDN controller, where the network update request is part of real-time publish/subscribe protocol, the sending network update request includes a publish message having a specified topic and a set of QoS attributes, and the receiving a network update request includes subscribing to the specified topic and the set of QoS attributes.
DISTRIBUTED SOFTWARE-DEFINED NETWORKING (SDN) CONTROL PLANE FRAMEWORK
A system includes a network of multiple network domains, each network domain includes a software defined network (SDN) controller. Each SDN controller includes a network interface circuitry, a processor and a memory. The network interface circuitry provides a communicative coupling with at least one domain of the multiple network domains. The memory includes instructions that when executed by the processor, performs a network update comprising adding links, subtracting links or reporting a status of links in at least one network domain upon receiving a network update request, and performs sending and receiving the network update request to a second SDN controller, where the network update request is part of real-time publish/subscribe protocol, the sending network update request includes a publish message having a specified topic and a set of QoS attributes, and the receiving a network update request includes subscribing to the specified topic and the set of QoS attributes.
DISTRIBUTED NODE DISCOVERY AND OVERLAY PATH MANAGEMENT ON A DATA COMMUNICATION NETWORK
An initial provisioning by a management plane of the SD-WAN is received from a centralized SD-WAN gateway with static path overlay between the network edge device on a local LAN and the centralized SD-WAN gateway. At runtime, intelligent decision are made about which overlay path to select and when for the new flow over a control plane of the SD-WAN, based on the topology of the remote network edge and the local SDWAN policy, and to build the selected overlay path.
Virtual IP support for bare metal cloud infrastructures
Disclosed is an improved approach for managing floating/virtual IP addresses in a virtualization system. Where a bare metal cloud provider does not provide adequate facilities to implement broadcast operations, the approach would capture broadcast packets, and from the captured packets, generate calls to the cloud provider to implement configuration changes to reflect the changes desired by the broadcast packets.
Secure aggregation of IoT messages
A system includes processing circuitry; and a memory device including instructions embodied thereon, wherein the instructions, which when executed by the processing circuitry, configure the processing circuitry to perform operations comprising: accessing input data, at an aggregator node, the input data including sensor data from a plurality of sensor nodes, each sensor data having a respective signature; validating the sensor data by using respective cryptographic hash functions on the sensor data and evaluating the respective result using the respective signature; performing an aggregation function on the sensor data to produce aggregate data; executing a hash function on the aggregate data to produce a hash value for the aggregate data; bundling the sensor data, respective signatures of the sensor data, aggregate data, and hash value for the aggregate data in a data structure; and exposing the data structure to subscriber nodes on the IoT network.
Techniques for preventing concurrent execution of declarative infrastructure provisioners
Techniques for preventing concurrent execution of an infrastructure orchestration service are described. Worker nodes can receive instructions, or tasks, for deploying infrastructure resources and can provide heartbeat notifications to scheduler nodes, also considered a lease. A signing proxy can track the heartbeat notifications sent from the worker nodes to the scheduler node. The signing proxy can receive requests corresponding to a performance of the tasks assigned to the worker nodes. The signing proxy can determine whether the lease between each worker node and the scheduler is valid. If the lease is valid, the signing proxy may make a call to services on behalf of the worker node, and if the lease is not valid, the signing proxy may not make a call to services on behalf of the worker node. Instead, the signing proxy may cut off all outgoing network traffic, blocking access of the worker node to services.
Routing visualization user interface
A configuration of a service of a cloud computing system is rendered in a user interface of an electronic display, according to a discovery chain generated by a networking tool using a service discovery function to establish the configuration. The configuration includes one or more of a router, a splitter, and/or a resolver, each having one or more configuration files that are represented as a graphical element within a graphical representation of the one or more of the router, the splitter, and/or the resolver. The configuration further includes data traffic routes between pairs of the configuration files, each being represented in the UI as a line between each pair of configuration files, where each line is rendered in the UI so as to avoid crossing over any graphical element that represents a configuration file.