Date: Fri, 29 Mar 2024 00:07:48 +0000 (UTC) Message-ID: <1005172335.923.1711670868370@ip-10-30-146-46.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_922_553053141.1711670868367" ------=_Part_922_553053141.1711670868367 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you are already running Mininet in a VM or on a physical serv=
er, it is easy to use onos.py
to start up a complete=
emulated ONOS network in a single VM - includin=
g a ONOS cluster, modeled control network, and data network.
This simplifies development on a laptop, because you can run a
Additionally, onos.py
models the con=
trol network as well as the data network; you can easily chan=
ge the number of nodes in your ONOS cluster, as well as things like the del=
ay or bandwidth between nodes in the control network. It's even possible to=
change the control network topology as well as the data network topology. =
(We hope to make this more convenient and powerful in the future.)
onos.py
provides a single, unified consol=
e via the mininet-onos>
prompt,&nbs=
p;where you can enter both Mininet and ONOS commands - this can be very con=
venient! (We call this "One Console to Rule Them All.")
onos.py
also automatically handles port f=
orwarding, so you can easily connect to the GUI (or to karaf, or t=
o the controllers' OpenFlow ports) by connecting to ports on the VM.
Chances are you're already using Mininet, so it's = nice to be able to start an ONOS cluster using Mininet itself without insta= lling or configuring additional software.
onos.py
parametrizes both the co=
ntrol network (ONOS cluster) and the data network; so it's easy to iterate =
over multiple cluster sizes and network topologies.
We also hope that using onos.py
will make ONOS de=
velopment easier and more fun.