scalingengine job from app-autoscaler/8.2.0
Github source:
8ef2566b
or
master branch
Properties¶
autoscaler
¶
cf
¶
api
¶the Cloud Foundry API endpoint
client_id
¶the client id to log in cf
idle_connection_timeout_ms
¶The maximum amount of time an idle (keep-alive) connection will remain idle before closing itself. Zero means no limit.
- Default
5000
max_idle_conns_per_host_ms
¶Controls the maximum idle (keep-alive) connections to keep pooled per-host. If zero, golang default (2) is used. A negative value will mean no idle connection pool reuse.
- Default
200
max_retries
¶The number of retries from the autoscaler to the cf api (cloud controller). 0 turns off the retries.
- Default
3
max_retry_wait_ms
¶The maximum amount of time in milliseconds to wait between retries. 0 leaves it to the implementation to decide
- Default
0
secret
¶the secret to log in cf
skip_ssl_validation
¶Flag to skip ssl validation to connect to CC and UAA
- Default
false
changeloglock_timeout_seconds
¶Liquibase changelog lock timeout duration in seconds
- Default
180
policy_db
¶
address
¶IP address on which the policydb server will listen
- Default
autoscalerpostgres.service.cf.internal
databases
¶The list of databases used in policydb database including name
db_scheme
¶Database scheme to be used to access policydb
- Default
postgres
port
¶Port on which the policydb server will listen
roles
¶The list of database roles used in policydb database including name/password
sslmode
¶sslmode to connect to postgres server
- Default
disable
tls
¶
ca
¶PEM-encoded ca certificate of tls database server
- Default
""
crt
¶PEM-encoded certificate of tls database client
- Default
""
key
¶PEM-encoded key of tls database client
- Default
""
policy_db_connection_config
¶
connection_max_lifetime
¶
- Default
60s
max_idle_connections
¶
- Default
10
max_open_connections
¶
- Default
20
scalingengine
¶
ca_cert
¶PEM-encoded CA certificate
defaultCoolDownSecs
¶Default value for cool_down_secs
- Default
300
health
¶
password
¶the password of health endpoint
- Default
""
port
¶the listening port of health endpoint
- Default
6204
username
¶the username of health endpoint
- Default
""
hooks
¶
post_start
¶Script to run after scalingengine has started
- Default
""
post_stop
¶Script to run after scalingengine has stopped
- Default
""
pre_start
¶Script to run before starting scalingengine
- Default
""- Example
|+ #!/bin/bash echo "Going to start scalingengine" echo "scalingengine data directory is ${DATA_DIR}" echo "scalingengine port is ${PORT}" echo "scalingengine directory is ${PACKAGE_DIR}"
pre_stop
¶Script to run before stopping scalingengine
- Default
""
http_client_timeout
¶Http client imeout for scalingengine to communicate with other autoscaler components
- Default
60s
lockSize
¶the lock size of scalingengine
- Default
32
logging
¶
level
¶the level of logging
- Default
info
require_consul
¶whether to start consul agent
- Default
false
server
¶
port
¶the listening port of server
- Default
6104
server_cert
¶PEM-encoded server certificate
server_key
¶PEM-encoded server key
scalingengine_db
¶
address
¶IP address on which the scalingenginedb server will listen
- Default
autoscalerpostgres.service.cf.internal
databases
¶The list of databases used in scalingenginedb database including name
db_scheme
¶Database scheme to be used to access scalingenginedb
- Default
postgres
port
¶Port on which the scalingenginedb server will listen
roles
¶The list of database roles used in scalingenginedb database including name/password
sslmode
¶sslmode to connect to postgres server
- Default
disable
tls
¶
ca
¶PEM-encoded ca certificate of tls database server
- Default
""
crt
¶PEM-encoded certificate of tls database client
- Default
""
key
¶PEM-encoded key of tls database client
- Default
""
scalingengine_db_connection_config
¶
connection_max_lifetime
¶
- Default
60s
max_idle_connections
¶
- Default
10
max_open_connections
¶
- Default
20
scheduler_db
¶
address
¶IP address on which the schedulerdb server will listen
- Default
autoscalerpostgres.service.cf.internal
databases
¶The list of databases used in schedulerdb database including name
db_scheme
¶Database scheme to be used to access schedulerdb
- Default
postgres
port
¶Port on which the schedulerdb server will listen
roles
¶The list of database roles used in schedulerdb database including name/password
sslmode
¶sslmode to connect to postgres server
- Default
disable
tls
¶
ca
¶PEM-encoded ca certificate of tls database server
- Default
""
crt
¶PEM-encoded certificate of tls database client
- Default
""
key
¶PEM-encoded key of tls database client
- Default
""
scheduler_db_connection_config
¶
connection_max_lifetime
¶
- Default
60s
max_idle_connections
¶
- Default
10
max_open_connections
¶
- Default
20
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/scalingengine/
directory
(learn more).
bin/hooks/post-start.sh
(fromhooks/post-start.sh.erb
)bin/hooks/post-stop.sh
(fromhooks/post-stop.sh.erb
)bin/hooks/pre-start.sh
(fromhooks/pre-start.sh.erb
)bin/hooks/pre-stop.sh
(fromhooks/pre-stop.sh.erb
)bin/liquibase.properties
(fromliquibase.properties
)bin/pre-start
(frompre-start.erb
)bin/scalingengine_ctl
(fromscalingengine_ctl
)config/certs/policy_db/ca.crt
(frompolicy_db_ca.crt.erb
)config/certs/policy_db/crt
(frompolicy_db.crt.erb
)config/certs/policy_db/key
(frompolicy_db.key.erb
)config/certs/scalingengine/ca.crt
(fromscalingengine_ca.crt.erb
)config/certs/scalingengine/server.crt
(fromscalingengine_server.crt.erb
)config/certs/scalingengine/server.key
(fromscalingengine_server.key.erb
)config/certs/scalingengine_db/ca.crt
(fromscalingengine_db_ca.crt.erb
)config/certs/scalingengine_db/crt
(fromscalingengine_db.crt.erb
)config/certs/scalingengine_db/key
(fromscalingengine_db.key.erb
)config/certs/scheduler_db/ca.crt
(fromscheduler_db_ca.crt.erb
)config/certs/scheduler_db/crt
(fromscheduler_db.crt.erb
)config/certs/scheduler_db/key
(fromscheduler_db.key.erb
)config/scalingengine.yml
(fromscalingengine.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.