Open Stack

Thank you. I will have a look.

Regards,
Niket

On Fri, Oct 5, 2018 at 4:15 PM Miguel Angel Ajo Pelayo <majopela at redhat.com>
wrote:

> have a look at dragonflow project, may be it's similar to what you're
> trying to accomplish
>
> On Fri, Oct 5, 2018, 1:56 PM Niket Agrawal <nickgrwl3 at gmail.com> wrote:
>
>> Hi,
>>
>> Thanks for the help. I am trying to run a custom Ryu app from the nova
>> compute node and have all the openvswitches connected to this new
>> controller. However, to be able to run this new app, I have to first stop
>> the existing neutron openvswitch agents in the same node as they run Ryu
>> app (integrated in Openstack) by default. Ryu in Openstack provides basic
>> functionalities like L2 switching but does not support launching a custom
>> app at the same time.
>> I'd like to have a single instance of Ryu controller control all the
>> openvswtich instances rather than having openvswitch agents in each node
>> managing the openvswitches separately. For this, I'll probably have to
>> migrate the existing functionality provided by Ryu app to this new app of
>> mine. Could you share some suggestions or are you aware of any previous
>> work done towards this, that I can read about?
>>
>> Regards,
>> Niket
>>
>> On Thu, Sep 27, 2018 at 9:21 AM Slawomir Kaplonski <skaplons at redhat.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Code of app is in
>>> https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_ryuapp.py
>>> and classes for specific bridge types are in
>>> https://github.com/openstack/neutron/tree/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native
>>>
>>> > Wiadomość napisana przez Niket Agrawal <nickgrwl3 at gmail.com> w dniu
>>> 27.09.2018, o godz. 00:08:
>>> >
>>> > Hi,
>>> >
>>> > Thanks for your reply. Is there a way to access the code that is
>>> running in the app to see what is the logic implemented in the app?
>>> >
>>> > Regards,
>>> > Niket
>>> >
>>> > On Wed, Sep 26, 2018 at 10:31 PM Slawomir Kaplonski <
>>> skaplons at redhat.com> wrote:
>>> > Hi,
>>> >
>>> > > Wiadomość napisana przez Niket Agrawal <nickgrwl3 at gmail.com> w dniu
>>> 26.09.2018, o godz. 18:11:
>>> > >
>>> > > Hello,
>>> > >
>>> > > I have a question regarding the Ryu integration in Openstack. By
>>> default, the openvswitch bridges (br-int, br-tun and br-ex) are registered
>>> to a controller running on 127.0.0.1 and port 6633. The output of ovs-vsctl
>>> get-manager is ptcp:127.0.0.1:6640. This is noticed on the nova compute
>>> node. However there is a different instance of the same Ryu controller
>>> running on the neutron gateway as well and the three openvswitch bridges
>>> (br-int, br-tun and br-ex) are registered to this instance of Ryu
>>> controller. If I stop neutron-openvswitch agent on the nova compute node,
>>> the bridges there are no longer connected to the controller, but the
>>> bridges in the neutron gateway continue to remain connected to the
>>> controller. Only when I stop the neutron openvswitch agent in the neutron
>>> gateway as well, the bridges there get disconnected.
>>> > >
>>> > > I'm unable to find where in the Openstack code I can access this
>>> implementation, because I intend to make a few tweaks to this architecture
>>> which is present currently. Also, I'd like to know which app is the Ryu SDN
>>> controller running by default at the moment. I feel the information in the
>>> code can help me find it too.
>>> >
>>> > Ryu app is started by neutron-openvswitch-agent in:
>>> https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/main.py#L34
>>> > Is it what You are looking for?
>>> >
>>> > >
>>> > > Regards,
>>> > > Niket
>>> > >
>>> __________________________________________________________________________
>>> > > OpenStack Development Mailing List (not for usage questions)
>>> > > Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>> > —
>>> > Slawek Kaplonski
>>> > Senior software engineer
>>> > Red Hat
>>> >
>>> >
>>> >
>>> __________________________________________________________________________
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>> __________________________________________________________________________
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>> —
>>> Slawek Kaplonski
>>> Senior software engineer
>>> Red Hat
>>>
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181005/9769b4b7/attachment.html>