Security-policy based virtual machine migration or cloning

1 . A method comprising:

maintaining a virtual machine (VM) object storing a security policy of a VM running on a first host computing system;

attaching the VM object to the VM;

in response to detecting a trigger event, identifying a second host computing system that is in compliance with the security policy in the VM object; and

executing a management operation to migrate or clone the VM along with the attached VM object from the first host computing system to the second host computing system.

2 . The method of claim 1 , further comprising:

upon migrating or cloning the VM along with the attached VM object, retrieving the security policy from the attached VM object;

determine at least one security profile employed in the second host computing system that complies with the retrieved security policy; and

applying the at least one security profile to the VM running on the second host computing system.

3 . The method of claim 1 , wherein the security policy comprises at least one rule to safeguard the VM.

4 . The method of claim 1 , wherein identifying the second host computing system that is in compliance with the security policy comprises:

detecting the trigger event initiated by a user to perform the management operation on the VM; and

in response to detecting the trigger event, identifying the second host computing system that is in compliance with the security policy.

5 . The method of claim 1 , wherein identifying the second host computing system that is in compliance with the security policy comprises:

detecting the trigger event that a load of the first host computing system has exceeded a threshold; and

in response to detecting the trigger event, identifying the second host computing system that is in compliance with the security policy.

6 . The method of claim 1 , wherein identifying the second host computing system that is in compliance with the security policy comprises:

detecting the trigger event of failure of the first host computing system; and

in response to detecting the trigger event, identifying the second host computing system that is in compliance with the security policy.

7 . The method of claim 1 , wherein the VM object is maintained by storing the security policy of the VM in an encrypted format.

8 . The method of claim 1 , wherein the security policy of the VM comprises an affinity rule specifying that the VM is to run on a specific host group including the second host computing system to provide security services.

9 . A management node comprising:

a processor; and

memory coupled to the processor, wherein the memory comprises a security policy-based migration module to:

in response to detecting a trigger event, retrieve, via a first agent running in a first host computing system, a security policy of a virtual machine (VM) from a VM object attached to the VM running on the first host computing system;

determine a second host computing system that complies with the security policy;

execute a management operation to migrate or clone the VM along with the attached VM object from the first host computing system to the second host computing system; and

apply, via a second agent running in the second host computing system, at least one security profile that complies with the security policy in the attached VM object to the migrated or cloned VM on the second host computing system.

10 . The management node of claim 9 , wherein the security policy-based migration module is to enable the second agent to:

upon migrating or cloning the VM along with the attached VM object, retrieve the security policy from the attached VM object;

determine the at least one security profile employed in the second host computing system that complies with the retrieved security policy; and

apply the at least one security profile to the VM running on the second host computing system.

11 . The management node of claim 9 , wherein the security policy comprises at least one rule to safeguard the VM.

12 . The management node of claim 9 , wherein the security policy-based migration module is to:

detect the trigger event that is initiated by a user, that a load of the first host computing system has exceeded a threshold, or that indicates a failure of the first host computing system.

13 . The management node of claim 9 , wherein the security policy-based migration module is to:

generate and maintain the VM object by storing the security policy of the VM in an encrypted format.

14 . The management node of claim 9 , wherein the security policy of the VM comprises an affinity rule specifying that the VM is to run on a specific host group including the second host computing system to provide security services.

15 . A non-transitory computer readable storage medium comprising instructions executable by a processor of a management node to:

retrieve, via a first agent running in a first host computing system, a security policy of a virtual machine (VM) from a VM object attached to the VM running on the first host computing system;

determine a second host computing system having a security profile that supports the security policy of the VM;

execute a management operation to migrate or clone the VM along with the attached VM object from the first host computing system to the second host computing system; and

apply, via a second agent running in the second host computing system, the security profile that supports the security policy in the attached VM object to the migrated or cloned VM on the second host computing system.

16 . The non-transitory computer readable storage medium of claim 15 , wherein instructions to execute the management operation comprise instructions to:

detect a trigger event; and

in response to detecting the trigger event, execute the management operation to migrate or clone the VM along with the attached VM object from the first host computing system to the second host computing system.

17 . The non-transitory computer readable storage medium of claim 16 , wherein instructions to detect the trigger event comprise instructions to:

detect the trigger event that is initiated by a user, that a load of the first host computing system has exceeded a threshold, or that indicates a failure of the first host computing system.

18 . The non-transitory computer readable storage medium of claim 15 , wherein instructions to execute the management operation comprise instructions to:

in response to detecting a trigger event to migrate the VM, execute the management operation to migrate the VM along with the attached VM object from the first host computing system to the second host computing system; or

in response to detecting a trigger event to deploy the VM, execute the management operation to clone the VM along with the attached VM object from the first host computing system to the second host computing system.

19 . The non-transitory computer readable storage medium of claim 15 , wherein instructions to apply the security profile to the VM comprise instructions to:

upon migrating or cloning the VM along with the attached VM object, retrieve, via the second agent, the security policy from the attached VM object;

determine the security profile employed in the second host computing system that supports the retrieved security policy; and

apply the security profile to the VM running on the second host computing system.

20 . The non-transitory computer readable storage medium of claim 15 , wherein the security policy of the VM comprises an affinity rule specifying that the VM is to run on a specific host group including the second host computing system to provide security services.