Extending

Event hooks

Pass hooks=[...] to Pixie(...) — each entry is a callable or a "module.function" import string. A hook

def my_hook(event, netboot, value, kwargs):
    ...
    return value

is invoked for every PixieEvent and may transform the value flowing through it. Events fire around object creation (NewPixieObject, SetPixieProperty, PixieInitiated), lookup (LookupTarget, FoundTarget, FoundTargetImage, FoundTargetDhcpzone), context construction (PixieContextForTarget), and the init/complete lifecycle (StartPixieInitialize … EndPixieComplete). This is the seam for customising how targets/images/zones are resolved and how the render context is assembled.

Custom DHCP backends

netboot.dhcp.DhcpServer dispatches on the URI scheme of a zone's dhcpservers entry: a subclass whose lowercased class name equals the scheme handles it.

from netboot.dhcp import DhcpServer

class dnsmasq(DhcpServer):        # handles dnsmasq://...
    def add_target(self, ctx):
        ...                       # arm DHCP for ctx.target
    def remove_target(self, ctx):
        ...                       # disarm it

Subclassing at any depth is honoured, so a backend may share an intermediate base. Import your plugin module before the config builds the zones — pass it via --load-module your.plugin (or list it under the config's module loading) so the DhcpServer subclass is registered when dnsmasq://... is resolved.

An unknown scheme raises a clear ValueError rather than silently doing nothing.