Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Deshmukh <Rahul.Deshmukh@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [RFC] HLD Review Request: Interoperability at server side
Date: Mon, 30 Jun 2008 20:05:50 +0530	[thread overview]
Message-ID: <4868EF46.7030002@sun.com> (raw)
In-Reply-To: <C48A9A97.611F%peter.braam@sun.com>

Please see the comments inline.

Peter Braam wrote:
> Really good - well done!  I feel comfortable that this can move ahead.
>   
Thanks !!!
> I just want to ask you to make sure that repeated upgrade - downgrade -
> upgrade events (in the case bugs in the new release force the user back to
> old) are handled correctly.  I did see a discussion of up and down, but no
> explicit mention of repeating that process multiple times.
>   
I will update the HLD to include the details related to repeating the 
upgrade -
downgrade process multiple times.
> Regards,
>
> Peter
>
>   
Thanks,
Rahul.
>
>
> On 6/25/08 11:26 PM, "Rahul Deshmukh" <Rahul.Deshmukh@Sun.COM> wrote:
>
>   
>> Hi Peter/Eric,
>>
>> Please inspect next version of "Interoperability at server side" HLD.
>>
>> Thanks,
>> Rahul.
>>
>>     
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel

  parent reply	other threads:[~2008-06-30 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48632894.1050204@sun.com>
2008-06-27 19:24 ` [Lustre-devel] [RFC] HLD Review Request: Interoperability at server side Peter Braam
2008-06-27 19:30   ` Nikita Danilov
2008-06-30 14:35   ` Rahul Deshmukh [this message]
2008-08-01 10:11     ` Rahul Deshmukh

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=4868EF46.7030002@sun.com \
    --to=rahul.deshmukh@sun.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox