Abstract: A system performs runtime adjustment of a configuration model. The system receives, at runtime, a change request directed at one or more modified entities in the configuration model. Based on leadership information, one or more infringing entities are identified among the one or more modified entities. The leadership information indicates an impact that one entity has on another entity with respect to a given constraint. Based on the leadership information, a propagation scope is identified for a constraint violated by an infringing entity. The propagation scope includes the infringing entity and other entities that are potentially affected by the request. For resolving single constraint violation, a collection of paths are created in the propagation scope and a path is selected one at a time starting from the shortest path in the collection. For resolving multiple constraint violation, a bonded path is formed for a group of propagation scopes that overlap.

Abstract: A system configuration is generated by integrating source models. Transformations are generated according to a weaving model that specifies relations among metamodels of the source models and the system configuration. The transformations, when executed, transform the source models into the system configuration that includes target entities. From the transformations, one or more integration constraints are generated for each target entity to be created or modified by an operation of the transformations. The integration constraints describe semantics of the relations specified by the weaving model. System configuration constraints are formed to include the integration constraints in addition to constraints of each source model. The transformations are executed to transform the source models into the system configuration to generate the system configuration obeying the system configuration constraints.

Abstract: A system configuration is partially validated in response to requested changes to the system configuration. First, a reduced set of constraints is identified among a plurality of constraints of the system configuration. The reduced set of constraints place restrictions on attribute values and relations of changed entities to which the requested changes are applied. Each constraint of the reduced set is categorized based on leadership information that indicates an impact that a changed entity has on another entity with respect to the constraint. Each categorized constraint of the reduced set is validated to determine whether to accept, reject or modify the system configuration having the requested changes.

Abstract: A system configuration is generated by integrating source models. Transformations are generated according to a weaving model that specifies relations among metamodels of the source models and the system configuration. The transformations, when executed, transform the source models into the system configuration that includes target entities. From the transformations, one or more integration constraints are generated for each target entity to be created or modified by an operation of the transformations. The integration constraints describe semantics of the relations specified by the weaving model. System configuration constraints are formed to include the integration constraints in addition to constraints of each source model. The transformations are executed to transform the source models into the system configuration to generate the system configuration obeying the system configuration constraints.

Abstract: A system performs runtime adjustment of a configuration model. The system receives, at runtime, a change request directed at one or more modified entities in the configuration model. Based on leadership information, one or more infringing entities are identified among the one or more modified entities. The leadership information indicates an impact that one entity has on another entity with respect to a given constraint. Based on the leadership information, a propagation scope is identified for a constraint violated by an infringing entity. The propagation scope includes the infringing entity and other entities that are potentially affected by the request. For resolving single constraint violation, a collection of paths are created in the propagation scope and a path is selected one at a time starting from the shortest path in the collection. For resolving multiple constraint violation, a bonded path is formed for a group of propagation scopes that overlap.

Abstract: A system configuration is partially validated in response to requested changes to the system configuration. First, a reduced set of constraints is identified among a plurality of constraints of the system configuration. The reduced set of constraints place restrictions on attribute values and relations of changed entities to which the requested changes are applied. Each constraint of the reduced set is categorized based on leadership information that indicates an impact that a changed entity has on another entity with respect to the constraint. Each categorized constraint of the reduced set is validated to determine whether to accept, reject or modify the system configuration having the requested changes.

Abstract: Disjoint node groups are generated for a node cluster to guarantee hardware redundancy for each service group to be configured on the node cluster. Each service group includes service units, and each service unit is a unit of redundancy for services provided and protected by the service group. Hardware dependency is identified between virtual machines in the node cluster and hardware elements to host the virtual machines. A first node group set (NG set) is formed using a first criterion to select the virtual machines into different node groups based on the hardware dependency, such that there is no common hardware element between any two node groups in the first NG set. The first NG set is mapped to a first set of service groups. Different node groups of the first NG set are mapped to different service units in each service group of the first set of service groups.

Abstract: Disjoint node groups are generated for a node cluster to guarantee hardware redundancy for each service group to be configured on the node cluster. Each service group includes service units, and each service unit is a unit of redundancy for services provided and protected by the service group. Hardware dependency is identified between virtual machines in the node cluster and hardware elements to host the virtual machines. A first node group set (NG set) is formed using a first criterion to select the virtual machines into different node groups based on the hardware dependency, such that there is no common hardware element between any two node groups in the first NG set. The first NG set is mapped to a first set of service groups. Different node groups of the first NG set are mapped to different service units in each service group of the first set of service groups.