On Sun, Oct 11, 2015 at 7:08 AM, Martin Packman <[email protected]> wrote: > I proposed a branch this week that alters how juju uses cloud-init to > create the ubuntu user when provisioning a machine. I've had code > review, but would appreciate further feedback: > > <http://reviews.vapour.ws/r/2860/> > > The main aim here is to avoid depending on the /etc/cloud/cloud.cfg in > the image, but keep the logic unified across *nix systems. This > includes a CentOS behaviour change that I hope is okay, removing the > shell script use setup and just using cloud-config.
I see we have https://bugs.launchpad.net/juju-core/+bug/1492066 fixed committed for 1.25 (thanks Dimiter), does this branch resolve any other known issues with deploying *Nix Specifically CentOS with Juju, or are there others we should identify here? -thanks, Antonio > > There are still a couple of things to be nervous about. The exisitng > container creation config is very much tied to ubuntu still, and I'm > not completely confident of stability across series for cloud-init > versions or default groups. > > My intention is to get a reasonable amount of testing in advance of > landing the branch, but comments welcome as well. > > Martin > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Antonio Rosales Ecosystem Engineering Canonical -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
