It is true that Mininet is not a bare-metal provisioning and orchestration system. Certain orchestration systems such as Emulab are capable of bare-metal provisioning of physical servers, and you can use an L1 switch, a full mesh interconnect, a programmable patch panel, or OpenFlow switches to provision physical links.
However, Mininet is extremely appropriate for *modeling* a physical network. You can create a network in Mininet which resembles the physical network you intend to build or analyze; once your controller works with the Mininet network, it should be possible to try using it with your physical network - that is a very common workflow: prototype in Mininet, then test and deploy on hardware. Extending Mininet to provision physical resources is certainly possible; first, you would need your hardware resources and a provisioning mechanism for reserving and configuring physical resources such as bare metal servers and switches as well as physical ports and links; then you could create Host and Link classes for Mininet that would provision physical resources. > On Mar 13, 2015, at 10:56 PM, Izzat Alsmadi <alsm...@gmail.com> wrote: > > Mininet is used to define virtual hosts, how can we define physical hosts and > topology in SDN is Mininet seems not to be proper for that ? > > Thank you > Izzat Alsmadi > > > -- > Sent from Gmail Mobile > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
