Hugh asked me yesterday to post on the list the issues i found out when
going though the docs/download/install steps, so here there are:
+ lack of global overview, it's very hard just by reading the docs
to see what ovirt requires, what it provides. Suggested some kind
of diagram might help, see attached a rough first version using
xfig, that may do it until someone with graphic skills and taste
refines it (and assuming i got all concepts right)
see attached ovirt.fig and ovirt.png
+ related to it, it's really good to have a glossary, use only the
same terms though the documentation for the same pieces of the
infrastructure. Ideally this should match libvirt terminology
(Node/Hypervisor/Domain), in the graphic I made:
- Console Node: for the physical machine running the WUI appliance
- Cluster Nodes: for the physical barebone machines used to run
the user domains
- WUI appliance: the domain running the services needed for ovirt
provisionning, authentication and management
- managed domains: for the domains the user actually want to run and
control
those terms are my pick, I find
'oVirt host(s)' and 'oVirt management host' too similar to
the point
they are confusing and not matching libvirt own terminology, sorry :-)
+ it's hard to see the requirement for installing my current list so
far is:
- one 64bits machine with an existing OS and KVM support to run the
WUI appliance domain, 2-3 GB available in the root user directory
(Xen based fully virt may work also with tweaking)
- at least one node for the cluster, a bare machine, able to
PXE boot (ideally otherwise booting from a CD or USB key)
64bits with hardware virtualization support
- at least one network connecting the machines and DNS and DHCP
for that network are under the user control (this may be relaxed
in the future)
General feedback is that this is a very contraining set, which may put
many 'would be' testers off, it's really better to put those
upfront
nothing is worse from their viewpoint than spending time for nothing,
on the other hand being explicit may get some of them in an helping mood
since we generally want to remove/ease a lot of those requirements.
+ some errors in the installation documentation at
http://ovirt.org/install-instructions.html
- "Move the image (wui-appliance.dsk.bz2) to /root and unzip it:
# tar -jxvf /root/wui-appliance.dsk.bz2"
This is actually a bzipped image and tar should not be used
# bunzip2 /root/wui-appliance.dsk.bz2
- in the default wui-appliance.xml, it is set up to boot from
a CDRom image:
<boot dev='cdrom' />
and later
<disk type='file' device='cdrom'>
<source file='/root/boot.iso' />
<target dev='hdc' />
</disk>
the first definition should be changed to
<boot dev='hd'/>
and the block describing the CDRom should be removed
so that the appliance actually boots from /root/wui-appliance.dsk
image.
- WUI domain creation instruction should be for KVM as the XML provided
is for KVM, so the command:
# virsh create /path/to/wui-appliance.xml
needs an extra
-c qemu:///system
argument to actually work
- Building the appliance from a kickstart is actually hard to set up,
do not suggest it as a way to avoid the time of the download
"Booting and provisioning a host or a VM with a kickstart is left
as an exercise for the reader."
is condescending, actually very hard, get rid of the section, assume
user will follow the standard track (download + using KVM), but document
separately the process for rebuilding the appliance, and changes needed
to run it as a Xen fully-virt domain (I assume only the xml and way to
launch the applicance need changes)
I guess it's all so far, i hope it will help going forward and ease
newcomers willing to test and help :-)
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
-------------- next part --------------
#FIG 3.2 Produced by xfig version 3.2.5
Landscape
Center
Inches
Letter
100.00
Single
-2
1200 2
6 6075 1125 11175 5100
2 2 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
6150 1200 8550 1200 8550 5025 6150 5025 6150 1200
2 2 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
8700 1200 11100 1200 11100 5025 8700 5025 8700 1200
2 1 0 1 0 7 50 -1 -1 4.000 0 0 -1 0 0 2
6150 4425 8550 4425
2 1 0 1 0 7 50 -1 -1 4.000 0 0 -1 0 0 2
8700 4425 11100 4425
2 3 0 1 0 1 50 -1 20 0.000 0 0 0 0 0 7
6780 4912 6975 4800 6975 4574 6780 4462 6585 4575 6585 4800
6780 4912
2 3 0 1 0 1 50 -1 20 0.000 0 0 0 0 0 7
9255 4912 9450 4800 9450 4574 9255 4462 9060 4575 9060 4800
9255 4912
2 4 0 2 0 7 50 -1 -1 6.000 0 0 7 0 0 5
8325 2550 8325 1425 6375 1425 6375 2550 8325 2550
2 4 0 2 0 7 50 -1 -1 6.000 0 0 7 0 0 5
8325 3900 8325 2775 6375 2775 6375 3900 8325 3900
2 4 0 2 0 7 50 -1 -1 6.000 0 0 7 0 0 5
10875 3000 10875 1875 8925 1875 8925 3000 10875 3000
4 0 0 50 -1 0 18 0.0000 4 255 1095 6825 1950 managed\001
4 0 0 50 -1 0 18 0.0000 4 195 915 6900 2250 domain\001
4 0 0 50 -1 0 18 0.0000 4 255 1095 6825 3300 managed\001
4 0 0 50 -1 0 18 0.0000 4 195 915 6900 3600 domain\001
4 0 0 50 -1 0 18 0.0000 4 255 1095 9375 2400 managed\001
4 0 0 50 -1 0 18 0.0000 4 195 915 9450 2700 domain\001
-6
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
1050 4425 4125 4425
2 2 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
1050 1200 4125 1200 4125 5025 1050 5025 1050 1200
2 4 0 2 0 7 50 -1 -1 0.000 0 0 7 0 0 5
3975 4200 2025 4200 2025 1425 3975 1425 3975 4200
2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 6.00 60.00 120.00
2775 5925 2775 5025
2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 6.00 60.00 120.00
7275 5925 7275 5025
2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 6.00 60.00 120.00
9675 5925 9675 5025
2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 1 1 2
1 1 6.00 60.00 120.00
1 1 6.00 60.00 120.00
675 5925 11850 5925
2 4 1 1 0 7 50 -1 -1 4.000 0 0 7 0 0 5
3900 4125 3900 3150 2100 3150 2100 4125 3900 4125
2 3 0 1 0 1 50 -1 20 0.000 0 0 0 0 0 7
3420 3937 3615 3825 3615 3599 3420 3487 3225 3600 3225 3825
3420 3937
2 1 0 1 0 7 50 -1 -1 4.000 0 0 -1 0 0 3
3300 1425 3975 900 3975 525
2 1 1 2 1 7 50 -1 -1 6.000 0 0 -1 1 0 3
1 1 6.00 60.00 120.00
7425 5850 9975 5850 9975 4875
2 1 1 2 1 7 50 -1 -1 6.000 0 0 7 1 1 4
1 1 6.00 60.00 120.00
1 1 6.00 60.00 120.00
3075 4050 3075 5850 7425 5850 7425 4800
2 4 1 1 0 7 50 -1 -1 4.000 0 0 7 0 0 5
3375 3075 3375 2325 2100 2325 2100 3075 3375 3075
2 4 1 1 0 7 50 -1 -1 4.000 0 0 7 0 0 5
3825 2175 3825 1500 2700 1500 2700 2175 3825 2175
4 0 0 50 -1 0 18 0.0000 4 195 1635 1425 4725 KVM or Xen\001
4 0 0 50 -1 0 18 0.0000 4 195 810 2175 3450 DHCP\001
4 0 0 50 -1 0 18 0.0000 4 255 765 2175 3825 Image\001
4 0 0 50 -1 0 18 0.0000 4 195 690 3150 3450 TFTP\001
4 0 0 50 -1 0 26 0.0000 4 300 2490 6900 900 Cluster Nodes\001
4 0 0 50 -1 0 26 0.0000 4 300 2505 900 900 Console Node\001
4 0 0 50 -1 0 18 0.0000 4 270 1860 4125 675 WUI appliance\001
4 0 0 50 -1 0 18 0.0000 4 195 915 4125 975 domain\001
4 0 0 50 -1 0 18 0.0000 4 195 1125 2175 2625 Kerberos\001
4 0 0 50 -1 0 18 0.0000 4 195 615 2400 2925 DNS\001
4 0 0 50 -1 0 18 0.0000 4 195 900 2850 1800 WebUI\001
4 0 0 50 -1 0 18 0.0000 4 255 930 2850 2100 Apache\001
4 0 -1 50 -1 0 18 0.0000 4 255 1590 4200 1950 Management\001
4 0 -1 50 -1 0 18 0.0000 4 255 1710 4200 3600 Provisionning\001
4 0 -1 50 -1 0 18 0.0000 4 195 1830 4200 2850 Authentication\001
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt.png
Type: image/png
Size: 10244 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20080215/e34f387e/attachment.png>
Daniel P. Berrange
2008-Feb-15 14:32 UTC
[Ovirt-devel] A few things (rather long actually)
On Fri, Feb 15, 2008 at 06:26:26AM -0500, Daniel Veillard wrote:> + related to it, it's really good to have a glossary, use only the > same terms though the documentation for the same pieces of the > infrastructure. Ideally this should match libvirt terminology > (Node/Hypervisor/Domain), in the graphic I made: > - Console Node: for the physical machine running the WUI applianceThat's a reasonable choice, or possibly 'Admin node'.> - Cluster Nodes: for the physical barebone machines used to run > the user domainsThe choice of the word 'cluster' is not good - the managed nodes can be standalone, or they can be clustered. I prefer 'Managed nodes'.> - WUI appliance: the domain running the services needed for ovirt > provisionning, authentication and management > - managed domains: for the domains the user actually want to run and > control > those terms are my pick, I find > 'oVirt host(s)' and 'oVirt management host' too similar to the point > they are confusing and not matching libvirt own terminology, sorry :-)We can add a glossary of terms to the documentation area of the website, or even better put it in the wiki so anyone can add entries for things they think need explaining.> + it's hard to see the requirement for installing my current list so > far is: > - one 64bits machine with an existing OS and KVM support to run the > WUI appliance domain, 2-3 GB available in the root user directory > (Xen based fully virt may work also with tweaking) > - at least one node for the cluster, a bare machine, able to > PXE boot (ideally otherwise booting from a CD or USB key) > 64bits with hardware virtualization support > - at least one network connecting the machines and DNS and DHCP > for that network are under the user control (this may be relaxed > in the future) > General feedback is that this is a very contraining set, which may put > many 'would be' testers off, it's really better to put those upfront > nothing is worse from their viewpoint than spending time for nothing, > on the other hand being explicit may get some of them in an helping mood > since we generally want to remove/ease a lot of those requirements.I've expanded the detail in the FAQ to give much more info about the requirements for deployment - can you take a look at it on the website now. I think it covers the points you raise here.> - Building the appliance from a kickstart is actually hard to set up, > do not suggest it as a way to avoid the time of the download > "Booting and provisioning a host or a VM with a kickstart is left > as an exercise for the reader." > is condescending, actually very hard, get rid of the section, assume > user will follow the standard track (download + using KVM), but document > separately the process for rebuilding the appliance, and changes needed > to run it as a Xen fully-virt domain (I assume only the xml and way to > launch the applicance need changes)I'd like to get to a place where building an either the wui appliance, or the managed host appliance consists of nothing more than invoking the Fedora livecd-creator tool. There is some work going on to make the livecd-creator more general purpose, so I think this is doable in the the Fedora 9 timescale. Just a reminder to anyone with suggestions - the wiki is available for any adhoc content you think will be useful to others... Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|