drakkar-lig / drakkar-lig/walt-python-packages
Name network interfaces according to vnode config
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
If we type for instance walt node config vnode1 networks=walt-net,exp-net, then it would be handy to have the network interfaces automatically named walt-net, exp-net inside the virtual node. Or if naming is too difficult, they could have an "altname" (ip link property add altname walt-net dev ens3, if iproute2 is new enough).
The association between mac and name could be passed using the kernel command line and then interpreted by walt-init or by some later code of the OS image (/bin/on-bootup, specific service, etc.).
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
Trace how walt node config passes vnode network settings into the virtual node, then inspect walt-init and /bin/on-bootup as possible handling points. Check how the MAC-to-network-name association could travel through the kernel command line. Done means configured networks appear as interface names or supported altnames inside the virtual node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100