Contributing

Environment

eNMS uses:

• Black for python code formatting.
• Flake8 to make sure that the python code is PEP8-compliant.
• Prettier for javascript code formatting.
• Eslint to make sure the javascript code is compliant with google standards for javascript.

There is a dedicated requirements_dev.txt file to install these python libraries:

pip install -r requirements_dev.txt

Pull Requests

Before opening a pull request with changes, one should make sure that:

1. Candidate Python code is:

   • Black compliant

     Black is a code formatting enforcement tool. Once installed (see their repository for details), compliance can be verified with the following command:

     black --check --verbose

   • PEP8 (flake8) compliant

     flake8 --config build/linting/.flake8

2. Candidate Javascript code is:

   • Prettier compliant

     npm run prettier

   • ESLint compliant

     npm run lint

Virtual Lab

• Install containerlab: `curl -sL https://containerlab.dev/setup | sudo -E bash -s "all"``
• Download Arista cEOS image, then import it (docker import cEOS64-lab-4.32.0F.tar.xz ceos:4.32.0F)
• Check that the image exists: docker images | grep ceos
• Add the yaml file lab.clab.yaml and the config files in eNMS / files / lab to lab folder
• Deploy with sudo containerlab deploy (check: sudo containerlab inspect)
• Destroy the lab: sudo containerlab destroy

Documentation

Concerning documentation updates, one can build a local version of the docs like so:

mkdocs build

If mkdocs is already initialized in one's environment, the following command will launch a local documentation server:

mkdocs serve -a 0.0.0.0:8000

This server will automatically update and refresh whenever any filesystem changes are made in the enms/docs folder or mkdocs.yml