openwisp / openwisp/openwisp-controller
[feature] Allow flagging a VPN template as the management VPN
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
⚠️ This issue is not suited for beginners.
Related to https://github.com/openwisp/openwisp-config/issues/208.
Allow flagging a VPN client template as the management VPN.
If a device config contains such a template, it shall determine its interface name and communicate it to the agent (we need to define this, more discussion is needed).
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
The issue names no files, tests, or entry points. Start by reviewing related issue 208 and clarify how a flagged VPN client template determines and communicates its interface name to the agent; done requires an agreed design and implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100