Data & Analytics Framework (DAF)
Failed to load latest commit information.
bin Added build scripts Oct 25, 2017
catalog_manager update doc and catalog manager deps Sep 7, 2018
ckan minor stuff Aug 8, 2017
common Updated common and storage version Sep 25, 2018
dataset-manager Feature/add metrics (#180) Dec 20, 2017
docs-dev moved md into daf-operational docs Sep 7, 2018
docs-ita/piano-triennale [PM-19] Jul 31, 2017
docs-usr Aggiornamento documentazione Jul 7, 2017
docs Create Mar 5, 2018
entity_manager 1. updated all the versions to be 1.0.0 Nov 24, 2017
faq now ingestion and storage do not run as root Dec 20, 2017
grafana/kubernetes added grafana Oct 19, 2017
haproxy Merge branch 'master' into 1.0-alpha Nov 7, 2017
infrastructure moved grafana dashboards into daf-operational Sep 7, 2018
ingestion_manager removed owner arg fom sftp call in security manager since method acce… Jan 29, 2018
iot_ingestion_manager Update Mar 12, 2018
iot_manager Reworks Storage Manager (#329) Jul 19, 2018
livy Minor fix to livy yaml configuration Feb 1, 2018
microsrv_plain Merge branch 'master' into 1.0-alpha Nov 7, 2017
nexus/kubernetes Upgraded Nexus version Apr 20, 2018
opentsdb merging classes from storage_manager_extension Nov 24, 2017
security_manager Bug sftp connection time increased Jul 31, 2018
storage_manager Updated storage_manager version Sep 25, 2018
superset made the superset state persistent on the shared file system Aug 2, 2017
versions Reworks Storage Manager (#329) Jul 19, 2018
.gitignore Fixed build nexus Aug 9, 2018
.gitmodules minor stuff Aug 8, 2017
AUTHORS Revert "Revert "Change license to BSD. Before merging, please evaluat… May 21, 2018
LICENSE Revert "Revert "Change license to BSD. Before merging, please evaluat… May 21, 2018 Link to the actual documentation in english Feb 5, 2018

Data & Analytics Framework (DAF)

Welcome to the project homepage.

Infrastructure setup

To see how the DAF is setup please take a look at the setup documentation.

Development Guidelines

In general, we prefer to keep all the project with Version 1.0.0-SNAPSHOT. This requires that could need to publish to your local nexus ivy repository some local projects. This part is experimental and can change in the future.


We use submodules for Kong and other projects. To init the repo submodule run:

$ git submodule init
$ git submodule update

Internal Team

Each time you start working on the DAF the desiderata is that:

  • For a new feature you have to create a branch with a meaningful name. The desiderata is something like feature_some_meaningful_name. It would be useful also to have a branch related to the feature
  • For a bug-fix you have to create a branch named bug_number_of_the_bug

Whenever the work on the branch is finished it is need to:

  1. squash all your commit in one commit
  2. create a pull request for master and assign it to another one in the team.

If you don't have practice with branching, squashing and merging you can use git-extras as helper. Git extras has commands like: git feature to create a feature, git squash to squash your commits.

The aim of this is to share your work.

The releases will be tagged and there will be also a branch.

External TEAM

Please fork the project and then do a pull request at the end. Pull request are super welcome !!! :)

Dev Doc

  1. metrics setup
  2. java configurations setup