Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

If you are just building the controller project only, then this doesn't come with OpenFlow, L2Switch, Dlux. This project bring only the core functions of ODL such as the clusting, MD-SAL/AD-SAL, and some NSF

There a few ways you can do things.

  1. Just download the latest released controller from OpenDaylight controller page This is good if you just want to get ODL up and running to play with the API's on a released
  2. Download the latest pre-build ODL releases from maser branch [Pre-built master branch release] (https://wiki.opendaylight.org/view/CrossProject:IntegrationGroup:ControllerArtifacts#LithiumLatestDistribution_Artifacts) Same as the above just using the latest code(new features/bugs) that maybe not in an official release
  3. Use a distribution built by a project (OpenFlow, L2Switch, Dlux, Integration) Useful if you wish to work on the code on a project only downsize that distribution may not have the need project in it IE OpenFlow won't have L2Switch in it you can build from Integration project which will build the same distribution you see in the release.

If you are just building the controller project only, then this doesn't come with OpenFlow, L2Switch, Dlux. This project bring only the core functions of ODL such as the clusting, MD-SAL/AD-SAL, and some NSF

There a few ways you can do things.

  1. Just download the latest released controller from OpenDaylight controller page This is good if you just want to get ODL up and running to play with the API's on a released
  2. Download the latest pre-build ODL releases from maser branch [Pre-built master branch release] (https://wiki.opendaylight.org/view/CrossProject:IntegrationGroup:ControllerArtifacts#LithiumLatestDistribution_Artifacts) Same as the above just using the latest code(new features/bugs) that maybe not in an official release
  3. Use a distribution built by a project (OpenFlow, L2Switch, Dlux, Integration) Useful if you wish to work on the code on a project only downsize that distribution may not have the need project in it IE OpenFlow won't have L2Switch in it you can build from Integration project which will build the same distribution you see in the release.

1 Example.

If you wish to make changes to DLUX, OpenFlow and Controller project then you would

1. Get the repo of each project 2. Edit your code changes 3. Build each project local in order of the dependency Dependency Diagram 4. Then build the integration project last (it has dependency of all other projects)

What this does is once you build a project, the needed JAR's are stored in your local Maven repo (on Mac and Linux ~/.m2/repository) When you build the integration project it will check your local Maven repo if the JAR isn't found then it download the need JAR from the OpenDaylight nexus. Hopefully this explains it.

If you are just building the controller project only, then this doesn't come with OpenFlow, L2Switch, Dlux. This project bring only the core functions of ODL such as the clusting, MD-SAL/AD-SAL, and some NSF

There a few ways you can do things.

    • Just download the latest released released controller from OpenDaylight controller OpenDaylight controller page

      This is good if you just want to get ODL up and running to play with the API's on a released

    • Download the latest pre-build ODL ODL releases from maser branch [Pre-built [Pre-built master branch release] release] (https://wiki.opendaylight.org/view/CrossProject:IntegrationGroup:ControllerArtifacts#LithiumLatestDistribution_Artifacts) Distribution_Artifacts) Same as the above just using the the latest code(new features/bugs) that that maybe not in an official release

    • Use a distribution built by a project (OpenFlow, L2Switch, Dlux, Integration) Useful if you wish to work on the code on a project only downsize that distribution may not have the need project in it IE OpenFlow won't have L2Switch in it you can build from Integration project which will build the same distribution you see in the release.

1

Example.

If you wish to make changes to DLUX, OpenFlow and Controller project then you would

1. Get the repo of each project 2. Edit your code changes 3. Build each project local in order of the dependency Dependency Diagram 4. Then build the integration project last (it has dependency of all other projects)

What this does is once you build a project, the needed JAR's are stored in your local Maven repo (on Mac and Linux ~/.m2/repository) When you build the integration project it will check your local Maven repo if the JAR isn't found then it download the need JAR from the OpenDaylight nexus. Hopefully this explains it.

If you are just building the controller project only, then this doesn't come with OpenFlow, L2Switch, Dlux. This project bring only the core functions of ODL such as the clusting, MD-SAL/AD-SAL, and some NSF

There a few ways you can do things.

  • Just download the latest released controller from OpenDaylight controller page

    This is good if you just want to get ODL up and running to play with the API's on a released

  • Download the latest pre-build ODL releases from maser branch [Pre-built master branch release] (https://wiki.opendaylight.org/view/CrossProject:IntegrationGroup:ControllerArtifacts#LithiumLatestDistribution_Artifacts) Same as the above just using the latest code(new features/bugs) that maybe not in an official release

  • Use a distribution built by a project (OpenFlow, L2Switch, Dlux, Integration) Useful if you wish to work on the code on a project only downsize that distribution may not have the need project in it IE OpenFlow won't have L2Switch in it you can build from Integration project which will build the same distribution you see in the release.

Example.

If you wish to make changes to DLUX, OpenFlow and Controller project then you would

1. Get the repo of each project project 2. Edit your the code where you want to make the changes 3. Build each project local in order of the dependency Dependency Diagram 4. Then build the integration project last (it has dependency of all other projects)

What this does is once you build a project, the needed JAR's are stored in your local Maven repo (on Mac and Linux ~/.m2/repository) When you build the integration project it will check your local Maven repo if the JAR isn't found then it download the need JAR from the OpenDaylight nexus. Hopefully this explains it.