openstack-heat - en to en_GB translation catalogue (66 entries)

en: A new OS::Zun::Container resource is added that allows users to manage docker containers powered by Zun. This resource will have an 'addresses' attribute that contains various networking information including the neutron port id. This allows users to orchestrate containers with other networking resources (i.e. floating ip).
en_GB: A new OS::Zun::Container resource is added that allows users to manage Docker containers powered by Zun. This resource will have an 'addresses' attribute that contains various networking information including the Neutron port id. This allows users to orchestrate containers with other networking resources (i.e. floating ip).

en: A new ``OS::Keystone::Region`` resource that helps in managing the lifecycle of keystone region.
en_GB: A new ``OS::Keystone::Region`` resource that helps in managing the lifecycle of Keystone region.

en: A new ``OS::Neutron:AddressScope`` resource that helps in managing the lifecycle of neutron address scope. Availability of this resource depends on availability of neutron ``address-scope`` API extension. This resource can be associated with multiple subnet pools in a one-to-many relationship. The subnet pools under an address scope must not overlap.
en_GB: A new ``OS::Neutron:AddressScope`` resource that helps in managing the lifecycle of Neutron address scope. Availability of this resource depends on availability of Neutron ``address-scope`` API extension. This resource can be associated with multiple subnet pools in a one-to-many relationship. The subnet pools under an address scope must not overlap.

en: A new ``OS::Neutron:Segment`` resource to create routed networks. Availability of this resource depends on availability of neutron ``segment`` API extension.
en_GB: A new ``OS::Neutron:Segment`` resource to create routed networks. Availability of this resource depends on availability of Neutron ``segment`` API extension.

en: A new ``OS::Neutron:SubnetPool`` resource that helps in managing the lifecycle of neutron subnet pool. Availability of this resource depends on availability of neutron ``subnet_allocation`` API extension.
en_GB: A new ``OS::Neutron:SubnetPool`` resource that helps in managing the lifecycle of Neutron subnet pool. Availability of this resource depends on availability of neutron ``subnet_allocation`` API extension.

en: A new property, deployment_swift_data is added to the OS::Nova::Server and OS::Heat::DeployedServer resources. The property is used to define the Swift container and object name that is used for deployment data for the server. If unset, the fallback is the previous behavior where these values will be automatically generated.
en_GB: A new property, deployment_swift_data is added to the OS::Nova::Server and OS::Heat::DeployedServer resources. The property is used to define the Swift container and object name that is used for deployment data for the server. If unset, the fallback is the previous behaviour where these values will be automatically generated.

en: A new resource ``OS::Sahara::Job`` has been added, which allows to create and launch sahara jobs. Job can be launched with resource-signal.
en_GB: A new resource ``OS::Sahara::Job`` has been added, which allows to create and launch Sahara jobs. Job can be launched with resource-signal.

en: A new resource plugin ``OS::Keystone::Domain`` is added to support the lifecycle of keystone domain.
en_GB: A new resource plugin ``OS::Keystone::Domain`` is added to support the lifecycle of Keystone domain.

en: A stack can be searched for resources based on their name, status, type, action, id and physcial_resource_id. And this feature is enabled both in REST API and CLI. For more details, please refer orchestration API document and heat CLI user guide.
en_GB: A stack can be searched for resources based on their name, status, type, action, id and physical_resource_id. And this feature is enabled both in REST API and CLI. For more details, please refer orchestration API document and Heat CLI user guide.

en: Add ``group`` property to ``OS::Heat::MultipartMime``. This allow you to set group for entire multipart cofig resource like ``group`` property in ``OS::Heat::SoftwareConfig``. Aware that, you must make sure all configs in MultipartMime works with ``group``. Default value is ``Heat::Ungrouped``.
en_GB: Add ``group`` property to ``OS::Heat::MultipartMime``. This allow you to set group for entire multipart config resource like ``group`` property in ``OS::Heat::SoftwareConfig``. Aware that, you must make sure all configs in MultipartMime works with ``group``. Default value is ``Heat::Ungrouped``.

en: Add `tags` parameter for create and update keystone projects. Defined comma deliniated list will insert tags into newly created or updated projects.
en_GB: Add `tags` parameter for create and update Keystone projects. Defined comma delineated list will insert tags into newly created or updated projects.

en: Add `template_dir` to config. Normally heat has template directory `/etc/heat/templates`. This change makes it more official. In the future, it is possible to implement features like access templates directly from global template environment.
en_GB: Add `template_dir` to config. Normally Heat has template directory `/etc/heat/templates`. This change makes it more official. In the future, it is possible to implement features like access templates directly from global template environment.

en: Add a new property ``networks`` to resource OS::Zun::Container. This property is an ordered list of nics to be added to this container, with information about connected networks, fixed ips, and port. This property can be updated without replacement.
en_GB: Add a new property ``networks`` to resource OS::Zun::Container. This property is an ordered list of NICs to be added to this container, with information about connected networks, fixed IPs, and port. This property can be updated without replacement.

en: Add new ``OS::Barbican::GenericContainer`` resource for storing arbitrary barbican secrets.
en_GB: Add new ``OS::Barbican::GenericContainer`` resource for storing arbitrary Barbican secrets.

en: Add optional 'period' property for Monasca Notification resource. The new added property will now allow the user to tell Monasca the interval in seconds to periodically invoke a webhook until the ALARM state transitions back to an OK state or vice versa. This is useful when the user wants to create a stack which will automatically scale up or scale down more than once if the alarm state continues to be in the same state.  To conform to the existing Heat autoscaling behaviour, we manually create the monasca notification resource in Heat with a default interval value of 60.
en_GB: Add optional 'period' property for Monasca Notification resource. The new added property will now allow the user to tell Monasca the interval in seconds to periodically invoke a webhook until the ALARM state transitions back to an OK state or vice versa. This is useful when the user wants to create a stack which will automatically scale up or scale down more than once if the alarm state continues to be in the same state.  To conform to the existing Heat autoscaling behaviour, we manually create the Monasca notification resource in Heat with a default interval value of 60.

en: Added ``network`` attribute to OS::Neutron::Port resource. The new attribute returns the neutron network that owns the port. The following examples demonstrate some (not all) possible expressions. (Obtains the network, the MTU (Maximum transmission unit), the network tags and finally the l2_adjacency property)::
en_GB: Added ``network`` attribute to OS::Neutron::Port resource. The new attribute returns the Neutron network that owns the port. The following examples demonstrate some (not all) possible expressions. (Obtains the network, the MTU (Maximum Transmission Unit), the network tags and finally the l2_adjacency property)::

en: Added a new schema property tags, to parameters, to categorize parameters based on features.
en_GB: Added a new schema property tags, to parameters, to categorise parameters based on features.

en: Added new section ``permutations`` for ``repeat`` function, to decide whether to iterate nested the over all the permutations of the elements in the given lists. If 'permutations' is not specified, we set the default value to true to compatible with before behavior. The args have to be lists instead of dicts if 'permutations' is False because keys in a dict are unordered, and the list args all have to be of the same length.
en_GB: Added new section ``permutations`` for ``repeat`` function, to decide whether to iterate nested the over all the permutations of the elements in the given lists. If 'permutations' is not specified, we set the default value to true to compatible with before behaviour. The args have to be lists instead of dicts if 'permutations' is False because keys in a dict are unordered, and the list args all have to be of the same length.

en: Added stack API support to provide a swift container that contains the child templates and environment files. All files would be fetched and used (if required), unless they are superceded by files in files map.
en_GB: Added stack API support to provide a swift container that contains the child templates and environment files. All files would be fetched and used (if required), unless they are superseded by files in files map.

en: Adds REST api support to cancel a stack create/update without rollback.
en_GB: Adds REST API support to cancel a stack create/update without rollback.

en: Adds new 'max_server_name_length' configuration option which defaults to the prior upper bound (53) and can be lowered by users (if they need to, for example due to ldap or other internal name limit restrictions).
en_GB: Adds new 'max_server_name_length' configuration option which defaults to the prior upper bound (53) and can be lowered by users (if they need to, for example due to LDAP or other internal name limit restrictions).

en: Adds new resources for octavia lbaas service.
en_GB: Adds new resources for Octavia LBaaS service.

en: Force delete the nova instance. If a resource is related with a nova instance which is in 'SOFT_DELETED' status, the resource can't be deleted, when nova config 'reclaim_instance_interval'. so, force-delete the nova instance, and then all the resources are related with the instance would be processed properly.
en_GB: Force delete the Nova instance. If a resource is related with a Nova instance which is in 'SOFT_DELETED' status, the resource can't be deleted, when Nova config 'reclaim_instance_interval'. so, force-delete the Nova instance, and then all the resources are related with the instance would be processed properly.

en: Heat does not work with keystone identity federation. This is a known limitation as heat uses keystone trusts for deferred authentication and trusts don't work with federated keystone. For more details check `https://etherpad.openstack.org/p/pike-ptg-cross-project-federation`.
en_GB: Heat does not work with Keystone identity federation. This is a known limitation as Heat uses keystone trusts for deferred authentication and trusts don't work with federated Keystone. For more details check `https://etherpad.openstack.org/p/pike-ptg-cross-project-federation`.

en: If upgrading with pre-icehouse stacks which contain resources that create users (such as OS::Nova::Server, OS::Heat::SoftwareDeployment, and OS::Heat::WaitConditionHandle), it is possible that the users will not be removed upon stack deletion due to the removal of a legacy fallback code path. In such a situation, these users will require manual removal.
en_GB: If upgrading with pre-Icehouse stacks which contain resources that create users (such as OS::Nova::Server, OS::Heat::SoftwareDeployment, and OS::Heat::WaitConditionHandle), it is possible that the users will not be removed upon stack deletion due to the removal of a legacy fallback code path. In such a situation, these users will require manual removal.

en: Magnum recently changed terminology to more intuitively convey key concepts in order to align with industry standards. "Bay" is now "Cluster" and "BayModel" is now "ClusterTemplate". This release deprecates the old names in favor of the new.
en_GB: Magnum recently changed terminology to more intuitively convey key concepts in order to align with industry standards. "Bay" is now "Cluster" and "BayModel" is now "ClusterTemplate". This release deprecates the old names in favour of the new.

en: New resource ``OS::Neutron::Quota`` is added to manage neutron quotas.
en_GB: New resource ``OS::Neutron::Quota`` is added to manage Neutron quotas.

en: New resource ``OS::Senlin::Cluster`` is added to create a cluster in senlin. A cluster is a group of homogeneous nodes.
en_GB: New resource ``OS::Senlin::Cluster`` is added to create a cluster in Senlin. A cluster is a group of homogeneous nodes.

en: New resource ``OS::Senlin::Node`` is added to create a node in senlin. Node represents a physical object exposed by other OpenStack services.
en_GB: New resource ``OS::Senlin::Node`` is added to create a node in Senlin. Node represents a physical object exposed by other OpenStack services.

en: New resource ``OS::Senlin::Policy`` is added to create a policy in senlin. Policy is a set of rules that can be checked and/or enforced when an Action is performed on a Cluster.
en_GB: New resource ``OS::Senlin::Policy`` is added to create a policy in Senlin. Policy is a set of rules that can be checked and/or enforced when an Action is performed on a Cluster.

en: New resource ``OS::Senlin::Profile`` is added to create a profile in senlin. Profile is a module used for creating nodes, it's the definition of a node.
en_GB: New resource ``OS::Senlin::Profile`` is added to create a profile in Senlin. Profile is a module used for creating nodes, it's the definition of a node.

en: New resource ``OS::Senlin::Receiver`` is added to create a receiver in senlin. Receiver can be used to hook the engine to some external event/alarm sources.
en_GB: New resource ``OS::Senlin::Receiver`` is added to create a receiver in Senlin. Receiver can be used to hook the engine to some external event/alarm sources.

en: Nova has removed api extension support and its api bindings. Heat has now removed support for extensions from nova client plugin and the resource plugins using it.
en_GB: Nova has removed API extension support and its API bindings. Heat has now removed support for extensions from Nova client plugin and the resource plugins using it.

en: Now heat keystone user name charaters limit increased from 64 to 255. Any extra charaters will lost when truncate the name to the last 255 charaters.
en_GB: Now Heat Keystone user name characters limit increased from 64 to 255. Any extra characters will lost when truncate the name to the last 255 characters.

en: Now the ``OS::Neutron::Port`` type supports the ``no_fixed_ips`` property, which allows users to create a network port without any fixed ips.
en_GB: Now the ``OS::Neutron::Port`` type supports the ``no_fixed_ips`` property, which allows users to create a network port without any fixed IPs.

en: OS::Cinder::QoSAssociation resource plugin is added to support cinder QoS Specs Association with Volume Types, which is provided by cinder ``qos-specs`` API extension.
en_GB: OS::Cinder::QoSAssociation resource plugin is added to support cinder QoS Specs Association with Volume Types, which is provided by Cinder ``qos-specs`` API extension.

en: OS::Heat::ResourceGroup now supports a removal_policies_mode property. This can be used to optionally select different behavior on update where you may wish to overwrite vs append to the current policy.
en_GB: OS::Heat::ResourceGroup now supports a removal_policies_mode property. This can be used to optionally select different behaviour on update where you may wish to overwrite vs append to the current policy.

en: OS::Magnum::Cluster resource plugin added to support magnum cluster feature, which is provided by magnum ``cluster`` API.
en_GB: OS::Magnum::Cluster resource plugin added to support magnum cluster feature, which is provided by Magnum ``cluster`` API.

en: OS::Magnum::ClusterTemplate resource plugin added to support magnum cluster template feature, which is provided by magnum ``clustertemplates`` API.
en_GB: OS::Magnum::ClusterTemplate resource plugin added to support magnum cluster template feature, which is provided by Magnum ``clustertemplates`` API.

en: OS::Monasca::AlarmDefinition and OS::Monasca::Notification resource plug-ins are now supported by heat community as monasca became offcial OpenStack project.
en_GB: OS::Monasca::AlarmDefinition and OS::Monasca::Notification resource plug-ins are now supported by Heat community as Monasca became official OpenStack project.

en: OS::Neutron::FloatingIPPortForward added. This feature allows an operator to create port-forwarding rules in Neutron for their floating ips.
en_GB: OS::Neutron::FloatingIPPortForward added. This feature allows an operator to create port-forwarding rules in Neutron for their floating IPs.

en: OS::Neutron::QoSBandwidthLimitRule resource plugin is added to support neutron QoS bandwidth limit rule, which is provided by neutron ``qos`` API extension.
en_GB: OS::Neutron::QoSBandwidthLimitRule resource plugin is added to support Neutron QoS bandwidth limit rule, which is provided by Neutron ``qos`` API extension.

en: OS::Neutron::QoSPolicy resource plugin is added to support QoS policy, which is provided by neutron ``qos`` API extension.
en_GB: OS::Neutron::QoSPolicy resource plugin is added to support QoS policy, which is provided by Neutron ``qos`` API extension.

en: OS::Nova::Server now supports ephemeral_size and ephemeral_format properties for block_device_mapping_v2 property. Property ephemeral_size is integer, that require flavor with ephemeral disk size greater that 0. Property ephemeral_format is string with allowed values ext2, ext3, ext4, xfs and ntfs for Windows guests; it is optional and if has no value, uses default, defined in nova config file.
en_GB: OS::Nova::Server now supports ephemeral_size and ephemeral_format properties for block_device_mapping_v2 property. Property ephemeral_size is an integer, that requires a flavour with an ephemeral disk size greater that 0. Property ephemeral_format is a string with allowed values ext2, ext3, ext4, xfs and ntfs for Windows guests; it is optional and if it has no value, it uses defaults defined in nova config file.

en: Operators can now apply different authorization policies to each action supported by the action API (``actions:suspend`` for suspend, ``actions:resume`` for resume, ``actions:check`` for check, ``actions:cancel_update`` for cancel operation and roll back, and ``actions:cancel_without_rollback`` for cancel operation without rolling back). The default for each is to use the existing ``actions:action`` rule that was previously the only way to specify policy for actions.
en_GB: Operators can now apply different authorisation policies to each action supported by the action API (``actions:suspend`` for suspend, ``actions:resume`` for resume, ``actions:check`` for check, ``actions:cancel_update`` for cancel operation and roll back, and ``actions:cancel_without_rollback`` for cancel operation without rolling back). The default for each is to use the existing ``actions:action`` rule that was previously the only way to specify policy for actions.

en: Resource ``OS::Neutron::Net`` now supports ``l2_adjacency`` atribute on whether L2 connectivity is available across the network or not.
en_GB: Resource ``OS::Neutron::Net`` now supports ``l2_adjacency`` attribute on whether L2 connectivity is available across the network or not.

en: Start using reno to manage release notes.
en_GB: Start using Reno to manage release notes.

en: Support to managing rbac policy for 'qos_policy' resource, which allows to share Neutron qos policy to subsets of tenants.
en_GB: Support to managing RBAC policy for 'qos_policy' resource, which allows to share Neutron QoS policy to subsets of tenants.

en: Supports internal DNS resolution and integration with external DNS services for neutron resources. Template authors can use the ``dns_name`` and ``dns_domain`` properties of neutron resource plugins for this functionality.
en_GB: Supports internal DNS resolution and integration with external DNS services for Neutron resources. Template authors can use the ``dns_name`` and ``dns_domain`` properties of Neutron resource plugins for this functionality.

en: Supports to get the webmks console url for OS::Nova::Server resource. And this requires nova api version equal or greater than 2.8.
en_GB: Supports to get the WebMKS console URL for OS::Nova::Server resource. And this requires Nova api version equal or greater than 2.8.

en: Template validation is improved to ignore the given set of error codes. For example, heat will report template as invalid one, if it does not find any required OpenStack services in the cloud deployment and while authoring the template, user might wants to avoid such scenarios, so that (s)he could create valid template without bothering about run-time environments. Please refer the API documentation of validate template for more details.
en_GB: Template validation is improved to ignore the given set of error codes. For example, Heat will report template as invalid one, if it does not find any required OpenStack services in the cloud deployment and while authoring the template, user might wants to avoid such scenarios, so that (s)he could create valid template without bothering about run-time environments. Please refer the API documentation of validate template for more details.

en: The 'attachments' attribute of OS::Cinder::Volume has been deprecated in favor of 'attachments_list', which has the correct type of LIST. This makes this data easier for end users to process.
en_GB: The 'attachments' attribute of OS::Cinder::Volume has been deprecated in favour of 'attachments_list', which has the correct type of LIST. This makes this data easier for end users to process.

en: The Heat plugin in Horizon has been replaced with a new stand-alone Horizon plugin, heat-dashboard. You can see more detail in the heat-dashboard repository (https://git.openstack.org/cgit/openstack/heat-dashboard).
en_GB: The Heat plugin in Horizon has been replaced with a new stand-alone Horizon plugin, Heat-dashboard. You can see more detail in the Heat-dashboard repository (https://git.openstack.org/cgit/openstack/heat-dashboard).

en: The ceilometer client plugin is no longer provided, due to the Ceilometer API no longer being available from Queens and the python-ceilometerclient library being unmaintained.
en_GB: The Ceilometer client plugin is no longer provided, due to the Ceilometer API no longer being available from Queens and the python-ceilometerclient library being unmaintained.

en: The database migration engine has changed from `sqlalchemy-migrate`__ to `alembic`__. For most deployments, this should have minimal to no impact and the switch should be mostly transparent. The main user-facing impact is the change in schema versioning. While sqlalchemy-migrate used a linear, integer-based versioning scheme, which required placeholder migrations to allow for potential migration backports, alembic uses a distributed version control-like schema where a migration's ancestor is encoded in the file and branches are possible. The alembic migration files therefore use a arbitrary UUID-like naming scheme and the ``heat-manage db_sync`` command now expects such an version when manually specifying the version that should be applied. For example::
en_GB: The database migration engine has changed from `sqlalchemy-migrate`__ to `alembic`__. For most deployments, this should have minimal to no impact and the switch should be mostly transparent. The main user-facing impact is the change in schema versioning. While sqlalchemy-migrate used a linear, integer-based versioning scheme, which required placeholder migrations to allow for potential migration backports, alembic uses a distributed version control-like schema where a migration's ancestor is encoded in the file and branches are possible. The alembic migration files, therefore, use an arbitrary UUID-like naming scheme and the ``heat-manage db_sync`` command now expects such a version when manually specifying the version that should be applied. For example::

en: The default policies provided by heat api have been updated to add support for default roles and system scope. This is part of a broader community effort to support read-only roles and implement secure, consistent default policies.
en_GB: The default policies provided by Heat API have been updated to add support for default roles and system scope. This is part of a broader community effort to support read-only roles and implement secure, consistent default policies.

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 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 backwards-compatible way.

en: The following resources types are now hidden. Neutron LBaaS v2 was already retired thus these resource types can no longer be used.
en_GB: The following resource types are now hidden. Neutron LBaaS v2 was already retired thus these resource types can no longer be used.

en: The ordering in the list of segments returned by ``OS::Neutron::Net`` resources is not predictable. Stack updates changeing attributes of the network can cause the list of segments to shift.
en_GB: The ordering in the list of segments returned by ``OS::Neutron::Net`` resources is not predictable. Stack updates changing attributes of the network can cause the list of segments to shift.

en: The ordering is now slightly more predictable, segments with name=``None`` are now placed first in the list. This doesn't guarantee the order, but typically only the segment implicitly created by neutron has no name attribute set. The template author should ensure other segments on the network does have a name set, so that the implicit segment will always be index 0. Resolving attributes of the implcitly created segment on the network resource can then predictibly happen using index 0. See `bug: 1894920 <https://bugs.launchpad.net/tripleo/+bug/1894920>`_.
en_GB: The ordering is now slightly more predictable, segments with name=``None`` are now placed first in the list. This doesn't guarantee the order, but typically only the segment implicitly created by neutron has no name attribute set. The template author should ensure other segments on the network does have a name set, so that the implicit segment will always be index 0. Resolving attributes of the implicitly created segment on the network resource can then predictably happen using index 0. See `bug: 1894920 <https://bugs.launchpad.net/tripleo/+bug/1894920>`_.

en: There was a mismatch between the way heat create role behaved with the templates or with the openstack CLI on what relates to the default domain if the domain is not specified on both cases the CLI will not assign on to the created new role but the heat templates will assign the "default" domain
en_GB: There was a mismatch between the way heat create role behaved with the templates or with the OpenStack CLI on what relates to the default domain if the domain is not specified on both cases the CLI will not assign on to the created new role but the heat templates will assign the "default" domain

en: Threshold alarm which uses ceilometer API is deprecated in aodh since Ocata. Please use ``OS::Aodh::GnocchiAggregationByResourcesAlarm`` in place of ``OS::Aodh::Alarm``.
en_GB: Threshold alarm which uses the Ceilometer API is deprecated in Aodh since Ocata. Please use ``OS::Aodh::GnocchiAggregationByResourcesAlarm`` in place of ``OS::Aodh::Alarm``.

en: When 'nested_depth' is set the response also includes an extra entry in the 'links' list with 'rel' set to 'root_stack'. This can be used by client side implementations to detect whether it is necessary to fall back to client-side recurisive event fetching.
en_GB: When 'nested_depth' is set the response also includes an extra entry in the 'links' list with 'rel' set to 'root_stack'. This can be used by client side implementations to detect whether it is necessary to fall back to client-side recursive event fetching.

en: ``personality`` property of ``OS::Nova::Server`` is now deprecated, please use ``user_data`` or ``metadata`` instead. If that property really required, use config ``max_nova_api_microversion`` to set the maximum nova API microversion <2.57 for nova client plugin to support personality property.
en_GB: ``personality`` property of ``OS::Nova::Server`` is now deprecated, please use ``user_data`` or ``metadata`` instead. If that property really required, use config ``max_nova_api_microversion`` to set the maximum nova API microversion <2.57 for Nova client plugin to support personality property.

en: file injection is deprecated in compute api. Deprecating injected_files, injected_file_content_bites, and injected_file_path_bytes properties accordingly in OS::Nova::Quota resource.
en_GB: file injection is deprecated in compute API. Deprecating injected_files, injected_file_content_bites, and injected_file_path_bytes properties accordingly in OS::Nova::Quota resource.

en: nova.host constraint is added to support to validate host attribute which is provided by nova ``host`` API extension.
en_GB: nova.host constraint is added to support to validate host attribute which is provided by Nova ``host`` API extension.
