Differences between revisions 6 and 7
Revision 6 as of 2008-04-04 17:00:54
Size: 3047
Comment:
Revision 7 as of 2008-04-04 17:27:12
Size: 4010
Comment:
Deletions are marked like this. Additions are marked like this.
Line 69: Line 69:
  Interesting thing:

I'm looking for ways that help me to chose between different virtualization solutions.

At the same time, I realized in these days, that I very much like the way of xen-tools to handle the disks - a filesystem is created directly inside a lvm volume, and a single partition (as opposed to a block device) is handed over to the guests.

I did believe it's not possible to reuse such lvm with partitions inside other virt solutions.
But that's wrong - you can boot such a thing in qemu with:

{{{
henning@xnote:~$ sudo qemu -kernel /boot/vmlinuz-2.6.18-6-686 -initrd /boot/initrd.img-2.6.18-6-686 -hda /dev/mapper/data-skolelinux--test--disk -append root=/dev/hda
Could not open '/dev/kqemu' - QEMU acceleration layer not activated
}}}

It might sound odd to use something that looks to qemu like a full block device as root filesystem - but it works, and it's only for my testing and development systems on the laptop. Fine.

My Plan for things to do on the Workmeeting: (could and should be translated some time)

Was will ich tun

  • Debian Java Pakete
    • Pbuilder config für sid
    • openjdk-6 versuchen zu bauen damit
  • Auf Notebook eine VM mit Skolelinux installieren - mögliche Alternativen:
    • kvm (bevorzugt, aber Probleme mit dem .24er Kernel - blank screen - http://localhost:3000/todo/show/267 )

    • virtualbox (doof wegen filebased Images, die man nicht austauschen kann mit anderen Systemen - keine Nutzung von LVM volumes)
    • vmware (doof,weil unfrei, geht scheinbar nicht mit 2.6.24 Kernel)
  • FAI Installationen für Skoelinux testen
    • Nochmal Ronnies Konfigurations aus dem Wiki testen für standalone und die anderen systemtype, die geht - auch mal schauen, wie und wo ich diese Konfiguration in ein SCM bringen kann
    • versuchen, einen main server hinzubekommen
  • Cipux dev Konzept checken, kommentieren, ...
  • Cipux und andere tools (Gosa, lwat) genauer unter die Lupe nehmen
    • In Cipux gibt es jetzt taint und input validation scheinbar - was ist mit anderen Punkte, die mir vorliegen?

concrete tasks I have to do

  • openjdk-6 building on sid
    • install testhost debian-sid-buildhost
      • create a sid config/base.tgz for my fai config
    • debug cpu escalation problem with pbuilder for sid when running on etch
    • build on other sid test host I have there
    • try pbuilder and/or building in sid chroot on another machine
  • FAI for DebianEdu

    • put contents from page ?DebianEdu/HowTo/FaiInstallDebianEdu into debian-edu SVN

    • Test install with this config from faitest-server-etch
      • standalone and workstation and terminal server (those that should work already)
      • main server
  • check mauve packaging for Andreas
    • download sources
    • run in pbuilder
    • debug
  • Learn about DebianEdu in general

    • (network)architecture documentation
    • read generic ldap documentation
    • look at debianedu ldap profiles in detail
  • admintool checking

Progress

2008-04-03

  • created some wiki pages and cleaned up some others (for java and cdd, and the workmeetings) in the debian wiki
  • add a contact link to the debian wiki frontpage which did not exist
  • tried to get the broken wiki:Self Interwiki linking fixed and got ignored and beeing laughed at by the helpful and constructive mr. weasel

  • worked on getting a sid pbuilder instance running (which failed to build and work as intendet)
  • tried to work around the various bugs in kvm/xen/Xwindows to get a sid virtual machine runinng for testing

2008-04-04

  • kept on working on the openjdk sid build environment
  • started to look at mauve(genome software) building problems for debian med

Interesting thing:

I'm looking for ways that help me to chose between different virtualization solutions.

At the same time, I realized in these days, that I very much like the way of xen-tools to handle the disks - a filesystem is created directly inside a lvm volume, and a single partition (as opposed to a block device) is handed over to the guests.

I did believe it's not possible to reuse such lvm with partitions inside other virt solutions. But that's wrong - you can boot such a thing in qemu with:

henning@xnote:~$ sudo qemu -kernel /boot/vmlinuz-2.6.18-6-686 -initrd /boot/initrd.img-2.6.18-6-686 -hda /dev/mapper/data-skolelinux--test--disk  -append root=/dev/hda
Could not open '/dev/kqemu' - QEMU acceleration layer not activated

It might sound odd to use something that looks to qemu like a full block device as root filesystem - but it works, and it's only for my testing and development systems on the laptop. Fine.