scheduler job from app-autoscaler/15.5.0
Github source:
90f9a6236 or
master branch
Properties¶
autoscaler¶
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
""
certificate¶PEM-encoded certificate of tls database client
- Default
""
private_key¶PEM-encoded key of tls database client
- Default
""
scheduler¶
application¶
props¶Additional properties to inject into the spring application properties file
- Default
""- Example
|+ logging.level.org.cloudfoundry.autoscaler.scheduler=info logging.level.org.quartz=info
ca_cert¶PEM-encoded CA certificate
cf_server¶
xfcc¶valid_org_guid¶approve org guid for xfcc endpoint
- Default
""valid_space_guid¶approve space guid for xfcc endpoint
- Default
""
health¶
basicAuthEnabled¶if true, basic auth is enabled on the endpoint
- Default
false
ca_cert¶PEM-encoded CA certificate for the health endpoint
password¶the password to protect the health endpoint
- Default
""
port¶the listening port of health endpoint
- Default
6204
server_cert¶PEM-encoded server certificate for the health endpoint
server_key¶PEM-encoded server key for the health endpoint
unprotected_endpoints¶List of all health-endpoints, that run without basic access authentication. Valid endpoints are /health/liveness, /health/prometheus
- Default
[]
username¶the username to protect the health endpoint
- Default
""
http¶
port¶Scheduler’s http port
- Default
0
http_client_timeout¶Http client imeout for scheduler to communicate with other autoscaler components, in seconds
- Default
60
job_reschedule_interval_millisecond¶Rescheduling interval for quartz job in milliseconds
- Default
10000
job_reschedule_maxcount¶Maximum no of jobs can be re-scheduled
- Default
6
jvm_options¶Java Virtual Machine parameters to be used when start scheduler process
- Default
""- Example
-Xmx400m -XX:MaxMetaspaceSize=128m
notification_reschedule_maxcount¶Maximum number of notification sent to scaling engine for job re-schedule
- Default
3
port¶Scheduler’s https port
- Default
6102
scaling_engine¶
ca_cert¶PEM-encoded CA certificate
client_cert¶PEM-encoded client certificate
client_key¶PEM-encoded client key
host¶URL where Scaling-engine is running
- Default
scalingengine.service.cf.internal
port¶Scaling Engine’s port
- Default
6104
server_cert¶PEM-encoded server certificate
server_key¶PEM-encoded server key
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
""
certificate¶PEM-encoded certificate of tls database client
- Default
""
private_key¶PEM-encoded key of tls database client
- Default
""
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/scheduler/ directory
(learn more).
bin/bpm-pre-start(frombpm-pre-start.erb)bin/install_crt_truststore(frominstall_crt_truststore.sh)bin/liquibase.properties(fromliquibase.properties)config/bpm.yml(frombpm.yml.erb)config/certs/ca.crt(fromscheduler_ca.crt.erb)config/certs/healthendpoint/ca.crt(fromhealthendpoint_ca.crt.erb)config/certs/healthendpoint/server.crt(fromhealthendpoint.crt.erb)config/certs/healthendpoint/server.key(fromhealthendpoint.key.erb)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/client.crt(fromscalingengine_client.crt.erb)config/certs/scalingengine/client.key(fromscalingengine_client.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/certs/server.crt(fromscheduler_server.crt.erb)config/certs/server.key(fromscheduler_server.key.erb)config/scheduler.yml(fromscheduler.yml.erb)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.