Is this now the correct way to install OMV [Sanity check]

1uke_ · 7. Mai 2020

Hello,

It's a while since I have last installed OMV.

I wanted to check I am not missing anything obvious.

I will be installing OMV on a Rock64 single board computer.

Is my understanding of the installation method correct?

1. Download and install Armbian buster

2. At the armbian buster terminal run - wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

***

I know this seems like a daft questions but in the past I am sure there was an .ISO that you could download and there was no need to install Armbian buster first.

ryecoaaron · 7. Mai 2020

There are ISOs for amd64 but never for arm boards. There used to be an image that OMV already installed but it was a nightmare to maintain and OMV 5 doesn't install in chroot (needed to create an image). So, I wrote a script to install it on an armbian maintained image.

This guide has all the info you need - Installing OMV5 on Raspberry PI's, Armbian SBC's, & i386 32-bit platforms but your basic method is right.

1uke_ · 7. Mai 2020

Thanks for the reply ryecoaaron

I think in the past I had installed on amd64.

Is there any benefits or drawbacks to installing Armbian first and then OMV as a service compared with just running from an image?

Anything I need to be aware or careful off?

ryecoaaron · 7. Mai 2020

Zitat von 1uke_

Is there any benefits or drawbacks to installing Armbian first and then OMV as a service compared with just running from an image?

The image was created the same way the install script installs on armbian. It just did it in chroot. Installing omv 4 in chroot was possible. OMV 5 in chroot is not possible because of saltstack issues. Either way, there is really no difference. Keeping the script up to date for the latest changes is MUCH easier than rebuilding a ton of images for all of the boards that we used to have images for.

Zitat von 1uke_

Anything I need to be aware or careful off?

Nope. I have installed using the script a few times in the last few days on a rock64.

1uke_ · 7. Mai 2020

Awesome thank you ryecoaaron

I really appreciate you letting me know that I am doing the right thing.

Thank you for your help!

motomouse · 9. Mai 2020

Zitat von ryecoaaron

Nope. I have installed using the script a few times in the last few days on a rock64.

Just for your information : I'm not sure if this is just me, or general issue, but using the method from the pdf guide is giving some deprecation warnings :

Python

/usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working

from collections import Iterable, Mapping, namedtuple

/usr/lib/python3/dist-packages/salt/utils/jinja.py:630: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working

if isinstance(lst1, collections.Hashable) and isinstance(lst2, collections.Hashable):

Python

/usr/lib/python3/dist-packages/salt/states/file.py:294: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working

from collections import Iterable, Mapping, defaultdict

Code

/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly

*salt.utils.args.get_function_argspec(original_function)

ryecoaaron · 10. Mai 2020

Zitat von motomouse

sing the method from the pdf guide is giving some deprecation warnings

They are warnings not errors from saltstack. They do not cause a problem and you will get them not matter how you install/configure OMV.

Jetzt mitmachen!