From: "Loke, Chetan" <Chetan.Loke@netscout.com> To: "Tom Coughlan" <coughlan@redhat.com>, "Hannes Reinecke" <hare@suse.de>, <tasleson@redhat.com> Cc: <Shyam_Iyer@Dell.com>, <vgoyal@redhat.com>, <rwheeler@redhat.com>, <linux-fsdevel@vger.kernel.org>, <linux-scsi@vger.kernel.org> Subject: RE: [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Date: Thu, 19 Jan 2012 11:17:30 -0500 [thread overview] Message-ID: <D3F292ADF945FB49B35E96C94C2061B9159134BD@nsmail.netscout.com> (raw) In-Reply-To: <1326113987.2580.8.camel@localhost.localdomain> > From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Tom Coughlan > > Yes, Red Hat does. Tony Asleson. libStorageMgmt: > > http://sourceforge.net/apps/trac/libstoragemgmt > > The current focus is on managing external storage (SMI-S, etc.). This > focus can be expanded over time. Contributions welcome. > Device management(scalability/feature mgmt) - 1) scalability: I may be wrong but storage boxes like symmetrix(and others) support large number of LUNs. So device management 'scalability' will make linux shine. By scalability I mean efficiently managing let's say 32K(?) LUNs. 2) feature management: As Shyam mentioned in earlier emails - provide an ecosystem similar to smart-phones. Let me provide an example(and then you guys can correct me by saying this already exists or bits and pieces exist): a) As a kernel developer - export all the features(to the upper layers) we can by querying the target. b) As an app developer - GetLUNFeatures(), could return - {Thin Provision, RAID-level, ... ). c) As a sys-admin - If I right click(for a volume/LUN) on my management GUI, I should be able to tell if my volume supports thin-prov, backed by DRBD[proxy?] etc. So once we provide b) from above, tens(if not hundreds) of apps will be developed in a short period of time. I feel libstoragemgmt is an excellent place to get all of this organized. Chetan Loke
WARNING: multiple messages have this Message-ID (diff)
From: "Loke, Chetan" <Chetan.Loke@netscout.com> To: Tom Coughlan <coughlan@redhat.com>, Hannes Reinecke <hare@suse.de>, tasleson@redhat.com Cc: Shyam_Iyer@Dell.com, vgoyal@redhat.com, rwheeler@redhat.com, linux-fsdevel@vger.kernel.org, linux-scsi@vger.kernel.org Subject: RE: [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Date: Thu, 19 Jan 2012 11:17:30 -0500 [thread overview] Message-ID: <D3F292ADF945FB49B35E96C94C2061B9159134BD@nsmail.netscout.com> (raw) In-Reply-To: <1326113987.2580.8.camel@localhost.localdomain> > From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Tom Coughlan > > Yes, Red Hat does. Tony Asleson. libStorageMgmt: > > http://sourceforge.net/apps/trac/libstoragemgmt > > The current focus is on managing external storage (SMI-S, etc.). This > focus can be expanded over time. Contributions welcome. > Device management(scalability/feature mgmt) - 1) scalability: I may be wrong but storage boxes like symmetrix(and others) support large number of LUNs. So device management 'scalability' will make linux shine. By scalability I mean efficiently managing let's say 32K(?) LUNs. 2) feature management: As Shyam mentioned in earlier emails - provide an ecosystem similar to smart-phones. Let me provide an example(and then you guys can correct me by saying this already exists or bits and pieces exist): a) As a kernel developer - export all the features(to the upper layers) we can by querying the target. b) As an app developer - GetLUNFeatures(), could return - {Thin Provision, RAID-level, ... ). c) As a sys-admin - If I right click(for a volume/LUN) on my management GUI, I should be able to tell if my volume supports thin-prov, backed by DRBD[proxy?] etc. So once we provide b) from above, tens(if not hundreds) of apps will be developed in a short period of time. I feel libstoragemgmt is an excellent place to get all of this organized. Chetan Loke
next prev parent reply other threads:[~2012-01-19 16:17 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-21 15:59 [LSF/MM TOPIC] linux servers as a storage server - what's missing? Ric Wheeler 2011-12-22 8:14 ` Shyam_Iyer 2011-12-22 8:14 ` Shyam_Iyer 2011-12-22 15:58 ` Vivek Goyal 2011-12-22 20:54 ` Shyam_Iyer 2011-12-22 20:54 ` Shyam_Iyer 2011-12-23 3:06 ` Vivek Goyal 2011-12-23 4:35 ` Shyam_Iyer 2011-12-23 4:35 ` Shyam_Iyer 2012-01-09 12:18 ` Hannes Reinecke 2012-01-09 12:59 ` Tom Coughlan 2012-01-10 6:53 ` Ric Wheeler 2012-01-20 8:55 ` Hannes Reinecke 2012-01-19 16:17 ` Loke, Chetan [this message] 2012-01-19 16:17 ` [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Loke, Chetan 2012-01-19 16:19 ` Ric Wheeler 2012-01-19 16:26 ` Loke, Chetan 2012-01-19 16:26 ` Loke, Chetan 2012-01-19 16:29 ` Ric Wheeler 2012-01-19 17:32 ` Loke, Chetan 2012-01-19 17:32 ` Loke, Chetan 2012-01-19 17:44 ` Ric Wheeler 2012-01-19 21:30 ` Loke, Chetan 2012-01-19 21:30 ` Loke, Chetan 2012-01-19 21:39 ` Ric Wheeler 2012-01-24 17:05 ` Loke, Chetan 2012-01-24 17:05 ` Loke, Chetan 2012-01-24 18:13 ` Ric Wheeler 2012-01-26 22:24 ` Dave Chinner 2012-01-26 22:29 ` Ric Wheeler 2012-01-03 19:26 ` [LSF/MM TOPIC][ATTEND] linux servers as a storage server - what's missing? Jeff Layton 2012-01-03 19:32 ` Chuck Lever 2012-01-17 21:16 ` J. Bruce Fields 2012-01-17 21:25 ` Chuck Lever 2012-01-24 21:36 ` J. Bruce Fields 2012-01-24 23:13 ` Ric Wheeler 2012-01-25 19:05 ` Christopher R. Hertel 2012-01-25 20:25 ` Christopher R. Hertel 2012-01-25 21:56 ` Roland Dreier 2012-01-25 22:09 ` Christopher R. Hertel 2012-01-26 21:52 ` Andy Grover 2012-01-26 11:15 ` Bart Van Assche 2012-01-18 17:00 ` [LSF/MM TOPIC] " Roland Dreier 2012-01-18 17:51 ` Ric Wheeler 2012-01-18 18:46 ` Roland Dreier 2012-01-18 18:51 ` Bart Van Assche 2012-01-18 19:00 ` Roland Dreier 2012-01-19 8:16 ` Rolf Eike Beer 2012-01-19 17:50 ` Loke, Chetan 2012-01-19 17:50 ` Loke, Chetan
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=D3F292ADF945FB49B35E96C94C2061B9159134BD@nsmail.netscout.com \ --to=chetan.loke@netscout.com \ --cc=Shyam_Iyer@Dell.com \ --cc=coughlan@redhat.com \ --cc=hare@suse.de \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-scsi@vger.kernel.org \ --cc=rwheeler@redhat.com \ --cc=tasleson@redhat.com \ --cc=vgoyal@redhat.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: linkBe 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.