1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
[% topdir = ".." -%]
[% PROCESS globals -%]
[% WRAPPER page
title = "Frequently Asked Questions (FAQ) about virt tools"
h1 = "Frequently Asked Questions (FAQ) about virt tools"
section = "faq"
local_stylesheet = 1
%]
[%-
# We could put this array in globals.
questions = [
{ name = "who",
q = "Who wrote these tools? Is this just a Red Hat / Fedora project?",
a = "
<p>
These tools are all open source and available on several Linux
distributions, including Fedora, Debian, Ubuntu and Gentoo,
and some of the programs have also been ported to
Mac OS X and Windows.
</p>
<p>
All of these projects solicit input from the widest possible
community, and libvirt in particular has active developers
from all the major Linux distros.
</p>
<p>
Red Hat sponsors some of the developers, Canonical are active in
libvirt development, Novell employees have sent patches, and
others projects and people come from the rest of the community.
</p>
<p>
If a tool you need is not available on your distro of choice,
please help to port it.
</p>" },
{ name = "why-virt-tools",
q = "Why are they called <q>virt tools</q>?",
a = "
<p>
Simply because most of the command line tools are called
virt-<i>something</i> (such as <code>virt-df</code> and
<code>virt-manager</code>) and so the name <q>virt tools</q>
stuck.
</p>" },
{ name = "project-criteria",
q = "Can you feature my project? What are the criteria for being called a virt tool?",
a = "
<p>
The project must be open source with an active upstream community.
It must complement the existing virt tools (in particular it should
use libvirt for lifecycle management).
</p>
<p>
Generally we focus on small tools which are useful for
system administrators who are responsible for a few physical machines.
</p>
<p>
The tool should be easy to install
(eg. just <code>apt-get install</code> / <code>yum install</code>,
not needing an expensive consultant to visit you on site!)
</p>
<p>
Our focus is on Linux tools, although a Windows- or Mac-only program
wouldn't be out of the question if it met the other criteria above.
</p>" },
]
-%]
<ul>
[% FOREACH x IN questions -%]
<li> <a href="#[% x.name %]">[% x.q %]</a> </li>
[%- END %]
</ul>
[% FOREACH x IN questions -%]
[% WRAPPER h2 h2=x.q anchor=x.name %]
[% x.a %]
[% END %]
[%- END %]
[% END -%]
|
