Snap package for Nova (Hypervisor)

Go to file

Corey Bryant 7d540c988b Switch to classic confinement Classic confinement drops apparmor/seccomp sandboxing and enables dropping privileges to a regular user when running services. We will continue to store all of the snap's files in $SNAP* directories and $SNAP_COMMON is used as the root directory where setup dirs, templates, and copyfiles are installed. Change-Id: I3d8d2160a2fd6fadae65491fcd4e479b7a6d66b6		2017-04-24 14:30:37 +00:00
snap	Switch to classic confinement	2017-04-24 14:30:37 +00:00
.gitignore	Initial baseline of hypervisor snap	2016-11-24 09:16:50 +00:00
.gitreview	Basic hygene tidy	2016-11-30 10:39:13 +00:00
bindep.txt	Switch to classic confinement	2017-04-24 14:30:37 +00:00
CONTRIBUTING.rst	Basic hygene tidy	2016-11-30 10:39:13 +00:00
LICENSE	Basic hygene tidy	2016-11-30 10:39:13 +00:00
README.md	Fixup misc typos	2016-11-30 10:40:55 +00:00
requirements.txt	Enable use of openvswitch interface now its landed in snapd	2016-12-15 15:07:08 +00:00
snapcraft.yaml	Switch to classic confinement	2017-04-24 14:30:37 +00:00
tox.ini	Switch to classic confinement	2017-04-24 14:30:37 +00:00

README.md

Nova Hypervisor Snap

This repository contains the source code of the snap for the OpenStack Compute service, Nova.

This snap specifically provides the compute and networking hypervisor daemons as part of a snap based OpenStack deployment:

nova-compute
nova-api-metadata (provided for local metadata service use)
neutron-openvswitch-agent
neutron-dhcp-agent
neutron-l3-agent
neutron-metadata-agent

This snap supports use of Libvirt/KVM Nova compute driver + Open vSwitch ML2 Neutron plugin.

Installing this snap

The nova-hypervisor snap can be installed directly from the snap store:

sudo snap install [--edge] --devmode nova-hypervisor

Currently, this snap makes use of libvirt and openvswitch daemons running on the host operating system, so these packages must be installed for a functional hypervisor install:

sudo apt install libvirt-bin qemu-kvm openvswitch-switch

In addition, the libvirt apparmor helper must be placed into complain mode until bug 1644507 is resolved:

sudo aa-complain /usr/lib/libvirt/virt-aa-helper

Configuring Nova and Neutron

Snaps run in an AppArmor and seccomp confined profile, so don't read configuration from /etc/{nova,neutron} on the hosting operating system install.

This snap supports configuration via the $SNAP_COMMON writable area for the snap:

etc/
├── neutron
│   ├── metadata_agent.ini
│   └── plugins
│       └── ml2
│           └── openvswitch_agent.ini
├── neutron.conf.d
│   └── neutron-snap.conf
├── nova
└── nova.conf.d
    ├── glance.conf
    ├── keystone.conf
    ├── neutron.conf
    └── nova-snap.conf

The nova-hypervisor snap can be configured in a few ways.

Firstly the nova daemons will detect and read etc/nova/nova.conf if it exists so you can reuse your existing tooling to write to this file for classic style configuration.

Alternatively the nova daemons will load all configuration files from etc/nova.conf.d - in the above example, glance and neutron configuration are configured using configuration snippets in separate files in etc/nova.conf.d.

Neutron daemons follow the same behaviour; each daemon has its own dedicated configuration file, but will also consume etc/neutron.conf and snippets from etc/neutron.conf.d as well if these are found.

For reference, $SNAP_COMMON is typically located under /var/snap/nova-hypervisor/common.

Restarting services

To restart all services:

sudo systemctl restart snap.nova-hypervisor.*

or restart services individually:

sudo systemctl restart snap.nova-hypervisor.nova-compute

Building this snap

Simply clone this repository and then install and run snapcraft:

git clone https://github.com/openstack-snaps/snap-nova-hypervisor
sudo apt install snapcraft
cd nova
snapcraft

Support

Please report any bugs related to this snap on Launchpad.

Alternatively you can find the OpenStack Snap team in #openstack-snaps on Freenode IRC.