15. Layer root¶
15.1. Overview¶
This is the root
layer of the MFDATA module.
This layer mainly includes core libraries and utilities like :
layerapi2 library and utilities which manage the layer system
wrappers (
python2
,python3
,python
…)(and some other documented below)
The root
layer is loaded by default and does not depend on another layer. This
is the layer dependencies root.
16. Special focus on python wrappers¶
16.1. python2 wrapper¶
The python2
wrapper is available in ${MFEXT_HOME}/bin
. It executes
a python2 interpreter with following layers loaded :
python2_core@mfext
python2@mfext
(if installed)python2_misc@mfext
(if installed)python2@{current_module}
(if installed)
So, if you want to execute a python2 script without any question about currently loaded layers, this is the way to go.
For example:
#!/usr/bin/env python2
print "this code will be always executed in python2 environment"
print "(thanks to the above python2 shebang)"
or
python2 /path/to/a/python2/script.py
16.2. python3 wrapper¶
The python3
wrapper is available in ${MFEXT_HOME}/bin
. It executes
a python3 interpreter with following layers loaded :
python3_core@mfext
python3@mfext
(if installed)python3_misc@mfext
(if installed)python3@{current_module}
(if installed)
So, if you want to execute a python3 script without any question about currently loaded layers, this is the way to go.
For example:
#!/usr/bin/env python3
print("this code will be always executed in python3 environment")
print("(thanks to the above python3 shebang)")
or
python3 /path/to/a/python3/script.py
16.3. python wrapper¶
The python
wrapper is available in ${MFEXT_HOME}/bin
. It works exactly
as the two above wrappers. But the major python version is selected with
the METWORK_PYTHON_MODE
environment variable.
16.4. Metadata¶
16.4.1. Layer Home¶
/opt/metwork-mfserv-0.9
16.4.2. Label¶
root@mfserv
16.4.3. Package¶
metwork-mfserv-minimal
16.4.4. Dependencies¶
misc@mfext
#+python3_circus@mfext
openresty@mfext
#+rpm@mfext
16.5. Utilities¶
16.5.1. mfserv.stop¶
Stop the mfserv
module. This is nearly
the same thing than service metwork stop mfserv
(as root
user).
16.5.2. mfserv.status¶
Get the status of the mfserv
module. This is nearly
the same thing than service metwork status mfserv
(as root
user).
The (unix) return code will be 0
if the module is ok.
16.5.3. mfserv_wrapper¶
/bin/sh: mfserv_wrapper: command not found