TritonDataCenter / TritonDataCenter/sdc-cloudapi
want support for additional "external" NIC tags
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 22
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently the logic which decides which networks are "public" and should be automatically added to instances without any specific networks requested is looking only for the "external" NIC tag.
It would be nice to have a SAPI tweakable for installations where another tag is used (e.g. we use the eait_core tag at UQ for historical reasons).
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
Locate the logic that identifies public networks and automatically adds them to instances without requested networks, then find how SAPI configuration is defined. Check how the external NIC tag is currently matched and determine the configuration and tests needed to support an alternate tag such as eait_core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100