Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | MaxSem | T92691 Requisition hardware | |||
Invalid | • Tfinc | T92692 Define latency goals | |||
Resolved | MaxSem | T92678 Puppetize OSM | |||
Resolved | Yurik | T105070 Puppetize Postgres 9.4 + Postgis 2.1 role for Maps Deployment | |||
Resolved | MaxSem | T92668 Estimate hardware requirements for initial rollout | |||
Resolved | • Tfinc | T92666 Estimate target traffic level for initial release | |||
Resolved | MaxSem | T92652 Outreach product teams about OSM | |||
Resolved | MaxSem | T104648 Create a load testing script |
Event Timeline
Comment Actions
How is this related to T82154: OSM Server Deployments - Master Tracking Ticket / {T83006}?
Comment Actions
The older tickets can be pretty much considered stalled, as most of h/w in question has been cannibalised for other purposes. Also, since this is basically a reboot of the project, all h/w requirements will be redone from scratch, see the dependencies.
Comment Actions
Well, this one is kinda special because what was requested is not what we wanted but what we had the money for :P