canonical / canonical/cloud-init

[enhancement]: Support V1/V2 network-config via nocloud-net with custom webserver

Open
#4,303 8 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

# Enhancement

When nocloud-net is [reading the seed data](https://github.com/canonical/cloud-init/blob/441d8f818de7e08836f43d1b9a1a4418f341b1a5/cloudinit/util.py#L1015), it doesn't read the `network-config` file as specified at the bottom of [the NoCloud docs](https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html). Even though supporting this would involve reconfiguring the network after it has already come up, there is no reason why this couldn't be done.

# Original Description
Why can't I specify the network-config using this method?
If a drive is mounted with the network-config file, this works.

Is there any reason why the custom webserver method (nocloud-net) does not support this?

See https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.