technical-info
26-10-2007
How I Restored My QEMU Windows XP Environment
- Booted off the Windows XP cdrom by typing the following at the command prompt:
qemu winxp.img -cdrom /dev/cdrom -boot d - When the "Welcome to Setup" screen appeared, pressed R to start the Recovery Console.
- Executed the FIXMBR command from the Recovery Console.
- Ran a CHKDSK to fixup any other problems that may have existed.
17-05-2007
I Beat Paul Everitt To The Punch
I gave the first Plone speech at a well known academic research institute in Taiwan.
13-02-2007
Achieving Server Xen
A summary of my experiences installing Xen 3 on Debian Etch.
The most pertinent hardware specifications for the server we installed Xen 3 on are as follows:
- 2x Intel Xeon 1.6 Ghz CPUs
- 4GB DDR2-667 RAM
- 3ware 9550SX-4LP PCI-X-to-SATA II RAID controller
- 4x Seagate Barracuda ES SATA 3.0GB/s 250GB hard drives (configured as RAID 5)
- Firstly, I downloaded and burned the Debian testing (etch) netinst CD image to CD.
- Following this, I began installing Debian etch on the server using the netinst CD.
At the disk partitioning screen, I setup the hard drive as follows:Disk /dev/sda: 749.9 GB, 749966721024 bytes
255 heads, 63 sectors/track, 91178 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 365 2931831 83 Linux
/dev/sda2 366 1581 9767520 8e Linux LVM
/dev/sda3 1582 4013 19535040 82 Linux swap / Solaris
/dev/sda4 4014 91178 700152862+ 8e Linux LVM
N.B. The /dev/sda4 LVM partition is where the logical volumes for the Xen guest domains (virtual servers) are to be stored.
I left the rest of the installation steps at their setup defaults. - I then installed Xen 3 on the server by entering the following command:
apt-get install xen-linux-system-2.6.18-3-xen-686 xen-tools \\
xen-docs-3.0 libc6-xen file xen-hypervisor-3.0.3-1-i386-pae \\
xen-linux-system-2.6.18-3-xen-vserver-686 bridge-utils - Following this, I made the following change in the /etc/xen/xend-config.sxp file and rebooted the server:
replace(network-script network-dummy)
with(network-script 'network-bridge netdev=eth0') - I now made the following changes to the /etc/xen-tools/xen-tools.conf file:
lvm = vservers
debootstrap = 1
size = 10Gb
memory = 512Mb
swap = 1Gb
fs = reiserfs
dist = etch
image = sparse
kernel = /boot/vmlinuz-2.6.18-3-xen-vserver-686
initrd = /boot/initrd.img-2.6.18-3-xen-vserver-686
mirror = http://debian.orcon.net.nz/debian - Following this, I created a new guest domain (or virtual server) on the server by entering the following command:
xen-create-image --hostname myservername.mydomain.co.nz --dhcp - I then booted the guest domain by entering the following:
xm create /etc/xen/myservername.mydomain.co.nz.cfg - I now connected a virtual console to my newly created guest domain by entering the following and then logged on as root:
xm console myservername.mydomain.co.nz - Finally, I set the root password and then logged off the
virtual console by typing CTRL+] and then made a ssh connection to the guest domain and started setting up the services on it.
24-12-2006
Sysadmin Stresses
What helped me to sleep at night.
After ensuring I had the prerequisite software, the installation wasn't difficult. It was a bit of a nuisance that Zenoss creates its own Zope instance but the specific python products it installed within the Zope instance really required this for ease of setup.
Once the Zenoss server software was installed, I then had to configure the network devices to notify Zenoss via SNMP of their current status. Though the organisation where I worked had a few varied operating systems and devices, this wasn't a problem. SNMP Informant (with the MBM module for CPU, case, and component monitoring), Syslog, and Zenwin provided monitoring for the Windows 2003 server (there were some gotchas with the setup of the SNMP service but a big thanks to #zenoss as they helped me resolve the particular issues I had). The snmp package took care of my Linux boxes and Zenoss' builtin Cisco support provided monitoring for the Cisco router.
Once I had added all the network devices, I then setup Zenoss to send notifications via email whenever specified Zenoss events occured.
When Zenoss is notified of an event it categorises the event by such things as type of event, severity, etc. When Zenoss is unsure of how to categorise an event, you can categorise it manually. Zenoss can use this criteria for its event notification system.
Something that really impressed me about the Zenoss project was that when I subscribed to the mailing list, I requested a Zenoss t-shirt and though I live at the bottom of the world in New Zealand they sent me one!


30-08-2006
Setting Up Windows Active Directory LDAP Authentication In Plone 2.5
A howto regarding setting up authentication against Active Directory in Plone 2.5 (PlonePAS)
Emerge Technology had an enquiry from a client recently regarding setting up authentication via Active Directory in Plone 2.5. I share our response here for the benefit of anyone else who wishes to do this (the test environment I setup included Microsoft Small Business Server 2003, Zope 2.9, and Plone 2.5):
One recommendation I would have is that you install LDAPMultiPlugins1.2 (available from here http://www.dataflake.org/software/ldapmultiplugins/ldapmultiplugins_1.2) and remove LDAPUserFolderExt-0.41 (As per normal Zope Product installation procedures you will need to stop and start your Zope instance after installing the product).
Following this, do the following:
- Go to acl_users and add a 'ActiveDirectory Multi Plugin'
- Go to 'Contents' of the new plugin, go to 'acl_users' and configure your LDAP settings there. You can test if it works correctly by searching for users via the 'Users' tab
- Setup your LDAP Schema mappings to Plone fields in the 'LDAP Schema' tab
- Go back to the ActiveDirectory Multi Plugin and enable the functionalities you require in the 'Activate' tab.
