% IMAGEFACTORY PLUGIN REFERENCE(7) Version 1.0 - February 22, 2012
Image Factory offers the ability to extend the support for operating systems and cloud types beyond what is included in the official releases. This document describes how plugins are used as well as how developers can write their own custom plugins.
Image Factory installs the stock plugins in the Python site-packages directory. If plugins are installed in another location, the path must exist in the PYTHON_PATH environment variable.
A symlink from the directory
/etc/imagefactory/plugins.d to the plugin’s .info file indicates that Image Factory should use the plugin.
The structure of a plugin is generally:
Example_ifplugin/ __init__.py Example_ifplugin.info ExampleMain.py ...
There are two requirements Image Factory plugins need to satisfy.
Assign delegate_class in the plugin’s initializer.
Define plugin metadata in the plugin’s info document.
When Image Factory builds, pushes, or takes a snapshot of an image, delegation is used to allow a plugin to customize the operation. The plugin must specify what class Image Factory should use to instantiate a delegate object. This is done by assigning the class to
from ExampleMain import ExampleMain as delegate_class
Here is what the module, ExampleMain.py, might contain.
import zope from imgfac.CloudDelegate import CloudDelegate class ExampleMain(object): zope.interface.implements(CloudDelegate) def builder_should_create_image(self, builder): # This is just an example, don't bother creating the image return False
A plugin must include a JSON formatted metadata file named plugin-name.info. In the example above, this file would be named Example-ifplugin.info.
The contents of this file are:
[["RHEL5", "U8", "x86_64"], ["Fedora", "16", None], ["Fedora", "17", "x86_64"]]