All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jan Tulak <jtulak@redhat.com>, lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
	Justin Mitchell <jumitche@redhat.com>
Subject: Re: [LSF/MM TOPIC] Springfield: smart and automated storage
Date: Sat, 27 Jan 2018 08:32:46 -0800	[thread overview]
Message-ID: <1517070766.3012.16.camel@HansenPartnership.com> (raw)
In-Reply-To: <CACj3i73kv3w_7JuYUi_iL6_2tVTYmj+HZBStfP6oEshz2Enx1w@mail.gmail.com>

On Sat, 2018-01-27 at 09:37 +0100, Jan Tulak wrote:
> Springfield is a collection of projects unifying multiple levels of
> the storage stack and providing a general API for automation, health
> and status monitoring, as well as sane and easy configuration across
> multiple levels of the storage stack. It is a scalable solution,
> working from a single node to large deployments with a mix of base
> metal, containers and VMs. For the first time, it was presented on
> Vault 2017 in a birds of a feather session.
> 
> Springfield builds upon and enhances the existing work of those
> projects:
> * udisks
> * libblockdev
> * blivet
> * libstoragemgmt
> 
> It is a coordinated effort to overcome many of the shortcomings of
> the current situation and provide a unified approach to storage
> management, so there is nothing like a binary or a library with the
> name “Springfield.”
> 
> An example of things we are trying to tackle is a useful storage
> reporting, like notifications about filesystem being full, especially
> with thin provisioning and multiple levels of the storage stack,
> where
> the user-visible status is not a true representation of what is
> happening underneath.
> 
> We want to see how the community sees this effort. What shortcomings
> of the current situation in storage layering can Springfield address
> (is there something we don’t see, but a project like this could
> help)? How would you use it, or what would make it more useful to
> you?

Do you have a link to the project page and the source tree(s)?

James

  reply	other threads:[~2018-01-27 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  8:37 [LSF/MM TOPIC] Springfield: smart and automated storage Jan Tulak
2018-01-27 16:32 ` James Bottomley [this message]
2018-01-29  8:48   ` Jan Tulak

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=1517070766.3012.16.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jtulak@redhat.com \
    --cc=jumitche@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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.