Discussion:
ngedit and user scripts
Maurice Hilarius
2008-03-26 17:48:35 UTC
Permalink
Hi there.

'man ngedit' mentions in passing: "User provided customization scripts".
This html blob has a "Custom scripts (for automated configuration of
tools)".
That is all I can find on this subject.

Therefore some questions come to mind:
1) Will Any executable do?
2) What permissions and ownership are needed for this script?
3) Where should it be place/ located?
4) Does one need to send it to nodes beforehand?
5) When will this be run? Immediately? Or is some intermediate step
needed to cause these to be executed?

Thanks all..
--
With our best regards,

//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. FAX: 01-780-456-9772/
/11060 - 166 Avenue email:***@harddata.com/
/Edmonton, AB, Canada http://www.harddata.com//
/ T5X 1Y3/
/
Mark Black
2008-03-26 19:40:29 UTC
Permalink
Hi Maurice

1. Use a shell script.
2. Don't care, when you run ngedit it will copy the script and set permissions. One thing to watch is hte name of the file. It will insist on a different name for each node group.
3. See 2
4. Handled automatically
5. Immediately after install

Mark

-----Original Message-----
From: Maurice Hilarius [mailto:***@harddata.com]
Sent: Wednesday, March 26, 2008 1:49 PM
To: kusu-***@osgdc.org
Cc: Mark Black
Subject: ngedit and user scripts


Hi there.

'man ngedit' mentions in passing: "User provided customization scripts".
This html blob has a "Custom scripts (for automated configuration of tools)".
That is all I can find on this subject.

Therefore some questions come to mind:
1) Will Any executable do?
2) What permissions and ownership are needed for this script?
3) Where should it be place/ located?
4) Does one need to send it to nodes beforehand?
5) When will this be run? Immediately? Or is some intermediate step needed to cause these to be executed?

Thanks all..
--
With our best regards,

Maurice W. Hilarius Telephone: 01-780-456-9771
Hard Data Ltd. FAX: 01-780-456-9772
11060 - 166 Avenue email:***@harddata.com
Edmonton, AB, Canada http://www.harddata.com/
T5X 1Y3
Maurice Hilarius
2008-03-28 20:24:11 UTC
Permalink
Hi,
RHEL edition of Kusu is not available on osgdc. Other builds such as
CentOS and Fedora are available. The links could be broken because
another build is happening.
http://www.osgdc.org/pub/build/
-Liming
I grabbed one of these ISOs and mount this on a freshly installed CentOS
box.

I see a set of directories containing (mostly) a whole list of rpm files.

Does one just install all of these rpms?
In any particular order?

Are any options / selection choices?

Where do you start?

Any suggestions deeply appreciated..
--
With our best regards,

//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. FAX: 01-780-456-9772/
/11060 - 166 Avenue email:***@harddata.com/
/Edmonton, AB, Canada http://www.harddata.com//
/ T5X 1Y3/
/
Najib Ninaba
2008-03-29 10:50:48 UTC
Permalink
Post by Maurice Hilarius
Hi,
RHEL edition of Kusu is not available on osgdc. Other builds such
as CentOS and Fedora are available. The links could be broken
because another build is happening.
http://www.osgdc.org/pub/build/
-Liming
I grabbed one of these ISOs and mount this on a freshly installed
CentOS box.
I see a set of directories containing (mostly) a whole list of rpm files.
Does one just install all of these rpms?
In any particular order?
Are any options / selection choices?
Where do you start?
Any suggestions deeply appreciated..
These ISOs are bootable Kusu ISOs. You would use them to install a
Kusu master. Check this link[1]. It's an installation guide for a Kusu
ISO for Fedora but the steps are similar for CentOS.

[1]http://www.osgdc.org/confluence/display/KUSU/Kusu+Installation+Guide

Best Regards,
-najib
Maurice Hilarius
2008-03-30 04:54:39 UTC
Permalink
Post by Najib Ninaba
These ISOs are bootable Kusu ISOs.
Figured that out.
Then figured that I needed a CentOS DVD for the "kit" for the OS
Got it installed, then , after the kit, the install resumed from teh
CentOS DVD!
Re-installed, this time removing the DVD.
There is not prompt to restore the KUSU DVD, and , if you do nto, it
carries on with a CentOS install, wiping out the KUSU install.

Anyway, second time was the trick.

Sort of.
When it was done, and rebooted, got piles of filesystem errors.
Not just on one, but all of the filesystems it created.

So, lots of fscks later, did get it to boot.

Weird, as I had done 3 previous installs on that disk recently, all with
no issues.

So, just to be safe did a full scan on that disk, with no errors found.

I think there might be a bug in the installer which is corrupting
filesystems.

After all is said and done, it does boot, but only gives me a text prompt.
If I "startx" it brings up an X session.
--
With our best regards,

//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. FAX: 01-780-456-9772/
/11060 - 166 Avenue email:***@harddata.com/
/Edmonton, AB, Canada http://www.harddata.com//
/ T5X 1Y3/
/
Mike Mazur
2008-03-30 08:54:58 UTC
Permalink
Hi Maurice,

On Sat, 29 Mar 2008 22:54:39 -0600
Post by Maurice Hilarius
Then figured that I needed a CentOS DVD for the "kit" for the OS
Good point, we should probably make this clearer in the installer.
Post by Maurice Hilarius
Got it installed, then , after the kit, the install resumed from teh
CentOS DVD!
Re-installed, this time removing the DVD.
There is not prompt to restore the KUSU DVD, and , if you do nto, it
carries on with a CentOS install, wiping out the KUSU install.
I find it strange that leaving the CentOS DVD in the drive and booting
will automatically trigger an installation without any input from the
user?
Post by Maurice Hilarius
Anyway, second time was the trick.
Sort of.
When it was done, and rebooted, got piles of filesystem errors.
Not just on one, but all of the filesystems it created.
So, lots of fscks later, did get it to boot.
Weird, as I had done 3 previous installs on that disk recently, all
with no issues.
So, just to be safe did a full scan on that disk, with no errors found.
I think there might be a bug in the installer which is corrupting
filesystems.
After all is said and done, it does boot, but only gives me a text
prompt. If I "startx" it brings up an X session.
Glad you got it working. Keep us up to date on your experiences!

Mike
George Goh
2008-03-30 16:18:19 UTC
Permalink
Hi Maurice,
Post by Maurice Hilarius
Then figured that I needed a CentOS DVD for the "kit" for the OS
Got it installed, then , after the kit, the install resumed from teh
CentOS DVD!
Re-installed, this time removing the DVD.
There is not prompt to restore the KUSU DVD, and , if you do nto, it
carries on with a CentOS install, wiping out the KUSU install.
I've created an issue in our bug tracker for this. View
http://bugs.osgdc.org/browse/KUSU-909 to watch this issue.
Post by Maurice Hilarius
Anyway, second time was the trick.
Sort of.
When it was done, and rebooted, got piles of filesystem errors.
Not just on one, but all of the filesystems it created.
So, lots of fscks later, did get it to boot.
Weird, as I had done 3 previous installs on that disk recently, all with
no issues.
So, just to be safe did a full scan on that disk, with no errors found.
I think there might be a bug in the installer which is corrupting
filesystems.
We OSGDC developers _really_ like things like logs
(/var/log/kusu/kusu.log, /tmp/syslog), so if you could please send them
to us, it'd be great. :-)

Also in this case, let us know your `fdisk -l` output as well.

Regards,
George
George Goh
2008-03-31 09:18:57 UTC
Permalink
Hi Maurice,

Could you send us a link of where we can get the file(s)?

Also, for the benefit of the community, it would be good if we posted
our communication on the mailing list(if it's not sensitive
information).

Regards,
George
Post by Mike Mazur
Hi Maurice,
Post by Maurice Hilarius
Then figured that I needed a CentOS DVD for the "kit" for the OS
Got it installed, then , after the kit, the install resumed from teh
CentOS DVD!
Re-installed, this time removing the DVD.
There is not prompt to restore the KUSU DVD, and , if you do nto, it
carries on with a CentOS install, wiping out the KUSU install.
I've created an issue in our bug tracker for this. View
http://bugs.osgdc.org/browse/KUSU-909 to watch this issue.
Post by Maurice Hilarius
Anyway, second time was the trick.
Sort of.
When it was done, and rebooted, got piles of filesystem errors.
Not just on one, but all of the filesystems it created.
So, lots of fscks later, did get it to boot.
Weird, as I had done 3 previous installs on that disk recently, all with
no issues.
So, just to be safe did a full scan on that disk, with no errors found.
I think there might be a bug in the installer which is corrupting
filesystems.
We OSGDC developers _really_ like things like logs
(/var/log/kusu/kusu.log, /tmp/syslog), so if you could please send them
to us, it'd be great. :-)
Also in this case, let us know your `fdisk -l` output as well.
Regards,
George
_______________________________________________
Kusu-users mailing list
http://mail.osgdc.org/mailman/listinfo/kusu-users
Loading...