Package: execo
Execo offers a Python API for asynchronous control of local or remote,
standalone or parallel, unix processes. It is especially well suited
for quickly and easily scripting workflows of parallel/distributed
operations on local or remote hosts: automate a scientific workflow,
conduct computer science experiments, perform automated tests,
etc. The core python package isexeco. Theexeco_g5kpackage
provides a set of tools and extensions for theGrid5000testbed. Theexeco_enginepackage
provides tools to ease the development of computer sciences
experiments.LicenseExeco is copyright INRIA Rhone-Alpes, Service Experimentation et
Developpement.Execo is free software: you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation, either version 3 of the License, or (at your
option) any later version.Execo is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
for more details.You should have received a copy of the GNU General Public License
along with Execo.  If not, see <http://www.gnu.org/licenses/>Versionslatest stable version: v2.7 (2023-01-25)Installation instructionsuseful linkshome page:https://gitlab.inria.fr/mimbert/execodocumentation pages:https://mimbert.gitlabpages.inria.fr/execo/package download:https://gitlab.inria.fr/mimbert/execo/-/packagesmailing lists:https://sympa.inria.fr/sympa/info/execo-userscode repository:git@gitlab.inria.fr:mimbert/execo.git /https://gitlab.inria.fr/mimbert/execo.gitplatformsworks on linux (primary development platform), darwin (macosx)should work on bsd (not tested)don’t know on windows or cygwin (not tested)prerequisitesexeco installation absolutely requirespython2.6 / 2.7 or
>=3.2.execo_g5kneedspython-requests. Optionnal packages are
(debian package names, in order of decreasing importance):under python 2.6,python-argparseis needed forexeco_engine.engine.Enginepython-keyringfor allowing storage ofexeco_g5k.api_utilsapi
password in the desktop environment keyring (allowing asking it only
once).python-psycopg2for optimized interface to Grid5000 OAR planning.sphinx-doc,graphvizfor building the documentation (usually
not needed for regular users).python-matplotlib(>= 1.2.0) for some graphical representations.python-networkx,python-pygraphviz,graphvizfor moduleexeco_g5k.topology. Later versions of networkx (at least v1.11)
also requirepython-pydotplus, but this dependency is not
explicitely listed in the debian package (as of July 2017).At runtime, connecting to remote hosts requiresssh,scpor
similar connection tools, and optionnalytaktuk(probably >=
3.6.http://taktuk.gforge.inria.fr/).execo.action.ChainPutrequires
bourne shell andnetcaton remote hosts.installationTo install execo from a source package (.tar.gz) or from the git
tree:$ python setup.py install [--user]to build documentation (if sphinx is available):$ python setup.py build_docto install documentation (if sphinx is available):$ python setup.py install_docIt is possible to install execo automatically withpiporeasy_install:$ pip install --user execoor:$ easy_install --user execoIt is possible to generate a debian package. For example, in the execo
package toplevel dir, run (the .deb will be generated in ../):$ dpkg-buildpackage -us -ucUsageSee html documentation for module execo and execo_g5k athttps://mimbert.gitlabpages.inria.fr/execo/BugsExeco is regularly used to perform advanced experiments and
administration / monitoring tasks, in and outside Grid5000. We
actively fix bugs. Bugs should be reported tohttp://bugzilla.inria.fr(product: execo)PublicationsMatthieu Imbert, Laurent Pouilloux, Jonathan Rouzaud-Cornabas, Adrien
Lèbre, Takahiro Hirofuchi “Using the EXECO toolbox to perform
automatic and reproducible cloud experiments”1st International Workshop on
UsiNg and building ClOud Testbeds UNICO, collocated with IEEE CloudCom
20132013How to contributestart contributing by sending clean patches or report bugs.stay consistent with the coding and naming stylecode must be compatible with python 2.6, 2.7 and 3.2+ (seehttps://mimbert.gitlabpages.inria.fr/execo/python2-python3.html)use the core systems provided (eg. the configuration system, the tty
coloring system, the logger, etc.) instead of developing your own.provide documented code (internal documentation as well as user
documentation where needed)ask a core developer before adding a dependency or dealing with
threads, signals (particularly: creating threads)indent with spaces, not tabs. one level of indentation is four
spaces (if needed: usereindent.py-rnv.in execo top
directory)recommended commit messages format:[<module_name>] <category>: commit message.<module_name> can be execo, execo_g5k, execo_engine. Omit if
commit is not specific to a module.<category> is free form but should indicate which part(s) of the
module the commit affects. Omit if a commit is not specific to a
module part.