I am not sure why "*_debian" is used. The image should work across OS. I have not seen use of "*_linux" as most docker images use some form of shell scripts.
Also, in my opinion, the docker image should not build OVS. If it can add appropriate OVS packages like https://github.com/servicefractal/ovs/blob/master/Dockerfile is better as they are already tested. Building OVS as a part of this will cause more testing impacts and is unnecessary. The objective is to run OVS in a container image. I would keep it simple. On Tue, Nov 12, 2019 at 12:51 AM aginwala <aginw...@asu.edu> wrote: > Thanks Guru. > > On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty <g...@ovn.org> wrote: > >> >> >> On Mon, 11 Nov 2019 at 10:08, aginwala <aginw...@asu.edu> wrote: >> >>> >>> >>> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty <g...@ovn.org> wrote: >>> >>>> >>>> >>>> On Fri, 8 Nov 2019 at 14:41, aginwala <aginw...@asu.edu> 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. >>>>> >>>> >>>> It is not clear to me. Is DKMS enabled here? Or is it that >>>> openvswitch/ovs:2.12.0_debian_4.15.0-66-generic will only work on >>>> kernel 4.15.0-66-generic? >>>> >>>> >>> No. Dkms is not enabled because idea is to release a new docker image >>> for every new kernel upgrade on compute (Not sure if dkms will help much in >>> container case as we are not installing on host). Do you have any specific >>> use case which? Yes on host with 4.15.0-66-generic. >>> >> >> It will probably be very hard to release each OVS version to so many >> available kernels. How do you decide which kernel that you want to release >> a image for? What is the plan here? I think it makes sense to release one >> image without a kernel module packed with it. >> >> Agree, we can't publish too many images based on different kernel > versions. Hence, I am ok with the approach you proposed by publishing > single image for each stable release leveraging host kernel modules. I have > pushed 2 debian images for each stable releases 2.11.2_debian and > 2.12.0_debian under openvswitch/ovs accordingly. I also sent the > corresponding patch https://patchwork.ozlabs.org/patch/1193372/ to > refactor the docker builds to support an option to skip kernel modules for > ovs repo so that user can choose to build/run with/without kernel modules. > Let me know further. > > >> >> >>> >>>>> On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty <g...@ovn.org> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Fri, 8 Nov 2019 at 14:18, aginwala <aginw...@asu.edu> 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 <aginw...@asu.edu> 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 <g...@ovn.org> wrote: >>>>>>>> >>>>>>>>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty <g...@ovn.org> 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 <aginw...@asu.edu> 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 >>>>>>>>>>> disc...@openvswitch.org >>>>>>>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>>>>>>>>>> >>>>>>>>>> _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
