The jujucharms.com interruption has been resolved. Thanks for your patience!
On Tue, Mar 21, 2017 at 2:13 PM, Jeff Pihach
wrote:
> Hi everyone,
>
> We're working on a resolution for those experiencing intermittent service
> interruption with jujucharms.com. This only affects jujucharms.com and
>
Hi everyone,
We're working on a resolution for those experiencing intermittent service
interruption with jujucharms.com. This only affects jujucharms.com and does
not affect Juju CLI operations like creating models and deploying
charms/bundles.
Sorry for the inconvenience.
--
Juju mailing list
J
PS: The in-page links in your README don't work in the charm store because
of this bug: https://github.com/juju/juju-gui/issues/2650
If you want' add a :+1: to that bug so they know I'm not the only one using
such links ;)
PPS: I saw *"By using the Elastisys CharmScaler, you agree to its license
a
The issue I see here is that there is much more momentum behind stuff like
Nagios. It would be great if you could just plug this into existing
monitoring/metrics solutions.
I see the Charm has some Nagios-related config options and relations, is
there some documentation about how this charm integr
On 21 March 2017 at 13:00, Merlijn Sebrechts
wrote:
> Awesome stuff!
>
> Would it make sense to expose the autoscaling options over an
> interface/relationship? So that you can connect the autoscaler to a charm
> and the charm tells the autoscaler how it should be scaled
>
Yea! It would be r
The question there is how different businesses will have different rules. I
think it makes sense for a relation to describe what the charm author
thinks is useful parameters/etc and maybe some default scaling config but I
think that different folks will have different tastes to this. Especially
as
Awesome stuff!
Would it make sense to expose the autoscaling options over an
interface/relationship? So that you can connect the autoscaler to a charm
and the charm tells the autoscaler how it should be scaled
2017-03-20 21:54 GMT+01:00 Simon Kollberg :
>
>
> On 20 March 2017 at 18:13, Char
Jacek, let's talk on the mongodb exporter sometime. I tried to get it
running but was unable to figure out how to get it to talk to the juju
mongodb. All I could get out of it was generic connection errors.
The relation thing you note is interesting. There's talk on the roadmap of
exposing control
Preferring a VPC if there is a single one that exists, even if it isn't
flagged as "default" for a region would probably be reasonable, and
probably not a lot of effort. If there are multiple, I wonder if we could
refuse to bootstrap/add-model unless one is specified.
John
=:->
On Tue, Mar 21, 2
Preferring a VPC if there is a single one that exists, even if it isn't
flagged as "default" for a region would probably be reasonable, and
probably not a lot of effort. If there are multiple, I wonder if we could
refuse to bootstrap/add-model unless one is specified.
John
=:->
On Tue, Mar 21, 2
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
Isn't this spending time on a problem that will tend to disappear (and is
probably already only like 0.1% of the user base)?
Not sure it's worth the effort. Just specify Juju requires a VPC in the
docs, and explain exactly how to fix it (call AWS...) and there you go. No
code, problem solved.
++
12 matches
Mail list logo