Name: syslog-service
Owner: CiscoCloud
Description: Go based Syslog service that can run within an infrastructure role on Mesos.
Created: 2015-06-22 02:28:50.0
Updated: 2016-12-10 14:59:01.0
Pushed: 2015-06-30 15:45:07.0
Homepage: null
Size: 144
Language: Go
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Go based Syslog service that can run within an infrastructure role on Mesos.
Get the project
$GOPATH/src/
dir -p github.com/CiscoCloud
github.com/CiscoCloud
t clone https://github.com/CiscoCloud/syslog-service.git
syslog-service
Build the scheduler and the executor
build framework.go
build executor.go
Package the executor (make sure the built binary has executable permissions before this step!)
p -r executor.zip executor
Place the built framework and executor archive somewhere on Mesos Master node
You will need a running Mesos master and slaves to run. The following commands should be launched on Mesos Master node.
<framework-location>
framework --master master:5050 --producer.config producer.config --topic syslog
List of available flags:
tifact.host="master": Binding host for artifact server.
tifact.port=6666: Binding port for artifact server.
u.per.task=0.2: CPUs per task.
ecutor.archive="executor.zip": Executor archive name. Absolute or relative path are both ok.
ecutor.name="executor": Executor binary name contained in archive.
stances=1: Number of tasks to run.
ster="master:5050": Mesos Master address <ip:port>.
m.per.task=256: Memory per task.
oducer.config: Producer properties file name.
nc: Flag to respond only after decoding-encoding is done.
pic: Topic to produce transformed data to.
oker.list: If you are not using kafka-mesos, comma-separated list of brokers (ip:port).
er="vagrant": User to run executor.
g.level="info": Set logging level.