Abstract: An example method of checking compatibility of a guest cluster executing as a virtual extension of a host cluster having an orchestration control plane managing the guest cluster, the host cluster being part of a software defined data center (SDDC), is described.

Abstract: Method, device, and storage medium for processing a driver on a terminal device side are provided. A method includes obtaining connection information between a peripheral device corresponding to the driver and a terminal device; determining, according to the connection information, driver installation options capable of successfully installing the driver; and displaying the driver installation options capable of successfully installing the driver.

Abstract: An asynchronous method is implemented in a manner that reduces the amount of runtime overhead needed to execute the asynchronous method. The data elements needed to suspend an asynchronous method to await completion of an asynchronous operation, to resume the asynchronous method at a resumption point, and to provide a completion status of the caller of the asynchronous method are consolidated into one or two reusable objects. An asynchronous method may be associated with a distinct object pool of reusable objects. The size of a pool and the total size of all pools can be configured statically or dynamically based on runtime conditions.

Abstract: A method includes identifying a source virtual machine to be migrated from a source domain to a target domain, extracting file-in-use metadata and shared asset metadata from virtual machine metadata of the source virtual machine, and copying one or more files identified in the file-in-use metadata to a target virtual machine in the target domain. For each of one or more shared assets identified in the shared asset metadata, the method further includes (a) determining whether or not the shared asset already exists in the target domain, (b) responsive to the shared asset already existing in the target domain, updating virtual machine metadata of the target virtual machine to specify the shared asset, and (c) responsive to the shared asset not already existing in the target domain, copying the shared asset to the target domain and updating virtual machine metadata of the target virtual machine to specify the shared asset.

Abstract: Some examples can accurately determine a status of a software update across a number of development system components. In some examples, a method may involve receiving a software update comprising a set of computer-executable instructions and a reference to a location at which a status chain is to be stored. The method may also involve, in response to receiving the software update, performing at least one software development action with respect to the software update by executing a software development component among a plurality of software development components. The method may further involve determining a status of the software update based on performance of the at least one software development action. And the method may involve automatically causing a block to be added to the status chain at least in part by interfacing with the location, the block indicating the status of the software update and the software development component.

Abstract: Embodiments disclosed herein provide systems, methods, and computer readable media for container based application reification. In a particular embodiment, an application reification system is provided including one or more computer readable storage media and a processing system operatively coupled with the one or more computer readable storage media. The application reification system further includes program instructions stored on the one or more computer readable storage media that, when read and executed by the processing system, direct the processing system to preserve a version of application data at a first time and a configuration of an application at the first time. At a second time subsequent to the first time, the program instructions direct the processing system to create a template for a container containing the application in the configuration and a pointer to the version of the application data in a secondary storage repository.

Abstract: A virtual machine management service obtains a request to instantiate a virtual machine image (VMI) to implement a virtual network function (VNF). The request specifies a set of processor requirements corresponding to instantiation of the VMI. In response to the request, the service identifies, from a server comprising a set of processor cores, available processor capacity. The service determines, based on the available processor capacity and the set of processor requirements, whether to instantiate the VMI on to a subset of processor cores of the server. Based on this determination, the service instantiates the VMI on to the subset of processor cores to implement the VNF.

Abstract: A system includes a memory, a processor in communication with the memory, and an automotive operating system (OS) with a software update manager for an automobile. The system is configured to determine a new software update is available, monitor operating metrics of the automotive OS, and determine an installation time-window when each of the operating metrics collectively fall within respective predetermined thresholds. Responsive to determining that each of the operating metrics fall within respective predetermined thresholds, the system is configured to signal to the software update manager to start the installation once the automobile meets installation criteria. The installation criteria include at least (i) a first criteria that the automobile is stationary and (ii) a second criteria that the automotive OS is in an available state.

Abstract: A method for managing updates of a data manager includes: obtaining a service call graph where the service call graph includes services grouped into service sub-trees and specifies a service hierarchy between the services; identifying the service sub-trees of the service call graph; identifying, using the service hierarchy, independent services among the services of the service call graph; generating, based on identifying the service sub-trees and the independent services, an update sequence for the services; predicting, using the update sequence and the services, an update window for the service sub-trees; and initiating an update of the services using the prediction of the update window.

Abstract: A manager creates agent information and provides a download page for an installer. In a case where the downloaded installer is activated in a host computer, agent installation processing is executed according to input work for setting information for connection with the manager by a user. Further, in a case where creation of the agent in its own apparatus is instructed, the manager creates, in the apparatus in which the manager operates, an agent in which the setting information for connection with the manager has been set, without the input work by the user that is necessary for the above-described installation processing using the installer.

Abstract: The present invention relates to a method and system for installing software onto a client in the NIM environment and corresponding client. Said method includes: initializing said client, wherein a virtual mapping device associated with a memory driver of the client is created, the virtual mapping device for scheduling between the client's memory driver and the remote NIM server with respect to the I/O operation for running the software so as to direct the I/O operation for running said software to the client's memory driver or the remote NIM server; running said software on the client; acquiring the resources desired for running software; and conducting data migration operation from the NIM server to the client while running said software, wherein the migrated data is the resource data obtained from NIM server and desired for installing said software; and the software installation being completed when all the data desired for installing said software are migrated to the memory driver of the client.

Abstract: A robotic process automation system provides a capability to deploy software robots (bots) by receiving from a deployment user a bot deployment request comprising a bot identification that identifies a specific preexisting bot and an authorized class of user to execute the specific preexisting bot. Credentials of the deployment user are checked. An execution device upon which the specific preexisting bot will execute is identified from a set of available devices. An authorization token is issued for the execution device to uniquely identify the execution device and to authorize the execution device to communicate with the robotic process automation system. In response to a request by the execution device the specific preexisting bot and credentials corresponding to the authorized class of user are provided, wherein the specific preexisting bot executes on the execution device automatically without input from any individual corresponding to the authorized class of user.

Abstract: Processor core power management in a virtualized environment. A hypervisor, executing on a processor device of a computing host, the processor device having a plurality of processor cores, receives from a guest operating system of a virtual machine, a request to set a virtual central processing unit (VCPU) of the virtual machine to a first requested P-state level of a plurality of P-state levels. Based on the request, the hypervisor associates the VCPU with a first processor core having a P-state that corresponds to the first requested P-state level.

Abstract: A build fail of a job in a development pipeline of an application development system is analyzed. A determination as to whether the build fail affects other jobs in the development pipeline is made. In response to determining that the build fail affects at least one of the other jobs of the plurality of jobs, an alert identifying the at least one of the other jobs affected by the build fail is generated.

Abstract: A system and method for a virtual desktop system is disclosed. The system includes a master fabric region including resources for provisioning a desktop. The system includes a plurality of expansion fabric regions. Each of the expansion fabric regions including replicated resources for provisioning the desktop from the master fabric region. The system includes a control plane having a global pool. A client device application operated by a user associated with the global pool accesses a desktop from either the master fabric region or one of the expansion fabric regions. The control plane is operable to add a new expansion fabric region to the plurality of expansion fabric regions or eliminate one of the plurality of expansion fabric regions.

Abstract: A method for minimizing allocation failures in a cloud computing system without overprovisioning may include determining a predicted supply for a virtual machine series in a system unit of the cloud computing system during an upcoming time period. The predicted supply may be based on a shared available current capacity and a shared available future added capacity for the virtual machine series in the system unit. The method may also include predicting an available capacity for the virtual machine series in the system unit during the upcoming time period. The predicted available capacity may be based at least in part on a predicted demand for the virtual machine series in the system unit during the upcoming time period and the predicted supply. The method may also include taking at least one mitigation action in response to determining that the predicted demand exceeds the predicted supply during the upcoming time period.

Abstract: An example method of interfacing with a hypervisor in a computing system is described, which includes a processor having at least three hierarchical privilege levels including a third privilege level more privileged than a second privilege level, the second privilege level more privileged than a first privilege level.

Abstract: Examples herein relate to checkpoint replication and copying of updated checkpoint data. For example, a memory controller coupled to a memory can receive a write request with an associated address to write or update checkpoint data and track updates to checkpoint data based on at least two levels of memory region sizes. A first level is associated with a larger memory region size than a memory region size associated with the second level. In some examples, the first level is a cache-line memory region size and the second level is a page memory region size. Updates to the checkpoint data can be tracked at the second level unless an update was previously tracked at the first level. Reduced amounts of updated checkpoint data can be transmitted during a checkpoint replication by using multiple region size trackers.

Abstract: Techniques are disclosed for dynamic access and instrumentation of model specific registers (MSRs). A virtual machine monitor (VMM) can provide a kernel application program interface (API) that can be utilized to access and instrument an MSR. A method may include receiving, by the VMM, an MSR instrumentation command that identifies an MSR to instrument and causing instrumentation of the MSR identified in the MSR instrumentation command. Instrumentation of the identified MSR can be caused by configuring or manipulating a virtual machine control structure (VMCS) of a guest virtual machine (VM). The MSR instrumentation command may be an MSR instrumentation request command, an MSR remove request command, an MSR value set request command, or an MSR value fetch request command. In some cases, the VMM may be a Type-I hypervisor.

Abstract: A system implements task contention reduction via policy-based selection. Tasks waiting to be performed are indexed in a task data structure that groups the tasks based on the resources to which the tasks pertain. Workers request batches of tasks for the workers to perform. A scan cycle includes building multiple batches of tasks by scanning the task data structure for a requesting worker. A policy (e.g., random or some other form of optimization) determines where the scan cycle starts in the data structure. Each batch of tasks is delivered to a worker along with a token that keeps the state of the scan cycle (e.g., where the scan cycle started, and where the next scan to build the next batch within the scan cycle begins). The worker returns the token with the next request for the next batch and the next batch is built based on the token's state information.