Juju devel 2.0-beta7 is released

2016-05-13 Thread Curtis Hovey-Canonical 
# Juju 2.0-beta7

A new development release of Juju, juju 2.0-beta7, is now available.
This release replaces version 2.0-beta6.


## Getting Juju

Juju 2.0-beta7 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-beta7

Upgrading environments to 2.0-beta7 is not supported.


## The complete release notes available on the Web

The release notes for Juju 2.0 beta7 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, …
localhost  lxd localhost
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 aws
  credential name: aws-creds
  replace existing credential? [y/N]: y
  auth-type: access-key
  access-key: ABC123ABC123ABC123AB
  secret-key:
credentials added for cloud aws

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 Beta7

* Support for MAAS 2
* The create-model command has been renamed to add-model


## Resolved issues

  * Juju does not support ec2 with no default vpc
Lp 1321442

  * Juju restore-backup does not complete properly
Lp 1569467

  * Juju still vulnerable to cve-2013-2566, cve-2015-2808
Lp 1571457

  * Boot resource 2.0 schema check failed: kflavor: expected string,
got nothing
Lp 1575768

  * Filesystem 2.0 schema check failed: mount_point: expected string,
got nothing
Lp 1575808

  * 'juju create-backup'  fails first on a mongodump dependency then
auth failure
Lp 1576270

  * --sslpemkeypassword parameter must be passed with = on yakkety
Lp 1581284

  * Charm get endpoint is not authenticated
Lp 1499338

  * [joyent] 4k ssh key can not be used: "cannot create credentials:
an error occurred while parsing the key: asn1: structure error:
length too large"

Re: Connecting to the controller database w/mongodb 3.2

2016-05-13 Thread Cheryl Jennings 
The QA team is looking at adding the mongo client into the juju-mongodb3.2
package.  In the meantime, I've been bootstrapping with a trusty controller
if I need to be able to examine the db.

On Fri, May 13, 2016 at 11:17 AM, Horacio Duran  wrote:

> so, for case 1) this link explains how to add the repo
> http://askubuntu.com/questions/724749/install-mongo-3-2-on-ubuntu-15-10
> for 2) following
> https://docs.mongodb.com/manual/reference/connection-string/ should work
>
>
>
> On Fri, May 13, 2016 at 12:57 PM, Casey Marshall <
> casey.marsh...@canonical.com> wrote:
>
>> On Fri, May 13, 2016 at 10:52 AM, Horacio Duran <
>> horacio.du...@canonical.com> wrote:
>>
>>> By connect I assume you mean to use the shell, for this you need the
>>> mongodb-org papa and install mongodb-org-shell, I am currently on the phone
>>> but as soon as I get to a computer I'll send you links
>>>
>>>
>> Well, for use case #1, yes, use the shell.
>>
>> For use case #2, I'd be using github.com/dcu/mongodb_exporter, which
>> uses mgo.v2 and just needs a mongodb URI
>> 
>> .
>>
>>
>>> On Friday, 13 May 2016, Casey Marshall 
>>> wrote:
>>>
 I seem to be unable to connect to the Juju 2.0 controller database
 lately. I'm thinking this might be related to the move to mongodb 3.2.

 Can someone in the know please share how to do this? While most users
 should never, ever connect directly to the controller's database, I have
 two good use cases for it:

 1. It's sometimes necessary for debugging the state of a live
 controller.
 2. I'd like to instrument a controller's mongodb with prometheus.io,
 but in order to do this, I need to derive the new connection info.

 Much thanks,
 Casey

>>>
>>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Connecting to the controller database w/mongodb 3.2

2016-05-13 Thread Horacio Duran 
so, for case 1) this link explains how to add the repo
http://askubuntu.com/questions/724749/install-mongo-3-2-on-ubuntu-15-10
for 2) following
https://docs.mongodb.com/manual/reference/connection-string/ should work



On Fri, May 13, 2016 at 12:57 PM, Casey Marshall <
casey.marsh...@canonical.com> wrote:

> On Fri, May 13, 2016 at 10:52 AM, Horacio Duran <
> horacio.du...@canonical.com> wrote:
>
>> By connect I assume you mean to use the shell, for this you need the
>> mongodb-org papa and install mongodb-org-shell, I am currently on the phone
>> but as soon as I get to a computer I'll send you links
>>
>>
> Well, for use case #1, yes, use the shell.
>
> For use case #2, I'd be using github.com/dcu/mongodb_exporter, which uses
> mgo.v2 and just needs a mongodb URI
> 
> .
>
>
>> On Friday, 13 May 2016, Casey Marshall 
>> wrote:
>>
>>> I seem to be unable to connect to the Juju 2.0 controller database
>>> lately. I'm thinking this might be related to the move to mongodb 3.2.
>>>
>>> Can someone in the know please share how to do this? While most users
>>> should never, ever connect directly to the controller's database, I have
>>> two good use cases for it:
>>>
>>> 1. It's sometimes necessary for debugging the state of a live controller.
>>> 2. I'd like to instrument a controller's mongodb with prometheus.io,
>>> but in order to do this, I need to derive the new connection info.
>>>
>>> Much thanks,
>>> Casey
>>>
>>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Connecting to the controller database w/mongodb 3.2

2016-05-13 Thread Casey Marshall 
On Fri, May 13, 2016 at 10:52 AM, Horacio Duran  wrote:

> By connect I assume you mean to use the shell, for this you need the
> mongodb-org papa and install mongodb-org-shell, I am currently on the phone
> but as soon as I get to a computer I'll send you links
>
>
Well, for use case #1, yes, use the shell.

For use case #2, I'd be using github.com/dcu/mongodb_exporter, which uses
mgo.v2 and just needs a mongodb URI

.


> On Friday, 13 May 2016, Casey Marshall 
> wrote:
>
>> I seem to be unable to connect to the Juju 2.0 controller database
>> lately. I'm thinking this might be related to the move to mongodb 3.2.
>>
>> Can someone in the know please share how to do this? While most users
>> should never, ever connect directly to the controller's database, I have
>> two good use cases for it:
>>
>> 1. It's sometimes necessary for debugging the state of a live controller.
>> 2. I'd like to instrument a controller's mongodb with prometheus.io, but
>> in order to do this, I need to derive the new connection info.
>>
>> Much thanks,
>> Casey
>>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Connecting to the controller database w/mongodb 3.2

2016-05-13 Thread Horacio Duran 
By connect I assume you mean to use the shell, for this you need the
mongodb-org papa and install mongodb-org-shell, I am currently on the phone
but as soon as I get to a computer I'll send you links

On Friday, 13 May 2016, Casey Marshall  wrote:

> I seem to be unable to connect to the Juju 2.0 controller database lately.
> I'm thinking this might be related to the move to mongodb 3.2.
>
> Can someone in the know please share how to do this? While most users
> should never, ever connect directly to the controller's database, I have
> two good use cases for it:
>
> 1. It's sometimes necessary for debugging the state of a live controller.
> 2. I'd like to instrument a controller's mongodb with prometheus.io, but
> in order to do this, I need to derive the new connection info.
>
> Much thanks,
> Casey
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Connecting to the controller database w/mongodb 3.2

2016-05-13 Thread Casey Marshall 
I seem to be unable to connect to the Juju 2.0 controller database lately.
I'm thinking this might be related to the move to mongodb 3.2.

Can someone in the know please share how to do this? While most users
should never, ever connect directly to the controller's database, I have
two good use cases for it:

1. It's sometimes necessary for debugging the state of a live controller.
2. I'd like to instrument a controller's mongodb with prometheus.io, but in
order to do this, I need to derive the new connection info.

Much thanks,
Casey
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev