Generate hekad 0.3 compatible sync config

RESOLVED FIXED

Status

Cloud Services
General
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: RaFromBRC, Assigned: vng)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
James would like to test a recent Heka behind a running Sync instance, but we don't have an configuration that will work on a recent Heka that he can work from. Can you use the current production Heka configuration files to generate functionally equivalent ones that will work w/ Heka 0.3?

Note that this will probably require setting up a syncstorage server environment that replaces metlog-py with heka-py. I started work on that a while ago and did most of the grunt work involved in the global search-and-replace for both server-storage and server-core, you can find my work on the following github branches:

https://github.com/mozilla-services/server-storage/tree/features/use-heka-py
https://github.com/mozilla-services/server-core/tree/features/use-heka-py

Those probably don't work quite right at the moment, and you'll probably have to install heka-py and heka-py-cef into the virtualenv by hand, but I did have it actually running and working with hekad 0.2 at one point, so it's definitely a good head start.
(Reporter)

Updated

4 years ago
Summary: Generate hekad 3.0 compatible sync config → Generate hekad 0.3 compatible sync config
Whiteboard: [qa+]
(Assignee)

Comment 1

4 years ago
Created attachment 770879 [details]
production hekad 0.1 JSON configuration for sync
(Assignee)

Comment 2

4 years ago
Created attachment 770920 [details]
hekad 0.3 TOML configuration
Status: NEW → ASSIGNED
v0.3 toml created by :vng
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
OK. I picked this up.
Will review and hold until we have a Stage-like Sync environment where this can actually be used.
You need to log in before you can comment on or make changes to this bug.