Code Monkey home page Code Monkey logo

ovs-toolbox's Introduction

header

ovs-toolbox

ovs-toolbox.py is a graphical user interface for Open vSwitch (OvS).

header

OvS bridges managed by this GUI, do not necessarily need to be local to your host. (They can be located on AWS, GCP, etc.. and managed remotely by this GUI via ssh/paramiko/sudo )

In addition, this GUI will help you with docker and KVM ecosystems (for simple tasks like connecting containers and VMs to OvS).

OvS related settings that you can manage with this GUI:

  • bridge creation
  • port/interface creation ( vlan, interface types, etc..)
  • port statistics
  • ingress policy
  • mirroring
  • bonding
  • RSTP, STP
  • multicast
  • flows (netflow,sflow,ipfix)
  • queues and QOS
  • OpenFlow flows
  • OpenFlow groups
  • various OvS databases (controller, manager, Open_vSwitch, ssl )

Docker related settings that you can manage with this GUI:

  • docker files creation
  • docker image creation, docker image build
  • docker run, stop and rm
  • docker inspect
  • docker containers network parameters and automatic connection to selected OvS through one or multiple network interfaces.

KVM related things you can do with this GUI:

  • virt-install settings
  • KVM network parameters and automatic connection to selected OvS

iproute related things you can do with this GUI:

  • interface creation (dummy, tap, tun, veth pair )
  • MTU setting
  • ip address setting

Plotnetcfg

For documentation, read ovs-toolbox wiki


© 2018 Nicolas Bonnand, Licensed under the Apache License, Version 2.0

ovs-toolbox's People

Contributors

nbonnand avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ovs-toolbox's Issues

Connecting external VM on a single Bridge

Hello Nicolas,

Is it possible to use ovs-toolbox to connect 2 external VM(VMware) to OVS based on Ubuntu?

Proposed architecture:
Vm1-Web1(VMware)-(port 80)
Vm2-Web2(VMware)-(Port 80)
Vm3(OVS-Switch with Open Day Light Controller) with 1 interface(ens33) bridge to host(hypervisor)
A bridge is used to connect Vm1-Web1(VMware) and Vm2-Web2(VMware) deployed on Vm3 using tun tap virtual port.(ip tuntap add mode tap vport1)
Interface ens33 is connected to the bridge.
Interface ens33 should be able to communicate with hypervisor(Windows 11).
VM3 should be able to communicate to the Internet also.
Hence the hypervisor(windows 11) should be able to communicated to the bridge.(To connect to the 2 web servers).

I am have been able to manually setup the above configurations using reference video such as:
https://www.howtoforge.com/tutorial/software-defined-networking-sdn-openflow-and-ovsdb-connection/
https://www.youtube.com/watch?v=Gud2GoI-W_w
https://www.youtube.com/watch?v=rYW7kQRyUvA&t=4s

Can you please confirm we can can setup the above configurations using the ovs-toolbox?
Can you also please indicate any steps required to configured the above configuration?
I also did not identify any method to allow interface to get IP from dhcp.(Example on ubuntu using command dhclient ens33)

Thank you in advance Nicolas for your help,
Thank you,
Dheeraaj

When I attempt to run: ./ovs-toolbox.py; I get "This application failed to start..." with a couple of errors related to qt.qpa.xcb

Hello,

Do you think you might be able to help me figure out if I have done something incorrectly or if there is an actual issue?

I am trying to run ovs-toolbox on CentOS 7, and I think I followed the directions properly from the install directions at https://github.com/nbonnand/ovs-toolbox/blob/master/INSTALL

More specifically, it looks like I am running the following versions after installing it:

  • CentOS Linux release 7.8.2003 (Core)
  • python3.6 / python3.6m and python 2.7
  • PyQt5 python3.6/site-packages (5.15.2) and python3.6/site-packages (from PyQt5) (12.8.1)
  • paramiko python3.6/site-packages (from paramiko) (1.4.0) and python3.6/site-packages (from paramiko) (3.2.0) and (3.2.1)

When I attempt to run the Python Script ending in .py that is:

"./ovs-toolbox.py" at the Linux Command Line Prompt: # ./ovs-toolbox.py

I get the following errors/outputs:

]# ./ovs-toolbox.py
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

Aborted (core dumped)
]#

Looking through Google, I am finding a decent amount of results, but I am not sure how relevant they are. What exactly is it asking to re-install, "Python, the ovs-toolbox, qt.qpa.xcb," or what? I attempted to re-install the python from sudo yum reinstall ..., and I re-downloaded and re-ran the shell to install the toolbox.

Do you have any ideas on how I might get this fixed?

I greatly appreciate any help that you can provide.

Thanks in advance,

Transaction Log

Hello,

Do you have a transaction logs, which saves all the commend send to the OVS ?
Where we review all the commands and send for potential error?
The same transaction logs can be used as export or import for future projects.

Thank you,
Dheeraaj

Connection to an existing bridge

Hello Nicolas,

The first step to use the tool-box is to create a profile.
If I have already a bridge configured with OVS running on Ubuntu.
How to connect the tool to an existing bridge which is already running?
Does it has the capacity to identify existing OVS configuration made:
Existing bridge created with tap interfaces?

Thank you,
Dheeraaj

test

This is a test

Version

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.