Re: killing old dead controllers

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:

Re: killing old dead controllers

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:

killing old dead controllers

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  

killing old dead controllers

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  

Re: Best practice in giving lxd containers routable IP addresses

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. ```

Re: Juju 2.2-rc2 has been released

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

Upgrading juju2

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

Re: Juju 2.2-rc2 has been released

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

Re: Juju 2.2-rc2 has been released

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

Re: Juju 2.2-rc2 has been released

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

Best practice in giving lxd containers routable IP addresses

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

Re: Juju 2.2-rc2 has been released

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:

Re: Juju 2.2-rc2 has been released

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:

Re: Juju 2.2-rc2 has been released

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 <simon.kollb...@elastisys.com > wrote: > conjure-up still seem to be on rc1 > > % sudo snap ins

Re: Juju-dev Digest, Vol 61, Issue 10

n techniques. > > - Menno > -- next part -- > An HTML attachment was scrubbed... > URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/ > 20170612/59c96e86/attachment-0001.html> > > --