Add log_line_prefix parameter for postgresql.conf #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the patch that added SSL support for rabbitmq, the migration revision was set incorrectly. This patch corrects the revision.
The original patch that added SSL support for rabbitmq missed the oslo_messaging_rabbitmq settings in glance-registry.conf. This patch corrects the mistake.
Fix mistakes from rabbitmq SSL addition
…033268) During node upgrade, we're executing chef-client from crowbar_join. If node reboots in this stage, upgrade script that executed this crowbar_join will be interrupted and cannot finish.
This is tech preview, so it doesn't hurt to expose more things by default.
We have to look inside the output of fetch_rabbitmq_settings output for rabbitmq configuration.
Do not assume swift-proxy node is also rabbitmq node
upgrade: Do not reboot XEN node from the first chef-client run
monasca: Add support for monasca-log-agent
* Deploy grafana alongside horizon * Add monitoring dashboards to Grafana
monasca: Remove unused api recipe
The ha recipe of the rabbitmq cookbook forcibly changes the IDs of the rabbitmq user and group after rabbitmq is installed. If we try to change group ownership of a file after rabbitmq is installed but before the rabbitmq group's gid is changed, the file will be left with just an apparently-random gid as its group. This was happening to the rabbitmq crowbar-generated private SSL key, which caused rabbitmq to be unable to read its own key. Subsequently, the memcached package was installed which scooped up the gid and the SSL key then became apparently owned by the memcached group. This patch simply delays generation of the SSL key pair until after the ha recipe has been able to muck with the rabbitmq user and group.
monasca: choose proper monitoring role node for monasca-server
Horizon Monasca integration
Ansible installer integration for Monasca
Enable users to specify the max_over_subscription_ratio when using
netapp driver. If other drivers needed this configuration value they
would add max_over_subscription_ratio to their configuration and the
template will render the value to the configuration file. So if for a
specific volume
volume[volume['backend_driver']]['max_over_subscription_ratio']
exists, then it's value will be included.
Please note that an integer is used for this number whereas OpenStack
will interpret this as a float.
CrowbarPacemakerSynchronization (that implements crowbar_pacemaker_sync_mark) has a generic check for node being part of a cluster. However, if a node is part of a cluster, but certain component is not deployed as Higly Available, sync marks should not be used at all.
This patch updates the grafana monasca dashboard to reflect the changes on the Metrics Api replacement from java to python
This file should not be installed by the package, as we don't want package installation to activate new services. so the attempt at deleting it is obsolete and this needs to be fixed in packaging instead.
When searching, the role is called 'monasca-server' and not 'monasca_server'.
tempest: Fix spelling of the monasca-server role
Tempest seems to pass with this change. partial revert: crowbar@eef7a80
heat: revert to using older config options
Allow deployment of OpenStack roles to SP3 nodes only.
Until volume encryption is supported for RBD in Nova (i.e. through qemu native RBD encryption), the tempest tests that cover this scenario will have to be skipped in Ceph environments.
Before this patch, we modified the role and saved it which caused the crowbar-revision to increase, which could lead to desynchronization when applying a barclamp to a subset of the keystone-server nodes. This patch avoids that by directly saving the endpoint information to the keystone-server nodes after the chef run, plus as a side effect, simplifies the code by avoiding any endpoint attributes modification before the chef run is done as its not really needed.
Tempest: disable encryption for RBD volumes
This change move the double quotes into the brackets.
keystone: better keystone http/https change logic (bsc#1044266)
In HA clouds a given service may be up on one controller and down on another. In this case, the behaviour of the Grafana dashboard is undefined since it may use the value from either http_status metric for displaying the service's status. By computing the maximum over all status checks we get a more accurate reading, i.e. the status transitions to DOWN if any backend is down in the time period under scrutiny and remains UP otherwise.
horizon: fix Openstack Grafana for HA clouds
monasca: Fix the host configuration of curator
* Added tailor made template for monasca-reconfigure script on monasca-server node. * Run monasca-reconfigure on monasca-server node instead of creating checks in chef. * Removed monitor_monasca recipe * Added Kibana HTTP check (Kibana plugin for monasca-setup does not create it) * Added elastisearch check setup resource/provider * Fixed some metric names in Monasca dashboard view definition
Configuration file for monasca-ui was missing KIBANA_POLICY_SCOPE and KIBANA_POLICY_RULE variables that are used when taking a decison wheter or not given user should see buttont that opens up Kibana. Depends-On: https://review.openstack.org/#/c/472575/
Use the nonversioned packages whenever possible.
monasca: show Monasca barclamp
postgresql: Bump the database version for SLES12SP3
monasca: Register logs endpoints in keystone
monasca: Specify policy values for kibana button
monasca: Hide password in SMTP configuration
monasca: Complete self monitoring dashboard
Add log_line_prefix parameter for postgresql.conf in json and schema file for databse barclamp.
|
sorry, wrong branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add log_line_prefix parameter for postgresql.conf
in json and schema file for databse barclamp.
Issue #46