doc(adopters): initial commit for openebs adopters (openebs#2736)

* doc(adopters): initial commit for openebs adopters This PR adds the ADOPTERS.md by gathering the details provided in openebs#2719 Signed-off-by: kmova <kiran.mova@mayadata.io>
haxorsprogramming · Sep 7, 2019 · ef5a756 · ef5a756
1 parent 70cf316
commit ef5a756
Show file tree

Hide file tree

Showing 7 changed files with 146 additions and 0 deletions.
diff --git a/ADOPTERS.md b/ADOPTERS.md
@@ -0,0 +1,26 @@
+# OpenEBS Adopters
+
+This is the list of organizations and users that publicly shared details of how they are using OpenEBS for running their Stateful workloads.  Please send PRs to add or remove organizations/users.
+
+Note: There are several other organizations/users that couldn’t publicly share their usage details, but are active in the [OpenEBS Slack](https://slack.openebs.io). 
+
+The list of organizations that have publicly shared the usage of OpenEBS:
+
+| Organization | Stateful Workloads | Success Story |
+| :--- | :--- | :--- |
+| [Plaid Cloud](https://github.com/PlaidCloud) | Redis, Prometheus, Elasticsearch, Postgresql | [English](./adopters/plaidcloud/README.md) |
+| [Code Wave](https://codewave.eu/) | Bitwarden, Bookstack, Allegros Ralph, Limesurvey, Grafana, Hackmd/Codimd, Minio, Nextcloud, Percona XtraDB Cluster Operator, Nextcloud, Sonarqube, Sentry, Jupyterhub | [English](./adopters/codewave/README.md) |
+| [Clouds Sky GmbH](https://cloudssky.com/en/) | Confluent Kafka, Strimzi Kafka, Elasticsearch, Prometheus | [English](./adopters/cloudssky/README.md) |
+| [CLEW Medical](https://clewmed.com/) | Postgresql, Keycloak, RabbitMQ | [English](./adopters/clewmedical/README.md) |
+
+
+The list of users that have publicly shared the usage of OpenEBS.
+
+| User | Stateful Workloads | Success Story |
+| :--- | :--- | :--- |
+| [tardich](https://github.com/tardich) | Postfix Mail Relay, NextCloud, Nexus Repository, Plex | [English](./adopters/users/tardich/README.md)  | 
+| [proegssilb](https://github.com/proegssilb) | PostgreSQL, Redis, Factorio (video game server) | [English](./adopters/users/proegssilb/README.md)  | 
+
+
+
+
diff --git a/adopters/clewmedical/README.md b/adopters/clewmedical/README.md
@@ -0,0 +1,11 @@
+**Company:** **[Clew Medical](https://clewmed.com/)**
+
+**OpenEBS storage engine:** Jiva
+
+**Stateful applications:** PostgreSQL, Keycloak, RabbitMQ
+
+**Environment:** Production & Development
+
+**Usage:** Organization
+
+**Why OpenEBS:** Easy to setup, stable, excellent support, active project
diff --git a/adopters/cloudssky/README.md b/adopters/cloudssky/README.md
@@ -0,0 +1,24 @@
+**Company** : **[Clouds Sky GmbH](https://cloudssky.com)**
+
+**Stateful Applications that you are running on OpenEBS**
+1. Confluent Kafka, Strimzi Kafka
+2. Elasticsearch
+3. Prometheus
+
+**Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?**
+1. Mostly Jiva and some cStor
+
+**Are you evaluating or already using in development, CI/CD, production**
+1. Using in development on bare-metal Kubernetes clusters.
+
+**Are you using for home use or for your organization**
+Organization
+
+**A brief description of the use case or details on how OpenEBS is helping your projects.**
+1. Using OpenEBS for Kafka implementations (Confluent as well as Strimzi) on bare-metal Kubernetes clusters.
+2. For most of the statefulsets on bare-metal environments, we are using OpenEBS.
+
+**If you would like your name (as home user) or organization name to be added to the Adopters.md, please provide a preferred contact handle like github id, twitter id, linkedin id, website etc.**
+1. Organization Name: Clouds Sky GmbH
+2. Website - [https://cloudssky.com/](https://cloudssky.com/en/)
+3. Twitter ID - [cloudsskygmbh](https://twitter.com/cloudsskygmbh)
diff --git a/adopters/codewave/README.md b/adopters/codewave/README.md
@@ -0,0 +1,29 @@
+### Company: [CodeWave](https://codewave.eu)
+
+### Storage Engine:
+Jiva. We are planning tests on cStor and might switch to it.
+
+### Number of Applications: 
+varies between 20 and 50 
+
+### Names of the Stateful Applications: 
+The tools we are using or were using with OpenEBS: Bitwarden, Bookstack, Allegros Ralph, LimeSurvey, Grafana, Hackmd/Codimd, MinIO, Nextcloud, Percona XtraDB Cluster Operator, Nextcloud, SonarQube, Sentry, JupyterHub.
+
+### Our products
+Contente - CMS (more like Anything Management System, since it manages much more than just typical web content).
+Synapticall - Callcenter management software with automatic routing, call recording, call transcription, etc.
+
+### CI/CD powered review applications 
+All of the projects we are writing for our customers (e.g. based on our CMS, or on Symfony, or simple static pages, WordPress) have a preview version for each of the feature branches and production-like staging, the last one being always persistent. For those, we are using OpenEBS to keep our data persisted and to move it around the cluster. 
+
+### Cluster Type: 
+Baremetal with some nodes on KVM virtual machines
+
+### For whom 
+CodeWave and all of our current clients we are hosting code/stagings for.
+
+### Any short notes on use cases of why you selected OpenEBS. 
+
+The above applications use OpenEBS mostly for DB persistence (Mysql/Maria/Percona, Postgres, Mongo etc), for live file storage (typical uploads, media etc) and/or for backups. Our internal tools are installed manually and mostly are under manual control, while CI/CD powered deployments (of our products and projects for our clients) are fully automated, with auto PVC provisioning and management. 
+
+We started using OpenEBS over one year ago, mostly because we found it easier to use and a bit more stable on our cluster than it's competition. It's not the only way of supporting persistent apps, but currently, it's most often used in our case and OpenEBS StorageClass serves as our default SC. 
diff --git a/adopters/plaidcloud/README.md b/adopters/plaidcloud/README.md
@@ -0,0 +1,35 @@
+### Company: [Plaid Cloud](https://github.com/PlaidCloud)
+
+### Stateful Applications that we are running on OpenEBS
+
+- Redis
+- Prometheus
+- Elasticsearch
+- PostgreSQL
+- Some home-grown stuff
+
+### Type of OpenEBS Storage Engines behind the above applications
+
+- **cStor** (for "monitoring" apps like Prometheus and Elasticsearch)
+- **Local PV** (for "customer-facing" apps like Redis, Postgresql, and our own)
+
+Initially we used cStor for all of our apps (separated into "fast" and "slow" storage pools), but recently moved our performance-sensitive workloads to use Local PVs.
+
+### Are you evaluating or already using in development, CI/CD, production?
+
+We are in the process of migrating our entire application stack to kubernetes, and so our environments are primarily evaluation. However, we are currently running customer workloads internally on our evaluation cluster, so OpenEBS is being used as close to production as it can be.
+
+### Are you using for home use or for your organization?
+
+We intend to use it in hosting https://plaidcloud.com for our organization once we complete our migration.
+
+### A brief description of the use case or details on how OpenEBS is helping your projects.
+
+Initially we used Portworx, but maintaining an external etcd cluster was troublesome for us and the cost of the setup was a bit excessive for an evaluation. So we evaluated OpenEBS as an alternative and it fit our needs well:
+- Relatively simple to install and configure (especially with recent versions).
+- Supports kubernetes-native operations.
+- Fast (Local PVs have had a noticeable improvement on the performance of our applications).
+- Very active project, good documentation, excellent support.
+
+Definitely happy with OpenEBS so far.
+
diff --git a/adopters/users/proegssilb/README.md b/adopters/users/proegssilb/README.md
@@ -0,0 +1,12 @@
+**Engine:** cStor, might be adding Local PV
+
+**Applications:** PostgreSQL, Redis, Factorio (video game server)
+
+**Future Applications:** NAS, Domain Controller, MinIO, and possibly more.
+
+**Stability:** One Cluster To Rule Them All! (Dev/Prod hybrid, homelab)
+
+**Environment Kind:** Homelab!
+
+OpenEBS is making it easy for me to put storage and compute on the same cheap hardware, and make that storage available to whatever workload might need it. When the lab is done, I expect the cluster to be fairly dense with functionality. Workloads vary between latency-sensitive databases and simple slow-but-reliable file storage.
+
diff --git a/adopters/users/tardich/README.md b/adopters/users/tardich/README.md
@@ -0,0 +1,9 @@
+**OpenEBS storage engine:** cStor
+
+**Stateful applications:** BareOS, Postfix Mail Relay, NextCloud, Nexus Repository, Plex
+
+**Environment:** Production & Development
+
+**Usage:** Home use for now, evaluationg in organization
+
+**Why OpenEBS:** Simplicity of installation, relatively low on resources, excellent support