Comment 3 for bug 1877470

Yeah, Adam helped me clear up my confusion: auto-converge is not a force-completion strategy, it kicks in immediately if allowed.

Perhaps a better UI would be:

  live-migration-strategy:
    type: string
    default: abort
    description: |
      Selects which strategy will be used during live migrations.
      Valid options: abort, auto-converge
      Only used if the deprecated live-migration-permit-post-copy and
      live-migration-permit-auto-converge options are unset
  live-migration-force-completion-strategy:
    type: string
    default: pause
    description: |
      Selects which strategy will be used when migrations are force-completed.
      Valid options: pause, post-copy
      Only used if the deprecated live-migration-permit-post-copy and
      live-migration-permit-auto-converge options are unset
  live-migration-permit-post-copy:
    type: boolean
    default: False
    description: |
      DEPRECATED: use live-migration-force-strategy instead
      If live-migration is enabled, this option allows Nova to switch an on-
      going live migration to post-copy mode.
  live-migration-permit-auto-converge:
    type: boolean
    default: False
    description: |
      DEPRECATED: use live-migration-force-strategy instead
      If live-migration is enabled, this option allows Nova to throttle down
      CPU when an on-going live migration is slow.
      WARNING: auto-converge will only be used if post-copy is disabled

I think the above would make it easier for a user to select how they want standard live migrations to be handled vs how they want force-completions to happen.
If both post-copy and auto-converge are selected the charm should go in a blocked state.