Date: Fri, 29 Mar 2024 13:03:13 +0000 (UTC) Message-ID: <1787266867.1117.1711717393217@ip-10-30-146-46.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1116_576832960.1711717393213" ------=_Part_1116_576832960.1711717393213 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
ONOS is an extensible and programmable network control platform = that supports the development of arbitrary software packages. The switch fr= om fixed-function networking platforms to programmable SDN platforms is ana= logous to the switch from fixed-function "feature" phones to smartphones, a= nd ONOS is designed to facilitate an expansive ecosystem of network applica= tions that are developed independently from the core ONOS system, much as u= ser applications are developed separately from the kernel in desktop and se= rver systems.
One way to get started with developing ONOS applications is to try modif= ying the existing O= NOS Sample Applications. This is a good way to get your feet wet by exp= erimenting with changes to existing functionality, and may be easier than c= reating an entirely new application from scratch.
If you wish to create an application from scratch, or wish to create a s= mall program with minimal code and functionality, you can start with a "tem= plate application" which uses a Maven archetype to create skeleton code whi= ch doesn't do much beyond setting up the basic infrastructure that can be c= ompiled and installed into ONOS, and can interact with the ONOS CLI and GUI= . Any additional functionality can be added as desired until it does what y= ou want.
Creating a template application is described in the Template Application Tutorial.