Storage provisioning
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Currently the Protocol does not describe the interface for storage provisioning.
Should there be an interface to provision storages?
What information is needed to create, update, delete or recover a storage? For example, owners, memory quota, availability, performance requirements, preservation strategy, and possibly initial data rights and processors..
What are the security considerations?
Who can provision a storage?
Currently servers provide one or more storages in an implementation defined way. Ditto tracking the owners of a storage.
The current definition of "owner" in the Protocol confines owner to a storage. The owners of a storage can't create other storages or delete their own storage, or have additional means to control or configure a storage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Protocol's current storage and owner definitions, including how servers expose storages and track owners. Clarify the requirements for creating, updating, deleting, and recovering storage, along with security and authorization questions. Done means the project has agreed on whether provisioning belongs in the Protocol and has documented the resulting interface and responsibilities.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100