Hi Shivaram: Thanks for comments. Can you explain what is the bottleneck? Also for addressing performance related issues that you suggested, I would say if you can submit PR in ovs repo mentioning to use additional docker options for startup for better performance, it would be helpful. I did not get a chance to try out additional options apart from the base ones as it just does its job at-least while running ovs/ovn in pre-prod/testing env. Didn't get as chance to scale test it.
On Fri, Nov 8, 2019 at 3:35 PM Shivaram Mysore <[email protected]> wrote: > The point about kernel module is correct- no need to include it in docket > image. It will not work. > > /Shivaram > ::Sent from my mobile device:: > > On Nov 8, 2019, at 5:42 PM, aginwala <[email protected]> wrote: > > > openvswitch.ko ships default with newer kernel but if we want to use say > stt, we need to build it with respective kernel for host on which we will > run. Hence, to skip host level installation , we pack the modules in > container. > > On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty <[email protected]> wrote: > >> >> >> On Fri, 8 Nov 2019 at 14:18, aginwala <[email protected]> wrote: >> >>> Hi all: >>> >>> >>> I have pushed two images to public openvswitch org on docker.io for ovs >>> and ovn; >>> OVS for ubuntu with 4.15 kernel: >>> *openvswitch/ovs:2.12.0_debian_4.15.0-66-generic* >>> >> >> Why is the kernel important here? Is the OVS kernel module being packed? >> >> >>> run as : docker run -itd --net=host --name=ovsdb-server >>> openvswitch/ovs:2.12.0_debian_4.15.0-66-generic ovsdb-server >>> docker run -itd --net=host --name=ovs-vswitchd >>> --volumes-from=ovsdb-server --privileged >>> openvswitch/ovs:2.12.0_debian_4.15.0-66-generic ovs-vswitchd >>> >>> OVN debian docker image: *openvswitch/ovn:2.12_e60f2f2_debian_master* >>> as we don't have a branch cut out for ovn yet. (Hence, tagged it with last >>> commit on master) >>> Follow steps as per: >>> https://github.com/ovn-org/ovn/blob/master/Documentation/intro/install/general.rst >>> >>> >>> Thanks Guru for sorting out the access/cleanups for openvswitch org on >>> docker.io. >>> >>> We can plan to align this docker push for each stable release ahead. >>> >>> >>> >>> On Fri, Nov 8, 2019 at 10:17 AM aginwala <[email protected]> wrote: >>> >>>> Thanks Guru: >>>> >>>> Sounds good. Can you please grant user aginwala as admin? I can create >>>> two repos ovs and ovn under openvswitch org and can push new stable release >>>> versions there. >>>> >>>> On Fri, Nov 8, 2019 at 10:04 AM Guru Shetty <[email protected]> wrote: >>>> >>>>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty <[email protected]> wrote: >>>>> >>>>>> I had created a openvswitch repo in docker as a placeholder. Happy to >>>>>> provide it to whoever the admin is. >>>>>> >>>>> >>>>> i.e. You can use the keyword "openvswitch". For e.g., right now, it >>>>> has one stale image. >>>>> >>>>> docker run -d --net=none openvswitch/ipam:v2.4.90 /bin/sh -c "while >>>>> true; do echo hello world; sleep 1; done" >>>>> >>>>> So if we want the name "openvswitch", this is one option. If we prefer >>>>> ovs/ovn or other keywords, then the admin can create a new one. >>>>> >>>>> >>>>>> >>>>>> On Thu, 7 Nov 2019 at 13:15, aginwala <[email protected]> wrote: >>>>>> >>>>>>> Hi All: >>>>>>> >>>>>>> As discussed in the meeting today, we all agreed that it will be a >>>>>>> good idea to push docker images for each new ovs/ovn stable release. >>>>>>> Hence, >>>>>>> need help from maintainers Ben/Mark/Justin/Han to address some open >>>>>>> action >>>>>>> items as it is more of org/ownership/rights related: >>>>>>> >>>>>>> 1. Get new repo created under docker.io with name either ovs/ovn >>>>>>> and declare it public repo >>>>>>> 2. How about copy-rights for running images for open source >>>>>>> projects >>>>>>> 3. Storage: unlimited or some limited GBs >>>>>>> 4. Naming conventions for docker images ;e.g >>>>>>> openswitch/ovn:2.13.1_debian or openswitch/ovn:2.13.1_rhel. >>>>>>> Similar for ovs. >>>>>>> >>>>>>> >>>>>>> Once this is done, we can bundle docker image changes in the same >>>>>>> release process >>>>>>> >>>>>>> Please feel free to add any missing piece. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> discuss mailing list >>>>>>> [email protected] >>>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>>>>>> >>>>>> _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
