Project

General

Profile

Actions
Copy link

User story #8873

closed

Allow to customize reports database name and user to ease a separate database

Added by Alexis Mousset over 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
System integration
Target version:
3.1.13
Pull Request:
https://github.com/Normation/cf-clerk...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Currently, the database name and the user name (rudder and rudder) are set in rudder-web.properties and rsyslog.d/rudder.conf. The rsyslog file is templated and the name and user are hardcoded in the source template, which makes it impossible to use different values.

This is a stopblocker when one wants to run several Rudder instance on the same database server, for example for dev and test.

A possible workaround is to edit /var/rudder/configuration-repository/techniques/system/distributePolicy/1.0/rudder-rsyslog-root.st on the root server and set the right values. This will be overwritten during each update though.

We will add two system variables: RUDDER_REPORTS_DB_NAME and RUDDER_REPORTS_DB_USER

Subtasks 9 (0 open — 9 closed)

User story #8847: Document the usage of a separate database from Rudder server rootReleasedJonathan CLARKE2016-08-25Actions
Bug #8898: Clear caches after restarting rudder in separate database setup docReleasedJonathan CLARKE2016-08-25Actions
User story #8880: Improve the documentation for a separate databaseReleasedJonathan CLARKE2016-08-23Actions
User story #8881: The database name and user can not be changed: rudder-web partReleasedVincent MEMBRÉ2016-08-23Actions
User story #8882: Use system variables to configure postgres db name and user for rsyslogReleasedJonathan CLARKE2016-09-02Actions
User story #8938: Use system variables to configure postgres db name and user for rsyslogReleasedAlexis Mousset2016-09-02Actions
User story #8884: Change .pgpass configuration to use the right valuesReleasedJonathan CLARKE2016-08-23Actions
User story #8888: The database name and user can not be changed: rudder-web part, branch 3.2ReleasedVincent MEMBRÉ2016-08-24Actions
Bug #8906: Replace values in rsyslog rudder-reports config file ReleasedJonathan CLARKE2016-08-26Actions
Actions
Copy link
 #1

Updated by Alexis Mousset over 8 years ago

  • Tracker changed from Bug to User story
Actions
Copy link
 #2

Updated by Alexis Mousset over 8 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Alexis Mousset over 8 years ago

  • Subject changed from Make the databse name and user configurable to Make the database name and user configurable
Actions
Copy link
 #4

Updated by François ARMAND over 8 years ago

The solution is to give database name and user as technique parameters, and use them in corresponding system technique.

I'm going to use that ticket for the rudder update.

Actions
Copy link
 #5

Updated by François ARMAND over 8 years ago

  • Tracker changed from User story to Bug
  • Subject changed from Make the database name and user configurable to The database name and user can not be changed
  • Description updated (diff)
  • Target version changed from 3.1.13 to 2.11.24
  • Reproduced set to No
Actions
Copy link
 #6

Updated by François ARMAND over 8 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #7

Updated by François ARMAND over 8 years ago

Some more thinking: we already get contextual information for that script, see:

:msg, ereregex, "R: @@[ a-zA-Z0-9_\-]+?@@[a-zA-Z0-9_\-]{1,64}?@@[a-zA-Z0-9\-]+@@[a-zA-Z0-9\-]+?@@[0-9]+?@@.*?@@.*?@@[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}[+-][0-9]{1,2}:[0-9]{2}##[a-zA-Z0-9\-]+?@#.*"  :ompgsql:${install_rsyslogd.rudder_postgres_server},rudder,rudder,${p.psql_password[2]};RudderReportsFormat

Shouldn't we pass the DB name/login in the same way ?
Or ok, perhaps we want to have something different for password, but the server URL is almost the same thing as the DB name.

Actions
Copy link
 #8

Updated by François ARMAND about 8 years ago

  • Tracker changed from Bug to User story
  • Target version changed from 2.11.24 to 3.1.13

We are targeting 3.1 because 2.11 is EOL in 15 days, so if somebody want that, he just need to use a supported version.

Actions
Copy link
 #9

Updated by François ARMAND about 8 years ago

  • Description updated (diff)
Actions
Copy link
 #10

Updated by François ARMAND about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/cf-clerk/pull/92
Actions
Copy link
 #11

Updated by François ARMAND about 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 33 to 100
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 8 years ago

  • Subject changed from The database name and user can not be changed to Allow to configure reports database name and user
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 8 years ago

  • Subject changed from Allow to configure reports database name and user to Allow to customize reports database name and user to ease a separate database
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 8 years ago

  • Category changed from System techniques to System integration
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.13 and 3.2.6 which were released today.

Actions
Copy link

Also available in: Atom PDF