https://github.com/opennebula/addon-drbdmanage
DRBD Manage Storage Driver for OpenNebula
https://github.com/opennebula/addon-drbdmanage
Last synced: 10 months ago
JSON representation
DRBD Manage Storage Driver for OpenNebula
- Host: GitHub
- URL: https://github.com/opennebula/addon-drbdmanage
- Owner: OpenNebula
- License: other
- Created: 2016-03-15T11:13:02.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2017-08-09T22:44:03.000Z (almost 9 years ago)
- Last Synced: 2025-04-04T07:41:27.908Z (about 1 year ago)
- Language: Shell
- Homepage:
- Size: 225 KB
- Stars: 8
- Watchers: 5
- Forks: 6
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# DRBD Manage Storage Driver
## Description
This driver allows for highly available storage using DRBD9 + DRBD Manage in
OpenNebula.
## Development
To contribute bug patches or new features, you can use the github Pull Request
model. It is assumed that code and documentation are contributed under the
Apache License 2.0.
Support for this addon can be found at the
[OpenNebula user forum](https://forum.opennebula.org/c/support) or the
[DRBD-User](http://lists.linbit.com/listinfo/drbd-user) mailing list.
## Authors
Hayley Swimelar [](hayley@linbit.com)
## Compatibility
* This addon is compatible with OpenNebula versions up to 5.0.2
* It was tested with versions 4.14 and 5.0.2
* This version of README.md describes the installation process for ONE 5.0.2 environments
* This is intended for use as an images datastore for use with an NFS system datastore
## Requirements
* DRBD9 9.0.0+
* DRBD Manage 0.99.2+
## Features
* quickly attaches images to VMs
* fast image clones
* transfers images over the network in diskless mode
## Limitations
* snapshots of images are not available
* this driver does not support the ssh system datastore
## Installation
Follow these steps on the Front-End node only.
### Clone the Repository and Run the Install Script.
Run the following commands as either oneadmin or root:
```bash
git clone git://git.linbit.com/addon-drbdmanage.git && cd addon-drbdmanage
chmod u+x install.sh
./install.sh
```
### Upgrading
To upgrade the driver, simply run the installation script again.
## Configuration
### Configure the Driver in OpenNebula
Modify the following sections of `/etc/one/oned.conf`
Add drbdmanage to the list of drivers in the `TM_MAD` and `DATASTORE_MAD`
sections:
```
TM_MAD = [
executable = "one_tm",
arguments = "-t 15 -d dummy,lvm,shared,fs_lvm,qcow2,ssh,vmfs,ceph,drbdmanage"
]
```
```
DATASTORE_MAD = [
EXECUTABLE = "one_datastore",
ARGUMENTS = "-t 15 -d dummy,fs,lvm,ceph,dev,iscsi_libvirt,vcenter,drbdmanage -s shared,ssh,ceph,fs_lvm,qcow2"
```
Add new TM_MAD_CONF and DS_MAD_CONF sections:
```
TM_MAD_CONF = [
name = "drbdmanage", ln_target = "NONE", clone_target = "SELF", shared = "yes"
]
```
```
DS_MAD_CONF = [
NAME = "drbdmanage", REQUIRED_ATTRS = "BRIDGE_LIST", PERSISTENT_ONLY = "NO",
MARKETPLACE_ACTIONS = "export"
]
```
After making these changes, restart the opennebula service.
### Configuring the Nodes
#### Overview of node Roles
The Front-End node issues commands to the Storage and Host nodes via DRBD
Manage.
Storage nodes hold disk images of VMs locally.
Host nodes are responsible for running instantiated VMs and typically have the
storage for the images they need attached across the network via DRBD Manage
diskless mode.
All nodes must have DRBD9 and DRBD Manage installed. This process is detailed in the
[User's Guide for DRBD9](http://docs.linbit.com/doc/users-guide-90/ch-admin-drbdmanage/)
It is possible to have Front-End and Host nodes act as storage nodes in
addition to their primary role as long as they the meet all the requirements
for both roles.
If you do not intend for the Front-End or Host nodes to be used as storage
nodes in addition to their primary role, they should be added to the DRBD
Manage cluster as
[pure controller nodes](http://docs.linbit.com/doc/users-guide-90/s-dm-add-node/#_adding_a_pure_controller_node).
#### Front-End Configuration
The Front-End node must be a control node with it's own copy of the control
volume, this means that you must provide a small, approximately 4Gb, volume
for the drbdpool volume group, even if you do not plan to use this node for
DRBD storage.
#### Host Configuration
The Host nodes may also be configured as
[pure client nodes](http://docs.linbit.com/doc/users-guide-90/s-dm-add-node/#_adding_a_pure_client_node)
without a local control volume by adding the `--satellite` option while adding
the node the the DRBD Manage cluster. This allows hosts to be added without
preparing local storage for DRBD on that node.
#### Storage Node Configuration
Only the Front-End and Host nodes require OpenNebula to be installed, but the
oneadmin user must be able to passwordlessly access storage nodes. Refer to
the OpenNebula install guide for your distribution on how to manually
configure the oneadmin user account.
The Storage nodes must use one of the storage plugins that support snapshots,
this means one of the thin LVM plugins or ZFS. The merits of the different
plugins are discussed in the
[User's Guide](http://docs.linbit.com/doc/users-guide-90/s-drbdmanage-storage-plugins/#_discussion_of_the_storage_plugins).
In this example preparation of thinly-provisioned storage using LVM for DRBD
Manage, you must create a volume group and thinLV using LVM on each storage
node.
Example of this process using two physical volumes (/dev/sdX and /dev/sdY) and
the default names for the volume group and thinpool. Make sure to set the thinLV's
metadata volume to a reasonable size, once it becomes full it can be difficult to resize:
```bash
pvcreate /dev/sdX /dev/sdY
vgcreate drbdpool /dev/sdX /dev/sdY
lvcreate -l 95%VG --poolmetadatasize 8g -T /dev/drbdpool/drbdthinpool
```
Instructions on how to configure DRBD Manage to use a storage plugin can be
found in the cluster configuration section of the
[User's Guide](http://docs.linbit.com/doc/users-guide-90/s-drbdmanage-storage-plugins/).
### Additonal Driver Configuration
Additional configuration for the driver can be found in the
`datastore/drbdmanage.conf` file in the driver director or in the install path,
normally `/var/lib/one/remotes/datastore/drbdmanage/drbdmanage.conf`
### Permissions for Oneadmin
The oneadmin user must have passwordless sudo access to the `drbdmanage` program on the Front-End node
```bash
oneadmin ALL=(root) NOPASSWD: /usr/bin/drbdmanage
```
and the `mkfs` command on the Storage nodes
```bash
oneadmin ALL=(root) NOPASSWD: /sbin/mkfs
```
A policy section for the oneadmin user must also be added in
`/etc/dbus-1/system.d/org.drbd.drbdmanaged.conf` on the Front-End node. Be
sure to leave the original policy section intact!
```
```
#### Groups
Be sure to consider the groups that oneadmin should be added to in order to
gain access to the devices and programs needed to access storage and
instantiate VMs. For this addon, the oneadmin user must belong to the `disk`
group on all nodes in order to access the DRBD devices where images are held.
```bash
usermod -a -G disk oneadmin
```
### Creating a New DRBD Manage Datastore
Create a datastore configuration file named ds.conf and use the `onedatastore`
tool to create a new datastore based on that configuration. There are two
mutually exclusive deployment options: DRBD_REDUNDANCY and
DRBD_DEPLOYMENT_NODES. For both of these options, BRIDGE_LIST must be a space
separated list of all storage nodes in the DRBD Manage cluster.
#### Deploying to a Redundancy Level
The DRBD_REDUNDANCY option takes a level of redundancy which is a number between
one and the total number of storage nodes. Resources are assigned to storage
nodes automatically based on the level of redundancy and DRBD Manage's
deployment policy. The following example shows a cluster with three storage
nodes that will deploy new resources to two of the nodes in the BRIDGE_LIST
based on the free space available on the storage nodes.
```bash
cat >ds.conf <ds.conf <ds.conf <