Documentation
This presentation given at the OpenDaylight Fluorine Developer Design Forum in March 2018 at ONS in LA gives a good overview of the project
(previously also this older presentation given at the OpenDaylight Oxygen Developer Forum in October 2017).
The Getting Started for Users
Getting Started for Developers
Requirements
Release Planning
Release Notesguide has further descriptions of the available features.
Planned Features (WIP)
Metrics enhancements
Future possible implementations
- direct OpenStack Ceilometer integration - looking for parties interested in contributing this!
- ..., Atlas, Datadog, Ganglia, Graphite, Influx, New Relic, SignalFx, StatsD, Wavefront, ...; via http://micrometer.io
Future tighter integrations with exsting ODL technical infrastructure
TODO (contributions welcome!):
- infrautils.jobcoordinator more extended metrics (it already has the basic ones), e.g. for labels per job key, and Timers for job execution, etc.
- monitored Executor ThreadPool related stuff
- Karaf Jetty server metrics
- ...
Logging with ExecutionOrigin ID
https://git.opendaylight.org/gerrit/#/q/topic:mdc
web API with OSGi and standalone implementation for (non-IT) e2e component tests and simple distribution
see https://git.opendaylight.org/gerrit/#/q/topic:simple-dist_web+(status:open+OR+status:merged)
Future Ideas
Tracing
Linux Foundation (LF) Cloud Native Computing Foundation (CNCF) Open Tracing for OpenDaylight and its north- and southbound!
Removed Features
Counters infrastructure
Create, update and output counters is a basic tool for debugging and generating statistics in any system. We've developed a counter infrastructure integrated into ODL which has already been successfully used with multiple products, and more recently in debugging and fixing the OpenFlow plugin/Java and LACP modules.
See Getting started with Counters and Presentation Slides from the ODL 2016 Developer Design Forum: [1] for more information about Counters.
Async infrastructure
Remove in https://git.opendaylight.org/gerrit/#/c/53215/ : The decision to split a service into one or more threads with asynchronous interactions between them is frequently dependent on constraints learned late in the development and even the deployment cycle. In order to allow flexibility in making these decisions we've developed an infrastructure which is configuration driven allowing agnostic code to be written under generic constrains which can then later be customized according to the required constraints.
Appendix
Helpful Links
Release Plans
The infrautils project does not publish forward looking release plans. This Wiki page does however have a "Completed & Available" and a "Planned Features (WIP)" section above. So whatever is in is in by cut off and makes it, what's not gets deferred to the next release. Parties interested in "Planned Features (WIP)" are welcome to contribute!
Aluminium
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Magnesium
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|