[sisuite-users] RHEL-9 (AmlaLinux-9) support added.

[LAHAYE Olivier]

Hi,

RHEL-9 (thru AlmaLinux-9 build) support added.

Packages available here: 
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/rhel-9-x86_64

Quick Start Guide available here:
https://github.com/finley/SystemImager/wiki/QuickStartGuide

--
Olivier LAHAYE

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New builds for Debian 10 & 11, RHEL 7 & 8

[LAHAYE Olivier]

Hi,

Small notice to inform that New SystemImager builds are available.
Now Debian builds are available here: 
http://olivier.lahaye1.free.fr/OSCAR/repos/

Quick start guide available here as usual:
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Cheers,

Olivier.

--
Olivier LAHAYE

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New systemimager build and new distros supported!

[LAHAYE Olivier]

Hi,

Small notice to inform that new SystemImager build has been made available for 
the following distributions:

  *   AlmaLinux-8 (and all RHEL-8 compatible distros)
  *   CentOS-7
  *   Debian-10 (amd64)
  *   Debian-11 (amd64)
  *   Open SuSE-15

As You can see, Debian is finally supported again.

As usual, this is a “work in progress”. Rsync transfer method works fine and 
most command as well.
The web interface replaces the old tk monitor interface, though the web console 
is ultra slow and needs rewrite (click wait response when the brower ask to 
stop waiting for the page rendering). It a take a few minutes. This problem 
will be fixed later.

The repositories have moved here:
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/

The Quick Start Guide has been updated and is available here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Happy deployments.

--
Olivier LAHAYE

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] SystemImager (NG) v4.9.0 status

[LAHAYE Olivier]

Hi all,

Small notice to tell that SystemImager-NG is still progressing.

  *   Can be installed on UEFI system and imaged from UEFI PXE
  *   Supports systemd-boot (basic stuff)
  *   Make sure /etc/default/grub and /etc/system-id are specific to installed 
system
  *   Supports for external drivers (e.g. megaraid_sas with old hardware 
support enabled)
  *   Supports for initramfs with native NetworkManager (default since RHEL-8.3)
  *   Had many bug fixes and imager code hardening.

Packaging for RHEL-8 is now done using AlmaLinux-8 instead of CentOS-8

I’ll do some tests for CentOS-7, AlmaLinux-8, OpenSuse-13 and release rpms for  
RHEL-7 like, RHEL-8 like, SuSE-13 like.

Packaging for Debian like is not ready, sorry, I have no time for that now. 
(though, there are chance that a make install DESTDIR=/usr may work somehow 
(don’t do that on something that is not a test system as result is unknown))

Regards,

Olivier.

--
Olivier LAHAYE
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Centos 7 Stable Repo without packages

[LAHAYE Olivier]

Hi Daniele,

Yes, the repo has been fixed with new build (20201106)
I’ve updated the quick start guide available here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide
Keep in mind that this is experimental. (though, this is the only working 
version for CentOS-7 and CentOS-8).

When doing the si_prepareclient, you may have some errors displayed regarding 
the systemconfig conf generation. Ignore this, this is deprecated.
If si_prepareclient is successful, you should see a rsyncd daemon running with 
systemimager temporary file.

Happy testing.

Cheers.

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : lundi 16 novembre 2020 à 11:43
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : Re: [sisuite-users] Centos 7 Stable Repo without packages

Hi Oliver,
I hope all is well, are there some good news about repo fix ?
Thank you.

D.

Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
Le informazioni contenute in questo messaggio sono riservate e confidenziali. 
Si esorta il destinatario della presente al rispetto degli obblighi in materia 
di trattamento dei dati personali ex REG: UE n.679/2016
The information contained in this message are confidential and privileged. The 
recipient of this message is urged to respect the obligations on personal data 
processing as ex REG: UE n.679/2016


From: LAHAYE Olivier 
Reply to: "sisuite-users@lists.sourceforge.net" 

Date: Tuesday, 10 November 2020 at 10:25
To: "sisuite-users@lists.sourceforge.net" 
Cc: "Mirco Pinetti (E4)" 
Subject: Re: [sisuite-users] Centos 7 Stable Repo without packages


Hi Daniele,

I made a new build, but it seems that there is an issue on the repo site. I’ll 
try to fix that ASAP.

Best regards,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : mardi 10 novembre 2020 à 09:47
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : Re: [sisuite-users] Centos 7 Stable Repo without packages

Hi,
   the good news is that I can test the SI suite also with CentOS 8 and not 
only the 7.
Are there some news about the Centos 7 – 8 repos ?

Thank you

D.

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Centos 7 Stable Repo without packages

[LAHAYE Olivier]

Hi Daniele,

I made a new build, but it seems that there is an issue on the repo site. I’ll 
try to fix that ASAP.

Best regards,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : mardi 10 novembre 2020 à 09:47
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : Re: [sisuite-users] Centos 7 Stable Repo without packages

Hi,
   the good news is that I can test the SI suite also with CentOS 8 and not 
only the 7.
Are there some news about the Centos 7 – 8 repos ?

Thank you

D.

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Centos 7 Stable Repo without packages

[LAHAYE Olivier]

Hi,

The problem is that you’re not using the correct repo (this one is not up to 
date; it’ll host stable releases)
You should follow the QuickStart Guide here:
https://github.com/finley/SystemImager/wiki/QuickStartGuide (especially the 
Migration paragraph if you already have an old systemimager install)
Keep in mind that this is a development (git branch SystemImager-NG) version 
(stable version won’t work on current OS releases (the last stable only 
supports CentOS-6 if I’m correct).

There is a known issue in si_prepareclient and si_getimage that is fixed in 
GIT. I’ll release a build today if I can.

I’ve successfully tested image creation and deployment on CentOS-7 and CentOS-8.

Note: you can start to follow the guide. You’ll be stopped at si_prepareclient. 
At that step, wait for new build and update and continue the guide.

Best regards,

Olivier.


De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 6 novembre 2020 à 09:36
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : [sisuite-users] Centos 7 Stable Repo without packages

Hi all,
I tried to follow the on line guide to install system Imger on Centos, so I 
create the stable repo:

# cat /etc/yum.repos.d/systemimager.org-stable.repo
[systemimager-stable]
name=SystemImager (stable)
baseurl=https://dl.bintray.com/systemimager/rpms/el7/$basearch/
gpgcheck=0
enabled=1

This repo is enabled:

# yum  repolist enabled
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.tugraz.at
* epel: fedora.westmancom.com
* extras: centos.anexia.at
* updates: ftp.tugraz.at
repo id 
repo name   
status
base/7/x86_64   
CentOS-7 - Base 
10,070
e4utils 
e4utils 
31
epel/x86_64 
Extra Packages for Enterprise Linux 7 - x86_64  
13,465
extras/7/x86_64 
CentOS-7 - Extras   
   413
systemimager-stable/x86_64  
SystemImager (stable)   
   157
updates/7/x86_64
CentOS-7 - Updates  
 1,134
repolist: 25,270

but when I try to install the SI rpm I have this error:

#yum -y install systemimager-server dracut-systemimager 
systemimager-initrd_template systemimager-common 
systemimager-x86_64boot-standard systemimager-doc systemimager-client
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.tugraz.at
* epel: mirror.rnet.missouri.edu
* extras: centos.anexia.at
* updates: ftp.tugraz.at
No package systemimager-server available.
No package dracut-systemimager available.
No package systemimager-initrd_template available.
No package systemimager-common available.
No package systemimager-x86_64boot-standard available.
No package systemimager-doc available.
No package systemimager-client available.
Error: Nothing to do

What am I doing wrong?

How can I fix it?

Thank you.

D.



Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
e. daniele.greg...@e4company.com  w. 
www.e4company.com
m. +39 346 6000 787  p. +39 0522 99 18 27   s. daniele.e4company
WHEN PERFORMANCE MATTERS
LinkedIn   |   
Twitter   |   
YouTube

Disclaimer:
Ai sensi e per gli effetti del Regolamento Europeo GDPR n. 679/2016, le 
informazioni contenute in questo messaggio sono riservate e confidenziali. Il 
loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le 
finalità indicate nello stesso. Ai sensi dell'art. 616 c.p e del REG:UE 
679/2016 i comportamenti che portano alla diffusione, distribuzione e/o 
copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal 
destinatario, costituiscono illecito penale e sono passibili di sanzione 
amministrativa. Pertanto, qualora Lei non fosse il destinatario del presente 
messaggio, La invitiamo ad eliminarlo dal Suo sistema ed a distruggere le 
eventuali copie o stampe, fornendo allo scrivente pronta 

[sisuite-users] New SystemImager -NG build (20201009)

[LAHAYE Olivier]

Hi,

A news SystemImager NG) build (still a development status) has been released 
for CentOS-7 and CentOS-8
This is build 4.9.0-0.20201009git

Only minor fixes. Mainly si_prepareclient fixes that avoid failing if no swap 
partition is found (image created from a container).
Note: Known issue: before using si_prepareclient, you have to copy 
/etc/systemimager/systemimager.json from server to golden client. This’ll be 
fixed in an upcoming build.

Note: The disk layout was previously created as 
/etc/systemimager/systemimager.conf. It is now created as 
/etc/systemimager/disks-layout.xml
This file need to be copied from the image or from the golden client to 
/var/lib/systemimager/scripts/disks-layouts/.xml (or clientname.xml, 
…) (this file will later be handled by si_getimage)
This file is yet incomplete as it lacks bootloader section. Please edit this 
file and add missing sections before trying to deploy.

Builds will be soon available here: 
http://www.usablesecurity.net/OSCAR/repos/unstable/

Quick start guide here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide (updated)

Best regards,

--
Olivier LAHAYE
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

[LAHAYE Olivier]

Hi,

Sorry, I didn’t noticed that my answer was stuck in my outbox.
The is no fix yet, but there is IMHO a workaround.

Can you try to copy /etc/systemimager/systemimager.json from the server to the 
golden client.
This should fix the issue.

This version is still in development, so there are the kind of issues that can 
be expected.

Beswt regards.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 9 octobre 2020 à 14:58
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi,
   Any news about the fix?

Thanks

Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
Le informazioni contenute in questo messaggio sono riservate e confidenziali. 
Si esorta il destinatario della presente al rispetto degli obblighi in materia 
di trattamento dei dati personali ex REG: UE n.679/2016
The information contained in this message are confidential and privileged. The 
recipient of this message is urged to respect the obligations on personal data 
processing as ex REG: UE n.679/2016


From: LAHAYE Olivier 
Reply to: "sisuite-users@lists.sourceforge.net" 

Date: Friday, 2 October 2020 at 16:02
To: "sisuite-users@lists.sourceforge.net" 
Subject: Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

This is the lastest version, so I need to investigate, I though the fix was in 
the latest release.
I’ll try to publish a fix, but I’m unsure I can do that before next Wednesday 
(won’t have access to test environment).

I’ll fix that and inform new build here.

Cheers,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 2 octobre 2020 à 15:49
À : "sisuite-users@lists.sourceforge.net" 
Objet : Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi Oliver,
   here the version:

[root@wn01 greg]# rpm -qa |grep systemimager
systemimager-webgui-4.9.0-0.20200601git.el8.noarch
systemimager-initrd_template-4.9.0-0.20200601git.el8.noarch
systemimager-server-4.9.0-0.20200601git.el8.noarch
systemimager-x86_64boot-standard-4.9.0-0.20200601git.el8.noarch
systemimager-common-4.9.0-0.20200601git.el8.noarch
dracut-systemimager-4.9.0-0.20200601git.el8.noarch
systemimager-client-4.9.0-0.20200601git.el8.noarch
[root@wn01 greg]# uname -a
Linux wn01 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul 26 03:54:29 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
[root@wn01 greg]# cat /etc/redhat-release
CentOS Linux release 8.2.2004 (Core)


Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
Le informazioni contenute in questo messaggio sono riservate e confidenziali. 
Si esorta il destinatario della presente al rispetto degli obblighi in materia 
di trattamento dei dati personali ex REG: UE n.679/2016
The information contained in this message are confidential and privileged. The 
recipient of this message is urged to respect the obligations on personal data 
processing as ex REG: UE n.679/2016


From: LAHAYE Olivier 
Reply to: "sisuite-users@lists.sourceforge.net" 

Date: Friday, 2 October 2020 at 14:51
To: "sisuite-users@lists.sourceforge.net" 
Subject: Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi Daniele,

Which version are you using ?

Cheers,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 2 octobre 2020 à 14:48
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi,
   I’m trying SI and I follow the quick start guide, from the client side I 
received this error message:

# si_prepareclient  --server 192.168.1.250
malformed JSON string, neither array, object, number, string or atom, at 
character offset 0 (before "(end of string)") at 
/usr/share/perl5/vendor_perl/SystemImager/JConfig.pm line 181.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
Compilation failed in require at /usr/sbin/si_prepareclient line 83.
BEGIN failed--compilation aborted at /usr/sbin/si_prepareclient line 83.

Do you have any hint to solve this?

Thank you

Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
e. daniele.greg...@e4company.com<mailto:daniele.greg...@e4company.com>  w. 
www.e4company.com<https://www.e4company.com/>
m. +39 346 6000 787  p. +39 0522 99 18 27   s. daniele.e4company
WHEN PERFORMANCE MATTERS
LinkedIn<https://www.linkedin.com/company/e4-computer-engineering-spa>   |   
Twitter<https://twitter.com/

Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

[LAHAYE Olivier]

This is the lastest version, so I need to investigate, I though the fix was in 
the latest release.
I’ll try to publish a fix, but I’m unsure I can do that before next Wednesday 
(won’t have access to test environment).

I’ll fix that and inform new build here.

Cheers,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 2 octobre 2020 à 15:49
À : "sisuite-users@lists.sourceforge.net" 
Objet : Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi Oliver,
   here the version:

[root@wn01 greg]# rpm -qa |grep systemimager
systemimager-webgui-4.9.0-0.20200601git.el8.noarch
systemimager-initrd_template-4.9.0-0.20200601git.el8.noarch
systemimager-server-4.9.0-0.20200601git.el8.noarch
systemimager-x86_64boot-standard-4.9.0-0.20200601git.el8.noarch
systemimager-common-4.9.0-0.20200601git.el8.noarch
dracut-systemimager-4.9.0-0.20200601git.el8.noarch
systemimager-client-4.9.0-0.20200601git.el8.noarch
[root@wn01 greg]# uname -a
Linux wn01 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul 26 03:54:29 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
[root@wn01 greg]# cat /etc/redhat-release
CentOS Linux release 8.2.2004 (Core)


Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
Le informazioni contenute in questo messaggio sono riservate e confidenziali. 
Si esorta il destinatario della presente al rispetto degli obblighi in materia 
di trattamento dei dati personali ex REG: UE n.679/2016
The information contained in this message are confidential and privileged. The 
recipient of this message is urged to respect the obligations on personal data 
processing as ex REG: UE n.679/2016


From: LAHAYE Olivier 
Reply to: "sisuite-users@lists.sourceforge.net" 

Date: Friday, 2 October 2020 at 14:51
To: "sisuite-users@lists.sourceforge.net" 
Subject: Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi Daniele,

Which version are you using ?

Cheers,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 2 octobre 2020 à 14:48
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi,
   I’m trying SI and I follow the quick start guide, from the client side I 
received this error message:

# si_prepareclient  --server 192.168.1.250
malformed JSON string, neither array, object, number, string or atom, at 
character offset 0 (before "(end of string)") at 
/usr/share/perl5/vendor_perl/SystemImager/JConfig.pm line 181.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
Compilation failed in require at /usr/sbin/si_prepareclient line 83.
BEGIN failed--compilation aborted at /usr/sbin/si_prepareclient line 83.

Do you have any hint to solve this?

Thank you

Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
e. daniele.greg...@e4company.com<mailto:daniele.greg...@e4company.com>  w. 
www.e4company.com<https://www.e4company.com/>
m. +39 346 6000 787  p. +39 0522 99 18 27   s. daniele.e4company
WHEN PERFORMANCE MATTERS
LinkedIn<https://www.linkedin.com/company/e4-computer-engineering-spa>   |   
Twitter<https://twitter.com/e4company>   |   
YouTube<https://www.youtube.com/user/e4company/videos>

Disclaimer:
Ai sensi e per gli effetti del Regolamento Europeo GDPR n. 679/2016, le 
informazioni contenute in questo messaggio sono riservate e confidenziali. Il 
loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le 
finalità indicate nello stesso. Ai sensi dell'art. 616 c.p e del REG:UE 
679/2016 i comportamenti che portano alla diffusione, distribuzione e/o 
copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal 
destinatario, costituiscono illecito penale e sono passibili di sanzione 
amministrativa. Pertanto, qualora Lei non fosse il destinatario del presente 
messaggio, La invitiamo ad eliminarlo dal Suo sistema ed a distruggere le 
eventuali copie o stampe, fornendo allo scrivente pronta comunicazione.
Disclaimer:
Pursuant and for the effects of European regulation GDPR n.679/2016, the 
information contained in this message are confidential and privileged. Their 
use is allowed only for the intended recipient of this e-mail, for the finality 
indicated in the same. Pursuant and for the effects of art. 616 c.p. and REG:UE 
679/2016, the behaviour that leads at diffusion, distribution and/or copying of 
the documents, transmitted from subjects different from recipients, will 
constitute a penal crime and could be object of administrative sanctions. 
Therefore, if you are not the intended recipient of 

Re: [sisuite-users] Trouble with CentOS8 client si_prepareclient

[LAHAYE Olivier]

Hi Daniele,

Which version are you using ?

Cheers,

Olivier.

De : "Daniele Gregori (E4)" 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : vendredi 2 octobre 2020 à 14:48
À : "sisuite-users@lists.sourceforge.net" 
Cc : "Mirco Pinetti (E4)" 
Objet : [sisuite-users] Trouble with CentOS8 client si_prepareclient

Hi,
   I’m trying SI and I follow the quick start guide, from the client side I 
received this error message:

# si_prepareclient  --server 192.168.1.250
malformed JSON string, neither array, object, number, string or atom, at 
character offset 0 (before "(end of string)") at 
/usr/share/perl5/vendor_perl/SystemImager/JConfig.pm line 181.
Compilation failed in require at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
BEGIN failed--compilation aborted at 
/usr/share/perl5/vendor_perl/SystemImager/UseYourOwnKernel.pm line 27.
Compilation failed in require at /usr/sbin/si_prepareclient line 83.
BEGIN failed--compilation aborted at /usr/sbin/si_prepareclient line 83.

Do you have any hint to solve this?

Thank you

Daniele Gregori, PhD •  Head of Engineering – Scientific Coordinator
E4 COMPUTER ENGINEERING Spa
e. daniele.greg...@e4company.com  w. 
www.e4company.com
m. +39 346 6000 787  p. +39 0522 99 18 27   s. daniele.e4company
WHEN PERFORMANCE MATTERS
LinkedIn   |   
Twitter   |   
YouTube

Disclaimer:
Ai sensi e per gli effetti del Regolamento Europeo GDPR n. 679/2016, le 
informazioni contenute in questo messaggio sono riservate e confidenziali. Il 
loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le 
finalità indicate nello stesso. Ai sensi dell'art. 616 c.p e del REG:UE 
679/2016 i comportamenti che portano alla diffusione, distribuzione e/o 
copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal 
destinatario, costituiscono illecito penale e sono passibili di sanzione 
amministrativa. Pertanto, qualora Lei non fosse il destinatario del presente 
messaggio, La invitiamo ad eliminarlo dal Suo sistema ed a distruggere le 
eventuali copie o stampe, fornendo allo scrivente pronta comunicazione.
Disclaimer:
Pursuant and for the effects of European regulation GDPR n.679/2016, the 
information contained in this message are confidential and privileged. Their 
use is allowed only for the intended recipient of this e-mail, for the finality 
indicated in the same. Pursuant and for the effects of art. 616 c.p. and REG:UE 
679/2016, the behaviour that leads at diffusion, distribution and/or copying of 
the documents, transmitted from subjects different from recipients, will 
constitute a penal crime and could be object of administrative sanctions. 
Therefore, if you are not the intended recipient of this message, please delete 
it from your system and destroy all copies or prints, providing to the sender a 
prompt communication.

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] SystemImager-NG build 20200525 supports CentOS-6.X CentOS-7.X CentOS-8.X and openSuSE-Leap-15.2

[LAHAYE Olivier]

Hi every one,

I hope all of you are fine during this Covid crisis.

Development of the new SystemImager was not stopped, and after days of hacking, 
finding bugs in Plymouth and in distro packaging, I’ve finally succeeded in 
porting SystemImager (next gen) to CentOS-8.1 and to openSUSE-Leap 15.2)

There is still lot of work before final stable release, but this release is 
already functional (I use it to deploy my CentOS-8 OSCAR Cluster).

Reminder: this SystemImager supports:

  *   CentOS-6 to CentOS-8.1, openSUSE Leap 12.2 (maybe other openSUSE and most 
Fedora distros)
  *   UEFI Bios
  *   UEFI grub2 installation (clover and reFind not yet supported but hooks in 
code are present)
  *   All storage devices and filesystems supported by distro vendor
  *   Raid, lvm, raid+lvm, …
  *   No need for a main script (disk detection, partitioning, formatting, 
mounting, bootloader install, … is handled by SystemImager logic). Mainscript 
is still supported (if you want to setup a mountpoint, some nfs stuffs, or any 
other things not handled by SystemImager logic)
  *   Web console
  *   Imager graphical GUI based on plymouth
  *   …

Builds will be soon available here: 
http://www.usablesecurity.net/OSCAR/repos/unstable/

Quick start guide here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Sorry, no up to date Debian/ubuntu packaging. SystemImager should be buildable 
for those distros provided dracut and dracut-network can be installed aside 
initramfs-tools (./configure; make install DESTDIR=/usr. WARNING, doing so will 
“pollute your system”, thouth other DESTDIR have not been tested and I doubt 
they are functional especially for web stuffs) but regarding packaging, a lot 
of work is still needed (mainly dependencies that needs to be backported)

Happy testing.

PS:  if you rebuild your initrd, the result will not work on openSUSE-15.2:

  *   dracut module 35network-legacy fails to run initqueue/online hook if 
network is brought up with dhcp: Imager fails in initqueue mainloop with 
timeout because online hook is never run.
  *   PlymouthGUI won’t show up on qemu / bochs / … due to a bad openSUSE patch 
that tries to manage DRM devices while it shouldn’t anymore.

--
Olivier LAHAYE
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New SystemImager Build.

[LAHAYE Olivier]

Dear developers and curious testers,

A new build of SystemImager is available for CentOS-6, CentOS-7, CentOS-8 and 
openSUSE-42 (build 20191219)
Soon available here: http://www.usablesecurity.net/OSCAR/repos/unstable/
(Available for 7 days here: 
ftp://ftp.cea.fr/incoming/y2k01/OSCAR/repos/unstable/)

This build has the new logging mechanism and a web interface with main menu, 
client list and web live console(s), system checks and systemimager 
configuration panel.
Note: the 3 icons at bottom of the main menu are not yet implemented (stubs for 
now).

The Quick start guide is updated and reflect current build.
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Happy testing.

--
Olivier LAHAYE
CEA  Saclay

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New Systeimager development build with new features.

[LAHAYE Olivier]

Hi,

A new SystemImager build is available  4.9.0-0.20190705git
See https://github.com/finley/SystemImager/wiki/QuickStartGuide for 
Installation and Migration guide from v4.1.6 and earlier. (make sure it is 
20190705 build when installing; sometime, web cache show older build)

Basically, new features are:

  *   Now, SystemImager is able to configure network (man 
systemimager.network-config). If config file is missing, systemimager will just 
configure the PXE booted interface.
  *   Fixed many small issues
  *   Now imager log will list imager version, kernel version and distro flavor 
in logs.
  *   Directboot now works fine on both centos-7 and centos-6.

Happy testing.

--
Olivier LAHAYE
CEA Saclay

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] Call for Ideas and Help for systemimager development and enhancements.

[LAHAYE Olivier]

Dear users and developers,

SystemImager is in heavy development right now, but as I’m alone on this 
development, progress is slower than I wish.

Some features are hard to maintain in term of OS compatibility and one of them 
is the remote console (using si_monitortk and clicking on a host being deployed)
This console depends on an ANSI Color Tk text widget I need to package and that 
may not be maintained in the future.
I also have a problem with refresh that hangs depending on netcat/nc/ncat 
versions that use different console switches.

For now, the remote console has the following problems:

  *   Can’t see the console log of a NATed client being imaged
  *   Can’t see the console log if the client imaging is finished
  *   Can’t see multiple consoles at a time
  *   Can’t filter logs (select only errors or only warnings for example)
  *   Logs stays on client and needs to be transferred by hand if one want to 
share it
  *   Based on perl/Tk with depedancy to TkTermANSIColor that is not packaged 
in distros
  *   Has problems with some ncat versions (nc, ncat multiple versions, netcat) 
(sockets timeout, hangs if input timeout (filesystem init too long, …)
  *   Requires an X display to start si_monitortk
  *   Requires to connect to image server to start si_monitortk

IMHO, a really cool feature would be to add a web interface to image server 
with the following features:

  *   Hosts statuses (si_monitortk main window replacement)
  *   Console log (with page auto-refresh for update)
  *   Info page with general setup
  *   HTML Online Doc
  *   PXE config
  *   More?

I think XSL and PHP would be the most timeline stable languages to create the 
web interface (other are constantly upgrading and obsoleting features and need 
port every 2 years or so with tons of libraries with v0.0.1 versions that die 
and become incompatible quickly)
/var/lib/systemimager/clients.xml which contains the client informations is in 
xml format, thus xsl is well suited to transform it to HTML…

Regarding the log storage daemon, I don’t know what would be the best, but as 
systemimagers is mainly based on perl and bash, I support perl would be the 
language of choice as bash would depend on nc/ncat/netcat that I want to avoid 
at any cost as behavior is inconsistent across distros and versions.

What do you think? Ideas and/or help is welcome 

Cheers,

Olivier.

--
   Olivier LAHAYE
   SystemImager v5 active developer.
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] SystemImager on LVM

[LAHAYE Olivier]

Hi Ozkan,

Systemimager-4.0.5 won’t work on any RHEL-7 based distros (RHEL-7, CentOS-7, 
ScientificLinux-7, Oracle Linux 7,) and generally won’t work on recent hardware 
as it was built long ago when some of recent hardware did not exists and thus, 
the booting kernel will not have the correct drivers.
If you use your own kernel, this can help start the imaging process, but you’ll 
hit other problems related to OS configuration (RHEL-7 uses systemd and 
NetworkManager for example which did not exists when systemimager-4.0.5 was 
build).

I strongly suggest to use latest beta builds from here: 
http://www.usablesecurity.net/OSCAR/repos/unstable/rhel-7-x86_64/

Configure the repository by issuing the following command:
rpm -ivh 
http://www.usablesecurity.net/OSCAR/repos/unstable/rhel-7-x86_64/oscar-release-6.1.3-0.20190513.el7.noarch.rpm

Then follow the systemimager quick start guide available here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

If you’re familiar with systemimager, this brand new design while introducing 
big changes should be easy to setup anyway.
This is still tagged as beta as only rsync protocol works, but the imaging 
process is already fairly robust on rhel-7 and now rhel-6.

Once I’ll have access to RHEL-8, I’ll do a build and I’m almost convinced it’ll 
work out of the box as it already works out of the box for fedora-26..30.

If you need further assistance, don’t hesitate to post here, I read it often 
and try to give answers to problems.

The current stable beta is version 4.9.0-0.20190702git if main repo is not up 
to date (it is not while I write this mail), you can find latest build here:
ftp://ftp.cea.fr/incoming/y2k01/OSCAR/repos/unstable/rhel-7-x86_64/ (this is a 
temporary repo that is cleared every 7 days, so do set it up for any other 
purpose that temporary need).

Cheers,

Olivier.


De : ozkan oksuz via sisuite-users 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : mardi 2 juillet 2019 à 15:10
À : ozkan oksuz via sisuite-users 
Cc : ozkan oksuz 
Objet : Re: [sisuite-users] SystemImager on LVM

Hi,

We are planning to install systemimager 4.0.2 server  on Oracle Linux 7.6.And 
hope to get our client images which are also Oracle Linux 7.6.
What we want to know if there is any technical limitations for this kind of 
setup?Will it work?What I mean is that can we just install the systemimager 
4.0.2 and clients packages on Oracle Linux 7.6?

Best Regards
Thanks

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New system imager v5 pre build with new functionalities.

[LAHAYE Olivier]

Hi,

A new build has been released for centos-6 and centos-7.

The new feature is that now, the network is setup by imaged from the network 
layout configuration file. This means that you don’t need a post-install script 
to setup the imaged client network.

The quick start guide has been updated here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Note: that the old repository has been replaced by a new one listed in the 
quick start guide.

Happy testing.

--
Olivier LAHAYE

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New system imager test build with network configuration support.

[LAHAYE Olivier]

Hi,

Small message to inform the community that a new systemimager build 
(4.9.0-0.20190402git) introduce a major enhancement: the client network 
configuration.
This configuration supports most common network usages:

  *   Ipv4/ipv6 support (ipv6 support is basic)
  *   Ethernet and Infiniband device support
  *   Aliases support (still not loading on NetworkManager controlled 
interfaces)
  *   Bonding support

Doc not yet written but a fairly complete example is available here:
https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/net-config.xml

All available options are described here: 
https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/51systemimager/network-config.xsd

Your network configuration file should be placed in 
/var/lib/systemimager/scripts/network-configs/ on the image server and be named 
in the same way disks layout (.xml extention is optional). (example: 
imagename.xml or hostname.xml or default.xml ….)

To validate your network configuration (before trying to image your client) 
just type the following command (on the image server):

si_lint –network-config=myimage.xml
where myimage.xml is your network configuration file.
(don’t provide full path)

There are still issues with aliases and NetworkManager (not loaded), but aside 
that everything seems working.

Happy testing.

--
Olivier LAHAYE
CID & ASSI - DRT Saclay

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New systemimager beta build (4.9.0-0.20190321git.el7)

[LAHAYE Olivier]

Today build add a new server command: si_lint.

This command aims to check the client configuration (disks layout, config file, 
….)
The aim is to check everything before trying to image a client and discover a 
client configuration problem.

As of today, only disks layout check is available:

si_lint --disks-layout=

  *   Layout file is searched in /var/lib/systemimager/scripts/disks-layout/
or

si_lint --disks-layout=*.xml

  *   This will check all disks layout

This new build also include preliminary support for imaged client network 
configuration (not enabled yet)

This build is only available for centos7. (build for other systems will be done 
next week or so)

The Quick start guide has also been updated.
It is available here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Happy testing.

--
Olivier LAHAYE
CEA Saclay

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] SystemImager on LVM

[LAHAYE Olivier]

Hi Ozkan,

I’m replying on the user list so the answer may benefit other people. (and 
there is no private stuff in your reply)

As stated before, I suggest to inspect the file: //etc/autoinstallscript.conf onb the server
This xml file describes the original disk partitioning.
From this file, the main install script has been generated.
This mail install script will try to create the partitions using fdisk or 
parted. Those commands are not very respectfull of exact requested size (if you 
request a 4 blocks partition, fdisk will create a 5 blocks partition for 
example).
As your backup did store the size in floating MB rounded, it is possible that 
you miss space by one or two blocks (if you’re using the same disk).

Please:
1/ inspect you install script (the partition creation section)
2/ Check where it fails (the partitioning command that fails)
3/ Try to put 100% or 0 instead of size for this command to tell to use all the 
space left. If it misses one or two block it’s not impacting for the 
restoration process.

Also make sure that the disk you’re trying to restore is at least the same size 
or bigger than the disk you did backup.

Another solution could be to setup a centos-7 server, move the centos-5 backup 
there and try to restore the centos-5 system using a centos-7 initrd imager 
(with the si.post-action=reboot). The only problem is that I’m not sure about 
boot loader setup (may work as grub1 is supported) and all virtual filesystem 
(/dev, /proc, …). You may need to write some post-install scripts to update the 
fstab with those.

Best regards,

Olivier.


De : ozkan oksuz 
Date : jeudi 21 mars 2019 à 12:52
À : LAHAYE Olivier 
Objet : Re: [sisuite-users] SystemImager on LVM


Hi Olivier

Thank you very much for the information you provide.


We have no choice but to work with Rhel 5.

With systemimager we got backups over the network. When we wanted to restore it 
again, there was a problem due to LVM. We've got a backup again, but we haven't 
restored it yet.

Best Regards.





14 Mart 2019 Perşembe 18:39:31 GMT+3 tarihinde, LAHAYE Olivier 
şunu yazdı:



Hi Ozkan,



RHEL-5 is a so old distro that is even not supported by redhat if I’m correct.

So I’m not sure I can help you on that point.



What are you trying to do when you speak of “backup”? Do you mean imaging an 
lvm system with an image created with si_getimage?



There is a brand new beta version that work on all dracut based systems 
starting from rhel-6 (thus rhel-7, suse-42.3 and upcoming, fedora-27+, and soon 
Debian 8 and 9 (works but package is incomplete). Unfortunately, it can’t build 
on rhel-5 that lack dracut package.



Seeing the error you provide, I would suggest to inspect //etc/autoinstallscript.conf (to check the disk structure) and 
compare that with the matching autoinstall script that would create the lvm 
volumes.



Cheers,



Olivier.





De : ozkan oksuz via sisuite-users 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : jeudi 14 mars 2019 à 07:26
À : "sisuite-users@lists.sourceforge.net" 
Cc : ozkan oksuz 
Objet : [sisuite-users] SystemImager on LVM



Hello.

I became a new member of the group.  I'm using Rhel 5.8

server edition. LVM structure. Can I get a backup of the system with

systemimager 4.0.2. Other computers that are not lvm have been backed up. We

can  restore backup, but when installing,

give the following error ( Error : The location 250057.95 is outside of the 
device /dev/sda ).

Thanks for everyting. Regard.
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New systemimager beta build (4.9.0-0.20190320git.el7)

[LAHAYE Olivier]

Hi,

A new systemimager build (4.9.0-0.20190320git.el7) is available for centos-7 / 
rhel-7 distro.
Source: 
https://github.com/finley/SystemImager/tree/initrd-from-imageserver-and-dont-package-initrd

Those who want to test can install it.
See quick start guide here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide for 
download/install/setup/usage.

New in this build (not sorted by importance):

  *   Systemimager-client package. Now you can do si_prepareclient whitout 
needing to install systemimager-server
  *   Systemimager-doc package is splitted from main package so you don’t have 
to install it on all your cluster nodes for example. This also reflect Debian 
packaging.
  *   Debian package vailable but still incomplete (don’t use them yet)
  *   More imager breakpoints (si systemimager.cmdline(7) manual)
  *   systemimager-monitor-rebooted script is now installed by imager. 
Postinstall script is not needed anymore.
  *   New bootloader section in disk-layout.xml file
 *   See example here: 
https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/disk-layout-complex.xml
  *   Bootloader is now installed as described in disk layout file (no more 
post install script required, only installed on designated disks)
  *   Support for EFI bootloader added (rEFInd)
  *   Disks-layout validation using xsd (a si_lint command (to be written) will 
help checking all systemimager configurations)
 *   In the mean time you can check your disk layout file validity using 
the following command:
 *   xmlstarlet val --err --xsd 
/usr/lib/dracut/modules.d/51systemimager/disks-layout.xsd 
/var/lib/systemimager/scripts/disks-layouts/
  *   si_mkbootserver now supports systemd
  *   si_mkbootserver now creates a GFX menu with cool systemimager background 
image (--vesamenu=y|n). (only available on systemd systems).
  *   brand new very smart partitioning code with optimized aligment and sizes 
rounded to next aligment to avoid gaps between partitions. This smart 
partitioning is able to create ‘*’ sized partition between 2 fixed size 
partitions thans to xsl recursive processing.
  *   Smart fstab generator. Line= parameter is ignored.
  *   Enhanced partition flags (efi, PART spécific GUID (linux swap, EFI system 
partition, …))
  *   Many many many bugfixes thanks to David Livingstone patience and heavy 
testing.

Now I’m working on the following stuffs:

  *   Network configuration (xml file; example: 
https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/net-config.xml
  *   Cleanup manuals. Move autoinstallscript.conf to systemimager.disks-layout 
for example
  *   si_lint command to check if client is ready for installation (all 
configurations files are valid, …)
  *   update bootloader section in disk layout file for better EFI 
options/configuration.
  *   Finish Debian packaging (update file list, dependances and post install 
scripts)

Happy testing.

--
Olivier LAHAYE
CEA Saclay

___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] SystemImager on LVM

[LAHAYE Olivier]

Hi Ozkan,

RHEL-5 is a so old distro that is even not supported by redhat if I’m correct.
So I’m not sure I can help you on that point.

What are you trying to do when you speak of “backup”? Do you mean imaging an 
lvm system with an image created with si_getimage?

There is a brand new beta version that work on all dracut based systems 
starting from rhel-6 (thus rhel-7, suse-42.3 and upcoming, fedora-27+, and soon 
Debian 8 and 9 (works but package is incomplete). Unfortunately, it can’t build 
on rhel-5 that lack dracut package.

Seeing the error you provide, I would suggest to inspect //etc/autoinstallscript.conf (to check the disk structure) and 
compare that with the matching autoinstall script that would create the lvm 
volumes.

Cheers,

Olivier.


De : ozkan oksuz via sisuite-users 
Répondre à : "sisuite-users@lists.sourceforge.net" 

Date : jeudi 14 mars 2019 à 07:26
À : "sisuite-users@lists.sourceforge.net" 
Cc : ozkan oksuz 
Objet : [sisuite-users] SystemImager on LVM


Hello.

I became a new member of the group.  I'm using Rhel 5.8

server edition. LVM structure. Can I get a backup of the system with

systemimager 4.0.2. Other computers that are not lvm have been backed up. We

can  restore backup, but when installing,

give the following error ( Error : The location 250057.95 is outside of the 
device /dev/sda ).


Thanks for everyting. Regard.
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] Systemimager NG v4.9.0 (5.0.0-pre) package for Debian 8 done.

[LAHAYE Olivier]

Hi,

Package for latest systemimager (v4.9.0) are available on OSCAR debian 8 repo 
here:
http://svn.oscar.openclustergroup.org/repos/unstable/debian-8-x86_64/

There are untested yet and are likely not working well. (need to see if Dracut 
is not too much broken; fixed i18n broken module, but there may be others)
The package content, the dependencies and most commands are working. What is 
untested is the initrd.img (the imager part)

This is for thoses who are adventurous.

Now working on Debian 9 packaging port.

Then I’ll do tests.

Cheers,

--
Olivier LAHAYE
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] SystemImager Next Generation (v5.0.0-pre): Debian port in progress.

[LAHAYE Olivier]

Hi,

SystemImager  is able to build an initrd imager on debian 8.11 (jessie) which 
will be the oldest supported.
Imaging using this initrd is not yet tested but chances are great that it’ll 
work with few (maybe no) teaks to systemimager dracut module.
Note: lvm2 won’t be supported on this Debian version as it lack the config 
command.

I have a docker file that permit a full build and system installation.

I’m now working on the packaging.

Once working, I’ll port to newer Debian distros.

Regards,

--
Olivier LAHAYE
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] 4.9.0 si_prepareclient error

[LAHAYE Olivier]

Hi David,

Version 4.9.0-20181019git should fix the problem. (si_mkbootpackage was fixed 
but not si_prepareclient). It's now fixed in whole systemimager code.

Though, IMHO, it is not necessary to regenerate initrd image if you're using 
standard centos kernel. The boot_standard package is generated using 
si_mkbootpackage from the build host running up to date distro (el7 version 
7.5.1804 in this situation). It can be usefull if you just updated to a kernel 
version newer than the one available in the boot_standard package and you want 
to run the imaged system without rebooting after imaging.

If you need more help, don't hesitate to post here.

Quick Start Guide (which lists new parameters and features) is available here: 
https://github.com/finley/SystemImager/wiki/QuickStartGuide

Screenshots and videos: https://github.com/finley/SystemImager/wiki/ScreenShots

Regards,

Olivier.

Le 18/10/2018 19:32, « David Livingstone »  a écrit :

Is the list alive ? Any idea about below error ?

Thanks
David

-Original Message-
From: David Livingstone 
Sent: Friday, September 28, 2018 12:04 PM
To: LAHAYE Olivier 
Subject: 4.9.0 si_prepareclient error

Olivier,

 Hello David Livingstone here. Just looking at Systemimager again after 
receiving a number of HPE DL380 gen10 servers and attempting to image RHEL 7.5 
systems.
 Is the sisuite-users@lists.sourceforge.net still the list to send issues 
to ? Is it still active ? 

Regardless via the Oscar repositories I loaded the latest 
systemimager-4.9.0-0.20180717git.el7 packages successfully. Specifics below. 
The issue I get is when running si_prepareclient. I works when I specify 
--no-uyok however it fails otherwise as given below.

Load specifics :
-HPE DL380 gen10 loaded with latest RHEL7.5 x86_64. Ext4 root on sda and no 
lvm.
- Systemimager packages :
systemimager-server-4.9.0-0.20180717git.el7.noarch
systemimager-x86_64initrd_template-4.9.0-0.20180717git.el7.noarch
systemimager-common-4.9.0-0.20180717git.el7.noarch
dracut-systemimager-4.9.0-0.20180717git.el7.noarch
systemimager-x86_64boot-standard-4.9.0-0.20180717git.el7.noarch
systemimager-client-4.9.0-0.20180717git.el7.noarch

Specifically 

   - This works :
[root@rhel-dev2 rh7]# si_prepareclient --server 192.168.81.11 --no-uyok

   - This fails :
[root@rhel-dev2 rh7]# si_prepareclient --server 192.168.81.11

Failure log :

When running : si_prepareclient --server 192.168.81.11 ...
...
...

Using "parted" to gather information about disk:
/dev/sda

find: 
'/lib/modules/3.10.0-862.11.6.el7.x86_64/kernel/drivers/input/joystick/*': No 
such file or directory

Unknown arguments: 3.10.0-862.11.6.el7.x86_64

Usage: /bin/dracut [OPTION]... [ []]

Version: 033-535.el7_5.1

Creates initial ramdisk images for preloading modules

  -h, --help  Display all options

If a [LIST] has multiple arguments, then you have to put these in quotes.

For example:

# dracut --add-drivers "module1 module2"  ...

FAILED: dracut --force --add systemimager --omit dash --no-hostonly 
--no-hostonly-cmdline --no-hostonly-i18n--omit-drivers "ac97_bus 
snd-compress snd-hrtimer snd-timer snd-hwdep snd-pcm snd snd-seq-midi-event 
snd-seq snd-seq-dummy snd-seq-midi-emul snd-seq-midi snd-seq-oss 
snd-seq-virmidi snd-rawmidi snd-seq-device snd-dummy snd-opl3-synth 
snd-opl3-lib snd-vx-lib snd-aloop snd-mpu401 snd-mpu401-uart snd-pcsp 
snd-virmidi snd-mtpav snd-firewire-lib snd-isight snd-scs1x 
snd-firewire-speakers snd-hda-core snd-hda-ext-core snd-tea575x-tuner 
snd-ak4114 snd-pt2258 snd-ak4xxx-adda snd-ak4113 snd-i2c snd-cs8427 snd-via82xx 
snd-emu10k1-synth snd-emu10k1 snd-emu10k1x snd-trident snd-atiixp snd-hdsp 
snd-hdspm snd-rme9652 snd-intel8x0m snd-echo3g snd-indigodj snd-darla24 
snd-layla20 snd-gina20 snd-indigoiox snd-gina24 snd-darla20 snd-mona 
snd-indigodjx snd-indigoio snd-indigo snd-layla24 snd-mia snd-intel8x0 
snd-rme32 snd-maestro3 snd-korg1212 snd-ice17xx-ak4xxx snd-ice1712 snd-ice1724 
snd-ac97-codec snd-vx222 snd-cs46xx snd-au8830 snd-au8810 snd-au8820 
snd-oxygen-lib snd-oxygen snd-virtuoso snd-mixart snd-ens1371 snd-atiixp-modem 
snd-ali5451 snd-via82xx-modem snd-hda-codec-analog snd-hda-codec-cmedia 
snd-hda-codec-cirrus snd-hda-codec-idt snd-hda-codec-realtek snd-hda-codec-hdmi 
snd-hda-codec-ca0132 snd-hda-codec-conexant snd-hda-codec-si3054 snd-hda-codec 
snd-hda-codec-via snd-hda-intel snd-hda-codec-generic snd-hda-codec-ca0110 
snd-lx6464es snd-pcxhr snd-cmipci snd-rme96 snd-ctxfi snd-asihpi snd-bt87x 
snd-ca0106 snd-ens1370 snd-lola snd-ad1889 snd-es1968 snd-soc-sst-acpi 
snd-soc-sst-ipc snd-soc-sst-dsp snd-soc-sst-match snd-soc-sst-firmware 
snd-soc-skl-ipc snd-soc-skl snd-soc-

Re: [sisuite-users] 4.9.0 si_prepareclient error

[LAHAYE Olivier]

Hi,

Yes, the list is alive.

I think that this error was fixed in latest snapshot, but apparently it's not 
I'll investigate ASAP.
The "No such file or directory" is not important (normal/expected) and is from 
Dracut, I'll try to hide it lated as it's not relevant
The problem here is that Dracut doesn't understand the kernel version argument. 
In fact behavior changed across Dracut versions about that, but adding the kver 
in Dracut cmdline should fix it.

I'll look at that soon to check it is fixed in git; if. Not I'll fix it.

Aside that, were you able to use it?

Olivier.


Le 18/10/2018 19:32, « David Livingstone »  a écrit :

Is the list alive ? Any idea about below error ?

Thanks
David

-Original Message-
From: David Livingstone 
Sent: Friday, September 28, 2018 12:04 PM
To: LAHAYE Olivier 
Subject: 4.9.0 si_prepareclient error

Olivier,

 Hello David Livingstone here. Just looking at Systemimager again after 
receiving a number of HPE DL380 gen10 servers and attempting to image RHEL 7.5 
systems.
 Is the sisuite-users@lists.sourceforge.net still the list to send issues 
to ? Is it still active ? 

Regardless via the Oscar repositories I loaded the latest 
systemimager-4.9.0-0.20180717git.el7 packages successfully. Specifics below. 
The issue I get is when running si_prepareclient. I works when I specify 
--no-uyok however it fails otherwise as given below.

Load specifics :
-HPE DL380 gen10 loaded with latest RHEL7.5 x86_64. Ext4 root on sda and no 
lvm.
- Systemimager packages :
systemimager-server-4.9.0-0.20180717git.el7.noarch
systemimager-x86_64initrd_template-4.9.0-0.20180717git.el7.noarch
systemimager-common-4.9.0-0.20180717git.el7.noarch
dracut-systemimager-4.9.0-0.20180717git.el7.noarch
systemimager-x86_64boot-standard-4.9.0-0.20180717git.el7.noarch
systemimager-client-4.9.0-0.20180717git.el7.noarch

Specifically 

   - This works :
[root@rhel-dev2 rh7]# si_prepareclient --server 192.168.81.11 --no-uyok

   - This fails :
[root@rhel-dev2 rh7]# si_prepareclient --server 192.168.81.11

Failure log :

When running : si_prepareclient --server 192.168.81.11 ...
...
...

Using "parted" to gather information about disk:
/dev/sda

find: 
'/lib/modules/3.10.0-862.11.6.el7.x86_64/kernel/drivers/input/joystick/*': No 
such file or directory

Unknown arguments: 3.10.0-862.11.6.el7.x86_64

Usage: /bin/dracut [OPTION]... [ []]

Version: 033-535.el7_5.1

Creates initial ramdisk images for preloading modules

  -h, --help  Display all options

If a [LIST] has multiple arguments, then you have to put these in quotes.

For example:

# dracut --add-drivers "module1 module2"  ...

FAILED: dracut --force --add systemimager --omit dash --no-hostonly 
--no-hostonly-cmdline --no-hostonly-i18n--omit-drivers "ac97_bus 
snd-compress snd-hrtimer snd-timer snd-hwdep snd-pcm snd snd-seq-midi-event 
snd-seq snd-seq-dummy snd-seq-midi-emul snd-seq-midi snd-seq-oss 
snd-seq-virmidi snd-rawmidi snd-seq-device snd-dummy snd-opl3-synth 
snd-opl3-lib snd-vx-lib snd-aloop snd-mpu401 snd-mpu401-uart snd-pcsp 
snd-virmidi snd-mtpav snd-firewire-lib snd-isight snd-scs1x 
snd-firewire-speakers snd-hda-core snd-hda-ext-core snd-tea575x-tuner 
snd-ak4114 snd-pt2258 snd-ak4xxx-adda snd-ak4113 snd-i2c snd-cs8427 snd-via82xx 
snd-emu10k1-synth snd-emu10k1 snd-emu10k1x snd-trident snd-atiixp snd-hdsp 
snd-hdspm snd-rme9652 snd-intel8x0m snd-echo3g snd-indigodj snd-darla24 
snd-layla20 snd-gina20 snd-indigoiox snd-gina24 snd-darla20 snd-mona 
snd-indigodjx snd-indigoio snd-indigo snd-layla24 snd-mia snd-intel8x0 
snd-rme32 snd-maestro3 snd-korg1212 snd-ice17xx-ak4xxx snd-ice1712 snd-ice1724 
snd-ac97-codec snd-vx222 snd-cs46xx snd-au8830 snd-au8810 snd-au8820 
snd-oxygen-lib snd-oxygen snd-virtuoso snd-mixart snd-ens1371 snd-atiixp-modem 
snd-ali5451 snd-via82xx-modem snd-hda-codec-analog snd-hda-codec-cmedia 
snd-hda-codec-cirrus snd-hda-codec-idt snd-hda-codec-realtek snd-hda-codec-hdmi 
snd-hda-codec-ca0132 snd-hda-codec-conexant snd-hda-codec-si3054 snd-hda-codec 
snd-hda-codec-via snd-hda-intel snd-hda-codec-generic snd-hda-codec-ca0110 
snd-lx6464es snd-pcxhr snd-cmipci snd-rme96 snd-ctxfi snd-asihpi snd-bt87x 
snd-ca0106 snd-ens1370 snd-lola snd-ad1889 snd-es1968 snd-soc-sst-acpi 
snd-soc-sst-ipc snd-soc-sst-dsp snd-soc-sst-match snd-soc-sst-firmware 
snd-soc-skl-ipc snd-soc-skl snd-soc-sst-haswell-pcm snd-intel-sst-acpi 
snd-intel-sst-core snd-soc-sst-atom-hifi2-platform snd-soc-skl_nau88l25_ssm4567 
snd-soc-sst-byt-cht-nocodec snd-soc-sst-cht-bsw-rt5645 
snd-soc-sst-cht-bsw-max98090_ti snd-soc-skl_rt286 snd-soc-sst-broadwell 
snd-soc-sst-bdw-rt5677-mach snd-soc-sst-bxt-da7219_max983

[sisuite-users] No more reboot needed when imaging a client. (Video)

[LAHAYE Olivier]

1st time in history: Install a system and run it without rebooting in between!

Now, it is not needed to reboot anymore after having imaged a node. If imager 
(initramfs) is running a kernel that has it's modules in the image (same 
version), then we just finish booting (mount /sysroot and swap-root and finish 
boot process just like if we had booted from scratch).

See SystemImager in action here:
http://olivier.lahaye1.free.fr/SystemImager/Videos/20180403_SystemImager_directboot.webm

Note:
- This install is using lvm over software raid (partitions); a somewhat complex 
disk layout
- The network error at the end is because I have a postinstall script that sets 
up an infiniband interface that is not present in my qemu VM (so this is 
expected).
Aside that everything works perfectly (including standard network).

Now backporting this feature to CentOS-6 (tested Ok on CentOS-7, should work on 
Fedora-27 and OpenSuSE-42.3 (will test later))

-- 
  Olivier LAHAYE

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] SystemImager next generation BIG progress: CentOS-6 and Open SuSE-42.3 support!

[LAHAYE Olivier]

I forgot to add few points.

If you want to use a main install script (let say for setting IMAGENAME or 
POST_ACTION, the skeleton can be found in 
/etc/systemimager/autoinstallscript.template
the most important thing is that it must contain the comment:
# script_version:2
This is to avoid running old script with disk partitionning and other stuffs 
that couyld break systemimager dracut logic.

A basic script can be:
--8<--8<--8<--8<--8<--8<--
#!/bin/sh
# script_version:2
# My sample script
#
. /lib/systemimager-lib.sh # load write_variables() function and some log 
message functions

IMAGENAME=oscar_image
loginfo "Set IMAGENAME=oscar_image"

write_variables # updates /tmp/variables.txt with new IMAGENAME

# end of main script
--8<--8<--8<--8<--8<--8<--

For the cmdline parameters, here is what I'm using:
si.image-server=10.0.1.1 si.config=testconfig.conf ramdisk_blocksize=1024 
ramdisk_size=128000 acpi=no noapic ip=dhcp dns=10.0.1.1 rd.vconsole.keymap=fr 
vga=791 splash si.debug

And my 10.0.1.1:/var/lib/systemimager/scripts/config/testconfig.conf file:
--8<--8<--8<--8<--8<--8<--
MAGENAME=testimage
MONITOR_SERVER=10.0.1.1
#MONITOR_PORT=8181
MONITOR_CONSOLE=yes
SKIP_LOCAL_CFG=y
DEBUG=yes
# SCRIPTNAME=testimage.master
# DL_PROTOCOL=rsync
SIS_POST_ACTION=shell
--8<--8<--8<--8<--8<--8<--

Menu entry in my /var/lib/tftpboot/pxelinux.cfg/default
--8<--8<--8<--8<--8<--8<--
LABEL systemimager
MENU LABEL ^S - Install a new Node
KERNEL sis_kernel
APPEND initrd=sis_initrd.img root=/dev/ram si.image-server=10.0.1.1 
si.config=testconfig.conf ramdisk_blocksize=1024 ramdisk_size=128000 ip=dhcp 
dns=10.0.1.1 rd.vconsole.keymap=fr vga=791 splash acpi=no noapic
--8<--8<--8<--8<------8<--8<--

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : LAHAYE Olivier
Envoyé : mercredi 21 mars 2018 18:12
À : sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : [PROVENANCE INTERNET] [sisuite-users] SystemImager next generation BIG 
progress: CentOS-6 and Open SuSE-42.3 support!


Systemimager is still progressing a lot!

New change since last announce:

- Support for CentOS-6 (finaly!)

- Support for Open SuSE-42.3

- Support For CentOS-7

- Support for Fedora-27

- Install script is not mandatory any-more (big change). You can still add one 
though.
 deployment process is the following:
 pre-install / format disks / mount partitions / run main install script / 
download/install image / install overrides / create config (mdadm, lvm, fstab, 
initramfs, ...) / bootloader / post install

- many cmdline parameters to control systemimager imaging process (no more 
option 140 DHCP parameters to configure (still supported)).
  parameters can be set at multiple places (DHCP, local.cfg, PXE-cmdline, 
/var/lib/systemimager/scripts/configs/.conf)

- disk layout is set in xml format and stored in 
/var/lib/systemimager/scripts/disks-layouts/.xml this permits to have a 
single image deployed to different nodes with different disks. No more one 
image per disk layout.

- Now protocols are splitted in dracut sub modules (systemimager-xmit)
  * For now, only rsync works. *
  Planned:
  systemimager-xmit-docker: build your image on a docker server (must be 
complete), install it on deployed hardware!
  systemimager-xmit-flamethrower
  systemimager-xmit-nfs: mount your image tree thru NFS and rsync locally from 
NFS mount point
  systemimager-xmit-rsync: as usual
  systemimager-xmit-ssh: using scp
  systemimager-xmit-template: a template file for adding more protocols
  systemimager-xmit-torrent: torrent deployment

- SSH tunnel is not considered any-more a protocol for systemimager image 
deployment.
  SSH tunnel is something running aside like a network layer. It was used for 
rsync, but IMHO could also be used for other protocols like NFS, docker, ...

- systemimager parameters (set as shell variables in local.cfg or 
/var/lib/systemimager/scripts/configs/.conf or set as cmdline parameter 
in PXE) are the following:
  - si.debug / $DEBUG: values: y|n => Enable debug messages
  - si.config / $SIS_CONFIG: name of file containing config (uses less 
cmdline). File is stored in /var/lib/systemimager/scripts/configs/. Name is 
given without its PATH
  - si.image-name / $IMAGENAME: name of the image (looks for 
imagename|imagename.master)
  - si.script-name / $SCRIPTNAME: name of main script (looks for 
scriptname|scriptname.sh|scriptname.master)
  - si.disk-layout / $DISKS_LAYOUT: name of file containing disks layout in xml 
format (see man a

[sisuite-users] SystemImager next generation BIG progress: CentOS-6 and Open SuSE-42.3 support!

[LAHAYE Olivier]

Systemimager is still progressing a lot!

New change since last announce:

- Support for CentOS-6 (finaly!)

- Support for Open SuSE-42.3

- Support For CentOS-7

- Support for Fedora-27

- Install script is not mandatory any-more (big change). You can still add one 
though.
 deployment process is the following:
 pre-install / format disks / mount partitions / run main install script / 
download/install image / install overrides / create config (mdadm, lvm, fstab, 
initramfs, ...) / bootloader / post install

- many cmdline parameters to control systemimager imaging process (no more 
option 140 DHCP parameters to configure (still supported)).
  parameters can be set at multiple places (DHCP, local.cfg, PXE-cmdline, 
/var/lib/systemimager/scripts/configs/.conf)

- disk layout is set in xml format and stored in 
/var/lib/systemimager/scripts/disks-layouts/.xml this permits to have a 
single image deployed to different nodes with different disks. No more one 
image per disk layout.

- Now protocols are splitted in dracut sub modules (systemimager-xmit)
  * For now, only rsync works. *
  Planned:
  systemimager-xmit-docker: build your image on a docker server (must be 
complete), install it on deployed hardware!
  systemimager-xmit-flamethrower
  systemimager-xmit-nfs: mount your image tree thru NFS and rsync locally from 
NFS mount point
  systemimager-xmit-rsync: as usual
  systemimager-xmit-ssh: using scp
  systemimager-xmit-template: a template file for adding more protocols
  systemimager-xmit-torrent: torrent deployment

- SSH tunnel is not considered any-more a protocol for systemimager image 
deployment.
  SSH tunnel is something running aside like a network layer. It was used for 
rsync, but IMHO could also be used for other protocols like NFS, docker, ...

- systemimager parameters (set as shell variables in local.cfg or 
/var/lib/systemimager/scripts/configs/.conf or set as cmdline parameter 
in PXE) are the following:
  - si.debug / $DEBUG: values: y|n => Enable debug messages
  - si.config / $SIS_CONFIG: name of file containing config (uses less 
cmdline). File is stored in /var/lib/systemimager/scripts/configs/. Name is 
given without its PATH
  - si.image-name / $IMAGENAME: name of the image (looks for 
imagename|imagename.master)
  - si.script-name / $SCRIPTNAME: name of main script (looks for 
scriptname|scriptname.sh|scriptname.master)
  - si.disk-layout / $DISKS_LAYOUT: name of file containing disks layout in xml 
format (see man autoinstallscript.conf for now) (looks for 
filename|filename.xml)
  - si.dl-protocol / $DL_PROTOCOL: protocolname as seen in dracut module 
systemimager-xmit-.sh. defaults to rsync except if other 
parameter let think otherwise.
  - si.monitor-server / $MONITOR_SERVER: name or ip for monitor server
  - si.monitor-port / $MONITOR_PORT: monitor server port (defaults to 8181. 
min:100, max:32000)
  - si.monitor-console / $MONITOR_CONSOLE: y|n|0|1|yes|no (enable/disable log 
reported to monitor console)
  - si.skip-local-cfg / SKIP_LOCAL_CFG: y|n|0|1|yes|no (default:n) if yes, try 
to read local.cfg from old disks or floppy (USB planed of course but not yet 
implemented)
  - si.image-server / $IMAGESERVER: name or ip for the image server
  - si.log-server-port / $LOG_SERVER_PORT: the log server port (default is 514, 
min:100, max:32000)
  - si.ssh-client / $SSH: y|n|0|1|yes|no (dfault "n").
  - si.ssh-download-url / $SSH_DOWNLOAD_URL: ssh download URL => sets 
DL_PROTOCOL to "ssh"
  - si.ssh-server / $SSHD: y|n|0|1|yes|no (enable / disable sshd access while 
imaging) (default "n")
  - si.flamethrower-directory-portbase: $FLAMETHROWER_DIRECTORY_PORTBASE: path
  - si.tmpfs-staging / $TMPFS_STAGING: path to staging dir.
  - si.term / $TERM: terminal type to use. defaults to "linux"
  - si.selinux-relabel / $SEL_RELABEL: y-n|0|1|yes|no: Request a SELinux files 
relabel after imaging disks
  - si.post-action / $SIS_POST_ACTION: what to do after imaging. defaults to 
reboot. Possible values: kexec, shell, reboot, shutdown, poweroff (and soon 
continue)
continue will boot the imaged system without reboot. This is possible as 
initramfs is simply mounting OS filesystems in /sysroot and calls swaproot. We 
are in the same situatiuon after imaging. We only need to check that imaging 
kernel (uname -r) has modules available in /sysroot/lib/modules/$(uname -r)/, 
then we exit the dracut hook initqueue and dracut finishes the boot for us.

- Parameters in DHCP are still possible and supported even in wickedd-dhcp4 
dhcp client in SuSE distros.
  - option-140: IMAGESERVER
  - option-141: LOG_SERVER_PORT
  - option-142: SSH_DOWNLOAD_URL
  - option-143: FLAMETHROWER_DIRECTORY_PORTBASE
  - option-144: TMPFS_STAGING

IMPORTANT:
- si_mkautoinstallscript is DEPRECATED and shouldn't be used (useless though)
- disk layout has changed. main scripts are now stored in 
/var/lib/systemimager/scripts/main-install (not /var/lib/systemimager/scripts)
This looks like:

[sisuite-users] New systemimager beta release.

[LAHAYE Olivier]

Dear all,

I've built a new systemimager release (4.5.0-0.20170920git). Hopefully there 
are no more script generation bugs.

Packages are available here: http://olivier.lahaye1.free.fr/SystemImager
This is a temporary location and is subject to change anytime soon.

You must regenerate your scripts ( for example: 
/usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install shell )

You can use these as yum/dnf repo by adding a systemimager.repo in 
/etc/yum.repos.d/
Content is (For CentOS-7):
-8<-8<-8<-8<-8<-
[SystemImager]
name=SystemImager CentOS-7
baseurl=http://olivier.lahaye1.free.fr/SystemImager/rhel-7-x86_64/
gpgcheck=0
enable=1
-8<-8<-8<-8<-8<-

You also need EPEL repositories available here: 
https://fedoraproject.org/wiki/EPEL/FAQ
(Using EPEL section)

Happy testing.

--
   Olivier LAHAYE
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] [Sisuite-devel] Net beta release v4.5.0-20170614git

[LAHAYE Olivier]

I've released the new version. you should see systemimager version 
4.5.0-0.20170629git

Cheers,

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : David Livingstone [david.livingst...@cn.ca]
Envoyé : jeudi 29 juin 2017 16:40
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] [Sisuite-devel] Net beta release v4.5.0-20170614git

Olivier - Thanks. Will wait for the new version and then try the OSCAR 
repository.

David

-Original Message-
From: olivier.laha...@free.fr [mailto:olivier.laha...@free.fr]
Sent: Thursday, June 29, 2017 3:07 AM
To: sisuite-users@lists.sourceforge.net
Cc: sisuite-de...@lists.sourceforge.net
Subject: Re: [sisuite-users] [Sisuite-devel] Net beta release v4.5.0-20170614git

David,

After reading a bit closer your message you're trying to install systemimager 
using the rpm command that doesn't handle dependancies download.
You need to use the "yum install" instead of "rpm -ivh" command. That should 
work.
Please try again using yum.
IMHO, it's a good idea to use the OSCAR repository:
rpm -ivh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r11073-1.el6.noarch.rpm
yum clean all; yum makecache
yum install systemimager-x86_64boot-standard systemimager-x86_64initrd_template 
systemimager-server systemimager-common systemimager-client dracut-systemimager 
All dependancies should be downloaded. If there are still some deps missing, 
then try to add the EPEL repository (Extended Package for Enterprise Linux. 
It's a port of many fedora packages). => rpm -ivh 
http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

Optionally you can install flamethrower, bittorrent and bittorrent-gui packages 
using yum install but this deployment method is not yet tested. It may or may 
not work.

Please wait until you see version v4.5.0-20170629git in OSCAR repository before 
trying again. (better version with many minor glitches fixes that I'll publish 
today).

Cheers,

- Mail original -
> De: "Olivier Lahaye" <olivier.laha...@free.fr>
> À: sisuite-users@lists.sourceforge.net
> Cc: sisuite-de...@lists.sourceforge.net
> Envoyé: Jeudi 29 Juin 2017 09:11:37
> Objet: Re: [Sisuite-devel] [sisuite-users] Net beta release
> v4.5.0-20170614git
>
> Hi David,
>
> I'll check at work later but it looks like you didn't setup the epel
> repo for rhel6/centos6.
> Aside that I've built a new release with many cosmetic fixes. I'll
> post it today with updated message regarding quick starting.
> I'll cross check install on my centos6 physical hardware before
> posting.
> As Brian said, the real release will end up on systemimager repo.
> Which will hosts non epel requirements like BitTorrent, flamethrower,
> cx_Freeze and perl Tk-TextANSIColor packages if don't miss any other.
> For the moment I'm using Oscar repo as it's easier for me (I'm using
> oscar packager tool that does everything for me (build deps, creates
> repo) for all distros)
>
> Envoyé de mon iPhone6+
>
> > Le 28 juin 2017 à 18:01, David Livingstone <david.livingst...@cn.ca>
> > a écrit :
> >
> > Olivier,
> >
> > Okay finally had a change to try and load below on rhel 6.4. From
> > the http://svn.oscar.openclustergroup.org/repos/unstable/ link below
> > I've gotten to the following :
> >
> >
> > [root@scdev1 2017]# rpm -ivh --test
> > systemimager-x86_64boot-standard-4.5.0-0.20170614git.el6.noarch.rpm
> > systemimager-x86_64initrd_template-4.5.0-0.20170614git.el6.noarch.rp
> > m systemimager-server-4.5.0-0.20170614git.el6.noarch.rpm
> > systemimager-common-4.5.0-0.20170614git.el6.noarch.rpm
> > systemimager-client-4.5.0-0.20170614git.el6.noarch.rpm
> > dracut-systemimager-4.5.0-0.20170615git.el6.noarch.rpm
> > perl-Tk-TextANSIColor-0.16-1.noarch.rpm
> > systemconfigurator-2.2.12-3.el6.noarch.rpm
> > error: Failed dependencies:
> >xfsprogs is needed by
> >systemimager-server-4.5.0-0.20170614git.el6.noarch
> >btrfs-progs is needed by
> >dracut-systemimager-4.5.0-0.20170615git.el6.noarch
> >dracut-network is needed by
> >dracut-systemimager-4.5.0-0.20170615git.el6.noarch
> >plymouth-plugin-script is needed by
> >dracut-systemimager-4.5.0-0.20170615git.el6.noarch
> >xfsprogs is needed by
> >dracut-systemimager-4.5.0-0.20170615git.el6.noarch
> > [root@scdev1 2017]#
> >
> > Obviously I am missing some packages however nothing is obvious in
> > the link above.
> >
> > Should I try the Easy install using OSCAR repositories for centos 6
> > ?
> >
> > Thanks
> > David
> >
> > -Orig

[sisuite-users] Net beta release v4.5.0-20170614git

[LAHAYE Olivier]

New relase with Plymouth GUI (if "splash" or "rhgb" keyword is present in PXE 
cmdline).

What's new in this release:

- New GUI dialogbox to display to request keypress when interactive shell is to 
be triggered (after install if requested or in case of failure. This leave time 
to read GUI previous messages)
- If post install action is non interactive (reboot, poweroff, kexec, ..., the 
dialogbox will be displayed during 5 seconds and then action will be performed.
- enhanced /lib/systemimager-lib.sh (new function to wait for a keypress in gui)
- new screenshots

Screenshots:
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_plymouth.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_success_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_failure_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_plymouth.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_failure_plymouth.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_success_plymouth.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/si_monitortk.png

What works aside cool interface (text or GUI)

- bootpackage creation works (si_mkbootpackage)
- script creation works (si_mkautoinstallscript)
- rsync deployment method works
- SSH deployment method works (tested si_pushinstall) (both text anf GUI
 modes will display a banner asking for si_pushinstall if no ssh keys is
 available)
- grub2 bootloader install works
- si_monitortk works fine (see screenshot)

Not tested but should work:
- grub1 bootloader install (CentOS-6)

TODO:
- stop cleanly rsync and unmount disks if CTRL-ALT-DEL is pressed during 
imaging.
- fix colormap bug on CENTOS-7 (drm driver bug)
- test and eventually fix flamethrower deployment
- test and eventually fix bittorrent deployment
- update doc with all cmdline new parameters

IMHO, this release is as stable as last stable release, though it is less 
tested so be careful.

Source: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2

Repos for RHEL6, RHEL7 and FC25:
http://svn.oscar.openclustergroup.org/repos/unstable/

Release number: v4.5.0-20170614git

Usual notes:

1/ You must regenerate your install scripts
E.g.: /usr/sbin/si_mkautoinstallscript --quiet --autodetect-disks --image 
oscarimage_sda --force --ip-assignment static --post-install cmdline

(--post-install can be shell, reboot, poweroff, cmdline, kexec...) (shell 
drops a debug shell at the end so you can check what was done)

cmdline parameter rd.sis.post-action=shell will drop a shell at the end of 
imaging.

2/ Easy install using OSCAR repositories

- For easy install on CentOS-7:
rpm -ivh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-7-x86_64/oscar-release-6.1.2r0-1.el7.centos.noarch.rpm

- For easy install on CentOS-6:
rpm -ivh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r11073-1.el6.noarch.rpm

- (Not yeat available for FC-25, you must create your repofile by hand or 
install CentOS-7 package and update /etc/yum.repos.d/oscar.repo)

3/ Note: to setup your PXE, most of relevant cmdline parameters can be found 
here:
(/usr/lib/dracut/modules.d/51systemimager/module-install.sh or install on old 
distros)

4/ Needs a postinstall script to setup network.
One that can be used is the following one:
http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/16all.network_config

Happy deployment.

-- 
   Olivier LAHAYE








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New beta release with enhanced GUI (CentOS 6, 7 and Fedora 25)

[LAHAYE Olivier]

New relase with Plymouth GUI (if "splash" or "rhgb" keyword is present in PXE 
cmdline).

What's new in this release:
- New GUI dialogbox to display important or static messages like asking for 
si_pushinstall command.
- enhanced /lib/systemimager-lib.sh (new functions to enable system messages, 
debug messages, use the gui dialog box)
- new cmdline parameters (enable debugging, fix the post imaging action
- many glitches and mug fixes.
- new screenshots

Screenshots:
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_plymouth.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_success_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_failure_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_text.png
- http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_plymouth.png

Text mode is still the default.

What works aside cool interface (text or GUI)
- bootpackage creation works (si_mkbootpackage)
- rsync deployment method works
- SSH deployment method works (tested si_pushinstall) (both text anf GUI modes 
will display a banner asking for si_pushinstall if no ssh keys is available)
- grub2 bootloader install works
- si_monitortk works fine

Not tested but should work:
- grub1 bootloader install (CentOS-6)

TODO:
- stop cleanly rsync and unmount disks if CTRL-ALT-DEL is pressed during 
imaging.
- fix colormap bug on CENTOS-7 (drm driver bug)
- test and eventually fix flamethrower deployment
- test and eventually fix bittorrent deployment
- update doc with all cmdline new parameters

IMHO, this release is as stable as last stable release, though it is less 
tested so be careful.

Source: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2

Repos for RHEL6, RHEL7 and FC25:
http://svn.oscar.openclustergroup.org/repos/unstable/
Release number: v4.5.0-20170613git

Usual notes:
1/ You must regenerate your install scripts
E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install cmdline

(post install can be shell, reboot, poweroff, cmdline, kexec...) (shell drops a 
debug shell at the end so you can check what was done)
cmdline parameter rd.sis.post-action=shell will drop a shell at the end of 
imaging.


2/ Easy install using OSCAR repositories
- For easy install on CentOS-7:

rpm -ivh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-7-x86_64/oscar-release-6.1.2r0-1.el7.centos.noarch.rpm

- For easy install on CentOS-6:

rpm -ivh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r11073-1.el6.noarch.rpm

- (Not yeat available for FC-25, you must create your repofile by hand 
or install CentOS-7 package and update /etc/yum.repos.d/oscar.repo)



3/ Note: to setup your PXE, most of relevant cmdline parameters can be found 
here:

(/usr/lib/dracut/modules.d/39systemimager/module-install.sh or install on old 
distros)



4/ Needs a postinstall script to setup network.

One that can be used is the following one:

http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/16all.network_config



Happy deployment.



Olivier.





-- 

   Olivier LAHAYE

   CEA DRT/LIST/DIR








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] systemimager-4.5.0-20170502git: seems to work fine so far.

[LAHAYE Olivier]

Hi,

I've just uploaded a new release that now hopefully works fine at least for 
CentOS-6, CentOS-7 and Fedora-25.
See previous messages to see how to use it.

Available here:
http://svn.oscar.openclustergroup.org/repos/unstable/

Source:
ttp://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2

Screenshot:
http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png

Note:
1/ You must regenerate your install scripts
E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install shell
(post install can be shell, reboot, poweroff, ...) (shell drops a debug shell 
at the end so you can check what was done)

2/ This is NOT for production environment, but so far it works well for rsync 
method.

Note:
- deployment using ssh will not work
- deployment using bittorent is not tested and and I would be surprised if it 
works. (please report success or failure if you can test)

TODO:
- Include ssh binary
- detect build environment and only include server ssh keys if ran outside 
rpmbuild environment
- include sshd binary so access is possible during imaging.
- more tests
- tests on real hardware
- test monitor console
- update doc: add cmdline systemimager dracut module variables to doc
- update doc: remove obsolete stuffs

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New SYSTEMIMAGER testing release.

[LAHAYE Olivier]

Hi,

I've juste release the 4.5.0-20170427git release.
It features:
- Support for grub / grub2 bootloader installation (no more post install script 
needed).
  => It is installed before scripts are run. in case it's not working, a post 
install script can fix the problem.
- beep should work better (nos pcspkr driver is loaded and beep is sent to 
/dev/console).
- more console output glitches cleanup
- It tries to relabel files with correct selinux policy if selinux is started. 
If not, it touch /.autorelabel in order to make sure that after next boot, the 
system whill have correct labels.
  This can be disabled by setting rd.sis.selinux-relabel=0 in the PXE 
initrd.img cmdline

More cmdline parameters are supported:
See /usr/share/dracut/modules.d/39systemimager/parse-sis-options-old.sh (on old 
dracut sustems like CentOS-6)
or
See /lib/dracut/modules.d/39systemimager/parse-sis-options.sh (on newer dracut 
systems like CentOS-7)

Howto test easily with a qemu vm:

put 00:16:76:43:8b:0e in your dhcp and make sure your pxe is ok.

update your image script (make a backup of the old one before)
example: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install shell

Then run the vm:
/usr/bin/qemu-system-x86_64 -machine accel=kvm -m 1024 -no-fd-bootchk -hda 
"/patch/to/a/10GB_disk.vmdk" -net 
nic,vlan=0,macaddr=00:16:76:43:8b:0e,model=rtl8139 -net 
user,vlan=0,hostname=new-node -rtc base=localtime -name "Linux x86_64" -kernel 
/usr/share/systemimager/boot/x86_64/standard/kernel -initrd 
/usr/share/systemimager/boot/x86_64/standard/initrd.img -append "rdshell 
SKIP_LOCAL_CFG=y MONITOR_SERVER= MONITOR_CONSOLE=yes 
IMAGESERVER= ramdisk_blocksize=1024 
ramdisk_size=128000 ip=dhcp ksdevice=bootif acpi=no noapic rd.neednet=1"

Happy testing.

-- 

   Olivier LAHAYE

   CEA DRT/LIST/DIR








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] New beta release (screenshot available!)

[LAHAYE Olivier]

Sorry,

Correct screenshot:
http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png (showing a 
CentOS-7 image being deployed from a CentOS-6 sis_initrd.img

Also forgot to tel again that grub post install scripts are mandatory:
They are available here:
http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/

I'm trying to find a way to have systemimager to create and install the default 
OS boot loader and remove the need for those scripts (it's not as easy as it 
sounds).

latest testing release is "4.5.0-0.20170424git" It is only available for 
CentOS-6, CentOS-7 and Fedora-25 for now. DEB world will be addressed later. 
NOTE: It should be able to image all kind of linux image anyway.

Happy testing.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : LAHAYE Olivier
Envoyé : lundi 24 avril 2017 19:38
À : sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : [PROVENANCE INTERNET] [sisuite-users] New beta release (screenshot 
available!)


Hi,

Here is a brand new release (20170424git) with fancy new features and that 
works far better.
- Progress bar
- colors
- Far better error detections and handling

Soon available here: http://svn.oscar.openclustergroup.org/repos/unstable/
Source tarball: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2
(you can build package for your rpm based distro using rpmbuild -tb 
systemimager.tar.bz2)

And now a cool screeshot:
http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO7.png

IMPORTANT NOTICE:
1/ You must regenerate your install scripts
E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install shell
(post install can be shell, reboot, poweroff, ...) (shell drops a debug shell 
at the end so you can check what was done)

2/ This is NOT for production environment.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New beta release (screenshot available!)

[LAHAYE Olivier]

Hi,

Here is a brand new release (20170424git) with fancy new features and that 
works far better.
- Progress bar
- colors
- Far better error detections and handling

Soon available here: http://svn.oscar.openclustergroup.org/repos/unstable/
Source tarball: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2
(you can build package for your rpm based distro using rpmbuild -tb 
systemimager.tar.bz2)

And now a cool screeshot:
http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO7.png

IMPORTANT NOTICE:
1/ You must regenerate your install scripts
E.g.: /usr/sbin/si_mkautoinstallscript -quiet --autodetect-disks -image 
oscarimage_sda -force -ip-assignment static -post-install shell
(post install can be shell, reboot, poweroff, ...) (shell drops a debug shell 
at the end so you can check what was done)

2/ This is NOT for production environment.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Systemimager NG: Working alpha

[LAHAYE Olivier]

David L,

I reply in the list as this mail contains usefull information for every testers.

Cool to here that systemimager is of any interest after such a long time 
without a working solution on modern distros.

Be very carefull as I had difficulties to make RHEL-6 working until the imaging 
script works (dracut is v004 (we are at v044))
I'm using qemu and centos-6 fails to have a working network on my descktop, so 
I can't tell if it really works on this release of CentOS.
- I end up to getting an IP (works)
- Then I fail pingtests (normal on qemu with -net user (only the gateway is 
pingable and it works)
- Then I try to rsync /scripts and it fails with no route to host (while there 
is a default route that itis correct and a correct IP and I can ping the 
gateway).
Possible problem could be: lack of qemu support in rhel6 kernel
Or it can also be a problem in systemimager that forgot to install a low level 
binary in the initrd and that ends up with a out of subject missleading error 
message. I hadn't yet the possibility to test on real hardware. but I'll do 
that soon.

Also you must regenerate your imaging scripts as the structure has changed. The 
good news is that now, the header of the script reports the command line used 
to generate it.
Also you must add the provided post installs  scripts (grub setup and network 
setup).

A bad trick could be to use the 86boot package from either rhel-7 or fedora. 
Those packages only contain matching kernel+initrd and it's a noarch package so 
even if it's ugly, I think it can work. (of course si_mkbootpackage will remain 
rhel-6 and generate rhel-6 based initrd, but if you're stuck it could be a 
viable alternative to use kernel+initrd from fc-25 boot package

si_monitortk is able to report the imaging progress, but as I'm using NAT on my 
VMs I was unable to test if the remote console is working.

I forgot to tell that IMAGING_SERVER can be specified on the kernel-cmdline
For all possible parameters, have look here:
https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/39systemimager/parse-sis-options.sh
(on rhel6, it's parse-sis-options-old.sh)
You can also use most dracut.cmdline parameters (man dracut.cmdline)

Cheers,

Olivier.

PS: Tis message should only be on the devel list, but as there is no working 
solution nowadays, it's good t know for non developpers that in case they 
really need a systemimager solution, this alpha release could help.

>From now, I'll only post on devel for all messages relative to systemimager 
>devel.
--
   Olivier LAHAYE
   CEA


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] Systemimager NG: Working alpha

[LAHAYE Olivier]

Hi systemimager users and contributors,

The long awaited systemimager that works on modern distros is almost there (as 
unstable alpha version for now).
It works so far on CentOS-7 and Fedora-25. CentOS-6 should also work (not yet 
tested but its old dracut component is taken into account)

rpms for RHEL-6, RHEL-7, FC-25 and source tarball are available on OSCAR 
Cluster repositories (see below)

I don't forget deb world, but no time for that now. 1st I need to polish the 
new dracut based architecture.
Then I'll focus on deb world trying to deal with dracut conflict with 
initramfs-tools on most deb distros.

repos: http://svn.oscar.openclustergroup.org/repos/unstable/
src: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2
git: 
https://github.com/finley/SystemImager/tree/initrd-from-imageserver-and-dont-package-initrd
post install scripts: 
http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_postinstall/

Please not that this is really EXPERIMENTAL. As such, do not use in real world 
except if you know what you're doing.

Note that you must regenerate your install scripts using 
si_mkautoinstallscript. This command now accpets "shell" as --post-install so 
you can get a shell even if install is successfull. usefull for debugging post 
install scripts.

si_mkbootpackage accepts an new parameter: --dracut-opts=""
For example, it is usefull when using it with qemu:
sudo si_mkbootpackage --dracut-opts="--add qemu --add qemu-net" 
--destination=/tmp
Or if you want a specific keyboard.
sudo si_mkbootpackage --dracut-opts="--kernel-cmdline 'rd.vconsole.keymap=fr'" 
--destination=/tmp
(man dracut.cmdline to see all paramaters that can be added that way)
Some options may conflict with si_mkbootpackage.
Note: si_mkbootpackage fails to compute initrd.img memory requirements. this is 
harmless; the generated bootpackage is working.

Also note that network and bootloader are no longer setup by systemconfigurator 
which is obsolete and doesn't know how to handle network manager or 
systemd-networkd. The above post-install-scripts with small tweeking should do 
the trick.

Happy testing.

Olivier.






-- 

   Olivier LAHAYE

   CEA DRT/LIST/DIR








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] SystemImager NG: it works :-)

[LAHAYE Olivier]

So far,

My rpm builds and tested ok on centos7
It has been built successfully on fedora20 but not tested.
on centos6, it is facing this bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1182297
This is not centos6 related and will be fixed soon. if I download the package, 
it builds fine.

Right now, I'm polishing the build. Then I'll cross check the list of binaries 
that needs to be included so most common user postinstall script can run. I 
will also include driver firmwares so the generic image will work for most 
common cases.
As for buzybox, I've chosen to not use it and use core utils instead. The image 
is bigger, but on common systems this is not an issue anymore. I made this 
choice because the buzybox package is not available on centos6 and maybe on 
other distros. This choice is very easy to revert. (either by reenabling 
buzybox.rul build or by using the os provided package and adding the correct 
dracut option.

Then I'll test that non systemd based  images still work (I see no reaseon why 
it wouldn't).

Then I'll update the deb build (minor update is needed (deps and list of files 
to include))

Stay tuned.

Cheers,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : David Livingstone [david.livingst...@cn.ca]
Envoyé : lundi 26 janvier 2015 20:00
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] SystemImager NG: it works :-)

Olivier – Looks great ! Let me know when you have something to test – I’m still 
using RHEL 6.

Thanks

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Monday, January 26, 2015 4:06 AM
To: sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] SystemImager NG: it works :-)


Hi,

I've finaly updated systemimager to work with host OS binaries instead of 
rebuilding everything.
This means that now, the initrd template and the default initrd and kernel are 
generated using dracut and I only build 3 components: cx_freeze, udpcast and 
bittorrent client. All other binaries are taken from the host OS and are thus 
in sync with kernel and drivers (which was not the case in previous release 
were binaries expected to run with boel kernel 3.7.5 were built on a totaly 
different kernel and in some circumstance were crashing or failing to built.

This is past.

I've not yet pushed to git my changes, because I must do some more testing, but 
the most difficult things are fixed.
things that still need to be addressed:
- buzybox rpm not available on centos7: do we build it or used standard tools
- need to fix list of binaries that we need
- test.

I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have 
tilme.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] SystemImager NG: it works :-)

[LAHAYE Olivier]

Hi,

I've finaly updated systemimager to work with host OS binaries instead of 
rebuilding everything.
This means that now, the initrd template and the default initrd and kernel are 
generated using dracut and I only build 3 components: cx_freeze, udpcast and 
bittorrent client. All other binaries are taken from the host OS and are thus 
in sync with kernel and drivers (which was not the case in previous release 
were binaries expected to run with boel kernel 3.7.5 were built on a totaly 
different kernel and in some circumstance were crashing or failing to built.

This is past.

I've not yet pushed to git my changes, because I must do some more testing, but 
the most difficult things are fixed.
things that still need to be addressed:
- buzybox rpm not available on centos7: do we build it or used standard tools
- need to fix list of binaries that we need
- test.

I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have 
tilme.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] NextGen Systemimager (dracut based): progress

[LAHAYE Olivier]

Hi,

Thanks a lot :-) It works fine thanks :-)

Now, my test systemimager builds in a matter of seconds :-)
It produces a dracut image that starts booting, unfortunately, it then hangs, 
but I'm near a solution I think.

Once I have something completely working, I'll push 4 changes:
- pod2man fixes
- makefiles fixes
- add an udpcast patch
- remove some .rul files and kernel build sinfrastructure.

I won't push anything until I'm shure that it works on rpm and deb based 
systems so it may take some time though.

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Brian Elliott Finley [br...@thefinleys.com]
Envoyé : mercredi 21 janvier 2015 15:46
À : SISuite Users List
Objet : Re: [sisuite-users] NextGen Systemimager (dracut based): progress


Olivier,

I'll take dare is that udpcast upload today.

Thanks!

-Brian

On Jan 21, 2015 8:19 AM, LAHAYE Olivier 
olivier.lah...@cea.frmailto:olivier.lah...@cea.fr wrote:

Hi,

I've just been able to create a cracut systemd based systemimager initrd image 
that is able to image a node.

This is a great step forward as it should work on all system that can build 
initrd using dracut tool.
For the moment I've only tested on fedora20 build and imaged a centos7 node 
without any problem.

The image was created by hand using dracut and systemd from the standard 
systemimager initrd_template.
I've just added a systemimager.target, a systemimager.service that runs 
/etc/init.d/rcS. This is ugly but it does work fine.

Now that I' have a proof of concept, I'm working on the systemimage build 
process to avoid building useless stuffs (only build systemimager specific 
stuffs and use everything else from the build host).

Now I'm hitting a small issue with udpcast. I need a more recent version, 
because the systemimager version fails to build on recent linus distros.

So if someone who can have access to systemimager download tree could update it 
with latest udpcast tarball, that would help me a lot.
Basically I need http://www.udpcast.linux.lu/download/udpcast-20120424.tar.bz2 
to be placed in http://download.systemimager.org/pub/udpcast/

There is still lot of work to do like identify what build host binaries should 
be copied into dracut image, but if I'm not interrupted, I should have a test 
version in a few weeks.

This version will be somewhat ugly regarding dracut concept as it won't use a 
systemimager dedicated dracut module to create the image, just a giant dracut 
commandline, but the result should be working well.
Once this phase is proven to work on most majort distros (deb+rpm), Ill try to 
learn how to create a systemimager dracut module so I can simplify and enhance 
the UYOK option.
This should work on non systemd based system as well; though I haven't tested 
yet.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] NextGen Systemimager (dracut based): progress

[LAHAYE Olivier]

Hi,

I've just been able to create a cracut systemd based systemimager initrd image 
that is able to image a node.

This is a great step forward as it should work on all system that can build 
initrd using dracut tool.
For the moment I've only tested on fedora20 build and imaged a centos7 node 
without any problem.

The image was created by hand using dracut and systemd from the standard 
systemimager initrd_template.
I've just added a systemimager.target, a systemimager.service that runs 
/etc/init.d/rcS. This is ugly but it does work fine.

Now that I' have a proof of concept, I'm working on the systemimage build 
process to avoid building useless stuffs (only build systemimager specific 
stuffs and use everything else from the build host).

Now I'm hitting a small issue with udpcast. I need a more recent version, 
because the systemimager version fails to build on recent linus distros.

So if someone who can have access to systemimager download tree could update it 
with latest udpcast tarball, that would help me a lot.
Basically I need http://www.udpcast.linux.lu/download/udpcast-20120424.tar.bz2 
to be placed in http://download.systemimager.org/pub/udpcast/

There is still lot of work to do like identify what build host binaries should 
be copied into dracut image, but if I'm not interrupted, I should have a test 
version in a few weeks.

This version will be somewhat ugly regarding dracut concept as it won't use a 
systemimager dedicated dracut module to create the image, just a giant dracut 
commandline, but the result should be working well.
Once this phase is proven to work on most majort distros (deb+rpm), Ill try to 
learn how to create a systemimager dracut module so I can simplify and enhance 
the UYOK option.
This should work on non systemd based system as well; though I haven't tested 
yet.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] Kernel panic on boot on DELL R720

[LAHAYE Olivier]

Ok, the good news is that you can boot.

The initrd generation in systemimager is broken since the beginning as it 
assumes that the kernel includes from the build OS have the same structures as 
the includes shipped with the kernel that is built for the initrd. In the past, 
that was the case, most supported distros were using kernel-2.6, unfortunately, 
now we have distros that still use kernel-2.6 (rhel-6) and distros that uses 
kernel 3.X (fedora-17+, ...) and thus it becomes a problem when building things 
like lvn that uses kernel structure. They uses the build OS structure, but runs 
on the psecific kernel that has different structures from the build OS. Thus 
lvn have problems (crash, freezes, ...).
I did my best to patch the initrd component build to use as much as I can the 
most relevant includes, but there are some cases where it is not possible 
unfortunately.

I'm working on a full rewrite of the initrd template generation by using dracut.

Using dractu would remove the need to use kernels that are different from the 
build os while keeping the advantage to support latest hardwares. The build 
time would be greatly reduced (no need to build a kernel and many components. 
The build would be reduced to specific components like bittorent client and a 
few other things. More over, the libs, kernel structures and binaries would be 
in siync each together, thus far more stable.

I've started testing and I'm able to build a next-gen initrd, but I'm still 
unable to boot it normally as it uses systemd and I haven't yet written the 
logic for that (easy).

I'm currently extremely buzy at preparing an OSCAR Cluster release for rhel6. 
Then I'l concentrate on fixing systemImager initrd template. I hope to have 
somethign ready before summer.

Best regards.
--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
Envoyé : mercredi 12 mars 2014 18:50
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] Kernel panic on boot on DELL R720

Hello,

I made some others test. A Debian wheezy 64bits netinstall or an Ubuntu
12.04 LTS 64 bits netinstall work fine.  For me a

I take the default Debian kernel and initrd from the installation and i
use it with PXE. The process stop when the init process try to find root
partition. All is OK because i haven't changed the PXE cmdline to boot
normally.

So, I tried to take this kernel and one initrd created by
si_prepareclient on this fresh installation. I have exactly the same
problem of /init not found.

I think the problem, is in the generating of the initrd but i don't know
how to debug it.

I have updated the BIOS.

Have you an other idea ?

Regards

Le 11/03/2014 10:00, LAHAYE Olivier a écrit :

 Then I would try rhel6 netinstall or fedora20 netinstall
 the rhel6 kernel is often well tested by DELL.

 I would also try t-o install latest BIOS.

 As a last resort I would call DEeLL support, maybe you have an hardware bug, 
 or maybe a BIOS config bug that is listed in a knowledge base.

 Best regards,

 Olivier.

 --
 Olivier LAHAYE
 CEA DRT/LIST/DIR

 
 De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
 Envoyé : lundi 10 mars 2014 19:09
 À : sisuite-users@lists.sourceforge.net
 Objet : Re: [sisuite-users] Kernel panic on boot on DELL R720

 Le 10/03/2014 11:39, Pierre BLONDEAU a écrit :
 Hy,

 Thank you for the answer.

 The ubuntu's server kernel point to linux-image-3.2.0-60-generic, i have
 tried it ( and double check now to be sure ).

 I see in the page that i must use a kernel at least 3.8 for Intel's
 E5-2600v2 precessor. But i have aslo tried
 linux-image-generic-lts-raring - 3.8.0.37.37 and
 linux-image-generic-lts-saucy - 3.11.0.18.17 .

 Did you say i should try the installer kernel ( from the netinst ) as
 pxe kernel ?

 Hy,

 I have tried with the netinstall kernel and i have the same kernel panic
 less the call trace:

 Freeing unused kernel memory : 836k ()
 Failed to execute /init
 Kernel panic - not syncing: No init found. Try passing init= option to
 kernel. See Linux Documentation/init.txt for guidance.

 Have you a other idea ?

 Regards

 Regards

 Le 10/03/2014 10:07, LAHAYE Olivier a écrit :
 I would suggest to use this release for the deployment server:
 http://www.ubuntu.com/certification/hardware/201205-10987/ and the
 enable use your own kernel. This may help.

 Best regards.

 --
  Olivier LAHAYE
  CEA DRT/LIST/DIR

 
 De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
 Envoyé : vendredi 7 mars 2014 17:24
 À : sisuite-users@lists.sourceforge.net
 Objet : [sisuite-users] Kernel panic on boot on DELL R720

 Good After Noon,

 We recently purchased a DELL R720.

 Network cards in this machine are too recent for our old kernel. It's a
 personalise ubuntu 2.6.32 with maximum of module. We had compiled the
 version 1.6.2 of the e1000e driver's

Re: [sisuite-users] Kernel panic on boot on DELL R720

[LAHAYE Olivier]

Then I would try rhel6 netinstall or fedora20 netinstall
the rhel6 kernel is often well tested by DELL.

I would also try t-o install latest BIOS.

As a last resort I would call DEeLL support, maybe you have an hardware bug, or 
maybe a BIOS config bug that is listed in a knowledge base.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
Envoyé : lundi 10 mars 2014 19:09
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] Kernel panic on boot on DELL R720

Le 10/03/2014 11:39, Pierre BLONDEAU a écrit :
 Hy,

 Thank you for the answer.

 The ubuntu's server kernel point to linux-image-3.2.0-60-generic, i have
 tried it ( and double check now to be sure ).

 I see in the page that i must use a kernel at least 3.8 for Intel's
 E5-2600v2 precessor. But i have aslo tried
 linux-image-generic-lts-raring - 3.8.0.37.37 and
 linux-image-generic-lts-saucy - 3.11.0.18.17 .

 Did you say i should try the installer kernel ( from the netinst ) as
 pxe kernel ?

Hy,

I have tried with the netinstall kernel and i have the same kernel panic
less the call trace:

Freeing unused kernel memory : 836k ()
Failed to execute /init
Kernel panic - not syncing: No init found. Try passing init= option to
kernel. See Linux Documentation/init.txt for guidance.

Have you a other idea ?

Regards

 Regards

 Le 10/03/2014 10:07, LAHAYE Olivier a écrit :
 I would suggest to use this release for the deployment server:
 http://www.ubuntu.com/certification/hardware/201205-10987/ and the
 enable use your own kernel. This may help.

 Best regards.

 --
 Olivier LAHAYE
 CEA DRT/LIST/DIR

 
 De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
 Envoyé : vendredi 7 mars 2014 17:24
 À : sisuite-users@lists.sourceforge.net
 Objet : [sisuite-users] Kernel panic on boot on DELL R720

 Good After Noon,

 We recently purchased a DELL R720.

 Network cards in this machine are too recent for our old kernel. It's a
 personalise ubuntu 2.6.32 with maximum of module. We had compiled the
 version 1.6.2 of the e1000e driver's . This version is too old for our
 machine. This kernel boot correctly, but the installation plant during
 the network configuration.

 So we tried with kernels 3.X after have patched si_prepareclient.

 We tested a lot of combinations:
- Kernel : 3.2, 3.8 and 3.11 ( lts ubuntu )
- si_prepareclient patched by us or that present in the 4.3 beta on
 http://svn.oscar.openclustergroup.org/repos/unstable/

 We also tried the kernel and initrd provided by
 systemimager-boot-amd64-standard:
- 4.1.99.svn4556yaubert -
 http://download.systemimager.org/debian/pool/main/s/systemimager/
- 4.3 -
 http://svn.oscar.openclustergroup.org/repos/unstable/debian-7-x86_64/Early


 At the begining, we have a kernel panic that looks like:
 Freeing unused kernel memory: 532k freed
 Failed to execute /init
 Kernel panic - not syncing: No init found. Try passing init= option to
 kernel.
 See Linux Documentation/init.txt for guidance.
 Pid: 1, comm: swapper/0 Not tainted 3.7.5-boel_v4.3.0 #1
 Call Trace:
[8134bbb1] panic+0xb6/0x1b5
[81340640] ? rest_init+0x70/0x70
[81340736] kernel_init+0xf6/0x100
[8135192c] ret_form_fork+0x7c/0xb0
[81340640] ? rest_init+0x70/0x70

 We tried disabling a maximum of kernel's arguments and increase the size
 of ramdisk in PXE's command line but it does not change :
 LABEL systemimager
   KERNEL u64/new/kernel
   APPEND initrd=u64/new/initrd.img root=/dev/ram ramdisk_size=100

 Do you have an idea ?

 Thanks in advance.

 Regards

 --
 --
 Pierre BLONDEAU
 Administrateur Systèmes  réseaux
 Université de Caen
 Laboratoire GREYC, Département d'informatique

 tel : 02 31 56 75 42
 bureau  : Campus 2, Science 3, 406
 --


 --

 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and
 their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/13534_NeoTech
 ___
 sisuite-users mailing list
 sisuite-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sisuite-users





 --
 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/13534_NeoTech

Re: [sisuite-users] Kernel panic on boot on DELL R720

[LAHAYE Olivier]

I would suggest to use this release for the deployment server: 
http://www.ubuntu.com/certification/hardware/201205-10987/ and the enable use 
your own kernel. This may help.

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : Pierre BLONDEAU [pierre.blond...@unicaen.fr]
Envoyé : vendredi 7 mars 2014 17:24
À : sisuite-users@lists.sourceforge.net
Objet : [sisuite-users] Kernel panic on boot on DELL R720

Good After Noon,

We recently purchased a DELL R720.

Network cards in this machine are too recent for our old kernel. It's a
personalise ubuntu 2.6.32 with maximum of module. We had compiled the
version 1.6.2 of the e1000e driver's . This version is too old for our
machine. This kernel boot correctly, but the installation plant during
the network configuration.

So we tried with kernels 3.X after have patched si_prepareclient.

We tested a lot of combinations:
  - Kernel : 3.2, 3.8 and 3.11 ( lts ubuntu )
  - si_prepareclient patched by us or that present in the 4.3 beta on
http://svn.oscar.openclustergroup.org/repos/unstable/

We also tried the kernel and initrd provided by
systemimager-boot-amd64-standard:
  - 4.1.99.svn4556yaubert -
http://download.systemimager.org/debian/pool/main/s/systemimager/
  - 4.3 -
http://svn.oscar.openclustergroup.org/repos/unstable/debian-7-x86_64/Early

At the begining, we have a kernel panic that looks like:
Freeing unused kernel memory: 532k freed
Failed to execute /init
Kernel panic - not syncing: No init found. Try passing init= option to
kernel.
See Linux Documentation/init.txt for guidance.
Pid: 1, comm: swapper/0 Not tainted 3.7.5-boel_v4.3.0 #1
Call Trace:
  [8134bbb1] panic+0xb6/0x1b5
  [81340640] ? rest_init+0x70/0x70
  [81340736] kernel_init+0xf6/0x100
  [8135192c] ret_form_fork+0x7c/0xb0
  [81340640] ? rest_init+0x70/0x70

We tried disabling a maximum of kernel's arguments and increase the size
of ramdisk in PXE's command line but it does not change :
LABEL systemimager
 KERNEL u64/new/kernel
 APPEND initrd=u64/new/initrd.img root=/dev/ram ramdisk_size=100

Do you have an idea ?

Thanks in advance.

Regards

--
--
Pierre BLONDEAU
Administrateur Systèmes  réseaux
Université de Caen
Laboratoire GREYC, Département d'informatique

tel : 02 31 56 75 42
bureau  : Campus 2, Science 3, 406
--


--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] error with si_prepareclient command (v4.3.0 version of systemimager-client)

[LAHAYE Olivier]

Hi Steven, thanks a lot for reporting this bug, I'll try to fix it soon.

Best regards,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : Steven DuChene [steven.a.duch...@hp.com]
Envoyé : mardi 4 mars 2014 00:07
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] error with si_prepareclient command (v4.3.0 version 
of systemimager-client)

On 03/03/2014 12:08 PM, Steven DuChene wrote:
 When I try to run the si_prepareclient command on a ubuntu-12.04LTS
 systems I get the following error:

 # si_prepareclient --server 10.23.18.10 --my-modules
 FATAL:  --firmware-dir option used without --include-system-firmware !
 Try si_prepareclient --help for more info.

 However I am not specifying or passing the --firmware-dir option to the
 command.
 --
 Steven DuChene


 --
 Subversion Kills Productivity. Get off Subversion  Make the Move to Perforce.
 With Perforce, you get hassle-free workflows. Merge that actually works.
 Faster operations. Version large binaries.  Built-in WAN optimization and the
 freedom to use Git, Perforce or both. Make the move to Perforce.
 http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk
 ___
 sisuite-users mailing list
 sisuite-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sisuite-users
BTW, if I comment out line 363 of the si_prepareclient script it works.

if (($server)  ($norsyncd)) {
 print FATAL:  --server option conflicts with --no-rsyncd!\n;
 print qq(Try $progname --help for more info.\n);
 exit 1;
}

#$firmware_dir=/lib/firmware if(!$firmware_dir);

if(!($system_firmware)) {
 if($firmware_dir) {
 print FATAL:  --firmware-dir option used without 
--include-system-firmware !\n;
 print qq(Try $progname --help for more info.\n);
 exit 1;
 }
} else {
 if( ! -d $firmware_dir) {
 print FATAL:  firmware dir $firmware_dir not found!\n;
 exit 1;
 }
}


--
Subversion Kills Productivity. Get off Subversion  Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
Subversion Kills Productivity. Get off Subversion  Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Re: [sisuite-users] support newer kernels in systemimager?

[LAHAYE Olivier]

Hi Steven,

Latest systemImager that handle kernels up to 3.99 are here:
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/

And more precisely here for other distros:
http://svn.oscar.openclustergroup.org/repos/unstable/

if you want to build from git:
git clone http://github.com/finley/SystemImager.git SystemImager
cd ./SystemImager
sudo make rpm # on rpm based distro
sudo make deb # on a deb based distro
make show_targets # to see all other possibilities
It's preferable to download all depending sources and put those in /usr/src
to do so:
make get_source
sudo cp initrd_source/src/* /usr/src
sudo cp src/* /usr/src

Note, it's a good idea to retreive source before doing a make rpm or make deb. 
upon failure, you don't need to redownload the external sources.

You can find also old versions (4.2.0-0.92svn4568) here:
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/rhel-6-x86_64/ (for rhel6)
http://bison.csm.ornl.gov/repos/unstable (for debians)
But they don't support newer kernels. (the regexp in the code responsible for 
checking kernel version is too restrictive).

You can find examples of postinstall scripts to setup gub, grub2, network, 
keyboard here:
http://olivier.lahaye1.free.fr/OSCAR/systemImager-scripts/
(grub 2 script is not yet perfect)

I'm planing to rework the way the binary templates are done using dracut. that 
way, we'll use server distro  (supported) files. for example, even on a 
redhat-el-6, you will be able to run redhat-6 kernel 2.6 on recent hardware 
(provided that this hardware is supported by redhat). Indeed it makes no sens 
to have a better kernel than the one installed by the distro as once installed 
it wouldn't boot. (of course the UYOK will persist and allow for installing 
custom kernel using post-installscript if you wish, just like it's done today).

Best regards.

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR


De : Steven DuChene [steven.a.duch...@hp.com]
Envoyé : mercredi 19 février 2014 23:06
À : yann aubert
Cc : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] support newer kernels in systemimager?

I tried to access this and the file is not really available.
I actually need the systemimager and other pieces for both RHEL/CentOS
and the Debian pieces. If I just have the debian/Ubuntu parts I cannot
implement my testing infrastructure.

Where can I get 4.2.X SIS/systemimager pieces? Both Debian/Ubuntu deb
packages and the equivalent rpm packages for RHEL/CentOS???
--
Steven DuChene

On 01/20/2014 05:29 AM, yann aubert wrote:
 Hi Brian,


 You can find debian packages here :
 https://ipnfiles.in2p3.fr/373a

 Yann


 On dim., 2014-01-19 at 22:59 -0600, Brian Elliott Finley wrote:
 Steven,

 I'm afraid I'm testing with an unstable version that I'm prepping to
 release, but it's not ready yet.

 Yann -- do you have debs that you have built from your 4.2.x source
 tree?  If so, I'd like to add them to the SystemImager Debian repo and
 get a copy to Steven.

 Thanks, -Brian


 On 2014-01-17, 08:36:14pm, DuChene, Steven A wrote:
 OK, I just checked the debian/Ubuntu  system where I am trying to run 
 si_prepareclient and it has systemimager  v4.1.6 packages installed.
 I notice the patch you sent seems to be from a 4.2.X branch. Where do I get 
 that branch from??? The newest available from the sourceforge files section 
 is 4.1.6 from 2008.

 Is there any place to download this from so I can transfer it to a group of 
 systems that do not have internet access?
 --
 Steven DuChene

 -Original Message-
 From: DuChene, Steven A
 Sent: Friday, January 17, 2014 8:17 AM
 To: Brian Elliott Finley
 Cc: sisuite-users@lists.sourceforge.net
 Subject: Re: [sisuite-users] support newer kernels in systemimager?

 Brian:
 What version of systemimager are you using to do your testing? I am looking 
 on the source forge files area and everything there is very old. Is there 
 some place where you are storing newer versions? I will try the patch you 
 sent though and see if applies cleanly to the bits I have installed.
 --
 Steve

 -Original Message-
 From: Brian Elliott Finley [mailto:br...@thefinleys.com]
 Sent: Sunday, January 12, 2014 9:16 PM
 To: DuChene, Steven A
 Cc: sisuite-users@lists.sourceforge.net
 Subject: Re: [sisuite-users] support newer kernels in systemimager?

 Thanks for the good information, Steven.

 It looks like Yann Aubert may have fixed the parsing issue.  I checked out 
 his repo, and see this in his commit log:

   ┌─[bfinley@bob] ~/src/systemimager.Yann_Aubert/branches/4.2.x/
   └─[$] svn log
   
 
   r4 | aubert | 2011-12-08 07:36:16 -0600 (Thu, 08 Dec 2011) | 2 lines

 -  Fix pvdisplay parsing when column appears in device name

   
 
   r3 | aubert | 2011-12-07 11:58:21 -0600 (Wed, 07 Dec 2011) | 2 

[sisuite-users] RE : RE : support newer kernels in systemimager?

[LAHAYE Olivier]

Hi David, thanks a lot for your support :-)

The latest beta packages are versionned with 4.3.0-0.16. This releases now 
builds with perl files installed in INSTALDIRS=vendor (no more use lib 
/usr/lib/systemimager needed).
This version includes the si_monitortk thread warning fix.
It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/

The package has been built for rhel-6, debian-6, fedora-17

For the future, as I said, I'm looking forward for any info/doc/script on how 
to build such a thing:
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : David Livingstone [david.livingst...@cn.ca]
Date d'envoi : jeudi 23 janvier 2014 21:24
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : support newer kernels in systemimager?

Olivier – 2. Definitely sounds like the way to go …

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Thursday, January 23, 2014 3:00 AM
To: sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] RE : support newer kernels in systemimager?

Hi,

Sorry for not participating often here, I'm extremely buzy working on releasing 
a new stable OSCAR cluster release that will support many distros.

Though, I'm still working on SystemImager. (just fixed si_monitortk thread 
warning)

The current git should support kernels from 2.4 to 3.99 if it ever exists.
We have built beta release here:
http://svn.oscar.openclustergroup.org/repos/unstable/

For more info, here is my analysis of the current situation and what I'd like 
to achieve:

Problem of the current release is that it fails to build template initrd and 
kernel on newer distros (like fedora-18+). The problem is that template initrd 
is based on udev when newer kernels needs latest udev version and build 
mechanism is not yet designed to build udev without systemd from systemd source 
tree.

IMHO, the way to generate templates is not compatible anymore with the variety 
of distros and kernel version. rhel6 is using a 2.6, while other distros are 
using kernel 3.x
Building latest kernel and lvm on an old system (rhel6) using installed system 
kernel includes leads to build failures or runtime crash.

2 solutions for the future:

1/ have different build tree for each distro with apropriate kernel = means 
old distro won't be supported on recent hardware . typically, our vanilla 
kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. = 
bad idea and very difficult to maintain.

2/ drop the idea to build our kernel and initrd from scratch and instead build 
the initrd using dracut. Big benefits:
   a/ we support the same hardware as the linux vendor. even with old kernel.
   b/ building the rpm is far more faster
   c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build 
host system includes.
UYOK would still be possible for users having hardware that is not supported by 
their linux vendor, but for the majority of cases, the templates would be far 
sufficient.

Unfortunately, I'm still searching a doc that tells how to build a non basic 
initrd.
Our case is similar to 
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

= If someone can point me to a page that explains how this image is built, 
that would be AWESOME.

It uses systemd and udev for loading hardware drivers and minimal services like 
network and so. Basicaly it havs everything we need.
Then we would just have to add needed binaries (lvm tools, ...) from installed 
system and (build)our specific stuffs like flamethrower client or bittorent 
client and replace stage2 loader with our rcS and voila! (cleaner, faster, 
higher ...;- )

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Jan Groenewald [j...@aims.ac.za]
Date d'envoi : lundi 20 janvier 2014 07:38
À : 
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] support newer kernels in systemimager?
Hi
This file

0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S 
UseYourOwnKernel.pm
systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
Checks the kernel version and throws an error for newer kernels. This patch 
allows me to use some 3.X kernels

1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat 
UseYourOwnKernel.pm.patch
--- UseYourOwnKernel.pm.orig2012-05-30 17:05:54.899344781 +0200
+++ UseYourOwnKernel.pm 2013-02-18 08:30:56.251862480 +0200
@@ -460,11 +460,12 @@
 #   2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue Nov 19 
15:15:43 CST 2002
 #   2.6.7-1-686 
(dilin...@toaster.hq.voxel.netmailto:dilin...@toaster.hq.voxel.net) #1 Thu 
Jul 8 05:36:53 EDT 2004
 #   2.6.22.5-31-default (geeko@buildhost

[sisuite-users] RE : support newer kernels in systemimager?

[LAHAYE Olivier]

Hi,

Sorry for not participating often here, I'm extremely buzy working on releasing 
a new stable OSCAR cluster release that will support many distros.

Though, I'm still working on SystemImager. (just fixed si_monitortk thread 
warning)

The current git should support kernels from 2.4 to 3.99 if it ever exists.
We have built beta release here:
http://svn.oscar.openclustergroup.org/repos/unstable/

For more info, here is my analysis of the current situation and what I'd like 
to achieve:

Problem of the current release is that it fails to build template initrd and 
kernel on newer distros (like fedora-18+). The problem is that template initrd 
is based on udev when newer kernels needs latest udev version and build 
mechanism is not yet designed to build udev without systemd from systemd source 
tree.

IMHO, the way to generate templates is not compatible anymore with the variety 
of distros and kernel version. rhel6 is using a 2.6, while other distros are 
using kernel 3.x
Building latest kernel and lvm on an old system (rhel6) using installed system 
kernel includes leads to build failures or runtime crash.

2 solutions for the future:

1/ have different build tree for each distro with apropriate kernel = means 
old distro won't be supported on recent hardware . typically, our vanilla 
kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. = 
bad idea and very difficult to maintain.

2/ drop the idea to build our kernel and initrd from scratch and instead build 
the initrd using dracut. Big benefits:
   a/ we support the same hardware as the linux vendor. even with old kernel.
   b/ building the rpm is far more faster
   c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build 
host system includes.
UYOK would still be possible for users having hardware that is not supported by 
their linux vendor, but for the majority of cases, the templates would be far 
sufficient.

Unfortunately, I'm still searching a doc that tells how to build a non basic 
initrd.
Our case is similar to 
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

= If someone can point me to a page that explains how this image is built, 
that would be AWESOME.

It uses systemd and udev for loading hardware drivers and minimal services like 
network and so. Basicaly it havs everything we need.
Then we would just have to add needed binaries (lvm tools, ...) from installed 
system and (build)our specific stuffs like flamethrower client or bittorent 
client and replace stage2 loader with our rcS and voila! (cleaner, faster, 
higher ...;- )

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Jan Groenewald [j...@aims.ac.za]
Date d'envoi : lundi 20 janvier 2014 07:38
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] support newer kernels in systemimager?

Hi

This file

0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S 
UseYourOwnKernel.pm
systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm

Checks the kernel version and throws an error for newer kernels. This patch 
allows me to use some 3.X kernels

1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat 
UseYourOwnKernel.pm.patch
--- UseYourOwnKernel.pm.orig2012-05-30 17:05:54.899344781 +0200
+++ UseYourOwnKernel.pm 2013-02-18 08:30:56.251862480 +0200
@@ -460,11 +460,12 @@
 #   2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue Nov 19 
15:15:43 CST 2002
 #   2.6.7-1-686 
(dilin...@toaster.hq.voxel.netmailto:dilin...@toaster.hq.voxel.net) #1 Thu 
Jul 8 05:36:53 EDT 2004
 #   2.6.22.5-31-default (geeko@buildhost) #1 SMP 
2007/09/21 22:29:00 UTC
+   #   3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 
2012
 #
 my $regex =
 #   | kernel version + build machine
 #   `---
-'(2\.[46]\.\d[^\/]*?) \(.*@.*\) [#]\d+.*' .
+'((2\.[46])|(3\.[0125])\.\d[^\/]*?) \(.*@.*\) 
[#]\d+.*' .
 #
 #   | build date
 #   `---
@@ -739,7 +740,7 @@
 # Find the right way to get modules info.
 my $uname_r = get_uname_r();
 my $modinfo_filename;
-if ($uname_r =~ /^2\.6/) {
+if ($uname_r =~ /(^2\.6)|(^3\.[0125])/) {
 $modinfo_filename = 'modinfo -F filename';
 } elsif ($uname_r =~ /^2\.4/) {
 $modinfo_filename = 'modinfo -n';


It is however already out of date as Ubuntu 12.04 can run 3.2 (linux-generic) 
3.5 (linux-generic-lts-quantal) 3.8 (linux-generic-lts-raring) or 3.11 
(linux-generic-lts-saucy) kernels:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

The patch will fix your problem 

[sisuite-users] RE : beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing

[LAHAYE Olivier]

hi David,

Thanks a lot for your report.
Thanks also for the patch. It is not yet integrated because I want to have a 
deterministic way of managing firmwares. I don't want to end in a situation 
when errors occure because guy A had installed a package and guy B didn't.
I think that the best way for the moment is to add command line switch to 
include system installed firmwares . By this way, the user will known that the 
problem can come from a missing firmware.

For the L switch, I understand that it is needed for the firmware sync, but 
this triggers some problems elsewhere were files a copied twice instead of 
having a link and a file.
using L switch is a quick hack but the image gets even bigger (already very 
big).

I'm aware of both issues, and I'll find a solution.

The freeze problem is more problematic. Did you try without using LVM? If it 
works, then it may be a bad lvm tools build (using system libs instead of 
initrd built libs. I tryed to fix most of them, but lvm may be one of them.

Best regards,

PS: Right now, I'm working on debian systemimager oscar-packager. I'll be back 
soon.

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : mercredi 17 avril 2013 23:31
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 
4.3.0-0.7 available for testing


Olivier,

Finally had a chance to test from a client running beta8 to a server running 
beta8. Both client and server are running rhel 6.4 x86_64.
- I prepared the images as both uyok and without and both worked. No problem 
with the getimage from the server.
- I then attempted to load the client with the image I had created. I attempted 
this with both the standard kernel and the uyok.
  Both worked up to the point in the script when lvcreate was executed. At this 
point the load/system would hang(reset required).
  See the log below. To restore I loaded from a server running a slightly older 
version( systemimager-server-4.3.0-0.2.el6.noarch)
  which did not have this problem.

Also note for reasons I have stated in the past I also modified 
UseYourOwnKernel.pm as follows :

[root@wild1 130408]# diff 
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm UseYourOwnKernel.pm
152c152
 $cmd = qq(rsync -a --exclude=build --exclude=source ) .
---
 $cmd = qq(rsync -aL --exclude=build --exclude=source ) .
159c159
 $cmd = qq(rsync -aR $module $staging_dir);
---
 $cmd = qq(rsync -aLR $module $staging_dir);
222a223,233
 #
 # Copy /lib/firmware file to initrd
 #
 #
 if (-d /lib/firmware) {
# copy firmware tree to new initrd.
$cmd = qq(rsync -aLR /lib/firmware $staging_dir);
!system( $cmd ) or die( Couldn't $cmd. );

 }


Log of failed boot :

parted -s -- /dev/sda set 2 lvm on
logger: logger: parted /dev/sda set 2 lvm on
New partition table for /dev/sda:
parted -s -- /dev/sda print
Model: HP LOGICAL VOLUME (scsi)
Disk /dev/sda: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End SizeType File system  Flags
1  512B1000MB  1000MB  primary   boot
2  1000MB  300GB   299GB   primary   lvm

Load software RAID modules.
Load device mapper driver (for LVM).
Initializing partition /dev/sda2 for use by LVM.
pvcreate -M2 -ff -y /dev/sda2 || shellout
WARNING: Forcing physical volume creation on /dev/sda2 of volume group rootvg
Physical volume /dev/sda2 successfully created
lvremove -f /dev/rootvg /dev/null 21  vgremove rootvg /dev/null 21
vgcreate -M2 -l 0 -p 0 -s 32768K rootvg /dev/sda2 || shellout
Volume group rootvg successfully created
lvcreate -L16777216K -n LogVol01 rootvg || shellout



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/17 15:14 -
From:   david.livingst...@cn.ca
To: sisuite-users@lists.sourceforge.net
Date:   2013/04/10 15:56
Subject:Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 
4.3.0-0.7 available for testing





Olivier,

Thanks. That does it. I still need to test loading the image. I will let you 
know.

David




David K Livingstone
CN Signals and Communications



From:   LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Date:   2013/04/08 06:37
Subject:[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 
4.3.0-0.7 available for testing





Hi,

The issue has been fixed.
I wonder how it could work on V0.2. There were 2 bugs:
One

[sisuite-users] RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

Hi,

In order to install systemimager, you need to install the oscar repository 
index so dependancies can be resolved.

rpm -Uvh 
http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r9868-1.noarch.rpm

Then

yum clean all; yum makecache
yum install systemimager*

Note that  ext4 is supported, but the /boot partition should'nt use this 
filesystem.
Note also that there are some missing firmwares. (only those that are included 
in kernel sources are provided).

If you want to build the rpm from sources, you can fetch missing sources from 
here:
http://olivier.lahaye1.free.fr/SOURCES/ copy them into /usr/src/ or /root/src/
The last srpm is beta10:
http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.3.0-0.10.src.rpm

Here you can find some example post install scripts: 
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

systemimager is still unable to manage grub2 or NetworkManager, but you can use 
post install scripts to do so.
grub1 was not working up to 0.9, but I've fixed some bugs recently, and it may 
work now without using the post install script found in the example scripts. 
Not had time to test.

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Geoffrey Letessier [geoffrey.letess...@ibpc.fr]
Date d'envoi : samedi 13 avril 2013 15:45
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] New systemimager rpms for centos6 with ext4 support

Hello Olivier,

Thanks for your promotion and improvements of SISuite.
I'm currently trying to quickly deploy a new HPC cluster on CentOS6.3[or 4]
with Grub2, LVM and Ext4 features.

I have a very basic experience with SISuite (only one time on an old cluster
on CentOS 5 without aforesaid features) but it seems to miss some
packages like systemconfigurator.

Can you help me to install your groundwork writing me a small install
procedure and also where to get missing packages?
I just need to be able to harvest and deploy a golden node image

Thanks in advance for your help, and one more time for your good works!
Geoffrey
--
CNRS LBT/IBPC



--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis  visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing

[LAHAYE Olivier]

Cool,

Thanks for the report, hopefully, the deployment will succeed.
Note, that you must setup network and bootloader using a post install script.
I've fixed grub1, but grub2 is not supported and NetworkManger is not supported 
as well.

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : mercredi 10 avril 2013 23:56
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 
4.3.0-0.7 available for testing


Olivier,

Thanks. That does it. I still need to test loading the image. I will let you 
know.

David




David K Livingstone
CN Signals and Communications



From:   LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Date:   2013/04/08 06:37
Subject:[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 
4.3.0-0.7 available for testing




Hi,

The issue has been fixed.
I wonder how it could work on V0.2. There were 2 bugs:
One that I introduced when I wanted to match kernel 3.x kernels with x 2
But there was also a bug in initrd detection. the routine was unable to check 
for initramfs files. If no initrd file was available, the error should have 
triggered as well

Anyway,

It's hopefully fixed and should be available shortly for fedora, rhel-6 and 
debian-7-x86_64 soon here:
http://svn.oscar.openclustergroup.org/repos/unstable/

The source rpm (and tarball) will be available here soon as well:
http://svn.oscar.openclustergroup.org/pkgs/downloads/

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : LAHAYE Olivier
Date d'envoi : lundi 8 avril 2013 09:24
À : sisuite-users@lists.sourceforge.net
Objet : RE : [sisuite-users] systemimager 4.3.0-0.7 available for testing


Hi,

Thanks a lot for this report, I'll try to understand the issue ASAP.
0.2 has the same code as 0.7 (differences are on the initrd and boot packages 
which are very different).

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : samedi 6 avril 2013 00:44
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing


Olivier,

I installed on a rhel 6.4 client and get the below error message when 
attempting to prepare the client. If I install
4.3.0-0.2 this does not happen.

systemimager-common-4.3.0-0.7.el6.noarch
systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch
systemimager-client-4.3.0-0.7.el6.noarch


- same error on vccs3 using --no-uyok and without - We get :
  - [root@mtl-vccs03d ~]# si_prepareclient --no-uyok --server 165.115.83.125

...

This client is ready to have its image retrieved.  You must now run
the si_getimage command on your imageserver.

Automatically create configuration file for systemconfigurator:
   /etc/systemconfig/systemconfig.conf
WARNING: unable to auto-detect kernel file!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by 
systemconfigurator)
[root@mtl-vccs03d ~]#



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/05 16:40 -
From:   David Livingstone/LIVING03/CNR/CA
To: sisuite-users@lists.sourceforge.net
Date:   2013/03/21 11:40
Subject:Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing





Olivier,

 Thanks ! I will download and test on rhel 6.x).  BTW I am currently using your 
previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions
 we have corresponded about.

David


David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca


From:   LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Date:   2013/03/20 10:17
Subject:[sisuite-users] systemimager 4.3.0-0.7 available for testing







Hi,

I've uploaded the rpms for systemimager beta version V4.3.0 (beta7)

I've built it for fedora-17 and centos-6.3
They are available here:  
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/

Note that you can install the oscar-release rpm which will setup the 
yum.repo.d/oscar.repo.

Usage notes:
- The pre install script required to modprobe disk controlers is not required 
anymore. (leave comments in it)
- the post install scripts 
(si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

[sisuite-users] RE : systemimager 4.3.0-0.7 available for testing

[LAHAYE Olivier]

Hi,

Thanks a lot for this report, I'll try to understand the issue ASAP.
0.2 has the same code as 0.7 (differences are on the initrd and boot packages 
which are very different).

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : samedi 6 avril 2013 00:44
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing


Olivier,

I installed on a rhel 6.4 client and get the below error message when 
attempting to prepare the client. If I install
4.3.0-0.2 this does not happen.

systemimager-common-4.3.0-0.7.el6.noarch
systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch
systemimager-client-4.3.0-0.7.el6.noarch


- same error on vccs3 using --no-uyok and without - We get :
  - [root@mtl-vccs03d ~]# si_prepareclient --no-uyok --server 165.115.83.125

...

This client is ready to have its image retrieved.  You must now run
the si_getimage command on your imageserver.

Automatically create configuration file for systemconfigurator:
   /etc/systemconfig/systemconfig.conf
WARNING: unable to auto-detect kernel file!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by 
systemconfigurator)
[root@mtl-vccs03d ~]#



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/05 16:40 -
From:   David Livingstone/LIVING03/CNR/CA
To: sisuite-users@lists.sourceforge.net
Date:   2013/03/21 11:40
Subject:Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing




Olivier,

 Thanks ! I will download and test on rhel 6.x).  BTW I am currently using your 
previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions
 we have corresponded about.

David


David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca


From:   LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Date:   2013/03/20 10:17
Subject:[sisuite-users] systemimager 4.3.0-0.7 available for testing






Hi,

I've uploaded the rpms for systemimager beta version V4.3.0 (beta7)

I've built it for fedora-17 and centos-6.3
They are available here:  
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/

Note that you can install the oscar-release rpm which will setup the 
yum.repo.d/oscar.repo.

Usage notes:
- The pre install script required to modprobe disk controlers is not required 
anymore. (leave comments in it)
- the post install scripts 
(si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2)
 are usefull for grub setup (systemconfigurator not yet ported for new grub, 
grub2 and other bootloaders and Network manager) Just comment everything in the 
pre_install script.

Firmwares available in the image are those that can be built from the kernel 
source tree. No external firmware is provided yet (need to check EULA).

Please keep in mind that this is a testing release. If you have a systemimager 
that is in production, don't upgrade).

Happy testing.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users



--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing

[LAHAYE Olivier]

Hi,

The issue has been fixed.
I wonder how it could work on V0.2. There were 2 bugs:
One that I introduced when I wanted to match kernel 3.x kernels with x 2
But there was also a bug in initrd detection. the routine was unable to check 
for initramfs files. If no initrd file was available, the error should have 
triggered as well

Anyway,

It's hopefully fixed and should be available shortly for fedora, rhel-6 and 
debian-7-x86_64 soon here:
http://svn.oscar.openclustergroup.org/repos/unstable/

The source rpm (and tarball) will be available here soon as well:
http://svn.oscar.openclustergroup.org/pkgs/downloads/

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : LAHAYE Olivier
Date d'envoi : lundi 8 avril 2013 09:24
À : sisuite-users@lists.sourceforge.net
Objet : RE : [sisuite-users] systemimager 4.3.0-0.7 available for testing


Hi,

Thanks a lot for this report, I'll try to understand the issue ASAP.
0.2 has the same code as 0.7 (differences are on the initrd and boot packages 
which are very different).

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : samedi 6 avril 2013 00:44
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing


Olivier,

I installed on a rhel 6.4 client and get the below error message when 
attempting to prepare the client. If I install
4.3.0-0.2 this does not happen.

systemimager-common-4.3.0-0.7.el6.noarch
systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch
systemimager-client-4.3.0-0.7.el6.noarch


- same error on vccs3 using --no-uyok and without - We get :
  - [root@mtl-vccs03d ~]# si_prepareclient --no-uyok --server 165.115.83.125

...

This client is ready to have its image retrieved.  You must now run
the si_getimage command on your imageserver.

Automatically create configuration file for systemconfigurator:
   /etc/systemconfig/systemconfig.conf
WARNING: unable to auto-detect kernel file!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by 
systemconfigurator)
[root@mtl-vccs03d ~]#



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/05 16:40 -
From:   David Livingstone/LIVING03/CNR/CA
To: sisuite-users@lists.sourceforge.net
Date:   2013/03/21 11:40
Subject:Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing




Olivier,

 Thanks ! I will download and test on rhel 6.x).  BTW I am currently using your 
previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions
 we have corresponded about.

David


David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca


From:   LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Date:   2013/03/20 10:17
Subject:[sisuite-users] systemimager 4.3.0-0.7 available for testing






Hi,

I've uploaded the rpms for systemimager beta version V4.3.0 (beta7)

I've built it for fedora-17 and centos-6.3
They are available here:  
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/

Note that you can install the oscar-release rpm which will setup the 
yum.repo.d/oscar.repo.

Usage notes:
- The pre install script required to modprobe disk controlers is not required 
anymore. (leave comments in it)
- the post install scripts 
(si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2)
 are usefull for grub setup (systemconfigurator not yet ported for new grub, 
grub2 and other bootloaders and Network manager) Just comment everything in the 
pre_install script.

Firmwares available in the image are those that can be built from the kernel 
source tree. No external firmware is provided yet (need to check EULA).

Please keep in mind that this is a testing release. If you have a systemimager 
that is in production, don't upgrade).

Happy testing.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users



--
Minimize network downtime and maximize

[sisuite-users] systemimager-4.3.0 beta7 for ubuntu-12-x86_64

[LAHAYE Olivier]

Dear all,

I've managed to build a beta7 release for systemiamger-4.3.0 for ubuntu 10.12

- It's not tested.
- The package release is not the goot one (all instead of ubuntu0.7)
- There is no repo yet, but the packages are available here for testing.

You can get the packages here (only for testing purpose).
http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ubuntu-12-x86_64/

As usual, you'll need postinstall scripts to setup the bootloader and the 
network.
You can take ideas from 
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2
You shouldn't need pre install script as hopefully, the hardware is now 
correctly detected.

Best regards,

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] systemimager V4.3.0-0.7: seems to work fine.

[LAHAYE Olivier]

Dear all,

I've finaly managed to build systemimager with recent udev, compatible modprobe 
command from kmod,, recent kernel updated dhcp, more lvm commands, more 
firmwares, most network drivers and disk controler drivers, 
- kernel-3.7.5
- udev-182 (the last one before it is shipped inside systemd)
- dhcp v3.1.3 (V4.* have a bug identified and reported upstream
- many updated tools (initrd is 31MB instead of 22MB)
- hardware is again automatically detected a initialized (no more need for a 
pre install script)

Tested on RHEL-6.3 and Fedora-17

My ISP is currently experiencing issues with the upload gateway. Once fixed, 
I'll upload rpms and srpms for fedora-17 and centos-6.3 for testing.

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] systemimager 4.3.0-0.7 available for testing

[LAHAYE Olivier]

Hi,

I've uploaded the rpms for systemimager beta version V4.3.0 (beta7)

I've built it for fedora-17 and centos-6.3
They are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/

Note that you can install the oscar-release rpm which will setup the 
yum.repo.d/oscar.repo.

Usage notes:
- The pre install script required to modprobe disk controlers is not required 
anymore. (leave comments in it)
- the post install scripts 
(si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2)
 are usefull for grub setup (systemconfigurator not yet ported for new grub, 
grub2 and other bootloaders and Network manager) Just comment everything in the 
pre_install script.

Firmwares available in the image are those that can be built from the kernel 
source tree. No external firmware is provided yet (need to check EULA).

Please keep in mind that this is a testing release. If you have a systemimager 
that is in production, don't upgrade).

Happy testing.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] Need Help: dhclient - No broadcast interfaces found.

[LAHAYE Olivier]

Dear all,

The new systemimager (new boel binaries) is almost finished and seems to works 
really fine on my test machines.
The new udevd works fine and correctly probe hardware, loads firmwares, the 
kernel does not crash, and I was able to reach the dhclient step. I can deploy 
an image if I fix the ip by typing dhclient eth0 and start the deploy script 
by hand.

The problem I have is that the dhclient fails to detect the eth0 interface if 
not specified on the command line (eth0 exists and can be configured).
if I issue a dhclient eth0, it works.
The problem is similar to this thread: 
http://forums.fedoraforum.org/showthread.php?t=252210

Unfortunately, this is an initrd and there is no NetworkManager at all.

So I assume that there is some way to free this interface from NetworkManager, 
but HOW?

- Is it a kernel option I need to enable/disable?
- if yes, will it be obsolete soon?
- Is it a udev option I need to enable/diable?
- if yes, will it be obsolete soon?
- Should I install network manager instead?
- should I write a script that loop on all interfaces shown by ifconfig -a, and 
if the BROADCAST flag is set, then issue a dhclient iface_name ?

Any advise is welcome. If no answer, I'll go for the 6th solution until I can 
find a better one.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : Build trunk

[LAHAYE Olivier]

Hi DongInn,

In fact the systemimager source repository is not up to date.

I've put up to date sources here: 
http://olivier.lahaye1.free.fr/SystemImager/downloads/
If someone could kindly  update the http://download.systemimager.org/pub/ 
directory with the files this would solve the problem for the long term.

For short term build, a simple download of the files in /root/src (you need to 
build as root as the mknod fails when creating the initial ramdisk) will do the 
trick.

To test if it works, just do make get_source.
To test build sub components, just do make xfsprogs_install for example. It 
should download (copy from /root/src) the xfsprog source (and if needed 
dependancies), build dependancies and xfsprogs and install this in the 
initrd_source/build_dir/ . This is convenient to test and debug sub package 
build.

Note: I've updated all .rul files so they all have a package_install rule. 
(some did had one, some other didn't; now, it should be consistent).

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : DongInn Kim [di...@cs.indiana.edu]
Date d'envoi : mercredi 13 février 2013 20:28
À : SystemImager Users
Objet : [sisuite-users] Build trunk

Hi,

It seems that trunk is broken because of the missing tar ball.
[13:32] thumb: trunk $ svn info
Path: .
Working Copy Root Path: /nfs/home/dikim/oscar/systemimager/trunk
URL: https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk
Repository Root: https://systemimager.svn.sourceforge.net/svnroot/systemimager
Repository UUID: 8b493298-60f9-0310-b619-f4cd4bc255a3
Revision: 4569
Node Kind: directory
Schedule: normal
Last Changed Author: olahaye74
Last Changed Rev: 4569
Last Changed Date: 2013-01-07 05:30:50 -0500 (Mon, 07 Jan 2013)

[13:32] thumb: trunk $
[13:32] thumb: trunk $ make all
[ -d /nfs/home/dikim/oscar/systemimager/trunk/src ] || mkdir -p 
/nfs/home/dikim/oscar/systemimager/trunk/src
/nfs/home/dikim/oscar/systemimager/trunk/tools/getsource 
http://download.systemimager.org/pub/linux/linux_2.6.34.1.orig.tar.gz 
/nfs/home/dikim/oscar/systemimager/trunk/src
getsource: Can't find a local copy of linux_2.6.34.1.orig.tar.gz.
getsource: I will try to fetch it from a well known site.  Please copy this
getsource: tarball to one of the following locations to prevent downloading
getsource: the source again and sucking up unnecessary bandwidth:
/u/dikim/oscar/systemimager/trunk
/usr/src
/u/dikim/src
--2013-02-13 13:32:55--  
http://download.systemimager.org/pub/linux/linux_2.6.34.1.orig.tar.gz
Resolving download.systemimager.orghttp://download.systemimager.org 
(download.systemimager.orghttp://download.systemimager.org)... 216.34.181.97
Connecting to download.systemimager.orghttp://download.systemimager.org 
(download.systemimager.orghttp://download.systemimager.org)|216.34.181.97|:80...
 connected.
HTTP request sent, awaiting response... 404 Not Found
2013-02-13 13:32:56 ERROR 404: Not Found.

make: *** 
[/nfs/home/dikim/oscar/systemimager/trunk/src/linux_2.6.34.1.orig.tar.gz] Error 
1
[13:32] thumb: trunk $

Is linux_2.6.34.1.orig.tar.gz a kernel file or systemimager file?

Regards,

--
- DongInn

--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).

[LAHAYE Olivier]

David,

I've updated my rpms 4.3.0-0.3 (currently being built).

- I've applyed your patch regarding the udev start.
- Regarding the firmwares, they were missing for unknown reason. Since I've 
upgraded the kernel to 3.7.2 and enabled many more drivers for disks (hpsa and 
more) and network devices (bnx2, ...), the firmwares that you were missing 
seems to be present in the image.
- Regarding UseYourOwnKernel, I didn't copy the firmwares as with the new 
kernel config, they seem to be included.
- I didn't had a look at the UYOK which doesn't copy the kernel and initrd.img.
- As for the -L option in rsync, I don't know if it's usefull as there are no 
links in the templates trees. If you use another tree, though, I'm not sure if 
the -L option is the way to fixe the issue you are seeing as it may result in 
bigger initrd with duplicate materials. at least a hard link could be a 
solution, though in the 1st place, the issue is caused by a missplaced thing 
and a trick is to create a softlink to hide the issue. Can't you have a tree 
with no soft links?

Could you give a test to these rpms and and test with default kernel?

Many thanks for your help.

Best Regards.

RPMS:
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-bittorrent-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-client-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-common-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-flamethrower-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-i386boot-standard-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-i386initrd_template-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-server-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-x86_64boot-standard-4.3.0-0.3.el6.noarch.rpm
http://olivier.lahaye1.free.fr/RPMS/noarch/systemimager-x86_64initrd_template-4.3.0-0.3.el6.noarch.rpm

SRPMS:
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.3.0-0.3.el6.src.rpm

Scrips:
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2
-- 

   Olivier LAHAYE

   CEA DRT/LIST/DCSI/DIR







De : david.livingst...@cn.ca [david.livingst...@cn.ca]

Date d'envoi : mercredi 16 janvier 2013 23:38

À : sisuite-users@lists.sourceforge.net

Objet : Re: [sisuite-users] RE : Which version ?






Olivier,
 

Thanks. So far I have installed the rpm's on a dl380G7 with rhel6.3 x86_64 and 
both prepared the image(uyok) and retrieved from




 a similar server with the server packages loaded.Next step will be to test 
load the image on another server using both the standard and uyok

( I'm a little gun shy tryingto load back to the same server incase there are 
problems).



I also re-applied the changes I've itemized below for the same reasons - btw 
the change below to rcS(start udev BEFORE load_my_modules) might



address why you had similar problems ie needing the pre-install script to load 
the modules).







 - 



David K Livingstone

CN Signals and Communications

10229 127 Avenue floor 2

Walker Operations East Building

Edmonton, AB, T5E 0B9

Ph  : 780 472-3959 Fax : 780 472-3046

Email: david.livingst...@cn.ca 












From: 
LAHAYE Olivier olivier.lah...@cea.fr



To: 
sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net



Date: 
2013/01/07 02:05 


Subject: 
[sisuite-users] RE :  Which version ?








Hi,

 

You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and 
post-install scripts available here:


http://olivier.lahaye1.free.fr/RPMS/extra/


Cheers,

 


-- 




   Olivier LAHAYE 

   CEA DRT/LIST/DCSI/DIR 



De : david.livingst...@cn.ca [david.livingst...@cn.ca]


Date d'envoi : mercredi 19 décembre 2012 00:09


À : sisuite-users@lists.sourceforge.net


Objet : [sisuite-users] Which version ?




I have been using a modified version of  4.1.99.svn4556_bli-1 to load my i386 
rhel6.x servers as




described below. I am now looking at imaging similar machines but now with the 
x86_64 version


of rhel6.3 so I need like initrd_template( and boot_standard if it works) 
packages.  



What  versions should I be trying ?  

http://olivier.lahaye1.free.fr/RPMS/noarch/
   ?? 

Thanks

 



David K Livingstone



 
CN Signals and Communications
 
10229 127 Avenue floor 2
 
Walker Operations East Building
 
Edmonton, AB, T5E 0B9
 
Ph  : 780 472-3959 Fax : 780 472-3046
 
Email: david.livingst...@cn.ca 

- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 -






From:

David Livingstone/LIVING03/CNR/CA



To:

sisuite-users@lists.sourceforge.net



Date:

2012/03/29 09:41 



Subject:

Loading RHEL 6.2 using 4.1.99.svn4556_bli-1









Using  systemimager  4.1.99.svn4556_bli-1(ext4 enabled version) I have 
successfully imaged a




RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was 
considering using

[sisuite-users] RE : New systemimager rpms for centos6: Missing lvm2

[LAHAYE Olivier]

Hi Ole,

I think that this is fixed now in http://olivier.lahaye1.free.fr/RPMS/noarch/

The RPMS have the same version but are new (4.3.0-0.2), so you need to 
reinstall those with

rpm -Uvh --force systemimager-*rpm

I've checked the inird.img and the templates and all the lvm commands are now 
present.

Please, tell me it it works as I cannot test for the moment.

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : vendredi 11 janvier 2013 13:12
À : sisuite-users@lists.sourceforge.net
Cc: LAHAYE Olivier
Objet : New systemimager rpms for centos6: Missing lvm2

Hi Olivier,

I'm testing your latest systemimager 4.3 RPMs dated 08-Jan-2013 from
http://olivier.lahaye1.free.fr/RPMS/noarch/.  I've generated PXE boot
files in the client's /etc/systemimager/boot/* using si_prepareclient.

However, my CentOS 6.3 clients have been installed with LVM disk
partitions, so the SI master scripts wants to execute various LVM
commands from the lvm2 RPM package.  Unfortunately it seems that the
lvm2 package is missing from the SI initrd.img, so the SI client install
crashes with the error:
pvcreate: not found

Question: Can you add the lvm2 package to SI's building of initrd.img?

Thanks,
Ole

--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark

--
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : New systemimager rpms for centos6: Missing lvm2

[LAHAYE Olivier]

Thanks for the info, I was not using lvm, so I didn't notice. I'll give a look.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : vendredi 11 janvier 2013 13:12
À : sisuite-users@lists.sourceforge.net
Cc: LAHAYE Olivier
Objet : New systemimager rpms for centos6: Missing lvm2

Hi Olivier,

I'm testing your latest systemimager 4.3 RPMs dated 08-Jan-2013 from
http://olivier.lahaye1.free.fr/RPMS/noarch/.  I've generated PXE boot
files in the client's /etc/systemimager/boot/* using si_prepareclient.

However, my CentOS 6.3 clients have been installed with LVM disk
partitions, so the SI master scripts wants to execute various LVM
commands from the lvm2 RPM package.  Unfortunately it seems that the
lvm2 package is missing from the SI initrd.img, so the SI client install
crashes with the error:
pvcreate: not found

Question: Can you add the lvm2 package to SI's building of initrd.img?

Thanks,
Ole

--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark

--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : RE : RE : new centos-6.3 RPMS

[LAHAYE Olivier]

Hi,

Thanks for this :-)

And Happy new year to you.

I've never used git, I hope I'll be able to find a quick start guide and newbee 
guide ;-)

Cheers,
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.com]
Date d'envoi : mardi 18 décembre 2012 19:31
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : RE : new centos-6.3 RPMS

Olivier -- I've added you to github now too.

Cheers, -Brian


On Tue, Dec 18, 2012 at 10:01 AM, LAHAYE Olivier 
olivier.lah...@cea.frmailto:olivier.lah...@cea.fr wrote:

Hi,

Brian, thanks for the svn access, it's cool now that I don't have to maintain 
tons of patches ;-)
My github account is olahaye74.

I've commited my modifications to the svn and tested a build and it worked 
:-) I should say, it built ;-)
So now, as the version is 4.3.0 in the devel tree, the rpm version will be 
4.3.0-0.x
(4.3.0-1 when a release will be created).

rpms available here http://olivier.lahaye1.free.fr/RPMS/noarch/
srpms available here http://olivier.lahaye1.free.fr/SRPMS/

Note that they should behave the same as v 4.2.0-0.91svn4568 as the current 
status is that I've commited the patch into the svn tree and updated the spec 
file to reflect that there is no more patches + minor modifications.
Hopefully I did not miss anything in the process. :-)

The i386initrd_template and i386boot-standard and currently being build, 
unfortunately, I'm on vaccation tonight and will only be back on january 7th, 
if the build process is not finished when I'll have to leave, I'll hybernate my 
VM and let the build finish later.

Best regards,

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.commailto:br...@thefinleys.com]
Date d'envoi : samedi 15 décembre 2012 18:49
À : 
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : new centos-6.3 RPMS

Contributors,

I have added Olivier to the SystemImager project on SourceForge, but I'd like 
to add each of you who want to contribute to the SystemImager project on GitHub 
too, as that's where it will all be moving.

If you don't have an account yet, no big -- just go to https://github.com and 
create one.  Then send me an email with your account name, and I'll get you 
added.

Thanks!

-Brian


On Thu, Nov 29, 2012 at 3:56 AM, LAHAYE Olivier 
olivier.lah...@cea.frmailto:olivier.lah...@cea.fr wrote:
Hi Brian,

My sourceforge username is olahaye74 (Olivier LAHAYE) (74 is because there 
was plenty of olivier.lahaye in France ;-))

I'm very glad to participate. In the meantime, I must let you know that I'm not 
extremely skilled in perl/python and such. I've modified systemimager so it can 
deploy oscar on centos6. The RPMS I've released are ok on centos6, but I've 
discovered that they can't build on centos5. In fact, the build system (initrd) 
after compiling some package does complete the initrd by copying missing libs 
from the build host system. Unfortunately, this behaviour breaks things as we 
have some binaries linked with libs that are too far in versions to be 
compatible (missing simbols).

What I want to say is that I'm a little bit afraid to make modifications that 
could break the whole stuff because my developper skills are not extreme (I'm 
sysadmin in 1st place).

Also I've never participated in such a project and thus I'm not familiar with 
how such modifications can go to the svn. (and I don't want to break things)

For example, I've had to upgrade a component, and to change the build script so 
it makes install instead of copying the resulting binaries as the new version 
uses libtool and the old copying method was copying the wrapper instead of the 
lib itself. This change had an impact to the centos5 compatibility. I mean, my 
modification let the thing build on centos6, but in the meantime, centos5 
became incompatible...

In the end, right now, my rpms cant be build on centos5, though, they can 
deploy any OS. This means that the deploy server must be centos6.

Best resgards.



--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.commailto:br...@thefinleys.com]
Date d'envoi : vendredi 23 novembre 2012 19:10
À : 
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Sun, Olivier,

Please send me your SourceForge usernames.  I appreciate your efforts, and 
would like to grant you both commit privileges to the SVN repository, so that 
you can commit your patches directly.

Bas, Franck, the same goes for you two if you wish.


Regarding a fork, that is generally necessary because one does not have the 
ability to modify the upstream original.  I will happily grant you this access, 
as I think it would be better for the community to improve the main code stream 
rather than

[sisuite-users] RE : Which version ?

[LAHAYE Olivier]

Hi,

You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and 
post-install scripts available here: http://olivier.lahaye1.free.fr/RPMS/extra/

Cheers,


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : mercredi 19 décembre 2012 00:09
À : sisuite-users@lists.sourceforge.net
Objet : [sisuite-users] Which version ?


I have been using a modified version of  4.1.99.svn4556_bli-1 to load my i386 
rhel6.x servers as
described below. I am now looking at imaging similar machines but now with the 
x86_64 version
of rhel6.3 so I need like initrd_template( and boot_standard if it works) 
packages.

What  versions should I be trying ?  
http://olivier.lahaye1.free.fr/RPMS/noarch/   ??

Thanks



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 -
From:   David Livingstone/LIVING03/CNR/CA
To: sisuite-users@lists.sourceforge.net
Date:   2012/03/29 09:41
Subject:Loading RHEL 6.2 using 4.1.99.svn4556_bli-1




Using  systemimager  4.1.99.svn4556_bli-1(ext4 enabled version) I have 
successfully imaged a
RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was 
considering using SALI
however for RHEL6.x grub2 is not an issue and ext4 support is included in  
4.1.99.svn4556_bli-1.

The setup I was imaging is a Proliant DL380G7 server with two p410 
controllers(p401i and p410)
with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The 
system is running
the latest RHEL 6.2.

The attempted to image the system in two ways:
1. standard kernel
2. uyok

1. standard kernel
I eventually got this to work but only after major modifications to the 
install script and manually
setting up grub.  The major issue here is that the default kernel uses the 
cciss driver and
device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa 
driver(scsi naming ex /dev/sda).
See 
http://h2.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf 
 .
In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the 
hpsa when possible.
I presume the standard kernel could be built with the hpsa module and some 
version logic
applied to resolve this.

2. uyok
This worked successfully after making some changes to address :
 - Needed modules(ie hpsa) as symbolic links  under /lib/modules/(uname -r)
   ex
[root@scdev ~]# ls -al 
/lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko
0 lrwxrwxrwx 1 root root 50 Mar  5 04:05 
/lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko - 
/lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko
[root@scdev ~]#
This results in the modules not being copied correctly in the generated 
initrd.
 I resolved this by modifying the UseYourOwnKernel.pm rsync invocations
 to copy the resultant files(the L rather then the l option. I include 
the diff
 below.

- Numerous /lib/firmware files were missing in the initrd. By default the
  bnx2 nic driver(driver for the four nic's on the motherboard) as well as
  others in the RHEL6.2 kernel request firmware which is missing in the
  uyok initrd. I got this to work by :
   - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd.
 Unfortunately this copies all of firmware as I couldn't figure out how 
to
 dynamically copy what was needed.
   - modified rcS under the std template to start udev BEFORE the modules
 are inserted.
- rcS : start udev before loading modules.
   - under the std template :
 
/usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS
- The ramdisk_size must be set high enough to accept the larger initrd.
-  I had to si_cpimage as part of testing and noted that for yuok the
   kernel and initrd.img files are not copied. They had to be copied 
manually.


Notes :
 When creating the image initially  I also had to change si_prepareclient to 
use parted rather then sfdisk. I believe a bug
 was submitted on this a long time ago which was never applied. parted supports 
gpt
 partitions and sfdisk does not.

[root@nasmtl sbin]# diff si_prepareclient 
si_prepareclient.orig.4.1.99.svn4556_bli
969,971c969,971
 #if($arch eq i386) {
 #$preferred_tool = 'sfdisk';
 #}
---
 if($arch eq i386) {
 $preferred_tool = 'sfdisk';
 }

- Diff for UseYourOwnKernel.pm
[root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig
152c152
 $cmd = qq(rsync -aL --exclude=build --exclude=source ) .
---
 $cmd = qq(rsync -a --exclude=build --exclude=source ) .

[sisuite-users] RE : RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

You're perfectly right, a big mistake from my part. I replaced 'Disk' by 
$DISK0 in my script (in order to avoid grepping 2 lines as the new parted now 
outputs Disk flags), but forgot to replace the simple quotes in the script.

Fixed in the svn, but maybe it should also be fixed in the git repos? (I've 
never used git and need time to learn it)

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : jeudi 27 décembre 2012 08:51
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support

Olivier,

Have you updated the line DISK_SIZE=`LC_ALL=C parted -s $DISK0 unit MB print | 
egrep '$DISK0' | awk '{print $NF}' | sed 's/MB//' ` in the .master script? I 
found it can not work in build 4.2.0-0.91svn4568 for redhat6.3.

I think it should be DISK_SIZE=`parted -s $DISK0 unit MB print | egrep 
$DISK0 | awk '{print $NF}' | sed 's/MB//' `, use  instead of '' around 
$DISK0, so shell can translate it.
I tested this fix, it can work.

Thx.
Jing





LAHAYE Olivier olivier.lah...@cea.fr

2012/12/18 17:03


To
Jing CDL Sun/China/IBM@IBMCN,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de...@lists.sourceforge.net, sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Subject
RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 
support








Jing,

You're perfectly right, the ext4 problem was related to default initrd. The 
build did not enable the ext4 module. It's fixed in last build.

Cheers,

Olivier.

--
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR


De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Thx for the reply.

When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, 
so I'm thinking maybe this is not a missing module problem?

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean 
the default initrd? because it seems  4.2.0-0.9svn4568 worked fine for me 
without the ext4 issue.

Yes, I did not use the systemimager default kernel and initrd, instead, I'm 
using my own kernel/initrd got from my golder client, it's rhel6.3, so I think 
it should work fine, right?





LAHAYE Olivier olivier.lah...@cea.fr
2012/12/17 17:16
To
Jing CDL Sun/China/IBM@IBMCN,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de...@lists.sourceforge.net, sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Subject
RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support










This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the 
systemimager initrd fails to automaticaly do that (did not have time to look at 
the problem).

if you did use the script, it means that you need to modify it to have more 
modules inserted. Or, if your hardware is too recent (not supported by provided 
 default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some 
utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build 
will copy missing stuffs from /lib /lib64 and other places and thoses version 
are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from 
system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy 
the build process so it builds everything and link everything with it's 
material which is not fully the case for now. (it still copy stuffs from the 
build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
 Olivier LAHAYE
 CEA DRT/LIST/DCSI/DIR


De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || 
shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing

LAHAYE Olivier olivier.lah...@cea.fr
2012/12/13 22:47
To
sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de

[sisuite-users] RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

Jing,

You're perfectly right, the ext4 problem was related to default initrd. The 
build did not enable the ext4 module. It's fixed in last build.

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Thx for the reply.

When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, 
so I'm thinking maybe this is not a missing module problem?

When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean 
the default initrd? because it seems  4.2.0-0.9svn4568 worked fine for me 
without the ext4 issue.

Yes, I did not use the systemimager default kernel and initrd, instead, I'm 
using my own kernel/initrd got from my golder client, it's rhel6.3, so I think 
it should work fine, right?






LAHAYE Olivier olivier.lah...@cea.fr

2012/12/17 17:16


To
Jing CDL Sun/China/IBM@IBMCN,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de...@lists.sourceforge.net, sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net
Subject
RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support








This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the 
systemimager initrd fails to automaticaly do that (did not have time to look at 
the problem).

if you did use the script, it means that you need to modify it to have more 
modules inserted. Or, if your hardware is too recent (not supported by provided 
 default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some 
utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build 
will copy missing stuffs from /lib /lib64 and other places and thoses version 
are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from 
system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy 
the build process so it builds everything and link everything with it's 
material which is not fully the case for now. (it still copy stuffs from the 
build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
  Olivier LAHAYE
  CEA DRT/LIST/DCSI/DIR


De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || 
shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing


LAHAYE Olivier olivier.lah...@cea.fr
2012/12/13 22:47
To
sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de...@lists.sourceforge.net
Subject
[Sisuite-devel] New systemimager rpms for centos6 with ext4 support










Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to 
setup grub, network and other stuffs as systemconfiguratior is unable to handle 
latest linux technologies.

Best regards,

Olivier
--
 Olivier LAHAYE
 CEA 
DRT/LIST/DCSI/DIR--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d___
sisuite-devel mailing list
sisuite-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency

[sisuite-users] RE : RE : new centos-6.3 RPMS

[LAHAYE Olivier]

Hi,

Brian, thanks for the svn access, it's cool now that I don't have to maintain 
tons of patches ;-)
My github account is olahaye74.

I've commited my modifications to the svn and tested a build and it worked 
:-) I should say, it built ;-)
So now, as the version is 4.3.0 in the devel tree, the rpm version will be 
4.3.0-0.x
(4.3.0-1 when a release will be created).

rpms available here http://olivier.lahaye1.free.fr/RPMS/noarch/
srpms available here http://olivier.lahaye1.free.fr/SRPMS/

Note that they should behave the same as v 4.2.0-0.91svn4568 as the current 
status is that I've commited the patch into the svn tree and updated the spec 
file to reflect that there is no more patches + minor modifications.
Hopefully I did not miss anything in the process. :-)

The i386initrd_template and i386boot-standard and currently being build, 
unfortunately, I'm on vaccation tonight and will only be back on january 7th, 
if the build process is not finished when I'll have to leave, I'll hybernate my 
VM and let the build finish later.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.com]
Date d'envoi : samedi 15 décembre 2012 18:49
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : new centos-6.3 RPMS

Contributors,

I have added Olivier to the SystemImager project on SourceForge, but I'd like 
to add each of you who want to contribute to the SystemImager project on GitHub 
too, as that's where it will all be moving.

If you don't have an account yet, no big -- just go to https://github.com and 
create one.  Then send me an email with your account name, and I'll get you 
added.

Thanks!

-Brian


On Thu, Nov 29, 2012 at 3:56 AM, LAHAYE Olivier 
olivier.lah...@cea.frmailto:olivier.lah...@cea.fr wrote:
Hi Brian,

My sourceforge username is olahaye74 (Olivier LAHAYE) (74 is because there 
was plenty of olivier.lahaye in France ;-))

I'm very glad to participate. In the meantime, I must let you know that I'm not 
extremely skilled in perl/python and such. I've modified systemimager so it can 
deploy oscar on centos6. The RPMS I've released are ok on centos6, but I've 
discovered that they can't build on centos5. In fact, the build system (initrd) 
after compiling some package does complete the initrd by copying missing libs 
from the build host system. Unfortunately, this behaviour breaks things as we 
have some binaries linked with libs that are too far in versions to be 
compatible (missing simbols).

What I want to say is that I'm a little bit afraid to make modifications that 
could break the whole stuff because my developper skills are not extreme (I'm 
sysadmin in 1st place).

Also I've never participated in such a project and thus I'm not familiar with 
how such modifications can go to the svn. (and I don't want to break things)

For example, I've had to upgrade a component, and to change the build script so 
it makes install instead of copying the resulting binaries as the new version 
uses libtool and the old copying method was copying the wrapper instead of the 
lib itself. This change had an impact to the centos5 compatibility. I mean, my 
modification let the thing build on centos6, but in the meantime, centos5 
became incompatible...

In the end, right now, my rpms cant be build on centos5, though, they can 
deploy any OS. This means that the deploy server must be centos6.

Best resgards.



--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.commailto:br...@thefinleys.com]
Date d'envoi : vendredi 23 novembre 2012 19:10
À : 
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Sun, Olivier,

Please send me your SourceForge usernames.  I appreciate your efforts, and 
would like to grant you both commit privileges to the SVN repository, so that 
you can commit your patches directly.

Bas, Franck, the same goes for you two if you wish.


Regarding a fork, that is generally necessary because one does not have the 
ability to modify the upstream original.  I will happily grant you this access, 
as I think it would be better for the community to improve the main code stream 
rather than to have a fork.  I know that SALI has special circumstances that 
made a fork appropriate for them, at least previously, but I would also be 
happy to allow that fork to merge into the mainstream if SALI considers that 
desirable.


Lastly, with regard to SystemConfigurator, it is no longer being maintained, 
and we should work to eliminate our dependency on it.  With modern Linuxes this 
should be very feasible through the use of SystemImager postscripts for setup 
of boot manager (Grub) and networking (if desirable).


All -- feel free to call me if you have any questions.  Just bear in mind that 
I'm generally somewhere in GMT-5 through GMT-7

[sisuite-users] RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

This means that your disk is not recognized.

Did you use my install scripts (especially the pre-install).
http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

It modprobs some modules in order to see disks. I don't know my the 
systemimager initrd fails to automaticaly do that (did not have time to look at 
the problem).

if you did use the script, it means that you need to modify it to have more 
modules inserted. Or, if your hardware is too recent (not supported by provided 
 default kernel), then you'll need to use your own kernel for the moment.

I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some 
utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build 
will copy missing stuffs from /lib /lib64 and other places and thoses version 
are for a 2.6.x kernel, not a 3.X kernel.
This is also the reason why build fails on CentOS5 cas the libs copied from 
system misses some symbols (too old).

In order to safely upgrade systemimager to latest kernel, we need to modifiy 
the build process so it builds everything and link everything with it's 
material which is not fully the case for now. (it still copy stuffs from the 
build system root tree (convenient ugly dirty hack)).

Hope this helps,

Cheers,

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

Hi,

I just tested these new rpms, but found the issues below, the install broken.

Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || 
shellout
Dec 17 14:42:36 x3550m4n02 kernel:  sda: unknown partition table


Thx.
Jing



LAHAYE Olivier olivier.lah...@cea.fr

2012/12/13 22:47


To
sisuite-users@lists.sourceforge.net 
sisuite-users@lists.sourceforge.net,
cc
sisuite-de...@lists.sourceforge.net 
sisuite-de...@lists.sourceforge.net
Subject
[Sisuite-devel] New systemimager rpms for centos6 with ext4 support








Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to 
setup grub, network and other stuffs as systemconfiguratior is unable to handle 
latest linux technologies.

Best regards,

Olivier
--
  Olivier LAHAYE
  CEA 
DRT/LIST/DCSI/DIR--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d___
sisuite-devel mailing list
sisuite-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : RE : RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

Ole, you're perfectly right,

Looking at 
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/pdf/Package_Manifest/Red_Hat_Enterprise_Linux-6-Package_Manifest-en-US.pdf
 I see none of the required packages.
Wow, this is realy wired. no static libc in RHEL6?. So no way to create a 
static binary from RHEL6?

Regarding the spec file from 
http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/glibc-2.12-1.80.el6_3.6.src.rpm
 , the static package should be built. Did redhat removed it by hand?

Regarding device-mapper-devel, the package is created from 
http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/lvm2-2.02.72-8.el6_0.4.src.rpm
= Same as above? did redhat removed the package?

And, as you said, the gperf package has an src.rpm.but no binary and not in the 
list of rhel6 packages.

As for the real requirements, I think they are all required 
unfortunately:(though maybe I'm wrong and maybe we could modify source to avoid 
those requirements; honestly I can't tell for now)

1/ GPERF: 
./initrd_source/build_dir/lib/modules/2.6.34.1-boel_v4.3.0/build/scripts/kconfig/Makefile:#
 The following requires flex/bison/gperf

2/ DEVICE-MAPPER-DEVEL: 
./autoconf/configure.ac:AC_CHECK_HEADERS([libdevmapper.h],[have_libdevmapper=yes])

3/ GLIBS-STATIC: 
./build_dir/lib/modules/2.6.34.1-boel_v4.3.0/build/kernel/exit.c: * implemented 
by calling sys_wait4() from libc.a.


I'm confident that if you rpmbuild --rebuild the missing packages (glibc, lvm2 
and gperf), you should obtain the missing packages. I understand that it's not 
a perfect situation, but for now I'm afraid that it's the way to go.

Maybe redhat has other optional repositories available? Looking at the packages 
list, only 3 static packages. maybe all static packages are on a specific 
repository? Or maybe redhat has removed most of them because of that: 
http://www.linuxtopia.org/online_books/rhel6/rhel_6_developer_guide/rhel_6_developer_lib.compatibility.static.html
(I'm sorry, I don't even have a single redhat system since V4 as I had poor 
experience with support and things like this one, though I can easily 
understand that rhel is mandatory for you)

hope this helps a little bit.

Best regards,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : lundi 17 décembre 2012 14:51
À : sisuite-users@lists.sourceforge.net
Cc: LAHAYE Olivier
Objet : Re: RE : [sisuite-users] RE : New systemimager rpms for centos6 with 
ext4 support

Hi Olivier,

 This is wired and I'm using standard distro CentOS-6 which is said to be a 
 full RHEL-6 clone.

In theory yes, but it seems there are differences!!  I looked up the
missing packages in the Red Hat Network (RHN):

 Don't you have the following packages? (they should be part of RHEL6)
 - gperf-3.0.3-9.1.el6.x86_64

gperf is in CentOS 6.3, but NOT in RHEL 6.3!

Strangely, Red Hat does have the source RPM in
http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ but
there are no binary RPMs from RHN.

 - glibc-static-2.12-1.80.el6_3.6.x86_64

glibc-static is in CentOS 6.3, but NOT in RHEL 5 or 6!

 - device-mapper-devel-1.02.74-10.el6_3.3.x86_64

device-mapper-devel is in CentOS 6.3, but NOT in RHEL 5 or 6!

Unfortunately these differences are *not* documented in
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.3.  I wonder if
anyone can explain why CentOS decided to build these packages?

I assume that you *really* need these packages for SystemImager?  It
would be better for RHEL6 sites if they could be omitted.

If we must install these packages on RHEL6, I propose that documentation
should be written referring people to the RPM downloads from CentOS mirrors.

Thanks,
Ole

--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

Dear all,

Here are my fixed systemimager rpms for centos-6.3
Now, the ext4 filesystem is fixed (the module was missing in the initrd image)
I've tested this on recent hardware and it worked like a charm.

Thoses RPMS are for testing purpose


RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
SRPMS: 
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

PS: Keep in mind that you need postinstall scripts (already posted here) to 
setup grub, network and other stuffs as systemconfiguratior is unable to handle 
latest linux technologies.

Best regards,

Olivier
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : New systemimager rpms for centos6 with ext4 support

[LAHAYE Olivier]

Hi Ole,

Thanks a lot for your support.
Here are the scripts I'm using. Note that you may not need all scripts.
Also note that you may need to edit the script (E;g. I use google DNS ip 
instead of my site ones ;-) )

http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2

Hopefully, systemconfiguration will be back to life one day as it's cool to 
have a system able to configure those stuffs without depending of the distro. 
(saldy I have no time at the moment for that).

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : jeudi 13 décembre 2012 15:53
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] New systemimager rpms for centos6 with ext4 support

Dear Olivier,

You're doing wonderful work!  I really want to test your SI setup with
CentOS6.

For completeness, could you kindly repost the link to your postinstall
scripts?  It's really difficult to find these things, so it helps people
if a complete package is presented.

Thanks,
Ole

On 12/13/2012 03:47 PM, LAHAYE Olivier wrote:

 Dear all,

 Here are my fixed systemimager rpms for centos-6.3
 Now, the ext4 filesystem is fixed (the module was missing in the initrd
 image)
 I've tested this on recent hardware and it worked like a charm.

 Thoses RPMS are for testing purpose


 RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch
 SRPMS:
 http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm

 PS: Keep in mind that you need postinstall scripts (already posted here)
 to setup grub, network and other stuffs as systemconfiguratior is unable
 to handle latest linux technologies.

 Best regards,

 Olivier
 --
 Olivier LAHAYE
 CEA DRT/LIST/DCSI/DIR


 --
 LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
 Remotely access PCs and mobile devices and provide instant support
 Improve your efficiency, and focus on delivering more value-add services
 Discover what IT Professionals Know. Rescue delivers
 http://p.sf.net/sfu/logmein_12329d2d



 ___
 sisuite-users mailing list
 sisuite-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sisuite-users


--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark,
Building 307, DK-2800 Kongens Lyngby, Denmark
E-mail: ole.h.niel...@fysik.dtu.dk
Homepage: http://www.fysik.dtu.dk/~ohnielse/
Tel: (+45) 4525 3187 / Mobile (+45) 5180 1620 / Fax: (+45) 4593 2399

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : new centos-6.3 RPMS

[LAHAYE Olivier]

Hi Brian,

My sourceforge username is olahaye74 (Olivier LAHAYE) (74 is because there 
was plenty of olivier.lahaye in France ;-))

I'm very glad to participate. In the meantime, I must let you know that I'm not 
extremely skilled in perl/python and such. I've modified systemimager so it can 
deploy oscar on centos6. The RPMS I've released are ok on centos6, but I've 
discovered that they can't build on centos5. In fact, the build system (initrd) 
after compiling some package does complete the initrd by copying missing libs 
from the build host system. Unfortunately, this behaviour breaks things as we 
have some binaries linked with libs that are too far in versions to be 
compatible (missing simbols).

What I want to say is that I'm a little bit afraid to make modifications that 
could break the whole stuff because my developper skills are not extreme (I'm 
sysadmin in 1st place).

Also I've never participated in such a project and thus I'm not familiar with 
how such modifications can go to the svn. (and I don't want to break things)

For example, I've had to upgrade a component, and to change the build script so 
it makes install instead of copying the resulting binaries as the new version 
uses libtool and the old copying method was copying the wrapper instead of the 
lib itself. This change had an impact to the centos5 compatibility. I mean, my 
modification let the thing build on centos6, but in the meantime, centos5 
became incompatible...

In the end, right now, my rpms cant be build on centos5, though, they can 
deploy any OS. This means that the deploy server must be centos6.

Best resgards.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Brian Elliott Finley [br...@thefinleys.com]
Date d'envoi : vendredi 23 novembre 2012 19:10
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Sun, Olivier,

Please send me your SourceForge usernames.  I appreciate your efforts, and 
would like to grant you both commit privileges to the SVN repository, so that 
you can commit your patches directly.

Bas, Franck, the same goes for you two if you wish.


Regarding a fork, that is generally necessary because one does not have the 
ability to modify the upstream original.  I will happily grant you this access, 
as I think it would be better for the community to improve the main code stream 
rather than to have a fork.  I know that SALI has special circumstances that 
made a fork appropriate for them, at least previously, but I would also be 
happy to allow that fork to merge into the mainstream if SALI considers that 
desirable.


Lastly, with regard to SystemConfigurator, it is no longer being maintained, 
and we should work to eliminate our dependency on it.  With modern Linuxes this 
should be very feasible through the use of SystemImager postscripts for setup 
of boot manager (Grub) and networking (if desirable).


All -- feel free to call me if you have any questions.  Just bear in mind that 
I'm generally somewhere in GMT-5 through GMT-7. ;-)  If unsure, start with a 
text message, or leave a voice mail if I don't answer right away, but I'll be 
glad to discuss.  My mobile is 469.444.0167.


Cheers, -Brian





On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun 
sj...@cn.ibm.commailto:sj...@cn.ibm.com wrote:
Hi Olivier,

Thanks for this sharing!

Have you cloning Centos-6.3 with these rpms successfully? I tried to use them 
for redhat6.3 cloning, bug failed...

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users




--
Brian Elliott Finley
Mobile: 469.444.0167
--
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : new centos-6.3 RPMS

[LAHAYE Olivier]

Hi,

After retesting (yesterday) the posted rpm, I made a mistake in the script 
generation. The provided partimage is more verbose than the previous one and 
parsing the output is different. I'll rebuild the rpm and repost them ASAP.
(or, if you want to test now, juste replace the '^Disk ' with $DISK0 in the 
DISK_SIZE computation). It should work.

Cheers.

To my knowledge, SALI is a fork of systemimager without systemconfigurator but 
with support for grub2 and new technologies.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : vendredi 23 novembre 2012 04:18
À : sisuite-users
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Thx Olivier!

I did not try the postscripts yet, actually I did not realize them until you 
told me :) I found them in another mail thread, will try them and let you know 
if they work for me.

BTW, I found the new initrd.img generated by SI 4.2.0 is much bigger than the 
one generated by SI 4.0.2, then is there any recommended ramdisk_size and 
tmpfs_size for the kernel parameters? where can I find the change lists or 
release notes so I can know what's actually updated from 4.0.2 to 4.2.0?

I'm new for this project, what's SALI? is it another cloning tool?

Thx.
Jing.
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : new centos-6.3 RPMS

[LAHAYE Olivier]

It looks wired. I neved had that. The transfer speed seems very slow.
maybe an network autoneg problem.
Do you have the same output on the physical console and on the

/usr/sbin/si_monitortk --progress ?

Do you have a # prompt on the physiscal consol (trying to issue a CTRL-C) ?

Olivier.


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : vendredi 23 novembre 2012 09:57
À : Jing CDL Sun
Cc : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Hi,

I got the console output as below during the rsync, then the console hung, it 
seems the image is not completely synced, but failed with no error. Have you 
ever seen this?


xcatpost/rmcmon/scripts/errmsgque
xcatpost/rmcmon/scripts/mkrmcresources
xcatpost/rmcmon/scripts/monerrorlog

sent 959338 bytes  received 808895236 bytes  3325891.47 bytes/sec
total size is 826180881  speedup is 1.02
receiving incremental file list
./

sent 34 bytes  received 56 bytes  180.00 bytes/sec
total size is 0  speedup is 0.00
receiving incremental file list

sent 4 bytes  received 6 bytes  20.00 bytes/sec
total size is 0  speedup is 0.00
receiving incremental file list

sent 4 bytes  received 6 bytes  6.67 bytes/sec
total size is 0  speedup is 0.00





Best Regards,
-
Sun Jing(孙靖)
IBM China Software Development Laboratory
Tel: (86-10) 82453625   E-mail: sj...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
 No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC

北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193



Jing CDL Sun/China/IBM

2012/11/23 11:18


To
sisuite-users@lists.sourceforge.net.,
cc

Subject
Re: [sisuite-users] new centos-6.3 
RPMS链接Notes://D23M0037/482571B8003D5139/DABA975B9FB113EB852564B5001283EA/0AB64B1E071ADAC848257ABD0027C1A6






Thx Olivier!

I did not try the postscripts yet, actually I did not realize them until you 
told me :) I found them in another mail thread, will try them and let you know 
if they work for me.

BTW, I found the new initrd.img generated by SI 4.2.0 is much bigger than the 
one generated by SI 4.0.2, then is there any recommended ramdisk_size and 
tmpfs_size for the kernel parameters? where can I find the change lists or 
release notes so I can know what's actually updated from 4.0.2 to 4.2.0?

I'm new for this project, what's SALI? is it another cloning tool?

Thx.
Jing.
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : new centos-6.3 RPMS

[LAHAYE Olivier]

I've updated my RPMS (fixed the generation of the master script).
I've successfully deployed 23 HP_DL165G7 with oscar-6.2beta successuflly.
si_monitortk --progess even report the REBOOTED status properly.

the rpms are available here:
http://olivier.lahaye1.free.fr/RPMS/noarch

http://olivier.lahaye1.free.fr/SRPMS/ (if you want to rebuild yourself and 
examine the rpms and patches applyed).

Happy deployment,

Cheers,

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : vendredi 23 novembre 2012 09:57
À : Jing CDL Sun
Cc : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] new centos-6.3 RPMS

Hi,

I got the console output as below during the rsync, then the console hung, it 
seems the image is not completely synced, but failed with no error. Have you 
ever seen this?


xcatpost/rmcmon/scripts/errmsgque
xcatpost/rmcmon/scripts/mkrmcresources
xcatpost/rmcmon/scripts/monerrorlog

sent 959338 bytes  received 808895236 bytes  3325891.47 bytes/sec
total size is 826180881  speedup is 1.02
receiving incremental file list
./

sent 34 bytes  received 56 bytes  180.00 bytes/sec
total size is 0  speedup is 0.00
receiving incremental file list

sent 4 bytes  received 6 bytes  20.00 bytes/sec
total size is 0  speedup is 0.00
receiving incremental file list

sent 4 bytes  received 6 bytes  6.67 bytes/sec
total size is 0  speedup is 0.00





Best Regards,
-
Sun Jing(孙靖)
IBM China Software Development Laboratory
Tel: (86-10) 82453625   E-mail: sj...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
 No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC

北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193



Jing CDL Sun/China/IBM

2012/11/23 11:18


To
sisuite-users@lists.sourceforge.net.,
cc

Subject
Re: [sisuite-users] new centos-6.3 
RPMS链接Notes://D23M0037/482571B8003D5139/DABA975B9FB113EB852564B5001283EA/0AB64B1E071ADAC848257ABD0027C1A6






Thx Olivier!

I did not try the postscripts yet, actually I did not realize them until you 
told me :) I found them in another mail thread, will try them and let you know 
if they work for me.

BTW, I found the new initrd.img generated by SI 4.2.0 is much bigger than the 
one generated by SI 4.0.2, then is there any recommended ramdisk_size and 
tmpfs_size for the kernel parameters? where can I find the change lists or 
release notes so I can know what's actually updated from 4.0.2 to 4.2.0?

I'm new for this project, what's SALI? is it another cloning tool?

Thx.
Jing.
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : new centos-6.3 RPMS

[LAHAYE Olivier]

Hi,

I've successfully deployed my oscar images with those rpms.
But I needed some post install scripts in order to have the grub bootloader 
installed.
I've posted the postinstall script as well did you used them?

Can you post a description of the problem you encountered? I must admit I feel 
a little bit alone and feedback is welcome.

I'd also be very happy if a developper could revew my patches and if ok commit 
them to the svn.

Cheers,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

De : Jing CDL Sun [sj...@cn.ibm.com]
Date d'envoi : mercredi 21 novembre 2012 08:16
À : sisuite-users
Objet : [sisuite-users] new centos-6.3 RPMS

Hi Olivier,

Thanks for this sharing!

Have you cloning Centos-6.3 with these rpms successfully? I tried to use them 
for redhat6.3 cloning, bug failed...
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] 95all.monitord_rebooted replacement

[LAHAYE Olivier]

Hi,

I've fully rewrote this post-install script so it works under RHEL distros.

What are the changes:
- SysVInit script is used whenever it is supported (n ot only on debian)
- chkconfig is used whenever it is possible (no manual links except on debian 
system when checkconfig util is not installed)
- lots of cleanup
- should be easy to port to systemd when required.

Note: IMHO, this script shouldn't be in post install.
Instead it should be at the end of the code running those scripts.

Cheers,

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : upgrade parted in systemimager to v3.1 (LAHAYE Olivier)

[LAHAYE Olivier]

Yes, I'm working on systemimager for centos-6.3 and I've ported OSCAR to this 
system as well with GPU support. (working on my own svn repos for oscar for the 
moment)

Right now, systemimager build and runs on centos-6.3 and I'm able to deploy 
oscar using it.
Though, some issues (that can be easily fixed) are still present.

Note also that systemconfigurator needs a lot of work.
It does not support centos-6, thus some post install scripts are required for:
- network config
- initramfs rebuild
- grub install

See attachement for scripts. Names are pretty self explanatory. WARNING, they 
were made for personal purpose and aimed at OSCAR deployment. They surely need 
at least a revew!
script 01all.insmod_script is a pre-install script to enable usb keyboards and 
permit acces upon failure if using an usb keyboard. it also for sata module to 
load so disks are properly detected.

RPMS are available for testing here:
http://olivier.lahaye1.free.fr/RPMS/noarch/ (use release 0.7svn4568)

Please make sure as well that you're allowed to use specific components like 
bittorent in your country before installing.

Best regards.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR


De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : mercredi 7 novembre 2012 11:02
À : sisuite-users@lists.sourceforge.net
Cc : LAHAYE Olivier
Objet : Re: upgrade parted in systemimager to v3.1 (LAHAYE Olivier)

Hi Olivier,

It's really fantastic that you're working out how to fix SystemImager so
that it'll support cloning of CentOS 6.x systems!!  I think a lot of
sites have moved from CentOS5 to CentOS6, and we really need
SystemImager for our clusters!

I wonder if you have systemimager-* RPM packages available which we
could test, until the powers that control the SI SVN server get around
to installing your patches?

Thanks a lot,
Ole

--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark


15all.grub_install
Description: 15all.grub_install


16all.network_config
Description: 16all.network_config


17all.keyboard_fr
Description: 17all.keyboard_fr


81all.fix_bad_initrd
Description: 81all.fix_bad_initrd


90all.yum_update
Description: 90all.yum_update


01all.insmod_script
Description: 01all.insmod_script
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] upgrade parted in systemimager to v3.1

[LAHAYE Olivier]

Hi,

When creating new set of rpms for centos-6.3, I just found a problem when 
imaging clients in the initrd image.
In fact, it looks like I'm hitting a bug very similar to:
https://bugzilla.redhat.com/show_bug.cgi?id=441244

This can be overrided by replacing line 578 in Server.pm:
$startMB{$m} = q($END_OF_LAST_LOGICAL);
by
$startMB{$m} = q#$(echo scale=3; ($END_OF_LAST_LOGICAL + 1) | bc)#;

But this is a ugly patch as you loose 1 block on the disk.

Now I think that the latest parted (v3.1) may fix this issue.
anyway, fixed or not, I4ve successfully bult a new set of rpms with v3.1.
Here is the small patch the build v3.1 instead of v2.3 (attached).


Also attached, the ugly patch (which IMHO, shouldn't be pushed as IMHO, parted 
v3.1 fixes it).

If someone with write access to the SVN think it's worth pushing the 
parted-v3.1 patch, please do so.

I'll test ASAP and report.

Cheers,

PS: With this RPMS I was able to fully deploy a beta OSCAR cluster on 
centos-6.3 (hardware: tyan motherboards with 7 M2090 GPUs and HP DL165 G7

PPS: I'm using post install scripts to replace missing components of 
systeconfigurator (network config, grub install, initramfs update)
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
Index: initrd_source/make.d/parted.rul
===
--- initrd_source/make.d/parted.rul	(révision 4568)
+++ initrd_source/make.d/parted.rul	(copie de travail)
@@ -6,8 +6,10 @@
 #   - go to 1.6.19
 #   2010.06.13  Brian Elliott Filney
 #   - go to 2.3
+#   2012.11.06  Olivier Lahaye
+#   - go to 3.1 (need to avoid redhat bug 441244)
 
-PARTED_VERSION := 2.3
+PARTED_VERSION := 3.1
 PARTED_TARBALL := parted-$(PARTED_VERSION).tar.xz
 #PARTED_URL := http://ftp.gnu.org/gnu/parted/$(PARTED_TARBALL)
 PARTED_URL := http://download.systemimager.org/pub/parted/$(PARTED_TARBALL)
Index: lib/SystemImager/Server.pm
===
--- lib/SystemImager/Server.pm	(révision 4568)
+++ lib/SystemImager/Server.pm	(copie de travail)
@@ -578,7 +578,12 @@
 $startMB{$m} = q($END_OF_LAST_PRIMARY);
 
 } elsif ($p_type{$m} eq logical) {
-$startMB{$m} = q($END_OF_LAST_LOGICAL);
+# $startMB{$m} = q($END_OF_LAST_LOGICAL);
+# Fix parted extended partition table kernel reload error: -OL-
+# Warning: The kernel was unable to re-read the partition table...
+# Maybe related to bug https://bugzilla.redhat.com/show_bug.cgi?id=441244
+# = TEMPORARY FIX until parted get fixed.
+$startMB{$m} = q#$(echo scale=3; ($END_OF_LAST_LOGICAL + 1) | bc)#;
 }
 
 if (($unit_of_measurement eq mb) 
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] initrd.rul 64bit fix patch

[LAHAYE Olivier]

hi,

On system with empty /lib/ld* , the initrd.rul will fail.
this patch avoid to fail in this situation.

If someone with write access to the svn could commit this fix, it would be cool.

PS: this fix has been successfully tested on centos-6.3 (building the rpm in 
order to deploy my OSCAR cluster on centos-6.3)

Cheers,

Olivier.
--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
Index: initrd_source/initrd.rul
===
--- initrd_source/initrd.rul	(révision 4568)
+++ initrd_source/initrd.rul	(copie de travail)
@@ -158,7 +158,7 @@
 $(ZLIB_DIR).install
 
 	# Copy over the standard libs. -BEF-
-	cp -a /lib/ld*   $(INITRD_BUILD_DIR)/lib
+	test -z $(echo /lib/ld*) || cp -a /lib/ld*   $(INITRD_BUILD_DIR)/lib
 	test ! -d /lib64 || cp -a /lib64/ld* $(INITRD_BUILD_DIR)/lib64
 	# Explicitly include more w/mklibs -L.  -dawild-
 ifeq ($(ARCH),x86_64)
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : RE : RE : Building SystemImager on CentOS 6.2? HELP

[LAHAYE Olivier]

Thanks for the info, unfortunately, my problem was related to 
systemconfigurator (systemimager is now working fine with CentOS-6.2 and 
default kernel) I'll soon release an updated src.rpm of systemimager

As you said, I used post install scripts to replace systemconfigurator and so 
far it works well.
I just thaught that some one had fixed systemconfigurator or at least found a 
replacement so I could update systemimager master script.

thanks for the input anyway.

Olivier.


De : Bas van der Vlies [b...@sara.nl]
Date d'envoi : jeudi 26 juillet 2012 15:44
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : RE : Building SystemImager on CentOS 6.2? HELP

 You can replace the SI kernel/initrd with the SALI kernel/initrd when
 booting SI clients, and even run your old SI .master installation
 scripts!  Some minor tweaks to the .master script must be performed as
 documented in
 https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/UsingYourOldInstallScript.
   It really works!  Of course, the installed CentOS 6.x client still
 won't boot due to systemconfigurator :-(

 SALI has their own master scripts which are a lot simpler than the SI
 scripts, but I think SALI hasn't been ported to CentOS 6.x yet because
 1) SALI still relies upon systemconfigurator, and 2) SALI doesn't seem
 to support LVM.


Just some comments on SALI. We use the SALI kernel/initrd  on Debian, Centos and
SUSE Linux PowerPC. The development is mostly donein a Debian enviroment, Only 
when
you want to make you own kernel/initrd you have to compile it from scratch.

We do not use the systemimager-server tools anymore. They are replaced by the 
SALI
server tools. they are noy documented yet :-(

As for the systemconfigurator tools we have replaced them partially by 
functions in the
`initrd` and  postinst scripts. So we get rid of the systemconfigurator tools. 
We have some ideas
howto replace them with other tools.

As for LVM the  SALI kernel/initrd  support it. For now there are now functions 
for it to hide the
complexity. So you must do the basic LVM commands in the master script.

 In conclusion, it seems to me that if you can make systemconfigurator
 work correctly on CentOS 6.x, then SI and/or SALI should work as well
 for installing clients that will be bootable.


We have implemented a `grub2_install` functions or create a
postinst script that will do it for you


--

*  Bas van der Vliese-mail: b...@sara.nl   *
*  SARA - Academic Computing Services   Amsterdam, The Netherlands *



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : RE : Building SystemImager on CentOS 6.2? HELP

[LAHAYE Olivier]

Hi,

After trying to use my RPM on a CentOS-6.2 system, I'm facing some issues that 
are hard to fix, thus I'm asking before starting to try to make a update so it 
works on CentOS-6.2

1st of all, I've already made some fix to systemimager so it works on 
CentOS-6.2, unfortunately, I'm stuck with systemconfigurator which is not 
supported on CentOS-6.2 (kernel-2.6) and therfore disable with no equivalent in 
systemimager. Because of this, the bootloader is not written to disk after the 
imaging, and therfore, the imaged system is unable to boot.

So the actual situation is the following:
- systemimager-4.1.99.svn4568/lib/SystemImager/Server.pm:1788 
SystemConfigurator deprecated and nothing to do its job (configure and write 
bootloader, ...)

- systemconfigurator-2.2.11-1/lib/SystemConfig/{Initrd/RH.pm, Boot*, ???} need 
to be fixed to have kernel 2.6+ properly handeled (initramfs instead of initrd, 
dracut instead of initrd (compatible script exist for the moment), ...

So now, I need help on having the ##SYSTEMCONFIGURATOR_PRE## and  
#SYSTEMCONFIGURATOR_POST## steps working in SystemImager. Works need to be done 
on the autoinstallscript and in systemconfigurator (or equivalent).

For now here are my patches for the latest systeminstaller to be able to deploy 
an image:

- systemimager_initrd_coreutils_rul.patch
Small Makefile fix (more clean)

- systemimager_initrd_mklib_bef.patch
Avoid overwriting libs that are alreadin installed in build_dir/ This prevent 
libmount-2.10 from CentOS-6.2 to overwrite libmount 2.12 from util-linux, and 
thus have mount, blkid and such to run instead of failing with wrong lib 
version.

- systemimager_initrd_rul.patch
Fix destination lib path.

- systemimager_initrd_udev_rul.patch
Disable systemd, libdir=/lib and use $MAKE

- systemimager_initrd_util_linux_rul.patch
Use $MAKE install instead of manualy copy binaries. If make install is not 
used, the libtool wrapper is copied instead of the real lib.

- systemimager_server_pm.patch
Fix that may be temporary. Right now, if the 1st partition inside the extended 
partition start at the same block, parted returns an error code. This fix avoid 
this by adding one block to the partition created inside the extended 
partition. Far from being a good fix, it makes at least things work. (fix 
commented in the patch)

- systemimager_sysvinit_initrd_rul.patch
Added a test to avoid failing  when trying to copy /lib/ld* and no files are 
found.

- systemimager_util_linux_rul.patch
Enhanced configure step.


Thanks a lot for your help.

PS: Cross posted on oscar-devel mailing list

De : LAHAYE Olivier
Date d'envoi : lundi 18 juin 2012 09:56
À : sisuite-users@lists.sourceforge.net
Objet : [sisuite-users] RE :  Building SystemImager on CentOS 6.2?

This is wired, as I'me sure I've faced the not updated kernel config issue 
(especially the compression method) and using my srpm on my centos-6.2, Id' 
doesn't ask for this.

I've re-uploaded my src.rpm. please check with this rpm and all the sources.

CentOS-6.2 and RHEL-6.2 should be very similar and shoud build the same way. 
(more over, this issue is related to the rpm, not the system. question is asked 
about things related to the rpm...)

http://olivier.lahaye1.free.fr/SOURCES/ grab the external sources here an copy 
this in /usr/src
Make sure you're using those sources when building and not something else 
downloaded elsewhere that could supersede some of those tarballs.

http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.6svn4568.el6.src.rpm
Install this and build it as root (I know it is bad, but I hadn't time to fix 
the mknod issue).

Cheers,

Olivier.

De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : vendredi 15 juin 2012 22:25
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] Building SystemImager on CentOS 6.2?

LAHAYE Olivier olivier.lah...@cea.fr wrote:
 Go there and fetch those sources. It should build without asking any 
 questions (it does for me).
 Hopefully I didn't forgot any Requires: in the spec file.
 http://olivier.lahaye1.free.fr/SOURCES/

Thanks a lot!  I grabbed the missing linux_2.6.34.1.orig.tar.gz file now.

Unfortunately the build process still asks unwarranted questions. This is what I
did:

1. I have checked out SVN trunk revision 4568 from
https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk
2. In the trunk/ directory I do: make source_tarball
3. Then I build it: cd tmp;  rpmbuild -ta systemimager-4.3.0.tar.bz2

However, during the build process the kernel wants to be reconfigured:

 + make all
 rm -rf /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1
 Extracting kernel source...done
 cp -a /root/rpmbuild/BUILD/systemimager-4.3.0/patches/linux.x86_64.config 
 /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/.config
 perl -pi -e s/^EXTRAVERSION =\s*(\S*)\s*\n/EXTRAVERSION = \1-boel_v4.3.0\n/ 
 /root

[sisuite-users] RE : Building SystemImager on CentOS 6.2?

[LAHAYE Olivier]

This is wired, as I'me sure I've faced the not updated kernel config issue 
(especially the compression method) and using my srpm on my centos-6.2, Id' 
doesn't ask for this.

I've re-uploaded my src.rpm. please check with this rpm and all the sources.

CentOS-6.2 and RHEL-6.2 should be very similar and shoud build the same way. 
(more over, this issue is related to the rpm, not the system. question is asked 
about things related to the rpm...)

http://olivier.lahaye1.free.fr/SOURCES/ grab the external sources here an copy 
this in /usr/src
Make sure you're using those sources when building and not something else 
downloaded elsewhere that could supersede some of those tarballs.

http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.6svn4568.el6.src.rpm
Install this and build it as root (I know it is bad, but I hadn't time to fix 
the mknod issue).

Cheers,

Olivier.

De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : vendredi 15 juin 2012 22:25
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] Building SystemImager on CentOS 6.2?

LAHAYE Olivier olivier.lah...@cea.fr wrote:
 Go there and fetch those sources. It should build without asking any 
 questions (it does for me).
 Hopefully I didn't forgot any Requires: in the spec file.
 http://olivier.lahaye1.free.fr/SOURCES/

Thanks a lot!  I grabbed the missing linux_2.6.34.1.orig.tar.gz file now.

Unfortunately the build process still asks unwarranted questions. This is what I
did:

1. I have checked out SVN trunk revision 4568 from
https://systemimager.svn.sourceforge.net/svnroot/systemimager/trunk
2. In the trunk/ directory I do: make source_tarball
3. Then I build it: cd tmp;  rpmbuild -ta systemimager-4.3.0.tar.bz2

However, during the build process the kernel wants to be reconfigured:

 + make all
 rm -rf /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1
 Extracting kernel source...done
 cp -a /root/rpmbuild/BUILD/systemimager-4.3.0/patches/linux.x86_64.config 
 /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/.config
 perl -pi -e s/^EXTRAVERSION =\s*(\S*)\s*\n/EXTRAVERSION = \1-boel_v4.3.0\n/ 
 /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1/Makefile
 make -C /root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1 oldconfig
 make[1]: Entering directory 
 `/root/rpmbuild/BUILD/systemimager-4.3.0/src/linux-2.6.34.1'
   HOSTCC  scripts/basic/fixdep
   HOSTCC  scripts/basic/docproc
   HOSTCC  scripts/basic/hash
   HOSTCC  scripts/kconfig/conf.o
   HOSTCC  scripts/kconfig/kxgettext.o
   SHIPPED scripts/kconfig/zconf.tab.c
   SHIPPED scripts/kconfig/lex.zconf.c
   SHIPPED scripts/kconfig/zconf.hash.c
   HOSTCC  scripts/kconfig/zconf.tab.o
   HOSTLD  scripts/kconfig/conf
 scripts/kconfig/conf -o arch/x86/Kconfig
 *
 * Restart config...
 *
 *
 * General setup
 *
 Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
 Local version - append to kernel release (LOCALVERSION) []
 Automatically append version information to the version string 
 (LOCALVERSION_AUTO) [Y/n/?] y
 Kernel compression mode
 1. Gzip (KERNEL_GZIP)
   2. Bzip2 (KERNEL_BZIP2)
   3. LZMA (KERNEL_LZMA)
   4. LZO (KERNEL_LZO) (NEW)
 choice[1-4?]:

So something must be wrong. I don't why I have to reconfigure the kernel whereas
Olivier doesn't. FYI, my build host is RHEL6.2 (fully updated).

Thanks for any help,
Ole

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] RE : Building SystemImager on CentOS 6.2?

[LAHAYE Olivier]

Go there and fetch those sources. It should build without asking any questions 
(it does for me).
Hopefully I didn't forgot any Requires: in the spec file.
http://olivier.lahaye1.free.fr/SOURCES/

Olivier.

De : Ole Holm Nielsen [ole.h.niel...@fysik.dtu.dk]
Date d'envoi : vendredi 15 juin 2012 15:05
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] Building SystemImager on CentOS 6.2?

LAHAYE Olivier olivier.lah...@cea.fr wrote:
 I've built the rpm on CentOS-6.2. The resulting rpms seems ok. As I'm porting 
 OSCAR on CentOS-6.2, I've been able to build client images so far, but I 
 can't tell if the resulting image is fully functionnal as systemimage-oscar 
 fail to generate the KERNEL0 line in 
 /var/lib/systemimager/images/imagename/etc/systemconfig/systemconfig.conf 
 (problem outside these rpms)

 To build the rpms, just look for the missing archive names in google and 
 download the archive into /usr./src directory.
 Note that (sadly) you have to be root to build the rpms as the rpm needs 
 mknode if I'm correct and I didn't find time to look at this issue and have 
 the rpm buildable as non-root.

 Although, it would be cool if the source repository could be updated as it's 
 a pain in the ass to google and fetch the correct sources archives and copy 
 those in the /usr/src directory.

I've made a bit of progress towards building the SI RPMs on an RHEL6.2
server, but I didn't make it to the goal yet:

1. I copied the downloaded sources from
/root/rpmbuild/BUILD/systemimager-4.3.0/initrd_source/src/ to the
permanent place /usr/src/. Strangely, today the correct e2fsprogs can be
downloaded successfully (it was absent yesterday).

2. The next missing download is a kernel source file
http://download.systemimager.org/pub/linux/linux_2.6.34.1.orig.tar.gz.
So I grabbed a similar file from
http://www.kernel.org/pub/linux/kernel/v2.6/ and renamed it with the
.orig (probably a no-no!). The kernel.org version seems to build, but I
had to answer a bunch of configure questions.

3. Next failure occurs when building parted-2.3:
...
checking for dm_task_create in -ldevmapper... no
configure: error: libdevmapper could not be found, but is required for the
--enable-device-mapper option, which is enabled by default.  Either disable
device-mapper support with --disable-device-mapper or download and install
device-mapper from:
http://sources.redhat.com/dm/
FYI, our RHEL6.2 server does have the device-mapper 32- and 64-bit RPMs
installed with /lib/libdevmapper.so.1.02.

Question: Am I on the right track, or is there a better way to build the
SI RPMs?

Thanks a lot,
Ole

--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

[sisuite-users] systemimager svn4568 RPM for EL6 done

[LAHAYE Olivier]

Hi,

I've managed to update systemimage spec file to have svn 4568 build on 
centos-6.2 (thus hopefully all rhel6 flavors).

The patch on sourcetree avoiding debian stuff to fail the redhat build is in 
the src.rpm

Changelog in the specfile:
* Tue Apr 24 2012 Olivier Lahaye olivier.lah...@cea.fr
- New svn snapshot 4568
- device-mapper-devel is needed
- quilt is needed for building sysvinit-2.87dsf
- Patch to sysvinit-2.87dsf to avoid debian specific stuffs
- Patch for new kernel config

It is available here.
http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.6svn4568.el6.src.rpm

Cheers,

Note: you have to manually download the required sources yourself in /usr/src 
as the systemimager ftp tree seems not up to date.

--
  Olivier Lahaye

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users