Hi,
I've noticed the Debian packages https://packages.debian.org/source/jessie-backports/lizardfs and the packages from packages.lizardfs.com are different:
- /etc/mfs instead of /etc/lizardfs
- mfs user and group instead of lizardfs
- /var/lib/mfs for the metadata instead of /var/lib/lizardfs
It is confusing for people who want to automate the installation of LizardFS because the default values are not the same depending on the package source. It would be better if the default directories were unified.
I suggest you to unify the default user / directory in packages.lizardfs.com with Debian. The user/group lizardfs and the directory /etc/lizardfs is a good choice because LizardFS is not MooseFS and shouldn't share the same directories as MooseFS. It could also be the opposite (Debian unified with your packages, with a backward compatibility).
I've noticed this because I'm developing a Puppet module to automate the configuration of LizardFS https://github.com/Asher256/puppet-lizardfs and I added a new parameter today (manage_repos=true) to give to the users the possibility to use the repository packages.lizardfs.com instead of the Debian repositories. I'll try to find a solution for my automated module, but it is a little bit confusing. I will maybe force some parameters on all operating systems (like /etc/lizardfs for example) to avoid this kind of issues.
Thank you.
Asher256
Hi,
I've noticed the Debian packages https://packages.debian.org/source/jessie-backports/lizardfs and the packages from packages.lizardfs.com are different:
It is confusing for people who want to automate the installation of LizardFS because the default values are not the same depending on the package source. It would be better if the default directories were unified.
I suggest you to unify the default user / directory in packages.lizardfs.com with Debian. The user/group lizardfs and the directory /etc/lizardfs is a good choice because LizardFS is not MooseFS and shouldn't share the same directories as MooseFS. It could also be the opposite (Debian unified with your packages, with a backward compatibility).
I've noticed this because I'm developing a Puppet module to automate the configuration of LizardFS https://github.com/Asher256/puppet-lizardfs and I added a new parameter today (manage_repos=true) to give to the users the possibility to use the repository packages.lizardfs.com instead of the Debian repositories. I'll try to find a solution for my automated module, but it is a little bit confusing. I will maybe force some parameters on all operating systems (like /etc/lizardfs for example) to avoid this kind of issues.
Thank you.
Asher256