Fix duplicate words
This change fixes duplicate consecutive words from docs as well as code. Signed-off-by: Rajesh Tailor <ratailor@redhat.com> Change-Id: I236ff41fccf831023b6f85840097148a30e84743
This commit is contained in:
@@ -43,7 +43,7 @@ Extended resource request
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
It is expected that neutron 20.0.0 (Yoga) will implement an extended resource
|
||||
request format via the the ``port-resource-request-groups`` neutron API
|
||||
request format via the ``port-resource-request-groups`` neutron API
|
||||
extension. As of nova 24.0.0 (Xena), nova already supports this extension if
|
||||
every nova-compute service is upgraded to Xena version and the
|
||||
``[upgrade_levels]/compute`` configuration does not prevent the computes from
|
||||
|
||||
@@ -615,7 +615,7 @@ Here are four possible values allowed for ``hw:viommu_model``
|
||||
**smmuv3**
|
||||
Supported on Libvirt since 5.5.0, for ARM virt guests.
|
||||
**intel**
|
||||
Supported for for Q35 guests.
|
||||
Supported for Q35 guests.
|
||||
|
||||
**auto**
|
||||
This option will translate to ``virtio`` if Libvirt supported,
|
||||
|
||||
@@ -70,7 +70,7 @@ Extended resource request
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
It is expected that neutron 20.0.0 (Yoga) will implement an extended resource
|
||||
request format via the the ``port-resource-request-groups`` neutron API
|
||||
request format via the ``port-resource-request-groups`` neutron API
|
||||
extension. As of nova 24.0.0 (Xena), nova already supports this extension if
|
||||
every nova-compute service is upgraded to Xena version and the
|
||||
:oslo.config:option:`upgrade_levels.compute` configuration does not prevent
|
||||
|
||||
@@ -78,7 +78,7 @@ Configuring a flavor or image
|
||||
:nova:extra-spec:`hw:cpu_realtime`. Starting in Victoria, it is possible
|
||||
to omit this when an emulator thread policy is configured using the
|
||||
:nova:extra-spec:`hw:emulator_threads_policy` extra spec, thus allowing all
|
||||
guest cores to be be allocated as real-time cores.
|
||||
guest cores to be allocated as real-time cores.
|
||||
|
||||
.. versionchanged:: 22.0.0 (Victoria)
|
||||
|
||||
|
||||
@@ -649,7 +649,7 @@ class ResourceTracker(object):
|
||||
|
||||
# NOTE(stephenfin): This runs on the destination, before we return to
|
||||
# the source and resume the instance there. As such, the migration
|
||||
# isn't really really reverted yet, but this status is what we use to
|
||||
# isn't really reverted yet, but this status is what we use to
|
||||
# indicate that we no longer needs to account for usage on this host
|
||||
migration.status = 'reverted'
|
||||
migration.save()
|
||||
|
||||
@@ -827,7 +827,7 @@ emulator threads.
|
||||
The behavior of this option depends on the definition of the deprecated
|
||||
``vcpu_pin_set`` option.
|
||||
|
||||
* If ``vcpu_pin_set`` is not defined, ``[compute] cpu_shared_set`` will be be
|
||||
* If ``vcpu_pin_set`` is not defined, ``[compute] cpu_shared_set`` will be
|
||||
used to provide ``VCPU`` inventory and to determine the host CPUs that
|
||||
unpinned instances can be scheduled to. It will also be used to determine the
|
||||
host CPUS that instance emulator threads should be offloaded to for instances
|
||||
|
||||
@@ -1313,7 +1313,7 @@ class PlacementInstanceHelperMixin(InstanceHelperMixin, PlacementHelperMixin):
|
||||
given flavor (assumes a single instance on the hypervisor).
|
||||
|
||||
:param compute_node_uuid: UUID of the ComputeNode to check.
|
||||
:param flavor: "flavor" entry dict from from GET /flavors/{flavor_id}
|
||||
:param flavor: "flavor" entry dict from GET /flavors/{flavor_id}
|
||||
:param volume_backed: True if the flavor is used with a volume-backed
|
||||
server, False otherwise.
|
||||
"""
|
||||
|
||||
@@ -6925,9 +6925,8 @@ class _ComputeAPIUnitTestMixIn(object):
|
||||
# This test checks the following scenario:
|
||||
# The instance is not mapped to a cell, so it should be retrieved from
|
||||
# a BuildRequest object. However the BuildRequest does not exist
|
||||
# because the instance was put in a cell and mapped while while
|
||||
# attempting to get the BuildRequest. So pull the instance from the
|
||||
# cell.
|
||||
# because the instance was put in a cell and mapped while attempting
|
||||
# to get the BuildRequest. So pull the instance from the cell.
|
||||
self.useFixture(nova_fixtures.AllServicesCurrent())
|
||||
build_req_obj = fake_build_request.fake_req_obj(self.context)
|
||||
instance = build_req_obj.instance
|
||||
|
||||
@@ -126,7 +126,7 @@ class HostsScopeTypePolicyTest(HostsPolicyTest):
|
||||
|
||||
|
||||
class HostsScopeTypeNoLegacyPolicyTest(HostsScopeTypePolicyTest):
|
||||
"""Test Hosts APIs policies with with no legacy deprecated rules
|
||||
"""Test Hosts APIs policies with no legacy deprecated rules
|
||||
and scope checks enabled which means scope + new defaults. So
|
||||
only system admin is able to perform hosts Operations.
|
||||
"""
|
||||
|
||||
@@ -2277,7 +2277,7 @@ class LibvirtDriver(driver.ComputeDriver):
|
||||
'disk_bus': disk_bus,
|
||||
'device_type': device_type}
|
||||
|
||||
# Note(cfb): If the volume has a custom block size, check that that we
|
||||
# Note(cfb): If the volume has a custom block size, check that we
|
||||
# are using QEMU/KVM. The presence of a block size is considered
|
||||
# mandatory by cinder so we fail if we can't honor the request.
|
||||
data = {}
|
||||
|
||||
Reference in New Issue
Block a user