Abstract: At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Abstract: At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Abstract: At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Abstract: Examples described herein provide for hardware interface services in virtualized systems. The hardware interface services may receive a vendor-agnostic command to control a particular hardware component. The particular hardware component may be identified, for example, by its location (e.g., physical and/or logical location or other identification) in the virtualized system. The hardware interface services described herein may identify a hardware component type (e.g., vendor, serial number, model number, etc.) based on the location provided. The hardware interface services may translate the vendor-agnostic command to a command specific for the identified hardware component.

Abstract: At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Abstract: A system and method include receiving, by a migration tool of a virtual computing system, an indication for hypervisor conversion for converting a hypervisor on nodes in a cluster of the virtual computing system from a first hypervisor type to a second hypervisor type. The system and method also include converting, one at a time, the hypervisor on each of the nodes from the first hypervisor type to the second hypervisor type in response to the indication, including converting virtual machines on each of the nodes for running on the second hypervisor type. The hypervisor and the virtual machines are converted on one node before starting conversion of the hypervisor and the virtual machines on another node, and the virtual machines of the one node are migrated from the one node before conversion and the migrated virtual machines remain operational during conversion of the hypervisor on the one node.

Abstract: A system and method include assigning, by an identifier management system of a virtual computing system, a hypervisor agnostic identifier to a virtual machine. The system and method also include creating a mapping of the hypervisor agnostic identifier to a first hypervisor specific identifier of the virtual machine, including storing the mapping in a database, and updating the mapping in response to a second hypervisor specific identifier being associated with the virtual machine. The updated mapping maps the hypervisor agnostic identifier to the second hypervisor specific identifier. The system and method further include making available the hypervisor agnostic identifier for use by other elements of the virtual computing system instead of the first hypervisor specific identifier and the second hypervisor specific identifier. The first hypervisor specific identifier and the second hypervisor specific identifier are hypervisor specific, while the hypervisor agnostic identifier is not hypervisor specific.

Abstract: At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Abstract: Examples described herein provide for hardware interface services in virtualized systems. The hardware interface services may receive a vendor-agnostic command to control a particular hardware component. The particular hardware component may be identified, for example, by its location (e.g., physical and/or logical location or other identification) in the virtualized system. The hardware interface services described herein may identify a hardware component type (e.g., vendor, serial number, model number, etc.) based on the location provided. The hardware interface services may translate the vendor-agnostic command to a command specific for the identified hardware component.

Abstract: A system and method include receiving, by a migration tool of a virtual computing system, an indication for hypervisor conversion for converting a hypervisor on nodes in a cluster of the virtual computing system from a first hypervisor type to a second hypervisor type. The system and method also include converting, one at a time, the hypervisor on each of the nodes from the first hypervisor type to the second hypervisor type in response to the indication, including converting virtual machines on each of the nodes for running on the second hypervisor type. The hypervisor and the virtual machines are converted on one node before starting conversion of the hypervisor and the virtual machines on another node, and the virtual machines of the one node are migrated from the one node before conversion and the migrated virtual machines remain operational during conversion of the hypervisor on the one node.

Abstract: A system and method include assigning, by an identifier management system of a virtual computing system, a hypervisor agnostic identifier to a virtual machine. The system and method also include creating a mapping of the hypervisor agnostic identifier to a first hypervisor specific identifier of the virtual machine, including storing the mapping in a database, and updating the mapping in response to a second hypervisor specific identifier being associated with the virtual machine. The updated mapping maps the hypervisor agnostic identifier to the second hypervisor specific identifier. The system and method further include making available the hypervisor agnostic identifier for use by other elements of the virtual computing system instead of the first hypervisor specific identifier and the second hypervisor specific identifier. The first hypervisor specific identifier and the second hypervisor specific identifier are hypervisor specific, while the hypervisor agnostic identifier is not hypervisor specific.