Patent classifications
G06F2009/45595
Near-hitless upgrade or fast bootup with virtualized hardware
An embodiment is directed to switchover operations with a virtualized network device in a cloud or remote infrastructure. The virtualized hardware switchover operations may be used to selectively and temporarily provide virtualized control-plane operations to the data-plane of a non-redundant network device undergoing an upgrade or a reboot of its control plane. A non-redundant network device may operate hitless, or near hitless, operation even when its control plane is unavailable.
System and method for distributed orchestration management in network function virtualization
A system and method for orchestrating distributed operations to be executed in a distributed computing system with multiple virtual infrastructures uses a distributed operation descriptor to find any Cloud-Native Network Function (CNF) entry in the distributed operation descriptor. For each found CNF entry, a CNF descriptor is retrieved from a CNF catalog and parsed to find an overridable property for a CNF described in the CNF descriptor for which a property override is defined. Then, a target virtual infrastructure is selected from the multiple virtual infrastructures to perform a lifecycle management operation of the CNF. Instructions are then transmitted to a local operator in the target virtual infrastructure with the property override so that information regarding the CNF is transmitted to a local orchestrator of the target virtual infrastructure to perform the lifecycle management operation of the CNF at the target virtual infrastructure using the property override.
Migration of network file copy operations between host computing devices
A method of migrating a network file copy (NFC) operation from a first host computing device to a second host computing device includes the steps of: transmitting a first request to the first host computing device to execute the NFC operation, wherein the NFC operation comprises transferring data from a shared datastore to another datastore; after transmitting the first request, selecting the second host computing device to complete the NFC operation in place of the first host computing device, and transmitting a second request to the first host computing device to stop executing the NFC operation; after transmitting the second request, detecting a message indicating that the first host computing device completed the copying of a first portion of the data; and in response to the detection of the message, transmitting a third request to the second host computing device to perform the remainder of the NFC operation.
Language interoperable runtime adaptable data collections
Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together. Adaptive data collections may also provide language-independent such that implementation code may be written once and subsequently used from multiple programming languages.
Composable edge device platforms
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.
Throttling CPU utilization by implementing a rate limiter
An approach for a hypervisor to throttle CPU utilization based on a CPU utilization throttling request received for a data flow is presented. A method comprises receiving a request for a CPU utilization throttling. The request is parsed to extract a CPU utilization level and a data flow identifier of the data flow. Upon receiving a data packet that belongs to the data flow identified by the data flow identifier, a packet size of the data packet is determined, and a rate limit table is accessed to determine, based on the CPU utilization level and the packet size, a rate limit for the data packet. If it is determined, based at least on the rate limit, that the CPU utilization level for the data flow would be exceeded if the data packet is transmitted toward its destination, then a recommendation is generated to drop the data packet.
System, method and computer program product for secure Bluetooth cryptography in a virtual mobile device platform
Embodiments are disclosed that allow encrypted data to be sent between a Bluetooth enabled device and a virtual device associated with a corresponding physical device. In particular, a Bluetooth implementation on the physical device may include one or more raw interfaces to facilitate endpoint to endpoint secure Bluetooth cryptography. Using these raw interfaces, an encrypted Bluetooth channel may be established directly between the virtual device and the Bluetooth enabled device using the radio of the physical device, where data may be encrypted and decrypted at an endpoint of the Bluetooth communication channel (such as at the virtual device or the Bluetooth enabled device) and passed through a Bluetooth implementation on the physical device without any additional encryption or decryption being performed on that data.
Network anomaly detection
A cloud network is a complex environment in which hundreds and thousands of users or entities can each host, create, modify, and develop multiple virtual machines. Each virtual machine can have complex behavior unknown to the provider or maintainer of the cloud. Technologies disclosed include methods, systems, and apparatuses to monitor the complex environment to detect network anomalies using machine learning techniques. In addition, techniques to modify and adapt to user feedback are provided allowing the developed models to be tuned for specific use cases, virtual machine types, and users.
Application-specific policies for failover from an edge site to a cloud
Example implementations relate to application-specific policies for failing over from an edge site to a cloud. When an application becomes operational within an edge site, a discovery phase is performed by a local disaster recovery (DR) agent. I/O associated with a workload of the application is monitored. An I/O rate for data replication that satisfies latency characteristics of the application is predicted based on the incoming I/O. Based on results of tests against multiple clouds indicative of their respective RTO/RPO values, information regarding a selected cloud to serve as a secondary system is stored in an application-specific policy. The application-specific policy is transferred to a remote DR agent running in the selected cloud. Responsive to a failover event, infrastructure within a virtualized environment of the selected cloud is enabled to support a failover workload for the application based on the application-specific policy.
Atomic groups for configuring HCI systems
An information handling system may include at least one processor, and a non-transitory memory coupled to the at least one processor. The information handling system may be configured to execute a configuration procedure to set up a plurality of information handling resources of the information handling system, and wherein the configuration procedure includes a plurality of logical groups related to different types of configuration. Each logical group may include one or more atomic groups, each atomic group including a plurality of logically related atomic operations. In response to a failure of a particular atomic operation of a particular atomic group, the information handling system may be configured to roll back the particular atomic operation and allow the configuration procedure to be restarted at a beginning of the particular atomic group.