As Nova user I would like to have ability to
configure cache parameters via Puppet, so we need
to add missing parameters to manifests.
Change-Id: I601163fd233396e456f459e58f39c7772e16ec81
This change updates the nova::keystone::auth class to include a
default service_name of 'nova' so that if a user changes the
auth_name, the service is still created as being related to 'nova'.
Change-Id: Iaf616a094bd2192fe0149307065cec11038d8c85
Closes-Bug: #1590040
https://review.openstack.org/229895 made sure nova networks could
only be created if the nova-network service was enabled. However,
it is still possible that Puppet tries to create them before the
service is started.
This patch should be backported to stable/mitaka and stable/liberty.
Change-Id: Iaf21b70f274d2c5769c6bb117697efe9e74873fd
This commit partially reverts original commit.
use_syslog option is not deprecated and still actual.
This reverts commit 9abc7531a94a7f8b983f93be426dbed3c7697e8d
Change-Id: I0bc443124077b663a9c9d85a0bf2772f476ae170
This may required in instances where socket.gethostname() (the default)
does not return a FQDN and an FQDN (or other identifer) is desired.
Change-Id: Icce3ebc401442651942f8de3eabffadaad812377
Add the parameter in order to Whether to use tunnelled migration,
where migration data is transported over the libvirtd connection.
Change-Id: I3498076b292e9dff88b9ad9d5c65c99a2a98cd7f
In the context of noVNC, numpy adds little performance according
to websockify maintainer: https://github.com/kanaka/websockify/issues/77
Change-Id: If35f10db90605ce3faa3555ac5689b631c9b51bf
Nova deprecated 2.0 API in Liberty and will remove it in Newton.
This patch does 3 things:
* in nova::keystone::auth, create nova API 2.1 endpoints by default and
not 2.0 anymore that is going to be removed.
puppet-keystone will update endpoints for the 'compute' service with
the new URL.
* in nova::keystone::auth, deprecate all parameters related to v3. They
are useless, since we now use v2.1 by default and it's the version
that is what v3 started out as.
Note: puppet-keystone won't remove the v3 endpoint. You can do it with
puppet-keystone or manually.
* deprecate osapi_v3 in nova::api. The parameter is useless and does not
need to bet set.
List of parameters deprecated:
* osapi_v3
* auth_name_v3
* service_description_v3
* service_name_v3
* public_url_v3
* internal_url_v3
* admin_url_v3
* configure_endpoint_v3
They have no effect and will be removed in a future release.
Change-Id: I8990ce21745fa7a995b92ed337622fa6ffc2756b
Offline/deleted hosts show as offline forever in the service list.
This undesirable output can be mitigated by offering a provider
that allows a user to mark such nova services as 'absent'.
Includes release note.
Change-Id: I303ab218bc6a48cf2c60727feecc522040a80a68
Related-Bug: #1471172
This change introduces new class nova::ironic::common which adds common
Ironic related parameters to nova.conf required for nova-api and nova-compute.
Change-Id: Ia878d19cffd833e9bf95d1b26ff0c2b6c02370d0
Closes-bug: #1581040
You see the following error when using puppet:
Error: Could not start Service[libvirt]: Execution of '/bin/systemctl
start libvirt-bin' returned 1: Job for libvirt-bin.service failed
because the control process exited with error code. See "systemctl
status libvirt-bin.service" and "journalctl -xe" for details.
This is because you cannot start the libvirt-bin service twice in a row.
root@pkvmci829:~# systemctl start libvirt-bin
root@pkvmci829:~# systemctl start libvirt-bin
Job for libvirt-bin.service failed because the control process exited
with error code. See "systemctl status libvirt-bin.service" and
"journalctl -xe" for details.
Systemd already is able to start libvirtd as a daemon. It does not need
the -d parameter added to /etc/default/libvirt-bin. This just causes
systemd to keep respawning libvirtd in a loop until it realizes that it
isn't working.
Change-Id: Iaffe85dda5c5bfed88f27602189aca074ec7aeda
Bindep is a binary automation tool used in openstack-infra. With it,
projects can better control the default packages installed into the
OS. Because we are using puppet, we actually don't want any packages
installed by default as to better test our manifests.
Change-Id: I278f72fce146a0b060ea002dd9bf87d311d8c73d
Co-Authored-By: Paul Belanger <pabelanger@redhat.com>
This option determines if the middleware should parse the
headers or not. Can be used in case if application is
behind the reverse proxy.
Change-Id: I22deb886706fe71115a04fb52a7051be4783a5c4
Related-bug: #1576740
Option "verbose" from group "DEFAULT" is deprecated for removal.
The parameter has no effect.
Deprecated verbose for logging and init
Remove verbose in README
Remove verbose from tests.
If this option is not set explicitly, there is no such warning.
Change-Id: If60ca414d4f7cc7bd50aafb9a9ac8b328b5b5c84
The rabbit_host parameter value is defined as
$::os_service_default by default, so fix it
in description.
Change-Id: I431c2aa5daad08e342bbc05ca098ccfbfaa46641
The listen parameter from nova::compute::serial has no effect anymore
and will be removed in future, please use proxyclient_address instead.
Change-Id: Ia30aeaf7d3d7b1961a8efa6e3fe6ccedfbb704ad
This commit adds support for the oslo.messaging amqp rpc_backend
which enables the AMQP 1.0 driver. A proposed feature for the
Newton oslo.messaging release is an update to the AMQP 1.0 driver
to support a stateless messaging interconnect for RPC traffic [1].
This patch:
* use oslo::messaging::amqp resource
* add new parameters for the oslo_messaging_amqp driver
* update spec tests for amqp as alternate rpc_backend
* add feature release note
[1] https://blueprints.launchpad.net/oslo.messaging/+spec/amqp-dispatch-router
Change-Id: I1bda9eb255e4e810f349c49780a34b116ea18a14
This reverts commit 271a2587a3.
This patch seems to have caused the TripleO upgrades job to fail
in that running Nova instances stopped working after an upgrade.
Could be there is a missing relationship or something in Puppet or
perhaps something else keystone related but updating to this
as a default seems it could break things.
Related bug: #1580076
Change-Id: I783fba6cbd3ba292d6ed64be2dd0772e20a0896d
The db_max_retries parameter regulates the number of reconnection
attempts performed after an error raised rather than at startup.
Change-Id: Ic5c7d1be866ab25f4bb01a89253a3db92e4ee6f5
Closes-Bug: 1579718
Relax beaker CLI tests so we tolerate warnings like:
"Ignoring domain related configs because identity API version is 2.0"
The warnings are present in aggregate & flavor tests.
Change-Id: I1376322147a66a817f52e3cf94f6043e37e799a3
Iury Gregory Melo Ferreira
Alexey Deryugin
Juan Antonio Osorio Robles
iberezovskiy
ZhongShengping
Jenkins
Emilien Macchi
Javier Pena
Marcus Furlong
Mathieu Gagné
Matthew Mosesohn
Denis Egorenko
Andrey Shestakov
Mark Hamzy
Mykyta Karpin
Andrew Smith
Dan Prince
Giulio Fidente