It's been a while since I wrote an article about a cool feature that we introduced together with Software Collections packaging format, which is *the ability to share the environment on multiple machines by NFS sharing *[1].
The idea is very simple -- install Software Collections of your favorite application stack (say Python 3.6 + NodeJS 8) and mount the /opt/rh on workstations. That way you have the same environment on all machines.
Now, I'd like to request some feedback -- is there anybody on the list (or outside, but you at least know about it) who uses this feature for the Software Collections packages?
Please, let us know! If you can't share it publicly, just drop me a direct mail. Of course, more feedback is welcome, but even simple YES would be also cool.
[1] https://developers.redhat.com/blog/2015/06/29/maintain-software-collections-...
Thanks! Honza
Am 09.02.2018 um 16:03 schrieb Honza Horak hhorak@redhat.com:
It's been a while since I wrote an article about a cool feature that we introduced together with Software Collections packaging format, which is *the ability to share the environment on multiple machines by NFS sharing *[1].
The idea is very simple -- install Software Collections of your favorite application stack (say Python 3.6 + NodeJS 8) and mount the /opt/rh on workstations. That way you have the same environment on all machines.
Now, I'd like to request some feedback -- is there anybody on the list (or outside, but you at least know about it) who uses this feature for the Software Collections packages?
Please, let us know! If you can't share it publicly, just drop me a direct mail. Of course, more feedback is welcome, but even simple YES would be also cool.
[1] https://developers.redhat.com/blog/2015/06/29/maintain-software-collections-...
Honestly, all SCL packages that we (re)build locally, are build with "rpmbuild --define 'nfsmountable 0'" ... (because we do not have such scenario).
-- LF
Le 09/02/2018 à 18:00, Leon Fauster a écrit :
Honestly, all SCL packages that we (re)build locally, are build with "rpmbuild --define 'nfsmountable 0'" ... (because we do not have such scenario).
IMHO, this option is very badly named (as it doesn't handle the needed "register" stuff)
It should be "fhs_compliance"
With 'nfsmountable 0' every is in /opt /opt/<vendor>/<scl>/root /opt/<vendor>/<scl>/root
With 'nfsmountable 1', you got a better tree
/opt/<vendor>/<scl>/root (read only) /etc/<vendor>/<scl>/ (configuration) /var/<vendor>/<scl>/ (data)
Remi
P.S. with scl-utils v2 you have a "rh_layout" option which gives the same tree, while nfsmountable gives something a bit different :(
-
Honza Horak -
Leon Fauster -
Remi Collet