---
title: Charmhub | Deploy OpenStack Hypervisor using Charmhub - The Open Operator Collection
description: Deploy the latest version of OpenStack Hypervisor on any cloud.
url: https://charmhub.io/openstack-hypervisor/actions
---

# OpenStack Hypervisor

[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")

Platform:

24.04

22.04

2024.1/stable 060d2288

```
juju deploy openstack-hypervisor --channel 2024.1/stable
```

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

* [disable](https://charmhub.io/openstack-hypervisor/actions#disable)
* [enable](https://charmhub.io/openstack-hypervisor/actions#enable)
* [list-flavors](https://charmhub.io/openstack-hypervisor/actions#list-flavors)
* [list-gpus](https://charmhub.io/openstack-hypervisor/actions#list-gpus)
* [list-nics](https://charmhub.io/openstack-hypervisor/actions#list-nics)
* [refresh-snap](https://charmhub.io/openstack-hypervisor/actions#refresh-snap)
* [running-guests](https://charmhub.io/openstack-hypervisor/actions#running-guests)
* [set-hypervisor-local-settings](https://charmhub.io/openstack-hypervisor/actions#set-hypervisor-local-settings)

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

* disable

  Prevent new instances from being created.

  Params

  + reason
    string

    Reason for disabling the hypervisor
* enable

  Allow new instances to be created.
* list-flavors

  List the flavors or compute host capabilities.
* list-gpus

  List host GPUs
* list-nics

  List host NICS, and which one are candidates for use as external NIC.
* refresh-snap

  Refresh the openstack-hypervisor snap to the latest available revision
  on the configured channel. The snap is held after installation to
  prevent automatic refreshes; use this action to apply updates explicitly.
* running-guests

  List the running guests on the hypervisor.

  Only lists guests created by the OpenStack cloud.
* set-hypervisor-local-settings

  Apply settings specific to this hypervisor unit

  Params

  + bridge-mapping
    string

    Space separated list of bridge:physnet:iface mappings. (br-ex:physnet1:ens3 ...)
  + external-nic
    string

    NIC that hypervisor will configure for North/South traffic
  + ip-address
    string

    IP address to use for service configuration
  + ovs-dpdk-ports
    string

    Comma separated list of interface names that will be used with DPDK.

    The interfaces will be bound to the DPDK-compatible driver (vfio-pci by default) and
    corresponding DPDK ports will be created in OVS. Any bridges and bonds that use
    those interfaces will be updated with the resulting DPDK ports, based on the
    MAAS/Netplan configuration.

    The NUMA nodes of those interfaces will be used to determine pinned CPUs
    and huge pages used by OVS.
  + pci-excluded-devices
    string

    A list of PCI addresses that will be excluded from the Nova PCI device whitelist.
    The main purpose of this setting is to accommodate per-node exclusion lists.

    For example, let's say that the user whitelisted all Intel x550 devices and then
    excluded one out of 4 such interfaces:
    pci\_device\_specs = [{"vendor\_id": "8086", "product\_id": "1563"}]
    excluded\_devices = ["0000:1b:00.1"]

    The updated device spec will contain the vendor/product and pci address of the remaining
    3 Intel x550 devies.

    ```
    [
        {"vendor_id": "8086", "product_id": "1563", "address": "0000:19:00.0"},
        {"vendor_id": "8086", "product_id": "1563", "address": "0000:19:00.1"},
        {"vendor_id": "8086", "product_id": "1563", "address": "0000:1b:00.0"},
    ]
    ```

    A device spec that doesn't contain any excluded devices will not be modified.
  + spice-proxy-address
    string

    IP address to use for configuration of SPICE consoles in instances.
