python-watcher - en to en_GB translation catalogue (23 entries)

en: API calls while building the Compute data model will be retried upon failure. The amount of failures allowed before giving up and the time before reattempting are configurable. The `api_call_retries` and `api_query_timeout` parameters in the `[collector]` group can be used to adjust these paremeters. 10 retries with a 1 second time in between reattempts is the default.
en_GB: API calls while building the Compute data model will be retried upon failure. The amount of failures allowed before giving up and the time before reattempting are configurable. The `api_call_retries` and `api_query_timeout` parameters in the `[collector]` group can be used to adjust these parameters. 10 retries with a 1 second time in between reattempts is the default.

en: Add a service supervisor to watch Watcher deamons.
en_GB: Add a service supervisor to watch Watcher daemons.

en: Add show data model api for Watcher. New in version 1.3. User can use 'openstack optimize datamodel list' command to view the current data model information in memory. User can also add '--audit <Audit_UUID>' to view specific data model in memory filted by the scope in audit. User can also add '--detail' to view detailed information about current data model. User can also add '--type <type>' to specify the type of data model. Default type is 'compute'. In the future, type 'storage' and 'baremetal' will be supported.
en_GB: Add show data model API for Watcher. New in version 1.3. User can use 'openstack optimize datamodel list' command to view the current data model information in memory. User can also add '--audit <Audit_UUID>' to view specific data model in memory filtered by the scope in audit. User can also add '--detail' to view detailed information about current data model. User can also add '--type <type>' to specify the type of data model. Default type is 'compute'. In the future, type 'storage' and 'baremetal' will be supported.

en: Added a generic scoring engine module, which will standarize interactions with scoring engines through the common API. It is possible to use the scoring engine by different Strategies, which improve the code and data model re-use.
en_GB: Added a generic scoring engine module, which will standardise interactions with scoring engines through the common API. It is possible to use the scoring engine by different Strategies, which improve the code and data model re-use.

en: Added a strategy that monitors if there is a higher load on some hosts compared to other hosts in the cluster and re-balances the work across hosts to minimize the standard deviation of the loads in the cluster.
en_GB: Added a strategy that monitors if there is a higher load on some hosts compared to other hosts in the cluster and re-balances the work across hosts to minimise the standard deviation of the loads in the cluster.

en: Added a way to compare the efficacy of different strategies for a give optimization goal.
en_GB: Added a way to compare the efficacy of different strategies for a give optimisation goal.

en: Added a way to create periodic audit to be able to optimize continuously the cloud infrastructure.
en_GB: Added a way to create periodic audit to be able to continuously optimise the cloud infrastructure.

en: Added a way to return the of available goals depending on which strategies have been deployed on the node where the decison engine is running.
en_GB: Added a way to return the of available goals depending on which strategies have been deployed on the node where the decision engine is running.

en: Added gnocchi support as data source for metrics. Administrator can change data source for each strategy using config file.
en_GB: Added Gnocchi support as data source for metrics. Administrator can change data source for each strategy using config file.

en: Added strategy to identify and migrate a Noisy Neighbor - a low priority VM that negatively affects peformance of a high priority VM by over utilizing Last Level Cache.
en_GB: Added strategy to identify and migrate a Noisy Neighbour - a low priority VM that negatively affects performance of a high priority VM by over utilising Last Level Cache.

en: Allow decision engine to pass strategy parameters, like optimization threshold, to selected strategy, also strategy to provide parameters info to end user.
en_GB: Allow decision engine to pass strategy parameters, like optimisation threshold, to selected strategy, also strategy to provide parameters info to end user.

en: Baremetal Model gets Audit scoper with an ability to exclude Ironic nodes.
en_GB: Baremetal Model gets Audit scope with an ability to exclude Ironic nodes.

en: Centralize all configuration options for Watcher.
en_GB: Centralise all configuration options for Watcher.

en: Existing workload_balance strategy based on the VM workloads of CPU. This feature improves the strategy. By the input parameter "metrics", it makes decision to migrate a VM base on CPU or memory utilization.
en_GB: Existing workload_balance strategy based on the VM workloads of CPU. This feature improves the strategy. By the input parameter "metrics", it makes decision to migrate a VM base on CPU or memory utilisation.

en: Grafana has been added as datasource that can be used for collecting metrics. The configuration options allow to specify what metrics and how they are stored in grafana so that no matter how Grafana is configured it can still be used. The configuration can be done via the typical configuration file but it is recommended to configure most options in the yaml file for metrics. For a complete walkthrough on configuring Grafana see: https://docs.openstack.org/watcher/latest/datasources/grafana.html
en_GB: Grafana has been added as datasource that can be used for collecting metrics. The configuration options allow to specify what metrics and how they are stored in Grafana so that no matter how Grafana is configured it can still be used. The configuration can be done via the typical configuration file but it is recommended to configure most options in the yaml file for metrics. For a complete walkthrough on configuring Grafana see: https://docs.openstack.org/watcher/latest/datasources/grafana.html

en: Provide a notification mechanism into Watcher that supports versioning. Whenever a Watcher object is created, updated or deleted, a versioned notification will, if it's relevant, be automatically sent to notify in order to allow an event-driven style of architecture within Watcher. Moreover, it will also give other services and/or 3rd party softwares (e.g. monitoring solutions or rules engines) the ability to react to such events.
en_GB: Provide a notification mechanism into Watcher that supports versioning. Whenever a Watcher object is created, updated or deleted, a versioned notification will, if it's relevant, be automatically sent to notify in order to allow an event-driven style of architecture within Watcher. Moreover, it will also give other services and/or 3rd party software (e.g. monitoring solutions or rules engines) the ability to react to such events.

en: The graph model describes how VMs are associated to compute hosts. This allows for seeing relationships upfront between the entities and hence can be used to identify hot/cold spots in the data center and influence a strategy decision.
en_GB: The graph model describes how VMs are associated to compute hosts. This allows for seeing relationships upfront between the entities and hence can be used to identify hot/cold spots in the data centre and influence a strategy decision.

en: The minimum required version of the ``[nova_client]/api_version`` value is now enforced to be ``2.56`` which is available since the Queens version of the nova compute service.
en_GB: The minimum required version of the ``[nova_client]/api_version`` value is now enforced to be ``2.56`` which is available since the Queens version of the Nova compute service.

en: Watcher can continuously optimize the OpenStack cloud for a specific strategy or goal by triggering an audit periodically which generates an action plan and run it automatically.
en_GB: Watcher can continuously optimise the OpenStack cloud for a specific strategy or goal by triggering an audit periodically which generates an action plan and run it automatically.

en: Watcher can now run specific actions in parallel improving the performances dramatically when executing an action plan.
en_GB: Watcher can now run specific actions in parallel improving the performance dramatically when executing an action plan.

en: Watcher starts to support API microversions since Stein cycle. From now onwards all API changes should be made with saving backward compatibility. To specify API version operator should use OpenStack-API-Version HTTP header. If operator wants to know the mininum and maximum supported versions by API, he/she can access /v1 resource and Watcher API will return appropriate headers in response.
en_GB: Watcher starts to support API microversions since the Stein cycle. From now onwards all API changes should be made with saving backward compatibility. To specify API version operator should use OpenStack-API-Version HTTP header. If operator wants to know the minimum and maximum supported versions by API, he/she can access /v1 resource and Watcher API will return appropriate headers in response.

en: We also add some new propeties:
en_GB: We also add some new properties:

en: vcpu_reserved: The amount of cpu a node has reserved for its own use.
en_GB: vcpu_reserved: The amount of CPU a node has reserved for its own use.
