[Users] oVirt 3.5 planning

[Sven Kieske]

Hi,

as Dan told me I'm gonna add one more feature request:

IPv6 Support for engine and compute nodes, so you are
able to use oVirt in an IPv6 only environment.

Currently ComputeNodes require their own IPv4 address.

I don't know if and what upstream dependencies might exist
but I think it is worth the effort, not speaking of
getting into some mainline distributions.

(AFAIK Fedora has a policy that all daemons which are
facing the network must support IPv6 ?)

It is the year 2014, we are running out of IPv4 addresses
world wide.

Every new product like oVirt should try it's best to support
IPv6 in general.


A second feature:

Fencing Hosts from engine, I already created a BZ for this one:

https://bugzilla.redhat.com/show_bug.cgi?id=1054778

In fact, it's target release was already set to 3.5
but that doesn't always mean it will make it ;)

This feature would really be helpful for local storage
DCs.

If I had to decide which one gets in I'd want the fencing from
engine.

Am 24.02.2014 17:59, schrieb Itamar Heim:
> with oVirt 3.4 getting close to GA with many many great features, time
> to collect requests for 3.5...

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen