[08:27] <sterfield> hey there
[08:28] <sterfield> I have a question, hope it’s not a stupid one
[08:28] <sterfield> I can see that cloud-init is grabing metadata and userdata from different sources, (EC2, nocloud, etc..)
[08:29] <sterfield> but is it possible to use those metadata / userdata in scripts ? I mean, they are pulled by cloud-init at boot time, so are they available ?
[08:30] <sterfield> or is it only for cloud-init internal configuration, like default hostname etc…
[08:30] <sterfield> ?
[08:30] <waldi> take a look into /var/lib/cloud/instance
[08:31] <sterfield> oh ok
[08:33] <sterfield_> sorry about that
[08:33] <sterfield_> I guess I was D/C at the wrong moment :x
[08:33] <sterfield_> so you were telling me to look in /var/lib/cloud/instance
[08:34] <sterfield_> which is a link to the instance/ID folder, which contains all the information pulled by cloud-init, right ?
[08:37] <waldi> smoser: any news on https://bugs.launchpad.net/cloud-init/+bug/1536961 and https://bugs.launchpad.net/cloud-init/+bug/1536964 ?
[08:41] <sterfield> Out of the 4 steps of cloud-init (init —local, init, config and final), I understood the last three and can see the modules called by each phase. However, I’m not fully understand the —local phase. This is a phase called at very early stage in the boot process, where network for example is not available. However, I don’t understand what’s done during this phase, and also how it is configured.