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 AWS.
To do this the charm utilizes the newly created Juju Python library. Just like you can control your own deployment with the Juju client, the CharmScaler is able to do operations on the controller it has access to. Giving charms privileges like this really opens up a whole new world of possibilities where in charms will be able to orchestrate other charms in numerous ways not possible before. Right now, the user needs to manually provide credentials (via the charm config) to the CharmScaler enabling it to connect and execute operations on the Juju controller. What I would love to see is a way to make certain charms have special access - some kind of "orchestrator charm privilege" where the necessary credentials needed by the python lib would be passed to the charm automagically. I really have the feeling having this kind of "orchestrator charm" functionality in Juju would benefit the community greatly. Though, I do think it should be something more ingrained in Juju itself rather than making developers come up with their own tricks to provide the charms with credentials. Let me know what you think! - Simon
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
