sysconfig
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 149 | 08 Sep 2025 | |
| latest/stable | 148 | 08 Sep 2025 | |
| latest/stable | 147 | 08 Sep 2025 | |
| latest/stable | 146 | 08 Sep 2025 | |
| latest/stable | 145 | 08 Sep 2025 | |
| latest/stable | 144 | 08 Sep 2025 | |
| latest/stable | 143 | 08 Sep 2025 | |
| latest/stable | 142 | 08 Sep 2025 | |
| latest/stable | 141 | 08 Sep 2025 | |
| latest/stable | 140 | 08 Sep 2025 | |
| latest/stable | 139 | 08 Sep 2025 | |
| latest/stable | 138 | 08 Sep 2025 | |
| latest/stable | 69 | 13 Dec 2024 | |
| latest/stable | 15 | 31 Aug 2022 | |
| latest/stable | 6 | 18 Oct 2021 | |
| latest/candidate | 149 | 26 Aug 2025 | |
| latest/candidate | 148 | 26 Aug 2025 | |
| latest/candidate | 147 | 26 Aug 2025 | |
| latest/candidate | 146 | 26 Aug 2025 | |
| latest/candidate | 145 | 26 Aug 2025 | |
| latest/candidate | 144 | 26 Aug 2025 | |
| latest/candidate | 143 | 26 Aug 2025 | |
| latest/candidate | 142 | 26 Aug 2025 | |
| latest/candidate | 141 | 26 Aug 2025 | |
| latest/candidate | 140 | 26 Aug 2025 | |
| latest/candidate | 139 | 26 Aug 2025 | |
| latest/candidate | 138 | 26 Aug 2025 | |
| latest/candidate | 6 | 18 Oct 2021 | |
| latest/edge | 161 | 08 Sep 2025 | |
| latest/edge | 160 | 08 Sep 2025 | |
| latest/edge | 159 | 08 Sep 2025 | |
| latest/edge | 158 | 08 Sep 2025 | |
| latest/edge | 157 | 08 Sep 2025 | |
| latest/edge | 156 | 08 Sep 2025 | |
| latest/edge | 155 | 08 Sep 2025 | |
| latest/edge | 154 | 08 Sep 2025 | |
| latest/edge | 153 | 08 Sep 2025 | |
| latest/edge | 152 | 08 Sep 2025 | |
| latest/edge | 151 | 08 Sep 2025 | |
| latest/edge | 150 | 08 Sep 2025 | |
| latest/edge | 69 | 02 Jan 2025 | |
| latest/edge | 6 | 02 Jan 2025 |
juju deploy sysconfig
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Tutorial: Get started
The sysconfig charm is a subordinate charm, designed to be deployed alongside any primary machine charm where you wish to tweak some system parameters. The parameters are controlled by the charm’s configuration. See configuration for a reference of what is supported.
For this tutorial, let’s consider the contrived case where you have a workload running, let’s say nova-compute:
$ juju status nova-compute
...
App Version Status Scale Charm Channel Rev Exposed Message
nova-compute 25.2.1 active 2 nova-compute yoga/stable 723 no Unit is ready
ovn-chassis 22.03.3 active 2 ovn-chassis 22.03/stable 222 no Unit is ready
Unit Workload Agent Machine Public address Ports Message
nova-compute/0* active idle 8 10.5.0.247 Unit is ready
ovn-chassis/0* active idle 10.5.0.247 Unit is ready
And you have determined that performance could be improved by changing the cpu governor to performance, however the machines have defaulted to ondemand. Here you can deploy sysconfig, relate it to nova-compute (through the juju-info endpoint), and configure sysconfig to set the cpu governor as desired:
$ juju deploy sysconfig
$ juju relate sysconfig nova-compute
$ juju config sysconfig governor=performance
Now sysconfig has been deployed and is alongside nova-compute:
$ juju status nova-compute
...
App Version Status Scale Charm Channel Rev Exposed Message
nova-compute 25.2.1 active 2 nova-compute yoga/stable 723 no Unit is ready
ovn-chassis 22.03.3 active 2 ovn-chassis 22.03/stable 222 no Unit is ready
sysconfig active 2 sysconfig stable 33 no ready
Unit Workload Agent Machine Public address Ports Message
nova-compute/0* active idle 8 10.5.0.247 Unit is ready
ovn-chassis/0* active idle 10.5.0.247 Unit is ready
sysconfig/0* active idle 10.5.0.247 ready