najib

Almost a week have passed before I got around to updating this but I’m proud to say that we have tagged 0.5_devel as of Aug 17th. On top of the improvements that made this release more stable than previous releases, a bunch of notable features have also been added:

• repoman - Repository management tool for Kusu
• repopatch - Patch management tool for Kusu
• Metakits support for kitops, boot-media-tool and buildkit
• driverpatch - Kernel/initrd patching tool for PXE boot images

Downloads will soon be made available so please do give Project Kusu a spin and we appreciate any and all comments (or better yet, log issues in our tracker).
Release Notes - Kusu - Version 0.5_devel
New Features implemented:

• [KUSU-213] - Allow nodes to be configured with PXE as the 1st boot order
• [KUSU-261] - Driverpatch - Tool to patch initrd for nodeinstaller deployments
• [KUSU-275] - Framework for kusu/kits configuration scripts
• [KUSU-301] - repopatch
• [KUSU-302] - repoman

Improvements made:

• [KUSU-109] - Handle metakits in KitOps
• [KUSU-189] - Support for metakits for boot-media-tool
• [KUSU-206] - Utilize nodegroup types when adding kits
• [KUSU-212] - Node state is being updated
• [KUSU-246] - Make kitops accept a plain directory containing a kit as a valid kit (media) source
• [KUSU-247] - KusuApp should check for any running instances
• [KUSU-249] - driverpacks support for boot-media-tool
• [KUSU-250] - metakits support for buildkit
• [KUSU-271] - Enable support for extra packages in nodeinstaller
• [KUSU-279] - Check at least 1 provision network is defined
• [KUSU-286] - check for existent for rpmbuild tool
• [KUSU-296] - Check for PartitionID=* entry in partitions table and handle the preservation flag as default preserve or otherwise
• [KUSU-298] - Enhance kusurc scripting framework to support conventional shell scripts.

Bugs fixed:

• [KUSU-201] - Node installer LVM partitioning doesn’t create VolGroup00
• [KUSU-217] - Installer exits when user presses enter on a network interface.
• [KUSU-223] - unable to find volume group during node install
• [KUSU-224] - Call repoman from kitops after kit manipulation
• [KUSU-237] - Need to have known names for the node groups at RPM install time to setup the CFM
• [KUSU-243] - Installer has exception in partitioning
• [KUSU-254] - buildkit generates a mismatch in arch between kitinfo and kit RPM
• [KUSU-257] - Node install fails in partitioning
• [KUSU-258] - Unable to detect os cd disk 2
• [KUSU-267] - The repos.repository has the wrong value
• [KUSU-268] - The nodegroups.repoids are not set for all nodegroups
• [KUSU-269] - compute-disked and compute-image has no associated os
• [KUSU-270] - Partitioning not working for nodeinstaller r1877
• [KUSU-272] - Node installer partitioning does not remove unwanted partitions.
• [KUSU-273] - Attempting to mount when the dev is not available
• [KUSU-278] - After editing the / mount point, next will fail min mount point checks
• [KUSU-280] - Changing LV size does not reflect in the installer screen.
• [KUSU-281] - buildkit to support removable flag when defining kits
• [KUSU-282] - kitops_app_test.py broke with the r1940 commit.
• [KUSU-283] - nodeinstaller does not exit with correct exit code
• [KUSU-284] - String representation for PhysicalVolume object causes Exception when PhysicalVolume has no group defined.
• [KUSU-287] - kusurc kusudb set up failed. kusudb not created. affects rhel 5 i386 and x86_64.
• [KUSU-289] - Updated repository causes kernel panic after reinstallation
• [KUSU-290] - Unhandled exception in creating a swap partition
• [KUSU-292] - Cheetah and pysqlite rpms do not have the python libraries
• [KUSU-294] - Cannot install compute node
• [KUSU-297] - CFM does not run due to /etc/cfm directory not created.
• [KUSU-303] - Unknown VGs not removed when the database entry says partitionID=* preserve=0
• [KUSU-306] - Build 2040 fails to install