golang-lvs's Introduction

Golang LVS

A small wrapper around ipvsadm to support go interacting with the Linux Virtual Server.

Data Types:

Ipvs

Data:

MulticastInterface: String with the name of the interface broadcast the multicast state information on.
Syncid: Id to use when broadcasting state.
Tcp: Timeout for TCP connections.
Tcpfin: Timeout for TCP-FIN packets.
Udp: Timeout for UDP connections.
Services: Slice of Services.

Methods:

FindService
AddService
EditService
RemoveService
SetTimeouts
Restore
Save
StartDaemon
StopDaemon
Zero

Service

Data:

Host: IP associated to the service.
Port: Port that the service listens to.
Type: Type of service (tcp, udp, fwmark).
Scheduler: Method of assigning connections to downstream servers (rr, wrr, lc, wlc, lblc, lblcr, dh, sh, sed, nq).
Persistence: Persistent connection timeout.
Netmask: Netmask to use to group connections together.
Servers: Slice of Servers.

Methods:

FindServer
AddServer
EditServer
RemoveServer
Zero
ToJson
FromJson
String

Server

Data:

Host: IP associated with the server.
Port: Port the downstream server is listening on.
Forwarder: Method to forward to the downstream server (g=gatewaying, i=ipip, m=masquerading).
Weight: Relative weight of this server to the others. 0 means no new connections.
UpperThreshold: Stop sending connections when this limit is reached. 0 means no limit.
LowerThreshold: Restart sending connections when connections drop to this number. 0 means not set.

Methods:

ToJson
FromJson
String

golang-lvs's People

Contributors

Stargazers

Watchers

golang-lvs's Issues

Add requirements or a check

Hi, Have been playing with this package to see if i can build a layer 4 load balancer with this.

This package assumes that ipvsadm is installed on the machine + there are enough privileges to get values returned. I could be wrong, but errors from lvs.Ipvs.Services are not returned when ipvsadm is missing on the host, this makes debugging a bit harder.

Example code:

package main

import (
	"fmt"

	lvs "github.com/nanobox-io/golang-lvs"
)

var listIpvs lvs.Ipvs

func main() {
	listIpvs.Save()
	output := listIpvs.Services

	fmt.Println(output)
}

Returns [] when either privileges are not there or ipvsadm is not installed.

Perhaps it is an idea to add requirements in the README or perhaps check in the code if ipvsadm / privileges are there.

unit testing difficulties

Without being able to change the "backend/backendStdin/backendRun" or having defined interfaces for Ipvs, Service, etc. it is difficult to mock out this library. Would you be open to either exposing the backend variables or providing a way to set them or creating interfaces for the existing structs? I am happy to create a PR to help.

I have had to resort to creating a set of adapters around the library in order to mock it, however this is time consuming and only benefits me. So i'm happy to contribute in any way.

nanobox-io / golang-lvs Goto Github PK

golang-lvs's Introduction

Golang LVS

Data Types:

Ipvs

Service

Server

golang-lvs's People

Contributors

Stargazers

Watchers

Forkers

golang-lvs's Issues

Support for UDP

Add requirements or a check

unit testing difficulties

Is there any example to use this package?

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent