ajmyyraare there any supported ways of hinting for the correct datasource? dmidecode reveals it of course but I don't see it being utilized. the new datasource eventually gets discovered and runs correctly, but before that there's quite a bit of wait for ec2 timeouts (120s) and for others as well11:43
ajmyyrathe fork is here and for utilizing UpCloud's network metadata service, if interested. https://github.com/ajmyyra/cloud-init/tree/datasource-upcloud11:48
ajmyyrajust testing with "cloud-init init" for now.11:48
meenaajmyyra: set datasource_list12:06
ajmyyraisn't it defined in cloudinit/settings.py?12:10
ajmyyraadded it there, of course12:10
ajmyyraor do you mean as provided cloudconfig? can add it there, of course but it would mean that images that don't have it included could have to go through the same wait before initializing.12:13
=== MAbeeTT2 is now known as MAbeeTT
cyphermoxI'm curious, I'm having some weird issues configuring Saltstack via cloud-init while a machine is being commissioned by MaaS -- on what phase does this run? I managed to get things to work with late commands, but it seems wrong when there is syntax for it in the first place17:08
meenaajmyyra: maybe setting ec2 strict could be enough17:10
meenaajmyyra, you can't provide the data source config via cloud-config, since the cloud-config is read from the data source.17:12
cyphermoxyou can do so from the boot command-line though17:12
meenacyphermox: salt runs in final stage https://github.com/canonical/cloud-init/blob/master/config/cloud.cfg.tmpl#L12417:16
ajmyyrameena: oh yeah, that too. might need to check ci.datasource as a command line option. seems like something I was after in the first place.21:40

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!