All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lenz Grimmer <lenz@grimmer.com>
To: linux-btrfs@vger.kernel.org
Subject: Managing storage (incl. Btrfs) on Linux with openATTIC
Date: Fri, 10 Jun 2016 12:54:17 +0200 (CEST)	[thread overview]
Message-ID: <1026941351.8013.1465556057388@office.mailbox.org> (raw)

Hi there,

if you're using Btrfs on Linux for file serving purposes, i'd like to invite you to take a look at our open source storage management project "openATTIC":

  http://openattic.org/

We provide a web UI and RESTful API to create CIFS/NFS shares on top of Btrfs and other file systems, including monitoring and snapshots. Other file systems like ext4, XFS or ZFS are supported, too. We also support sharing block volumes via iSCSI and Fibre Channel via LIO and are currently working on adding Ceph Management and Monitoring support as well.

openATTIC 2.0 is currently in development and we're looking for more testers and feedback. Packages for the Debian/Ubuntu, RHEL/CentOS and SUSE are available via apt/yum repos.

For the time being, we don't yet support all the nifty Btrfs features (e.g. RAID levels), but you can already use openATTIC to manage (e.g. creating and snapshotting) and monitor Btrfs file systems via the WebUI. We plan to further extend the Btrfs functionality incrementally with each release. Some use cases we have in mind are documented here: https://wiki.openattic.org/display/OP/openATTIC+Storage+Management+Use+Cases

So if you're looking for a free (GPLv2) storage management tool that supports your favorite file system, we'd be glad if you give openATTIC a try!

Thanks and sorry for the noise,

Lenz
-- 
 Lenz Grimmer <lenz@grimmer.com> - http://www.lenzg.net/

                 reply	other threads:[~2016-06-10 10:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1026941351.8013.1465556057388@office.mailbox.org \
    --to=lenz@grimmer.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.