[11:49] <Odd_Bloke> smoser`: utlemming: So I think the version of cloud-init uploaded to vivid yesterday is fairly fundamentally broken by the snappy merge.
[11:50] <Odd_Bloke> In that SSH is disabled by default.
[11:51] <Odd_Bloke> smoser`: utlemming: I _think_ the fix is to remove snappy from the list of cloud_config_modules, and ensure that the snappy image build process includes it.
[11:51] <Odd_Bloke> I'm booting a snappy instance now to have a look at what it currently does.
[11:56] <Odd_Bloke> smoser`: https://code.launchpad.net/~daniel-thewatkins/cloud-init/no-snappy-by-default includes that change.
[14:37] <smoser> Odd_Bloke, agreed i screwed that up.
[14:38] <smoser> lets just configure it off by default.. make the module do nothing, and we can enable it in snappy
[14:46] <smoser> Odd_Bloke, alternatively we can enable that module based on presence of some "this-is-snappy" flag on filesystem or other runtime check
[14:46] <smoser> thats what i'd like.