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
