Abstract: A technique to implement access control from within an application begins by dynamically-generating a “management scope” for a transaction associated with a set of managed resources. The management scope is a collection of permissions defined by at least one of: a set of roles, and a set of resource administration rights, that are assigned to a first operator that issues the transaction. As the transaction executes, a request to alter the transaction is then received from a second operator. According to the technique, the management scope for the transaction and associated with the first operator is then evaluated against a management scope associated with the second operator. Upon determining the management scope associated with the first operator has a given relationship to the management scope for the second operator, the transaction is permitted to be altered in response to the request. The given relationship is scoped by one or more rules.

Abstract: A technique to implement access control from within an application begins by dynamically-generating a “management scope” for a transaction associated with a set of managed resources. The management scope is a collection of permissions defined by at least one of: a set of roles, and a set of resource administration rights, that are assigned to a first operator that issues the transaction. As the transaction executes, a request to alter the transaction is then received from a second operator. According to the technique, the management scope for the transaction and associated with the first operator is then evaluated against a management scope associated with the second operator. Upon determining the management scope associated with the first operator has a given relationship to the management scope for the second operator, the transaction is permitted to be altered in response to the request. The given relationship is scoped by one or more rules.

Abstract: Examples perform concurrent execution of distributed workflows sharing common operations by a plurality of nodes, such as execution of recovery plans for disaster recovery of virtual machines operating on and off premises. Concurrent execution of identical operations that were part of a previously executed workflow are prevented, by evaluating the source of the workflow and whether the workflow has previously been initiated by that source. The disclosure is scalable to allow for new nodes to be included.

Abstract: Examples perform concurrent execution of distributed workflows sharing common operations by a plurality of nodes, such as execution of recovery plans for disaster recovery of virtual machines operating on and off premises. Concurrent execution of identical operations that were part of a previously executed workflow are prevented, by evaluating the source of the workflow and whether the workflow has previously been initiated by that source. The disclosure is scalable to allow for new nodes to be included.