Ovn Central

  • By OpenStack Charmers
  • Cloud
Channel Revision Published Runs on
latest/edge 188 23 Apr 2024
Ubuntu 22.04
22.03/stable 204 26 Apr 2024
Ubuntu 22.04 Ubuntu 20.04
openstack-21.09/edge 19 22 Feb 2022
Ubuntu 20.04
openstack-20.12/edge 18 22 Feb 2022
Ubuntu 20.04
openstack-20.03/edge 17 22 Feb 2022
Ubuntu 20.04 Ubuntu 18.04
23.09/stable 196 24 Apr 2024
Ubuntu 23.10
23.03/stable 203 25 Apr 2024
Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04
22.09/stable 200 25 Apr 2024
Ubuntu 22.10 Ubuntu 22.04
21.09/stable 24 05 Aug 2022
Ubuntu 20.04
20.12/stable 30 23 Jan 2023
Ubuntu 20.04
20.03/stable 35 23 Jan 2023
Ubuntu 20.04 Ubuntu 18.04
juju deploy ovn-central --channel latest/edge
Show information

Learn to deploy on juju >

Platform:

Ubuntu
22.04

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