Abstract: A system is upgraded by rolling upgrade with dynamic batch sizes in multiple iterations. The system includes multiple hosts that host multiple resources. The rolling upgrade calculates a number of hosts to upgrade and a number of resources to upgrade for each iteration. The calculation subtracts a reserved number of hosts from a capacity of the system to account for potential failover and potential resource scaling operations during the iteration. Based on the calculated number of hosts to upgrade, it is determined whether the system has a capacity for upgrade. If the capacity exists, the calculated number of hosts to upgrade and the calculated number of resources to upgrade are upgraded, while accepting resource scaling requests during the iteration.

Abstract: An upgrade campaign specification upgrades a system from a current configuration to a target configuration. A method is provided for selecting one or more upgrade campaign specifications from a given set of upgrade campaign specifications. For each upgrade campaign specification, the method (1) identifies software and management operations specified in the upgrade campaign specification for upgrading the system; and (2) for each of a set of one or more scenarios defined in terms of operation execution time selection and execution mode, simulates upgrade of the system according to a corresponding arrangement of the software and management operations, thereby obtaining a corresponding execution time and a corresponding outage. A subset of the upgrade campaign specifications is rejected, for which the corresponding execution times do not meet an execution time threshold or for which the corresponding outages do not meet an outage threshold.

Abstract: A Network Service Descriptor (NSD) is generated, from Virtualized Network Functions (VNFs) existing in a VNF catalog, for instantiating a network service which satisfies given network service requirements. From the VNF catalog, a system selects VNFs that provide functionalities and architectural blocks required to fulfill the NS requirements. The system generates at least a VNF forwarding graph (VNFFG), which includes relations between the functionalities and the architectural blocks of the selected VNFs as well as traffic flows between the selected VNFs. The system then creates the NSD, which includes the VNFFG, for instantiating the network service.

Abstract: The disclosure relates to a method, executed in a Network Function Virtualization Infrastructure (NFVI) software modification manager, for coordination of NFVI software modifications of a NFVI providing at least one Virtual Resource (VR) hosting at least one Virtual Network Function (VNF), comprising receiving an NFVI software modifications request; sending a notification that a software modification procedure of the at least one VR is about to start to a VNF level manager, the VNF level manager managing a VNF hosted on the at least one VR provided by the NFVI; applying software modifications to at least one resource of the at least one VR; and notifying the VNF level manager about completion of the software modifications.

Abstract: A method dynamically responds to a change in a workload managed by Availability Management Framework (AMF), where the workload is represented by a set of service instances (Sis) protected by a service group (SG) in a cluster. When receiving a notification of the workload change indicating an impacted SI in the set of Sis, the method applies at least one strategy from a collection of SG-level strategies and cluster-level strategies to adjust an amount of resources available to at least the impacted SI. Each SG-level strategy changes one or more configuration attributes within the SG according to a redundancy model used by the SG, and each cluster-level strategy changes one or more configuration attributes within the cluster according to one or more redundancy models used by SGs within the cluster. The method causes the AMF to apply a configuration change to respond to the workload change.

Abstract: A system is reconfigured at runtime when triggers are issued in response to events taking place in the system. The triggers, which are issued on configuration entities, are correlated by transferring relations of the configuration entities to relations of the triggers to thereby identify related triggers. Elasticity rules are selected for the triggers, where the elasticity rules specify actions for resource allocation or deallocation at runtime. Selected actions of the selected elasticity rules for the related triggers are executed to reconfigure the system according to a set of action correlation meta-rules which provide an ordering of the actions.

Abstract: An upgrade campaign is generated for entities of a system described by a source configuration. According to the upgrade campaign, the system is upgraded to a target configuration using available software. A change model describes changes from the source configuration to the target configuration. According to the change model, an upgrade campaign specification model is generated, which contains at least one upgrade campaign element for each change in the change model. A subset of upgrade campaign elements are matched based on a first set of rules, and the matched upgrade campaign elements are merged into an upgrade procedure in the upgrade campaign specification model. The upgrade procedures are ordered based on a second set of rules and dependencies among the entities of the system, where the dependencies are extracted from the source configuration, the target configuration and the description of available software.

Abstract: An upgrade campaign specification upgrades a system from a current configuration to a target configuration. A method is provided for selecting one or more upgrade campaign specifications from a given set of upgrade campaign specifications. For each upgrade campaign specification, the method (1) identifies software and management operations specified in the upgrade campaign specification for upgrading the system; and (2) for each of a set of one or more scenarios defined in terms of operation execution time selection and execution mode, simulates upgrade of the system according to a corresponding arrangement of the software and management operations, thereby obtaining a corresponding execution time and a corresponding outage. A subset of the upgrade campaign specifications is rejected, for which the corresponding execution times do not meet an execution time threshold or for which the corresponding outages do not meet an outage threshold.

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 configuration is generated for a software that is to be deployed for providing high service availability to satisfy configuration requirements. One or more configuration patterns are identified, each of which specifies a set of attribute values and an actual recovery action for a failed component as a configuration option of the software. The unchangeable attribute values of the software are matched with the configuration patterns to obtain a matching configuration pattern, whose actual recovery action incurs a smallest component failure recovery impact zone. The matching configuration pattern is selected as at least a portion of the configuration of the software. Then the changeable attribute values of the software are set to the corresponding attribute values of the matching configuration pattern to satisfy the configuration requirements.

Abstract: A system is adapted to generate a configuration for a service provider system to provide a highly available (HA) service. The system first identifies type stacks that provide the HA service and one or more component types in each type stack. Each type stack is a combination of prototypes that describe features and capabilities of available software providing the HA service. The system estimates, for each component type in the type stacks, a mean-time-to-recover (MTTR) of the HA service based on time for completing an actual recovery action in response to a component failure. The system further estimates service availability provided by each type stack based on the MTTR and a mean-time-to-failure (MTTF) of each component type in the type stack. The system then eliminates one or more of the type stacks that do not satisfy a requested service availability before proceeding to subsequent steps of configuration generation.

Abstract: A system is upgraded by rolling upgrade with dynamic batch sizes in multiple iterations. The system includes multiple hosts that host multiple resources. The rolling upgrade calculates a number of hosts to upgrade and a number of resources to upgrade for each iteration. The calculation subtracts a reserved number of hosts from a capacity of the system to account for potential failover and potential resource scaling operations during the iteration. Based on the calculated number of hosts to upgrade, it is determined whether the system has a capacity for upgrade. If the capacity exists, the calculated number of hosts to upgrade and the calculated number of resources to upgrade are upgraded, while accepting resource scaling requests during the iteration.

Abstract: An upgrade campaign is generated for entities of a system described by a source configuration. According to the upgrade campaign, the system is upgraded to a target configuration using available software. A change model describes changes from the source configuration to the target configuration. According to the change model, an upgrade campaign specification model is generated, which contains at least one upgrade campaign element for each change in the change model. A subset of upgrade campaign elements are matched based on a first set of rules, and the matched upgrade campaign elements are merged into an upgrade procedure in the upgrade campaign specification model. The upgrade procedures are ordered based on a second set of rules and dependencies among the entities of the system, where the dependencies are extracted from the source configuration, the target configuration and the description of available software.

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: There is described a method for providing a Virtualized Network Function (VNF) according to Network Service (NS) requirements. The method comprises selecting an on-boarded VNF descriptor (VNFD) from a VNF catalogue, configuring parameters of the selected on-boarded VNFD according to the requirements of the NS and instantiating a VNF according to the configured on-boarded VNFD. There is also described a method for providing a Network Service (NS). The method comprises selecting an on-boarded NS Descriptor (NSD) from an NS catalogue, modifying NSD information of the selected on-boarded NSD and instantiating the NS according to the modified on-boarded NSD.

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 configuration is generated that enables Availability Management Framework (AMF) to manage virtual machines (VMs) and support hardware redundancy for each of service groups (SGs). Each component service instance (CST) is configured to represent one or more of the VMs to be managed by AMF. Configuration attributes are set to associate each VM with one CSI, such that the VMs to be hosted on a same physical host are associated with different CSIs of a same service instance. Service units (SUs) of different SGs are configured such that each SU is hosted by any one VM on the same physical host, while the different SUs of a same SG are mapped to the VMs hosted on different physical hosts. The configuration enables the AMF to manage an application formed by the SGs in a virtualized environment in a same way as in a non-virtualized environment without modification to the application.

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 is adapted to generate a configuration for a service provider system to provide a highly available (HA) service. The system first identifies type stacks that provide the HA service and one or more component types in each type stack. Each type stack is a combination of prototypes that describe features and capabilities of available software providing the HA service. The system estimates, for each component type in the type stacks, a mean-time-to-recover (MTTR) of the HA service based on time for completing an actual recovery action in response to a component failure. The system further estimates service availability provided by each type stack based on the MTTR and a mean-time-to-failure (MTTF) of each component type in the type stack. The system then eliminates one or more of the type stacks that do not satisfy a requested service availability before proceeding to subsequent steps of configuration generation.

Abstract: A method dynamically responds to a change in a workload managed by Availability Management Framework (AMF), where the workload is represented by a set of service instances (Sis) protected by a service group (SG) in a cluster. When receiving a notification of the workload change indicating an impacted SI in the set of Sis, the method applies at least one strategy from a collection of SG-level strategies and cluster-level strategies to adjust an amount of resources available to at least the impacted SI. Each SG-level strategy changes one or more configuration attributes within the SG according to a redundancy model used by the SG, and each cluster-level strategy changes one or more configuration attributes within the cluster according to one or more redundancy models used by SGs within the cluster. The method causes the AMF to apply a configuration change to respond to the workload change.