From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Possibility of a BTRFS module for Ansible.
Date: Thu, 19 Nov 2015 12:50:45 -0500 [thread overview]
Message-ID: <564E0BF5.1030302@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
I recently started using Ansible for orchestrating updates, backups, and
other similar stuff. Working with BTRFS with it has gotten annoying
really fast due to some of the hoops I have to jump through to get the
btrfs command to work in a way that the shell and command modules in
Ansible expect (it would be really nice to have an option for subv
delete that would work like rm -f). Because of this, I'm looking at
writing a module for BTRFS management (ZFS has one, why shouldn't we?),
but I wanted to check here first to see if:
1. Anybody may have already started working on this (in which case, I'd
love to help).
2. Anybody here actually uses Ansible and could help with testing
(module inclusion requires testing by a third party).
3. Anyone had any suggestion as to what might be worthwhile to include.
At a minimum, I'm looking at supporting scrub, balance, defrag,
subvolume creation/removal/snapshotting, and probably send/receive.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
reply other threads:[~2015-11-19 17:51 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=564E0BF5.1030302@gmail.com \
--to=ahferroin7@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox