Re: Southbound switch

[Soheil Hassas Yeganeh]

We support OF1.0 and OF1.2 but southbound protocols are abstracted in the nom package. Have you encountered any problem connecting an OpenFlow switch to the controller?

All control applications (e.g., Kandoo, LearningSwitch...) are written based on nom not OpenFlow.The Kandoo example demonstrates how one can implement a local and a centralized application using Beehive. It uses the same northbound (I'm assuming that by northbound you mean the controller APIs) that any other control application uses.

-- Soheil

On Tuesday, September 1, 2015 at 5:35:21 PM UTC-4, aravind c wrote:

Hi,
I am looking at your Beehive and the beehive-netctl code. I am unable to understand from the description/implementation of the northbound controller using kandoo, what do you intend the southbound switch provider to be?
Especially in the context of the kandoo example.

Thanks,
Aravind

[aravind c]

Hi Soheil,
I see where my misunderstanding was. My understanding of the example application was the following -
1. Northbound Controller: I assumed that Kandoo is the distributed northbound controller (implemented as two layers- local controller on each node and a central controller) and that can collect flow statistics and issue control messages similar to Openstack
2. Southbound Switch Provider: Typically this could hardware that supports Openflow based switching or software switch provider such as Open Virtual Switch.

With this model, I wanted to find out what was the interface to the southbound switch provider in the example. In the openstack example this would be the Neutron plugin.

Can you please explain how nom detects that an Openflow switch has been created on a node?

Thanks,
Aravind

[Soheil Hassas Yeganeh]

Hi Arvind, 

With this model, I wanted to find out what was the interface to the southbound switch provider in the example. In the openstack example this would be the Neutron plugin.

OF out of the box, or any other protocol if you implement the southbound driver.

 

Can you please explain how nom detects that an Openflow switch has been created on a node?

OVS connects the OF port (say 6666) of one of the Beehive controllers in your control plane. For example, if you run one instance of the Beehive controller on every compute machine, you can just connect your OVS to the controller running on that end-host, and the rest should work automatically.

To write a Neutron plugin, you need to implement a Beehive application, maybe centralized, maybe sharded based on tenants. You can expose a REST interface on your Beehive application. Neutron can connect to any Beehive controller in the cluster to it's requests.

Hope that helps.

Best,

Soheil

[aravind c]

Soheil,
Thanks for the response. I see that of.addr can be used to configure the connection with the switch provider.

Thanks,
Aravind

[Soheil Hassas Yeganeh]

Great! please report issues on github if you encountered any bugs. 

Thanks,

Soheil

--
You received this message because you are subscribed to the Google Groups "beehive-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beehive-dev...@googlegroups.com.
To post to this group, send email to beehi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beehive-dev/b0b1ae49-a742-45f4-810e-d9bc7a2acb24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.