Re: juju devel 2.0-beta4 is released
Great news, kudos all! Please note that although the example states "juju upgrade-gui 2.1.1" we've replaced 2.1.1 version with 2.1.2, which is also the default one that get's installed. Have fun. On Fri, Apr 15, 2016 at 6:38 AM, Curtis Hovey-Canonical < cur...@canonical.com> wrote: > # juju 2.0-beta4 > > A new development release of Juju, juju 2.0-beta4, is now available. > This release replaces version 2.0-beta3. > > > ## Getting Juju > > Juju 2.0-beta4 is available for Xenial 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-beta4 > > Upgrading to this development releases is not supported. > > > ## The complete release notes available on the Web > > The release notes for Juju 2.0-beta4 are very long. They are too large > to post to a list. The complete release notes are published at > > https://jujucharms.com/docs/devel/temp-release-notes > > > ## Getting started with Juju 2.0 > > Juju 2.0 allows you to get started creating models without modifying any > definition files. Just provide your credentials and go! (Note: to > fully understand the new bootstrap experience please see the "New > Bootstrap and Cloud Management Experience" section below) > > * LXD provider (requires lxd 2.0.0~rc9 or later): > The LXD provider requires no credentials, so you can create a > controller by just specifying its name: > > juju bootstrap lxd > > Note that the lxdbr0 bridge needs to be properly configured for the lxd > provider to work, for details see: > http://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/ > > * Public Clouds: > Known public clouds can be listed with juju list-clouds: > > juju list-clouds > > CLOUD TYPEREGIONS > awsec2 us-east-1, us-west-1, us-west-2, ... > aws-china ec2 cn-north-1 > aws-govec2 us-gov-west-1 > azure azure japanwest, centralindia, eastus2, > ... > azure-chinaazure chinaeast, chinanorth > cloudsigma cloudsigma mia, sjc, wdc, zrh, hnl > google gce us-east1, us-central1, ... > joyent joyent us-east-1, us-east-2, us-east-3, … > lxdlxd > maas maas > manual manual > rackspace rackspace LON, SYD, HKG, DFW, ORD, IAD > > Add your credentials using either: > > juju add-credential > or > juju add-credential -f creds.yaml > or > juju autoload-credentials > > When specifying just the cloud, juju add-credential will allow a new > credential to be added interactively. You will be prompted type the > required credential attributes. Example: > > juju add-credential maas > credential name: hmaas > replace existing credential? [y/N]: y > auth-type: oauth1 > maas-oauth: > credentials added for cloud maas > > The new credentials.yaml file at: ~/.local/share/juju/credentials.yaml > > The autoload tool will search for existing credentials for AWS, > OpenStack/Rackspace, and Google clouds. You will then be prompted for > which ones you'd like to save. > > If you have an existing credential.yaml file, you can also import a > named credential, eg for MAAS > > cat credentials.yaml > > credentials: > maas: >my-credentials: > auth-type: oauth1 > maas-oauth: > > or, for AWS > > cat credentials.yaml > > credentials: > aws: > default-credential: my-credentials > my-credentials: > auth-type: access-key > access-key: > secret-key: > > Bootstrap using your default credentials: > > juju bootstrap [/region] > > Examples: > > juju bootstrap aws-controller aws > > juju bootstrap mass-controller maas/192.168.0.1 > > In the MAAS example above, you specify the host address of the MAAS > controller. So to use Juju on MAAS out of the box, you set up a > credentials file (either interactively, or based on the example above) > and then bootstrap. This avoids the need for any cloud configuration. > But it's also possible to set up a named MAAS cloud definition as > explained later. > > More details on the new bootstrap experience, including defining private > clouds can be found in the New Bootstrap and Cloud Management Experience > section. > > > ## What's New in Beta4 > > * Mongo 3.2 is now used when bootstrapping on Xenial hosts > * address-allocation feature flag no longer supported in MAAS provider > * prefer-ipv6 setting is now ignored in all providers > * MAAS 1.9+ provisioned LXD containers now have a bridge per NIC > * Accurate address selection based on spaces (in MAAS) > * extra-bindings support for charms metadata > *
juju devel 2.0-beta4 is released
# juju 2.0-beta4 A new development release of Juju, juju 2.0-beta4, is now available. This release replaces version 2.0-beta3. ## Getting Juju Juju 2.0-beta4 is available for Xenial 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-beta4 Upgrading to this development releases is not supported. ## The complete release notes available on the Web The release notes for Juju 2.0-beta4 are very long. They are too large to post to a list. The complete release notes are published at https://jujucharms.com/docs/devel/temp-release-notes ## Getting started with Juju 2.0 Juju 2.0 allows you to get started creating models without modifying any definition files. Just provide your credentials and go! (Note: to fully understand the new bootstrap experience please see the "New Bootstrap and Cloud Management Experience" section below) * LXD provider (requires lxd 2.0.0~rc9 or later): The LXD provider requires no credentials, so you can create a controller by just specifying its name: juju bootstrap lxd Note that the lxdbr0 bridge needs to be properly configured for the lxd provider to work, for details see: http://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/ * Public Clouds: Known public clouds can be listed with juju list-clouds: juju list-clouds CLOUD TYPEREGIONS awsec2 us-east-1, us-west-1, us-west-2, ... aws-china ec2 cn-north-1 aws-govec2 us-gov-west-1 azure azure japanwest, centralindia, eastus2, ... azure-chinaazure chinaeast, chinanorth cloudsigma cloudsigma mia, sjc, wdc, zrh, hnl google gce us-east1, us-central1, ... joyent joyent us-east-1, us-east-2, us-east-3, … lxdlxd maas maas manual manual rackspace rackspace LON, SYD, HKG, DFW, ORD, IAD Add your credentials using either: juju add-credential or juju add-credential -f creds.yaml or juju autoload-credentials When specifying just the cloud, juju add-credential will allow a new credential to be added interactively. You will be prompted type the required credential attributes. Example: juju add-credential maas credential name: hmaas replace existing credential? [y/N]: y auth-type: oauth1 maas-oauth: credentials added for cloud maas The new credentials.yaml file at: ~/.local/share/juju/credentials.yaml The autoload tool will search for existing credentials for AWS, OpenStack/Rackspace, and Google clouds. You will then be prompted for which ones you'd like to save. If you have an existing credential.yaml file, you can also import a named credential, eg for MAAS cat credentials.yaml credentials: maas: my-credentials: auth-type: oauth1 maas-oauth: or, for AWS cat credentials.yaml credentials: aws: default-credential: my-credentials my-credentials: auth-type: access-key access-key: secret-key: Bootstrap using your default credentials: juju bootstrap [/region] Examples: juju bootstrap aws-controller aws juju bootstrap mass-controller maas/192.168.0.1 In the MAAS example above, you specify the host address of the MAAS controller. So to use Juju on MAAS out of the box, you set up a credentials file (either interactively, or based on the example above) and then bootstrap. This avoids the need for any cloud configuration. But it's also possible to set up a named MAAS cloud definition as explained later. More details on the new bootstrap experience, including defining private clouds can be found in the New Bootstrap and Cloud Management Experience section. ## What's New in Beta4 * Mongo 3.2 is now used when bootstrapping on Xenial hosts * address-allocation feature flag no longer supported in MAAS provider * prefer-ipv6 setting is now ignored in all providers * MAAS 1.9+ provisioned LXD containers now have a bridge per NIC * Accurate address selection based on spaces (in MAAS) * extra-bindings support for charms metadata * network-get hook tool arguments changed * Juju GUI in the Controller * Juju Now Respects CharmStore Channels ### Mongo 3.2 Support Juju will now use Mongo 3.2 for its database, with the new Wired Tiger storage engine enabled. This is initially only when bootstrapping on Xenial. Trusty and Wily will be supported soon. ### address-allocation feature flag no longer supported in MAAS provider In earlier releases, it was possible to get Juju to use static IP addresses for containers from the same subnet as their host machine, using
