holman | minimal: just saw this sorry | 00:19 |
---|---|---|
holman | Ill look at it tomorrow | 00:19 |
minimal | thanks | 00:31 |
holman | Welcome back meena o/ | 02:20 |
holman | deostroll: version, distro? | 02:20 |
deostroll | i followed this approach for cloud-init -> https://superuser.com/questions/827977/use-cloud-init-with-virtualbox/853957#853957 | 16:55 |
deostroll | i don't get the significance of meta-data file. Hoping someone can explain 🙏 | 16:57 |
minimal | deostroll: "i don't get the significance of meta-data file" - the significance is it is required. cloud-init uses the instance-id to determine whether a particular boot is a "new" boot and so needs (re)configuration or a reboot of an existing VM | 17:00 |
deostroll | So in my current vm instance I have attached a disk meant for cloud-init. So the meta-data file guarantees that cloud-init doesn't redo itself the next time I power up my vm instance. Is this the correct understanding? | 17:04 |
minimal | yes | 17:06 |
deostroll | Reg link shared above, I had to figure that we need special cloud distro images (vmdk). Is the setup experience different when start off with the distro's live-server iso files? | 17:14 |
deostroll | So the above question rephrased is: can I perform a cloud-init part of an iso os install? | 17:16 |
minimal | deostroll: cloud-init is designed to be used when an OS disk image is booted, not during an install. However, having said that, distro can decide to use cloud-init as a basis for an OS installer - specifically Ubuntu Server uses cloud-init via Subquity for installation | 17:39 |
dbungert | https://canonical-subiquity.readthedocs-hosted.com/en/latest/ has more details on that last part | 17:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!