Thread: kitops (name,ver,arch) naming for OS kit

I am using Red Hat HPC Solution 5.3.

contents of /etc/kusu-release:
Kusu "Platform OCS" 5 (build 1991)

When kitops adds a RHEL OS kit such as RHEL 5.2 or RHEL 5.3, the resulting kit is named "rhel5.3-5-x86_64" or "rhel5.2-5-x86_64".

Everything works fine but the naming convention seems odd to me. I would expect something more like "rhel-5.2-x86_64" or "rhel-5.3-x86_64".

Also the corresponding /depot/kits directory structure looks like:

/depot/kits/rhel5.3/5/x86_64/...
/depot/kist/rhel5.2/5/x86_64/...

whereas I would expect something more like:

/depot/kits/rhel/5.3/x86_64/...
/depot/kits/rhel/5.2/x86_64/...

I can modify /opt/kusu/lib/python/kusu/kitops/kitops.py
so that the naming convention for the (name,ver,arch) tuple comes out more like I would expect; i.e. I now get for OS kit names:

rhel-5.3-x86_64
rhel-5.2-x86_64

and I get the expected directory structure:

/depot/kits/rhel/5.3/x86_64/...
/depot/kits/rhel/5.2/x86_64/...

And everything seems to work fine this way too.

But I am not sure if doing this will break something else.

Can anyone tell me if the default naming convention behavior is by design, or if there is some reason for the odd naming and version naming?

Hi

RHHPC solution is based on Kusu 1.1.

Having to change only kitops is not enough. Various tools such as repoman or nodeinstaller depends on the version number. The version number is the major version of the OS.

We will be properly fixing this in Kusu 1.2 when the proper major/minor versions are stored. kitops -l has been enhanced to show the full version such as RHEL 5.3 or SLES 10.2.

-Liming

Thanks very much, I understand. I am leaving things as they want to behave by default (usually the best policy anyway...).