On Mon, Aug 07, 2017 at 02:43:00PM -0400,
Sam Hague <
shague@...> wrote:
> Hanish,
>
> yes that is fine to do. The bigger issue is where should the agent live in
> ODL. If it makes sense to add to neutron northbound then they can pull the
> source in. Or it may make more sense to be another project. I included
> neutron-dev on this email so likely need to explain more about this agent
> to see if it fits in that project.
>
> Thanks, Sam
>
> On Mon, Aug 7, 2017 at 2:03 PM, hanish gogada <
hanishgogadahcu@...>
> wrote:
>
> > Thanks Anil. I have a general question, we have a generic usecase, to
> > implement this, we would like to propose an implementation which involves
> > running an agent on the compute node and want to upstream that code. Does
> > community approve this style of architecture or it is strictly no agent on
> > the compute node.
> >
> > Thanks
> > hanish gogada
> >
> > On Thu, Jul 27, 2017 at 1:35 PM, Anil Vishnoi <
vishnoianil@...>
> > wrote:
> >
> >> OVS and ovsdb don't really care as far as connection can be established
> >> between both of them. I never tried but as far as i know, you can enable
> >> the connection forwarding between the interfaces using NAT rule in iptables
> >> and allowing the traffic from external ip address using iptable forwarding
> >> rule. You might have to enable the ipv4 forwarding in your box.
> >>
> >> On Sun, Jul 23, 2017 at 11:32 PM, hanish gogada <
> >>
hanishgogadahcu@...> wrote:
> >>
> >>>
> >>> Thanks Anil, Can i use iptables to do the nat between the ovs and
> >>> ovsdb?, i am not sure but i feel the following things might cause some
> >>> problems.
> >>>
> >>> 1) If we have a fragment lost, is the vswitchd is resilient?
> >>> 2) would iptables cause significant performace hit.
> >>>
> >>> Did anyone tried iptables nat between ovsdb and ovs. Can you please help
> >>> me on this.
> >>>
> >>> Thanks
> >>> hanish gogada
> >>>
> >>> On Wed, Jul 19, 2017 at 3:29 AM, Anil Vishnoi <
vishnoianil@...>
> >>> wrote:
> >>>
> >>>> Hi Hanish,
> >>>>
> >>>> Is your OVS device is bound to any specific ip address? As far as your
> >>>> ovs manager is set to "ptcp:6640", it should accept connection coming
> >>>> through both the interfaces (data and management).
> >>>>
> >>>> On Tue, Jul 18, 2017 at 7:22 AM, hanish gogada <
> >>>>
hanishgogadahcu@...> wrote:
> >>>>
> >>>>> Hi
> >>>>>
> >>>>> Thanks for reading, I am work on integration of opendaylight and
> >>>>> openstack. Currently i have a usecase where ovsdb on compute nodes is
> >>>>> listening only on data network (for passive connection) and opendaylight
> >>>>> resides in the mgmt network. Every compute node also has mgmt interface.
> >>>>> Can we add iptable rules for traffic forwarding or is there any better way
> >>>>> of doing this. Any help is much appreciated.
> >>>>>
> >>>>> Thanks
> >>>>> hanish gogada
> >>>>>
> >>>>> ______________________________
_________________
> >>>>> ovsdb-dev mailing list
> >>>>>
ovsdb-dev@....org
> >>>>>
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Thanks
> >>>> Anil
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Thanks
> >> Anil
> >>
> >
> >
> > ______________________________
_________________
> > ovsdb-dev mailing list
> >
ovsdb-dev@....org
> >
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
> >
> >
