`jhack lobotomy`

[PietroPasotti]

lobotomy command. Helpful when you have to endure an event storm.

Idea: (temporary) disable event processing for a charm. Juju will know nothing, but the charm will ignore all events and be effectively dead.

Usage:

Lobotomy replaces the dispatch script with one that does nothing except put a juju-log that says that the event has been skipped. Lobotomy can be applied and lifted in batches to whole applications o entire models.

[benhoyt]

Interesting idea! A couple of thoughts/questions:

• Can you give an example of when in practice would this be useful? It seems to me that by the time you know you're getting an "event storm" it's probably too late.
• The name is creative but I don't think a good analogy: an actual lobotomy is brutal and irreversible, this is non-destructive and easily reversible. In terms of medical analogies, a "vasectomy" is about stopping the flow of something and is much easier to reverse, but we probably shouldn't go there. :-) I couldn't think of a nice terse way to say "temporary stop the flow of events", but what keeping it boring and self-explanatory and using jhack charm disable-events / jhack charm enable-events?

[PietroPasotti]

storm

in some cases you know that you're about to get an event storm you don't want. For example, you want to remove a charm that has 100 relations, and you don't care about all those broken/departed events, you just want the charm to go.

A user came to me with a juju 2.9->3 migration scenario, where they needed to suspend event processing because model migration apparently involves breaking all cross-model relations and re-creating them on the new juju3 model. And they didn't want that to happen as you 'know' that the new model and the old one will be topologically identical and the events will effectively be for nothing and cause unnecessary workload restarts and downtime.