#4864 Need rel-eng approval for oVirt Node Spin to give to Fedora Board for trademark approval process.
Closed: Invalid None Opened 12 years ago by rbergero.

https://fedoraproject.org/wiki/Ovirt_Node_Spin

Need a +1 on this spin to get this through the board trademark approval process.


at the moment im -1

we shouldn't be using ext2 for the filesystem

cleanup rpmdb to allow non-matching host and chroot RPM versions

rm -f /var/lib/rpm/__db*

we shouldnt be doing that. we compose all images on the target os and its just kinda icky

strip out all unncesssary locales

localedef --list-archive | grep -v -i -E 'en_US.utf8' |xargs localedef --delete-from-archive
mv /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.tmpl
/usr/sbin/build-locale-archive

we should leave the locales alone, we have a large portion of non english speaking users.

fedora-release needs to be installed. it sets up some important variable for a working yum as well as defining on the system what version of fedora this is.

we shouldn't be using ext2 for the filesystem

We use it to be able share R/O root among multiple nodes, ext2 is w/o journal so it safe for R/O access (ext >=3 mounted ro still can modify the image with journal recovery).

cleanup rpmdb

We can remove that, we need it for internal build system where builder host is older (rhbz#590104).

we should leave the locales alone, we have a large portion of non english speaking users.
fedora-release needs to be installed. it sets up some important variable for a working yum...

The goal of ovirt node image is to provide minimal OS environment for running virtual machines in the smallest footprint possible and image is treated as firmware: single package updates are not allow and yum is not installed. Upgrade is performed by updating the whole image.
There's standalone use-case where users log into oVirt Node console but in the managed node where node automatically registers with the management server, users don't need to ever look at node console, so English only locale is acceptable. It is not desktop spin, it's a server spin.
If that doesn't match Fedora goals, then we can continue building on our oVirt brand, but we thought it made sense to have minimal hypervisor spin provided within Fedora and we adjusted to Spin SIG rules by removing image minimization step from kickstart (ISO size ~250MB, with minimization ~150)

sorry been awhile here,

this basically goes against everything that is fedora, id want to get feedback from the board, and fesco before saying yes or no. but i'm heavily favouring saying no. we do not update spins once we have shipped them. users will be expecting to use this for the whole 13 months of a fedora release and there is the potential that there are hypervisor vulnerabilities that we can never get a fix onto machine for, since we wont ever push out a updated image.

Sorry, I forgot to update this ticket: we decided to drop ovirt node spin in Fedora, and keep doing Remix based on Fedora.

Metadata Update from @rbergero:
- Issue assigned to ausil
- Issue set to the milestone: Fedora 16 Beta

7 years ago

Login to comment on this ticket.

Metadata