Comment 2 for bug 2025724

Hi @manadart, yes. We've been discussing how to use juju's leadership to actually manage the workload leadership.

I think one example is to manage the VIP.
Originally, we'd use pacemaker + corosync. That means the charm leader will often be a different unit than the VIP owner.
Another example would the DB primaries.

The goal is to give the charms more control to actually request the charm leadership when they detect something has changed / needs to change on the workload side.
So, in this case, if the VIP needs to move (e.g. a restart of the workload owning the VIP will cause to lose it), then we'd also move the charm leader to the same unit.

That way, in a quick glance, juju status would tell you who is the leader.