This snap is designed to be used with a deployed OpenStack Control plane such as delivered by Sunbeam.
Getting Started
To get started with the OpenStack Hypervisor, install the snap using snapd:
$ sudo snap install openstack-hypervisor
The snap needs to be configured with credentials and URL's for the Identity service of the OpenStack cloud that it will form part of - for example:
$ sudo snap set openstack-hypervisor \
identity.auth_url=http://10.64.140.43:80/sunbeam-keystone \
identity.username=nova-hypervisor-01 \
identity.password=supersecure21
it's also possible to configure domain and project configuration.
The snap also needs to be configured with access to RabbitMQ:
$ sudo snap set openstack-hypervisor \
rabbitmq.url=rabbit://nova:supersecure22@10.152.183.212:5672/openstack
and with URL's for access to Network services:
$ sudo snap set openstack-hypervisor \
network.ovn-sb-connection=tcp:10.152.183.220:6642
The snap has numerous other configuration options - see "Configuration Reference" for full details.
Configuration Reference
compute
Configuration of options related to compute (Nova):
compute.virt-type
libvirt Virtualization typeThis option is runtime detected by the snap and will be set
to kvm
if the host is capable of full virtualization or qemu
if not.
compute.cpu-mode
(host-model
) CPU mode for instancesValid values: host-model
, host-passthrough
, custom
, none
.
compute.cpu-models
CPU models for hypervisorAn ordered list of CPU models the host supports.
Only used with compute.cpu-mode
is set to custom
.
For more details please refer to the Nova [configuration reference](https://docs.openstack.org/nova/latest/admin/cpu-models.html) for cpu models.
compute.spice-proxy-address
(localhost
) IP address for SPICE consolesIP address to use for configuration of SPICE consoles in instances.
identity
Configuration of options related to identity (Keystone):
identity.auth-url
Full URL for Keystone APIidentity.username
Username for services to useidentity.password
Password for services to useidentity.user-domain-name
(service_domain
) Domain for useridentity.project-name
(services
) Service projectidentity.project-domain-name
(service_domain
) Domain for service projectidentity.region-name
(RegionOne
) OpenStack region to uselogging
Configuration of logging options across all services:
logging.debug
(false
) Enable debug log levelnode
Configuration of options related to the hypervisor node in general:
node.fqdn
(hostname -f
) Fully qualified hostname for nodenode.ip-address
IP address to use for service configurationThese options are use to configure the identity of the agents that run as part of the snap.
network
Configuration of options related to networking, including Neutron and OVN:
network.dns-domain
DNS domain name to use for networking
network.dns-servers
External DNS servers to use for forwarding DNS requests
network.external-bridge
(br-ex
) Name of OVS external network bridge
network.physnet-name
(physnet1
) Neutron label for physical network
network.ip-address
(node.ip-address
) IP address to use for overlay network endpoints
network.ovn-sb-connection
(tcp:127.0.0.1:6642
) OVN Southbound DB connection URL
network.enable-gateway
(False) Enable OVS/OVS as north/south gateway
TLS configuration for OVN can also be supplied via snap configuration:
network.ovn-key
Private TLS keynetwork.ovn-cert
TLS certificate for ovn-key
network.ovn-cacert
CA certificate (and chain) for certificate validationAll of the above options must be provided as base64 encoded strings.
rabbitmq
Configuration of options related to RabbitMQ messaging:
rabbitmq.url
(rabbit://localhost:5672
) Full connection URL to RabbitMQThank you for your report. Information you provided will help us investigate further.
There was an error while sending your report. Please try again later.
You are about to open
Do you wish to proceed?
Snaps are applications packaged with all their dependencies to run on all popular Linux distributions from a single build. They update automatically and roll back gracefully.
Snaps are discoverable and installable from the Snap Store, an app store with an audience of millions.
On Arch Linux, snap can be installed from the Arch User Repository (AUR). The manual build process is the Arch-supported install method for AUR packages, and you’ll need the prerequisites installed before you can install any AUR package. You can then install snap with the following:
git clone https://aur.archlinux.org/snapd.git
cd snapd
makepkg -si
Once installed, the systemd unit that manages the main snap communication socket needs to be enabled:
sudo systemctl enable --now snapd.socket
If AppArmor is enabled in your system, enable the service which loads AppArmor profiles for snaps:
sudo systemctl enable --now snapd.apparmor.service
To enable classic snap support, enter the following to create a symbolic link between /var/lib/snapd/snap
and /snap
:
sudo ln -s /var/lib/snapd/snap /snap
Either log out and back in again, or restart your system, to ensure snap’s paths are updated correctly.
To install openstack-hypervisor, simply use the following command:
sudo snap install openstack-hypervisor
Browse and find snaps from the convenience of your desktop using the snap store snap.
Interested to find out more about snaps? Want to publish your own application? Visit snapcraft.io now.