Patent classifications
H04L41/0856
Model driven process for automated deployment of domain 2.0 virtualized services and applications on cloud infrastructure
A model-driven system automatically deploys a virtualized service, including multiple service components, on a distributed cloud infrastructure. A master service orchestrator causes a cloud platform orchestrator to retrieve a cloud services archive file, extract a cloud resource configuration template and create cloud resources at appropriate data centers as specified. The master service orchestrator also causes a software defined network controller to retrieve the cloud services archive file, to extract a cloud network configuration template and to configure layer 1 through layer 3 virtual network functions and to set up routes between them. Additionally, the master service orchestrator causes an application controller to retrieve the cloud services archive file, to extract a deployment orchestration plan and to configure and start layer 4 through layer 7 application components and bring them to a state of operational readiness.
APPLICATION CONSISTENT NETWORK BACKUP USING THREE PHASE FULL QUORUM
A three-phase full quorum commit method enabling backing up of network devices that do not offer direct hooks in order to have application consistent protection. Devices are verified to be ready to perform a backup, and a condition of reaching and maintaining a full quorum of devices within a maximum time period is required before the system can be backed up. The three phase backup process reduces the chance of changes to network devices from corrupting consistency among the saved states of the different and disparate network devices. Multiple devices of different makes and models participate together as a unified backup as a network partition and all devices are verified as being in a ready state. The device configuration data is moved from device memory to local disk, and can then be tiered to secondary storage.
ACCELERATED NETWORK RECONNECT USING PREVIOUS CONNECTION PARAMETERS
A Wi-Fi device includes a controller coupled to a writeable memory implementing a MAC and PHY layer and to a transceiver. Connection data stored in the writeable memory includes Wi-Fi connection parameters including ≥1 router MAC level information or a most recently utilized (MRU) channel used, and IP addresses including ≥1 of an IP address of the Wi-Fi device, IP address of the MRU router, an IP address of a MRU target server, and an IP address of a network connected device. An accelerated reconnecting to a Wi-Fi network algorithm is implemented by the processor is for starting from being in a network disconnected state, establishing current connection parameters for a current Wi-Fi network connection using the Wi-Fi connection parameters for at least one MAC layer parameter for the MAC layer.
HIGHLY SCALABLE CONTAINER NETWORK INTERFACE OPERATION TO REDUCE STARTUP OVERHEAD OF FUNCTIONS
Systems and methods for providing a container network interface (CNI) specification that has been modified with a set of annotations, a set of operations, and a set of policies to provide network configuration reuse, network configuration replication, and database management (garbage collection) functionality are described. In response to receiving a request to initiate a function, whether the function is to be reused or replicated may be determined. In response to determining that the function is to be reused, calling a container network interface (CNI) plugin with a first operation that decouples database functions from network functions, so that the database can cache and reuse a network configuration generated for the function. In response to determining that the function is to be replicated, calling the CNI plugin with a second operation to create the network configuration and generate and store a template of the network configuration in the database.
Procedure for managing a failure in a network of nodes based on a local strategy
Disclosed is a failure management method in a network of nodes, including, for each considered node: first, a step of locally saving the state of this considered node, to a storage medium for this node in question. Then, if the considered node has failed, retrieving the local backup of the state of this considered node, by redirecting the link between the considered node and its storage medium to connect this storage medium to an operational node other than the considered node, this operational node already in the process of carrying out this calculation, the local backups of these considered nodes, used for the retrieving steps being coherent with each other so as to correspond to the same state of calculation. If a considered node failed, returning this local backup for this considered node to a new additional node added to the network at the time of the failure.
Automated validation of power topology via power state transitioning
Systems and techniques that facilitate automated validation of power topology are provided. In various embodiments, a control component can transmit a transition command to a power-distribution node of a data center, wherein the transition command can cause an outlet of the power-distribution node to transition between power states. In various aspects, a verification component can verify that a power-consumption node of the data center is connected to the outlet by comparing a pre-transition power characteristic of the power-consumption node with a post-transition power characteristic of the power-consumption node.
HYBRID SOFTWARE-DEFINED NETWORKING AND MOBILE AD-HOC NETWORKING ROUTING IN MESH NETWORKS
A network controller is configured to cause a network to implement a primary network configuration of a network and a secondary network configuration as a backup to the primary network configuration. The network controller may be configured to receive information from a plurality of nodes of a network and information related to the client data to be transmitted through the network. Based on the node information, the network controller is configured to determine available nodes and possible links in the network and then determine a topology of the network. The primary network configuration is determined based on the topology. The network controller then sends instructions to the plurality of nodes of the network to implement the primary network configuration and to switch to a secondary network configuration where a failure of the primary network configuration occurs, wherein the secondary network configuration implements mobile ad-hoc networking in the determined topology.
MANAGING CONFIGURATIONS OF MOBILE DEVICES ACROSS MOBILITY CONFIGURATION ENVIRONMENTS
Embodiments described herein provide for systems and methods for managing configurations of mobile devices. A server may receive an instruction inputted via a graphical control to translate configurations from a first device environment to a second device environment. The server may identify, via an interface, a resource accessible by a first plurality of mobile devices in the first device environment based on the instruction. The server may determine, from the first device environment, a first profile identifying a first plurality of attributes defining a first configuration for the first plurality of mobile devices. The server may generate, using the first profile, a second profile identifying a second plurality of attributes defining a second configuration for a second plurality of mobile devices in the second device environment. The server may transmit, via the interface, the second profile to the second plurality of mobile devices.
Cloud Data Ingestion System
A computing system identifies a plurality of virtualization elements executing on a cloud computing environment. The computing system retrieves a first set of data related to software resources executing across the plurality of virtualization elements. The computing system retrieves a second set of data related to hardware resources associated with the plurality of virtualization elements. The computing system retrieves delta updates to the first set of data, wherein the delta updates are retrieved in real-time. The computing system generates a first database. The first database includes the first set of data related to the software resources, the second set of data related to the hardware resources associated with the plurality of virtualization elements, and the delta updates. The computing system generates a configuration management database hosted by a configuration management database system.
Transmission system, device management server, fault management method, and program
[Problem] A transmission system, an apparatus management server, a failure management method, and a program enabling the cause of a failure associated with a silent change of an article to be swiftly identified are provided. [Solution] An apparatus management server 100 of a transmission system includes a collection unit configured to collect history information on an introduction instance of articles to an optical transmission apparatus 10 and an information analysis unit 130 configured to visualize and display, based on the history information collected, a graph in which a starting date of use for each of the articles is associated with the number of introductions of the article.