Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update ADOPTERS.md with OpenEBS usage details #2719

Closed
akhilerm opened this issue Aug 22, 2019 · 54 comments
Closed

Update ADOPTERS.md with OpenEBS usage details #2719

akhilerm opened this issue Aug 22, 2019 · 54 comments
Assignees
Labels

Comments

@akhilerm
Copy link
Member

akhilerm commented Aug 22, 2019

OpenEBS Community is working towards becoming a CNCF incubating project. One of the requirements is to add an ADOPTERS.md. The purpose of this issue is to get a list of organizations/individuals who are using OpenEBS to power their persistent storage workloads in Kubernetes.

The idea is to use the information provided in this issue to create the ADOPTERS.md file.

Please comment on this issue with details like:

  • Stateful Applications that you are running on OpenEBS
  • Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?
  • Are you evaluating or already using in development, CI/CD, production
  • Are you using for home use or for your organization
  • A brief description of the use case or details on how OpenEBS is helping your projects.

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.

@tardich
Copy link

tardich commented Aug 26, 2019

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

@proegssilb
Copy link

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.

I'm OK with having my github handle, "proegssilb", attached to to an Adopters.md file.

@gbates101
Copy link

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.

Preferred handle for Adopters.md would be our organization: https://github.com/PlaidCloud

@rgembalik
Copy link

rgembalik commented Aug 28, 2019

Company: CodeWave

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.

@ishantanu
Copy link

Company : Clouds Sky GmbH

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/en/
  3. Twitter ID - cloudsskygmbh

@spectordotan
Copy link

spectordotan commented Sep 3, 2019

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

kmova added a commit to kmova/openebs that referenced this issue Sep 6, 2019
This PR adds the ADOPTERS.md by gathering the details
provided in openebs#2719

Signed-off-by: kmova <[email protected]>
kmova added a commit to kmova/openebs that referenced this issue Sep 6, 2019
This PR adds the ADOPTERS.md by gathering the details
provided in openebs#2719

Signed-off-by: kmova <[email protected]>
kmova added a commit to kmova/openebs that referenced this issue Sep 6, 2019
This PR adds the ADOPTERS.md by gathering the details
provided in openebs#2719

Signed-off-by: kmova <[email protected]>
AmitKumarDas pushed a commit that referenced this issue Sep 7, 2019
* doc(adopters): initial commit for openebs adopters

This PR adds the ADOPTERS.md by gathering the details
provided in #2719

Signed-off-by: kmova <[email protected]>
@pidren
Copy link

pidren commented Sep 13, 2019

Stateful Applications that you are running on OpenEBS

  • Gerrit (multiple flavors), NPM, Maven, Redis, NFS, Sonarqube
  • Various internal tooling requiring stateful storage.

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?

About ~90% cStor, 10% Jiva.

Are you evaluating or already using in development, CI/CD, production

Used in dev, staging, and production clusters.

Are you using for home use or for your organization

For Arista Networks.

A brief description of the use case or details on how OpenEBS is helping your projects.

  • Easy for developers to use: developers don't have to worry beyond choosing the right storageclass and size of storage. Decouples developers from storage integrity and unnecessary details that they shouldn't have to worry about.
  • Withstand cluster disasters: OpenEBS' ability to spread volumes across multiple nodes in a kubernetes cluster as well as automatic recovery of degraded replicas without operator involvement was our highest requirement for a storage solution, and OpenEBS met this perfectly. Rolling upgrades with kubernetes is a breeze thanks OpenEBS, since we only need to maintain quorum and not require all replicas/nodes to be online.
  • Separation of application from storage in terms of physical location: application is entirely decoupled from where the storage is thanks to iSCSI backbone. We can optimize storage nodes vs. nodes serving applications thanks to OpenEBS being built on networked storage.
  • Configurability and ease of deployment: deployment of the entire stack is very easy. As an early adopter, upgrades are a pain point, but I'm pleased to see the team have fixed this in later versions with helm, which is the right thing to do. Configurable NDM and cStor pools that allowed us to have
    extensive custom configurations for our storage nodes vs. application nodes.
  • Doesn't require 139746387243 nodes to operate (exaggeration): compared to Ceph, amount of starting nodes required to operate OpenEBS is incomparably lower/efficient.
  • Uses age old technologies proven to work, rather than unproven solutions: built on iSCSI, ZFS. Standard solutions. No unknown unicorn magic.

@supremedacos
Copy link

Company: Comcast (https://github.com/Comcast)

Stateful Applications that you are running on OpenEBS

  • Prometheus
  • Alertmanager
  • Influxdb
  • Helm Chartmuseum

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?

cStor

Are you evaluating or already using in development, CI/CD, production

Already using in dev and production

Are you using for home use or for your organization

Using for the organization

A brief description of the use case or details on how OpenEBS is helping your projects.

We are currently using openebs as persistent storage for a lot of our monitoring, alerting, and metrics gathering applications (Prometheus, Alertmanager, and Influxdb). We are also using it as the backend storage for helm chartmuseum where we store our custom helm charts used for deployments.

kmova added a commit to kmova/openebs that referenced this issue Sep 21, 2019
Related: openebs#2719

Updated the ADOPTER.md with details from new companies
Also refactor to list using alphabetical order.

Signed-off-by: kmova <[email protected]>
@obeyler
Copy link

obeyler commented Oct 11, 2019

Company:

Orange

Stateful Applications that you are running on OpenEBS

  • Prometheus
  • Alertmanager
  • Chartmuseum
  • Harbor
  • Gitlab
  • Postgresql
  • Redis
  • OpenLdap
  • Rabbit
  • Mysql
  • Minio
  • Metabase
  • Kubeapps
    ...

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?

cStor LocalPV

Are you evaluating or already using in development, CI/CD, production

Already using in dev and next release will be use in production

Are you using for home use or for your organization

Using for the organization

A brief description of the use case or details on how OpenEBS is helping your projects.

 installed on several K8S deployed by bosh. It gives same storageclass on our different iaas (openstack/cloudwatt/vsphere).
The excellent support and responsiveness provided by the OpenEBS team is highly appreciated.

kmova added a commit to kmova/openebs that referenced this issue Oct 31, 2019
Update Adopter.md with the details provided in:
openebs#2719 (comment)

Signed-off-by: kmova <[email protected]>
AmitKumarDas pushed a commit that referenced this issue Oct 31, 2019
Update Adopter.md with the details provided in:
#2719 (comment)

Signed-off-by: kmova <[email protected]>
@github-actions
Copy link

Issues go stale after 30d of inactivity.

@radicand
Copy link

ARM64 cluster in a home-lab setting

Stateful Applications that you are running on OpenEBS

  • Wordpress
  • MariaDB

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV

  • Jiva

Are you evaluating or already using in development, CI/CD, production

  • In "production"

Are you using for home use or for your organization

  • For use in home lab, potential organizational use in the future based on technical needs

A brief description of the use case or details on how OpenEBS is helping your projects.

  • I have a small Raspberry Pi-based Kubernetes cluster (using k3s.io), operating using the official Raspbian 64-bit kernel. My cluster is capable of running arm (32bit) or arm64 containers, and for OpenEBS I'm using the new arm64 images recently published. My home lab setup is small (3 nodes), but they have external storage attached and it's helpful to know that if one node goes down, the pods can safely migrate to another node and be recreated with the same storage.

kmova added a commit to kmova/openebs that referenced this issue Dec 26, 2019
Updated the details provided by the user in the following
comment: openebs#2719 (comment)

Signed-off-by: kmova <[email protected]>
@jggc
Copy link

jggc commented Dec 21, 2021

Company : NationTech

We manage our clients infrastructure and do consulting and development over the full IT and Stoftware Stack

Stateful Applications that you are running on OpenEBS

Anything our clients require but at the moment

  • ElasticSearch
  • Kibana
  • Prometheus
  • Alertmanager
  • Postgresql
  • Docker registry
  • Odoo
  • NextCloud
  • Grafana
  • Django
  • FluentD
  • And some more

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?

ZFS-LocalPV

Are you evaluating or already using in development, CI/CD, production

Using in development and production clusters

Are you using for home use or for your organization

Mainly organization

A brief description of the use case or details on how OpenEBS is helping your projects.

Very easy to set up and get to a production grade setup with proper automation, dashboards and alerts. Best thing about it I think is the transparency. There is nothing about openebs/zfs-localpv that feels like a black box and it's something important for us when we are considering deploying a storage solution.

@github-actions
Copy link

Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.

@RytisLT
Copy link

RytisLT commented Apr 4, 2022

I'm running True NAS Scale with OpenEBS (Local PV) + FluxCD

Stateful Applications that you are running on OpenEBS

  • owncloud
  • jellyfin
  • photoprism
  • filebrowser
  • pyload

Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?

Local PV

Are you evaluating or already using in development, CI/CD, production

evaluating for Home NAS

A brief description of the use case or details on how OpenEBS is helping your projects.

I'm using True NAS Scale with Flux CD to fully describe the desired state of my NAS. OpenEBS + Flux CD allows me to define my applications, their configs and storage needs (ZPool Datasets) in git without needing to interact with True NAS Scale UI. Since the entire state is version controlled disaster recovery should be a cake walk.

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.

Linked In

@github-actions
Copy link

github-actions bot commented Jul 4, 2022

Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.

@cxfcxf
Copy link

cxfcxf commented Jul 9, 2022

Engine: cStor
Applications: Thanos, Prometheus
Future Applications: in house apps
Environment Kind: 2 dev and 2 prod cluster (only on-perm uses it), cloud will get handled by eks

we are trying to move apps to container and eventually using k8s to replace current vm environment
openebs provides a way to handle drives and storage, the way we like since most of our usage requires data integrity

Github: link
Org: Magnite

@nkwangleiGIT
Copy link

1、Stateful Applications that you are running on OpenEBS
Kubevirt, middlewares like MySQL、Redis、Kafka、RabbitMQ、MinIO etc...

2、Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?
hostpath & LVM local PV

3、Are you evaluating or already using in development, CI/CD, production
hostpath for production and development enviroment, LVM for testing and move to production once verified

4、Are you using for home use or for your organization
For both home and organization: TenxCloud, https://www.tenxcloud.com

5、A brief description of the use case or details on how OpenEBS is helping your projects.
Easy to use, active github project
Developed using golang, better for maintainence and community contribution
Use local PV for better performance, and LVM for better isolation

6、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.
organization name: TenxCloud
github id: nkwangleiGIT

@github-actions
Copy link

Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.

@rudolfbyker
Copy link

rudolfbyker commented Aug 1, 2023

  • Stateful Applications that you are running on OpenEBS
    • Drupal
    • Grafana
    • Moodle
    • MariaDB
    • Apache Solr
    • Verdaccio (Private NPM registry)
    • Probably more that I'm forgetting now. All our stateful stuff is on ZFS datasets provisioned by OpenEBS :)
  • Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV?
    • Local ZFS PVs
  • Are you evaluating or already using in development, CI/CD, production
    • Production and development.
  • Are you using for home use or for your organization
  • A brief description of the use case or details on how OpenEBS is helping your projects.
    • This is a super easy way of creating isolated file systems of any size.
    • Instant snapshots are amazing for backups and development (i.e. cloning a large production site instantly and working on that). This requires some fancy custom scripting with kubectl, but it would have been slow or impossible without openebs/zfs-localpv.

@orville-wright
Copy link
Contributor

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests