date:20170612

Re: killing old dead controllers

2017-06-12 Thread John Meinel

If the machines are just gone (you manually destroyed them via 'lxc
stop/delete'). You can just do:
 juju unregister lxd-test

It will remove it from the local registry without trying to tear anything
down.

John
=:->


On Tue, Jun 13, 2017 at 8:17 AM, Daniel Bidwell  wrote:

> I have a machine with 2 dead controllers that I can't figure out how to
> delete.  A "juju controllers" produces the following:
>
> root@juju:~# juju controllers
> Use --refresh flag with this command to see the latest information.
>
> Controller  ModelUser   Access Cloud/Region
>   Models  MachinesHA  Version
> lxd-test-admin  superuser  lxd/localhost
>2 1  none  2.0.2
> test-lxd*   default  admin  superuser  localhost/
> localhost   2 1  none  2.1.3
>
> lxc list produces:
>
> root@juju:~# lxc list
> +--+---+--+--+--+---+
> | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
> +--+---+--+--+--+---+
>
> Any attemtp to remove, delete, kill, or destroy results in the command
> hanging and never coming back.  I have been trying to develop some
> local charms using lxd.  I know that this kind of testing and
> developemnt is hard on vms/containers, but throwing away the vm and
> reinstalling ubuntu is probably not the desired behaviour.
> --
> Daniel Bidwell 
>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

killing old dead controllers

2017-06-12 Thread Daniel Bidwell

I have a machine with 2 dead controllers that I can't figure out how to
delete.  A "juju controllers" produces the following:

root@juju:~# juju controllers
Use --refresh flag with this command to see the latest information.

Controller  ModelUser   Access Cloud/Region Models  Machines
HA  Version
lxd-test-admin  superuser  lxd/localhost 2 1  
none  2.0.2  
test-lxd*   default  admin  superuser  localhost/localhost   2 1  
none  2.1.3

lxc list produces:

root@juju:~# lxc list
+--+---+--+--+--+---+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+--+---+--+--+--+---+

Any attemtp to remove, delete, kill, or destroy results in the command
hanging and never coming back.  I have been trying to develop some
local charms using lxd.  I know that this kind of testing and
developemnt is hard on vms/containers, but throwing away the vm and
reinstalling ubuntu is probably not the desired behaviour.
-- 
Daniel Bidwell 


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

Re: Best practice in giving lxd containers routable IP addresses

2017-06-12 Thread Jeff Pihach

Hi Daniel,

When going through the network setup for lxd as outlined[0] in the
"Walkthrough of network configuration" section. You can set the "Bridge
interface name" to the primary interface on the host. Your lxc profile
should look as follows, where "br0" is the interface name of the host.

```
$ lxc profile show default
config: {}
description: Default LXD profile
devices:
  eth0:
name: eth0
nictype: bridged
parent: br0
type: nic
name: default
```

Now whenever I create new containers they are assigned an IP on the
network. You'll then want to add your ssh-key to the authorized_keys on the
container to be able to ssh in.

Hope this helps!

[0] https://jujucharms.com/docs/stable/tut-lxd

On Mon, Jun 12, 2017 at 10:08 AM, Daniel Bidwell 
wrote:

> What is the best practice in giving lxd containers routable IP
> addresses?  I would like to treat the containers as regular vm's for
> production, not as non-routable devops machines.  Is there a document
> somewhere show how to configure this?
> --
> Daniel Bidwell 
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.2-rc2 has been released

2017-06-12 Thread Nicholas Skaggs

Yes, and this too has been corrected. You should expect releases to flow 
down to level of risk. So, when 2.2 releases, beta, candidate and stable 
will all point to the 2.2 revision (until the first beta for 2.3, and so 
on).

channels:
  latest/stable:2.1.3  (1922) 24MB classic
  latest/candidate: 2.2-rc2(1929) 25MB classic
  latest/beta:  2.2-rc2(1929) 25MB classic
  latest/edge:  2.3-alpha1+develop-1cb9c09 (1933) 42MB classic

Nicholas

On 06/12/2017 12:17 PM, Jason Hobbs wrote:

Nicholas,

Thanks.  beta is still 2.2rc1.  Should it be 2.2rc2 also?

Jason

On Mon, Jun 12, 2017 at 11:15 AM, Nicholas Skaggs 
mailto:nicholas.ska...@canonical.com>> 
wrote:

Thanks for the heads-up Jason. Yes, small snafu with publishing
the builds. Edge builds are tracking develop (2.3-alpha1) and now
are being published again.

Nicholas

On 06/12/2017 11:18 AM, Jason Hobbs wrote:

I noticed that for the juju snap, edge and beta channels have
older releases than candidate.  Shouldn't they always be at
least the same version as candidate, if not newer?

  stable:2.1.3   (1922) 24MB classic
  candidate: 2.2-rc2 (1929) 25MB classic
  beta:  2.2-rc1 (1925) 25MB classic
  edge:  2.2-rc1+develop-7256fe0 (1915) 44MB classic

Thanks,
Jason

On Fri, Jun 9, 2017 at 6:25 AM, Chris Lee
mailto:chris@canonical.com>
>> wrote:

# Juju 2.2-rc2 Release Notes

We are delighted to announce the release of Juju and
conjure-up
2.2-rc2! In this release, Juju greatly improves memory and
storage
consumption, works on KVM containers, and improves network
modelling. conjure-up now supports Juju as a Service (JAAS),
provides a MacOS client, and adds support for repeatable spell
deployments.

The best way to get your hands on this release of Juju and
conjure-up is to install them via snap packages (see
https://snapcraft.io/for more info on snaps).

   snap install juju --classic --candidate

snap install conjure-up --classic --candidate

Other packages are available for a variety of platforms.
Please
see the online documentation at
https://jujucharms.com/docs/devel/reference-releases#development

>

Please note that if you are upgrading an existing controller,
please make sure there is at least 6G of free disk space. The
upgrade step for the logs can take a while, in the
vicinity of 10
or more minutes if the current logs collection is at its
maximum size.

Since 2.2-rc1

## New and Improved

Better support credential management in the Azure provider

* support autoload-credentials and juju add-credential in the
azure provider when Azure CLI is installed.

(this removes the requirement that the user discover their
subscription ID before creating credentials)

Rate limit login and connection requests to the
controller(s) on
busy systems.

## Fixes

Fix issue where status history logs were not pruned:

https://bugs.launchpad.net/juju/+bug/1696491

>

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

>

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

Upgrading juju2

2017-06-12 Thread Mario Splivalo

Hi, ladies and lads!

I am verifying the juju upgrade procedure and I ran into some
‘misunderstandings’ which I’m hoping could be clarified out here.

I am running juju 2.0.0 and the plan is to upgrade it to the latest 2.1
version, which is currently 2.1.3.

This is the procedure I followed:

I innstalled 2.0.2 from xenial-updates  and bootstrapped a 2.0.0 controller:

$ juju bootstrap stsstack RegionOne --agent-version=2.0.0

After that I deployed some services (e.g. juju deploy mongodb -n3), and
after all of that got settled down I started the upgrade:

$ juju upgrade-juju -m controller

I expected to upgraded to latest 2.0 version, which is 2.0.4. Instead, I
got this:


ubuntu@juju-2-0:~$ juju upgrade-juju -m controller
no prepackaged tools available, using local agent binary 2.0.2.1
started upgrade to 2.0.2.1


After that I upgraded my local client to the latest available versions
from ppa:juju/stable:

$ juju --version
2.1.3-xenial-amd64

I then run ‘juju upgrade-juju’, and I again got the ‘no prepackaged
toools’ message:

ubuntu@juju-2-0:~$ juju upgrade-juju  -m controller
no prepackaged tools available, using local agent binary 2.1.3.1
started upgrade to 2.1.3.1


So, my questions are:

- what does ‘no prepackaged tools available’ means?

- why I got upgraded to 2.0.2.1? (I can’t find 2.0.2.1 in simplestreams;
I’m assuming that I haven’t got upgraded to 2.0.4 because my client
version is 2.0.2, but where did this 2.0.2.1 came from?

- same for 2.3.1 - why I got upgraded to 2.3.1.1?

- when I do ‘upgrade-juju -m controller’ again, I get upgraded to
2.0.2.2, 2.0.2.3, 2.0.2.4, and so on. The jujud’s in /var/lib/juju/tools
are all the same. Is this a juju 2.0 bug?

- Also, when I download 2.1.3 agent from simplestreams
(http://streams.canonical.com/juju/tools/agent/2.1.3/juju-2.1.3-ubuntu-amd64.tgz),
the jujud binaries are not the same: http://paste.ubuntu.com/24841752/



Thank you in advance,

Mario

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

Re: Juju 2.2-rc2 has been released

2017-06-12 Thread Jason Hobbs

Nicholas,

Thanks.  beta is still 2.2rc1.  Should it be 2.2rc2 also?

Jason

On Mon, Jun 12, 2017 at 11:15 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:

> Thanks for the heads-up Jason. Yes, small snafu with publishing the
> builds. Edge builds are tracking develop (2.3-alpha1) and now are being
> published again.
>
> Nicholas
>
> On 06/12/2017 11:18 AM, Jason Hobbs wrote:
>
>> I noticed that for the juju snap, edge and beta channels have older
>> releases than candidate.  Shouldn't they always be at least the same
>> version as candidate, if not newer?
>>
>>   stable:2.1.3   (1922) 24MB classic
>>   candidate: 2.2-rc2 (1929) 25MB classic
>>   beta:  2.2-rc1 (1925) 25MB classic
>>   edge:  2.2-rc1+develop-7256fe0 (1915) 44MB classic
>>
>> Thanks,
>> Jason
>>
>> On Fri, Jun 9, 2017 at 6:25 AM, Chris Lee > > wrote:
>>
>> # Juju 2.2-rc2 Release Notes
>>
>> We are delighted to announce the release of Juju and conjure-up
>> 2.2-rc2! In this release, Juju greatly improves memory and storage
>> consumption, works on KVM containers, and improves network
>> modelling. conjure-up now supports Juju as a Service (JAAS),
>> provides a MacOS client, and adds support for repeatable spell
>> deployments.
>>
>> The best way to get your hands on this release of Juju and
>> conjure-up is to install them via snap packages (see
>> https://snapcraft.io/for more info on snaps).
>>
>>snap install juju --classic --candidate
>>
>> snap install conjure-up --classic --candidate
>>
>> Other packages are available for a variety of platforms. Please
>> see the online documentation at
>> https://jujucharms.com/docs/devel/reference-releases#development
>> 
>>
>> Please note that if you are upgrading an existing controller,
>> please make sure there is at least 6G of free disk space. The
>> upgrade step for the logs can take a while, in the vicinity of 10
>> or more minutes if the current logs collection is at its maximum size.
>>
>> Since 2.2-rc1
>>
>> ## New and Improved
>>
>> 
>> 
>>
>> Better support credential management in the Azure provider
>>
>> * support autoload-credentials and juju add-credential in the
>> azure provider when Azure CLI is installed.
>>
>> (this removes the requirement that the user discover their
>> subscription ID before creating credentials)
>>
>> Rate limit login and connection requests to the controller(s) on
>> busy systems.
>>
>> ## Fixes
>>
>> 
>> 
>>
>> Fix issue where status history logs were not pruned:
>>
>> https://bugs.launchpad.net/juju/+bug/1696491
>> 
>>
>>
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com 
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>> 
>>
>>
>>
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.2-rc2 has been released

2017-06-12 Thread Nicholas Skaggs

Thanks for the heads-up Jason. Yes, small snafu with publishing the 
builds. Edge builds are tracking develop (2.3-alpha1) and now are being 
published again.


Nicholas

On 06/12/2017 11:18 AM, Jason Hobbs wrote:
I noticed that for the juju snap, edge and beta channels have older 
releases than candidate.  Shouldn't they always be at least the same 
version as candidate, if not newer?


  stable:2.1.3   (1922) 24MB classic
  candidate: 2.2-rc2 (1929) 25MB classic
  beta:  2.2-rc1 (1925) 25MB classic
  edge:  2.2-rc1+develop-7256fe0 (1915) 44MB classic

Thanks,
Jason

On Fri, Jun 9, 2017 at 6:25 AM, Chris Lee > wrote:


# Juju 2.2-rc2 Release Notes

We are delighted to announce the release of Juju and conjure-up
2.2-rc2! In this release, Juju greatly improves memory and storage
consumption, works on KVM containers, and improves network
modelling. conjure-up now supports Juju as a Service (JAAS),
provides a MacOS client, and adds support for repeatable spell
deployments.

The best way to get your hands on this release of Juju and
conjure-up is to install them via snap packages (see
https://snapcraft.io/for more info on snaps).

   snap install juju --classic --candidate

snap install conjure-up --classic --candidate

Other packages are available for a variety of platforms. Please
see the online documentation at
https://jujucharms.com/docs/devel/reference-releases#development


Please note that if you are upgrading an existing controller,
please make sure there is at least 6G of free disk space. The
upgrade step for the logs can take a while, in the vicinity of 10
or more minutes if the current logs collection is at its maximum size.

Since 2.2-rc1

## New and Improved



Better support credential management in the Azure provider

* support autoload-credentials and juju add-credential in the
azure provider when Azure CLI is installed.

(this removes the requirement that the user discover their
subscription ID before creating credentials)

Rate limit login and connection requests to the controller(s) on
busy systems.

## Fixes



Fix issue where status history logs were not pruned:

https://bugs.launchpad.net/juju/+bug/1696491




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








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

Best practice in giving lxd containers routable IP addresses

2017-06-12 Thread Daniel Bidwell

What is the best practice in giving lxd containers routable IP
addresses?  I would like to treat the containers as regular vm's for
production, not as non-routable devops machines.  Is there a document
somewhere show how to configure this?
-- 
Daniel Bidwell 


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

Re: Juju 2.2-rc2 has been released

2017-06-12 Thread Jason Hobbs

I noticed that for the juju snap, edge and beta channels have older
releases than candidate.  Shouldn't they always be at least the same
version as candidate, if not newer?

  stable:2.1.3   (1922) 24MB classic
  candidate: 2.2-rc2 (1929) 25MB classic
  beta:  2.2-rc1 (1925) 25MB classic
  edge:  2.2-rc1+develop-7256fe0 (1915) 44MB classic

Thanks,
Jason

On Fri, Jun 9, 2017 at 6:25 AM, Chris Lee  wrote:

> # Juju 2.2-rc2 Release Notes
>
>
>
> We are delighted to announce the release of Juju and conjure-up 2.2-rc2!
> In this release, Juju greatly improves memory and storage consumption,
> works on KVM containers, and improves network modelling. conjure-up now
> supports Juju as a Service (JAAS), provides a MacOS client, and adds
> support for repeatable spell deployments.
>
>
>
> The best way to get your hands on this release of Juju and conjure-up is
> to install them via snap packages (see https://snapcraft.io/ for more
> info on snaps).
>
>
>
> snap install juju --classic --candidate
>
> snap install conjure-up --classic --candidate
>
>
>
> Other packages are available for a variety of platforms. Please see the
> online documentation at https://jujucharms.com/docs/
> devel/reference-releases#development
>
>
>
> Please note that if you are upgrading an existing controller, please make
> sure there is at least 6G of free disk space. The upgrade step for the logs
> can take a while, in the vicinity of 10 or more minutes if the current logs
> collection is at its maximum size.
>
>
>
> Since 2.2-rc1
>
>
> ## New and Improved
>
> --
>
>
>
> Better support credential management in the Azure provider
>
> * support autoload-credentials and juju add-credential in the azure
> provider when Azure CLI is installed.
>
> (this removes the requirement that the user discover their subscription ID
> before creating credentials)
>
>
>
> Rate limit login and connection requests to the controller(s) on busy
> systems.
>
>
>
> ## Fixes
>
> --
>
>
>
> Fix issue where status history logs were not pruned:
>
>   https://bugs.launchpad.net/juju/+bug/1696491
>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.2-rc2 has been released

2017-06-12 Thread Cory Johns

Simon,

That was my mistake, I forgot to click release on that.
 conjure-up-rc2-20170612 is now available on the candidate channel.

On Fri, Jun 9, 2017 at 8:06 PM, Simon Kollberg  wrote:

> conjure-up still seem to be on rc1
>
> % sudo snap install conjure-up --classic --candidate
> conjure-up (candidate) 2.2-rc1-20170606.0106 from 'canonical' installed
> % juju --version
> 2.2-rc1-xenial-amd64
> % conjure-up --version
> conjure-up 2.2-rc1
> % sudo snap remove conjure-up
> conjure-up removed
> % sudo snap install juju --classic --candidate
> juju (candidate) 2.2-rc2 from 'canonical' installed
> % juju --version
> 2.2-rc2-xenial-amd64
>
> On 9 June 2017 at 13:25, Chris Lee  wrote:
>
>> # Juju 2.2-rc2 Release Notes
>>
>>
>>
>> We are delighted to announce the release of Juju and conjure-up 2.2-rc2!
>> In this release, Juju greatly improves memory and storage consumption,
>> works on KVM containers, and improves network modelling. conjure-up now
>> supports Juju as a Service (JAAS), provides a MacOS client, and adds
>> support for repeatable spell deployments.
>>
>>
>>
>> The best way to get your hands on this release of Juju and conjure-up is
>> to install them via snap packages (see https://snapcraft.io/ for more
>> info on snaps).
>>
>>
>>
>> snap install juju --classic --candidate
>>
>> snap install conjure-up --classic --candidate
>>
>>
>>
>> Other packages are available for a variety of platforms. Please see the
>> online documentation at https://jujucharms.com/docs/de
>> vel/reference-releases#development
>>
>>
>>
>> Please note that if you are upgrading an existing controller, please make
>> sure there is at least 6G of free disk space. The upgrade step for the logs
>> can take a while, in the vicinity of 10 or more minutes if the current logs
>> collection is at its maximum size.
>>
>>
>>
>> Since 2.2-rc1
>>
>>
>> ## New and Improved
>>
>> --
>>
>>
>>
>> Better support credential management in the Azure provider
>>
>> * support autoload-credentials and juju add-credential in the azure
>> provider when Azure CLI is installed.
>>
>> (this removes the requirement that the user discover their subscription
>> ID before creating credentials)
>>
>>
>>
>> Rate limit login and connection requests to the controller(s) on busy
>> systems.
>>
>>
>>
>> ## Fixes
>>
>> --
>>
>>
>>
>> Fix issue where status history logs were not pruned:
>>
>>   https://bugs.launchpad.net/juju/+bug/1696491
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: killing old dead controllers

killing old dead controllers

Re: Best practice in giving lxd containers routable IP addresses

Re: Juju 2.2-rc2 has been released

Upgrading juju2

Re: Juju 2.2-rc2 has been released

Re: Juju 2.2-rc2 has been released

Best practice in giving lxd containers routable IP addresses

Re: Juju 2.2-rc2 has been released

Re: Juju 2.2-rc2 has been released

10 matches

Site Navigation

Mail list logo

Footer information