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

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-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

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 
> 
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-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: 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-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: 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-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: Juju-dev Digest, Vol 61, Issue 10

2017-06-12 Thread James Beedy 
Menno - Nice!

On performance monitoring, I always thought it would be interesting to see
what insight an APM might give. I've tried building Juju with the newrelic
APM agent a few times and had no luck (novice GO programmer here). I have
been playing around with the newrelic APM quite a bit with a few of our own
application stacks internally, and it has been producing great information
to our teams on how our apps perform in various areas.

* High level service map (part of the APM) that shows a few of our apps and
their external dependencies http://imgur.com/a/vmj2n

* Snip of digging into db query time http://imgur.com/a/HczPX

* Snip of web transaction tab http://imgur.com/a/Vp05q

I think it would be really cool to see a service map, and transaction
metrics similar to ^, for a juju controller and agents.

~James

On Mon, Jun 12, 2017 at 5:00 AM, <juju-dev-requ...@lists.ubuntu.com> wrote:

> Send Juju-dev mailing list submissions to
> juju-dev@lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> or, via email, send a message with subject or body 'help' to
> juju-dev-requ...@lists.ubuntu.com
>
> You can reach the person managing the list at
> juju-dev-ow...@lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Juju-dev digest..."
>
>
> Today's Topics:
>
>1. Debugging MongoDB performance issues (Menno Smits)
>
>
> --
>
> Message: 1
> Date: Mon, 12 Jun 2017 15:39:16 +1200
> From: Menno Smits <menno.sm...@canonical.com>
> To: juju-dev <juju-dev@lists.ubuntu.com>
> Subject: Debugging MongoDB performance issues
> Message-ID:
> <CALBC4VCKt4RF-WhGm4FbrF_VTro7TPZa7DFXsSG63vKBfpvyoQ@
> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi everyone,
>
> I started writing an email to a few Juju developers with tips on diagnosing
> MongoDB performance issues but then realised that this would be more useful
> as a wiki page.
>
> https://github.com/juju/juju/wiki/Diagnosing-MongoDB-Performance
>
> Feel free to expand and add your own techniques.
>
> - Menno
> -- next part --
> An HTML attachment was scrubbed...
> URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/
> 20170612/59c96e86/attachment-0001.html>
>
> --
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
> End of Juju-dev Digest, Vol 61, Issue 10
> 
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev