I would like to ensure we are properly tell users about these great features that are landing. Thus, I filed https://bugs.launchpad.net/juju-core/+bug/1220456 to document the usage and cavets for juju unset and manual ssh provisioning. Could someone knowledgeable in these implementations put in some notes on what we should tell the users. We can clean up the wording and delivery. We just need the content beyond juju help.
-thanks, Antonio On Tue, Sep 3, 2013 at 4:30 PM, Kapil Thangavelu <[email protected]> wrote: > There's one significant feature that didn't make the release notes, namely > manual provisioning via ssh has been integrated into juju add-machine. > > > > > On Mon, Sep 2, 2013 at 10:13 PM, David Cheney <[email protected]> > wrote: >> >> juju-core 1.13.3 >> ================ >> >> A new development release of Juju, juju-core 1.13.3, is now available. >> >> Getting Juju >> ------------ >> >> The location of the PPA has changed, please note the new location. >> >> juju-core 1.13.3 is available from the Juju development PPA >> >> https://launchpad.net/~juju/+archive/devel >> >> New and Notable >> --------------- >> >> * The new command “juju unset <service> <setting1> …” allows a >> configuration setting for a service to be removed. Removing the >> configuration setting will revert it to the charm default. This is the >> first step in solving #1194945. >> * The Windows Azure provider now defines a public storage container >> for tools. No configuration changes are required. Closes #1216770. >> >> Resolved issues >> --------------- >> >> * A bug relating to the formatting of tool versions has been >> resolved. This formatting error was only visible when using the -v or >> --debug flag. Closes #1216285. >> >> Configuration changes >> --------------------- >> >> * none >> >> Known issues >> ------------ >> >> * The JUJU_ENV environment variable is not being passed down to >> plugins. LP #1216254. >> * An unexpected dependency between the api server and the >> provisioning worker (which runs the same process) can cause delays >> provisioning new machines. LP #1220027. >> >> Testing on Canonistack and HP Cloud >> ----------------------------------- >> >> A publicly readable bucket has been created for holding the Juju tools >> on Canonistack. To use it, put this in your ~/.juju/environments.yaml >> (all on one line): >> >> public-bucket-url: >> >> https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60 >> >> For HP Cloud the public bucket is available at: >> >> public-bucket-url: >> https://region-a.geo-1.objects.hpcloudsvc.com/v1/60502529753910 >> >> As an unstable release we do not make guarantees about clean upgrade >> paths of running environments from one 1.13.x version to another. >> However, live-upgrades should work now, and will be a supported >> feature of stable releases. >> >> We encourage everyone to subscribe the mailing list at >> [email protected], or join us on #juju-dev on freenode. >> >> Dave Cheney >> On behalf of the Juju team >> https://launchpad.net/juju-core >> >> -- >> canonical-juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.canonical.com/mailman/listinfo/canonical-juju > > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
