Re: F18 cloud-init proposed rebase update

2013-05-03 Thread Jan van Eldik
Hi Padraig, On 05/02/2013 07:41 PM, Pádraig Brady wrote: Note el6 is still at 0.6.3-0.12.bzr532 Could the EL6 version be upgraded as well please? Anything we can do to help? cheers, Jan ___ cloud mailing list cloud@lists.fedoraproject.org

Re: F18 cloud-init proposed rebase update

2013-05-02 Thread Steven Hardy
On Thu, May 02, 2013 at 06:41:38PM +0100, Pádraig Brady wrote: > FYI, I broke your change into 2 and redid the tarball to exclude the large > .bzr subdir > http://pkgs.fedoraproject.org/cgit/cloud-init.git/commit/?id=da2ae016 > http://pkgs.fedoraproject.org/cgit/cloud-init.git/commit/?id=f9b16

Re: F18 cloud-init proposed rebase update

2013-05-02 Thread Garrett Holmstrom
On 2013-05-02 9:04, Pádraig Brady wrote: On 05/02/2013 04:49 PM, Steven Hardy wrote: Hi, I've been working through debugging a number of issues with cloud-init 0.7.1 as currently packaged for F18. The most major problem is that it no longer seems possible to define a user via the user-defined

Re: F18 cloud-init proposed rebase update

2013-05-02 Thread Pádraig Brady
FYI, I broke your change into 2 and redid the tarball to exclude the large .bzr subdir http://pkgs.fedoraproject.org/cgit/cloud-init.git/commit/?id=da2ae016 http://pkgs.fedoraproject.org/cgit/cloud-init.git/commit/?id=f9b16976 BTW I linked to the upstream source with a trick to reference the c

Re: F18 cloud-init proposed rebase update

2013-05-02 Thread Pádraig Brady
On 05/02/2013 04:49 PM, Steven Hardy wrote: > Hi, > > I've been working through debugging a number of issues with cloud-init > 0.7.1 as currently packaged for F18. > > The most major problem is that it no longer seems possible to define a user > via the user-defined cloud-config data and have th

F18 cloud-init proposed rebase update

2013-05-02 Thread Steven Hardy
Hi, I've been working through debugging a number of issues with cloud-init 0.7.1 as currently packaged for F18. The most major problem is that it no longer seems possible to define a user via the user-defined cloud-config data and have that user get an SSH authorized_keys correctly installed, wh