[ovs-discuss] OVS/OVN docker image for each stable release
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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Hi If it is useful, we can start this with: GitHub.com/ServiceFractal/ovs /Shivaram ::Sent from my mobile device:: > On Nov 7, 2019, at 4:15 PM, aginwala 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: > Get new repo created under docker.io with name either ovs/ovn and declare it > public repo > How about copy-rights for running images for open source projects > Storage: unlimited or some limited GBs > 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Thanks Shivaram. I will wait for mainteners to comment as it would be nice to host a docker image of at-least one stable release to start with which could be either 2.11/2.12 or upcoming 2.13 version under ovs/ovn org. What do you think? On Thu, Nov 7, 2019 at 3:56 PM Shivaram Mysore wrote: > Hi > If it is useful, we can start this with: > GitHub.com/ServiceFractal/ovs > > /Shivaram > ::Sent from my mobile device:: > > On Nov 7, 2019, at 4:15 PM, aginwala 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
I had created a openvswitch repo in docker as a placeholder. Happy to provide it to whoever the admin is. On Thu, 7 Nov 2019 at 13:15, aginwala 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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 wrote: > On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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* 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 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 wrote: > >> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: >> >>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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 wrote: > > > On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: >>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
In my opinion, docker run options are incomplete and may not work. Please check the github page that I referred to earlier /Shivaram ::Sent from my mobile device:: > On Nov 8, 2019, at 5:19 PM, aginwala 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 > 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 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 wrote: On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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: > Get new repo created under docker.io with name either ovs/ovn and declare > it public repo > How about copy-rights for running images for open source projects > Storage: unlimited or some limited GBs > 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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 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 wrote: >> >> >>> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: >> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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: >>> Get new repo created under docker.io with name either ovs/ovn and >>> declare it public repo >>> How about copy-rights for running images for open source projects >>> Storage: unlimited or some limited GBs >>> 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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 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 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 wrote: > >> >> >> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
I am giving a talk about the same at OVS conference. Most of the info is documented in the github repo. If that does not help, please post questions and I will help document the same. /Shivaram ::Sent from my mobile device:: > On Nov 8, 2019, at 6:49 PM, aginwala wrote: > > > 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 >> 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 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 wrote: > On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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: > Get new repo created under docker.io with name either ovs/ovn and > declare it public repo > How about copy-rights for running images for open source projects > Storage: unlimited or some limited GBs > 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...
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Sounds good. Looking forward to it. Just want to reiterate that this discussion is more about maintaining docker image for each stable ovn/ovs upstream release and inputs from mainteners. We can start a separate thread for performance and other issues for running ovs/ovn in containers accordingly after your talk. On Fri, Nov 8, 2019 at 4:53 PM Shivaram Mysore wrote: > I am giving a talk about the same at OVS conference. Most of the info is > documented in the github repo. > > If that does not help, please post questions and I will help document the > same. > > /Shivaram > ::Sent from my mobile device:: > > On Nov 8, 2019, at 6:49 PM, aginwala wrote: > > > 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 > 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 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 wrote: >> >>> >>> >>> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > >> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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. ___ disc
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Fri, 8 Nov 2019 at 14:41, aginwala 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? > > On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty wrote: > >> >> >> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: > > > On Fri, 8 Nov 2019 at 14:41, aginwala 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. > >> On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty wrote: >> >>> >>> >>> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > >> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Mon, 11 Nov 2019 at 10:08, aginwala wrote: > > > On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: > >> >> >> On Fri, 8 Nov 2019 at 14:41, aginwala 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. > >>> On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty wrote: >>> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: >> >>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Guru is correct. You cannot include a kernel module in a docker image. /Shivaram ::Sent from my mobile device:: > On Nov 11, 2019, at 1:04 PM, Guru Shetty wrote: > > > > >> On Mon, 11 Nov 2019 at 10:08, aginwala wrote: >> >> >>> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >>> >>> On Fri, 8 Nov 2019 at 14:41, aginwala 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. > > > On Fri, Nov 8, 2019 at 2:37 PM Guru Shetty wrote: > > >> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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: >> Get new repo created under docker.io with name either ovs/ovn and >> declare it public repo >> How about copy-rights for running images for open source projects >> Storage: unlimited or some limited GBs >> 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/ma
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Thanks Guru. On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: > > > On Mon, 11 Nov 2019 at 10:08, aginwala wrote: > >> >> >> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >> >>> >>> >>> On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: > > > On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: >>> On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 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 open
Re: [ovs-discuss] OVS/OVN docker image for each stable release
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 wrote: > Thanks Guru. > > On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: > >> >> >> On Mon, 11 Nov 2019 at 10:08, aginwala wrote: >> >>> >>> >>> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >>> On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: > >> >> >> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > On Fri, 8 Nov 2019 at 09:53, Guru Shetty 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 wrote: >> >>> Hi All: >>> >>
Re: [ovs-discuss] OVS/OVN docker image for each stable release
Thanks Shivaram: On Tue, Nov 12, 2019 at 9:28 AM Shivaram Mysore wrote: > 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. > > Because the container image published is ubuntu and hence we tagged it with _debian. It doesn't indicate it will not work on rhel. If we all agree we can remove the tags and update the readme.md on docker.io that each container image is using ubuntu as base image. I am fine with any approach. > 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. > > I think the objective is to have an image per upstream stable ovs release and hence building it in container. Hope everyone is ok here. > On Tue, Nov 12, 2019 at 12:51 AM aginwala wrote: > >> Thanks Guru. >> >> On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: >> >>> >>> >>> On Mon, 11 Nov 2019 at 10:08, aginwala wrote: >>> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: > > > On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: >> >>> >>> >>> On Fri, 8 Nov 2019 at 14:18, aginwala 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 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 wrote: > >> On Fri, 8 Nov 2019 at 09:53, Guru Shetty wrote: >> >>> I had created a openvswitch repo in docker as
Re: [ovs-discuss] OVS/OVN docker image for each stable release
No need to indicate "built on Ubuntu" for docker image tags. Alpine tag is specifically used as it used different libraries and image size is small. Ideally, for Docker images, we should use Alpine Linux. If OVS for Alpine is latest, then image size will be further reduced. Note thAt at the end of the day, container is just a delivery or packaging vehicle. /Shivaram ::Sent from my mobile device:: > On Nov 12, 2019, at 9:49 AM, aginwala wrote: > > > Thanks Shivaram: > >> On Tue, Nov 12, 2019 at 9:28 AM Shivaram Mysore >> wrote: >> 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. >> > Because the container image published is ubuntu and hence we tagged it with > _debian. It doesn't indicate it will not work on rhel. If we all agree we can > remove the tags and update the readme.md on docker.io that each container > image is using ubuntu as base image. I am fine with any approach. >> 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. >> > I think the objective is to have an image per upstream stable ovs release and > hence building it in container. Hope everyone is ok here. >>> On Tue, Nov 12, 2019 at 12:51 AM aginwala wrote: >>> Thanks Guru. >>> > On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: > > >> On Mon, 11 Nov 2019 at 10:08, aginwala wrote: >> >> >>> On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >>> >>> On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: > On Fri, 8 Nov 2019 at 14:18, aginwala 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 pla
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Wed, Nov 13, 2019 at 12:02 AM Shivaram Mysore wrote: > > No need to indicate "built on Ubuntu" for docker image tags. > Alpine tag is specifically used as it used different libraries and image size > is small. Ideally, for Docker images, we should use Alpine Linux. If OVS > for Alpine is latest, then image size will be further reduced. > > Note thAt at the end of the day, container is just a delivery or packaging > vehicle. > > /Shivaram > ::Sent from my mobile device:: > > On Nov 12, 2019, at 9:49 AM, aginwala wrote: > > > Thanks Shivaram: > > On Tue, Nov 12, 2019 at 9:28 AM Shivaram Mysore > wrote: >> >> 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. >> > Because the container image published is ubuntu and hence we tagged it with > _debian. It doesn't indicate it will not work on rhel. If we all agree we can > remove the tags and update the readme.md on docker.io that each container > image is using ubuntu as base image. I am fine with any approach. >> >> 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. I think the idea was to have an OVS container image with the latest master code right Aliasgar ? Getting OVS packages is good, but then the debian/ubuntu/fedora packages should be updated as soon as OVS does a release. Thanks Numan >> > I think the objective is to have an image per upstream stable ovs release and > hence building it in container. Hope everyone is ok here. >> >> On Tue, Nov 12, 2019 at 12:51 AM aginwala wrote: >>> >>> Thanks Guru. >>> >>> On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: On Mon, 11 Nov 2019 at 10:08, aginwala wrote: > > > > On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: >> >> >> >> On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: On Fri, 8 Nov 2019 at 14:18, aginwala 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
Re: [ovs-discuss] OVS/OVN docker image for each stable release
On Tue, Nov 12, 2019 at 10:57 PM Numan Siddique wrote: > On Wed, Nov 13, 2019 at 12:02 AM Shivaram Mysore > wrote: > > > > No need to indicate "built on Ubuntu" for docker image tags. > > Alpine tag is specifically used as it used different libraries and image > size is small. Ideally, for Docker images, we should use Alpine Linux. If > OVS for Alpine is latest, then image size will be further reduced. > > > > Note thAt at the end of the day, container is just a delivery or > packaging vehicle. > > > > /Shivaram > > ::Sent from my mobile device:: > > > > On Nov 12, 2019, at 9:49 AM, aginwala wrote: > > > > > > Thanks Shivaram: > > > > On Tue, Nov 12, 2019 at 9:28 AM Shivaram Mysore < > shivaram.mys...@gmail.com> wrote: > >> > >> 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. > >> > > Because the container image published is ubuntu and hence we tagged it > with _debian. It doesn't indicate it will not work on rhel. If we all agree > we can remove the tags and update the readme.md on docker.io that each > container image is using ubuntu as base image. I am fine with any approach. > >> > >> 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. > > I think the idea was to have an OVS container image with the latest > master code right Aliasgar ? Yes. E.g ovs docker image for ovs release 2.12.0 with debian/rhel will checkout v2.12.0 code from git and build it. That way source code will exist in docker image from which ovs2.12.0 will be installed on that container. > > > Getting OVS packages is good, but then the debian/ubuntu/fedora > packages should be updated as soon as OVS does a release. You mean to say e.g install with dpkg -i for latest version pushed using *2.12.0.deb for debian and skip building from source Code? So I think the open question now is; do we want to have source code in version specific container image with ovs installed from source code or we just need version specific ovs installed without source in the container? Thanks > Numan > > >> > > I think the objective is to have an image per upstream stable ovs > release and hence building it in container. Hope everyone is ok here. > >> > >> On Tue, Nov 12, 2019 at 12:51 AM aginwala wrote: > >>> > >>> Thanks Guru. > >>> > >>> On Mon, Nov 11, 2019 at 1:03 PM Guru Shetty wrote: > > > > On Mon, 11 Nov 2019 at 10:08, aginwala wrote: > > > > > > > > On Mon, Nov 11, 2019 at 9:00 AM Guru Shetty wrote: > >> > >> > >> > >> On Fri, 8 Nov 2019 at 14:41, aginwala 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 wrote: > > > > On Fri, 8 Nov 2019 at 14:18, aginwala 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 kern
