Guest User

Untitled

a guest
Nov 20th, 2018
103
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.41 KB | None | 0 0
  1. backend {
  2. # Override the default backend.
  3. #default = "LocalWithDocker"
  4.  
  5. # The list of providers.
  6. providers {
  7.  
  8. # The local provider is included by default in the reference.conf. This is an example.
  9.  
  10. # Define a new backend provider.
  11. LocalWithDocker {
  12. # The actor that runs the backend. In this case, it's the Shared File System (SFS) ConfigBackend.
  13. actor-factory = "cromwell.backend.impl.sfs.config.ConfigBackendLifecycleActorFactory"
  14.  
  15. # The backend custom configuration.
  16. config {
  17.  
  18. # Optional limits on the number of concurrent jobs
  19. #concurrent-job-limit = 5
  20.  
  21. # The list of possible runtime custom attributes.
  22. runtime-attributes = """
  23. String? docker
  24. String? docker_user
  25. String? cpu
  26. String? memory_mb
  27. """
  28.  
  29. # Submit string when there is no "docker" runtime attribute.
  30. submit = "/usr/bin/env bash ${script}"
  31.  
  32. # Submit string when there is a "docker" runtime attribute.
  33. submit-docker = """
  34. docker run \
  35. --rm -i \
  36. ${"--cpus=" + cpu} \
  37. ${"--memory=" + memory_mb + "m" }
  38. ${"--user " + docker_user} \
  39. --entrypoint ${job_shell} \
  40. -v ${cwd}:${docker_cwd} \
  41. ${docker} ${script}
  42. """
  43.  
  44. # Root directory where Cromwell writes job results. This directory must be
  45. # visible and writeable by the Cromwell process as well as the jobs that Cromwell
  46. # launches.
  47. root = "cromwell-executions"
  48.  
  49. # Root directory where Cromwell writes job results in the container. This value
  50. # can be used to specify where the execution folder is mounted in the container.
  51. # it is used for the construction of the docker_cwd string in the submit-docker
  52. # value above.
  53. dockerRoot = "/cromwell-executions"
  54.  
  55. # File system configuration.
  56. filesystems {
  57.  
  58. # For SFS backends, the "local" configuration specifies how files are handled.
  59. local {
  60.  
  61. # Try to hard link (ln), then soft-link (ln -s), and if both fail, then copy the files.
  62. localization: [
  63. "hard-link", "soft-link", "copy"
  64. ]
  65.  
  66. # Call caching strategies
  67. caching {
  68. # When copying a cached result, what type of file duplication should occur. Attempted in the order listed below:
  69. duplication-strategy: [
  70. "hard-link", "soft-link", "copy"
  71. ]
  72.  
  73. # Possible values: file, path
  74. # "file" will compute an md5 hash of the file content.
  75. # "path" will compute an md5 hash of the file path. This strategy will only be effective if the duplication-strategy (above) is set to "soft-link",
  76. # in order to allow for the original file path to be hashed.
  77. hashing-strategy: "file"
  78.  
  79. # When true, will check if a sibling file with the same name and the .md5 extension exists, and if it does, use the content of this file as a hash.
  80. # If false or the md5 does not exist, will proceed with the above-defined hashing strategy.
  81. check-sibling-md5: false
  82. }
  83. }
  84. }
  85.  
  86. # The defaults for runtime attributes if not provided.
  87. default-runtime-attributes {
  88. failOnStderr: false
  89. continueOnReturnCode: 0
  90. cpu: 1
  91. memory: "4 MB"
  92. }
  93. }
  94. }
  95. }
  96. }
Add Comment
Please, Sign In to add comment