From: Andy Grover <agrover@redhat.com>
To: nab@risingtidesystems.com
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
"Patil, Kiran" <kiran.patil@intel.com>,
"Love, Robert W" <robert.w.love@intel.com>,
Madhu Iyengar <madhu.iyengar@qlogic.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
Jerome Martin <jxm@risingtidesystems.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
"J.H." <warthog9@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Matthew Wilcox <matthew@wil.cx>,
Stefan Hajnoczi <stefanha@gmail.com>,
linux-iscsi-target-dev <linux-iscsi-target-dev@googlegroups.com>,
linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Boaz Harrosh <bharrosh@panasas.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Fleischmann <mwf@risingtidesystems.com>
Subject: Re: rtsadmin-v1.99 BETA packages
Date: Tue, 17 May 2011 10:12:00 -0700 [thread overview]
Message-ID: <4DD2AC60.6010506@redhat.com> (raw)
In-Reply-To: <1305617458.2856.139.camel@haakon2.linux-iscsi.org>
On 05/17/2011 12:30 AM, Nicholas A. Bellinger wrote:
> So to clarify here. We intend to keep everything related to single
> target management for rtslib/configshell/rtsadmin available under AGPLv3
> on http://www.risingtidesystems.com/git/ This currently includes:
>
> *) high level single node management, libs, and docs for target core
> *) high level single node management, libs, and docs for fabrics using
> the mainline target_core_fabric_config.c framework.
> *) configshell python library and docs
> *) Ability to build rpm/deb source packages with necessary dependecies
>
> Our commerical versions will include a number of integrated features to
> complement single node target core/fabric management, along with
> allowing rtsadmin-v2 to function in a larger multi-node cluster
> environment.
>
> To the question of contributing code to the AGPLv3 licensed community
> edition of rtslib/configshell/rtsadmin, we are doing a dual licensing
> model like MySQL. Please feel free to contact Marc directly with
> specific questions that you may have wrt to licensing for our python
> code.
Thanks for the clarification.
Regards -- Andy
next prev parent reply other threads:[~2011-05-17 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1304121705.14278.196.camel@haakon2.linux-iscsi.org>
[not found] ` <1304553788.10072.241.camel@haakon2.linux-iscsi.org>
2011-05-11 16:59 ` rtsadmin-v1.99 BETA packages Andy Grover
2011-05-11 17:36 ` mwf
2011-05-12 0:30 ` Nicholas A. Bellinger
2011-05-12 1:26 ` Andy Grover
2011-05-12 1:56 ` Nicholas A. Bellinger
2011-05-14 1:41 ` Nicholas A. Bellinger
2011-05-14 23:36 ` Andy Grover
2011-05-17 7:30 ` Nicholas A. Bellinger
2011-05-17 17:12 ` Andy Grover [this message]
[not found] ` <BANLkTikmp8LdCt2CcpJ21feL8x6=ODGMHQ@mail.gmail.com>
2011-05-17 17:12 ` Andy Grover
2011-07-26 10:29 ` Sangale Harshada Vijay
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=4DD2AC60.6010506@redhat.com \
--to=agrover@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=jxm@risingtidesystems.com \
--cc=kiran.patil@intel.com \
--cc=linux-iscsi-target-dev@googlegroups.com \
--cc=linux-scsi@vger.kernel.org \
--cc=madhu.iyengar@qlogic.com \
--cc=matthew@wil.cx \
--cc=michaelc@cs.wisc.edu \
--cc=mwf@risingtidesystems.com \
--cc=nab@risingtidesystems.com \
--cc=pbonzini@redhat.com \
--cc=robert.w.love@intel.com \
--cc=stefanha@gmail.com \
--cc=warthog9@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.