All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] An updated quick start guide for a virtual Lustre clustre - call for input
Date: Wed, 03 Jun 2015 14:57:25 -0700	[thread overview]
Message-ID: <556F7845.3010703@llnl.gov> (raw)
In-Reply-To: <CA+sy+eT0B+=vBDzXJjPPsh+6sgXODnbk_J-Zb3+sNDW=MbbmLw@mail.gmail.com>

Hi John,

Don't worry about how we link to it at this stage.  Just pick a 
descriptive, unique, short title (which will also function as the URL, 
so choose wisely) and make the page.  But even there, don't sweat it too 
much, because we can always rename the page later if we come up with a 
better title.

We can worry about from where we should link to your page when the page 
was reached a point that you think it is ready for general consumption 
of its target audience.  No doubt there will be links to it from more 
than one other page.

Chris

On 06/03/2015 02:52 PM, John Suykerbuyk wrote:
> Thanks Chris,
>
> Is there a particular section or place you'd like me to post my Lustre
> Quick Start guide?  Looking around on wiki.lustre.org
> <http://wiki.lustre.org>, the best fit seems to be to add a "Guides"
> subsection to the developer page and then add my document to that.
>
> - John "S"
>
> On Wed, Jun 3, 2015 at 3:35 PM, Christopher J. Morrone
> <morrone2 at llnl.gov <mailto:morrone2@llnl.gov>> wrote:
>
>     Hi John,
>
>     Welcome aboard!  We are happy to have you.
>
>     I don't have to much to say, except that we probably won't have much
>     useful input for you until we can see the draft.  When you get the
>     draft up on wiki.lustre.org <http://wiki.lustre.org>, let us know
>     again and I am sure that some of us will have some feedback for you.
>
>     Thanks,
>     Chris
>
>     On 06/03/2015 01:27 PM, John Suykerbuyk wrote:
>
>         Hello,
>
>
>         I?m a fairly new hire with Seagate?s Cloud Services group
>         supporting and
>         contributing to Lustre.  Being relatively unfamiliar with
>         Lustre, I was
>         given the opportunity to write a quick-start guide that new
>         developers
>         such as myself could follow.
>
>         I?m soliciting any input as to what others might want to be included
>         before submitting my final draft.
>
>         At LUG 2015, Brian Andrus had an excellent presentation that I?m
>         basing
>         my document upon and extending
>         (http://cdn.opensfs.org/wp-content/uploads/2015/04/Lustre-101_Andrus.pdf).
>
>
>         My intent is to enable new developers to quickly get a virtual
>         Lustre
>         cluster up and running with very little knowledge of Lustre, KVM
>         or even
>         specifics of which repositories and packages to pull from to get
>         things
>         to ?just work?.
>
>
>         At the moment, my write up is about 80% complete, and I have a
>         collection of very simple BASH scripts that bootstraps Centos
>         6.6 VM?s
>         entirely from a local kickstart file with no local installation
>         media
>         required (everything is pulled from mirrors.centos.org
>         <http://mirrors.centos.org>
>         <http://mirrors.centos.org>).  I am also setting up YUM in the
>         VM?s to
>         prioritise the repos at
>         https://downloads.hpdd.intel.com/public/lustreand
>         https://downloads.hpdd.intel.com/public/e2fsprogsahead of
>         anything else
>         along with another very simple script that does the the actual
>         install
>         and configuration.
>
>
>         I chose to document much of the menial steps in scripts as it
>         serves to
>         both document what pages of text would attempt to explain and it
>         gives
>         the option to ?just use it?.
>
>
>         Before wrapping this up and presenting the final draft, I am
>         turning to
>         the community for any input on things that should be included.
>
>
>         Thank you!
>
>         John Suykerbuyk
>
>
>
>         _______________________________________________
>         lustre-devel mailing list
>         lustre-devel at lists.lustre.org <mailto:lustre-devel@lists.lustre.org>
>         http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>
>     _______________________________________________
>     lustre-devel mailing list
>     lustre-devel at lists.lustre.org <mailto:lustre-devel@lists.lustre.org>
>     http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>

      reply	other threads:[~2015-06-03 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 20:27 [lustre-devel] An updated quick start guide for a virtual Lustre clustre - call for input John Suykerbuyk
2015-06-03 21:35 ` Christopher J. Morrone
2015-06-03 21:52   ` John Suykerbuyk
2015-06-03 21:57     ` Christopher J. Morrone [this message]

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=556F7845.3010703@llnl.gov \
    --to=morrone2@llnl.gov \
    --cc=lustre-devel@lists.lustre.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.