How to update the base kit to 1.0? - HPC Community - High Performance Computing (HPC) Community

_fmms_ · #1 (**permalink**) October 13th, 2008, 02:37 PM

What is the official way to update a kusu base kit?

I have been running 0.10 and wanted to update to 1.0

Code:

[root@master ~]# kitops -l
Kit:            base
Description:    Base Kit
Version:        0.10
Architecture:   noarch
OS Kit:         No
Removable:      No
Node Groups:    installer-centos-5-x86_64, compute-centos-5-x86_64,
                compute-imaged-centos-5-x86_64, compute-diskless-centos-5-x86_64

Kit:            centos
Description:    OS kit for centos 5 x86_64
Version:        5
Architecture:   x86_64
OS Kit:         Yes
Removable:      Yes
Node Groups:    installer-centos-5-x86_64, compute-centos-5-x86_64,
                compute-imaged-centos-5-x86_64, compute-diskless-centos-5-x86_64

Kit:            centos-updates
Description:    Updates for centos 5 x86_64 on Mon Oct 13 13:26:00 2008
Version:        5_x86_64_r1
Architecture:   noarch
OS Kit:         No
Removable:      Yes
Node Groups:    installer-centos-5-x86_64, compute-centos-5-x86_64,
                compute-imaged-centos-5-x86_64, compute-diskless-centos-5-x86_64

Kit:            base
Description:    Base Kit
Version:        1.0
Architecture:   noarch
OS Kit:         No
Removable:      No
Node Groups:

I first downloaded the new base iso and added that to my kits with kitops.
Then I added it to the repo with

Code:

$ repoman -r "Repo for centos-5-x86_64" -a -k base -o "1.0"
$ repoman -u

Calling ngedit now does not look good, as one can not distinguish the different versions ... It displays both versions as installed but just the old one is...

So I am no back to call

Code:

[root@master var]# yum update
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
 * kusu-installer: 172.20.0.1
kusu-installer            100% |=========================| 1.1 kB    00:00
primary.xml.gz            100% |=========================| 1.1 MB    00:00
kusu-insta: ################################################## 3305/3305
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package kusu-ui.noarch 0:1.0-1 set to be updated
---> Package kusu-path.noarch 0:1.0-1 set to be updated
---> Package kusu-hardware.noarch 0:1.0-1 set to be updated
---> Package kusu-buildkit.noarch 0:1.0-1 set to be updated
---> Package component-gnome-desktop.noarch 0:1.0-1 set to be updated
---> Package kusu-partitiontool.noarch 0:1.0-1 set to be updated
---> Package kusu-repoman.noarch 0:1.0-1 set to be updated
---> Package kusu-nodeinstaller-patchfiles.noarch 0:1.0-1 set to be updated
---> Package kusu-nodeinstaller.noarch 0:1.0-1 set to be updated
---> Package kusu-driverpatch.noarch 0:1.0-1 set to be updated
---> Package component-base-node.noarch 0:1.0-1 set to be updated
---> Package kusu-base-node.x86_64 0:1.0-1 set to be updated
---> Package kusu-core.noarch 0:1.0-1 set to be updated
---> Package kusu-networktool.noarch 0:1.0-1 set to be updated
---> Package kusu-base-installer.noarch 0:1.0-1 set to be updated
---> Package kusu-util.noarch 0:1.0-1 set to be updated
---> Package component-base-installer.noarch 0:1.0-1 set to be updated
---> Package initrd-templates.noarch 0:1.0-1 set to be updated
---> Package kusu-boot.noarch 0:1.0-1 set to be updated
---> Package kusu-kitops.noarch 0:1.0-1 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Updating:
 component-base-installer  noarch     1.0-1            kusu-installer    2.6 k
 component-base-node     noarch     1.0-1            kusu-installer    2.0 k
 component-gnome-desktop  noarch     1.0-1            kusu-installer    3.3 k
 initrd-templates        noarch     1.0-1            kusu-installer     32 k
 kusu-base-installer     noarch     1.0-1            kusu-installer    326 k
 kusu-base-node          x86_64     1.0-1            kusu-installer     45 k
 kusu-boot               noarch     1.0-1            kusu-installer     47 k
 kusu-buildkit           noarch     1.0-1            kusu-installer     52 k
 kusu-core               noarch     1.0-1            kusu-installer     65 k
 kusu-driverpatch        noarch     1.0-1            kusu-installer     35 k
 kusu-hardware           noarch     1.0-1            kusu-installer     21 k
 kusu-kitops             noarch     1.0-1            kusu-installer     36 k
 kusu-networktool        noarch     1.0-1            kusu-installer     13 k
 kusu-nodeinstaller      noarch     1.0-1            kusu-installer     43 k
 kusu-nodeinstaller-patchfiles  noarch     1.0-1            kusu-installer     16 k
 kusu-partitiontool      noarch     1.0-1            kusu-installer     89 k
 kusu-path               noarch     1.0-1            kusu-installer     20 k
 kusu-repoman            noarch     1.0-1            kusu-installer     56 k
 kusu-ui                 noarch     1.0-1            kusu-installer     27 k
 kusu-util               noarch     1.0-1            kusu-installer     51 k

Transaction Summary
=============================================================================
Install      0 Package(s)
Update      20 Package(s)
Remove       0 Package(s)

Total download size: 981 k

Is this what I want? How am i supposed to update?

_fmms_ · #2 (**permalink**) October 13th, 2008, 03:35 PM

I patched ngedit a bit and now it would probably be working if my cfmsync would do anything...

Code:

[root@master var]# diff -u /opt/kusu/sbin/ngedit.orig /opt/kusu/sbin/ngedit
--- /opt/kusu/sbin/ngedit.orig  2008-10-13 17:50:07.000000000 +0200
+++ /opt/kusu/sbin/ngedit       2008-10-13 17:58:23.000000000 +0200
@@ -641,7 +641,7 @@

         self.screenGrid = snack.Grid(1, 2)

-        query = '''SELECT c.kid,k.rname,c.cid,c.cname FROM components c, kits k,
+        query = '''SELECT c.kid,k.rname,k.version,c.cid,c.cname FROM components c, kits k,
                    repos_have_kits rk, repos r WHERE c.kid = k.kid AND k.kid = rk.kid
                    AND rk.repoid = r.repoid AND r.repoid = %s AND (r.ostype like
                    concat(c.os,'%%') OR isnull(c.os)) ORDER BY c.kid''' % curNG['repoid']
@@ -675,19 +675,19 @@

         self.__ct = snack.CheckboxTree(height = 10, scroll = 1)
         curkid = rv[0][0]
-        self.__ct.append(rv[0][1])
+        self.__ct.append(rv[0][1]+'-'+rv[0][2])
         i = 0
-        for kid,rname,cid,cname in rv:
+        for kid,rname,version,cid,cname in rv:
             if kid <> curkid:
                 #new kid encountered - append it
                 i += 1
                 curkid = kid
-                self.__ct.append(rname)
+                self.__ct.append(rname+'-'+version)
             if cid in cidlst:
                 isSel = 1
             else:

If this patch makes any sense I can open a ticket for it.

_fmms_ · #3 (**permalink**) October 13th, 2008, 03:57 PM

Ok there is another problem as far as I can see...

Code:

$ cat /opt/kusu/etc/package.lst.orig
# Generated automatically.  Do not Edit!
centos-5-x86_64
component-base-installer
component-base-node
component-centos-updates_5_x86_64_r1
component-gnome-desktop
component-lava-master-v1_0

The packages in there do not contain version numbers and therefore cfmsync -p does not update the packages after selecting them in ngedit.

_fmms_ · #4 (**permalink**) October 14th, 2008, 11:22 AM

cfmsync -u seems to be better ...

George Goh · #5 (**permalink**) October 17th, 2008, 04:04 AM

Hi,

For the base kit, there is no need to cfmsync after installing a new version. Basically, you will want to remove the old version of your base kit from the repo and install the new version.

After that, a 'yum update' will be sufficient(which I see you have done).

However, I do see the possibility where other kits may need to use cfmsync when they are updated to a new version. Please file this as an issue, and we will look into it.

Thanks again for contributing to Kusu :-)

_fmms_ · #6 (**permalink**) October 17th, 2008, 08:04 AM

I split this issue into the following tickets:
[#KUSU-960] cfmsync does not work for updating kits - Open Source Grid Development Center ,

[#KUSU-961] [PATCH] ngedit should display version information - Open Source Grid Development Center and

[#KUSU-962] kitops unable to update minor versions - Open Source Grid Development Center

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode