11–20 of 52 posts
I am going to guess large high throughput switches and some degree of software defined networks that knock putting your printers on one C-network and your servers on another into a cock hat
Apart from raw power, is there some way I can reconfigure my network without moving a cable that I previously could not?
(It's late, so just to be sure, I'm not trolling)
The hardware compatibility list is pretty slim at the moment: http://www.openswitch.net/documents/user/hardware-compatibil...
How is this any better/different than Open vSwitch? http://openvswitch.org/
openvswitch is simply an interface which provides the ability to programmatically configure your network devices. You could run it on OpenSwitch as the program/module which talks with a controller.
This seems like a good, if belated, move on HPs part. Ethernet switches have become trivial to build with off the shelf parts. If you open up the software then you can focus on things like build quality and reliability.
As I stopped knowing anything about datacenters around 2001, can anyone tell me what a network operating system is? I am going to guess large high throughput switches and some degree of software defined networks that knock putting your printers on one C-network and your servers on another into a cock hat Apart from raw power, is there some way I can reconfigure my network without moving a cable that I previously coul…
As I stopped knowing anything about datacenters around 2001, can anyone tell me what a network operating system is? I am going to guess large high throughput switches and some degree of software defined networks that knock putting your printers on one C-network and your servers on another into a cock hat Apart from raw power, is there some way I can reconfigure my network without moving a cable that I previously coul…
One area where a lot of smarts are needed needed, for example, is making sure that you're intelligently routing encrypted packets to the right machines without reverting to a broadcast to every router, switch, and machine in the DC.
I've also heard a lot about people running brand new untested protocols (like TCP replacements) right alongside traditional protocols through SDN.
I'm probably going to do a much worse job of explaining things than the guys who presented at the Open Networking Summit [1]. I highly recommend giving the keynotes a listen.
[1] https://www.youtube.com/user/OpenNetSummit
Edit: I do think this relates to SDN more than a traditional router/switch OS, based on the comments about "traditional and programmatic, declarative control plane." Either way, though, the link above is definitely good stuff.
How is this any better/different than Open vSwitch? http://openvswitch.org/
Essentially, one of the aims of OpenSwitch is to build a cohesive API around a wide set of Linux networking tools and daemons, and build a broad community to make it happen.
Earlier quoted context omitted.
openvswitch is simply an interface which provides the ability to programmatically configure your network devices. You could run it on OpenSwitch as the program/module which talks with a controller.
More so, there's already a white box switch that runs it, Pica8 switch is basically a Debian distro with OVS and proprietary drivers.
https://www.sdxcentral.com/articles/news/pica8s-white-box-os...
This seems like a good, if belated, move on HPs part. Ethernet switches have become trivial to build with off the shelf parts. If you open up the software then you can focus on things like build quality and reliability.
It sounds too good to me. How will they make money in the Ethernet switching sector?
This seems like a good, if belated, move on HPs part. Ethernet switches have become trivial to build with off the shelf parts. If you open up the software then you can focus on things like build quality and reliability.
It sounds too good to me. How will they make money in the Ethernet switching sector?