Ovn Central

Learn about actions >

• cluster-kick

  Request removal of a server from the cluster. This action is equivalent to running "ovn-appctl cluster/kick" command and can be run on any unit connected to the cluster. This action takes ID of a server in southbound or northbound cluster (or both) as an argument. At least one of these arguments must be specified. To get the list of servers (and their IDs) connected to the cluster, user can run "cluster-status" action.

  Params

  • i-really-mean-it boolean

    Confirmation by user to really perform this destructive action

  • nb-server-id ['string', 'number']

    ID of a server to kick from Northbound cluster

  • sb-server-id ['string', 'number']

    ID of a server to kick from Southbound cluster

  Required

  i-really-mean-it

• cluster-status

  Show status of an OVN cluster. Action result will contain two keys, "ovnsb" and "ovnnb", each of these keys will contain yaml structure with data from "ovn-appctl cluster/status" command representing status of Southbound and Northbound clusters. Additional "unit_map" key is included in each cluster status that pairs server IDs of cluster members with unit IDs on which these servers run. In case the action finds servers in cluster that are not associated with any known unit, the "unit_map" will also include key "UNKNOWN" with list of these disassociated servers.

• pause

  Pause services. If the deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must first be paused as well. Not doing so may lead to an interruption of service.

• restart-services

  Restarts services this charm manages.

  Params

  • deferred-only boolean

    Restart all deferred services.

  • run-hooks boolean

    Run any hooks which have been deferred.

  • services string

    List of services to restart.

• resume

  Resume services. If the deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must be resumed as well.

• run-deferred-hooks

  Run deferable hooks and restart services. . NOTE: Service will be restarted as needed irrespective of enable-auto-restarts

• show-deferred-events