Closed Bug 506055 Opened 15 years ago Closed 15 years ago

Get services.mozilla.com set up properly

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 508658

People

(Reporter: telliott, Assigned: zandr)

Details

Right now, s.m.c is a pretty ad-hoc machine with a set of random scripts, an arbitrary API and a bunch of scotch tape. Before anant leaves, we should try to accomplish the following: 1) get php upgraded on that machine 2) get the new API working, including a captcha API, alongside the old one. 3) do a code cleanup to get rid of a bunch of old no-longer-used stuff 4) clone it all onto a second box and drop the thing behind a load-balancer. I propose that we grab the next proxy machine in line and set that one up to be what we want. Then we stick that behind the load balancer, take traffic there, then rebuild proxy01 and get that into rotation. Thoughts? Barriers? Assigning this to zandr first to get the box built. Once that's done, pass it over to me and anant and I will get the APIs installed.
Sounds like a plan. One thought: perhaps a VM might work well for redundancy? The current machine is under very low load, I don't see a real need to add another full box other than for hot-swap purposes.
I'm thinking more stuff like a headcrash, or other hardware failure.
Wouldn't a hot-swap work fine in that situation?
Sure, though if we have a hot-swap standing by, may as well put it to work!
Is now the right time to roll this into production and have it live on a cluster?
Sounds like a repeat of bug 508658.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.