User:Mstone/Commentaries/Infrastructure 1: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
== Proposed Requirements == |
|||
Here are some proposed requirements for a software system and procedure for communal maintenance of infrastructure: |
|||
; Data integrity |
; Data integrity |
Revision as of 17:58, 20 August 2008
Here are some proposed requirements for a software system and procedure for communal maintenance of infrastructure:
- Data integrity
- It should be possible to verify the integrity of reference documentation on an independent system booted from read-only media.
- Timely access
- Failures of otherwise critical pieces of OLPC infrastructure should not inhibit timely read or write access to the reference documentation.
- Credential rotation
- When people leave the VIG, it should be easy to remove their access to secrets created after their exit.
- If people ever leave the VIG non-amicably, it should be possible to quickly update important secrets throughout the OLPC infrastructure.
- Publishability
- Secrets should be carefully separated from public knowledge (e.g. with encryption or quarantine) so that everything else can be published.