Closed Bug 1357600 Opened 9 years ago Closed 9 years ago

Conflicts between BMO and dockerflow "Containerized App Requirements"

Categories

(bugzilla.mozilla.org :: Infrastructure, enhancement)

Product:
bugzilla.mozilla.org
Component:
Infrastructure
Version:
Production
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dylan, Unassigned)

Details

https://github.com/mozilla-services/Dockerflow#containerized-app-requirements > 1. Accept its configuration through environment variables. This is not something BMO supports. Upstream can supports $DATABASE_URL as per heroku (bug 1284263), but there are other parameters that need passing in. In addition, the file comparable to this contains a very important secret value, that has a long lifetime and must never be leaked. What do you use for transferring credentials into the containers? The stuff about $PORT is fine, that's directly supportable in the httpd config. > 4. Respond to `/__version__` with the contents of `/app/version.json`. There are some assumptions built into this that are probably not true, the early version might be a lie. > 5. Respond to `/__heartbeat__` with a HTTP 200 or 5xx on error. This should check backing services like a database for connectivity. I'm not sure what this check should do, and we'll probably not check the DB here. This would probably make sense if we maintained a persistent DB connection but that isn't currently the case; in this context it would be checking that one out of > 6. Respond to /__lbheartbeat__ with an HTTP 200. > This is for load balancer checks and should **not** check backing services. This is a very good thing and we can happily support this. > 7. Send text logs to `stdout` or `stderr`. This probably a significant bottle neck compared to UDP syslog. BMO *can* do this, but it would not be ideal.
Flags: needinfo?(ckolos)
Flags: needinfo?(bobm)
(In reply to Dylan Hardison [:dylan] (he/him) from comment #0) > https://github.com/mozilla-services/Dockerflow#containerized-app-requirements > > > 1. Accept its configuration through environment variables. good thing and we can happily support this. We discussed this in the meeting, and it'll be handled by $SOME_TOOL. > > 7. Send text logs to `stdout` or `stderr`. BMO speaks syslog, syslog speaks to stderr/stdout. Everyone is happy.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ckolos)
Flags: needinfo?(bobm)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.