1. Take the root image from a pristine SLES 10.2 repository, and copy
the contents of the root image to a working location.
mkdir -p $WORKING_DIR/mnt $WORKING_DIR/rootimg
mount -o loop $REPO_LOCATION/boot/i386/root $WORKING_DIR/mnt
cp -avr $WORKING_DIR/mnt/* $WORKING_DIR/rootimg
umount $WORKING_DIR/mnt
2. Replace the original ‘yast’ script with my own script.
mv $WORKING_DIR/rootimg/sbin/yast $WORKING_DIR/rootimg/sbin/yast.real
Partitioning is important in Kusu for the following reasons:
- On the master node, the disks need to be correctly partitioned, so that repositories can be created on the disk before handing over to the distro's auto-installation mechanism.
- On the compute node, partitioning needs to take place unattended, according to a predefined schema in the database, with options to preserve certain types of partitions as well.
Over the next few blog entries, I will describe the approach taken
Overview
The Kusu installer is the first program that is run when the user boots from a Kusu ISO. It is a wizard-style program responsible for collecting the initial information that will describe and set up a Kusu cluster, including the timezone, networks, root password, disk partitioning, and kits available.
The Kusu installer is made up of 2 parts: the screens (context-specific info and prompts), and the navigation framework. In this document, I will describe the screens.
Liming and I took delivery for some shiny new hardware at our data centre today. These are a Dell 1950, and 2950 with dual Quad-core Xeon CPUs and 8GB of RAM each. The 1950 has two 15k, 300G SAS drives, while the 2950 has three 10k, 400G SAS drives. Very nice!
The 2950: Don’t carry this alone!
Greetings true believers!
I’m George Goh, one of your friendly neighbourhood cluster monkeys. Najib, our lead ape, has granted me access to blog here about general things happening in the OSGDC, and more specifically, Project Kusu and the components that I maintain, so let’s get things rolling… .
Here at OSGDC, we adopt the SCRUM methodology(http://en.wikipedia.org/wiki/Scrum_%28development%29) to keep things tight and moving fast. We have recently ended our third full
| File | Date | Downloads |
|---|---|---|
| Kusu-0.6_devel.centos-5.i386.iso : Kusu Development Release version 0.6 for CentOS 5 on the i386 architecture. MD5 Sum: e071e5deba94 ... | April 10th, 2008 | 54 |
| Kusu-0.6_devel.centos-5.x86_64.iso : Kusu Development Release version 0.6 for CentOS 5 on the x86_64 architecture. MD5 Sum: 718888d6a2 ... | April 10th, 2008 | 56 |
| Kusu-0.6_devel.fedora-6.i386.iso : Kusu Development Release version 0.6 for Fedora Core 6 on the i386 architecture. MD5 Sum: 993e730 ... | April 10th, 2008 | 43 |
| Kusu-0.6_devel.fedora-6.x86_64.iso : Kusu Development Release version 0.6 for Fedora Core 6 on the x86_64 architecture. MD5 Sum: 137ef ... | April 10th, 2008 | 48 |
| Kusu-0.7_devel.centos-5.i386.iso : Kusu Development Release version 0.7 for CentOS 5 on the i386 architecture. MD5 Sum: 87c0baf82661 ... | April 10th, 2008 | 49 |
| Kusu-0.7_devel.centos-5.x86_64.iso : Kusu Development Release version 0.7 for CentOS 5 on the x86_64 architecture. MD5 Sum: 464a31e962 ... | April 10th, 2008 | 43 |
| Kusu-0.7_devel.fedora-6.i386.iso : Kusu Development Release version 0.7 for Fedora Core 6 on the i386 architecture. MD5 Sum: 01d0797 ... | April 10th, 2008 | 59 |
| Kusu-0.7_devel.fedora-6.x86_64.iso : Kusu Development Release version 0.7 for Fedora Core 6 on the x86_64 architecture. MD5 Sum: a8687 ... | April 10th, 2008 | 71 |
| Kusu-0.8_devel.centos-5.1.x86_64.iso : Kusu Development Release version 0.8 for CentOS 5.1 on the x86_64 architecture. MD5 Sum: 96e7df46 ... | May 3rd, 2008 | 80 |
| Kusu-0.8_devel.centos-5.i386.iso : Kusu Development Release version 0.8 for CentOS 5 on the i386 architecture. MD5 Sum: 670e5028ac39d0 ... | May 3rd, 2008 | 80 |
| Kusu-0.8_devel.fedora-6.i386.iso : Kusu Development Release version 0.8 for Fedora Core 6 on the i386 architecture. MD5 Sum: 154c9b47f ... | May 3rd, 2008 | 86 |
Find all posts
View Articles
View Blog Entries
