ETA for OMV 5.0 - 2020, 2021, 2022?

    • OMV 5.x (beta)
    • ETA for OMV 5.0 - 2020, 2021, 2022?

      @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 :D ).
      And how long will the transition phase be this time?

      Thanks for your precious time and please don't feel rushed! :saint:
    • I think OMV5 will be released after Debian 10.1. From my side all features are done in OMV5.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • It's done when it's done :) But good to hear that 10.1 is coming soon.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • David B wrote:

      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 - forum.openmediavault.org/index…?postID=186122#post186122
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • votdev wrote:

      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.
    • I have the feeling that OMV5 requires more beta testers before it is released.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Mr Smile wrote:

      votdev wrote:

      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.

      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.
    • ETA for OMV 5.0 - weeks, months, quarters, 2020?

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

      Thanks Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - tvos | android tv | libreelec | win10 | kodi krypton
      frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
      -------------------------------------------
      backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • 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.
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      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.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • 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
    • ness1602 wrote:

      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.
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Source Code

      1. root@OMV:~# apt install -f
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      6. 1 not fully installed or removed.
      7. After this operation, 0 B of additional disk space will be used.
      8. Setting up openmediavault-omvextrasorg (5.1.4) ...
      9. Updating configuration database ...
      10. Running migration conf.system.omvextras_5.0.4
      11. Running migration conf.system.omvextras_5.1
      12. dpkg: error processing package openmediavault-omvextrasorg (--configure):
      13. installed openmediavault-omvextrasorg package post-installation script subprocess returned error exit status 1
      14. Processing triggers for openmediavault (5.0.14-1) ...
      15. Updating locale files ...
      16. Updating file permissions ...
      17. Purging internal cache ...
      18. Restarting engine daemon ...
      19. Errors were encountered while processing:
      20. openmediavault-omvextrasorg
      21. E: Sub-process /usr/bin/dpkg returned an error code (1)
      Display All
    • Unfortunately, that is after that initial install. Was omv-extras 4.x installed when you installed it?
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Users Online 8

      2 Members and 6 Guests