---
title: Charmhub | Deploy Nova Cloud Controller using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of Nova Cloud Controller on any cloud.
url: https://charmhub.io/nova-cloud-controller/actions
---

# Nova Cloud Controller

[OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

* [OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")
* [Cloud](https://charmhub.io/?filter=cloud)

Platform:

24.04

23.10

23.04

22.10

22.04

20.04

18.04

14.04

12.04

yoga/stable 882

```
juju deploy nova-cloud-controller --channel yoga/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

* [archive-data](https://charmhub.io/nova-cloud-controller/actions#archive-data)
* [clear-unit-knownhost-cache](https://charmhub.io/nova-cloud-controller/actions#clear-unit-knownhost-cache)
* [openstack-upgrade](https://charmhub.io/nova-cloud-controller/actions#openstack-upgrade)
* [pause](https://charmhub.io/nova-cloud-controller/actions#pause)
* [purge-data](https://charmhub.io/nova-cloud-controller/actions#purge-data)
* [resume](https://charmhub.io/nova-cloud-controller/actions#resume)
* [security-checklist](https://charmhub.io/nova-cloud-controller/actions#security-checklist)
* [sync-compute-availability-zones](https://charmhub.io/nova-cloud-controller/actions#sync-compute-availability-zones)

[Learn about actions >](https://juju.is/docs/juju/action)

* archive-data

  Run job to archive deleted rows in database

  Params

  + batch-size
    integer
* clear-unit-knownhost-cache

  Clear the knownhost cache for (default) all the units, a service, or a
  single unit.
  .
  The default is all units. If the 'target' param has an '/' in it, then it
  is assumed ot be a single unit. If no '/' is present, then all the units
  in a service will be refreshed.
  .
  e.g. target="nova-compute/4" will just clear the nova-compute/4 unit (in
  the 'nova-compute' application), whereas target='nova-compute' will refresh
  all of the units in the 'nova-compute' application.
  .
  The action triggers a refresh resolution of the known hosts for the unit,
  which then populates the cache, updates the knownhosts file for the
  associated service (e.g. 'nova-compute'), and, importantly, sets the
  relation data for that associated service with the new knownhosts file.
  This may cause a 'cloud-compute' relation changed hook on the associated
  nova-compute units if the hosts have changed.
  .
  This action still functions even if the 'cache-known-hosts' config value is
  not set; caching of hosts occurs regardless of that setting, and so this
  action can be used to force an update if DNS has changed in the system, or
  for a particular host (although this scenario is unlikely).

  Params

  + target
    string
* openstack-upgrade

  Perform openstack upgrades. Config option action-managed-upgrade must be
  set to True.
* pause

  Pause the nova-cloud-controller unit. This action will stop related
  services.
* purge-data

  Run job to purge stale soft deleted rows in database

  Params

  + before
    string

    Delete data from all shadow tables that is older than the date provided.
    Date strings may be fuzzy, such as `Oct 21 2015`.
* resume

  Resume the nova-cloud-controller unit. This action will start related
  services.
* security-checklist

  Validate the running configuration against the OpenStack security guides
  checklist
* sync-compute-availability-zones

  Update Nova host aggregates to match the availability zone defined in the
  related nova-compute units. This action will create any missing host
  aggregates in Nova and add hypervisors to the appropriate host aggregates.
  This action will not remove any hypervisors from host aggregates already
  configured in nova.
  .
  This action requires that the nova-cloud-controller application be fully
  related to keystone. This action will fail if the Nova API is unavailable.
  Successful completion of this action will report a list of each hypervisor
  added to an availability zone. Successful completion with no output means
  that all hypervisors were associated with their host aggregates.
  .
  This action is only available for OpenStack Stein and newer.