Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version #5

Open
BurlyLuo opened this issue Dec 9, 2020 · 6 comments
Open

Version #5

BurlyLuo opened this issue Dec 9, 2020 · 6 comments

Comments

@BurlyLuo
Copy link

BurlyLuo commented Dec 9, 2020

Hello,Would you mind share the platform of fedora and ovs ans so on .you know if we get the wrong version of the environment ,we will face many problem.
tks.

@dkupper76
Copy link

Hello BurlyLuo and Nicolas,

I too would like to know what version of Fedora you are running OVS and OVS-toolbox on. That being said, they both should work on similar systems, like Centos. I am running CentOS Linux release 7.8.2003 (Core), probably the biggest difference is CentOS 7 still uses yum, while Fedora uses dnf, and Fedora is upstream from CentOS.

Thank you,

Daryl

@nbonnand
Copy link
Owner

nbonnand commented Dec 9, 2020

Hello,Would you mind share the platform of fedora and ovs ans so on .you know if we get the wrong version of the environment ,we will face many problem.
tks.

Hello,

OK, I should add a compatibility section in the wiki to show OS/packages I have tested ovs-toolbox with !

ovs-toolbox is compatible with latest ubuntu / centos / fedora platforms. Let me one week, and I'll complete wiki with more accurate details about tested platforms.

Here are my Fedora caracteristics:

$ rpm -q python3 python3-qt5 plotnetcfg graphviz fedora-release-common virt-install libvirt-client qemu-kvm
python3-3.8.6-1.fc32.x86_64
python3-qt5-5.14.2-3.fc32.x86_64
plotnetcfg-0.4.1-12.fc32.x86_64
graphviz-2.42.4-1.fc32.x86_64
fedora-release-common-32-4.noarch
virt-install-2.2.1-3.fc32.noarch
libvirt-client-6.1.0-4.fc32.x86_64
qemu-kvm-4.2.1-1.fc32.x86_64

$ pip3 list | egrep 'lxml|paramiko'
lxml 4.4.1
paramiko 2.7.1

$ docker -v
Docker version 19.03.11, build 42e35e6

Regards

Nicolas

@nbonnand
Copy link
Owner

nbonnand commented Dec 9, 2020

and of course openvswitch !!!!

$ rpm -q openvswitch
openvswitch-2.13.1-1.fc32.x86_64

@nbonnand
Copy link
Owner

nbonnand commented Dec 9, 2020

These packages will be needed if you play with docker networking, but I guess they are are already part of Fedora default installation.

$ rpm -q iproute util-linux
iproute-5.7.0-1.fc32.x86_64
util-linux-2.35.2-1.fc32.x86_64

Under Fedora, util-linux provides nsenter command. ( ovs-toolbox is using nsenter to enter into docker container namespace. )

@BurlyLuo
Copy link
Author

Thanks,well received the feedbacck.
About the docker image,if we run the test container with fedora image,unfortunately,the image can not contain the basic network tools,Like ping,ifconfig,tcpdump and so on.
there is option to use,the image is docker.io/burlyluo/nettoolbox:v1 which build by myself.and the image has the small size.
you can use the commond view the image details:
docker history --format {{.CreatedBy}} --no-trunc=true "docker.io/burlyluo/nettoolbox:v1"|sed "s//bin/sh\ -c\ #(nop)\ //g"|sed "s//bin/sh\ -c/RUN/g" |tac

@BurlyLuo
Copy link
Author

Hello BurlyLuo and Nicolas,

I too would like to know what version of Fedora you are running OVS and OVS-toolbox on. That being said, they both should work on similar systems, like Centos. I am running CentOS Linux release 7.8.2003 (Core), probably the biggest difference is CentOS 7 still uses yum, while Fedora uses dnf, and Fedora is upstream from CentOS.

Thank you,

Daryl

THX.
In my platform,the CentOS 7,It works well.
I think the software can not depend on the platform.maybe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants