TritonDataCenter / TritonDataCenter/sdc-cloudapi
CloudAPI should include ability to reprovision a machine
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 22
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently CloudAPI is missing ability to reprovision a machine to a current or newer image version.
Therefore also Triton CLI is missing the ability.
-Is there a technical reasoning behind this or is this just not implemented yet?
Reprovisioning is a useful feature when doing rolling upgrades and not wanting to spin up new instance for the upgrade (a little bit of container anti-pattern but useful in limited use-cases).
This would be "nice to have" feature in the long run but not a must - more modern way would be to just spin up a new instance and fail over to that when ready.
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 reviewing the existing CloudAPI machine-provisioning behavior and the corresponding Triton CLI capabilities. Define how reprovisioning a machine to its current or newer image version should work, including the API and CLI surface. Done means both CloudAPI and Triton CLI support the requested reprovisioning workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100