Add parameters to configure tasks & taskflow executor. Allows mainly to
allow enabling automatic image conversion at import using the
Use glance::<service>::authtoken to configure keystone_authtoken
section in glance configs, with all parameters required
to configure keystonemiddleware.
Also changed auth_type to auth_strategy, because auth_type is
related to keystone authentication.
Glance is now using the HTTPProxyToWSGI middleware from
oslo.middlware in its default api-paste configuration . This commit
gives us the ability to enable/disable that middleware.
We had a prelude note when releasing Mitaka. This note
keep showing-up at every release while we're on Newton now.
We don't need a prelude release note, we already have nice sections
for every note we push.
This patch aims to remove this prelude starting from Newton.
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
This patch switches the service name from 'Image Service' to
just 'glance' so that it matches what we do for other services.
Typically we use the project (auth) name for the service_name.
Not having a consistent catalog can cause failure to find
endpoints for some services. Mistral for example would fail
to lookup the glance endpoint due to it being set as 'Image Service'
rather than 'glance'.
This change updates glance::keystone::auth to include the
user-provided auth_name as a parameter for the service_identity
provider. Hardcoding the namevar of that resource as was agreed. the
service_name parameter was not undef as in other resources, so the
name was left as-is. And we no longer pick a service_name out of the
service_name and auth_name; now only the service_name is taken into
The README file refers to an invalid *_address parameters
when *_url parameters should be used. The example in the
manifest does not show a password listed (which is required).
In glance, user can specify the desired id when creating
a new image. This can be convenient for some cases where
users want predictable ids for image, as referencing ramdisk_id
or kernel_id for AMI images.
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.
Co-Authored-By: Paul Belanger <email@example.com>
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
The db_max_retries parameter regulates the number of reconnection
attempts performed after an error raised rather than at startup.
Co-Authored-By: Giulio Fidende <firstname.lastname@example.org>
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 the images test.
* switch messaging related parameters to $::os_service_default
as they are used in oslo::messaging_rabbit define
* update unit tests
* update docs for notify::rabbitmq class
* drop deprecated rabbit_durable_queues parameter
* fix notification parameters according to mitaka config file
It appears that the resources decleration, that made purge_config work,
was accidently removed. I am adding it back so that the option will work
again. This resources decleration was setting the purge flag with a
boolean, so that inifile would handle it.
* Adding in spec tests
https://review.openstack.org/298718 changed the way images are listed,
by removing the '--long' parameter. This breaks when called by the
openstacklib provider, because that was the "properties" argument in
so the command-line used '' as a last argument, causing the failure.
This will require a stable/mitaka backport.
They bring no value in our CI, we already test a full deployment of
Glance and workflow of image upload, we don't need them.
Moreover, they make our life complicated when debbuging CI issues.
Let's drop the tests.