244
edits
Update:Requirements: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Update:Home_Page|Update: Home Page]] » Requirements | [[Update:Home_Page|Update: Home Page]] » Requirements | ||
== Infrastructure == | |||
* [[Update:Architecture_and_General_Design|Architecture and General Design]] | |||
* [[Update:Infrastructure|Architecture Notes/Details/Requirements]] | |||
In looking at the future, we need to identify what it's going to take to handle the UMO service during peak loads. The community will not judge us on how sexy UMO is or the tools built around it. We believe the community and pundits will be most critical of UMO if it fails to perform during peak usage. If a new security update is released and UMO melts down, that will reflect poorly on the use of Firefox but also the Mozilla Foundation as a whole. | |||
The [[Update:Infrastructure|existing infrastructure]] will not scale to handle peak loads at this time. Peak loads will occur when new and popular extensions come out and most notably when security updates are released. We need to build a scalable, reliable and secure infrastructure to handle the delivery of the UMO service to end users. | |||
Corey Shields will be tasked with coming up with a plan for this and presenting it to the Mozilla Foundation system administrators. The [http://osuosl.org OSL] would be willing to completely manage this service up to the application layer (including upgrades, etc) for the MoFo. | |||
== General Requirements == | == General Requirements == | ||