--src-ip and --src-group were deprecated in 2016, change
to use --remote-ip and --remote-group, respectively.
Related to https://review.opendev.org/#/c/659400/
Change-Id: Ie609380b130410e3548eeacffd72871c6b5722ea
These were renamed to remove the quota_* prefix
and the old ones and the pick()'s can now be removed.
Change-Id: Ibe5b5f49386e101598afcab210944cdcf69c8eeb
Previously Tripleo validate-tempest role was used to run tempest
on tripleo jobs. Recently we are moving to os_tempest (an unified
role developed by openstack-ansible team).
It moves the vars to os_tempest.
Below is the other var changes:
run_tempest: false -> to disable validate-tempest role
use_os_tempest: true -> enable os_tempest
tempest_whitelist -> tempest_test_whitelist
Change-Id: Ifd19684f2b0a272b28248f70afd78c5be8330f5a
Signed-off-by: Chandan Kumar <chkumar@redhat.com>
Deprecated by Iefade0f0a9bb0ab83c0aba6c5f263bde240cf9a2 in Stein this
can now be removed in Train.
Depends-On: https://review.opendev.org/655170
Change-Id: I5b8a8173b4434442622ad0f5a018f6238a2648e2
Commit 958c5b2f35e0789b0e280ba1f7662ebe19e4bad6 accidentally added the
new cross_az_attach parameter in the deprecated sections. This commit
just moves it up so it's clear this parameter is not deprecated.
Change-Id: Ib32dc7f21c916190f952c1ae5a353434a6969616
nova-scheduler uses CONF.default_availabiliy_zone.
However, the required class was not included in scheduler.pp
This patch includes nova::availability_zone class in scheduler.pp.
Signed-off-by: Keigo Noha <knoha@redhat.com>
Closes-Bug: #1824273
Change-Id: Ia94a5d7baf1dd2efc8339475176a1e1c24ad99d0
Indicates that the nova-metadata API service has been deployed
per-cell, so that we can have better performance and data isolation in a
multi-cell deployment. Users should consider the use of this configuration
depending on how neutron is setup. If networks span cells, you might need
to run nova-metadata API service globally. If your networks are segmented
along cell boundaries, then you can run nova-metadata API service per cell.
When running nova-metadata API service per cell, you should also configure
each Neutron metadata-agent to point to the corresponding nova-metadata API
service.
Related-Bug: #1823760
Change-Id: Ia4dc22b2d013e00629f5945b230ab57a3e3a6465
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I2e692ba106aee68080f28cf181712d41a6cf373d
Sem-Ver: feature
These options are for libvirt's configuration file; and allow us to use
custom paths for these parameters, instead of relying on the default
ones.
Related-Bug: #1821139
Change-Id: I208bb53c2a270d770d114116fde3f062c0d66985
Adds the cross_az_attach parameter to allow configuring attach between
instance and volume in different availability zones.
Change-Id: I064f872e20537642880d5482cb9e0c2a801715ef
implements: blueprint split-controlplane-templates
The Placement service is currently scheduled to be extracted from the
Nova project during the Train cycle. Ahead of this the deployment of the
service using puppet-nova has now been deprecated in favour of the
puppet-placement module.
Change-Id: Iefade0f0a9bb0ab83c0aba6c5f263bde240cf9a2
The previous `compute` white list was resulting in the job timing out
more often than not. This change limits this white list to the compute
API and basic server ops scenario tests to ensure we no longer time out.
Change-Id: I7d4ac315d8ce0c9e1b651e58abfc569bbe3f7505
This changes all the puppet 3 validate_* functions
to use the validate_legacy function.
The validate_legacy function has been available since
about three years but require Puppet >= 4.4.0 and since
there is Puppet 4.10.12 as latest we should assume people
are running a fairly new Puppet 4 version.
This is the first step to then remove all validate function
calls and use proper types for parameter as described in spec [1].
[1] https://review.openstack.org/#/c/568929/
Change-Id: I53648532bc2aa7031f33b82e2b8486f6927be49d
To allow for the deprecation and future removal of any Placement service
deployment logic from puppet-nova this code first needs to be separated
into its own class.
Change-Id: Iadc2970afb65a6b3a1a3241147d042e6b04b0ad2
In Debian, the nova-serialproxy service is packaged together with the
other proxy services in a nova-consoleproxy package. This patch fixes
this issue.
Change-Id: Ib629a4fd15ec5236ba9b2b216c9cfd70a350e757
Service_token_roles_required missing in the server config file which
allows backwards compatibility to ensure that the service tokens are
compared against a list of possible roles for validity.
Change-Id: I826a09ede0d15502da69cd0b48c5e54854e07f6c
Closes-Bug: 1778198
Live migration is currently totally broken if a NUMA topology is
present. This affects everything that's been regrettably stuffed in with
NUMA topology including CPU pinning, hugepage support and emulator
thread support. Side effects can range from simple unexpected
performance hits (due to instances running on the same cores) to
complete failures (due to instance cores or huge pages being mapped to
CPUs/NUMA nodes that don't exist on the destination host).
Until such a time as we resolve these issues, we should alert users to
the fact that such issues exist. A workaround option is provided for
operators that _really_ need the broken behavior, but it's defaulted to
False to highlight the brokenness of this feature to unsuspecting
operators.
The related nova change is I217fba9138132b107e9d62895d699d238392e761
The proposed change exposes the 'enable_numa_live_migration'
workarounds option for TripleO deployment. By default this feature will be
disabled for NUMA topology instances.
Change-Id: I16794fbfef0e6e83d3fcebb9e6bc2fcf478ebf72
