On 18/09/17 17:27, Jacek Nykis wrote:
> Hi Folks,
>
> Could we get cs:~prometheus-charmers/prometheus-alertmanager promulgated?
>
> The code for the charm is
> https://git.launchpad.net/prometheus-alertmanager-charm and there's a
> team that maintains it https:/
Hi Folks,
Could we get cs:~prometheus-charmers/prometheus-alertmanager promulgated?
The code for the charm is
https://git.launchpad.net/prometheus-alertmanager-charm and there's a
team that maintains it https://launchpad.net/~prometheus-charmers. That
team already maintains a number of other pro
On 20/03/17 18:04, Rick Harding wrote:
> During The Juju Show #8 [1] last week we talked about how to setup your
> controllers to be provide metrics through Prometheus to Grafana to keep
> an eye on those controllers in production.
>
> I put together a blog post [2] about how to set it up, config
On 07/02/17 02:25, Andrew Wilkins wrote:
> 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:
>
On 21/11/16 23:26, Menno Smits wrote:
> On 18 November 2016 at 05:07, Nate Finch wrote:
>
>> Resources are also stored in mongo and can be unlimited in size (not much
>> different than fat charms, except that at least they're only pulled down on
>> demand).
>>
>> We should let admins configure th
On 17/11/16 08:20, Uros Jovanovic wrote:
> Hi all,
>
> I'd like to start a discussion on how to handle storage issues on
> controller machines, especially what we can do when storage is getting 95%
> or even 98% full. There are many processes that are storing data, we have
> at least:
> - charms a
On 19/10/16 16:15, Marco Ceppi wrote:
>> 2. Don't colocate units if at all possible. In separate containers on the
>> same machine, sure. But there's absolutely no guarantee that colocated
>> units won't conflict with each other. What you're asking about is the very
>> problem colocation causes.
On 01/04/16 14:34, Mark Shuttleworth wrote:
>
>> * cli for storage is not as nice as other juju commands. For example we
>> have the in the docs:
>>
>> juju deploy cs:~axwalk/postgresql --storage data=ebs-ssd,10G pg-ssd
>>
>> I suspect most charms will use single storage device so it may be
>> pos
On 19/03/16 03:20, Andrew Wilkins wrote:
> It seems like the issues you've noted below are all documentation issues,
> rather than limitations in the implementation. Please correct me if I'm
> wrong.
>
>
>> If we come up with sensible defaults for different providers we could
>> make end users' e
On 08/03/16 23:51, Mark Shuttleworth wrote:
> *Storage*
>
> * shared filesystems (NFS, GlusterFS, CephFS, LXD bind-mounts)
> * object storage abstraction (probably just mapping to S3-compatible APIS)
>
> I'm interested in feedback on the operations aspects of storage. For
> example, whether it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/05/14 06:06, Sameer Zeidat wrote:
> Hello,
>
> I've created a couple of charms that I deploy to both MAAS and
> hpcloud environments.
>
> I added a second network interface, eth1, to some of my MAAS nodes
> and now unit-get private-address retu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/14 21:01, Andreas Hasenack wrote:
> On Tue, Apr 1, 2014 at 4:07 PM, Jorge O. Castro
> wrote:
>> Hi everyone,
>>
>> Matt Bruzek and I have been doing some charm testing on a machine
>> that does not have general access to the internet. So cha
12 matches
Mail list logo
