swarm_manager job from service-fabrik/3.248.0
              Github source:
              55b6db1b or
              master branch
            
Properties¶
broker¶
  
  
    
syslog¶
host¶Syslog ingestor host IP of ELK stack
- Default
  10.1.4.3
port¶Syslog ingestor Port
- Default
  5514
common¶
  
  
    
tls_cacert¶Trust only remotes providing a certificate signed by the CA given here
env¶
  
  
    
http_proxy¶HTTP proxy that Docker should use
https_proxy¶HTTPS proxy that Docker should use
no_proxy¶List of comma-separated hosts that Docker should skip connecting to the proxy
swarm¶
  
  
    
discovery¶Swarm discovery string (ie: consul:///, etcd://,/, zk://,/, [nodes://],
discovery_options¶Swarm discovery options
- Default
  []
name¶Name for swarm manager, used syslog shipper name
- Default
  service_fabrik_swarm_manager
tls¶Use TLS
- Default
  true
tls_cert¶TLS certificate file
tls_key¶TLS key file
tls_verify¶Use TLS and verify the remote
- Default
  true
swarm_manager¶
  
  
    
advertise¶Address of the Swarm Manager joining the cluster. Other Swarm Manager(s) MUST be able to reach the Swarm Manager at this address.
api_enable_cors¶Enable CORS headers in the remote API
- Default
  false
debug¶Enable debug mode
- Default
  false
filters¶Filters to use [health, port, dependency, affinity, constraint]
- Default
  - health - port - dependency - affinity - constraint
heartbeat¶Time in second between each heartbeat
- Default
  20s
listen_address¶Listen address
- Default
  0.0.0.0
log_level¶Log level (options: debug, info, warn, error, fatal, panic)
- Default
  info
logs_dir¶logs directory of swarm_manager
- Default
  /var/vcap/sys/log/swarm_manager
node_heartbeat_retries¶No of retries swarm manager makes to check if docker nodes is healthy again if it was un-healthy previously
- Default
  "60"
overcommit¶Overcommit to apply on resources
- Default
  "0.5"
port¶Listen port
- Default
  "2376"
replication¶Enable Swarm manager replication
- Default
  false
replication_ttl¶Leader lock release time on failure
- Default
  30s
strategy¶Placement strategy to use [spread, binpack, random]
- Default
  spread
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/swarm_manager/ directory
            (learn more).
          
bin/job_properties.sh(frombin/job_properties.sh.erb)bin/swarm_manager_ctl(frombin/swarm_manager_ctl)config/docker.cacert(fromconfig/docker.cacert.erb)config/docker.cert(fromconfig/docker.cert.erb)config/docker.key(fromconfig/docker.key.erb)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.