In order To improve the ease of installation, we are working on two new tools:
1. Fedora oVirt spin
We are planning on integrating oVirt to a live fedora spin[1]
This will simplify the the installation for new users. It will contain the oVirt "AllInOne" [2] on top of a Fedora liveCD desktop.
This will allow users to experiment with oVirt before later installing it.
The idea is user will install fedora from the CD, then answer the questions of the all-in-one setup.
2. Simple demo environment
As a second stage, for simple demo use cases, we want to take this one step further.
We'd like to extend this live spin to include a complete environment - sample vm/template/iso/node,etc so that a user can boot from a USB key and have a complete environment that's pre-installed and configured, this will probably will be done with a script calling one of the APIs[3] to create it.
The user would download an image, write it to a USB disk and then boot it[4].
the idea is user can copy this iso to a usb disk (or a qcow/vdmk) and
Once booted the user will have a pre-installed, pre-configured oVirt Engine, host and local storage domain complete with ISOs, VM and template.
any suggestions/help will be appreciated
[1]http://fedoraproject.org/wiki/Spins_Custom
[2]http://wiki.ovirt.org/wiki/Feature/AllInOne
[3]http://wiki.ovirt.org/wiki/CLI |http://wiki.ovirt.org/wiki/SDK
[4] bare metal or nested virtualization

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFC112D71993FC584DA975D1C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Garrett's new MediaWiki skin is getting close to completion, and it
happens to run on MediaWiki 1.19, which we need to upgrade to.
We have a few approaches:
1. Staggered upgrade - update MediaWiki 1.19 (either with an RPM or
ZIP), test, then update the theme. Do move to OpenShift as another proces=
s.
2. One rollover - create the new site with the new version and the new
theme on OpenShift, import the data (pages and users), test; then freeze
the old wiki, do a final import of pages and users, and roll over DNS to
the OpenShift instance.
Advantages? Disadvantages? Different approaches?
Garrett - we have our install at /wiki, which is a bit standard, and
there are reasons AIUI:
http://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory
Note the admonition that doing the wiki at root-level means no support
from Wikimedia developers.
The idea to make the MediaWiki instance the entire site means we need to
decide how we want www.ovirt.org to resolve, same with wiki.ovirt.org,
and do we hack MediaWiki to make it work with / instead of /wiki.
- Karsten, who wrote all this when about to check on the situation with
MediaWiki 1.19 in Fedora/EPEL, and realized we could skip the problem by
using OpenShift directly and immediately.
--=20
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org .^\ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
--------------enigFC112D71993FC584DA975D1C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iD8DBQFQY30G2ZIOBq0ODEERAikdAJ0ZAmalWITyFe/JzFp+5D5FVXEpNQCfZoVx
mFRgnovPojNyP7VgUDa8pPM=
=OXB8
-----END PGP SIGNATURE-----
--------------enigFC112D71993FC584DA975D1C--