G06F2009/45562

VIRTUAL MACHINE MIGRATION METHOD AND RELATED DEVICE

Embodiments of this application disclose a virtual machine migration method. One example method includes: indicating, by a controller, a proxy virtual machine to mount a volume; replacing, by using the proxy virtual machine, a driver of an original platform in the volume with a driver of a target platform; and then, mounting a replaced volume to a target virtual machine.

HITLESS CONTAINER UPGRADE WITHOUT AN ORCHESTRATOR

Systems, methods, and computer-readable media are disclosed for performing a hitless upgrade of executable code in the absence of an orchestrator or other upgrade manager. A mechanism is disclosed that utilizes containers to update software functionality, features, or the like without interrupting a service provided by a container and without relying on an orchestrator or other upgrade manager to coordinate the upgrade process. State information indicative of a current state of module(s) within a container is maintained in an external data store such as a state database. A hand-off from a current container to a new container that updates module code/functionality of the current container can be initiated upon determining that a state metric calculated by the old container at a future timestamp matches a state metric independently calculated by the new container at the same timestamp.

VIRTUAL ACCELERATORS IN A VIRTUALIZED COMPUTING SYSTEM
20230017676 · 2023-01-19 ·

An example method of virtualizing a hardware accelerator in a host cluster of a virtualized computing system includes: commanding, at an initiator host in the host cluster, a programmable expansion bus device to reconfigure as a virtual accelerator based on specifications of a hardware accelerator in a target host of the host cluster; executing, in the programmable expansion bus device, software to emulate the virtual accelerator as connected to an expansion bus of the initiator host; receiving, at the programmable expansion bus device, compute tasks from an application executing in the initiator host; and sending, to the target host, the compute tasks for processing by the hardware accelerator.

CONTAINERIZED FIRMWARE SERVICES

Temporary firmware is provided as cloud services. Different temporary firmware containers are downloaded via a communications network. A light-weight operating system launches and executes the temporary firmware containers during a boot operation, POST operation, or other scheme. The temporary firmware containers thus detect and perhaps resolve POST errors. The light-weight operating system may also download a full-service/resource operating system. A second or subsequent boot operation may be performed, but control is ceded to the full-service/resource operating system. Multiple firmware tenants may thus be temporarily downloaded to a bare metal machine to support POST error detection activities. Advanced OS serviceability, diagnostics, and other containerized firmware may thus be quickly and simply launched without requiring the excessive time and difficulties of using the full-service/resource operating system.

DEPLOYING A CLOUD INSTANCE OF A USER VIRTUAL MACHINE

An instruction to generate a cloud instantiation of a secondary storage system is provided. One or more secondary storage clusters are virtually rebuilt in the cloud instantiation of the secondary storage system. A new cloud instance of a user virtual machine is deployed based on at least a portion of data stored in the one or more rebuilt secondary storage clusters of the cloud instantiation of the secondary storage system. A version of at least the portion of the data of the one or more rebuilt secondary storage clusters is provided to a cloud deployment server.

SIDECAR-BASED INTEGRATION CAPABILITIES FOR CONTAINERIZED APPLICATIONS
20230221981 · 2023-07-13 ·

Methods and systems for improved integration functions for applications are provided. In one embodiment, a method is provided that includes receiving a request to execute an application. The request may specify a primary container image for the application and a secondary container image for an integration function used by the application. A primary container may be created for execution of the primary container image and a secondary container image separate from the primary container may be created for execution of the secondary container image. The primary and secondary containers may be executed to implement the application.

Automated Deployment of Control Nodes at Remote Locations
20230224212 · 2023-07-13 ·

A control node can be automatically deployed at a remote location according to some examples described herein. In one example, a system can automatically set up a control node at a remote location by performing various operations. The operations can include interacting with the remote location to deploy an instance of the control node at the remote location. The operations can include providing a configuration script to the remote location for use by the instance in configuring one or more managed nodes. The operations can include providing connection information to the remote location for use by the instance in establishing a network connection to the one or more managed nodes. The system can then initiate a configuration process in which the control node establishes the network connection to the one or more managed nodes and then configures the one or more managed nodes in accordance with the configuration script.

EFFICIENT MASS VIRTUAL MACHINE (VM) CLONING

In one set of embodiments, during an initial pre-copying phase, copies of the virtual disks of a VM or VM template can be distributed across one or more datastores, prior to the start of any cloning. This effectively seeds each datastore with a disk pool comprising a certain number of copies of the VM/VM template's virtual disks. Then, at the time of receiving a user request to create k clones from the VM/VM template, up to k copies of the VM/VM template's virtual disks that already reside in the disk pools of one or more target datastores can be moved from those disk pools to the clones' home folders on the target datastores, thereby reducing or eliminating the need to create brand new copies of the virtual disks on demand.

MACHINE LEARNING BASED PREDICTIONS OF UPGRADE TESTING OUTCOMES FOR INFORMATION TECHNOLOGY ENVIRONMENTS
20230221973 · 2023-07-13 ·

A method and system for machine learning based predictions of upgrade testing outcomes for information technology (IT) environments. At least with respect to computing, an upgrade may entail the replacement of a product—in the form of hardware, software, and/or firmware—with a newer or better version, which may serve to bring the product up to date, improve the characteristic(s) of the product, and/or resolve any issue(s) inflicting the product. Further, through the process of upgrade testing, an upgrade may be assessed to determine its impact on an operability of varying environments following application of the upgrade thereon. Moreover, each environment may reflect a different history of product upgrades that had been applied thereon prior to the upgrade being tested. The disclosed method and system, accordingly, propose a framework directed to ascertaining the post-upgrade outcomes of actual IT environments using machine learning applied to post-upgrade outcomes of simulated IT environments.

HYPERVISOR ASSISTED VIRTUAL MACHINE CLONE AUTO-REGISTRATION WITH CLOUD

A method for automatically reregistering a clone virtual machine with a cloud security monitoring service is provided. The method generally includes detecting a connection between a cloud agent running in a virtual machine on a host and a hypervisor module on the host. In response to detecting the connection, the cloud agent queries the hypervisor module for one or more first identifiers of the virtual machine. The method generally includes checking a database, by the cloud agent, for one or more second identifiers stored in the database matching the one or more first identifiers received from the hypervisor module and, based on finding no second identifiers stored in the database matching the one or more first identifiers, sending a request to the cloud security monitoring service to register the virtual machine with the cloud security monitoring service.