All Projects → LINBIT → Drbd

LINBIT / Drbd

Licence: gpl-2.0
LINBIT DRBD kernel module

Programming Languages

c
50402 projects - #5 most used programming language

Projects that are alternatives of or similar to Drbd

neo4j-aws-ha-cluster
Neo4j Enterprise HA Cluster on AWS ECS
Stars: ✭ 13 (-96.69%)
Mutual labels:  high-availability
Appactive
AppActive: A middleware to build an application with multiple active architectures(阿里巴巴开源的一款标准通用且功能强大的构建应用多活架构的开源中间件)
Stars: ✭ 241 (-38.68%)
Mutual labels:  high-availability
Postgresql cluster
PostgreSQL High-Availability Cluster (based on "Patroni" and "DCS(etcd)"). Automating deployment with Ansible.
Stars: ✭ 294 (-25.19%)
Mutual labels:  high-availability
syros
DevOps tool for managing microservices
Stars: ✭ 27 (-93.13%)
Mutual labels:  high-availability
sms
高可用短信微服务
Stars: ✭ 57 (-85.5%)
Mutual labels:  high-availability
Weave
A Reliable and Fault Tolerant RAFT-based Distributed Key Store written in Java.
Stars: ✭ 14 (-96.44%)
Mutual labels:  high-availability
ansible-pihole
Bootstrap a Raspberry Pi with Ansible and install Docker + Pi-hole
Stars: ✭ 52 (-86.77%)
Mutual labels:  high-availability
System Series
📚 服务端开发实践与工程架构,服务端基础篇 | 微服务与云原生篇 | Spring 篇 | Node.js 篇 | DevOps 篇 | 信息安全与渗透测试篇
Stars: ✭ 336 (-14.5%)
Mutual labels:  high-availability
stackstorm-ha
K8s Helm Chart (βeta!) that codifies StackStorm (aka "IFTTT for Ops" https://stackstorm.com/) Highly Availability fleet as a simple to use reproducible infrastructure-as-code app
Stars: ✭ 74 (-81.17%)
Mutual labels:  high-availability
Glusterfs
Gluster Filesystem : Build your distributed storage in minutes
Stars: ✭ 3,437 (+774.55%)
Mutual labels:  high-availability
HAProxy-2-RPM-builder
Build latest HAProxy binary with prometheus metrics support
Stars: ✭ 28 (-92.88%)
Mutual labels:  high-availability
radondb-mysql-kubernetes
Open Source,High Availability Cluster,based on MySQL
Stars: ✭ 146 (-62.85%)
Mutual labels:  high-availability
K8s
Important production-grade Kubernetes Ops Services
Stars: ✭ 253 (-35.62%)
Mutual labels:  high-availability
Gauntlet
🔖 Guides, Articles, Podcasts, Videos and Notes to Build Reliable Large-Scale Distributed Systems.
Stars: ✭ 336 (-14.5%)
Mutual labels:  high-availability
Stolon
PostgreSQL cloud native High Availability and more.
Stars: ✭ 3,481 (+785.75%)
Mutual labels:  high-availability
kube-karp
☸ Add a floating virtual IP to Kubernetes cluster nodes for load balancing easily.
Stars: ✭ 104 (-73.54%)
Mutual labels:  high-availability
socket.io-pubsub
Socket.io adapter for Google Pub/Sub, allowing to setup a socket.io cluster
Stars: ✭ 29 (-92.62%)
Mutual labels:  high-availability
Linstor Server
High Performance Software-Defined Block Storage for container, cloud and virtualisation. Fully integrated with Docker, Kubernetes, Openstack, Proxmox etc.
Stars: ✭ 374 (-4.83%)
Mutual labels:  high-availability
Tarsjava
Java language framework rpc source code implementation
Stars: ✭ 321 (-18.32%)
Mutual labels:  high-availability
Paf
PostgreSQL Automatic Failover: High-Availibility for Postgres, based on Pacemaker and Corosync.
Stars: ✭ 288 (-26.72%)
Mutual labels:  high-availability

DRBD9

This repository contains the Linux kernel code for DRBD9.

DRBD, developed by LINBIT, is a software that allows RAID 1 functionality over TCP/IP and RDMA for GNU/Linux. DRBD is a block device which is designed to build high availability clusters and software defined storage by providing a virtual shared device which keeps disks in nodes synchronised using TCP/IP or RDMA. This simulates RAID 1 but avoids the use of uncommon hardware (shared SCSI buses or Fibre Channel).

Using DRBD

Please read the user-guide provided at docs.linbit.com.

Support

For further products and professional support, please contact us.

Contributing

Development is coordinated via mailing lists. Currently, we do not intend to use github issue tracking/github PRs.

Building DRBD

Since version 9.0.20, DRBD has been using a kernel backwards compatibility system based on Coccinelle semantic patches. While this has many advantages, it also makes it a little harder for "casual" developers to build DRBD from the git sources. The problem is that we require a very recent version of spatch (at least 1.0.8 at time of writing), and most distributions only have relatively old versions in their repositories.

From git

For users wishing to build DRBD from its git sources, here are a few options:

  1. Use a recent kernel. When building against a recent(ish) upstream kernel, chances are you won't even have to use any of the compat features, which means you won't require compatibility patches and in turn don't need spatch installed.
  2. On Ubuntu 18.04 and newer, use a recent spatch version from the Coccinelle PPA. This provides (at time of writing) version 1.0.8, which is recent enough to build DRBD.
  3. Build and install spatch from source. This will also give you a version that is recent enough to build DRBD.

From a release tarball

For use cases where it is appropriate to just build DRBD from a release tarball, here are some options:

  1. Use a distribution kernel and rely on the shipped "compat patch cache". We pre-generate compatibility patches for a list of commonly used distribution kernels and ship them with every release tarball. If your kernel matches one of those in the cache, you won't need spatch because the cached patch will be applied directly.
  2. For all other kernels, you can use LINBIT's "spatch as a service" online service, which transparently and automatically generates compatibility patches based on your kernels feature set.
  3. If you are using an exotic kernel and you do not have internet access or otherwise can't or don't want to use "spatch as a service", you will have to install a recent version of coccinelle (see above).

For a release tarball, these options should be handled transparently for the user. In other words, if you download a tarball and type "make", it should work in next to all cases.

Releases

Releases generated by git tags on github are snapshots of the git repository at the given time. You most likely do not want to use these. They might lack things such as generated man pages, the configure script, and other generated files. If you want to build from a tarball, use the ones provided by us.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].