View RSS Feed

najib

Kusu is now been tagged 0.4_devel

Rate this Entry
by on July 28th, 2007 at 09:39 AM (1184 Views)
Our 4th release is finally ready and there’s been quite a few nifty features for this round. Building Kusu Kits is made easier by the buildkit tool (preview release and largely untested currently) and Kusu now fully supports RHEL5 and CentOS5. The partitiontool library now supports preservation mode and other improvements as well of a whole slew of bugfixes were made for this release.
Release Notes - Kusu - Version 0.4_devel


New Features Implemented:

  • [KUSU-138] - buildkit for creating thirdparty kits
  • [KUSU-154] - Kusu supporting Centos 5
  • [KUSU-184] - Kusu supporting RHEL 5
  • [KUSU-211] - Add preservation to partitiontool
Improvements added:

  • [KUSU-81] - Create disc1/.discinfo directory for centos5
  • [KUSU-86] - When downloading repository, raise exception if /depot not mounted
  • [KUSU-87] - Look in fstab in existing partitions to determine existing mountpoints
  • [KUSU-129] - Use Tag revision instead of repoistory level revision
  • [KUSU-176] - Create progress dialogs for Node Installer
  • [KUSU-177] - Change name of anaconda script
  • [KUSU-202] - Create multiple ks.cfg in /depot/repos based on IP
  • [KUSU-203] - Add types column to nodegroups table
  • [KUSU-204] - Display nodegroups kits belong to in kitops –list
  • [KUSU-205] - Change hostname to netname in network device configuration screen
  • [KUSU-208] - Create ntp configuration
  • [KUSU-209] - Create type column in networks table
  • [KUSU-210] - Ensure on Installer that there is the minimum of /, /depot and swap partitions.
  • [KUSU-214] - syslog during node installation should be forwarded
  • [KUSU-215] - Move master installer back to installer nodegroup
  • [KUSU-218] - hostname check for ntp server
  • [KUSU-242] - Preservation for certain partition types in master installer default partitioning schema.
Bugs closed:

  • [KUSU-179] - ks.cfg not found
  • [KUSU-183] - Centos 5 class does not have getArch implementation
  • [KUSU-187] - Installer reboots when kitops raises exception during media detection
  • [KUSU-190] - Default node groups are missing
  • [KUSU-191] - The database is not fully populated after installation
  • [KUSU-192] - The kernel parameters for the Compute nodes have been hardcoded
  • [KUSU-193] - The names assigned to the various interfaces are not used
  • [KUSU-194] - The database is not fully populated after installation — repos table
  • [KUSU-195] - The database is not fully populated after installation — ng_has_net extra entries
  • [KUSU-196] - The database is not fully populated after installation — appglobals table
  • [KUSU-198] - The database is not fully populated after installation — networks table
  • [KUSU-199] - Check for existing physical nics b4 configuring
  • [KUSU-216] - fqhn of the master installer not used
  • [KUSU-219] - node installation failed
  • [KUSU-221] - format option not consistent in Partition screen
  • [KUSU-222] - KUSU_DIST in rhel is wrong
  • [KUSU-229] - Two repos are created on master installer
  • [KUSU-231] - installer unittest fail on centos 5 i386
  • [KUSU-234] - buildkit creates kit and component spec files in working directory.
  • [KUSU-235] - Exception after scanning disk
  • [KUSU-238] - default partitioning failing due to dictionary change
  • [KUSU-239] - editing a partition raises an exception that is invalid

Updated April 10th, 2008 at 10:18 AM by najib

Categories
Kusu/OCS

Comments

Trackbacks

Total Trackbacks 0
Trackback URL: