Good question.
But I can assure you that not everything is golden goose.
Sometimes there is legacy, lack of knowledge, and so on, and there are many use cases
where a full test env is not a given.
It is desired yes, but currently not an option.
By the way, to quote some famous people, everyone has a test environment, only few of us
are lucky enough to have prod env as well.
And based on the problems we encountered recently, which were upgrade related, it would
have been difficult to have a 1:1 test env anyway, as this issue for sure would not have
been caught.
Cheers,
On 6 Mar 2017, at 13:28, Sven Kieske <s.kieske(a)mittwald.de>
wrote:
On 06/03/17 10:48, Andrea Ghelardi wrote:
> A) there could be no test environment to check the upgraded version behavior
and
>
> B) the upgrade itself may require more than a bit of effort when there are dozen
hosts and multiple clusters involved,
> this does not really encourage to always push the datacenter to the latest version
available, especially if the in-production version is not misbehaving.
>
> Please note I'm just sharing our company view and not blaming anyone.
>
> Cheers
> Andrea
As a side note:
What kind of data center do you run, that lacks any test environment?
If you don't have a testbed, than you have far worse problems than the
number of bugfixes and things which might (not) work in a new ovirt version.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +495772 293100
F: +495772 293333
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
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users