Abstract: Proxy-less power management using an automation engine is disclosed. An entity manager executing on a computing device determines that a first entity requires a power management function to be performed against the first entity. The entity manager generates power management execution information that identifies a power device address of a power management device that controls the first entity. An automation engine is initiated on the computing device with the power management execution information to cause the power management function to be performed against the first entity via the power management device based on the power management execution information.

Abstract: Disclosed is a method, comprising obtaining configuration information for a virtual machine (VM) that is to be imported from a source platform to a target platform, creating an overlay image of a virtual disk image of the VM on an external disk, creating a second overlay image of the virtual disk image on a temporary disk of the target platform, the temporary disk comprising an active layer of the virtual disk image, and the external disk comprising a backing file of the temporary disk, starting a second VM on the target platform in view of the configuration information and copying, by a processing device, the temporary disk and the external disk to a target disk on the target platform.

Abstract: Disclosed is a method, comprising obtaining configuration information for a virtual machine (VM) that is to be imported from a source platform to a target platform, creating an overlay image of a virtual disk image of the VM on an external disk, creating a second overlay image of the virtual disk image on a temporary disk of the target platform, the temporary disk comprising an active layer of the virtual disk image, and the external disk comprising a backing file of the temporary disk, starting a second VM on the target platform in view of the configuration information and copying, by a processing device, the temporary disk and the external disk to a target disk on the target platform.

Abstract: Proxy-less power management using an automation engine is disclosed. An entity manager executing on a computing device determines that a first entity requires a power management function to be performed against the first entity. The entity manager generates power management execution information that identifies a power device address of a power management device that controls the first entity. An automation engine is initiated on the computing device with the power management execution information to cause the power management function to be performed against the first entity via the power management device based on the power management execution information.

Abstract: Proxy-less power management using an automation engine is disclosed. An entity manager executing on a computing device determines that a first entity requires a power management function to be performed against the first entity. The entity manager generates power management execution information that identifies a power device address of a power management device that controls the first entity. An automation engine is initiated on the computing device with the power management execution information to cause the power management function to be performed against the first entity via the power management device based on the power management execution information.

Abstract: Proxy-less power management using an automation engine is disclosed. An entity manager executing on a computing device determines that a first entity requires a power management function to be performed against the first entity. The entity manager generates power management execution information that identifies a power device address of a power management device that controls the first entity. An automation engine is initiated on the computing device with the power management execution information to cause the power management function to be performed against the first entity via the power management device based on the power management execution information.

Abstract: A lightweight directory access (LDAP) broker receives user information associated with a query for information in an LDAP repository. The query may be in an abstraction format. The LDAP broker determines a computing domain in view of the user information and retrieves a configuration file associated with the computing domain. The configuration file comprises a mapping for the query between an abstraction format and a vendor specific format. The LDAP broker converts the query to the vendor specific format in view of the mapping in the configuration file.

Abstract: A lightweight directory access (LDAP) broker receives user information associated with a query for information in an LDAP repository. The query may be in an abstraction format. The LDAP broker determines a computing domain in view of the user information and retrieves a configuration file associated with the computing domain. The configuration file comprises a mapping for the query between an abstraction format and a vendor specific format. The LDAP broker converts the query to the vendor specific format in view of the mapping in the configuration file.