On 2 December 2013 10:31, Chris Fordham <[email protected]> wrote:
> On Mon, Dec 2, 2013 at 7:14 PM, Paul Wise <[email protected]> wrote: > >> On Mon, 2013-12-02 at 08:01 +0000, Bromberger, James wrote: >> >> > Yes, but we've hit a snag in confirming the cloud-init is working well >> > (or perhaps my confidence that cloud-init in the images for 72. Is >> > working well enough o be pushed forward to marketplace). I've been >> > travelling and haven’t had time, and a few seconds between work has >> > been massaging snapshot.d.o -> s3/glacier. ;) >> >> I see, I wonder if the QA for these should be automated? >> > Yes please. > > >> >> > Happy if someone wants to tell me the 7.2 AMIs we have are infact OK, >> > of if we do have an error in cloud-init execution.... >> >> I just launched a 7.2 64-bit instance in Sydney, no issues so far. >> > Paul, did you test cloud-init? There is at least one thread showing issues > on this list. > > >> -- >> bye, >> pabs >> >> http://wiki.debian.org/PaulWise >> > > Hey guys I have been working on the cloud-init plugin over the weekend (and hvm AMIs): https://github.com/andsens/build-debian-cloud/tree/python-WIP I have not tested anything yet, but I am almost certain that there are problems with the current AMIs. The generate-hostkeys, authorized_keys and expand-root scripts have not been disabled, meaning that there is duplicated functionality (I am pretty sure cloud-init does all those things). I have created a cloud_init plugin that fixes those things, I haven't had the time to test anything yet though.
