Bug 9585 - new lustre-client
Summary: new lustre-client
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-01 14:48 CEST by michel tyteca
Modified: 2016-11-02 09:28 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
spec file for lustre-client (5.89 KB, text/plain)
2013-04-01 14:48 CEST, michel tyteca
Details

Description michel tyteca 2013-04-01 14:48:39 CEST
Created attachment 3681 [details]
spec file for lustre-client

Lustre FS works on Mageia-2
===========================
At Metefrance research, the standard workstation is a Linux Box under Mageia2. There are also
servers and a small HPC (20 nodes) running on the same distribtuion. Of course we dispose also of
a large HPC , dedicated to forecast models an big climate models that i am not responsible.
NFS was the network file system we used to share our data (30 servers, 500 workstations).
But i plan to use LustreFS, more scalable, to offer a one large vision of our space.
So i compiled and packaged the last release of lustre-client, developped by whamcloud,
for Mageia-2 distribution.
I think is a good thing because of a professionnal use of Mageia distribution around the
scientific comunnity. So i join a spec file to my message after fifteen days of positive 
tests.

Sorry for my english


Lustre FS client fonctionne sur Mageia-2
=========================================
Je ne sais pas si vous suivez cet aspect sinon ce qui suit peut vous informer.

Au centre de recherche de Meteofrance, tous les chercheurs disposent d'un poste sous Linux
mageia-2, d'un ensemble de serveurs de fichiers et d'un cluster d'une vingtaine de noeuds
egalement sous Mageia-2 que j'administre.
Ces ressources sont completes par la mise a disposition d'un HPC qui sert essentiellemnt a
l'exploitation et a la recherche des modeles de previsions et de climat (dont je ne suis pas
responsable).
Jusqu'a maintenant, les serveurs de fichiers etaient connectes a un SAN iSCSI et offraient
leur espace par NFS (~30 serveurs, ~20 clients NFS/serveur).
La nouvelle organisation sera architecturee autour d'un FS LUSTRE, bien plus scalable,
et offrira une vision globale sur tout l'espace.

Il se trouve que j'ai pu faire fonctionner le client lustre sur Mageia 2 sur les kernels
3.4.24 et maintenant 3.4.34. Whamcloud, a l'origine de la version 2 de LUSTRE a oeuvre pour
permettre au futur client lustre de s'integrer au kernel sans patch.
La version 2.3.62 parait suffisamment mure pour fonctionner.
Il me semble que la chose n'est pas sans interet dans la mesure ou Mageia peut apparaitre comme
une solution mure pour le poste de travail ou serveur dans le milieu professionnel scientifique.
Rares sont encore les distributions qui peuvent declarer etre compatible avec client lustre.
(a ma connaissance Chors Redhat/Centos/SLinux, je ne connais que Fedora et Ubuntu et encore 
pas n'importe qu'elle release).

Je vous transmets le fichier spec utilise, que l'on peut fortement ameliorer.
Bien que mes tests ne soient pas exhaustifs, aucune erreur n'a ete trouve depuis 15 jours apres
30To d'echanges avec plusieurs clients.


Michel TYTECA (michel.tyteca@meteo.fr)
Comment 1 Damien Lallement 2013-06-04 18:21:08 CEST
Thanks Michel. WIP! :-)

Status: NEW => ASSIGNED
CC: (none) => mageia
Assignee: bugsquad => mageia

Comment 2 Damien Lallement 2013-06-27 16:20:08 CEST
Hi Michel,

Can I try to package 2.4.51 or do you think 2.3.65 is better (for cauldron for now)?
Moreover, do you want this package in Mageia 2 or in Mageia 3?
Comment 3 Manuel Hiebel 2013-10-11 23:25:48 CEST
Changing version to Cauldron for keeping this request.
When Mageia 2 will be in End Of Life in a little more than one month, we will close these version bugs.

If the package is present in Mageia 3 or Cauldron, you can close this bug. Thanks.

--
Mageia Bugsquad

Version: 2 => Cauldron

Marja Van Waes 2015-04-21 19:28:42 CEST

CC: (none) => marja11
Attachment 3681 mime type: application/octet-stream => text/plain

Comment 4 Marja Van Waes 2015-04-21 19:32:52 CEST
Assigning back to Bug Squad, because Damien went MIA

@ Michel tyteca

You never replied to Damien's question in comment 2, does that mean you are no longer interested in having this packaged?

Status: ASSIGNED => NEW
Assignee: mageia => bugsquad

Comment 5 Maat 2016-02-04 10:23:32 CET
Hi all,

Lustre is a great distributed filesystem... i think we should definitely consider packaging it (server and client).

For huge and distributed data storage it's very good and even us could use it for our build system !

So even if Michel did not answer yet i think we don't want to close this issue.

Bests,

CC: (none) => maat-ml

Comment 6 Samuel Verschelde 2016-10-11 20:53:09 CEST
Assigning this package request to all packagers collectively. On a voluntary basis, one of them might want to integrate it to the distribution and maintain it for bug and security fixes.

You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Assignee: bugsquad => pkg-bugs

Comment 7 Marja Van Waes 2016-11-02 09:28:46 CET
Sorry, bugs@ml and pkg-bugs@ml members, for the avalanche.

72 bugs with the "New RPM package request" component, had a severity of "normal" or more, which can lead to losing precious time when searching Bugzilla for bugs that urgently need to get fixed

Now mass-changing that to "enhancement", as it should be for package requests.

https://wiki.mageia.org/en/How_to_report_a_bug_properly#How_to_file_a_package_request

@ the reporter of this package request

Please check in http://madb.mageia.org/ whether this software did already get packaged, and close this bug report if it did.
Please do also close it if you find a package with the same purpose, that meets your needs.

Severity: normal => enhancement


Note You need to log in before you can comment on or make changes to this bug.