1139945 - Deploy Infernyx 0.1.37 to Stage

Status: RESOLVED FIXED

(Content Services Graveyard :: Tiles: Ops, defect)

Description

[Tim Spurway [:tspurway]]

This patch contains the scripts/csdash.py script to populate the Metrics Dashboard.

Note that Ops will have to make two additional changes to other repos:

- patch expects new variables defined in the config_infernyx module:

RS_PORT = 5432
DASH_USER = 'read_only'
DASH_PASSWORD = <password for redshift user>
DASH_BUCKET = 'net-mozaws-prod-metrics-data'
DASH_KEY_ID = <access key for dashboard s3 bucket>
DASH_ACCESS_KEY = <secret key for s3 bucket>

Note that :edwong has the S3 secrets - :relud has the RedShift secrets

- a cron job will need to spawn this script (with no arguments) daily.  I would suggest 4am UTC

Comment 1

[Daniel Thorn [:relud]]

If no DASH_KEY_ID or DASH_ACCESS_KEY is provided, will it use the default permissions (ie boto using an ec2 instance's role permissions), or will it fail. Ideally it should use the default permissions, so that access need only be granted to the role.

What kind of permissions does the DASH user need in redshift? just select * ?

Comment 2

[Tim Spurway [:tspurway]]

If the S3 keys aren't provided it will fail.  I could wire it up to use the same mechanism we use in database.py, but wasn't sure we could use that mechanism for multiple endpoints.  I am assuming we can?  I could make that change and bump the version - let me know if that's the better route

DASH for redshift needs select * only to tiles, impression_stats_daily

Comment 3

[Tim Spurway [:tspurway]]

CORRECTION: if the DASH_KEY_ID and DASH_ACCESS_KEY are both configured to none and the perms are granted to that role, it should work as is

Comment 4

[Daniel Thorn [:relud]]

This is deployed to stage