From c96860501ecc3f91b034e6f23fb33fcc650bf4e4 Mon Sep 17 00:00:00 2001 From: nskaggs Date: Fri, 1 Jul 2016 18:00:28 +0100 Subject: [PATCH 1/5] Release 2.0-beta11 is the current devel release. --- src/en/reference-releases.md | 10 +-- src/en/temp-release-notes.md | 169 +++++++++-------------------------- 2 files changed, 46 insertions(+), 133 deletions(-) diff --git a/src/en/reference-releases.md b/src/en/reference-releases.md index b742d92a4..53ce344ff 100644 --- a/src/en/reference-releases.md +++ b/src/en/reference-releases.md @@ -76,8 +76,8 @@ agent-stream: proposed ## Development -2.0-beta9 is currently in development for testing. -The previous development release was 2.0-beta7. +2.0-beta11 is currently in development for testing. +The previous development release was 2.0-beta10. Development releases provide new features that are being stablised. These releases are *not* suitable for production environments. Upgrading @@ -92,13 +92,13 @@ sudo apt-get install juju {: .instruction } Centos -: [juju-2.0-beta9-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-centos7.tar.gz/+md5)) +: [juju-2.0-beta11-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz/+md5)) {: .instruction } OS X -: [juju-2.0-beta9-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-osx.tar.gz/+md5)) +: [juju-2.0-beta11-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-osx.tar.gz/+md5)) {: .instruction } Windows -: [juju-setup-2.0-beta9.exe](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-setup-2.0-beta9.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-setup-2.0-beta9.exe/+md5)) +: [juju-setup-2.0-beta11.exe](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe/+md5)) {: .instruction } diff --git a/src/en/temp-release-notes.md b/src/en/temp-release-notes.md index b31a42af5..420b5be9e 100644 --- a/src/en/temp-release-notes.md +++ b/src/en/temp-release-notes.md @@ -1,32 +1,30 @@ -# Juju 2.0-beta9 +# Juju 2.0-beta11 -A new development release of Juju, juju 2.0-beta9, is now available. +A new development release of Juju, juju 2.0-beta11, is now available. This release replaces version 2.0-beta8. ## Getting Juju -Juju 2.0-beta9 is available for Yakkety and backported to earlier +Juju 2.0-beta11 is available for Yakkety and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows, Centos, and OS X users will find installers at: - https://launchpad.net/juju-core/+milestone/2.0-beta9 + https://launchpad.net/juju-core/+milestone/2.0-beta11 -Upgrading 1.x environments to 2.0-beta9 is not yet supported. Once 2.x is +Upgrading 1.x environments to 2.0-beta11 is not yet supported. Once 2.x is proven we will provide an upgrade path from 1.25 -## What's New in Beta9 - -* “Services” are now known as “Applications” -* New `juju unregister` command for cleaning up local references to controllers - Usage: juju unregister -* Removal of support for legacy lxc containers in favor of lxd -* `juju status` has been enhanced for ease of reading +## What's New in Beta11 +* Config can now be associated with clouds in clouds.yaml +* Experimental Features: + * Juju log forwarding + * Audit logging ## Notable Changes @@ -57,6 +55,9 @@ proven we will provide an upgrade path from 1.25 * Automatic Retries of Failed Hooks * Enhancements to juju run * SSH Host Key Checking +* Config can be included in clouds.yaml +* Juju log forwarding +* Audit logging * Known Issues @@ -190,7 +191,7 @@ The main new commands of note are: juju grant Juju revoke juju list-shares - juju use-model + juju use-model juju list-users juju switch-user @@ -267,7 +268,7 @@ https://jujucharms.com/docs/devel/controllers https://jujucharms.com/docs/devel/models -#### LXD, Manual, and MAAS Providers +#### LXD, Manual, and MAAS Providers To bootstrap models using the LXD, manual, and MAAS providers, see the special clouds section of: https://jujucharms.com/docs/devel/clouds @@ -355,7 +356,7 @@ key-id, manta-url ### Native Support for Charm Bundles The Juju 'deploy' command can now deploy a bundle. A bundle is a -collection of charms that together create an entire system. The +collection of charms that together create an entire system. The Juju Quickstart or Deployer plugins are no longer needed to deploy a bundle of charms. See: https://jujucharms.com/docs/devel/charms-bundles @@ -415,15 +416,15 @@ to utilize a cloud provider. LXD has been made available in Trusty backports, but needs manual dependency resolution: - + sudo apt-get --target-release trusty-backports install lxd - + Before using a locally running LXD after installing it, either through Juju or the LXD CLI ("lxc"), you must either log out and back in or run this command: - + newgrp lxd - + See: https://linuxcontainers.org/lxd/getting-started-cli/ @@ -463,7 +464,7 @@ allocating more machines than there are public IP addresses. A new provider has been added that supports hosting a Juju model in Rackspace Public Cloud. As Rackspace Cloud is based on OpenStack, -most of the features and configuration options for those two +most of the features and configuration options for those two providers are identical. @@ -472,7 +473,7 @@ providers are identical. While bootstrapping, you can now specify constraints for the bootstrap machine independently of the application constraints: - juju bootstrap --constraints + juju bootstrap --constraints --bootstrap-constraints You can also specify the series of the bootstrap machine: @@ -626,7 +627,7 @@ address to use for a given unit. There is currently a mandatory '--primary-address' argument to 'network- get', which guarantees a single IP address to be returned. -Example (within a charm hook): +Example (within a charm hook): relation-ids cluster url:2 @@ -692,14 +693,14 @@ Three new commands have been introduced: 1. juju list-resources usage: juju list-resources [options] application-or-unit - + This command shows the resources required by and those in use by an existing application or unit in your model. 2. juju push-resource usage: juju push-resource [options] application name=file - + This command uploads a file from your local disk to the juju controller to be used as a resource for a application. @@ -914,115 +915,27 @@ The SSH host keys of Juju managed machines are now tracked and are verified by t The host key checks can be disabled using the new --no-host-key-checks option for Juju’s SSH related commands. Routine use of this option is strongly discouraged. +### Config can be included in clouds.yaml +The cloud definitions in the clouds.yaml file can contain a config section which contains configuration attributes which will be used for all models hosted by the controller. + +clouds: + home-maas: + type: maas + config: + bootstrap-timeout: 900 + set-numa-control-policy: true + ### Known issues * Juju 2.0 no longer supports KVM for local provider Lp 1547665 * Cannot deploy a dense openstack bundle with native deploy Lp 1555808 - * LXD containers /etc/network/interfaces as generated by Juju gets - overwritten by LXD container start - Lp 1566801 - * HA recovery fails in azure - Lp 1593299 + * Cannot get status after restore is denied + Lp 1595686 + * [aws] adding a machine post-bootstrap on the controller model closes of + api port in controller security group + Lp 1598164 * Credentials files containing Joyent credentials must be updated to - work with beta3 and later (See "Joyent Provider No Longer Uses Manta + work with beta3 and later (See "Joyent Provider No Longer Uses Manta Storage") - - - -# Resolved issues - - * Machine agent failed to register ip addresses, borks agent - Lp 1537585 - - * 2.0 beta6: only able to access lxd containers (on maas deployed - host) from the maas network - Lp 1576674 - - * Cannot run upgrade-juju as upload-tools refers to "admin" model - post the s/admin/controller/ change - Lp 1586298 - - * Maas bridge script needs to reside in /var/tmp on precise - Lp 1587788 - - * Commands should prompt you to "juju login" if your password has - expired - Lp 1589748 - - * Juju deploy --to lxd does not create base machine - Lp 1590960 - - * Goroutine panic launching container on xenial - Lp 1592210 - - * Rename of status-set --service flag to --application breaks charms - Lp 1592733 - - * Manual: bootstrapping fails with "creating hosted model: model - already exists" - Lp 1593033 - - * Juju gui cannot create new models - Lp 1593042 - - * Include complete information in client.charminfo api call - Lp 1593188 - - * Storage: error message for unknown storage is terrible - Lp 1504637 - - * Provide a way to clean up dead controllers / models from - cache.yaml - Lp 1553059 - - * Bootstrapping gce lies about the availability zone of the - controller - Lp 1577614 - - * Functional-container-networking-lxd fails with invalid parent - device name - Lp 1581627 - - * Juju instance names could be more compact - Lp 1581893 - - * Status-history panics with badly formatted names - Lp 1583412 - - * List-* commands should be aliases for what they're listing - Lp 1585005 - - * Juju agree should tell the user what to do next - Lp 1588559 - - * Model name validation error doesn't specify model name - Lp 1590095 - - * Maas 1.9.3 + juju 1.25.5 - on the juju controller node eth0 and - juju-br0 interfaces have the same ip address at the same time - Lp 1590689 - - * Juju status with default tabular format or juju list-machines does - not show containers and can hide errors - Lp 1571545 - - * Juju register not clear that you're creating a new password - Lp 1576318 - - * Help for juju run-action refers to commands that don't exist - Lp 1588095 - - * Juju status with no controllers offers up juju switch - Lp 1589061 - - * Alias a 'foos' to list-foos - Lp 1589066 - - * List-actions should produce tabular output - Lp 1590205 - - * Juju list-controllers --format=yaml displays controller that - cannot be addressed. - Lp 1588924 From 9f3b04b10780adc86c80d62d0abc41ce01fff44e Mon Sep 17 00:00:00 2001 From: Nicholas Skaggs Date: Fri, 1 Jul 2016 18:04:00 +0100 Subject: [PATCH 2/5] Release 2.0-beta11 is the current devel release. --- src/en/reference-releases.md | 10 +-- src/en/temp-release-notes.md | 169 +++++++++-------------------------- 2 files changed, 46 insertions(+), 133 deletions(-) diff --git a/src/en/reference-releases.md b/src/en/reference-releases.md index b742d92a4..53ce344ff 100644 --- a/src/en/reference-releases.md +++ b/src/en/reference-releases.md @@ -76,8 +76,8 @@ agent-stream: proposed ## Development -2.0-beta9 is currently in development for testing. -The previous development release was 2.0-beta7. +2.0-beta11 is currently in development for testing. +The previous development release was 2.0-beta10. Development releases provide new features that are being stablised. These releases are *not* suitable for production environments. Upgrading @@ -92,13 +92,13 @@ sudo apt-get install juju {: .instruction } Centos -: [juju-2.0-beta9-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-centos7.tar.gz/+md5)) +: [juju-2.0-beta11-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz/+md5)) {: .instruction } OS X -: [juju-2.0-beta9-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-2.0-beta9-osx.tar.gz/+md5)) +: [juju-2.0-beta11-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-osx.tar.gz/+md5)) {: .instruction } Windows -: [juju-setup-2.0-beta9.exe](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-setup-2.0-beta9.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta9/+download/juju-setup-2.0-beta9.exe/+md5)) +: [juju-setup-2.0-beta11.exe](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe/+md5)) {: .instruction } diff --git a/src/en/temp-release-notes.md b/src/en/temp-release-notes.md index b31a42af5..420b5be9e 100644 --- a/src/en/temp-release-notes.md +++ b/src/en/temp-release-notes.md @@ -1,32 +1,30 @@ -# Juju 2.0-beta9 +# Juju 2.0-beta11 -A new development release of Juju, juju 2.0-beta9, is now available. +A new development release of Juju, juju 2.0-beta11, is now available. This release replaces version 2.0-beta8. ## Getting Juju -Juju 2.0-beta9 is available for Yakkety and backported to earlier +Juju 2.0-beta11 is available for Yakkety and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows, Centos, and OS X users will find installers at: - https://launchpad.net/juju-core/+milestone/2.0-beta9 + https://launchpad.net/juju-core/+milestone/2.0-beta11 -Upgrading 1.x environments to 2.0-beta9 is not yet supported. Once 2.x is +Upgrading 1.x environments to 2.0-beta11 is not yet supported. Once 2.x is proven we will provide an upgrade path from 1.25 -## What's New in Beta9 - -* “Services” are now known as “Applications” -* New `juju unregister` command for cleaning up local references to controllers - Usage: juju unregister -* Removal of support for legacy lxc containers in favor of lxd -* `juju status` has been enhanced for ease of reading +## What's New in Beta11 +* Config can now be associated with clouds in clouds.yaml +* Experimental Features: + * Juju log forwarding + * Audit logging ## Notable Changes @@ -57,6 +55,9 @@ proven we will provide an upgrade path from 1.25 * Automatic Retries of Failed Hooks * Enhancements to juju run * SSH Host Key Checking +* Config can be included in clouds.yaml +* Juju log forwarding +* Audit logging * Known Issues @@ -190,7 +191,7 @@ The main new commands of note are: juju grant Juju revoke juju list-shares - juju use-model + juju use-model juju list-users juju switch-user @@ -267,7 +268,7 @@ https://jujucharms.com/docs/devel/controllers https://jujucharms.com/docs/devel/models -#### LXD, Manual, and MAAS Providers +#### LXD, Manual, and MAAS Providers To bootstrap models using the LXD, manual, and MAAS providers, see the special clouds section of: https://jujucharms.com/docs/devel/clouds @@ -355,7 +356,7 @@ key-id, manta-url ### Native Support for Charm Bundles The Juju 'deploy' command can now deploy a bundle. A bundle is a -collection of charms that together create an entire system. The +collection of charms that together create an entire system. The Juju Quickstart or Deployer plugins are no longer needed to deploy a bundle of charms. See: https://jujucharms.com/docs/devel/charms-bundles @@ -415,15 +416,15 @@ to utilize a cloud provider. LXD has been made available in Trusty backports, but needs manual dependency resolution: - + sudo apt-get --target-release trusty-backports install lxd - + Before using a locally running LXD after installing it, either through Juju or the LXD CLI ("lxc"), you must either log out and back in or run this command: - + newgrp lxd - + See: https://linuxcontainers.org/lxd/getting-started-cli/ @@ -463,7 +464,7 @@ allocating more machines than there are public IP addresses. A new provider has been added that supports hosting a Juju model in Rackspace Public Cloud. As Rackspace Cloud is based on OpenStack, -most of the features and configuration options for those two +most of the features and configuration options for those two providers are identical. @@ -472,7 +473,7 @@ providers are identical. While bootstrapping, you can now specify constraints for the bootstrap machine independently of the application constraints: - juju bootstrap --constraints + juju bootstrap --constraints --bootstrap-constraints You can also specify the series of the bootstrap machine: @@ -626,7 +627,7 @@ address to use for a given unit. There is currently a mandatory '--primary-address' argument to 'network- get', which guarantees a single IP address to be returned. -Example (within a charm hook): +Example (within a charm hook): relation-ids cluster url:2 @@ -692,14 +693,14 @@ Three new commands have been introduced: 1. juju list-resources usage: juju list-resources [options] application-or-unit - + This command shows the resources required by and those in use by an existing application or unit in your model. 2. juju push-resource usage: juju push-resource [options] application name=file - + This command uploads a file from your local disk to the juju controller to be used as a resource for a application. @@ -914,115 +915,27 @@ The SSH host keys of Juju managed machines are now tracked and are verified by t The host key checks can be disabled using the new --no-host-key-checks option for Juju’s SSH related commands. Routine use of this option is strongly discouraged. +### Config can be included in clouds.yaml +The cloud definitions in the clouds.yaml file can contain a config section which contains configuration attributes which will be used for all models hosted by the controller. + +clouds: + home-maas: + type: maas + config: + bootstrap-timeout: 900 + set-numa-control-policy: true + ### Known issues * Juju 2.0 no longer supports KVM for local provider Lp 1547665 * Cannot deploy a dense openstack bundle with native deploy Lp 1555808 - * LXD containers /etc/network/interfaces as generated by Juju gets - overwritten by LXD container start - Lp 1566801 - * HA recovery fails in azure - Lp 1593299 + * Cannot get status after restore is denied + Lp 1595686 + * [aws] adding a machine post-bootstrap on the controller model closes of + api port in controller security group + Lp 1598164 * Credentials files containing Joyent credentials must be updated to - work with beta3 and later (See "Joyent Provider No Longer Uses Manta + work with beta3 and later (See "Joyent Provider No Longer Uses Manta Storage") - - - -# Resolved issues - - * Machine agent failed to register ip addresses, borks agent - Lp 1537585 - - * 2.0 beta6: only able to access lxd containers (on maas deployed - host) from the maas network - Lp 1576674 - - * Cannot run upgrade-juju as upload-tools refers to "admin" model - post the s/admin/controller/ change - Lp 1586298 - - * Maas bridge script needs to reside in /var/tmp on precise - Lp 1587788 - - * Commands should prompt you to "juju login" if your password has - expired - Lp 1589748 - - * Juju deploy --to lxd does not create base machine - Lp 1590960 - - * Goroutine panic launching container on xenial - Lp 1592210 - - * Rename of status-set --service flag to --application breaks charms - Lp 1592733 - - * Manual: bootstrapping fails with "creating hosted model: model - already exists" - Lp 1593033 - - * Juju gui cannot create new models - Lp 1593042 - - * Include complete information in client.charminfo api call - Lp 1593188 - - * Storage: error message for unknown storage is terrible - Lp 1504637 - - * Provide a way to clean up dead controllers / models from - cache.yaml - Lp 1553059 - - * Bootstrapping gce lies about the availability zone of the - controller - Lp 1577614 - - * Functional-container-networking-lxd fails with invalid parent - device name - Lp 1581627 - - * Juju instance names could be more compact - Lp 1581893 - - * Status-history panics with badly formatted names - Lp 1583412 - - * List-* commands should be aliases for what they're listing - Lp 1585005 - - * Juju agree should tell the user what to do next - Lp 1588559 - - * Model name validation error doesn't specify model name - Lp 1590095 - - * Maas 1.9.3 + juju 1.25.5 - on the juju controller node eth0 and - juju-br0 interfaces have the same ip address at the same time - Lp 1590689 - - * Juju status with default tabular format or juju list-machines does - not show containers and can hide errors - Lp 1571545 - - * Juju register not clear that you're creating a new password - Lp 1576318 - - * Help for juju run-action refers to commands that don't exist - Lp 1588095 - - * Juju status with no controllers offers up juju switch - Lp 1589061 - - * Alias a 'foos' to list-foos - Lp 1589066 - - * List-actions should produce tabular output - Lp 1590205 - - * Juju list-controllers --format=yaml displays controller that - cannot be addressed. - Lp 1588924 From 487b35a5fced79b2e7fc4206da17e5e8cb10fa58 Mon Sep 17 00:00:00 2001 From: Nicholas Skaggs Date: Fri, 1 Jul 2016 18:47:02 +0100 Subject: [PATCH 3/5] fix conflicts --- src/en/reference-releases.md | 17 +++++++++++++++++ src/en/temp-release-notes.md | 26 +++++++++----------------- 2 files changed, 26 insertions(+), 17 deletions(-) diff --git a/src/en/reference-releases.md b/src/en/reference-releases.md index 53ce344ff..4b9b84c9b 100644 --- a/src/en/reference-releases.md +++ b/src/en/reference-releases.md @@ -76,8 +76,13 @@ agent-stream: proposed ## Development +<<<<<<< HEAD 2.0-beta11 is currently in development for testing. The previous development release was 2.0-beta10. +======= +2.0-beta8 is currently in development for testing. +The previous development release was 2.0-beta7. +>>>>>>> parent of 24a56d1... Release 2.0-beta9 is the current devel release. Development releases provide new features that are being stablised. These releases are *not* suitable for production environments. Upgrading @@ -92,6 +97,7 @@ sudo apt-get install juju {: .instruction } Centos +<<<<<<< HEAD : [juju-2.0-beta11-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-2.0-beta11-centos7.tar.gz/+md5)) {: .instruction } @@ -101,4 +107,15 @@ OS X Windows : [juju-setup-2.0-beta11.exe](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta11/+download/juju-setup-2.0-beta11.exe/+md5)) +======= +: [juju-2.0-beta8-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-2.0-beta8-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-2.0-beta8-centos7.tar.gz/+md5)) +{: .instruction } + +OS X +: [juju-2.0-beta8-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-2.0-beta8-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-2.0-beta8-osx.tar.gz/+md5)) +{: .instruction } + +Windows +: [juju-setup-2.0-beta8.exe](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-setup-2.0-beta8.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta8/+download/juju-setup-2.0-beta8.exe/+md5)) +>>>>>>> parent of 24a56d1... Release 2.0-beta9 is the current devel release. {: .instruction } diff --git a/src/en/temp-release-notes.md b/src/en/temp-release-notes.md index 420b5be9e..f00030925 100644 --- a/src/en/temp-release-notes.md +++ b/src/en/temp-release-notes.md @@ -1,28 +1,15 @@ # Juju 2.0-beta11 A new development release of Juju, juju 2.0-beta11, is now available. -This release replaces version 2.0-beta8. - - -## Getting Juju - -Juju 2.0-beta11 is available for Yakkety and backported to earlier -series in the following PPA: - - https://launchpad.net/~juju/+archive/devel - -Windows, Centos, and OS X users will find installers at: - - https://launchpad.net/juju-core/+milestone/2.0-beta11 - -Upgrading 1.x environments to 2.0-beta11 is not yet supported. Once 2.x is -proven we will provide an upgrade path from 1.25 +This release replaces version 2.0-beta10. ## What's New in Beta11 * Config can now be associated with clouds in clouds.yaml -* Experimental Features: +* Consistent wire protocol for the Juju API. For more details, see: + https://lists.ubuntu.com/archives/juju-dev/2016-June/005715.html +* Initial support for: * Juju log forwarding * Audit logging @@ -925,6 +912,11 @@ clouds: bootstrap-timeout: 900 set-numa-control-policy: true +### Juju Log forwarding + +### + + ### Known issues * Juju 2.0 no longer supports KVM for local provider From 26124708b6b8cced5bb7842fe1db7a0227e8da98 Mon Sep 17 00:00:00 2001 From: Nicholas Skaggs Date: Sat, 2 Jul 2016 00:13:07 +0100 Subject: [PATCH 4/5] add audit log --- src/en/temp-release-notes.md | 55 ++++++++++++++++++++++++++++++++++-- 1 file changed, 53 insertions(+), 2 deletions(-) diff --git a/src/en/temp-release-notes.md b/src/en/temp-release-notes.md index ac6de9c40..110a93e95 100644 --- a/src/en/temp-release-notes.md +++ b/src/en/temp-release-notes.md @@ -3,7 +3,6 @@ A new development release of Juju, juju 2.0-beta11, is now available. This release replaces version 2.0-beta10. - ## What's New in Beta11 * Config can now be associated with clouds in clouds.yaml @@ -914,9 +913,60 @@ clouds: ### Juju Log Forwarding +Log forwarding is a bare bones implementation which is undergoing ongoing development work to improve the user experience. It should be considered only as a proof of concept. When enabled, log messages for all hosted models in a controller are forwarded to a syslog server. Currently, all required config to activate the feature needs to be provided at bootstrap via a config.yaml file. + +$ juju bootstrap --config logconfig.yaml + +The contents of the yaml file should currently be as follows: + +syslog-host: : +syslog-ca-cert: | + -----BEGIN CERTIFICATE----- + + -----END CERTIFICATE----- +syslog-client-cert: | + -----BEGIN CERTIFICATE----- + + -----END CERTIFICATE----- +syslog-client-key: | + -----BEGIN PRIVATE KEY----- + + -----END PRIVATE KEY----- + +#### Wire Format +Syslog messages will be sent using the RFC 5424 message format. We make use of the structured data facility defined in the more recent RFC. + +Log Messages: +The facility code will be 1 (user level message). Severity will be mapped as follows: +Juju ERROR = Error (3) +Juju WARNING = Warning (4) +Juju INFO = Informational (6) +Juju DEBUG = Debug (7) +Juju TRACE = Debug (7) + +Messages will use structured data to record relevant environment and user action parameters. Key pair definitions will be: + +SDID: origin +enterpriseId: 28978 (Canonical, Ltd.) +software: jujud +swVersion: + +SDID: model@28978 +controller-uuid: +model-uuid: + +SDID: log@28978 +source: : +module: +#### Example log (error) message + +<11>1 2016-02-28T09:57:10.804642398-05:00 172.12.3.1 juju - - [origin enterpriseId="28978" software="jujud" "2.0.0"] [model@28978 controller-uuid="deadbeef" model-uuid="deadbeef"] [log@28978 source-file="provider/ec2/storage.go" source-line="60"] Could not initialise machine block storage + ### Audit Logging -In its initial implementation, audit logging is on by default. The audit log will be in /var/log/juju/audit.log for each controller. +In its initial implementation, audit logging is on by default. The audit log will be in /var/log/juju/audit.log for each controller machine. If running in an HA environment, the audit.log files on each controller machine must be collated to get a complete log. Future releases will provide a utility to merge the logs, akin to debug-log. + +Since users may interact with Juju from multiple sources (CLI, GUI, deployer, etc.), audit log entries record the API calls made, rather than only reporting CLI commands run. Only those API calls originating from authenticated users calling the external API are logged. ### Known issues @@ -934,6 +984,7 @@ In its initial implementation, audit logging is on by default. The audit log wi Storage") + # Resolved issues * Ha recovery fails in azure From 5429687438300cde0174a4ee5ef50f1dba52eb90 Mon Sep 17 00:00:00 2001 From: Nicholas Skaggs Date: Thu, 11 Aug 2016 17:49:08 -0400 Subject: [PATCH 5/5] Release 2.0-beta15 is the current devel release. --- src/en/reference-releases.md | 8 +- src/en/temp-release-notes.md | 214 ++++++++++++----------------------- 2 files changed, 76 insertions(+), 146 deletions(-) diff --git a/src/en/reference-releases.md b/src/en/reference-releases.md index 0a76185e5..53971dbed 100644 --- a/src/en/reference-releases.md +++ b/src/en/reference-releases.md @@ -76,7 +76,7 @@ agent-stream: proposed ## Development -2.0-beta14 is currently in development for testing. +2.0-beta15 is currently in development for testing. The previous development release was 2.0-beta13. Development releases provide new features that are being stablised. @@ -92,13 +92,13 @@ sudo apt-get install juju {: .instruction } Centos -: [juju-2.0-beta14-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-2.0-beta14-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-2.0-beta14-centos7.tar.gz/+md5)) +: [juju-2.0-beta15-centos7.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-2.0-beta15-centos7.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-2.0-beta15-centos7.tar.gz/+md5)) {: .instruction } OS X -: [juju-2.0-beta14-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-2.0-beta14-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-2.0-beta14-osx.tar.gz/+md5)) +: [juju-2.0-beta15-osx.tar.gz](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-2.0-beta15-osx.tar.gz) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-2.0-beta15-osx.tar.gz/+md5)) {: .instruction } Windows -: [juju-setup-2.0-beta14.exe](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-setup-2.0-beta14.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta14/+download/juju-setup-2.0-beta14.exe/+md5)) +: [juju-setup-2.0-beta15.exe](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-setup-2.0-beta15.exe) ([md5](https://launchpad.net/juju-core/trunk/2.0-beta15/+download/juju-setup-2.0-beta15.exe/+md5)) {: .instruction } diff --git a/src/en/temp-release-notes.md b/src/en/temp-release-notes.md index a9a3b0546..fb483d67a 100644 --- a/src/en/temp-release-notes.md +++ b/src/en/temp-release-notes.md @@ -1,30 +1,22 @@ -# Juju 2.0-beta12 - -A new development release of Juju, juju 2.0-beta14, is now available. -This release replaces version 2.0-beta13. - - -## What's New in Beta14 - -* New model config capability allows managing custom configuration on - models much easier. See “Shared Model Config” in the release notes. -* First baby step to an interactive bootstrap experience. Look for - more on this in future betas. -* Ensure that openstack clouds that are configured to support - Multi-hypervisors. Juju can deploy workloads to the desired - hypervisor. - Lp 1600054 -* Juju will detect LXD default profile's bridge name and use it. - Lp 1575676 -* Added support for the remove-user command. - Lp 1570096 -* Improve the scalability when destroying large models. - Lp 1579010 -* Print a more user friendly error message when an api request is made - and a model uuid is not found - Lp 1602034 -* Updated fix for 'duplicate key error' - Lp 1593828, Lp 1604644 +# Juju 2.0-beta15 + +A new development release of Juju, juju 2.0-beta15, is now available. +This release replaces version 2.0-beta14. + + +## What's New in beta15 + +This releases addresses stability and performance issues including 29 bugs +from b14 last week. Some notable ones include: + +* lxd containers not using configured proxy for downloading images + LP 1594720 https://bugs.launchpad.net/juju-core/+bug/1594720 +* juju2 beta11 unable to parse PORT during a maas bootstrap + LP 1599972 https://bugs.launchpad.net/juju-core/+bug/1599972 +* LXD no longer activates all interfaces on initial deploy when using MAAS2rc3 and JUJU Beta13 + LP 1608105 https://bugs.launchpad.net/juju-core/+bug/1608105 +* It is not possible to refer to multiple models with the same name from the CLI + LP 1597720 https://bugs.launchpad.net/juju-core/+bug/1597720 ## Notable Changes @@ -60,7 +52,7 @@ This release replaces version 2.0-beta13. * Juju log forwarding * Audit logging * Model permissions -* application-version-set +* New hook command: application-version-set * Shared Model Config * Known Issues @@ -348,7 +340,6 @@ https://jujucharms.com/docs/devel/users-auth https://jujucharms.com/docs/devel/users-creating https://jujucharms.com/docs/devel/users-manage - ### Joyent Provider No Longer Uses Manta Storage The use of Joyent Manta Storage is no longer necessary and has been @@ -417,7 +408,6 @@ your local model more like a traditional Juju model. Because of this, you can test things like Juju high-availability without needing to utilize a cloud provider. - #### Setting up LXD on older series LXD has been made available in Trusty backports, but needs manual @@ -627,11 +617,8 @@ endpoints explicitly. #### New Hook Command: network-get -When deploying an application with endpoint bindings specified, charm authors -can use the new "network-get" hook command to determine which address to -advertise for a given endpoint. This approach will eventually replace "unit-get -private-address" as well as various other ways to get the address to use for a -given unit. +When deploying an application with endpoint bindings specified, charm authors can use the new "network-get" hook command to determine which address to advertise for a given endpoint. This approach will eventually replace "unit-get private-address" as well as various other ways to get the +address to use for a given unit. There is currently a mandatory '--primary-address' argument to 'network- get', which guarantees a single IP address to be returned. @@ -904,47 +891,28 @@ juju. This currently happens with an exponential backoff with a factor of 2 star A model config flag `automatically-retry-hooks` is now available that will toggle this behavior. It affects all the units running in the same model. By default the flag is true and that is the recommended value for regular deployments. It is toggleable mainly for debugging purposes. - ### Enhancements to juju run Starting from 2.0 juju run will work by queueing actions using the name 'Juju-run'. The command line API has not changed. A few things to note: -* Juju run is now supported on windows machines. The commands will be executed - through powershell. -* Any actions named 'juju-run' defined in the charm will **not** work anymore. - The charm build tool will forbid any actions starting with 'juju-' to be - defined, similar to relations. -* Because the commands are now actions statistics related to queue times, - execution times, etc. can be gathered. -* The specified timeout is only taken into account when actually executing the - action and does **not** account for delays that might come from the action - waiting to be executed. +* Juju run is now supported on windows machines. The commands will be executed through powershell. +* Any actions named 'juju-run' defined in the charm will **not** work anymore. The charm build tool will forbid any actions starting with 'juju-' to be defined, similar to relations. +* Because the commands are now actions statistics related to queue times, execution times, etc. can be gathered. +* The specified timeout is only taken into account when actually executing the action and does **not** account for delays that might come from the action waiting to be executed. * `show-action-status` will also list actions queued by `juju-run` -* To avoid flooding a new flag has been created for `show-action-status`. - You can now use `--name ` to only get the actions corresponding - to a particular name. +* To avoid flooding a new flag has been created for `show-action-status`. You can now use `--name ` to only get the actions corresponding to a particular name. * `show-action-output` can be used to get more information on a - particular command. +particular command. ### SSH Host Key Checking +The SSH host keys of Juju managed machines are now tracked and are verified by the juju ssh, scp and debug-hooks commands. This ensures that SSH connections established by these commands are actually made to the intended hosts, removing the possibility of man-in-the-middle attacks. -The SSH host keys of Juju managed machines are now tracked and are verified by -the juju ssh, scp and debug-hooks commands. This ensures that SSH connections -established by these commands are actually made to the intended hosts, removing -the possibility of man-in-the-middle attacks. - -The host key checks can be disabled using the new --no-host-key-checks option -for Juju's SSH related commands. Routine use of this option is strongly -discouraged. - +The host key checks can be disabled using the new --no-host-key-checks option for Juju’s SSH related commands. Routine use of this option is strongly discouraged. ### Config can be included in clouds.yaml - -The cloud definitions in the clouds.yaml file can contain a config section which -contains configuration attributes which will be used for all models hosted by -the controller. +The cloud definitions in the clouds.yaml file can contain a config section which contains configuration attributes which will be used for all models hosted by the controller. clouds: home-maas: @@ -955,12 +923,10 @@ clouds: ### Juju Log Forwarding -When enabled, log messages for all hosted models in a controller are forwarded -to a syslog server over a secure TLS connection. The easiest way to configure -the feature is to provide a config.yaml file at bootstrap. +When enabled, log messages for all hosted models in a controller are forwarded to a syslog server over a secure TLS connection. The easiest way to configure the feature is to provide a config.yaml file at bootstrap. - juju bootstrap - --config logforward-enabled=true --config logconfig.yaml +$ juju bootstrap + --config logforward-enabled=true --config logconfig.yaml The contents of the yaml file should currently be as follows: @@ -978,27 +944,20 @@ syslog-client-key: | -----END PRIVATE KEY----- -The feature can be toggled on or off by setting the logforward-enabled -attribute. When enabled, a maximum of 100 previous log lines will be forwarded - +The feature can be toggled on or off by setting the logforward-enabled attribute. When enabled, a maximum of 100 previous log lines will be forwarded #### Wire Format - -Syslog messages will be sent using the RFC 5424 message format. We make use of -the structured data facility defined in the more recent RFC. +Syslog messages will be sent using the RFC 5424 message format. We make use of the structured data facility defined in the more recent RFC. Log Messages: -The facility code will be 1 (user level message). Severity will be -mapped as follows: +The facility code will be 1 (user level message). Severity will be mapped as follows: +Juju ERROR = Error (3) +Juju WARNING = Warning (4) +Juju INFO = Informational (6) +Juju DEBUG = Debug (7) +Juju TRACE = Debug (7) - Juju ERROR = Error (3) - Juju WARNING = Warning (4) - Juju INFO = Informational (6) - Juju DEBUG = Debug (7) - Juju TRACE = Debug (7) - -Messages will use structured data to record relevant environment and user action -parameters. Key pair definitions will be: +Messages will use structured data to record relevant environment and user action parameters. Key pair definitions will be: SDID: origin enterpriseId: 28978 (Canonical, Ltd.) @@ -1012,59 +971,38 @@ model-uuid: SDID: log@28978 source: : module: - - #### Example log (error) message - <11>1 2016-02-28T09:57:10.804642398-05:00 172.12.3.1 juju - - [origin enterpriseId="28978" software="jujud" "2.0.0"] [model@28978 controller-uuid="deadbeef" model-uuid="deadbeef"] [log@28978 source-file="provider/ec2/storage.go" source-line="60"] Could not initialise machine block storage - +<11>1 2016-02-28T09:57:10.804642398-05:00 172.12.3.1 juju - - [origin enterpriseId="28978" software="jujud" "2.0.0"] [model@28978 controller-uuid="deadbeef" model-uuid="deadbeef"] [log@28978 source-file="provider/ec2/storage.go" source-line="60"] Could not initialise machine block storage ### Audit Logging -In its initial implementation, audit logging is on by default. The audit log -will be in /var/log/juju/audit.log for each controller machine. If running in -an HA environment, the audit.log files on each controller machine must be -collated to get a complete log. Future releases will provide a utility to merge -the logs, akin to debug-log. - -Since users may interact with Juju from multiple sources (CLI, GUI, deployer, -etc.), audit log entries record the API calls made, rather than only reporting -CLI commands run. Only those API calls originating from authenticated users -calling the external API are logged. +In its initial implementation, audit logging is on by default. The audit log will be in /var/log/juju/audit.log for each controller machine. If running in an HA environment, the audit.log files on each controller machine must be collated to get a complete log. Future releases will provide a utility to merge the logs, akin to debug-log. +Since users may interact with Juju from multiple sources (CLI, GUI, deployer, etc.), audit log entries record the API calls made, rather than only reporting CLI commands run. Only those API calls originating from authenticated users calling the external API are logged. ### Model permissions -Three level of permissions are now available for users on models. A user can be -given one of three level of permissions on each one of the models in a -controller. - +Three level of permissions are now available for users on models. +A user can be given one of three level of permissions on each one of the models in a controller. The permissions for a model are: - * Read: The user can login to the model and obtain status and information - about it. + * Read: The user can login to the model and obtain status and information about it. * Write: The user can deploy/delete services and add relations into a model. - * Admin: The user has full control over the model except for controller - level actions such as deletion. Model owners can delete their own models. - + * Admin: The user has full control over the model except for controller level actions such as deletion. Model owners can delete their own models. ### application-version-set -Charm authors may trigger this command from any hook to output what version of -the application is running. This could be a package version, for instance -postgres version 9.5. It could also be a build number or version control -revision identifier, for instance git sha 6fb7ba68. The version details will -then be displayed in "juju status" output with the application details. - -Example (within a charm hook): +Charm authors may trigger this command from any hook to output what version of the application is running. This could be a package version, for instance postgres version 9.5. It could also be a build number or version control revision identifier, for instance git sha 6fb7ba68. The version details will then be displayed in "juju status" output with the application details. - application-version-set 9.5.3 +Example (within a charm hook): + + $ application-version-set 9.5.3 Then application status will show: APP VERSION STATUS EXPOSED ORIGIN CHARM REV OS postgresql 9.5.3 active false local postgresql 0 ubuntu - ### Shared Model Config New/changed commands relevant to this feature: @@ -1088,20 +1026,19 @@ The management of hosted model configuration has been improved in several ways: There are 3 sources of model attribute values: 1. default - hard coded into Juju - 2. controller - shared by all models created on controllers within an HA - environment + 2. controller - shared by all models created on controllers within an HA environment 3. model - set by the user An example juju model-config output: ATTRIBUTE FROM VALUE - agent-metadata-url default + agent-metadata-url default agent-stream default released agent-version model 2.0-beta14.4 - apt-ftp-proxy default - apt-http-proxy default - apt-https-proxy default - apt-mirror default + apt-ftp-proxy default + apt-http-proxy default + apt-https-proxy default + apt-mirror default automatically-retry-hooks default True default-series default xenial development default False @@ -1110,10 +1047,10 @@ An example juju model-config output: enable-os-upgrade default True firewall-mode default instance ftp-proxy controller http://local - http-proxy default - https-proxy default + http-proxy default + https-proxy default ignore-machine-addresses default False - image-metadata-url default + image-metadata-url default image-stream default released logforward-enabled default False logging-config model =INFO;unit=DEBUG @@ -1135,18 +1072,14 @@ Points of note are that: - the FROM value is calculated dynamically so that if a default value changes to match the model, the output is adjusted accordingly -The behaviour of juju unset-model-config has changed. Previously, any unset -attribute would revert to the empty value. Now, the value will revert to the -closest inherited value. In the case above: - +The behaviour of juju unset-model-config has changed. Previously, any unset attribute would revert to the empty value. Now, the value will revert to the closest inherited value. In the case above: - ftp-proxy has inherited the controller value http://local - juju set-model-config ftp-proxy=http://another will set a new "model" value for this attribute - juju unset-model-config ftp-proxy will revert to the controller value http://local -For this release, shared controller config attributes are specified in the -clouds.yaml file. +For this release, shared controller config attributes are specified in the clouds.yaml file. clouds: lxdtest: @@ -1156,9 +1089,7 @@ clouds.yaml file. set-numa-control-policy: true ftp-proxy: http://local -These cannot be changed once set. The next Juju beta will include new -functionality to: - +These cannot be changed once set. The next Juju beta will include new functionality to: - set and unset shared controller attributes - display the values of shared attributes used when creating models, and where those attributes are defined (default or controller) @@ -1172,12 +1103,11 @@ functionality to: Lp 1547665 * Cannot deploy a dense openstack bundle with native deploy Lp 1555808 - * grant-revoke: reenabled users missing from list-users - Lp 1609494 - * backup-restore failed creating collection EOF - Lp 1605653 - * Juju 2.0-beta12 userdata execution fails on Windows - Lp 1604474 + * Cannot get status after restore is denied + Lp 1595686 + * [aws] adding a machine post-bootstrap on the controller model closes of + api port in controller security group + Lp 1598164 * Credentials files containing Joyent credentials must be updated to - work with beta3 and later (See "Joyent Provider No Longer Uses Manta + work with beta3 and later (See "Joyent Provider No Longer Uses Manta Storage")