[affinity-dev] Sample Bundles in the Virtualization Edition
|
Ed Warnicke (eaw) <eaw@...>
Hideyuki,
toggle quoted message
Show quoted text
My one concern on removing simple forwarding is to make sure that we have a virtualization edition that, when someone runs run.sh, *does* something useful (ie, pinball works) without requiring much if any configuration… thoughts? Ed On Nov 5, 2013, at 3:12 AM, Hideyuki Tai <h-tai@...> wrote:
Hi Virtualization Edition people, |
|
|
|
Hideyuki Tai <h-tai@...>
Hi Ed,
toggle quoted message
Show quoted text
When someone runs run.sh and send some configuration to Affinity, OpenDOVE, or VTN, the Virtualization Edition does something useful. It requires some configuration, but it does something great related to virtualization. I think it's the same with simpleforwarding bundle to require configuration. Simpleforwarding bundle requires subnet gateway configuration to forward packets. I mean that even the Virtualization Edition include simpleforwarding, we need some configuration anyway. My one concern on simpleforwarding bundle is that simpleforwarding sets flow entries automatically after detecting host information. It means that simpleforwarding ignore virtual network configuration on Affinity and VTN, and may install flow entries which interfere with Affinity and VTN. Therefore, I would like to remove simpleforwarding bundle from the Virtualization Edition. Furthermore, I think simpleforwarding bundle doesn't do virtualization jobs, but just simulates a traditional IP network. So it is a little weird to me that the Virtualization Edition include simpleforwarding bundle. To be honest, It's not clear to me that other project in the Virtualization Edtion needs simpleforwarding bundle, or simpleforwarding bundle interfere with other bundles too. So I would like to hear from other project people. Regards, Hideyuki Tai -----Original Message----- |
|
|
|
Luis Gomez <luis.gomez@...>
Hi all,
toggle quoted message
Show quoted text
I have a more general question here (I cc controller dev): maybe I am missing something but why the simple forwarding application is always on in the controller (i.e. creating flows for all known hosts)? I see it is a very good use case but in my opinion it should have a turn on/off button, same as subnet gateway feature. It is not only for VTN, I am thinking on any app or consumer of the controller that may be interested in knowing the attached hosts without automatically creating flows for them. Thanks/Luis -----Original Message-----
From: affinity-dev-bounces@... [mailto:affinity-dev-bounces@...] On Behalf Of Hideyuki Tai Sent: Tuesday, November 05, 2013 6:41 PM To: Ed Warnicke (eaw) Cc: <affinity-dev@...>; <defense4all-dev@...>; ovsdb-dev@...; opendove-dev@...; vtn-dev@... Subject: Re: [affinity-dev] Sample Bundles in the Virtualization Edition Hi Ed, When someone runs run.sh and send some configuration to Affinity, OpenDOVE, or VTN, the Virtualization Edition does something useful. It requires some configuration, but it does something great related to virtualization. I think it's the same with simpleforwarding bundle to require configuration. Simpleforwarding bundle requires subnet gateway configuration to forward packets. I mean that even the Virtualization Edition include simpleforwarding, we need some configuration anyway. My one concern on simpleforwarding bundle is that simpleforwarding sets flow entries automatically after detecting host information. It means that simpleforwarding ignore virtual network configuration on Affinity and VTN, and may install flow entries which interfere with Affinity and VTN. Therefore, I would like to remove simpleforwarding bundle from the Virtualization Edition. Furthermore, I think simpleforwarding bundle doesn't do virtualization jobs, but just simulates a traditional IP network. So it is a little weird to me that the Virtualization Edition include simpleforwarding bundle. To be honest, It's not clear to me that other project in the Virtualization Edtion needs simpleforwarding bundle, or simpleforwarding bundle interfere with other bundles too. So I would like to hear from other project people. Regards, Hideyuki Tai -----Original Message-----_______________________________________________ affinity-dev mailing list affinity-dev@... https://lists.opendaylight.org/mailman/listinfo/affinity-dev |
|
|
|
Colin Dixon <ckd@...>
For what it's worth, I'm in the process of removing the requirements to configure SimpleFowarding so that it acts as a normal L2 switch across all the ports in the system when there's no configuration. > -----Original Message-----
> From: Ed Warnicke (eaw) [mailto:eaw@...] > Sent: Wednesday, November 06, 2013 12:19 AM > To: Tai, Hideyuki > Cc: <affinity-dev@...>; opendove-dev@... > ; ovsdb-dev@...; > <defense4all-dev@...>; vtn-dev@... > Subject: Re: [affinity-dev] Sample Bundles in the Virtualization Edition > > Hideyuki, > My one concern on removing simple forwarding is to make sure that we have > a virtualization edition that, when someone runs run.sh, *does* > something useful > (ie, pinball works) without requiring much if any configuration… thoughts? > > Ed > On Nov 5, 2013, at 3:12 AM, Hideyuki Tai <h-tai@...> wrote: > > Hi Virtualization Edition people, > > Do any projects in the Virtualization Edition need sample bundles? > - org.opendaylight.controller.samples.loadbalancer > - org.opendaylight.controller.samples.sample-toaster > - org.opendaylight.controller.samples.simpleforwarding > > Is it ok to remove all sample bundles from the Virtualization Edition? > > These bundles are just *sample* bundles, > and already included in the Base Edition. > > Furthermore, VTN Manager does not correctly work, > if samples.loadbalancer or samples.simpleforwarding is running. > These bundles set flow entries to switches, > so it might break flow entries set by VTN Manager. > > Therefore, if all bundles delivered by projects in the Virtualization Edition > does not need these bundles, > I would like to remove sample bundles from the Virtualization Edition. > > Thanks, > Hideyuki Tai > > _______________________________________________ > affinity-dev mailing list > affinity-dev@... > https://lists.opendaylight.org/mailman/listinfo/affinity-dev |
|
|