Summary
Data on disk space associated with a deleted server will be explicitly scrubbed (overwritten or deleted) before the disk space is allocated to a new customer.
Release Note
No end-user impact.
Rationale
Risk mitigation: When a customer selects the option to delete a server, the customer’s may data remain intact on the hard drive space associated with the server until it is overwritten or deleted, depending on the technology used. If the customer’s data is not explicitly overwritten or deleted then a subsequent customer with access to that disk space can potentially retrieve it.
User stories
(1) A customer has deleted a XC server. After an appropriate delay period has expired and before allocating the disk space to a new customer, the data must be explicitly overwritten. (2) A customer has deleted a XS server. After an appropriate delay period has expired and before allocating the disk space to a new customer, the image container must be explicitly deleted.
Assumptions
(1) Assume there is a way to configure how long after a server has been deleted that the data must be scrubbed. (2) Assume there is a way to queue scrubbing activities on a host. (3) Assume there is a way to address different technologies (fileshare vs. image container vs. other).
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.