Skip to content

gridcentric/veta

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Veta

Veta is a backup manager for OpenStack, supporting fine-grained backup schedules and retention policies.

Veta supports both regular nova snapshots and Gridcentric VMS live-images as snapshot backends.

Installation

Veta must be installed on API nodes, Horizon nodes (if the Horizon plugin is desired) and on a controller node designated to run the Veta manager.

To install Veta, clone the repository and run:

sudo python setup.py install

Setting up API extensions

You should add the Veta extension to your nova.conf in order to expose the API. You can do so by appending the following lines to nova.conf:

osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
osapi_compute_extension=veta.extension.Veta_extension

Next, you should restart the API server.

sudo restart nova-api

Setting up the manager

If you will be using Keystone authentication for Veta (e.g. if your Glance installation is using Keystone to authenticate requests), you will need to create a service account for Veta:

keystone user-create --name veta --tenant-id <SERVICE TENANT ID> --pass <VETA SERVICE PASSWORD>
keystone user-role-add --user-id <VETA USER ID> --tenant-id <SERVICE TENANT ID> --role-id <ADMIN ROLE ID>

(See the keystone tenant-list and keystone user-role-list commands for help on getting the appropriate <SERVICE TENANT ID> and <ADMIN ROLE ID> parameters.)

You will then need to add the following options to /etc/nova/veta-manager.conf, under the [DEFAULT] section:

[DEFAULT]
veta_auth_strategy=keystone
veta_auth_user=veta
veta_auth_tenant=<SERVICE TENANT NAME>
veta_auth_password=<VETA SERVICE PASSWORD>
veta_auth_url=<KEYSTONE URL> # Defaults to https://127.0.0.1:5000/v2.0

Veta comes with an upstart script for automatically starting on upstart-based systems. To start veta manually, use:

sudo start veta-manager

Setting up the dashboard

Note that the veta novaclient plugin must be installed on the Horizon node(s) in order for the Veta Horizon plugin to work.

To enable the Veta Horizon plugin, modify /etc/openstack-dashboard/local_settings.py (on Ubuntu Server 12.04) or /etc/openstack-dashboard/local_settings (on RHEL 6.4 / CentOS 6.4) and add the following lines:

import sys
mod = sys.modules['openstack_dashboard.settings']
mod.INSTALLED_APPS += ('veta.horizon',)

Then, restart the web server with service apache2 restart and navigate to Horizon. There will be a new panel labeled "Instance Backups".

Setting the Snapshot Driver

To set the backup snapshot driver, you must add the option veta_snapshot_driver to a configuration file that is read by both nova-api and veta-manager, for example the /etc/nova/nova.conf file.

The following drivers are included with Veta:

  • novadriver.NovaSnapshotDriver (default) - uses Nova "snapshots" (i.e. the output of nova image-create for instance backups.
  • cobaltdriver.CobaltSnapshotDriver - uses Cobalt live images for instance backups.

For example, to use the Cobalt driver, append the following to /etc/nova/nova.conf:

veta_snapshot_driver=cobaltdriver.CobaltSnapshotDriver

About

Backup for OpenStack, powered by Gridcentric VMS

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages