Thanks for the info. I haven't tried the diskless build yet. Does it use 
nfsroot or only ramdisk? If it uses nfsroot, can you have multiple nfs 
server servicing different groups of nodes? Or can you build the root fs 
on a NAS (like a netapp) ?


Mahmoud Hanafi
Sr. System Administrator
CSC HPC COE
Bld. 676
2435 Fifth Street
WPAFB, Ohio 45433
(937) 255-1536


Computer Sciences Corporation 
Registered Office: 2100 East Grand Avenue, El Segundo California 90245, 
USA
Registered in USA No: C-489-59

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to 
any order or other contract unless pursuant to explicit written agreement 
or government initiative expressly permitting the use of e-mail for such 
purpose.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




"Mark Black" <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
02/27/2008 12:36 PM
Please respond to
Users of Kusu  <[email protected]>


To
"Users of Kusu" <[email protected]>, "Shawn Starr" 
<[EMAIL PROTECTED]>
cc

Subject
RE: [Kusu-users] docs & question...






Hi Mahmoud

Unfortunately not all OCS users are as advanced as you are.  The packages 
and custom scripts are typically added by ngedit, but adding them is 
basically just adding a database entry.

Adding a custom script could be done by:
                 1. Copy the script you want to run to 
/depot/repos/custom_scripts
                 2. Get the nodegroup ID of the node group that should run 
this script
                      # sqlrunner -q 'select ngid,ngname from nodegroups'
         The first column is the nodegroup ID
                 3. Add the script into the scripts table i.e.
                      # sqlrunner -q 'insert into scripts set ngid={Your 
ngid}, script="{Your script name}"'

Adding packages is a similiar process:
                 1. Get the nodegroup ID of the node group that should run 
this script
                      # sqlrunner -q 'select ngid,ngname from nodegroups'
         The first column is the nodegroup ID
                 2. Add the script into the scripts table i.e.
                      # sqlrunner -q 'insert into packages set ngid={Your 
ngid}, packagename="{Name of the package}"'

This bypasses the checking the ngedit tool does, so it allows you to make 
mistakes.


Mark

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mahmoud Hanafi
Sent: Wednesday, February 27, 2008 10:50 AM
To: Shawn Starr
Cc: Users of Kusu
Subject: RE: [Kusu-users] docs & question...


I would like to be able to extend a compute by adding scripts and 
packages(with-out using a UI). Is there a similar approach as in OCS4.x 
(extend-compute.xml)


Mahmoud Hanafi
Sr. System Administrator
CSC HPC COE
Bld. 676
2435 Fifth Street
WPAFB, Ohio 45433
(937) 255-1536


Computer Sciences Corporation 
Registered Office: 2100 East Grand Avenue, El Segundo California 90245, 
USA
Registered in USA No: C-489-59

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to 
any order or other contract unless pursuant to explicit written agreement 
or government initiative expressly permitting the use of e-mail for such 
purpose.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




"Shawn Starr" <[EMAIL PROTECTED]> 
02/27/2008 10:34 AM

To
"Users of Kusu" <[email protected]>
cc
Mahmoud Hanafi/DEF/[EMAIL PROTECTED]
Subject
RE: [Kusu-users] docs & question...






Hi Mahmoud, 


1) Add host allows you to add multiple nodes (pre-populate). To do this 
use:


addhost -f [filename of mac addresses] -j [interface the compute nodes use 

to provision from] -n [nodegroup name]


The mac address file format is the following:

aa:bb:cc:dd:ee:ff
bb:cc:dd:ee:ff:aa
...

2) When you mean extend what specifically, packages or scripts? If you 
have 3rd party packages drop them in 
/depot/contrib/[distribution]/[version]/x86_64 then run the ngedit command 

to select the custom package(s) you want to install.

3) Using the ngedit command you copy a node group and modify the node 
group to your liking.

Thanks, 
Shawn.


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Mahmoud Hanafi
> Sent: Tuesday, February 26, 2008 9:19 PM
> To: [email protected]
> Subject: [Kusu-users] docs & question...
> 
> 
> Is there a document that description the overall architecture 
> of kusu. 
> 
> Some basic question....
> 1. how do I add a bulk of nodes at the same time? (i have the 
> mac address 
> already)
> 2. How do I extend the base install of a compute node.
> 3. How do I add additional node types?
> 
> 
> Mahmoud Hanafi
> Sr. System Administrator
> CSC HPC COE
> Bld. 676
> 2435 Fifth Street
> WPAFB, Ohio 45433
> (937) 255-1536
> 
> 
> Computer Sciences Corporation 
> Registered Office: 2100 East Grand Avenue, El Segundo 
> California 90245, 
> USA
> Registered in USA No: C-489-59
> 
> --------------------------------------------------------------
> --------------------------------------------------------------
> --------------------------------------------------------------
> ----------------------
> This is a PRIVATE message. If you are not the intended 
> recipient, please 
> delete without copying and kindly advise us by e-mail of the 
> mistake in 
> delivery. 
> NOTE: Regardless of content, this e-mail shall not operate to 
> bind CSC to 
> any order or other contract unless pursuant to explicit 
> written agreement 
> or government initiative expressly permitting the use of 
> e-mail for such 
> purpose.
> --------------------------------------------------------------
> --------------------------------------------------------------
> --------------------------------------------------------------
> ----------------------
> _______________________________________________
> Kusu-users mailing list
> [email protected]
> http://mail.osgdc.org/mailman/listinfo/kusu-users
> 

_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users

_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users

Reply via email to