Lustre discuss - Sep 2008 - Installation of Lustre on ubuntu /Debian

Hi All,

 

I want to install Lustre on Ubuntu OR Debian.

 

Has anyone done installation of Lustre 1.6.x.x on Ubuntu OR Debian.

 

If yes what version and how.

 

Thanks and Regards

 

Chirag Raval

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080909/6513c5c1/attachment.html

http://wiki.lustre.org/index.php?title=Debian_Install

http://www.mail-archive.com/lustre-discuss at lists.lustre.org/msg01925.html

On Tue, 2008-09-09 at 11:37 +0530, Chirag Raval wrote:
> Hi All,
> 
>  
> 
> I want to install Lustre on Ubuntu OR Debian.
> 
>  
> 
> Has anyone done installation of Lustre 1.6.x.x on Ubuntu OR Debian.
> 
>  
> 
> If yes what version and how.
> 
>  
> 
> Thanks and Regards
> 
>  
> 
> Chirag Raval
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

Hey,

Kalpak Shah wrote on Tuesday 09 September 2008 at
08:19:08:
> http://wiki.lustre.org/index.php?title=Debian_Install
What''s that ?? 

If you want to use Debian on your servers, please have a look right here: 
http://packages.debian.org/lustre

There is a small README.Debian inside lustre-source and linux-lustre-patch 
under /usr/share/doc/lustre-source/README.Debian where is described how to get 
started on debian. But please refer also to the official documents available at 
http://www.lustre.org
In Lenny will be version 1.6.5.1 of lustre and we''ll shortly provide
1.6.5.1
backports of lustre for etch on backports.org.

Hope this helps,

Greetings
Patrick Winnertz

-- 
Patrick Winnertz
Tel.: +49 (0) 2161 / 4643 - 0

credativ GmbH, HRB M?nchengladbach 12080
Hohenzollernstr. 133, 41061 M?nchengladbach
Gesch?ftsf?hrung: Dr. Michael Meskes, J?rg Folz

On Sep 09, 2008  08:53 +0200, Patrick Winnertz wrote:
> Kalpak Shah wrote on Tuesday 09 September 2008 at 08:19:08:
> > http://wiki.lustre.org/index.php?title=Debian_Install
> What''s that ?? 
>
> If you want to use Debian on your servers, please have a look right here: 
> http://packages.debian.org/lustre
Can you please update the above wiki page to reference the right
packages.

Also, I''d be happy to include the Debian packaging into the Lustre
CVS repository so that e.g. "make debs" can be run to build the .deb
packages, like "make rpms".  Unfortunately, my Debian-fu is low
these days, so it would need to be in the form of a patch against
Lustre, preferrably put in a bug.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

On Wed, 2008-09-10 at 03:55 -0600, Andreas Dilger wrote:
> 
> Also, I''d be happy to include the Debian packaging into the Lustre
> CVS repository so that e.g. "make debs" can be run to build the
.deb
> packages, like "make rpms".  Unfortunately, my Debian-fu is low
> these days, so it would need to be in the form of a patch against
> Lustre, preferrably put in a bug.
My dpkg-fu is pretty low too, but I have put together a /debian dir that
builds the patchless client (and the userspace tools of course).  The
problem I always seem to run into is that at some point between sitting
down at a fresh debian (ubuntu in my case) system and getting all
packages produced, including both modules and userspace tools, one has
to be root for at least some of the time.  IIRC, it''s usually the
module-assistant part that needs you to be (real, not fakeroot) root.

I think there is some way to use m-a with "-u" to get around this but
even then IIRC, m-a was pretty unhappy until I put lustre
into /usr/share/modass/compliant.list which again, required root.

Andreas, I''m not sure how you feel about it, but IMHO, its very
important that one can produce the full array of packages from a (say)
"make debs" in a lustre source pool without having to be(come) root at
any point in the process.

Would any of current debian package maintainers on this list like to
help us get to that point?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080910/4d0ec791/attachment-0001.bin

On Wednesday 10 September 2008 16:39:59 Brian J. Murrell
wrote:
> On Wed, 2008-09-10 at 03:55 -0600, Andreas Dilger wrote:
> > Also, I''d be happy to include the Debian packaging into the
Lustre
> > CVS repository so that e.g. "make debs" can be run to build
the .deb
> > packages, like "make rpms".  Unfortunately, my Debian-fu is
low
> > these days, so it would need to be in the form of a patch against
> > Lustre, preferrably put in a bug.
>
> My dpkg-fu is pretty low too, but I have put together a /debian dir that
> builds the patchless client (and the userspace tools of course).  The
> problem I always seem to run into is that at some point between sitting
> down at a fresh debian (ubuntu in my case) system and getting all
> packages produced, including both modules and userspace tools, one has
> to be root for at least some of the time.  IIRC, it''s usually the
> module-assistant part that needs you to be (real, not fakeroot) root.
Why should you need to use module-assistent? All you need to do is to compile 
Lustre and put the .ko files into a debian package?
>
> I think there is some way to use m-a with "-u" to get around this
but
> even then IIRC, m-a was pretty unhappy until I put lustre
> into /usr/share/modass/compliant.list which again, required root.
>
> Andreas, I''m not sure how you feel about it, but IMHO, its very
> important that one can produce the full array of packages from a (say)
> "make debs" in a lustre source pool without having to be(come)
root at
> any point in the process.
I don''t know if it is really important, since there is already a debian
way to
create packages. Actually in Lenny all packages are included and only the 
kernel modules have to be build, but even that can be easily done 
by "aptitude install lustre-source". And then building the modules
with
make-kpkg. Well o.k., I see your point when it comes to build a new lustre 
version, which is not in -stable yet. But for that there is always the 
possibility to backport the stuff from Debian Sid (unstable).
All of this applies to Ubuntu as well.
>
> Would any of current debian package maintainers on this list like to
> help us get to that point?
Patrick, Goswin and I certainly can help you (Patrick and Goswin have by far 
more experience to create clean packages than I have).


Cheers,
Bernd


-- 
Bernd Schubert
Q-Leap Networks GmbH

On Sep 10, 2008  18:11 +0200, Bernd Schubert wrote:
> there is already a debian way to 
> create packages. Actually in Lenny all packages are included and only the 
> kernel modules have to be build, but even that can be easily done 
> by "aptitude install lustre-source". And then building the
modules with
> make-kpkg. Well o.k., I see your point when it comes to build a new lustre 
> version, which is not in -stable yet. But for that there is always the 
> possibility to backport the stuff from Debian Sid (unstable).
My point is that personally I like to be able to "make rpms" from the
Lustre sources for my RPM-based systems, and I''d similarly like to
be able to do "make debs" to do whatever is needed to give me .deb
packages for my Deb-based systems instead of just doing "make install"
and having the files placed into system directories.

Having upstream packages doesn''t really help me in this regard, nor
does it help anyone that needs to apply a patch or wants to test the
code from CVS.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

Bernd Schubert wrote on Wednesday 10 September 2008 at
18:11:09:
> On Wednesday 10 September 2008 16:39:59 Brian J. Murrell wrote:
> > On Wed, 2008-09-10 at 03:55 -0600, Andreas Dilger wrote:
> > > Also, I''d be happy to include the Debian packaging into
the Lustre
> > > CVS repository so that e.g. "make debs" can be run to
build the .deb
> > > packages, like "make rpms".  Unfortunately, my
Debian-fu is low
> > > these days, so it would need to be in the form of a patch against
> > > Lustre, preferrably put in a bug.
> >
> > My dpkg-fu is pretty low too, but I have put together a /debian dir
that
> > builds the patchless client (and the userspace tools of course).  The
> > problem I always seem to run into is that at some point between
sitting
> > down at a fresh debian (ubuntu in my case) system and getting all
> > packages produced, including both modules and userspace tools, one has
> > to be root for at least some of the time.  IIRC, it''s usually
the
> > module-assistant part that needs you to be (real, not fakeroot) root.
>
> Why should you need to use module-assistent? All you need to do is to
> compile Lustre and put the .ko files into a debian package?
Yes. there is no need to use m-a if you only want to provide already compiled 
modules to exactly defined kernel version. 
But if you want to build several packages each for another kernel version it 
would make more sense to build a source package which is later build against 
the kernelversion. 
>
> > I think there is some way to use m-a with "-u" to get around
this but
> > even then IIRC, m-a was pretty unhappy until I put lustre
> > into /usr/share/modass/compliant.list which again, required root.
> >
> > Andreas, I''m not sure how you feel about it, but IMHO, its
very
> > important that one can produce the full array of packages from a (say)
> > "make debs" in a lustre source pool without having to
be(come) root at
> > any point in the process.
>
> I don''t know if it is really important, since there is already a
debian way
> to create packages. Actually in Lenny all packages are included and only
> the kernel modules have to be build, but even that can be easily done
> by "aptitude install lustre-source". And then building the
modules with
> make-kpkg. Well o.k., I see your point when it comes to build a new lustre
> version, which is not in -stable yet. But for that there is always the
> possibility to backport the stuff from Debian Sid (unstable).
> All of this applies to Ubuntu as well.
Please also remember that debian has backports.org which belongs now to the  
official debian infrastructure. Which backports.org it is possible to provide 
newer version of lustre to stable users. That''s what we want to use
once lenny
is stable. 
These packages will then be build from what is inside testing.
>
> > Would any of current debian package maintainers on this list like to
> > help us get to that point?
Yes, but I would suggest to use the debian infrastructure for providing 
packages for debian users. (As ubuntu is based on debian the goal to provide 
lustre to ubuntu users is also fullfilled). 



Greetings
Winnie

--
Patrick Winnertz
Tel.: +49 (0) 2161 / 4643 - 0

credativ GmbH, HRB M?nchengladbach 12080
Hohenzollernstr. 133, 41061 M?nchengladbach
Gesch?ftsf?hrung: Dr. Michael Meskes, J?rg Folz

On Thu, 2008-09-11 at 12:56 +0200, Patrick Winnertz
wrote:
> Yes. there is no need to use m-a if you only want to provide already
compiled
> modules to exactly defined kernel version. 
> But if you want to build several packages each for another kernel version
it
> would make more sense to build a source package which is later build
against
> the kernelversion. 
Let me prefix all of this by saying, we are not proposing to officially
release and support debian packages.

But if we are going to add support into the source tree for
building .debs we might as well do it with all future possibilities in
mind.

That said, maybe for a releaseable set of packages, we would want to
build both a (lustre modules) source package for people to build against
whatever kernel they wish and a binary modules package built against
whatever kernel we''d propose to be supporting.
> Yes, but I would suggest to use the debian infrastructure for providing 
> packages for debian users. (As ubuntu is based on debian the goal to
provide
> lustre to ubuntu users is also fullfilled). 
That''s fine, but what we need to tackle first is making it easy for
developers to (as Andreas put it) "make debs" and get all of the .debs
needed to install against the kernel that configure was pointed at.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080911/c8c7bb7f/attachment.bin

On Thu, 2008-09-11 at 04:01 +0200, Goswin von Brederlow
wrote:
> 
> I always build my own kernel with make-kpkg and I build lustre modules
> at the same time. So I never tested building lustre modules with
> m-a. I guess that just joined my ToDo list. But it should definetly
> work as plain user using fakeroot where needed.
I thought I tried every which way I could to make that happen but I
could not get it to.  I''d love to see whatever solution you come up
with.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080911/2f409f26/attachment.bin

On Wed, 2008-09-10 at 18:11 +0200, Bernd Schubert wrote:
> 
> Why should you need to use module-assistent?
Just because it seems to be promoted as the "official" way to build
kernel module packages.
> All you need to do is to compile 
> Lustre and put the .ko files into a debian package?
Indeed.  m-a just seemed like a nice neat way to do that be immune from
futurisms as any futurisms would presumably be incorporated into m-a.

Basically it''s just a case of trying to use "official
interfaces".
> I don''t know if it is really important, since there is already a
debian way to
> create packages. Actually in Lenny all packages are included and only the 
> kernel modules have to be build, but even that can be easily done 
> by "aptitude install lustre-source".
Yeah, this is all great for users.  It doesn''t help developers though,
with a lustre source code pool that needs to build and test packages.
> Well o.k., I see your point when it comes to build a new lustre 
> version, which is not in -stable yet.
That too.
> But for that there is always the 
> possibility to backport the stuff from Debian Sid (unstable).
> All of this applies to Ubuntu as well.
None of it covers the developer''s workflow to getting to something
reasonable to include in a (i.e. backports) repository though.
> Patrick, Goswin and I certainly can help you (Patrick and Goswin have by
far
> more experience to create clean packages than I have).
Any contributions will be most welcome.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080911/ca22480b/attachment.bin

> -----Original Message-----
> From: lustre-discuss-bounces at lists.lustre.org [mailto:lustre-discuss-
> bounces at lists.lustre.org] On Behalf Of Brian J. Murrell
> Sent: Thursday, September 11, 2008 11:01 AM
> To: lustre-discuss at lists.lustre.org
> Subject: Re: [Lustre-discuss] Installation of Lustre on ubuntu /Debian
> 
> On Thu, 2008-09-11 at 04:01 +0200, Goswin von Brederlow wrote:
> >
> > I always build my own kernel with make-kpkg and I build lustre
> modules
> > at the same time. So I never tested building lustre modules with
m-a.
> > I guess that just joined my ToDo list. But it should definetly work
> as
> > plain user using fakeroot where needed.
> 
> I thought I tried every which way I could to make that happen but I
> could not get it to.  I''d love to see whatever solution you come
up
> with.
> 
> b.
All I do is install the linux-patch-lustre and lustre-source packages,
run a make-kpkg --with-patches lustre and then boot into the new kernel
then use m-a to make the lustre modules package.

Robert LeBlanc
College of Life Sciences Computer Support
Brigham Young University
(801) 422-1882
leblanc at byu.edu

On Fri, 2008-09-12 at 08:22 -0600, Robert LeBlanc wrote:
> 
> All I do is install the linux-patch-lustre and lustre-source packages,
> run a make-kpkg --with-patches lustre and then boot into the new kernel
> then use m-a to make the lustre modules package.
Robert, as I''ve said though, that''s fine for users working
from
repositories, but it does not help a developer who has a source pool in
front of him and needs to, from that pool, produce the kernel, modules
and all userspace packages, without needing root and without needing to
reboot his workstation.

It''s well established that Lustre is in the debian repositories. 
It''s
the local developer build environment that needs to be worked on.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080912/d7798b5b/attachment.bin