Closed
Bug 1361439
Opened 7 years ago
Closed 7 years ago
Create dockerflow-compliant container that runs a BMO web head
Categories
(bugzilla.mozilla.org :: General, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dylan, Assigned: dylan)
References
()
Details
Attachments
(1 file)
A first step towards running bugzilla-dev (and eventually, all of bugzilla) in cloud-services infrastructure will be supplying a container that runs the a BMO webhead. BMO may require exceptions or changes to the dockerflow requirements, but the best way of proceeding is to be able to stand something up.
Assignee | ||
Updated•7 years ago
|
Summary: Create dockerflow-compliant container for that runs a BMO web head → Create dockerflow-compliant container that runs a BMO web head
Assignee | ||
Updated•7 years ago
|
Blocks: bmo-cloud-migration
Assignee | ||
Comment 1•7 years ago
|
||
I'm at the point where I need to know how secrets and other config data can be passed in. All my configuration can come in the format of this file: https://github.com/mozilla-bteam/bmo/blob/master/vagrant_support/checksetup_answers.j2 but I need to know how the stuff built around the containers passes that to the container's entry point. Cheers!
Flags: needinfo?(ckolos)
:dylan All container configuration is done via 1 of 2 ways: 1) As env vars 2) Via config files In both cases, puppet does the heavy lifting. For ENV vars, those are dumped to a file, /etc/dockerflow/${env}.txt. This file is then referenced when the systemd unit is created and passed to the container. In the event that a configuration file is required/wanted, the file is created as a puppet template and put into place when last-mile configuration of the application is done. We store secrets in a private repo. Access to those is limited to members of cloudops only.
Flags: needinfo?(ckolos)
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8871580 -
Flags: review?(rsoderberg)
Assignee | ||
Updated•7 years ago
|
Attachment #8871580 -
Attachment description: WIP PR → PR
Assignee | ||
Comment 4•7 years ago
|
||
Comment on attachment 8871580 [details] [review] PR this was approved in github
Attachment #8871580 -
Flags: review?(rsoderberg) → review+
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•