The oslo.cache 3.7.0 release introduced some options for redis backend
and redis sentinel backend. This introduces for these parameters.
Depneds-on: https://review.opendev.org/910629
Change-Id: I6c7ca526af7ddba27660791c23d1895d668b460b
... as is described. This option should be set to an appropriate key
value and the previous default (False) is not suitable for production
use.
Change-Id: Ic54025f2b6c1d023a8458491e3f26dda8adbceb0
Some services such as ceilometer-polling requires valid identity, so
we should ensure the identity resources are created before the services
are started.
Change-Id: Ifff2d097efa97156023b9bdc5ff62332f7875cac
The purge_config parameters only accept boolean values. This enforces
that using the typed parameters.
Change-Id: Ic78d8c273f9dfd5d979b2e449fc36ec9aa77f262
This parameter requires an array value. Let's validate the input at
the parameter layer to avoid unexpected failure within the lower logic.
Change-Id: Ib370a7c6930398675e8c18011e9ea8d5a90d0525
Upon enabling this parameter in all namespaces, ceilometer
agents(central, compute, ipmi) will be able to identify users
and project names in the metrics generated from their nodes.
Without this change, the parameter is missing in compute and
ipmi namespace.
Change-Id: I0c047e9c8e33c05247d7af69d2a80e7cc22a0304
This ensures the parameters used by if-else logic accept only boolean
values because non-boolean can result in unexpected behavior.
Change-Id: Iaf3c11b61dc738d267282a6bc1d445a554695178
This change introduces capability to use separate polling agents
(central, compute and ipmi) instead of the single polling service.
Change-Id: Idaa46ad71f4bedaca91b75a732649de967663659
Ceilometer no longer requires its own database since metric/event
storage was offloaded to Gnocchi/Panko. These implementations were
formally deprecated during the previous cycle[1] so can be removed.
This also updates the outdated example manifests to adapt to
the removal and the recent refactoring.
[1] 60882c29df
Change-Id: Id18b9221703eda9311b81c5a5dfdd41cc68f5424
... because these parameters were deprecated during the previous
cycle[1] and the feature has been removed from Ceilometer already.
[1] e5ce40b16d
Change-Id: Ibaba550aa9a13c7b1afb62970e391c1d4beb2f08
Enabling this parameter will identify user and project
names from the polled metrics [1].
These details are collected by making additional requests
to keystone service, depending upon the scale of environment,
number of projects/users and the count of metrics polled in
every iteration, enabling this could overwhelm the keystone
service.
[1] Iee5dbf09a1fd3ac571746fc66d2683eb8e6a1b27
Depends-on: https://review.opendev.org/852948
Signed-off-by: Yadnesh Kulkarni <ykulkarn@redhat.com>
Change-Id: I045c7cd7a86d0f7f97a9078cbfc74353dcff0eb8
This is follow-up of e5ce40b16d and now
enforces that the parameters are removed from ceilometer.conf because
these were already removed from ceilometer and no longer used.
Depends-on: https://review.opendev.org/840808
Change-Id: I4d9196133ead84d4b388929231ce970882fcaaa6
... because the parameter was deprecated during Wallaby cycle[1] in
favor of the new workers parameter.
[1] 15921006c5
Change-Id: I787bbe850cfcca737b9ad9de5db676b868549f2e
... because it was deprecated during Xena cycle[1] in favor of the new
ceilometer::coordination class.
[1] 1155b41db0
Change-Id: I0885b79bd83bcc3b41b8da0bd0fd00f29d176f13
Since metric/event storage was offloaded to Gnocchi/Panko, ceilometer
no longer requires its own backend storage.
Change-Id: Idf9904e7e8f1b5eca3f25cd37fb83e9adbca0995
This change refactors how the ceilometer service user and group are
managed.
- The ceilometer service user and group are created by the common
package. While the user resource should still be declared to manage
its group membership, we don't need the group resource.
- Introduces the configuration knob to disable user/group management.
This would be useful in the case where all service users are
declared externally.
Change-Id: Iaabe5b02f0ebd782debd0f3ca41e2fdafbf9c80f
... because these options were deprecated during the Yoga cycle when
GenericHardwareDeclarativePollster was deprecated[1].
[1] d10f6ca32fd9dfe5100cb54531adb4bba866edf8
Change-Id: I2bf6423d54234822b05a1a22f3cc29d0f7a3c1e7
After spending huge effort to understand the exact requirements to
enforce SRBAC, we learned it's very difficult to find the required
scope in each credential. This requires understanding implementation of
client-side as well as server-side, and requirement might be different
according to the deployment architecture or features used.
Instead of implementing support based on the actual implementation,
this introduces support for system scope credentials to all places
where keystone user credential is defined, and make all credential
configurations consistent.
Change-Id: I3a659a6b43d9c47e88334c24fb866a73a8f24a24
Zuul