|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/12/2013 6:09 PM, Chris Fordham wrote: > I gave it a real quick test. > I noticed the following: > > [....] Starting Cloud service: cloud-initCloud-init v. 0.7.2 running 'modules:config' at Tue, 17 Dec 2013 09:20:23 +0000. Up 139.74 seconds. > 2013-12-17 09:20:23,605 - stages.py[WARNING]: Module ssh-import-id is verified on ['ubuntu'] distros but not on debian distro. It may or may not work correctly. > Generating locales (this might take a while)... > en_US.UTF-8... done > Generation complete. > 2013-12-17 09:20:25,565 - util.py[WARNING]: Running apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_apt_configure.pyc'>) failed > 2013-12-17 09:20:25,572 - stages.py[WARNING]: Module landscape is verified on ['ubuntu'] distros but not on debian distro. It may or may not work correctly. > i.e. cc_apt_configure failed. Perhaps its another upstream bug? > I'm not sure about that issue.... so all help appreciated on anyone looking at this (I'll continue tomorrow evening) - but what I /have/ worked out (and is embarrassingly obvious) is that by default cloud-init checks a set of metadata servers - and Ec2 was the 5th one in the line. So this makes the cloud-init AMI much quicker - around 12 seconds from start to end, down from around 140 seconds. So I have just patched build-debian-cloud (pull req submitted to Anders) to let the cloud-init plug-in specify the metadata server. I've distributed these to all regions, and updated the list of AMIs on the wiki; the set of AMI IDs are: Region, 32 bit, 64 bit - ------------------------------- US-East-1, ami-23735a4a, ami-5b715832 US-West-1, ami-70dbeb35, ami-76dbeb33 US-West-2, ami-d4a4c0e4, ami-d0a4c0e0 EU-West-1, ami-ae49a0d9, ami-a249a0d5 AP-Southeast-1, ami-18fca84a, ami-1afca848 AP-Southeast-2, ami-8942ddb3, ami-8b42ddb1 AP-Northeast-1, ami-8d12708c, ami-8b12708a SA-East-1, ami-5f78d942, ami-5d78d940 This message is signed to confirm these IDs at this time; but please consider these as testing until we resolve the issue with the "configure apt" issue above. James - -- /Mobile:/ +61 422 166 708, /Email:/ james_AT_rcpt.to -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQIcBAEBAgAGBQJSsH3DAAoJEK7IKHSdhcU8uw8P/jY0dU1Zu6Rg3z5IeIVi94YW nrD0AWbyrq/d9EaUB2ydXcP/UCczWL36vlNcMUA7k1d13yY4fx32DutBtdW/m9oI m88+craaheyaDRdp6IM050CYSW1/jkGFYlBJJSY13SuBA7kZGvI8ZVr6Eh0TMofb KJETZpj/gwOjs/blEcuZ/ebXZTpxhknmiFcfUNFXoZ1Y4yhGgdyIJ8y2f/szM5o0 cqYnKsI/XM4y1OQSKXE7f6TPDJ0Akzkm6kod8q2jWNBAvCGazWwBlxn/J1UDxbHg QQJlxrJO+r18ywaKoNPuOKpGykqAP4GLhn9XemyYpd1c+tsZ3628Ubp04ll6sGOk EOVusF0/ny/pe8N7hjMkhHmRgsqlQsEk5SCoBmDPiwwKDrgO4Oc/csNdqDbnM5lx FDxsBdNUJRO2vi5KY1JHHXddK+OZ2IVh3C9gDdwuOjw+4q3dHBow4TasVxGLDBXn bT0pLlorBUMndOrw0VM8y93GCdVkUKOaIJC5cwp29qv2zGeb4KyGHReSTAJSfTdr +zzyu/6h1JsHC8gbZgqF8W7UGqe8yFYXLjPauIgw9MnUTNOGPT4rVkw5K5vZWHkr +SYj9Vnb3RJexBnTxOG8nv3z3PIwah8A2c1N45/unFEDktYK+gYSTHDgA9pIXhZX k0qDhzTwPQbyZ+fjVsG9 =jXCJ -----END PGP SIGNATURE----- |