canonical / canonical/cloud-init

Support network-config for the nocloud-net datasource

Open
#3,305 0 comments 1 reaction 0 assignees View on GitHub
bug launchpad
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

This bug was originally filed in Launchpad as [LP: #1809180](https://bugs.launchpad.net/cloud-init/+bug/1809180)

Launchpad details

affected_projects = []

assignee = None
assignee_name = None
date_closed = None
date_created = 2018-12-19T23:12:41.495696+00:00
date_fix_committed = None
date_fix_released = None
id = 1809180
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1809180
milestone = None
owner = simonklb
owner_name = Simon Kollberg
private = False
status = triaged
submitter = simonklb
submitter_name = Simon Kollberg
tags = []
duplicates = []

_Launchpad user **Simon Kollberg(simonklb)** wrote on 2018-12-19T23:12:41.495696+00:00_

Currently the nocloud-net datasource does not read the network-config from the provide URL. It would be nice if this was supported so that the network can be configured after the fallback network has been established. This way you can boot the image in a different environment without having to run cloud-init a second time.

Example network-config:

version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4: true

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.