gmane.comp.clustering.kusu.devel

Re: Creating a multi-boot nodegroup

George Goh — 2010-09-16T01:36:10

Thanks Liming,

I didn't try this yesterday as I was away. Will try this today and let you
know if it works.

-George

On Tue, Sep 14, 2010 at 8:42 PM, Tsai Li Ming <ltsai< at >osgdc.org> wrote:

Re: Creating a multi-boot nodegroup

Tsai Li Ming — 2010-09-14T12:42:48


On Tuesday 14,September,2010 10:40 AM, George Goh wrote:

Hi,

Here's a sample of a multiboot nodegroup in raw SQL statement:

insert into nodegroups (repoid, ngname, installtype, ngdesc, nameformat, 
kernel, initrd, kparams, type) VALUES (1000, 'Dualboot_Windows', 
'multiboot', 'Boot Windows Partition', 'compute-#RR-#NN', 'none', 
'none', 'hd0 1', 'compute') ;

insert into nodegroups (repoid, ngname, installtype, ngdesc, nameformat, 
kernel, initrd, kparams, type) VALUES (1000, 'Dualboot_Linux', 
'multiboot', 'Boot Linux Partition', 'compute-#RR-#NN', 'none', 'none', 
'hd0 2', 'compute') ;

insert into ng_has_net (ngid, netid) VALUES ((select ngid from 
nodegroups where ngname='Dualboot_Windows'), (select networks.netid from 
ng_has_net, networks where ng_has_net.netid=networks.netid AND 
networks.type='provision' AND ng_has_net.ngid=1));

insert into ng_has_net (ngid, netid) VALUES ((select ngid from 
nodegroups where ngname='Dualboot_Linux'), (select networks.netid from 
ng_has_net, networks where ng_ha

Creating a multi-boot nodegroup

George Goh — 2010-09-14T02:40:47

Hi,

Can someone show me how to create a proper multiboot nodegroup? I have tried
the following, but the node disappears when moving a node from diskless to
multiboot (this is not actually a diskless machine, I just don't want to
touch the disks):

<BEGIN TRANSCRIPT>

[root< at >gg-kusu ~]# python
Python 2.4.3 (#1, Sep  3 2009, 15:37:37)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
installtype='multiboot', type='compute')
[root< at >gg-kusu ~]# ngedit -l
unmanaged :  : other
installer-centos-5.5-x86_64 :  : installer
compute-centos-5.5-x86_64 :  : compute
compute-imaged-centos-5.5-x86_64 :  : compute-imaged
compute-diskless-centos-5.5-x86_64 :  : compute-diskless
groupA : clone : compute-diskless
groupB : clone : compute-diskless
localboot :  : compute
You have new mail in /var/spool/mail/root
[root< at >gg-kusu pxelinux.cfg]# nghosts -l
Node Group Names
================

groupA
----------------
groupA000   Installed

groupB
---------------
groupB0

Re: Make cfmsync show status of individual updates

Tsai Li Ming — 2010-08-31T05:29:04


On Tuesday 31,August,2010 01:23 PM, George Goh wrote:


Hi George,

cfmsync calls cfmclient and that the yum output (for rhel) is redirected 
to the /var/log/kusu/cfmclient.log.

The call to cfmclient is blocking on the installer node.

And please don't top post the next time.

-Liming

Re: Make cfmsync show status of individual updates

George Goh — 2010-08-31T05:23:05

Thanks for the reply Liming,

It turned out to be an error in the post-install script in the component
rpm. It couldn't find certain Kusu environment variables and died silently -
sourcing /opt/kusu/bin/kusuenv.sh fixed the issue.

Is the output of post-install scripts silenced in the rpm install process or
cfmsync? Is there any way to "un-silence" it?

Thanks,
-George

On Tue, Aug 31, 2010 at 12:44 PM, Tsai Li Ming <ltsai< at >osgdc.org> wrote:

Re: Make cfmsync show status of individual updates

Tsai Li Ming — 2010-08-31T04:44:14


On Tuesday 31,August,2010 12:21 PM, George Goh wrote:

Hi George,

Can you post an example of the script and the component SPEC file?

Regards,
Liming

Make cfmsync show status of individual updates

George Goh — 2010-08-31T04:21:13

Hi,

I created a kit with component post scripts (these create a new nodegroup)
that run during cfmsync.

However, when I run `cfmsync -fp`, it seems to return immediately, with the
script seemingly running in the background.

Anyway, to bring this background output to the foreground?

Thanks,
-George

Re: Specifications for Kit API

Tsai Li Ming — 2010-08-26T09:05:10

On Thursday 26,August,2010 04:38 PM, George Goh wrote:

Welcome back!

We will be publishing the specifications shortly. We are currently 
revamping our site for a launch. Once it is done, we will announce it to 
the list.

In the mean time, here are the links:
KIT API 0.1: http://docs.google.com/View?id=dgnwxbjj_30j28fp577
KIT API 0.2: http://docs.google.com/View?id=dgnwxbjj_29qbhx3jds
KIT API 0.3: http://docs.google.com/View?id=dgn6ghn6_23c4jcr8fc
(currently reserved for future implementation)
KIT API 0.4: http://docs.google.com/View?id=dc7rpsvg_2csj96xpm

We will be also publishing the related Kusu version that supports the 
various Kit API.

Currently,
0.1: Kusu 1.0 and above
0.2: Kusu 2.0 and above
0.3: Reserved. Not in used yet.
0.4: Kusu 2.1 and above. Scheduled to be release by end of year.

Each new kusu version will be fully backward compatible with older kit 
apis unless it is noted in the accompanying release notes.

Regards,
Liming

Specifications for Kit API

George Goh — 2010-08-26T08:38:41

Hi,

Are there any publicly available specifications of the various kit versions?

Thanks,
-George