vyos-cloud-init.git - (mirror of https://github.com/vyos/vyos-cloud-init.git)

Age	Commit message (Collapse)	Author
2016-03-22	Fix typo	Wesley Wiedenmeier

2016-03-22	Wrap read calls to /sys/class/net/DEV/{carrier, dormant, operstate} in	Wesley Wiedenmeier
	try/except blocks because there are sometimes read errors on the files and this should not cause a stacktrace
2016-03-21	Added net.find_fallback_network_device() to find an appropriate device to dhcp	Wesley Wiedenmeier
	on in the event that no network configuration was provided to cloud-init - Devices in /sys/class/net aside from loopback devices are scanned - Each device is tested to determine if it has a carrier using /sys/class/net/DEV/carrier, devices which do are preferred as they are most likely connected to the outside world - Devices which do not have a carrier but which might still be connected due to being in a dormant or down state are used as fallbacks in case no devices are found which have a carrier - A network state dictionary is generated to be passed to render_network_state to write ENI - A systemd link file is generated that will rename the chosen device to eth0
2016-03-18	Added comments	Wesley Wiedenmeier

2016-03-18	Handle static ip= entries by appending a static subnet to the device	Wesley Wiedenmeier

2016-03-18	If proto not specified, determine it using logic from:	Wesley Wiedenmeier
	lp:cloud-initramfs-tools/dyn-netconf/scripts/init-bottom/cloud-initramfs-dyn-netconf
2016-03-18	Fully parse files at /run/net-dev.conf, loading parameters for address,	Wesley Wiedenmeier
	broadcast, netmask, gateway and hostname if present
2016-03-17	Check for and merge in configuration caused by the 'ip' parameter on the	Wesley Wiedenmeier
	kernel's cmdline during network configuration parsing. - Search for .conf files in /run with names starting with 'net', as these are created during early boot if the ip parameter is present - If any are present and valid they are merged with network configuration from the current data source - If the devices affected by the 'ip' parameter are already present in network configuration, then a subnet entry will be added to the device's configuration unless an identical entry is already present - If any of the devices affected are not present then a mostly blank configuration will be generated for the device and the appropriate subnet specified
2016-03-10	adjust net to fit with cloudinit	Scott Moser
	at this point, this works: python -m cloudinit.net.network_state examples/network-all.yaml
2016-03-10	initial copy of curtin net	Scott Moser
	just add curtin/net as cloudinit/net and then copy curtin/udev.py as cloudinit/net/udev.py