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 and privacy statement."* at the bottom of your readme. You might want to look at the "terms" feature. https://jujucharms.com/docs/2.1/developer-terms 2017-03-21 14:10 GMT+01:00 Merlijn Sebrechts <merlijn.sebrec...@gmail.com>: > 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 integrates with Nagios? > > 2017-03-21 13:36 GMT+01:00 Simon Kollberg <simon.kollb...@elastisys.com>: > >> >> >> On 21 March 2017 at 13:00, Merlijn Sebrechts <merlijn.sebrec...@gmail.com >> > 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 really good to let developers decide which metrics is >> the most useful to look at when autoscaling their application, especially >> since that is one of the big strengths in Juju - letting the experts give >> you sane defaults. >> >> I've been juggling the idea about integrating the Juju metrics into the >> CharmScaler seeing how that would give the charmers an already existing >> interface to specify their application metrics. However, as it stands right >> now, Juju only collects those metrices every five minutes which obviously >> wouldn't be a sufficient rate for smooth autoscaling. >> >> >>> >>> >>> 2017-03-20 21:54 GMT+01:00 Simon Kollberg <simon.kollb...@elastisys.com> >>> : >>> >>>> >>>> >>>> On 20 March 2017 at 18:13, Charles Butler <charles.but...@canonical.com >>>> > wrote: >>>> >>>>> Greetings, >>>>> >>>>> I realized last week I had completed a review and failed to send an >>>>> update to the mailing list. As some of you may have heard on the Juju Show >>>>> that Elastisys released their Charm Scaler to the promulgated channel. >>>>> >>>>> >>>>> This was an easy +1 from me, with comprehensive test suites, and >>>>> example cases for auto-horizontal-scaling workloads based on CPU load. >>>>> >>>>> https://jujucharms.com/charmscaler/ >>>>> >>>>> >>>> Thanks a lot for the review, Charles! >>>> >>>> We're really looking forward to see the community use our autoscaler to >>>> increase performance and availability for all of the awesome charms out >>>> there and we hope the CharmScaler can become a great addition to the Juju >>>> ecosystem. The CharmScaler is very much in it's infancy when it comes to >>>> functionality but we are planning on extending it with a lot of features >>>> that is already available in the Elastisys platform such as support for >>>> more built-in and custom metrics, smarter scaling-algorithms and >>>> robustness. We also welcome PRs, feature requests and/or bug reports on the >>>> charm's GitHub page https://github.com/elastisys/layer-charmscaler . >>>> >>>> >>>>> This particular charm is near and dear to my own interests, as they >>>>> have published a POC bundle using Canonical Distribution of Kubernetes as >>>>> the subject matter. Enjoy horizontally scaled workers when you reach node >>>>> pressure thresholds on CPU. >>>>> >>>>> https://jujucharms.com/u/elastisys/autoscaled-kubernetes/0 >>>>> >>>> >>>> Seeing how easy Juju makes bundling charms together building and >>>> deploying the autoscaled Kubernetes was a sheer pleasure. To be honest, >>>> what took me the most time was creating a (sort of) nice look for the GUI. >>>> :) However, I think we should go one step further. Rather than having to >>>> create a completely new bundle every time you want to extend a "core" >>>> bundle with one or more charms, why not enable bundles in the bundle >>>> manifests? That way two or more bundles could be combined just like charms. >>>> I know I'm not the first one to bring this up, so if this has already been >>>> requested on the mailing-list excuse this and just count it as a +1! >>>> >>>> >>>>> >>>>> >>>>> Congratulations on your promulgation status to our friends >>>>> at Elastisys! I look forward to seeing the bundles this charm unlocks the >>>>> auto-scaling goodness thanks to tight integration with Juju. >>>>> >>>> >>>> We are very excited to see our charm getting the Juju stamp of >>>> approval! Thanks again. >>>> >>>> >>>>> >>>>> All the best, >>>>> >>>>> Charles >>>>> -- >>>>> Juju Charmer >>>>> Canonical Group Ltd. >>>>> Ubuntu - Linux for human beings | www.ubuntu.com >>>>> conjure-up canonical-kubernetes | jujucharms.com >>>>> >>>>> -- >>>>> Juju mailing list >>>>> Juju@lists.ubuntu.com >>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>>>> an/listinfo/juju >>>>> >>>>> >>>> >>>> -- >>>> Juju mailing list >>>> Juju@lists.ubuntu.com >>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >>>> an/listinfo/juju >>>> >>>> >>> >> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
