New in 2.1-beta5: Prometheus monitoring

[Andrew Wilkins]

Hi folks,

In the release notes there was an innocuous line about introspection
endpoints added to the controller. What this really means is that you can
now monitor Juju controllers with Prometheus. Juju controllers export
metrics, including:
 - API requests (total number and latencies by facade/method, grouped by
error code)
 - numbers of entities (models, users, machines, ...)
 - mgo/txn op counts

We're working on getting the online docs updated. In the mean time, please
refer to https://github.com/juju/docs/issues/1624 for instructions on how
to set up Prometheus to scrape Juju. It would be great to get some early
feedback.

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

Re: Can't push to my own team

[Tom Barber]

Thanks Ryan

Just tried it,  same error.

bugg@tom-laptop2:~/Projects/charms/builds/apache-solr$ charm whoami
User: spicule
Group membership: apachefoundation, apachesoftwarefoundation,
charm-contributors, containers

For whatever reason, it refuses to see the spicule team.


On Tue, Feb 7, 2017 at 12:25 AM, Ryan Beisner 
wrote:

> Hi Tom,
>
> On a rare occasion, I've had to use a slightly larger hammer than
> logout/login, which is to remove (or rename) the following files:
> ~/.go-cookies
> ~/.local/share/juju/store-usso-token
>
> That should force a fresh re-auth.
>
> Cheers,
>
> Ryan
>
>
>
> On Mon, Feb 6, 2017 at 5:38 PM, Tom Barber  wrote:
>
>> Hi folks
>>
>> For whatever reason
>>
>> charm whoami
>>
>> has decided it wont see my own membership of my own LP team even though
>> LP lists me as the owner:
>> https://launchpad.net/~spiculecharms/+members
>>
>> This prevents me pushing charms to the charm store for a reason I can't
>> fathom.
>>
>> I did some work with Cory and did the usual logout and in on
>> jujucharms.com and charm login, but none of them brought my group
>> membership back.
>>
>> So where have I messed up?
>>
>>
>>
>> --
>> Tom Barber
>> CTO Spicule LTD
>> t...@spicule.co.uk
>>
>> http://spicule.co.uk
>>
>> @spiculeim 
>>
>> Schedule a meeting with me 
>>
>> GB: +44(0)5603641316 <+44%2056%200364%201316>
>> US: +18448141689 <(844)%20814-1689>
>>
>> 
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>


-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689


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

Re: Can't push to my own team

[Ryan Beisner]

Hi Tom,

On a rare occasion, I've had to use a slightly larger hammer than
logout/login, which is to remove (or rename) the following files:
~/.go-cookies
~/.local/share/juju/store-usso-token

That should force a fresh re-auth.

Cheers,

Ryan



On Mon, Feb 6, 2017 at 5:38 PM, Tom Barber  wrote:

> Hi folks
>
> For whatever reason
>
> charm whoami
>
> has decided it wont see my own membership of my own LP team even though LP
> lists me as the owner:
> https://launchpad.net/~spiculecharms/+members
>
> This prevents me pushing charms to the charm store for a reason I can't
> fathom.
>
> I did some work with Cory and did the usual logout and in on
> jujucharms.com and charm login, but none of them brought my group
> membership back.
>
> So where have I messed up?
>
>
>
> --
> Tom Barber
> CTO Spicule LTD
> t...@spicule.co.uk
>
> http://spicule.co.uk
>
> @spiculeim 
>
> Schedule a meeting with me 
>
> GB: +44(0)5603641316 <+44%2056%200364%201316>
> US: +18448141689 <(844)%20814-1689>
>
> 
>
> --
> 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-crashdump tool integration & its own repo

[dann frazier]

On Mon, Feb 6, 2017 at 8:00 AM, Cory Johns  wrote:
> A few months ago, Gregory announced the crashdump plugin to the list. [1]
> It's a great tool for debugging charm failures, so we decided to integrate
> it into Matrix [2] and the bundle for doing charm & bundle CI, cwr-ci [3].
> We also plan to integrate it into bundletester, so that all of our testing
> tools can provide a rich set of data to diagnose any test failures.  This
> gives us a standard mechanism for collecting debugging information from a
> Juju deployment.
>
> Because it is now being depended on by several other tools, it made sense to
> break it out from the juju-plugins experimental repo [4] and give it a repo
> of its own.  So, you can now find juju-crashdump at:
>
> https://github.com/juju/juju-crashdump
>
> We're continuing to improve it, and feedback, bugs, contributions, etc. are
> all welcome.

Cory, Thanks for the heads-up. Should I rebase/redirect my existing
PRs, or will those still be processed as-is?

  -dann

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

Re: Create Juju Charms from your browser!

[Cory Johns]

This is really cool!

On Mon, Feb 6, 2017 at 6:34 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Answers in-line.
>
> 2017-02-06 6:36 GMT+01:00 Andrew Wilkins :
>>
>>
>> Very cool, thanks for sharing.
>>
>> A few things which I think would make this even better:
>>  - integration with Ubuntu SSO (or GitHub OAuth, etc.)
>>
>
> This will probably be the most difficult task. Eclipse Che doesn't have
> any authentication mechanism builtin. Each user has to have their own
> Eclipse Che instance. Codenvy is a commercial product based on Eclipse Che
> that has authentication builtin, but it is closed-source.
>
>
>>  - with above: inject macaroon/token into the charmbox container, so that
>> the juju CLI would be automatically logged in (would only work with
>> external identity management)
>>
>
> Yes, that would be awesome! Even without the above, we might be able to do
> it by supplying a token to the Che Charm.
>
>
>>  - with above: Right-click "Deploy to Juju", with detection of changes to
>> deployed code and an option to update.
>>
>>
> YES! The Che team is working on a feature called "smart commands
> ". This will allow us to
> create stuff like a `build charm` action that appears in the right-click
> menu of a layer, a `build charm` command that build the currently selected
> layer, a `deploy charm` command that deploys/updates the charm.
>
> Che's speed of development is really fast, and they seem to be going in a
> direction that will allow us to create deep integration between Juju and
> Che.
>
>
>> ... in case anyone has spare time ;)
>>
>> Cheers,
>> Andrew
>>
>
>
> --
> 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

juju-crashdump tool integration & its own repo

[Cory Johns]

A few months ago, Gregory announced the crashdump plugin to the list. [1]
 It's a great tool for debugging charm failures, so we decided to integrate
it into Matrix [2] and the bundle for doing charm & bundle CI, cwr-ci [3].
We also plan to integrate it into bundletester, so that all of our testing
tools can provide a rich set of data to diagnose any test failures.  This
gives us a standard mechanism for collecting debugging information from a
Juju deployment.

Because it is now being depended on by several other tools, it made sense
to break it out from the juju-plugins experimental repo [4] and give it a
repo of its own.  So, you can now find juju-crashdump at:

https://github.com/juju/juju-crashdump

We're continuing to improve it, and feedback, bugs, contributions, etc. are
all welcome.


[1]: https://lists.ubuntu.com/archives/juju/2016-November/008115.html
[2]: https://lists.ubuntu.com/archives/juju/2016-November/008108.html
[3]: https://lists.ubuntu.com/archives/juju/2016-December/008312.html
[4]: https://github.com/juju/plugins
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Create Juju Charms from your browser!

[Merlijn Sebrechts]

Answers in-line.

2017-02-06 6:36 GMT+01:00 Andrew Wilkins :
>
>
> Very cool, thanks for sharing.
>
> A few things which I think would make this even better:
>  - integration with Ubuntu SSO (or GitHub OAuth, etc.)
>

This will probably be the most difficult task. Eclipse Che doesn't have any
authentication mechanism builtin. Each user has to have their own Eclipse
Che instance. Codenvy is a commercial product based on Eclipse Che that has
authentication builtin, but it is closed-source.


>  - with above: inject macaroon/token into the charmbox container, so that
> the juju CLI would be automatically logged in (would only work with
> external identity management)
>

Yes, that would be awesome! Even without the above, we might be able to do
it by supplying a token to the Che Charm.


>  - with above: Right-click "Deploy to Juju", with detection of changes to
> deployed code and an option to update.
>
>
YES! The Che team is working on a feature called "smart commands
". This will allow us to create
stuff like a `build charm` action that appears in the right-click menu of a
layer, a `build charm` command that build the currently selected layer, a
`deploy charm` command that deploys/updates the charm.

Che's speed of development is really fast, and they seem to be going in a
direction that will allow us to create deep integration between Juju and
Che.


> ... in case anyone has spare time ;)
>
> Cheers,
> Andrew
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju