Closed
Bug 993911
Opened 10 years ago
Closed 10 years ago
Create accounts/access with platform similar to existing services
Categories
(Content Services Graveyard :: General, defect)
Content Services Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
Iteration:
34.3
People
(Reporter: Mardak, Unassigned)
References
Details
Both bug 993908 and bug 993909 are server side functionality that will need some account/access kickoff. oyiptong, please add more details.
Flags: needinfo?(oyiptong)
Flags: firefox-backlog?
Reporter | ||
Updated•10 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Comment 1•10 years ago
|
||
we've had a conversation with mmayo and this bug is to track a kick-off meeting we'd like to have. we're running a few server-side pieces and it looks we're handling it (the UP team). We're running a python web service, essentially recording stats and sending them to a local hekad. The local hekad sends the stuff to a central hekad, with a few listeners. We plan to have listeners fetching messages on the hekad message queue and storing them in various storage locations, including redshift and S3. We will also store some data in S3 and will be served using Cloudfront. Those contain images. more context here: https://docs.google.com/a/mozilla.com/document/d/1ItO5SuUQpPr0Sls0GK-TXxSP_3ZhEEB86z4UjyGeC0w We're still gathering what the system will need (especially in its future revisions) so we need to be able to change things in the system. mmayo suggested we think about whether we need an account in the services IAM or our own AWS account (which we already have)
Flags: needinfo?(oyiptong)
Comment 2•10 years ago
|
||
The user accounts to be created are: Marina Samuel: msamuel@mozilla.com Edward Lee: elee@mozilla.com Maxim Zhilyaev: mzhilyaev@mozilla.com Olivier Yiptong: oyiptong@mozilla.com
Comment 4•10 years ago
|
||
We'll also want some automation scripts to create our servers, ideally using the same tools as what Services Ops/Dev expect, if it already exists. A stack that looks like this: reverse proxy, process manager, python app, local heka Another that is: central hekad Thanks!
Reporter | ||
Updated•10 years ago
|
Component: General → Content Services
Reporter | ||
Updated•10 years ago
|
Whiteboard: [qa?] → p=3 [qa?]
Updated•10 years ago
|
Whiteboard: p=3 [qa?] → p=0
Comment 5•10 years ago
|
||
Any update on this bug? We'd like to get a sense of timeline in order to plan for which Firefox release train we can catch. Thanks,
Comment 6•10 years ago
|
||
(In reply to Olivier Yiptong [:oyiptong] from comment #5) > Any update on this bug? Sorry about the wait. Services Operations is waiting on a new Development IAM for AWS. It should be in place soon.
Comment 7•10 years ago
|
||
Services Ops has given us access to their dev environment and are working with us to set up a production environment for us
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Iteration: --- → 34.3
Flags: qe-verify-
Whiteboard: p=0
Assignee | ||
Updated•10 years ago
|
Product: Mozilla Services → Content Services
You need to log in
before you can comment on or make changes to this bug.
Description
•