1 **************************
2 Who should use this guide?
3 **************************
5 OpenDaylight is for users considering open options in network programming. This
6 guide provides information for the following types of users:
8 #. Those new to OpenDaylight who want to install it and select the features they
9 need to run their network environment using only the command line and GUI.
13 #. Network administrators and engineers.
15 #. Network engineers and network application developers who want to use
16 OpenDaylight’s REST APIs to manage their network programmatically.
17 #. Network engineers and network application developers who want to write their
18 own OpenDaylight services and plugins for greater functionality. This group
19 of users needs a significant level of expertise in the following areas, which
20 is beyond the scope of this document:
22 a. The YANG modeling language
23 #. The Model-Driven Service Abstraction Layer (MD-SAL)
25 #. Management of the shared data store
26 #. How to handle notifications and/or Remote Procedure Calls (RPCs)
28 #. Developers who would like to join the OpenDaylight community and contribute
29 code upstream. People in this group design offerings such as
30 applications/services, protocol implementations, and so on, to increase
31 OpenDaylight functionality for the benefit of all end-users.
33 .. note:: If you develop code to build new functionality for OpenDaylight and
34 push it upstream (not required), it can become part of the OpenDaylight
35 release. Users can then install the features to implement the solution you’ve