Platform Team/Server Kit/Architecture: Difference between revisions
No edit summary |
|||
| Line 59: | Line 59: | ||
* pure data, like leases and content black lists, to fetch as-is from the Mothership. | * pure data, like leases and content black lists, to fetch as-is from the Mothership. | ||
After installing the main package, it will provide possibility to fetch | After installing the main package, it will provide possibility to fetch pure data from the Mothersip, and finally running Mace to complete school server setup. | ||
The maintaining process will be: | The maintaining process will be: | ||
| Line 67: | Line 67: | ||
** Sugar Server Kit upstream repository that follows the [[Sugar_Server_Kit/Release_plan|Statement of purpose for releases]], i.e., declares that newly appeared updates should not break already deployed systems; | ** Sugar Server Kit upstream repository that follows the [[Sugar_Server_Kit/Release_plan|Statement of purpose for releases]], i.e., declares that newly appeared updates should not break already deployed systems; | ||
* taking care that pure data on the Mothership is up-to-date, e.g., leases are properly created, content filtering blacklists are fresh, etc.; | * taking care that pure data on the Mothership is up-to-date, e.g., leases are properly created, content filtering blacklists are fresh, etc.; | ||
* do occasional changes in the main school server package to add new services or tune downstream Mace configuration and upload it to the repository that will be used for unattended updates on school servers | * do occasional changes in the main school server package to add new services or tune downstream Mace configuration and upload it to the repository that will be used for unattended updates on school servers. | ||
=== Highly maintained school servers === | === Highly maintained school servers === | ||