vyos-cloud-init.git/udev, branch equuleus (mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=equuleus 2018-11-08T04:35:56+00:00 azure: add udev rules to create cloud-init Gen2 disk name symlinks 2018-11-08T04:35:56+00:00 Chad Smith chad.smith@canonical.com 2018-11-08T04:35:56+00:00 urn:sha1:3b332c93f765c9208f7e059d8a0c2463f7ffe12a Cloud-init delivers udev rules on Azure to create the following symlinks: - /dev/disk/cloud/azure_root - /dev/disk/cloud/azure_root-part# - /dev/disk/cloud/azure_resource - /dev/disk/cloud/azure_resource-part# Cloud-init cc_disk_setup expects presence of these dev links in order to setup the mounted ephemeral disks. Gen1 instances udev rules match based only a DEVICE_ID attribute that no longer exists on Gen2 instances. Supplement existing Gen1 rules with matches on specitic SCSI target/lun path 0:0:0 and 0:0:1 and generate links for azure_root and azure_resource respectively. LP: #1797480 remove blocking udev functionality 2016-05-27T21:03:49+00:00 Scott Moser smoser@ubuntu.com 2016-05-27T21:03:49+00:00 urn:sha1:b16533714e02fc71d463ca73abee5c9f6237f115 This didn't really work. See bug for more info. LP: #1577844 improve how cloud-init-wait waits 2016-03-29T13:11:25+00:00 Scott Moser smoser@ubuntu.com 2016-03-29T13:11:25+00:00 urn:sha1:78c9de871eb2a68da36fb4397fe756b88dc9eb15 Instead of sleep and check loop, use 'udevadm settle' to wait. since we run from a udev event, this is sufficient. udev settle will exit when either of a.) the file exists b.) the udev event queue has all been processed. c.) timeout is reached. Since cloud-init-wait is being run as a udev event, 'b' cannot be satisfied until it finishes. Thus, this essentially becomes a inotify based wait for the file /run/cloud-init/network-config-ready and no loops are needed. improve how cloud-init-wait waits 2016-03-28T18:47:19+00:00 Scott Moser smoser@ubuntu.com 2016-03-28T18:47:19+00:00 urn:sha1:bf88c6ef54608f4488fca806b5f30afad08d6c51 since we run from a udev event, this is sufficient. udev settle will exit when either of a.) the file exists b.) the udev event queue has all been processed. Since cloud-init-wait is being run as a udev event, 'b' cannot be satisfied until it finishes. Thus, this essentially becomes a inotify based wait for the file /run/cloud-init/network-config-ready and no loops are needed. fix creation of network-config-ready and dont bother waiting on lo 2016-03-21T02:31:21+00:00 Scott Moser smoser@ubuntu.com 2016-03-21T02:31:21+00:00 urn:sha1:16751f75a51814e4873199eddec15040dd221561 remove the 'find_name' function that was here. 2016-03-19T00:42:49+00:00 Scott Moser smoser@ubuntu.com 2016-03-19T00:42:49+00:00 urn:sha1:db54b59b90c8db2fc4a637ae09d3f0df14e77acb I had left this in to commit it, it was my first pass at cloud-init doing the naming itself. That design was then replaced with the idea for cloud-init to instead write systemd.rules files. commit the systemd waiting mechanism 2016-03-19T00:40:54+00:00 Scott Moser smoser@ubuntu.com 2016-03-19T00:40:54+00:00 urn:sha1:519c0936e3e80fc14225e500fbb61d0d12d28c35 Note, still broken as cloud-init local is not going to ever touch the CI_NET_READY file (/run/cloud-init/network-config-ready). So as this is , it will actually just block for 60 seconds and go on. add this, its getting moved, but i wanted some of the content stored 2016-03-19T00:35:36+00:00 Scott Moser smoser@ubuntu.com 2016-03-19T00:35:36+00:00 urn:sha1:72b56d0f59f321519f25b039937a24b0ce338295 Add udev rules for Azure ephemeral disks. 2015-07-21T12:06:11+00:00 Daniel Watkins daniel.watkins@canonical.com 2015-07-21T12:06:11+00:00 urn:sha1:3aeec2dd6460fbdd3b8f217ad8aa231acb4bfd45 And install them in the Debian packaging.