Closed
Bug 1240805
Opened 10 years ago
Closed 10 years ago
Set up a Mesos staging env
Categories
(Participation Infrastructure :: Community Ops, task)
Participation Infrastructure
Community Ops
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: yousef, Assigned: yousef)
Details
We need to set up a Mesos staging environment to experiment with changes and not affect prod.
| Assignee | ||
Comment 1•10 years ago
|
||
I've got a mostly auto-scaling setup of mesos master/slaves, marathon and zookeeper, just bamboo/haproxy left. Are we ok using our current org to host it or do we want to make a new one?
https://github.com/mozilla-cit
Flags: needinfo?(jgiannelos)
Comment 2•10 years ago
|
||
I would prefer our code to be under our main "Mozilla" github organization. It looks like there already is a "Community Ops" team. Do you want to use that one?
@Pierros
Any ideas?
Flags: needinfo?(jgiannelos) → needinfo?(pierros)
| Assignee | ||
Comment 3•10 years ago
|
||
I got an r+ from wex because he "owns" that team on GitHub. Repo is at https://github.com/mozilla/partinfra-playbooks
Comment 4•10 years ago
|
||
Looks OK. I will add a deprecation notice in our current repos (under my account) and we can start using these as a main repo for our ansible playbooks.
Updated•10 years ago
|
Assignee: nobody → yousef
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Flags: needinfo?(pierros)
You need to log in
before you can comment on or make changes to this bug.
Description
•