Re: Orchestration charms

2017-01-16 Thread Mark Shuttleworth
On 11/01/17 07:03, Casey Marshall wrote: > > On Mon, Jan 9, 2017 at 11:53 AM, Simon Kollberg > mailto:simon.kollb...@elastisys.com>> > wrote: > > Right now, the user needs to manually provide credentials (via the > charm > config) to the CharmScaler enabling it to connect and execute >

Re: Orchestration charms

2017-01-11 Thread Casey Marshall
Hi Simon, I'm glad you asked about this. The need for certain services to operate on the controller for autoscaling and other purposes has come up before. Juju's considering exposing different aspects of the controller as applications -- for monitoring, log access and other aspects of operating th

Orchestration charms

2017-01-09 Thread Simon Kollberg
Hello Juju people! I'm currently working on a charm with a some what special characteristics. We call it the CharmScaler. The purpose of the charm is to automatically scale the number of units of a charm depending on the current usage of the application. Much like the autoscaling in Kubernetes and