make internal storage service into init container
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Currently internal storage is used as a service in OpenPAI. We can make it an init container. Using init container has the following advantages:
- Different services can leverage the same logic.
- It is more convenient to ensure the correct storage is mounted.
- Cleaner than current implementation.
Considering there's only one service using internal storage now, it may be not worth the effort to implement the above mechanism. We can leave it to a future work.
Contributor guide
No contributing guide indexed for this repository
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 locating the OpenPAI internal storage service and the deployment configuration that mounts its storage. Review how Kubernetes init containers would replace the current service, and define done as a documented, working migration that preserves storage availability for the consuming service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100