Difference between pages "ZFS Install Guide" and "Zope HOWTO"

From Funtoo
(Difference between pages)
Jump to: navigation, search
m
 
m
 
Line 1: Line 1:
== Introduction ==
+
This page documents how to use Zope with Funtoo Experimental, which currently has good Zope support thanks to [[Progress Overlay Python]] integration.
  
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.
+
== About Zope ==
  
=== Introduction to ZFS ===
+
Zope is an Open Source application server framework written in Python. It has an interesting history which you should familiarize yourself with before starting Zope development, as it contains several interesting twists and turns.
  
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:
+
=== Zope History ===
  
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
+
{{Note}} This HOWTO targets Zope 2.13, which includes Five. It is typically the version you should be using for new Zope projects.
  
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
+
* There are two versions of Zope, Zope 2 and Zope 3. One might assume that Zope 3 is the version that people should use for new software development projects by default, but this is not the case. Most Zope-based projects continue to use Zope 2. Zope 3 was an attempt to redesign Zope 2 from scratch, and is completely different from Zope 2, but it was not adopted by the community.
  
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
+
* There is also something called [http://codespeak.net/z3/five/ Five] (named because it is "2 + 3") that backports many of the new features of Zope 3 into the Zope 2 framework. Several projects will use Zope 2 plus Five in order to use some of the newer features in Zope. Five was merged into mainline Zope 2 in early 2010, and first appeared in Zope 2.8.
  
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
+
* You can learn more about the history of Zope 2, 3 and Five in the [http://svn.zope.org/Zope/trunk/src/Products/Five/README.txt?view=markup Five README].
  
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
+
* To make things even more interesting, work on [http://docs.zope.org/zope2/releases/4.0/ Zope 4] is underway, and it will be based on 2.13 rather than 3.x. It includes a number of [http://docs.zope.org/zope2/releases/4.0/CHANGES.html#restructuring incompatible changes] with prior versions.
 +
=== Zope Resources ===
  
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
+
Now that you understand what version of Zope you should be targeting (2.13), we can point you towards the correct documentation :)
  
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
+
; [http://docs.zope.org/zope2/zope2book/ The Zope 2 Book]: This book provides a general introduction to Zope concepts and ZMI. It is a good place to start, but doesn't provide a direct introduction to Zope development. It's recommended that you skim through this book to familiarize yourself with Zope. It generally does not assume much prior knowledge about Web development or Python.
 +
; [http://docs.zope.org/zope2/zdgbook/ Zope Developer's Guide]: This guide will give you a better introduction to Zope development. It assumes you already know Python. Skip chapters 1 and 2 and start in [http://docs.zope.org/zope2/zdgbook/ComponentsAndInterfaces.html chapter 3], which covers components and interfaces. [http://docs.zope.org/zope2/zdgbook/Products.html Chapter 5] covers the creation of your first product.
 +
; Five: We're not done yet. There is a bunch of stuff in Zope 2.13 that is not in the official documentation. Namely, the stuff in Five. Check out [http://codespeak.net/z3/five/manual.html The Five Manual].
 +
; ZTK: [http://docs.zope.org/ztkpackages.html ZTK Documentation]
 +
; ZCA: [http://www.muthukadan.net/docs/zca.html A Comprehensive Guide to Zope Component Architecture] offers a good introduction to the programming concepts of ZCA. We also have a new page on [[Zope Component Architecture]] which will help you to understand the big picture of ZCA and why it is useful. ZCML ("Z-camel") is a part of ZCA and  was introduced in Zope 3, so typically you will find ZCML documented within Zope 3 documentation and book.
 +
; Content Components: Views and Viewlets: [http://docs.zope.org/zope.viewlet/index.html This tutorial on viewlets] also contains some viewlet-related ZCML examples near the end. The "Content Component way" of developing in Zope seems to be a Zope 3 thing and tied to ZCML. Chapter 13+ of Stephan Richter's ''Zope 3 Developer's Handbook'' (book) seems to cover this quite well. You will probably also want to check out Philipp Weitershausen's ''Web Component Development with Zope 3'' (book).
 +
; [http://wiki.zope.org/zope2/Zope2Wiki Zope 2 Wiki]: Main wiki page for all things related to Zope 2.
 +
; [http://docs.zope.org docs.zope.org]: This is the main site for Zope documentation.
  
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
+
== First Steps ==
  
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
+
First, you will need to emerge {{Package|net-zope/zope}}:
 
+
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.
+
 
+
The only area where btrfs is ahead of ZFS is in the area of small file
+
efficiency. btrfs supports a feature called block suballocation, which
+
enables it to store small files far more efficiently than ZFS. It is
+
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol
+
to obtain similar benefits (with arguably better data integrity) when
+
dealing with many small files (e.g. the portage tree).
+
 
+
=== Disclaimers ===
+
 
+
{{fancywarning|This guide is a work in progress. Expect some quirks.}}
+
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}
+
 
+
== Video Tutorial ==
+
 
+
As a companion to the install instructions below, a YouTube video ZFS install tutorial is now available:
+
 
+
{{#widget:YouTube|id=kxEdSXwU0ZI|width=640|height=360}}
+
 
+
== Downloading the ISO (With ZFS) ==
+
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS already included. When booting, use the "alternate"-kernel. The ZFS-module won't work with the default kernel.
+
 
+
<pre>
+
Name: sysresccd-3.8.1_zfs_0.6.2.iso  (510 MB)
+
Release Date: 2013-11-03
+
md5sum aa33ef61c5d85ad564372327940498c3
+
</pre>
+
 
+
 
+
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
+
 
+
== Creating a bootable USB from ISO ==
+
After you download the iso, you can do the following steps to create a bootable USB:
+
  
 
<console>
 
<console>
Make a temporary directory
+
# ##i## emerge -av zope
# ##i##mkdir /tmp/loop
+
 
+
Mount the iso
+
# ##i##mount -o ro,loop /root/sysresccd-3.7.1_zfs_0.6.2.iso /tmp/loop
+
 
+
Run the usb installer
+
# ##i##/tmp/loop/usb_inst.sh
+
 
</console>
 
</console>
  
That should be all you need to do to get your flash drive working.
+
Zope is now installed.
  
When you are booting into system rescue cd, make sure you select the '''alternative 64 bit kernel'''. ZFS support was specifically added to the alternative 64 bit kernel rather than the standard 64 bit kernel.
+
== Project Skeleton ==
  
== Creating partitions ==
+
{{Note}} Zope should be run by a regular user account, not as the root user.
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.
+
 
+
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.
+
 
+
==== gdisk (GPT Style) ====
+
 
+
'''A Fresh Start''':
+
 
+
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.
+
We will also assume that <tt>/dev/sda</tt> is the target drive.<br />
+
  
 +
The first step in using Zope is to ensure that you are using a regular user account. Create a new directory called ''<tt>zope_test</tt>'':
 
<console>
 
<console>
# ##i##gdisk /dev/sda
+
$##bl## cd
 
+
$##bl## mkdir zope_test
Command: ##i##x ↵
+
Expert command: ##i##z ↵
+
About to wipe out GPT on /dev/sda. Proceed?: ##i##y ↵
+
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.
+
Blank out MBR?: ##i##y ↵
+
 
</console>
 
</console>
  
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}
+
Now, enter the directory, and create an "instance", which is a set of files and directories that are used to contain a Zope project:
 
+
Now that we have a clean drive, we will create the new layout.
+
 
+
'''Create Partition 1''' (boot):
+
 
<console>
 
<console>
Command: ##i##n ↵
+
$##bl## cd zope_test
Partition Number: ##i##
+
$##bl## /usr/lib/zope-2.13/bin/mkzopeinstance
First sector: ##i##↵
+
Last sector: ##i##+250M ↵
+
Hex Code: ##i##↵
+
 
</console>
 
</console>
  
'''Create Partition 2''' (BIOS Boot Partition):
+
You will see the following output, and will be prompted to answer a few questions:
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+32M ↵
+
Hex Code: ##i##EF02 ↵
+
</console>
+
 
+
'''Create Partition 3''' (ZFS):
+
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##↵
+
Hex Code: ##i##bf00 ↵
+
 
+
Command: ##i##p ↵
+
 
+
Number  Start (sector)    End (sector)  Size      Code  Name
+
  1            2048          514047  250.0 MiB  8300  Linux filesystem
+
  2          514048          579583  32.0 MiB    EF02  BIOS boot partition
+
  3          579584      1953525134  931.2 GiB  BF00  Solaris root
+
 
+
Command: ##i##w ↵
+
</console>
+
 
+
 
+
=== Format your boot volume ===
+
Format your separate /boot partition:
+
<console># ##i##mkfs.ext2 /dev/sda1</console>
+
 
+
=== Encryption (Optional) ===
+
If you want encryption, then create your encrypted vault(s) now by doing the following:
+
 
+
 
<console>
 
<console>
# ##i##cryptsetup luksFormat /dev/sda3
+
Please choose a directory in which you'd like to install
# ##i##cryptsetup luksOpen /dev/sda3 vault_1
+
Zope "instance home" files such as database files, configuration
</console>
+
files, etc.
  
=== Create the zpool ===
+
Directory: instance
We will first create the pool. The pool will be named `tank` and the disk will be aligned to 4096 (using ashift=12)
+
Please choose a username and password for the initial user.
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo tank /dev/sda3</console>
+
These will be the credentials you use to initially manage
 +
your new Zope instance.
  
{{fancyimportant|If you are using encrypted root, change '''/dev/sda3 to /dev/mapper/vault_1'''.}}
+
Username: admin
 
+
Password: ****
{{fancynote|'''ashift<nowiki>=</nowiki>12''' should be use if you have a newer, advanced format disk that has a sector size of 4096 bytes. If you have an older disk with 512 byte sectors, you should use '''ashift<nowiki>=</nowiki>9''' or don't add the option for auto detection}}
+
Verify password: ****
 
+
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''}}
+
 
+
=== Create the zfs datasets ===
+
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.
+
 
+
<console>
+
Create some empty containers for organization purposes, and make the dataset that will hold /
+
# ##i##zfs create -p tank/os/funtoo
+
# ##i##zfs create -o mountpoint=/ tank/os/funtoo/root
+
 
+
Optional, but recommended datasets: /home
+
# ##i##zfs create -o mountpoint=/home tank/os/funtoo/home
+
 
+
Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
+
# ##i##zfs create -o mountpoint=/usr/src tank/os/funtoo/src
+
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off tank/os/funtoo/portage
+
# ##i##zfs create -o mountpoint=/usr/portage/distfiles tank/os/funtoo/portage/distfiles
+
# ##i##zfs create -o mountpoint=/usr/portage/packages tank/os/funtoo/portage/packages
+
 
</console>
 
</console>
  
=== Create your swap zvol ===
+
Now, we will start our Zope instance:
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of SWAP (This is kinda big though). For machines with this much memory, You could just make it 2G if you don't have any problems.'''
+
 
<console>
 
<console>
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 1G tank/swap
+
$##bl## cd instance
 +
$##bl## bin/runzope
 
</console>
 
</console>
  
=== Format your swap zvol ===
+
Now that Zope is running, you can visit ''<tt>localhost:8080</tt>'' in your Web browser. You will see a nice introductory page to Zope.
<console>
+
# ##i##mkswap -f /dev/zvol/tank/swap
+
# ##i##swapon /dev/zvol/tank/swap
+
</console>
+
  
Now we will continue to install funtoo.
+
If you now go to the ''<tt>localhost:8080/manage</tt>'' URL, you will be prompted to log in. Enter the username and password you specified. You are now logged in to the ZMI (Zope Management Interface.)
  
== Installing Funtoo ==
+
You can stop your application by pressing Control-C. In the future, you can start and stop your Zope instance using the following commands:
[[Funtoo_Linux_Installation|Download and extract the Funtoo stage3 and continue installation as normal.]]
+
  
Then once you've extracted the stage3, chroot into your new funtoo environment:
 
 
<console>
 
<console>
Go into the directory that you will chroot into
+
$##bl## zopectl start
# ##i##cd /mnt/funtoo
+
$##bl## zopectl stop
 
+
Mount your boot drive
+
# ##i##mount /dev/sda1 /mnt/funtoo/boot
+
 
+
Bind the kernel related directories
+
# ##i##mount -t proc none /mnt/funtoo/proc
+
# ##i##mount --rbind /dev /mnt/funtoo/dev
+
# ##i##mount --rbind /sys /mnt/funtoo/sys
+
 
+
Copy network settings
+
# ##i##cp /etc/resolv.conf /mnt/funtoo/etc/
+
 
+
chroot into your new funtoo environment
+
# ##i##env -i HOME=/root TERM=$TERM chroot /mnt/funtoo /bin/bash --login
+
 
+
Place your mountpoints into your /etc/mtab file
+
# ##i##cat /proc/mounts > /etc/mtab
+
 
+
Sync your tree
+
# ##i##emerge --sync
+
 
</console>
 
</console>
  
=== Add filesystems to /etc/fstab ===
+
{{Note}} ''<tt>zopectl start</tt>'' will cause your instance to run in the background rather than consuming a shell console.
  
Before we continue to compile and or install our kernel in the next step, we will edit the /etc/fstab file because if we decide to install our kernel through portage, portage will need to know where is your /boot so that it can place the files in there. We also need to update /etc/mtab so our system knows what is mounted
+
== First Project ==
  
<console>
+
We will create a single very primitive Zope package, consisting of an Interface for a TODO class, and a TODO class.
# ##i##nano /etc/fstab
+
  
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
+
Create the following files and directories relative to your project root:
  
/dev/sda1              /boot          ext2            defaults        0 2
+
* Create the directory <tt>lib/python/example</tt>.
/dev/zvol/tank/swap    none            swap            sw              0 0
+
* Create the file <tt>lib/python/example/__init__.py</tt> by typing <tt>touch lib/python/example/__init__.py</tt>.
</console>
+
* Create these files:
  
== Kernel Configuration ==
+
=== <tt>etc/package-includes/example-configure.zcml</tt> ===
To speed up this step, you can install "bliss-kernel" since it's already properly configured for ZFS and a lot of other configurations. The kernel is also compiled and ready to go. To install 'bliss-kernel' type the following:
+
 
+
<console>
+
# ##i##emerge bliss-kernel
+
</console>
+
  
Now make sure that your /usr/src/linux symlink is pointing to this kernel by typing the following:
+
This file registers the ''<tt>example</tt>'' directory you created in ''<tt>lib/python</tt>'' as a ''package'', so that it is seen by Zope:
  
 
<console>
 
<console>
# ##i##eselect kernel list
+
<include package="example" />
Available kernel symlink targets:
+
[1]  linux-3.10.10-FB.01 *
+
 
</console>
 
</console>
  
You should see a star next to the bliss-kernel version you installed. In this case it was 3.10.10-FB.01. If it's not set, you can type '''eselect kernel set #'''.
+
=== <tt>lib/python/example/interfaces.py</tt> ===
  
== Installing the ZFS userspace tools and kernel modules ==
+
The following file defines the ''<tt>ITODO</tt>'' interface, and also uses some Zope Schema functions to define what kind of data we expect to store in objects that implement ''<tt>ITODO</tt>'':
 
+
<console># ##i##emerge -av zfs spl zfs-kmod</console>
+
 
+
(spl = Solaris Porting Layer)
+
 
+
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.
+
  
 
<console>
 
<console>
# ##i##zpool status
+
from zope.interface import Interface
# ##i##zfs list
+
from zope.schema import List, Text, TextLine, Int
</console>
+
  
If everything worked, continue.
+
class ITODO(Interface):
 
+
    name = TextLine(title=u'Name', required=True)
== Install the bootloader ==
+
    todo = List(title=u"TODO Items", required=True, value_type=TextLine(title=u'TODO'))
=== GRUB 2 ===
+
    daysleft = Int(title=u'Days left to complete', required=True)
Before you do this, make sure this checklist is followed:
+
    description = Text(title=u'Description', required=True)
* Installed kernel and kernel modules
+
* Installed zfs package from the tree
+
* /dev, /proc, /sys are mounted in the chroot environment
+
 
+
Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.
+
 
+
<console># ##i##echo "sys-boot/grub libzfs" >> /etc/portage/package.use</console>
+
 
+
Then we will compile grub2:
+
 
+
<console># ##i##emerge -av grub</console>
+
 
+
Once this is done, you can check that grub is version 2.00 by doing the following command:
+
<console>
+
# ##i##grub-install --version
+
grub-install (GRUB) 2.00
+
 
</console>
 
</console>
  
Now try to install grub2:
+
=== <tt>lib/python/example/TODO.py</tt> ===
<console># ##i##grub-install /dev/sda</console>
+
  
You should receive the following message
+
Now, we define ''<tt>TODO</tt>'' to be a ''persistent'' object, meaning it can be stored in the ZODB. We specify that it implements our previously-defined ''<tt>ITODO</tt>'' interface, and provide reasonable defaults for all values when we create a new TODO object:
<console>Installation finished. No error reported.</console>
+
 
+
If not, then go back to the above checklist.
+
 
+
=== LILO ===
+
Before you do this, make sure the following checklist is followed:
+
* /dev/, /proc and /sys are mounted.
+
* Installed the sys-fs/zfs package from the tree.
+
Once the above requirements are met, LILO can be installed.
+
 
+
Now we will install LILO.
+
<console># ##i##emerge -av sys-boot/lilo</console>
+
Once the installation of LILO is complete we will need to edit the lilo.conf file.
+
<console># ##i##nano /etc/lilo.conf
+
boot=/dev/sda
+
prompt
+
timeout=4
+
default=Funtoo
+
 
+
image=/boot/bzImage
+
      label=Funtoo
+
      read-only
+
      append="root=tank/os/funtoo/root"
+
      initrd=/boot/initramfs
+
</console>
+
All that is left now is to install the bootcode to the MBR.
+
 
+
This can be accomplished by running:
+
<console># ##i##/sbin/lilo</console>
+
If it is successful you should see:
+
 
<console>
 
<console>
Warning: LBA32 addressing assumed
+
from persistent import Persistent
Added Funtoo + *
+
from zope.interface import implements
One warning was issued
+
from example.interfaces import ITODO
</console>
+
  
== Create the initramfs ==
+
class TODO(Persistent):
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.
+
    implements(ITODO)
 
+
    name = u''
=== genkernel ===
+
    todo = []
<console>
+
    daysleft = 0
# ##i##emerge -av sys-kernel/genkernel
+
    description = u''
# You only need to add --luks if you used encryption
+
# ##i##genkernel --zfs --luks initramfs
+
 
</console>
 
</console>
  
=== Bliss Initramfs Creator ===
+
=== <tt>lib/python/example/configure.zcml</tt> ===
If you are encrypting your drives, then add the "luks" use flag to your package.use before emerging:
+
  
 +
Create an empty ''<tt>configure.zcml</tt>'' configuration file:
 
<console>
 
<console>
# ##i##echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use
+
<configure xmlns="http://namespaces.zope.org/zope"
 +
    xmlns:five="http://namespaces.zope.org/five"
 +
    xmlns:browser="http://namespaces.zope.org/browser">
 +
</configure>
 
</console>
 
</console>
  
Now install the creator:
+
== Debug Mode ==
  
 +
We can test our first project by entering debug mode:
 
<console>
 
<console>
# ##i##emerge bliss-initramfs
+
$##bl## bin/zopectl debug
 +
Starting debugger (the name "app" is bound to the top-level Zope object)
 
</console>
 
</console>
  
 
+
Now, let's try creating a new TODO object and writing it out to a ZODB database:
Then go into the install directory, run the script as root, and place it into /boot:
+
<console># ##i##cd /opt/bliss-initramfs
+
# ##i##./createInit
+
# ##i##mv initrd-<kernel_name> /boot
+
</console>
+
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.
+
 
+
== Using boot-update ==
+
=== /boot on separate partition ===
+
If you created a separate non-zfs partition for boot then configuring boot-update is almost exactly the same as a normal install except that auto detection for root does not work. You must tell boot-update what your root is.
+
==== Genkernel ====
+
If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
+
Example entry for boot.conf:
+
 
<console>
 
<console>
"Funtoo ZFS" {
+
>>> from ZODB import FileStorage, DB
        kernel vmlinuz[-v]
+
>>> storage = FileStorage.FileStorage('mydatabase.fs')
        initrd initramfs-genkernel-x86_64[-v]
+
>>> db = DB(storage)
        params real_root=ZFS=tank/os/funtoo/root
+
>>> connection = db.open()
        params += dozfs=force
+
>>> import transaction
        # Also add 'params += crypt_root=/dev/sda3' if you used encryption
+
>>> root = connection.root()
        # Adjust the above setting to your system if needed
+
>>> from example.TODO import TODO
}
+
>>> a = TODO
 +
>>> a.name = u'My TODOs'
 +
>>> a.TODOS = [ u'Do Laundry', u'Wash Dishes' ]
 +
>>> a.daysleft = 1
 +
>>> a.description = u'Things I need to do today.'
 +
>>> root[u'today'] = a
 +
>>> transaction.commit()
 
</console>
 
</console>
 
==== Bliss Initramfs Creator ====
 
If you used the Bliss Initramfs Creator then all you need to do is add 'root=<root>' to your params.
 
Example entry for boot.conf:
 
<console>
 
"Funtoo ZFS" {
 
        kernel vmlinuz[-v]
 
        initrd initrd[-v]
 
        params root=tank/os/funtoo/root quiet
 
        # If you have an encrypted device with a regular passphrase,
 
        # you can add the following line
 
        params += enc_root=/dev/sda3 enc_type=pass
 
}
 
</console>
 
 
After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
 
<console># ##i##boot-update</console>
 
 
=== /boot on ZFS ===
 
TBC - pending update to boot-update to support this
 
 
== Final configuration ==
 
=== Add the zfs tools to openrc ===
 
<console># ##i##rc-update add zfs boot</console>
 
 
=== Clean up and reboot ===
 
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.
 
 
<console>
 
Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
 
# ##i##cd /
 
# ##i##rm stage3-latest.tar.xz
 
 
Set your root password
 
# ##i##passwd
 
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!
 
 
Get out of the chroot environment
 
# ##i##exit
 
 
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
 
# ##i##umount -l proc dev sys boot
 
 
Turn off the swap
 
# ##i##swapoff /dev/zvol/tank/swap
 
 
Export the zpool
 
# ##i##cd /
 
# ##i##zpool export tank
 
 
Reboot
 
# ##i##reboot
 
</console>
 
 
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}
 
 
and that should be enough to get your system to boot on ZFS.
 
 
== After reboot ==
 
=== Create initial ZFS Snapshot ===
 
Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.
 
 
To take the snapshot of your system, type the following:
 
<console># ##i##zfs snapshot -r tank@install</console>
 
 
To see if your snapshot was taken, type:
 
<console># ##i##zfs list -t snapshot</console>
 
 
If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):
 
<console># ##i##zfs rollback tank/os/funtoo/root@install</console>
 
 
{{fancyimportant|'''For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the [[ZFS_Fun|ZFS Fun]] page.'''}}
 
  
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
[[Category:Filesystems]]
 
 
[[Category:Featured]]
 
[[Category:Featured]]
 
__NOTITLE__
 

Revision as of 14:21, 13 January 2014

This page documents how to use Zope with Funtoo Experimental, which currently has good Zope support thanks to Progress Overlay Python integration.

Contents

About Zope

Zope is an Open Source application server framework written in Python. It has an interesting history which you should familiarize yourself with before starting Zope development, as it contains several interesting twists and turns.

Zope History

Note Note: This HOWTO targets Zope 2.13, which includes Five. It is typically the version you should be using for new Zope projects.

  • There are two versions of Zope, Zope 2 and Zope 3. One might assume that Zope 3 is the version that people should use for new software development projects by default, but this is not the case. Most Zope-based projects continue to use Zope 2. Zope 3 was an attempt to redesign Zope 2 from scratch, and is completely different from Zope 2, but it was not adopted by the community.
  • There is also something called Five (named because it is "2 + 3") that backports many of the new features of Zope 3 into the Zope 2 framework. Several projects will use Zope 2 plus Five in order to use some of the newer features in Zope. Five was merged into mainline Zope 2 in early 2010, and first appeared in Zope 2.8.
  • You can learn more about the history of Zope 2, 3 and Five in the Five README.
  • To make things even more interesting, work on Zope 4 is underway, and it will be based on 2.13 rather than 3.x. It includes a number of incompatible changes with prior versions.

Zope Resources

Now that you understand what version of Zope you should be targeting (2.13), we can point you towards the correct documentation :)

The Zope 2 Book
This book provides a general introduction to Zope concepts and ZMI. It is a good place to start, but doesn't provide a direct introduction to Zope development. It's recommended that you skim through this book to familiarize yourself with Zope. It generally does not assume much prior knowledge about Web development or Python.
Zope Developer's Guide
This guide will give you a better introduction to Zope development. It assumes you already know Python. Skip chapters 1 and 2 and start in chapter 3, which covers components and interfaces. Chapter 5 covers the creation of your first product.
Five
We're not done yet. There is a bunch of stuff in Zope 2.13 that is not in the official documentation. Namely, the stuff in Five. Check out The Five Manual.
ZTK
ZTK Documentation
ZCA
A Comprehensive Guide to Zope Component Architecture offers a good introduction to the programming concepts of ZCA. We also have a new page on Zope Component Architecture which will help you to understand the big picture of ZCA and why it is useful. ZCML ("Z-camel") is a part of ZCA and was introduced in Zope 3, so typically you will find ZCML documented within Zope 3 documentation and book.
Content Components
Views and Viewlets: This tutorial on viewlets also contains some viewlet-related ZCML examples near the end. The "Content Component way" of developing in Zope seems to be a Zope 3 thing and tied to ZCML. Chapter 13+ of Stephan Richter's Zope 3 Developer's Handbook (book) seems to cover this quite well. You will probably also want to check out Philipp Weitershausen's Web Component Development with Zope 3 (book).
Zope 2 Wiki
Main wiki page for all things related to Zope 2.
docs.zope.org
This is the main site for Zope documentation.

First Steps

First, you will need to emerge net-zope/zope:

#  emerge -av zope

Zope is now installed.

Project Skeleton

Note Note: Zope should be run by a regular user account, not as the root user.

The first step in using Zope is to ensure that you are using a regular user account. Create a new directory called zope_test:

$ cd
$ mkdir zope_test

Now, enter the directory, and create an "instance", which is a set of files and directories that are used to contain a Zope project:

$ cd zope_test
$ /usr/lib/zope-2.13/bin/mkzopeinstance

You will see the following output, and will be prompted to answer a few questions:

Please choose a directory in which you'd like to install
Zope "instance home" files such as database files, configuration
files, etc.

Directory: instance
Please choose a username and password for the initial user.
These will be the credentials you use to initially manage
your new Zope instance.

Username: admin
Password: ****
Verify password: **** 

Now, we will start our Zope instance:

$ cd instance
$ bin/runzope

Now that Zope is running, you can visit localhost:8080 in your Web browser. You will see a nice introductory page to Zope.

If you now go to the localhost:8080/manage URL, you will be prompted to log in. Enter the username and password you specified. You are now logged in to the ZMI (Zope Management Interface.)

You can stop your application by pressing Control-C. In the future, you can start and stop your Zope instance using the following commands:

$ zopectl start
$ zopectl stop

Note Note: zopectl start will cause your instance to run in the background rather than consuming a shell console.

First Project

We will create a single very primitive Zope package, consisting of an Interface for a TODO class, and a TODO class.

Create the following files and directories relative to your project root:

  • Create the directory lib/python/example.
  • Create the file lib/python/example/__init__.py by typing touch lib/python/example/__init__.py.
  • Create these files:

etc/package-includes/example-configure.zcml

This file registers the example directory you created in lib/python as a package, so that it is seen by Zope:

<include package="example" />

lib/python/example/interfaces.py

The following file defines the ITODO interface, and also uses some Zope Schema functions to define what kind of data we expect to store in objects that implement ITODO:

from zope.interface import Interface
from zope.schema import List, Text, TextLine, Int

class ITODO(Interface):
    name = TextLine(title=u'Name', required=True)
    todo = List(title=u"TODO Items", required=True, value_type=TextLine(title=u'TODO'))
    daysleft = Int(title=u'Days left to complete', required=True)
    description = Text(title=u'Description', required=True)

lib/python/example/TODO.py

Now, we define TODO to be a persistent object, meaning it can be stored in the ZODB. We specify that it implements our previously-defined ITODO interface, and provide reasonable defaults for all values when we create a new TODO object:

from persistent import Persistent
from zope.interface import implements
from example.interfaces import ITODO

class TODO(Persistent):
    implements(ITODO)
    name = u''
    todo = []
    daysleft = 0
    description = u''

lib/python/example/configure.zcml

Create an empty configure.zcml configuration file:

<configure xmlns="http://namespaces.zope.org/zope"
     xmlns:five="http://namespaces.zope.org/five"
     xmlns:browser="http://namespaces.zope.org/browser">
</configure>

Debug Mode

We can test our first project by entering debug mode:

$ bin/zopectl debug
Starting debugger (the name "app" is bound to the top-level Zope object)

Now, let's try creating a new TODO object and writing it out to a ZODB database:

>>> from ZODB import FileStorage, DB
>>> storage = FileStorage.FileStorage('mydatabase.fs')
>>> db = DB(storage)
>>> connection = db.open()
>>> import transaction
>>> root = connection.root()
>>> from example.TODO import TODO
>>> a = TODO
>>> a.name = u'My TODOs'
>>> a.TODOS = [ u'Do Laundry', u'Wash Dishes' ]
>>> a.daysleft = 1
>>> a.description = u'Things I need to do today.'
>>> root[u'today'] = a
>>> transaction.commit()