On Fri, May 26, 2017 at 4:48 AM, Numan Siddique <nusid...@redhat.com> wrote:
>
>
> On Fri, May 26, 2017 at 3:30 AM, Andy Zhou <az...@ovn.org> wrote:
>>
>> On Thu, May 25, 2017 at 1:55 AM, <nusid...@redhat.com> wrote:
>> > From: Numan Siddique <nusid...@redhat.com>
>> >
>> > This patch adds the following functions
>> > - start_nb_ovsdb, stop_nb_ovsdb, restart_nb_ovsdb to start, stop and
>> > restart the OVN NB DB ovsdb-server independently.
>> > - start_sb_ovsdb, stop_sb_ovsdb, restart_sb_ovsdb to start, stop and
>> > restart the OVN SB DB ovsdb-server independently.
>> >
>> > These commands can be used to run ovsdb-server for each DB in a separate
>> > container.
>> >
>> > Signed-off-by: Numan Siddique <nusid...@redhat.com>
>>
>> LGTM.
>> Acked-by: Andy Zhou <az...@ovn.org>
>>
>> What's the intended use cases for running ovsdb-servers in separate
>> containers?
>> Where would northd run?
>
>
>
> The Openstack kolla project [1], it generates a separate container image for
> vswitchd and ovsdb-server.
> The goal is to support kolla images for OVN. I have submitted the patch here
> [2].
> Based on the present approach taken in kolla for openvswitch, this patch
> generates a separate container image for nb ovsdb-server, sb ovsdb-server,
> ovn-northd and ovn-controller. the nb ovsdb-server, sb ovsdb-server and
> ovn-northd is expected to be run in the same host (as separate containers).
>
> [1] - https://github.com/openstack/kolla/tree/master/docker/openvswitch
> [2] - https://review.openstack.org/#/c/459179/
>
Thanks, this is useful background information. I will push the patch
to master soon.
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
