From: Adam Kliment <adam.kliment@virtualmaster.cz>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] announcing drbd ruby gem
Date: Wed, 16 Feb 2011 11:38:01 +0100 [thread overview]
Message-ID: <4D5BA909.4090206@virtualmaster.cz> (raw)
Hello DRBD developers,
I'd like to present our prototype of drbd gem - ruby wrapper over
drbdadm. Gem is available on rubygems [1] (gem install drbd) and source
is placed on GitHub [2]. Please give as some feedback on GitHub issue
tracker [3]. We will really appreciate all questoins, bug-reports,
feature requests, tips and code reviews or hints for refactoring. Feel
free to fork.
Actually it is by-hand tested on Debian Etch, Ubuntu 8.04 and Ubuntu
9.10 with the single version of DRBD: 8.3.7. We would like to conserve
actual functionality with automated RSpec tests to assure compatibility
for future versions of DRBD. Volunteers, maintainers and tips for this
test suite are welcome! ;-)
Best regards
Adam Kliment
[1] https://rubygems.org/gems/drbd
[2] https://github.com/n1k/drbd
[3] https://github.com/n1k/drbd/issues
--
Virtualmaster
Karla Majera 93
252 31, Všenory
email: info@virtualmaster.cz
jabber: info@virtualmaster.cz
tel: +420.272049092
fax: +420.272048064
web: http://www.virtualmaster.cz
reply other threads:[~2011-02-16 10:58 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=4D5BA909.4090206@virtualmaster.cz \
--to=adam.kliment@virtualmaster.cz \
--cc=drbd-dev@lists.linbit.com \
/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