trove - en to en_GB translation catalogue (70 entries)

en: A locality flag was added to the trove ReST API to allow a user to specify whether new replicas should be on the same hypervisor (affinity) or on different hypervisors (anti-affinity).
en_GB: A locality flag was added to the Trove REST API to allow a user to specify whether new replicas should be on the same hypervisor (affinity) or on different hypervisors (anti-affinity).

en: A locality flag was added to the trove ReST API to allow a user to specify whether the instances of a cluster should be on the same hypervisor (affinity) or on different hypervisors (anti-affinity).
en_GB: A locality flag was added to the trove REST API to allow a user to specify whether the instances of a cluster should be on the same hypervisor (affinity) or on different hypervisors (anti-affinity).

en: A new feature called 'module management' has been added to Trove. Users can now create, update, list and delete modules. A module is a file that is provided to Trove, and when a database instance is launched, that file is deposited on the guest instance. This feature can be used for depositing files like, for example, license files onto guest database instances.
en_GB: A new feature called 'module management' has been added to Trove. Users can now create, update, list and delete modules. A module is a file that is provided to Trove, and when a database instance is launched, that file is deposited on the guest instance. This feature can be used for depositing files like, for example, licence files onto guest database instances.

en: Add 'max-prepared-stmt-cnt' to the list of valid values which can be used in configuration groups for Mysql, Percona, MariaDB and PXC
en_GB: Add 'max-prepared-stmt-cnt' to the list of valid values which can be used in configuration groups for MySQL, Percona, MariaDB and PXC

en: Add Compute ID (server_id) and Volume ID (volume_id) to trove show output for admin users. Bug
en_GB: Add Compute ID (server_id) and Volume ID (volume_id) to Trove show output for admin users. Bug

en: Add RBAC (role-based access control) enforcement on all trove APIs. Allows to define a role-based access rule for every trove API call (rule definitions are available in /etc/trove/policy.json).
en_GB: Add RBAC (role-based access control) enforcement on all trove APIs. Allows to define a role-based access rule for every Trove API call (rule definitions are available in /etc/trove/policy.json).

en: Add disk column in flavor-list Bug 1617987.
en_GB: Add disk column in flavour-list Bug 1617987.

en: Add ephemeral column in flavor-list (Bug 1617980)
en_GB: Add ephemeral column in flavour-list (Bug 1617980)

en: Add vCPUs column in flavor-list Bug 1261876.
en_GB: Add vCPUs column in flavour-list Bug 1261876.

en: Added a new field ``operating_status`` for the instance to show the actual operational status of user's database. See https://docs.openstack.org/trove/latest/user/instance-status.html for more information.
en_GB: Added a new field ``operating_status`` for the instance to show the actual operational status of the user's database. See https://docs.openstack.org/trove/latest/user/instance-status.html for more information.

en: Added a periodic task for postgresql datastore to clean up the archived WAL files. Added a check when creating incremental backups for postgresql. A new container image ``openstacktrove/db-backup-postgresql:1.1.2`` is uploaded to docker hub.
en_GB: Added a periodic task for the PostgreSQL datastore to clean up the archived WAL files. Added a check when creating incremental backups for PostgreSQL. A new container image ``openstacktrove/db-backup-postgresql:1.1.2`` is uploaded to docker hub.

en: Added custom container registry configuration for trove guest agent, it's now possible to use images in private registry rather than docker hub.
en_GB: Added custom container registry configuration for Trove guest agent, it's now possible to use images in the private registry rather than Docker hub.

en: Added support for designate v2 api with a new dns driver. To use this driver set dns_driver = trove.dns.designate.driver.DesignateDriverV2
en_GB: Added support for designate v2 API with a new DNS driver. To use this driver set dns_driver = trove.dns.designate.driver.DesignateDriverV2

en: Added the ability to create the cinder volume in the same AZ as the nova instance. Set ``enable_volume_az`` to True (defaults to False)
en_GB: Added the ability to create the Cinder volume in the same AZ as the Nova instance. Set ``enable_volume_az`` to True (defaults to False)

en: Added the ability to quota on total amount of RAM in MB used per project. Set ``quota.max_ram_per_tenant`` to enable. Default is -1 (unlimited) to be backwards compatible. Existing installations will need to manually backfill quote usage for this to work as expected.
en_GB: Added the ability to quota on the total amount of RAM in MB used per project. Set ``quota.max_ram_per_tenant`` to enable. Default is -1 (unlimited) to be backwards compatible. Existing installations will need to manually backfill quote usage for this to work as expected.

en: After upgrading the guestagent was in an inconsistent state. This became apparent after restarting or resizing the instance after upgrading.
en_GB: After upgrading the guest agent was in an inconsistent state. This became apparent after restarting or resizing the instance after upgrading.

en: Applying a module again will now relect the update name, type, datastore and datastore_version values. Bug 1611525
en_GB: Applying a module again will now reflect the update name, type, datastore and datastore_version values. Bug 1611525

en: Changed the network mode of database container to "bridge" and exposed the service ports. Cloud operator could adjust the iptables to restrict network access from the database container to the outside. An example::
en_GB: Changed the network mode of the database container to "bridge" and exposed the service ports. Cloud operator could adjust the iptables to restrict network access from the database container to the outside. An example::

en: Database service (mysql and mariadb) is now running as docker container inside the trove instance. The image is defined by ``docker_image`` config option for each datastore.
en_GB: Database service (MySQL and MariaDB) is now running as a Docker container inside the trove instance. The image is defined by ``docker_image`` config option for each datastore.

en: Dropping support for python 2.6
en_GB: Dropping support for Python 2.6

en: Existing database services are not affected. However, in order for Trove to communicate with trove guest agent, new guest image needs to be built and existing trove instances need to be backed up and restored.
en_GB: Existing database services are not affected. However, in order for Trove to communicate with Trove guest agent, a new guest image needs to be built and existing trove instances need to be backed up and restored.

en: Fix bug 1537986 which corrects the pagination in the mysql user list command. When internal users (ignore_users) are eliminated from the list, the pagination was not correctly handled.
en_GB: Fix bug 1537986 which corrects the pagination in the MySQL user list command. When internal users (ignore_users) are eliminated from the list, the pagination was not correctly handled.

en: Fix cluster creation error which caused by "NameError: name 'common_glance' is not defined"
en_GB: Fix cluster creation error caused by "NameError: name 'common_glance' is not defined"

en: Fix docker start failed in trove guest-agent when docker_insecure_registries is not set.
en_GB: Fix Docker start failed in Trove guest-agent when docker_insecure_registries is not set.

en: Fix guest-agent failed to start mysql-5.7 container due to the missing of the configdir. note that we don't test mysql 5.7(aka.5.7.40) image in Trove CI tests. `Stroy 2010543 <https://storyboard.openstack.org/#!/story/2010543>`__
en_GB: Fix guest-agent failed to start MySQL-5.7 container due to the missing of the configdir. note that we don't test MySQL 5.7(aka.5.7.40) image in Trove CI tests. `Stroy 2010543 <https://storyboard.openstack.org/#!/story/2010543>`__

en: Fix guest-agent failed to start postgres container due to execution of the "CREATE DATABASE" statement within the context manager of psycopg library. See the following for details `Stroy 2010761 <https://storyboard.openstack.org/#!/story/2010761>`__
en_GB: Fix guest-agent failed to start PostgreSQL container due to execution of the "CREATE DATABASE" statement within the context manager of psycopg library. See the following for details `Stroy 2010761 <https://storyboard.openstack.org/#!/story/2010761>`__

en: Fix guest-agent.conf is not generated in trove guest vm. `Stroy 2010231 <https://storyboard.openstack.org/#!/story/2010231>`__
en_GB: Fix guest-agent.conf is not generated in Trove guest VM. `Stroy 2010231 <https://storyboard.openstack.org/#!/story/2010231>`__

en: Fix mysql instance permission issue when restoring a backup. `Stroy 2010467 <https://storyboard.openstack.org/#!/story/2010467>`__
en_GB: Fix MySQL instance permission issue when restoring a backup. `Stroy 2010467 <https://storyboard.openstack.org/#!/story/2010467>`__

en: Fixed an issue that the replication configuration is lost after resizing instance.
en_GB: Fixed an issue that the replication configuration is lost after resizing the instance.

en: Fixed parsing of GTID references containing a list of GTIDs from xtrabackup_binlog_info file on MySql replicas.
en_GB: Fixed parsing of GTID references containing a list of GTIDs from xtrabackup_binlog_info file on MySQL replicas.

en: Fixed the issue that datastore version cannot be deleted because of dependency of deleted instances. Now, when instance or backup is deleted, the datastore version attribute is set to NULL in database. When datastore configuration parameter is deleted, the record is deleted from database rather than only set 'deleted' field to 1.
en_GB: Fixed the issue that the datastore version cannot be deleted because of dependency of deleted instances. When an instance or backup is deleted, the datastore version attribute is set to NULL in the database. When the datastore configuration parameter is deleted, the record is deleted from the database rather than only set the 'deleted' field to 1.

en: Fixes an issue in galera_common shrink that wrong load removed nodes which could missing a ClusterShrinkMustNotLeaveClusterEmpty exception or meet a NotFound error. Bug 1699953
en_GB: Fixes an issue in galera_common shrink that the wrong load removed nodes which could be missing a ClusterShrinkMustNotLeaveClusterEmpty exception or meet a NotFound error. Bug 1699953

en: Fixes an issue with redis configuration,it use a wrong min value for repl-backlog-size in validation rules. Bug 1697596
en_GB: It fixes an issue with Redis configuration, it uses a wrong min value for repl-backlog-size in validation rules. Bug 1697596

en: Fixes bug 1507841, provides a configuration setting to enable Role Based Access Control (RBAC) for MongoDB clusters. If mongodb.cluster_secure is set to False (default is True) then RBAC will be disabled.
en_GB: It fixes bug 1507841, and provides a configuration setting to enable Role Based Access Control (RBAC) for MongoDB clusters. If mongodb.cluster_secure is set to False (default is True) then RBAC will be disabled.

en: Fixes bug 1526024, a failure in growing a mongodb cluster because of a problem in the way in which passwords were synchronized with new query routers.
en_GB: Fixes bug 1526024, a failure in growing a MongoDB cluster because of a problem in the way in which passwords were synchronised with new query routers.

en: Full and incremental backup and restore strategy for postgres based on pg_basebackup and WAL shipping.
en_GB: Full and incremental backup and restore strategy for PostgreSQL based on pg_basebackup and WAL shipping.

en: Generate trove events for the current period, and not a future period.
en_GB: Generate trove events for the current period and not a future period.

en: Implement Postgres guestagent models for databases and users.
en_GB: Implement PostgreSQL guestagent models for databases and users.

en: Implement RootController extension for the Postgres datastore.
en_GB: Implement RootController extension for the PostgreSQL datastore.

en: Implement configuration groups for Cassandra 2.1. You can now manage configuration of Cassandra datastores using the Trove configuration groups capability.
en_GB: Implement configuration groups for Cassandra 2.1. You can now manage the configuration of Cassandra datastores using the Trove configuration groups capability.

en: In Mitaka release, support was added for full offline backup and restore using the default circular logging. In this release, the name of the strategy for offline backup and restore was changed from DB2Backup to DB2OfflineBackup. Hence, to enable offline backups, we should set backup_strategy=DB2OfflineBackup and for online backups, backup_strategy=DB2OnlineBackup. The property backup_namespace and restore_namespace will be the same for both types of backup and restore.
en_GB: In the Mitaka release, support was added for full offline backup and restore using the default circular logging. In this release, the name of the strategy for offline backup and restore was changed from DB2Backup to DB2OfflineBackup. Hence, to enable offline backups, we should set backup_strategy=DB2OfflineBackup and for online backups, backup_strategy=DB2OnlineBackup. The property backup_namespace and restore_namespace will be the same for both types of backup and restore.

en: In multi-region deployment with geo-replicated Swift, the user can restore a backup in one region by manually specifying the original backup data location created in another region.
en_GB: In a multi-region deployment with geo-replicated Swift, the user can restore a backup in one region by manually specifying the original backup data location created in another region.

en: MariaDB allows an server to be a master and a slave simutaneously, so when migrating masters, if the old master is reactivated before attaching the other replicas to the new master, new unexpected GTIDs may be created on the old master and synced to some of the other replicas by chance, as the other replicas are still connecting to the old one by the time. After that these diverged slave will fail changing to the new master. This will be fixed by first attaching the other replicas to the new master, and then dealing with old master. Fixes #1754539
en_GB: MariaDB allows a server to be a master and a slave simultaneously, so when migrating masters, if the old master is reactivated before attaching the other replicas to the new master, new unexpected GTIDs may be created on the old master and synced to some of the other replicas by chance, as the other replicas are still connecting to the old one by the time. After that these diverged slaves will fail to change to the new master. This will be fixed by first attaching the other replicas to the new master, and then dealing with the old master. Fixes #1754539

en: MariaDB historically leveraged the mysql manager for guest support including the configuration groups implementation. With MariaDB now having its own manager class that inherits from Mysql, it needs to have validation_rules and a ConfigParser setup. Bug 1532256
en_GB: MariaDB historically leveraged the MySQL manager for guest support including the configuration groups implementation. With MariaDB now having its own manager class that inherits from MySQL, it needs to have validation_rules and a ConfigParser setup. Bug 1532256

en: Pass instance nic and az to cluster grow.  Add specific Fix for mongodb to use the instance nic and az.
en_GB: Pass instance nic and az to cluster grow.  Add specific Fix for MongoDB to use the instance nic and az.

en: Peviously root disable API returns a HTTP 200 response without any content, a HTTP 204 reponse which is more appropriate will be returned now.
en_GB: Previously root disable API returns a HTTP 200 response without any content, a HTTP 204 response which is more appropriate will be returned now.

en: Python 2.7 support has been dropped. Last release of Trove to support py2.7 is OpenStack Train. The minimum version of Python now supported by Trove is Python 3.6.
en_GB: Python 2.7 support has been dropped. The last release of Trove to support Python 2.7 was OpenStack Train. The minimum version of Python now supported by Trove is Python 3.6.

en: Remove support of creating volume from Nova. The former configuration "use_nova_server_volume" is not used any more, for creating volumes, cinderclient will be always used. Fixes bug #1673408.
en_GB: Remove support for creating volume from Nova. The former configuration "use_nova_server_volume" is not used anymore, for creating volumes, cinderclient will be always used. Fixes bug #1673408.

en: Support ``subnet_id`` and ``ip_address`` for creating instance. When creating instance, trove will check the network conflicts between user's network and the management network, additionally, the cloud admin is able to define other reserved networks by configuring ``reserved_network_cidrs``.
en_GB: Support ``subnet_id`` and ``ip_address`` for creating an instance. When creating an instance, Trove will check the network conflicts between user's network and the management network, additionally, the cloud admin is able to define other reserved networks by configuring ``reserved_network_cidrs``.

en: Support db instance rebuild. The rebuild operation is mainly for Trove upgrade, especially when the interface between Trove controller and guest agent changes. After Trove controller is upgraded, the cloud administrator needs to send rebuild request with the new guest image ID. Communication with the end users is needed as the database service is offline during the process. User's data in the database is not affected.
en_GB: Support db instance rebuild. The rebuild operation is mainly for Trove upgrades, especially when the interface between the Trove controller and guest agent changes. After the Trove controller is upgraded, the cloud administrator needs to send a rebuild request with the new guest image ID. Communication with the end users is needed as the database service is offline during the process. User's data in the database is not affected.

en: Support for standard WAL based streaming replication for postgresql guests. Sets up read-only hot standby servers.
en_GB: Support for standard WAL based streaming replication for PostgreSQL guests. Sets up read-only hot standby servers.

en: Support has been added for Cassandra backup and resture using the Nodetool utility.
en_GB: Support has been added for Cassandra backup and restore using the Nodetool utility.

en: Support to filter backups by ``instance_id``, additionally, admin user can get backups of all the projects by specifying ``all_projects`` in the query string parameters.
en_GB: Support to filter backups by ``instance_id``, additionally, the admin user can get backups of all the projects by specifying ``all_projects`` in the query string parameters.

en: The adds support for pxc to grow a cluster. * api and taskmanager support for shrinking a cluster * validate that the networks given are the same for each instance in the cluster. * make sure to add the existing networks on an instance in the cluster. * add new Error task for grow and shrink. * nova client version configuration changed to a string option rather than an int option because the nova microversions change nova api output. This was needed for the network interfaces on existing instances. * testing for grow and shrink cluster
en_GB: This adds support for pxc to grow a cluster. * API and taskmanager support for shrinking a cluster * validate that the networks given are the same for each instance in the cluster. * make sure to add the existing networks on an instance in the cluster. * add new Error task for grow and shrink. * Nova client version configuration changed to a string option rather than an int option because the Nova microversions change Nova API output. This was needed for the network interfaces on existing instances. * testing for grow and shrink cluster

en: The cloud admin is able to apply a security group to management port(with purpose of communicating with control plane and other management tasks) of the Trove instance, by setting the ``management_security_groups`` config option. The cloud admin is responsible for managing the security group rules. The security group and its rules need to be created before deploying Trove.
en_GB: The cloud admin is able to apply a security group to the management port(with the purpose of communicating with the control plane and other management tasks) of the Trove instance, by setting the ``management_security_groups`` config option. The cloud admin is responsible for managing the security group rules. The security group and its rules need to be created before deploying Trove.

en: The database backup and restore operations are performed by docker container inside the trove instance.
en_GB: The database backup and restore operations are performed by the Docker container inside the Trove instance.

en: The default value of ``[oslo_policy] policy_file`` config option has been changed from ``policy.json`` to ``policy.yaml``. Operators who are utilizing customized or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them in YAML format. Use the `oslopolicy-convert-json-to-yaml <https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ tool to convert a JSON to YAML formatted policy file in backward compatible way.
en_GB: The default value of ``[oslo_policy] policy_file`` config option has been changed from ``policy.json`` to ``policy.yaml``. Operators who are utilizing customized or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them into YAML format. Use the `oslopolicy-convert-json-to-yaml <https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ tool to convert a JSON to YAML formatted policy file in a backward compatible way.

en: The default value of the trove guest agent config option ``[postgresql] backup_docker_image`` is changed to ``openstacktrove/db-backup-postgresql:1.1.1``. There is nothing to do if the option is not configured explicitly.
en_GB: The default value of the Trove guest agent config option ``[postgresql] backup_docker_image`` is changed to ``openstacktrove/db-backup-postgresql:1.1.1``. There is nothing to do if the option is not configured explicitly.

en: The following config options are deprecated in favor of a separate configuration section ``service_credentials`` introduced to define the Trove service user credentials for communication with other OpenStack services.
en_GB: The following config options are deprecated in favour of a separate configuration section ``service_credentials`` introduced to define the Trove service user credentials for communication with other OpenStack services.

en: The guest log code raises a non-serializable exception if the given Swift endpoint is invalid. This causes an ambiguous "Circular reference detected" error on the guest, and a timeout on the caller. This case is now caught and the correct exception raised.
en_GB: The guest log code raises a non-serializable exception if the given Swift endpoint is invalid. This causes an ambiguous "Circular reference detected" error on the guest and a timeout on the caller. This case is now caught and the correct exception raised.

en: The management security group won't affect the Trove instances created before upgrade.
en_GB: The management security group won't affect the Trove instances created before the upgrade.

en: The payload for cluster GET now returns ips for all networks, not just the first one found for each instance. Bug 1642695
en_GB: The payload for cluster GET now returns IPs for all networks, not just the first one found for each instance. Bug 1642695

en: The user can create backup strategy to define the configurations for creating backups, e.g. the swift container to store the backup data. Users can also specify the container name when creating backups which takes precedence over the backup strategy configuration.
en_GB: The user can create a backup strategy to define the configurations for creating backups, e.g. the swift container to store the backup data. Users can also specify the container name when creating backups which take precedence over the backup strategy configuration.

en: This patch set implements the following functionality for Cassandra datastore. create/delete/get user list users change password grant/revoke/list access update attributes create/delete database list databases Notes on Cassandra users In Cassandra only SUPERUSERS can create other users and grant permissions to database resources. Trove uses the 'os_admin' superuser to perform its administrative tasks. It proactively removes the built-in 'cassandra' superuser on prepare. The users it creates are all 'normal' (NOSUPERUSER) accounts. The permissions it can grant are also limited to non-superuser operations. This is to prevent anybody from creating a new superuser via the Trove API. Updatable attributes include username and password. The configuration template had to be updated to enable authentication and authorization support (original configuration allowed anonymous connections). Default implementations used are authenticator org.apache.cassandra.auth.PasswordAuthenticator authorizer org.apache.cassandra.auth.CassandraAuthorizer The superuser password is set to a random Trove password which is then stored in a Trove-read-only file in '~/.cassandra/cqlshrc' which is also the default location for client settings. Notes on Cassandra keyspaces Cassandra stores replicas on multiple nodes to ensure reliability and fault tolerance. All replicas are equally important; there is no primary or master. A replication strategy determines the nodes where replicas are placed. The total number of replicas across the cluster is referred to as the replication factor. The above 'create database' implementation uses 'SimpleStrategy' with just a single replica on the guest machine. This is a very simplistic configuration only good for the most basic applications and demonstration purposes. SimpleStrategy is for a single data center only. The following system keyspaces have been included in the default 'ignore_dbs' configuration list and therefore excluded from all database operations 'system', 'system_auth', 'system_traces' Notes on user rename Cassandra does not have a native way for renaming users. The reason why Cassandra itself does not implement rename is apparently just lack of demand for that feature. We implement it by creating a new user, transferring permissions and dropping the old one (which also removes its existing permissions). I asked about the sanity of this rename approach on the Cassandra mailing list and IRC channel and there should not be anything inherently wrong with the proposed procedure. This method, however, requires the user to always provide a password. Additional notes Trove uses the official open-source Python driver for Cassandra to connect to the database and execute queries. The connection is implemented in CassandraConnection. It is now also used to obtain the current database status as opposed to the original method of parsing output of the client tool. The 'common/operating_system' module was extended with two new functions for reading/writing ini-style and YAML configuration files to/from Python dicts. Unit tests were added to 'guestagent/test_operating_system'. The existing Manager unit tests were extended to include the added functionality. Also includes some minor improvements to comments and log messages. Used the existing operating_system interface to update file ownership. The system module was removed and its contents moved to the Application class. This is to reduce the number of files and help facilitate overriding.
en_GB: This patch set implements the following functionality for Cassandra datastore. create/delete/get user list users change password grant/revoke/list access update attributes create/delete database list databases Notes on Cassandra users In Cassandra only SUPERUSERS can create other users and grant permissions to database resources. Trove uses the 'os_admin' superuser to perform its administrative tasks. It proactively removes the built-in 'cassandra' superuser on prepare. The users it creates are all 'normal' (NOSUPERUSER) accounts. The permissions it can grant are also limited to non-superuser operations. This is to prevent anybody from creating a new superuser via the Trove API. Updatable attributes include username and password. The configuration template had to be updated to enable authentication and authorization support (original configuration allowed anonymous connections). Default implementations used are authenticator org.apache.cassandra.auth.PasswordAuthenticator authorizer org.apache.cassandra.auth.CassandraAuthorizer The superuser password is set to a random Trove password which is then stored in a Trove-read-only file in '~/.cassandra/cqlshrc' which is also the default location for client settings. Notes on Cassandra keyspaces Cassandra stores replicas on multiple nodes to ensure reliability and fault tolerance. All replicas are equally important; there is no primary or master. A replication strategy determines the nodes where replicas are placed. The total number of replicas across the cluster is referred to as the replication factor. The above 'create database' implementation uses 'SimpleStrategy' with just a single replica on the guest machine. This is a very simplistic configuration only good for the most basic applications and demonstration purposes. SimpleStrategy is for a single data centre only. The following system keyspaces have been included in the default 'ignore_dbs' configuration list and therefore excluded from all database operations 'system', 'system_auth', 'system_traces' Notes on user rename Cassandra does not have a native way for renaming users. The reason why Cassandra itself does not implement rename is apparently just a lack of demand for that feature. We implement it by creating a new user, transferring permissions and dropping the old one (which also removes its existing permissions). I asked about the sanity of this rename approach on the Cassandra mailing list and IRC channel and there should not be anything inherently wrong with the proposed procedure. This method, however, requires the user to always provide a password. Additional notes Trove uses the official open-source Python driver for Cassandra to connect to the database and execute queries. The connection is implemented in CassandraConnection. It is now also used to obtain the current database status as opposed to the original method of parsing output of the client tool. The 'common/operating_system' module was extended with two new functions for reading/writing ini-style and YAML configuration files to/from Python dicts. Unit tests were added to 'guestagent/test_operating_system'. The existing Manager unit tests were extended to include the added functionality. Also includes some minor improvements to comments and log messages. Used the existing operating_system interface to update file ownership. The system module was removed and its contents moved to the Application class. This is to reduce the number of files and help facilitate overriding.

en: This would apply to any type of cluster that uses the galera strategy while setting the nics on a create call. When we called cast to set() the object was a list of lists. The set method can not has a list so this was causesing a unhashable error. The change is to make the instance_nics a list of strings (what we originaly expected) to resolve this issue. Bug 1570602.
en_GB: This would apply to any type of cluster that uses the Galera strategy while setting the nics on a create call. When we called cast to set() the object was a list of lists. The set method can not has a list so this was causing an unhashable error. The change is to make the instance_nics a list of strings (what we originally expected) to resolve this issue. Bug 1570602.

en: Trove admin user is able to remove the default configuration parameters for datastore version, e.g. ``trove-manage db_remove_datastore_config_parameters mysql 5.7.29``
en_GB: The Trove admin user is able to remove the default configuration parameters for datastore version, e.g. ``trove-manage db_remove_datastore_config_parameters mysql 5.7.29``

en: Use of JSON policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on migration of any custom policy files.
en_GB: Use of JSON policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on the migration of any custom policy files.

en: Vertica comes with a User Defined Load function that takes a URL as a load source. This can be used to load files that are stored in Swift. As this is a common use case, it is valuable to enable this by default. This can be done in the post-prepare method for Vertica. A new UDL_LIBS list has been added that describes any UDLs to be loaded into the database. This change only has one entry - the curl function.
en_GB: Vertica comes with a User Defined Load (UDL) function that takes a URL as a load source. This can be used to load files that are stored in Swift. As this is a common use case, it is valuable to enable this by default. This can be done in the post-prepare method for Vertica. A new UDL_LIBS list has been added that describes any UDLs to be loaded into the database. This change only has one entry - the curl function.

en: check if the user input is legal, currently, trove may have a  RCE vulnerability. more details see: `Stroy 2010004 <https://storyboard.openstack.org/#!/story/2010004>`__
en_GB: check if the user input is legal, currently, Trove may have a  RCE vulnerability. For more details see: `Stroy 2010004 <https://storyboard.openstack.org/#!/story/2010004>`__

en: explicitly specify utf8mb3 as character set for mysql
en_GB: explicitly specify utf8mb3 as the character set for MySQL
