Lustre community - Oct 2010 - SC10 HPCFS Community Technical Meeting Agenda

Hi folks,

We have a ballroom that will comfortably seat 100 people for our first
face-to-face community meeting at SC10 at 6-8PM on Sunday, November 14th. This
kind of resource is very hard to come by so many kind thanks to Intel for the
generous contribution.

A few ideas were kicked around on the HPCFS call today and we all agreed that
the session should be technically focused. I''ll outline my
interpretation of proposed topics in a draft agenda, below, to get the creative
juices flowing.

0. Meeting kick-off (10 minutes)
- welcome everyone to the session; review agenda
- really no time to do introductions of 100 people; any thoughts on this?
- review: HPCFS booth; other meetings this week; future events; update on LUG
2011

1. Feature Development Projects (45 minutes)
- have community members -- vendors and users alike -- deliver short
"lightning talks" on their Lustre feature development and testing
projects; this will give us a broad perspective of who is working on what
- for development projects, answer a set of standard questions as much as
you''re willing or able to: base Lustre version; estimated resources and
duration; anticipated completion date; where to find out more
- for testing projects, answer standard questions: test cluster characteristics;
routine availability (e.g. available for 4-hour test shot once a week); special
availability (e.g. available for an entire week, twice a year); test suite
summary
- time budget: ~5 minutes each; larger organizations (e.g. Oracle) may take 7-10
minutes
- we''ll poll organizations in advance to determine who is going to
present and fine-tune the line-up
- to make this go smoothly, we''ll need folks to submit PDF material in
advance and have it pre-loaded on a projection system

2. Community Collaboration Discussion Panel (60 minutes)
- conduct a panel discussion with leading community engineering leaders where
some substantial amount of Lustre development is happening
- participants should include: Jacques-Charles Lafoucriere (CEA), Brian
Behlendorf (LLNL), Andreas Dilger (Oracle), Eric Barton (WhamCloud), Peter Braam
or Chris Bloxham (Xyratex); others are welcome
- format can be a series of questions to the panel; they can have prepared
slides to address (submitted in advance) or just talk

Candiate questions (10 minutes each topic plus 5 minutes general discussion):
- what are the anticipated challenges and opportunities (2 questions) associated
with the rapidly evolving Lustre development community
- how can we coordinate bug fixing and feature development into a common set of
branches for testing and evaluation?
- how can we collaborate with Oracle to ensure that changes (bug fixes and
features) get included upstream into the canonical release branches?
- what common practices, processes, and standards are required to ensure
compatibility and the highest standards of quality for Lustre?

3. Meeting wrap-up and next actions (5 minutes)
- summarize key next actions

There was also some discussion about a Lustre feature requirements gathering
exercise. In my experience, such an effort could easily take 2-4 hours with an
audience as large as this and probably can''t be managed effectively
with our limited time. My suggestion is to focus on some of the community
collaboration basics, above, and defer this matter to a later meeting (LUG,
perhaps).

Some questions to help generate discussion:
- how closely does this match your expectations?
- who are the "must have" organizations/people to which we should
reach out?
- is there anything really important that appears to be missing?
- is the proposed format practical and workable?

I''m looking forward to the discussion.

Cheers,
Bojanic______________________________________________________________________
This email may contain privileged or confidential information, which should only
be used for the purpose for which it was sent by Xyratex. No further rights or
licenses are granted to use such information. If you are not the intended
recipient of this message, please notify the sender by return and delete it. You
may not use, copy, disclose or rely on the information contained in it.
 
Internet email is susceptible to data corruption, interception and unauthorised
amendment for which Xyratex does not accept liability. While we have taken
reasonable precautions to ensure that this email is free of viruses, Xyratex
does not accept liability for the presence of any computer viruses in this
email, nor for any losses caused as a result of viruses.
 
Xyratex Technology Limited (03134912), Registered in England & Wales,
Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
 
The Xyratex group of companies also includes, Xyratex Ltd, registered in
Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia)
Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in
The People''s Republic of China and Xyratex Japan Limited registered in
Japan.
______________________________________________________________________

On 2010-10-18, at 13:07, Peter Bojanic wrote:
> A few ideas were kicked around on the HPCFS call today and we all agreed
that the session should be technically focused. I''ll outline my
interpretation of proposed topics in a draft agenda, below, to get the creative
juices flowing.
> 
> 0. Meeting kick-off (10 minutes)
> - welcome everyone to the session; review agenda
> - really no time to do introductions of 100 people; any thoughts on this?
> - review: HPCFS booth; other meetings this week; future events; update on
LUG 2011
> 
> 1. Feature Development Projects (45 minutes)
> - have community members -- vendors and users alike -- deliver short
"lightning talks" on their Lustre feature development and testing
projects; this will give us a broad perspective of who is working on what
> - for development projects, answer a set of standard questions as much as
you''re willing or able to: base Lustre version; estimated resources and
duration; anticipated completion date; where to find out more
This seems fairly reasonable (ignoring the completion dates for now), and will
avoid us stepping on each other''s toes.  I think to a large extent
Oracle''s development plans are widely known, while other
vendor''s plans are not.
> - for testing projects, answer standard questions: test cluster
characteristics; routine availability (e.g. available for 4-hour test shot once
a week); special availability (e.g. available for an entire week, twice a year);
test suite summary
> - time budget: ~5 minutes each; larger organizations (e.g. Oracle) may take
7-10 minutes
> - we''ll poll organizations in advance to determine who is going to
present and fine-tune the line-up
> - to make this go smoothly, we''ll need folks to submit PDF
material in advance and have it pre-loaded on a projection system
> 
> 2. Community Collaboration Discussion Panel (60 minutes)
> - conduct a panel discussion with leading community engineering leaders
where some substantial amount of Lustre development is happening
> - participants should include: Jacques-Charles Lafoucriere (CEA), Brian
Behlendorf (LLNL), Andreas Dilger (Oracle), Eric Barton (WhamCloud), Peter Braam
or Chris Bloxham (Xyratex); others are welcome
> - format can be a series of questions to the panel; they can have prepared
slides to address (submitted in advance) or just talk
> 
> Candiate questions (10 minutes each topic plus 5 minutes general
discussion):
> - what are the anticipated challenges and opportunities (2 questions)
associated with the rapidly evolving Lustre development community
> - how can we coordinate bug fixing and feature development into a common
set of branches for testing and evaluation?
> - how can we collaborate with Oracle to ensure that changes (bug fixes and
features) get included upstream into the canonical release branches?
> - what common practices, processes, and standards are required to ensure
compatibility and the highest standards of quality for Lustre?
Also seems reasonable.  I would be willing to participate in this panel.
> 3. Meeting wrap-up and next actions (5 minutes)
> - summarize key next actions
> 
> There was also some discussion about a Lustre feature requirements
gathering exercise. In my experience, such an effort could easily take 2-4 hours
with an audience as large as this and probably can''t be managed
effectively with our limited time. My suggestion is to focus on some of the
community collaboration basics, above, and defer this matter to a later meeting
(LUG, perhaps).
I agree - we spent a whole day on requirements gathering in the past, and it
didn''t turn up any real surprises.  In the end, many of the areas that
were voted (e.g. RAS) highly got little to no development funding, while
performance is always king of the hill.

Cheers, Andreas
--
Andreas Dilger
Lustre Technical Lead
Oracle Corporation Canada Inc.

Hi folks,

We have a ballroom that will comfortably seat 100 people for our first
face-to-face community meeting at SC10 at 6-8PM on Sunday, November 14th. This
kind of resource is very hard to come by so many kind thanks to Intel for the
generous contribution.

A few ideas were kicked around on the HPCFS call today and we all agreed that
the session should be technically focused. I''ll outline my
interpretation of proposed topics in a draft agenda, below, to get the creative
juices flowing.

0. Meeting kick-off (10 minutes)
- welcome everyone to the session; review agenda
- really no time to do introductions of 100 people; any thoughts on this?
- review: HPCFS booth; other meetings this week; future events; update on LUG
2011

1. Feature Development Projects (45 minutes)
- have community members -- vendors and users alike -- deliver short
"lightning talks" on their Lustre feature development and testing
projects; this will give us a broad perspective of who is working on what
- for development projects, answer a set of standard questions as much as
you''re willing or able to: base Lustre version; estimated resources and
duration; anticipated completion date; where to find out more
- for testing projects, answer standard questions: test cluster characteristics;
routine availability (e.g. available for 4-hour test shot once a week); special
availability (e.g. available for an entire week, twice a year); test suite
summary
- time budget: ~5 minutes each; larger organizations (e.g. Oracle) may take 7-10
minutes
- we''ll poll organizations in advance to determine who is going to
present and fine-tune the line-up
- to make this go smoothly, we''ll need folks to submit PDF material in
advance and have it pre-loaded on a projection system

2. Community Collaboration Discussion Panel (60 minutes)
- conduct a panel discussion with leading community engineering leaders where
some substantial amount of Lustre development is happening
- participants should include:  Aurelien Degremont (CEA), Brian Behlendorf
(LLNL), Andreas Dilger (Oracle), Robert Read (WhamCloud), Peter Braam or Chris
Bloxham (Xyratex); others are welcome
- format can be a series of questions to the panel; they can have prepared
slides to address (submitted in advance) or just talk

Candiate questions (10 minutes each topic plus 5 minutes general discussion):
- what are the anticipated challenges and opportunities (2 questions) associated
with the rapidly evolving Lustre development community
- how can we coordinate bug fixing and feature development into a common set of
branches for testing and evaluation?
- how can we collaborate with Oracle to ensure that changes (bug fixes and
features) get included upstream into the canonical release branches?
- what common practices, processes, and standards are required to ensure
compatibility and the highest standards of quality for Lustre?

3. Meeting wrap-up and next actions (5 minutes)
- summarize key next actions

There was also some discussion about a Lustre feature requirements gathering
exercise. In my experience, such an effort could easily take 2-4 hours with an
audience as large as this and probably can''t be managed effectively
with our limited time. My suggestion is to focus on some of the community
collaboration basics, above, and defer this matter to a later meeting (LUG,
perhaps).

Some questions to help generate discussion:
- how closely does this match your expectations?
- who are the "must have" organizations/people to which we should
reach out?
- is there anything really important that appears to be missing?
- is the proposed format practical and workable?

I''m looking forward to the discussion.

Cheers,
Bojanic______________________________________________________________________
This email may contain privileged or confidential information, which should only
be used for the purpose for which it was sent by Xyratex. No further rights or
licenses are granted to use such information. If you are not the intended
recipient of this message, please notify the sender by return and delete it. You
may not use, copy, disclose or rely on the information contained in it.
 
Internet email is susceptible to data corruption, interception and unauthorised
amendment for which Xyratex does not accept liability. While we have taken
reasonable precautions to ensure that this email is free of viruses, Xyratex
does not accept liability for the presence of any computer viruses in this
email, nor for any losses caused as a result of viruses.
 
Xyratex Technology Limited (03134912), Registered in England & Wales,
Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
 
The Xyratex group of companies also includes, Xyratex Ltd, registered in
Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia)
Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in
The People''s Republic of China and Xyratex Japan Limited registered in
Japan.
______________________________________________________________________

Hi folks,

I spoke to J Ray Scott of PSC this week and he''s generously agreed to
facilitate the panel discussion (part 2). I anticipate he''ll reach out
by email to all the confirmed panelists (to: line of this email). Unfortunately
Livermore are unable to participate but if you have any other suggestions of
substantial Lustre contributors, please recommend to J Ray.

I''ve seeded a set of "Candidate questions", below. I
encourage J Ray to treat this only as a suggestion and take the discussion in a
direction that he believes will be interesting to the user community. I would
ask, though, that we get visibility to the questions in advance to sufficiently
prepare.

On a final note, I''d like to be invited as a panelist for part 2 to
represent Xyratex. We have a number of strong technical leaders doing Lustre
work but I''ve been encouraged to represent us in this forum.

Many thanks, J Ray, for rising to the occasion!

Cheers,
Bojanic

Begin forwarded message:
> From: "Peter Bojanic" <Peter_Bojanic at xyratex.com>
> Date: October 25, 2010 14:24:32 MDT
> To: <lustre-community at lists.lustre.org>
> Subject: [Lustre-community] SC10 HPCFS Community Technical Meeting Agenda
> 
> Hi folks,
> 
> We have a ballroom that will comfortably seat 100 people for our first
face-to-face community meeting at SC10 at 6-8PM on Sunday, November 14th. This
kind of resource is very hard to come by so many kind thanks to Intel for the
generous contribution.
> 
> A few ideas were kicked around on the HPCFS call today and we all agreed
that the session should be technically focused. I''ll outline my
interpretation of proposed topics in a draft agenda, below, to get the creative
juices flowing.
> 
> 0. Meeting kick-off (10 minutes)
> - welcome everyone to the session; review agenda
> - really no time to do introductions of 100 people; any thoughts on this?
> - review: HPCFS booth; other meetings this week; future events; update on
LUG 2011
> 
> 1. Feature Development Projects (45 minutes)
> - have community members -- vendors and users alike -- deliver short
"lightning talks" on their Lustre feature development and testing
projects; this will give us a broad perspective of who is working on what
> - for development projects, answer a set of standard questions as much as
you''re willing or able to: base Lustre version; estimated resources and
duration; anticipated completion date; where to find out more
> - for testing projects, answer standard questions: test cluster
characteristics; routine availability (e.g. available for 4-hour test shot once
a week); special availability (e.g. available for an entire week, twice a year);
test suite summary
> - time budget: ~5 minutes each; larger organizations (e.g. Oracle) may take
7-10 minutes
> - we''ll poll organizations in advance to determine who is going to
present and fine-tune the line-up
> - to make this go smoothly, we''ll need folks to submit PDF
material in advance and have it pre-loaded on a projection system
> 
> 2. Community Collaboration Discussion Panel (60 minutes)
> - conduct a panel discussion with leading community engineering leaders
where some substantial amount of Lustre development is happening
> - participants should include:  Aurelien Degremont (CEA), Brian Behlendorf
(LLNL), Andreas Dilger (Oracle), Robert Read (WhamCloud), Peter Braam or Chris
Bloxham (Xyratex); others are welcome
> - format can be a series of questions to the panel; they can have prepared
slides to address (submitted in advance) or just talk
> 
> Candiate questions (10 minutes each topic plus 5 minutes general
discussion):
> - what are the anticipated challenges and opportunities (2 questions)
associated with the rapidly evolving Lustre development community
> - how can we coordinate bug fixing and feature development into a common
set of branches for testing and evaluation?
> - how can we collaborate with Oracle to ensure that changes (bug fixes and
features) get included upstream into the canonical release branches?
> - what common practices, processes, and standards are required to ensure
compatibility and the highest standards of quality for Lustre?
> 
> 3. Meeting wrap-up and next actions (5 minutes)
> - summarize key next actions
> 
> There was also some discussion about a Lustre feature requirements
gathering exercise. In my experience, such an effort could easily take 2-4 hours
with an audience as large as this and probably can''t be managed
effectively with our limited time. My suggestion is to focus on some of the
community collaboration basics, above, and defer this matter to a later meeting
(LUG, perhaps).
> 
> Some questions to help generate discussion:
> - how closely does this match your expectations?
> - who are the "must have" organizations/people to which we should
reach out?
> - is there anything really important that appears to be missing?
> - is the proposed format practical and workable?
> 
> I''m looking forward to the discussion.
> 
> Cheers,
> Bojanic>
______________________________________________________________________
> This email may contain privileged or confidential information, which should
only be used for the purpose for which it was sent by Xyratex. No further rights
or licenses are granted to use such information. If you are not the intended
recipient of this message, please notify the sender by return and delete it. You
may not use, copy, disclose or rely on the information contained in it.
> 
> Internet email is susceptible to data corruption, interception and
unauthorised amendment for which Xyratex does not accept liability. While we
have taken reasonable precautions to ensure that this email is free of viruses,
Xyratex does not accept liability for the presence of any computer viruses in
this email, nor for any losses caused as a result of viruses.
> 
> Xyratex Technology Limited (03134912), Registered in England & Wales,
Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
> 
> The Xyratex group of companies also includes, Xyratex Ltd, registered in
Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia)
Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in
The People''s Republic of China and Xyratex Japan Limited registered in
Japan.
> ______________________________________________________________________
> 
> 
> _______________________________________________
> Lustre-community mailing list
> Lustre-community at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-community

On 2010-11-04, at 12:18, Peter Bojanic wrote:
> I spoke to J Ray Scott of PSC this week and he''s generously agreed
to facilitate the panel discussion (part 2). I anticipate he''ll reach
out by email to all the confirmed panelists (to: line of this email).
Unfortunately Livermore are unable to participate but if you have any other
suggestions of substantial Lustre contributors, please recommend to J Ray.
Peter, J Ray,
thanks for continuing to move this forward.  I look forward to seeing everyone
at SC - in only 10 days!
> I''ve seeded a set of "Candidate questions", below. I
encourage J Ray to treat this only as a suggestion and take the discussion in a
direction that he believes will be interesting to the user community. I would
ask, though, that we get visibility to the questions in advance to sufficiently
prepare.
Agreed.
> On a final note, I''d like to be invited as a panelist for part 2
to represent Xyratex. We have a number of strong technical leaders doing Lustre
work but I''ve been encouraged to represent us in this forum.
I''m happy to have you join us on the panel to represent Xyratex.
> Begin forwarded message:
> 
>> From: "Peter Bojanic" <Peter_Bojanic at xyratex.com>
>> Date: October 25, 2010 14:24:32 MDT
>> To: <lustre-community at lists.lustre.org>
>> Subject: [Lustre-community] SC10 HPCFS Community Technical Meeting
Agenda
>> 
>> Hi folks,
>> 
>> We have a ballroom that will comfortably seat 100 people for our first
face-to-face community meeting at SC10 at 6-8PM on Sunday, November 14th. This
kind of resource is very hard to come by so many kind thanks to Intel for the
generous contribution.
>> 
>> A few ideas were kicked around on the HPCFS call today and we all
agreed that the session should be technically focused. I''ll outline my
interpretation of proposed topics in a draft agenda, below, to get the creative
juices flowing.
>> 
>> 0. Meeting kick-off (10 minutes)
>> - welcome everyone to the session; review agenda
>> - really no time to do introductions of 100 people; any thoughts on
this?
>> - review: HPCFS booth; other meetings this week; future events; update
on LUG 2011
>> 
>> 1. Feature Development Projects (45 minutes)
>> - have community members -- vendors and users alike -- deliver short
"lightning talks" on their Lustre feature development and testing
projects; this will give us a broad perspective of who is working on what
>> - for development projects, answer a set of standard questions as much
as you''re willing or able to: base Lustre version; estimated resources
and duration; anticipated completion date; where to find out more
>> - for testing projects, answer standard questions: test cluster
characteristics; routine availability (e.g. available for 4-hour test shot once
a week); special availability (e.g. available for an entire week, twice a year);
test suite summary
>> - time budget: ~5 minutes each; larger organizations (e.g. Oracle) may
take 7-10 minutes
>> - we''ll poll organizations in advance to determine who is
going to present and fine-tune the line-up
>> - to make this go smoothly, we''ll need folks to submit PDF
material in advance and have it pre-loaded on a projection system
>> 
>> 2. Community Collaboration Discussion Panel (60 minutes)
>> - conduct a panel discussion with leading community engineering leaders
where some substantial amount of Lustre development is happening
>> - participants should include:  Aurelien Degremont (CEA), Brian
Behlendorf (LLNL), Andreas Dilger (Oracle), Robert Read (WhamCloud), Peter Braam
or Chris Bloxham (Xyratex); others are welcome
>> - format can be a series of questions to the panel; they can have
prepared slides to address (submitted in advance) or just talk
>> 
>> Candiate questions (10 minutes each topic plus 5 minutes general
discussion):
>> - what are the anticipated challenges and opportunities (2 questions)
associated with the rapidly evolving Lustre development community
>> - how can we coordinate bug fixing and feature development into a
common set of branches for testing and evaluation?
>> - how can we collaborate with Oracle to ensure that changes (bug fixes
and features) get included upstream into the canonical release branches?
>> - what common practices, processes, and standards are required to
ensure compatibility and the highest standards of quality for Lustre?
>> 
>> 3. Meeting wrap-up and next actions (5 minutes)
>> - summarize key next actions
>> 
>> There was also some discussion about a Lustre feature requirements
gathering exercise. In my experience, such an effort could easily take 2-4 hours
with an audience as large as this and probably can''t be managed
effectively with our limited time. My suggestion is to focus on some of the
community collaboration basics, above, and defer this matter to a later meeting
(LUG, perhaps).
>> 
>> Some questions to help generate discussion:
>> - how closely does this match your expectations?
>> - who are the "must have" organizations/people to which we
should reach out?
>> - is there anything really important that appears to be missing?
>> - is the proposed format practical and workable?
>> 
>> I''m looking forward to the discussion.
>> 
>> Cheers,
>> Bojanic>>
______________________________________________________________________
>> This email may contain privileged or confidential information, which
should only be used for the purpose for which it was sent by Xyratex. No further
rights or licenses are granted to use such information. If you are not the
intended recipient of this message, please notify the sender by return and
delete it. You may not use, copy, disclose or rely on the information contained
in it.
>> 
>> Internet email is susceptible to data corruption, interception and
unauthorised amendment for which Xyratex does not accept liability. While we
have taken reasonable precautions to ensure that this email is free of viruses,
Xyratex does not accept liability for the presence of any computer viruses in
this email, nor for any losses caused as a result of viruses.
>> 
>> Xyratex Technology Limited (03134912), Registered in England &
Wales, Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
>> 
>> The Xyratex group of companies also includes, Xyratex Ltd, registered
in Bermuda, Xyratex International Inc, registered in California, Xyratex
(Malaysia) Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd
registered in The People''s Republic of China and Xyratex Japan Limited
registered in Japan.
>> ______________________________________________________________________
>> 
>> 
>> _______________________________________________
>> Lustre-community mailing list
>> Lustre-community at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-community
> 

Cheers, Andreas
--
Andreas Dilger
Lustre Technical Lead
Oracle Corporation Canada Inc.