Closed Bug 935684 Opened 12 years ago Closed 12 years ago

Socorro 65 config changes

Categories

(Socorro :: Infra, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lars, Assigned: bburton)

References

Details

(Whiteboard: [config change])

with the deployment of Socorro 65, the configuration for HBase found in common_hbase.ini should change: old: forbidden_keys='email, url, user_id, exploitability' new: forbidden_keys='url, email, user_id, exploitability, json_dump.sensitive, upload_file_minidump_flash1.json_dump.sensitive, upload_file_minidump_flash2.json_dump.sensitive, upload_file_minidump_browser.json_dump.sensitive'
-> % svn diff Index: crashmover.ini =================================================================== --- crashmover.ini (revision 77667) +++ crashmover.ini (working copy) @@ -241,7 +241,7 @@ # name: forbidden_keys # doc: a comma delimited list of keys to not allowed in the processed crash # converter: socorro.external.fs.crashstorage.<lambda> - forbidden_keys='url, email, user_id, exploitability' + forbidden_keys='url, email, user_id, exploitability, json_dump.sensitive, upload_file_minidump_flash1.json_dump.sensitive, upload_file_minidump_flash2.json_dump.sensitive, upload_file_minidump_browser.json_dump.sensitive' # name: fs_root # doc: a path to a file system Index: common_hbase.ini =================================================================== --- common_hbase.ini (revision 77667) +++ common_hbase.ini (working copy) @@ -21,7 +21,7 @@ # name: forbidden_keys # doc: a comma delimited list of keys banned from the processed crash in HBase # converter: socorro.external.hb.connection_context.<lambda> -forbidden_keys='email, url, user_id, exploitability' +forbidden_keys='url, email, user_id, exploitability, json_dump.sensitive, upload_file_minidump_flash1.json_dump.sensitive, upload_file_minidump_flash2.json_dump.sensitive, upload_file_minidump_browser.json_dump.sensitive' # name: hbase_connection_context_class # doc: the class responsible for proving an hbase connection
Config changes have been pushed out
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Deploy was rolled back, this still needs to be redone
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
so that Socorro 65 config changes are all in the same place, I'm adding them to this bug: 1) the aforementioned hbase changes - all instances of the key "forbidden_keys" should have the values in comment #0 2) config change for middleware.ini: the production middleware.ini file should be the same as the staging middleware (as we changed it this morning) along with substitutions for the prod hosts/usernames/passwords...
Summary: Socorro 65 config change for HBase → Socorro 65 config changes
(In reply to K Lars Lohn [:lars] [:klohn] from comment #4) > so that Socorro 65 config changes are all in the same place, I'm adding them > to this bug: > > > 2) config change for middleware.ini: the production middleware.ini file > should be the same as the staging middleware (as we changed it this > morning) along with substitutions for the prod hosts/usernames/passwords... https://bugzilla.mozilla.org/show_bug.cgi?id=938198
Apache config changes to turn on configman middleware: https://bugzilla.mozilla.org/show_bug.cgi?id=927639
Depends on: 927639, 938198
17:41:53 solarce | lars: the forbidden_keys changes to common_hbase.ini and crashmover.ini are done
Landed and looks good
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.