NOTED: a framework to optimise network traffic via the analysis of data from File Transfer Services
Copyright:
© Copyright 2022 CERN. This software is distributed under the terms of
the GNU General Public Licence version 3 (GPL Version 3), copied verbatim
in the file "LICENCE.txt". In applying this licence, CERN does not waive
the privileges and immunities granted to it by virtue of its status as an
Intergovernmental Organization or submit itself to any jurisdiction.
PyPI Compilation steps:
# Steps to install NOTED by using a virtual environment
$ yum install python3-pip -y
$ yum install python3.8
$ pip3 install virtualenv
$ python3.8 -m venv venv-noted
$ . venv-noted/bin/activate
(venv-noted) $ python3 -m pip install noted-dev
# Write your configuration file, there is one example in noted/config/
(venv-noted) $ nano noted/src/noted/config/config.yaml
# Run NOTED
# (venv-noted) $ noted noted/src/noted/config/config.yaml [--verbosity debug/info/warning]
Docker Compilation steps:
# Download noted docker container
$ docker pull noted-docker
# Run docker container and keep it running in the background
$ docker run --detach --entrypoint /sbin/init --network="host" --privileged --name noted_cern_kit_controller noted-docker
# Copy config file into the container
$ docker cp src/noted/config/config-example.yaml noted_cern_kit_controller:/app/noted/config
# Run commands in the container from outside
$ docker exec noted_cern_kit_controller noted -h
$ docker exec noted_cern_kit_controller /app/src/noted/scripts/setup.sh mail
$ docker exec noted_cern_kit_controller noted config/config-example.yaml &
# Stop noted
$ docker exec noted_cern_kit_controller pkill noted
# Optional: login into the container (NOTE: type "exit" to logout)
$ docker exec -it noted_cern_kit_controller /bin/bash
Program description:
noted -h
usage: noted [-h] [-v VERBOSITY] config_file
NOTED: a framework to optimise network traffic via the analysis of data from File Transfer Services.
positional arguments:
config_file the name of the configuration file [config-example.yaml]
optional arguments:
-h, --help show this help message and exit
-v VERBOSITY, --verbosity VERBOSITY
defines the logging level [debug, info, warning]
Folder structure of NOTED:
- In config folder is available one or more config.yaml where the user defines the parameters to monitor the links.
- In logs folder: noted_email.txt: the last email notification that has been send to the responsible of the link to provide/cancel the dynamic circuit. transfer_broker.log: the log of NOTED [one log per execution]. sense.log: the log of sense-o, it is generated when NOTED calls the sense-o API [one log per execution].
- In query folder are available the queries to CERN Kibana [this folder is transparent to the user, don't use it].
- In transfers folder: transfer_broker_all_transfers.txt: file with all the transfers in the link even if the source/destination dynamic circuits are down. transfer_broker_src_rcsite.txt: file with the transfers of {src -> dst} when the source dynamic circuit is up, otherwise the transfers are not saved. transfer_broker_dst_rcsite.txt: file with the transfers of {dst -> src} when the destination dynamic circuit is up, otherwise the transfers are not saved.
noted
├── config
│ └── config.yaml
├── logs
│ ├── noted_email.txt
│ └── sense.log
│ └── transfer_broker.log
├── query
│ ├── query_monit_prod_fts_raw_queue_dst_rcsite
│ └── query_monit_prod_fts_raw_queue_src_rcsite
├── sense-o
│ │ ├── sense-cancel.sh
│ │ └── sense-provision.sh
└── transfers
├── transfer_broker_all_transfers.txt
├── transfer_broker_dst_rcsite.txt
└── transfer_broker_src_rcsite.txt
Structure of NOTED repository:
.
├── README.md
└── noted_transfer_broker
├── COPYRIGHT.txt
├── LICENCE.txt
├── Makefile
├── MANIFEST.in
├── README.md
├── setup.cfg
├── setup.py
└── src
├── noted
├── __init__.py
├── main.py
├── config
│ └── config-example.yaml
├── documentation
│ ├── noted_main_function_documentation.pdf
│ ├── noted_transfer_broker_class_documentation.pdf
│ ├── reduced_noted_main_function_documentation.pdf
│ └── reduced_noted_transfer_broker_class_documentation.pdf
├── html
│ ├── TransferBroker.html
│ └── main.html
├── logs
│ ├── noted_email.txt
│ ├── sense.log
│ ├── transfer_broker.log
├── modules
│ ├── __init__.py
│ ├── plot_transfers.py
│ └── transferbroker.py
├── params
│ └── params.ini
├── query
│ ├── query_monit_prod_fts_raw_queue_dst_rcsite
│ └── query_monit_prod_fts_raw_queue_src_rcsite
├── scripts
│ └── setup.sh
├── sense-o
│ ├── sense-cancel.sh
│ └── sense-provision.sh
└── transfers
├── transfer_broker_all_transfers.txt
├── transfer_broker_dst_rcsite.txt
└── transfer_broker_src_rcsite.txt
Metadata
Release files for noted-dev 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| noted-dev-1.2.tar.gz | 334.7 kB | Without provenance | Details for noted-dev-1.2.tar.gz |
Release files / noted-dev-1.2.tar.gz
| Download URL | noted-dev-1.2.tar.gz |
|---|---|
| Size | 334.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1468533c9f96c9a98023f1410c615ce66577f4f254bf8cd3f3ab265bb9b9ca22
|
|
BLAKE2b-256 checksum How to use checksums |
b47ffdb18c17787b23b9470d923f0855afb144029b13b3bc1ce6f093168dc8a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.5
|
Security for noted-dev 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.