grootfs job from grootfs/0.24.0
Github source:
cd787f7
or
master branch
Properties¶
grootfs
¶
driver
¶Filesystem driver to use.
- Default
overlay-xfs
dropsonde_port
¶Local metron agent’s port.
- Default
3457
external_logdevice_size_in_mb
¶EXPERIMENTAL: Size of the XFS external log device in megabytes. 0 means disabled.
- Default
0
graph_cleanup_threshold_in_mb
¶Total size of all filesystem layers downloaded from Docker registries before graph cleanup is activated. -1 disables graph cleanup.
- Default
-1
insecure_docker_registry_list
¶A list of IP:PORT tuples that we allow pulling docker images from using self-signed certificates.
- Default
[]
log_level
¶Log level for grootfs - can be debug, info, error or fatal.
- Default
info
persistent_image_list
¶List of base images (tarballs or Docker URLs) which will never be deleted during cleanup.
- Default
[]
skip_mount
¶Do not mount image root filesystem automatically, just return the mount information.
- Default
false
slow_action_threshold_in_seconds
¶EXPERIMENTAL: Defines a acceptable duration for grootfs actions before a system report log is emitted. 0 means disabled.
- Default
0
store_size_bytes
¶The size of the grootfs store. Changes to this value do not update the store on existing hosts. To resize the store, the job host must be recreated. If 0 the size will be the same as the ephemeral disk.
- Default
0
use_persistent_disk
¶EXPERIMENTAL: If true, places the image store on /var/vcap/store. If false (the default), uses /var/vcap/data
- Default
false
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/grootfs/
directory
(learn more).
bin/btrfs-setup
(frombin/btrfs-setup.erb
)bin/overlay-xfs-setup
(frombin/overlay-xfs-setup.erb
)bin/pre-start
(frombin/pre-start.erb
)bin/utils
(frombin/utils.erb
)config/grootfs_config.yml
(fromconfig/grootfs_config.yml.erb
)config/privileged_grootfs_config.yml
(fromconfig/privileged_grootfs_config.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.