OMV 5.0 - finally out! :-)

Mr Smile · Jul 12th 2019

@votdev I know this is an extremely unpopular question, but can you estimate roughly when OMV 5.0 Usul will be ready for release?

Throughout the next weeks I planned to put a new server into operation and would like to know if it is worth waiting for the new version. I just don't want to take the trouble again to set everything up twice in a row.
That's exactly what happened to me when Arrakis was released. The transition time between Arrakis Release and Erasmus EOL had been 2 months only, if I remember correctly.

I can see that there is an Usul beta on Sourceforge already and installing a Debian 9 right now feels a bit wrong to me too.

I deliberately don't ask for a date. Please just give me your estimation if it's a question of weeks, months, quarters (or years ).
And how long will the transition phase be this time?

Thanks for your precious time and please don't feel rushed!

votdev · Jul 12th 2019

I think OMV5 will be released after Debian 10.1. From my side all features are done in OMV5.

Mr Smile · Jul 12th 2019

Quote from votdev

I think OMV5 will be released after Debian 10.1. From my side all features are done in OMV5.

Thanks for this statement. Sounds to me like a good plan. Then I'm going to wait patiently.

WastlJ · Jul 31st 2019

FYI:

stable (10.1) Planned for 2019-09-07

Source: https://release.debian.org/

votdev · Aug 6th 2019

It's done when it's done But good to hear that 10.1 is coming soon.

KM0201 · Aug 17th 2019

Woops, wrong thread.

David B · Aug 24th 2019

Looking forward to OMV5! And also OMV6's upcoming new UI. Regarding OMV5, how compatible are OMV4 plugins with 5? Will they mostly work or should I expect things to break?

ryecoaaron · Aug 24th 2019

Quote from David B

how compatible are OMV4 plugins with 5?

They aren't. That is why they are being ported. Here is the post I keep updated with the porting status - https://forum.openmediavault.o…?postID=186122#post186122

Mr Smile · Nov 17th 2019

Quote from votdev

I think OMV5 will be released after Debian 10.1. From my side all features are done in OMV5.

Debian 10.2 is out now. Just wanted to ask if plans have changed. Somewhere else in the forum I've read about planned features and GUI changes for OMV6. Talking about v6 while all people are waiting for v5 sounds a bit strange to me. Is v5 maybe left out completely? At least it may have a rather short release cycle as according to one blog post from August the ETA of OMV6 is 2020.

Please don't get it wrong! I'm thankful for having OMV at all and I understand why fixed release dates are problematic but I have to say that from my user perspective I'm very uncomfortable with this current situation. In a perfect world new OMV versions should somehow align with new debian releases. This would give us users a perspective of (2 year) long term stability and give you ( votdev , @ryecoaaron) more air to breath between two releases.

For me long term stability (while at the same time using an actively supported version) is more important than having the most bleeding edge features available. In this sense I'm a bit shocked to see so many users asking questions in forum about completely outdated versions.

Having a somehow "fixed" 2 year release cycle like debian (and routine upgrade paths) could also train users to upgrade more often. I admit I would also prefer not to touch a system that is running and doing its job for years. Having to care for a dist upgrade every two years while being up-to-date in between seems to me like a good tradeoff.

votdev · Nov 17th 2019

I have the feeling that OMV5 requires more beta testers before it is released.

HannesJo · Nov 19th 2019

Quote from Mr Smile

Debian 10.2 is out now. Just wanted to ask if plans have changed. Somewhere else in the forum I've read about planned features and GUI changes for OMV6. Talking about v6 while all people are waiting for v5 sounds a bit strange to me. Is v5 maybe left out completely? At least it may have a rather short release cycle as according to one blog post from August the ETA of OMV6 is 2020.
Please don't get it wrong! I'm thankful for having OMV at all and I understand why fixed release dates are problematic but I have to say that from my user perspective I'm very uncomfortable with this current situation. In a perfect world new OMV versions should somehow align with new debian releases. This would give us users a perspective of (2 year) long term stability and give you ( votdev , @ryecoaaron) more air to breath between two releases.

For me long term stability (while at the same time using an actively supported version) is more important than having the most bleeding edge features available. In this sense I'm a bit shocked to see so many users asking questions in forum about completely outdated versions.

Having a somehow "fixed" 2 year release cycle like debian (and routine upgrade paths) could also train users to upgrade more often. I admit I would also prefer not to touch a system that is running and doing its job for years. Having to care for a dist upgrade every two years while being up-to-date in between seems to me like a good tradeoff.

Actually you can set up your server using OMV 5. What is the difference if votdev has the status officially as released or still as BETA? That doesn't even change the development status. If you need features from Debian 10 or OMV 5, nobody prevents you from using them. I do and have no problems with it.

ness1602 · Nov 19th 2019

OMV 5 is okay ATM. The upgrade isn't that peachy(i had some trouble with zfs upgrading and omvextras),but can be done.
I personally don't see the difference betweend OMV4 and OMV5

hoppel118 · Nov 19th 2019

Can you describe the trouble with zfs in more detail please?

Thanks Hoppel

ryecoaaron · Nov 19th 2019

While I probably should change it, omv-extras doesn't have an upgrade path since OMV 5.x wasn't originally going to have an upgrade path from OMV 4.x. This probably caused the zfs upgrade issues.

votdev · Nov 19th 2019

Quote from ryecoaaron

since OMV 5.x wasn't originally going to have an upgrade path from OMV 4.x.

This is true. It seems to work, but there was really no intention because there were too many changes, e.g. switching from Debian network configuration to systemd-networkd.

Adoby · Nov 19th 2019

How long can OMV 4 be expected to be left alive? A year?

ness1602 · Nov 19th 2019

I upgradaed debian( change stretch -> buster) with apt dist-upgrade. Restarted the machine. Installed OMV5 by volker's guide. Installed omv5extras from the site. And there are some problems stilll with extras,cause i have flasmemory plugin version 4, but everything else is version 5.
I had to remove all zfs things, install proxmox 5.3 kernel and then install zfs-zed and zfs utils.
The procedure is somewhat skethcy, but i wanted to try it at home, because i have a ferw

ryecoaaron · Nov 19th 2019

Quote from ness1602

And there are some problems stilll with extras,cause i have flasmemory plugin version 4, but everything else is version 5.

Installing the new version of omv-extras should upgrade the repo list and apt-get update should update the package list. If a plugin didn't get upgrade, something went wrong with apt and omv-extras can't fix that. I would be very curious to see the output from the upgrade.

ness1602 · Nov 19th 2019

Code

root@OMV:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openmediavault-omvextrasorg (5.1.4) ...
Updating configuration database ...
  Running migration conf.system.omvextras_5.0.4
  Running migration conf.system.omvextras_5.1
dpkg: error processing package openmediavault-omvextrasorg (--configure):
 installed openmediavault-omvextrasorg package post-installation script subprocess returned error exit status 1
Processing triggers for openmediavault (5.0.14-1) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Errors were encountered while processing:
 openmediavault-omvextrasorg
E: Sub-process /usr/bin/dpkg returned an error code (1)

Display More

ryecoaaron · Nov 19th 2019

Unfortunately, that is after that initial install. Was omv-extras 4.x installed when you installed it?

Participate now!