v1.2.1

v1.2.1

What's Changed

Adding new cloud instances is now easier. Simply define the resources they reserve and identify the server archetype on which the instance will be hosted. Refer to the contribution documentation for more information.

Internal changes

• Externalizing impacts computation outside the asset's model by creating a service for this purpose (boaviztapi/service/impacts_computation.py)
• Updating cloud instance model and impacts computation in line with : #252 (comment)
• Improve impact model (boaviztapi/model/impact.py). All the assets keep the impacts as an attribute once they have been calculated. Performance is significantly improved in the event of a verbose call.

Bug fixes

• Power consumption was modelled for one component unit. Consumption was only multiplied by the number of components when calculating impacts at device level. The consumption of the component now reflects the consumption of all the units.
• #256
• #257
• #243
• #248

Breaking changes

• 'instance_per_instance' is no longer included in the verbose output of the cloud route.
• Previously, the verbose returned the impacts of each platform's components in their entirety. Now, only the impacts associated with the instance are returned for each component. Components impacts returned by cloud router shouldn't be divided by instance_per_instance.

Contributors

New Contributors

• @cosmastech made their first contribution in #243
• @tibosmn made their first contribution in #248

Other contributors

@da-ekchajzer
@samuelrince
@JacobValdemar

Full Changelog: v1.1.0...v1.2.0