[vtn-dev] Fwd: [affinity-dev] Sample Bundles in the Virtualization Edition
Colin Dixon <ckd@...>
toggle quoted message Show quoted text
I agree 100%.
> > -----Original Message-----
> > From: Ed Warnicke (eaw) [mailto:eaw@...]
> > Sent: Wednesday, November 06, 2013 12:19 AM
> > To: Tai, Hideyuki
> > Cc: <affinity-dev@...>; opendove-
> > ; 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
Luis Gomez <luis.gomez@...>
I support the idea of having apps and features doing something useful with very few (b) or no configuration (a). Only concern is for those that do not require configuration (a), at least make sure they have very low or none impact in the controller behavior or switches configuration. A good example is Topology Manager that without any configuration reads information from the switches and creates a topology with no impact in controller/switches. On the other side we have Simple Forwarding app that writes flows in the switches whenever the controller discovers a host, I think this is quite an impact for an app that runs out of the box. With this I do not mean to remove this feature or other features like this but move them to (b) -> enable them with simple configuration, what you are actually proposing.
On the other hand, I take the chance to encourage the projects to come up with a simple (first contact) demo case for their contributions and publish it in the wiki, same thing OVSDB folks have done today at TSC call:
From: vtn-dev-bounces@... [mailto:vtn-dev-bounces@...] On Behalf Of Colin Dixon
Sent: Wednesday, November 06, 2013 2:45 PM
To: <affinity-dev@...>; <opendove-dev@...>; <ovsdb-dev@...>; <defense4all-dev@...>; <vtn-dev@...>
Subject: Re: [vtn-dev] Fwd: [affinity-dev] Sample Bundles in the Virtualization Edition
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.
|1 - 2 of 2|