Ovs container is a container with ovs capabilities. Once a container is created from this image (with host_network=True), ovs capabilities will be plugged into the container.
For more details see the Introduction to Zero-OS in the /docs documentation directory, which includes a comprehensive table of contents.
For more details see the [For more details see the Introduction to the Open vSwitch Plugin in the /docs documentation directory, which includes a table of contents.
to build simply run
makeThis will create output directly image which is an ubuntu root with openvswitch installed.
It also will have the required .startup.toml and .plugin.toml
Once the image is created you cat upload it to hub.gig.tech
Add a new VSwitch
{
"bridge": "name", //bridge name
"options": {"stp_enable": "true"} //optional options
}Delete a VSwitch
{
"bridge": "name", //bridge name
}Add a new port to a switch
{
"bridge": "name", //bridge name
"port": "port name", //port name
"vlan": 10, //vlan tag (0 for no vlan tag)
"options": { //extra options to set on the port (optional)
"type": "patch", //set type option
"options:peer": "peer name", //set peer name option
}
}Add a port to a bridge
{
"bridge": "name", //bridge name [optional]
"port": "port name", //port name
}Add a bond to a bridge
{
"bridge": "name", //bridge name
"port": "bond-name",
"links": ["eth0", "ethc1", "..."], //link names to bond
"mode": "mode", //bond modes (active-backup, balance-slb, balance-tcp)
"lacp": bool,
}Set attributes in a table
{
"table": "table-name", //table name (Interface, etc...)
"record": "record-key", //record key (port name, etc...)
"options": {
"key", "value", // (ex: "type": "patch")
}
}Those command abstract some networking operations
Create a tagged bridge with given vlan tag
{
"master": "master-bridge-name", //ex: backplane
"vlan": tag, //vlan tag (0==untagged, or 1 to 4094)
"name": "create-bridge-name" //[optional], if not given bridge name will be "vlbr[tag]"
}returns the created bridge name
Create a vxlan bridge with given vxlan id
{
"master": "master-bridge-name", //ex: vxbackend
"vxlan": id, //vxlan id
}returns the created bridge name