On Sat, Jul 6, 2013 at 2:18 PM, Thomas Goirand <[email protected]> wrote: > On 07/06/2013 08:06 PM, Bromberger, James wrote: >> Having cloud-init in the AMIs is, IMHO, a core requirement for our next >> major release. Lots of newer things depend upon it. > > I'm happy to read this. > >> Right now we have cloud-init in backports and testing/Jessie (yay! Well done >> Thomas, Jakub and Charles). > > Thanks, but unfortunately, it is still waiting for FTP masters approval. > >> Moving from the current three scripts (resize root, fetch SSH key, and >> execute #! Userdata), to cloud-init, should be backwardly compatible. >> The question becomes: do we do this during the Wheezy cycle by pulling >> in from backports
I'm a strong advocate of using cloud-init over any distro-specific tools for instance customization. It's not perfect but cloud-init is widely used by many distributions which makes it easier for users to move to Debian cloud images if we support it as well. I think any effort spent for making cloud-init work better with Debian is worthwhile. ...Juerg > I would vote for that, yes! And this is why I uploaded to backports. > Also, backports is currently part of Debian, so there isn't any > political problem with that. > >> or wait until Jessie becomes stable? > > That's in a year and a half, I think that's a way too long to wait. > >> Similar discussions then arise about things like SDKs; which are open >> source, but change frequently. Should they be from main, or backports? >> Also the (new, unified, python-based) AWS cli: >> https://github.com/aws/aws-cli/ - backports, or main? > > Backport *IS* main. So I'm unsure what you are proposing. Do you mean > backports or Jessie? If we want backports, then it has to reach Jessie > anyway. > >> (PS: really looking forward to getting some good discussions at Debconf >> going on what we want to do) > > Likewise! :) > > Thomas > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CADLDEKtiR=m2pifd2oh9yajaszcmhegsh1fjqkmk8hxe_ao...@mail.gmail.com
