Advertisement
Guest User

galaxy job runner config

a guest
Dec 14th, 2011
221
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 22.09 KB | None | 0 0
  1. # Galaxy is configured by default to be useable in a single-user development
  2. # environment.  To tune the application for a multi-user production
  3. # environment, see the documentation at:
  4. # http://bitbucket.org/galaxy/galaxy-central/wiki/Config/ProductionServer
  5. # Throughout this sample configuration file, except where stated otherwise,
  6. # uncommented values override the default if left unset, whereas commented
  7. # values are set to the default value.
  8. # examples of many of these options are explained in more detail in the wiki:
  9. # Config hackers are encouraged to check there before asking for help.
  10.  
  11. # ---- HTTP Server ----------------------------------------------------------
  12. # Configuration of the internal HTTP server.
  13. [server:runner0]
  14.  
  15. # The internal HTTP server to use.  Currently only Paste is provided.  This
  16. # option is required.
  17. use = egg:Paste#http
  18.  
  19. # The port on which to listen.
  20. port = 8080
  21.  
  22. # The address on which to listen.  By default, only listen to localhost (Galaxy
  23. # will not be accessible over the network).  Use '0.0.0.0' to listen on all
  24. # available network interfaces.
  25. host = 127.0.0.1
  26.  
  27. # Use a threadpool for the web server instead of creating a thread for each
  28. # request.
  29. use_threadpool = True
  30.  
  31. # Number of threads in the web server thread pool.
  32. threadpool_workers = 7
  33.  
  34. # ---- Filters --------------------------------------------------------------
  35. # Filters sit between Galaxy and the HTTP server.
  36. # These filters are disabled by default.  They can be enabled with
  37. # 'filter-with' in the [app:main] section below.
  38.  
  39. # Define the gzip filter.
  40. [filter:gzip]
  41. use = egg:Paste#gzip
  42.  
  43. # Define the proxy-prefix filter.
  44. #[filter:proxy-prefix]
  45. #use = egg:PasteDeploy#prefix
  46. #prefix = /galaxy
  47.  
  48. # ---- Galaxy ---------------------------------------------------------------
  49. # Configuration of the Galaxy application.
  50. [app:main]
  51.  
  52. # -- Application and filtering
  53. # The factory for the WSGI application.  This should not be changed.
  54. paste.app_factory = galaxy.web.buildapp:app_factory
  55.  
  56. # If not running behind a proxy server, you may want to enable gzip compression
  57. # to decrease the size of data transferred over the network.  If using a proxy
  58. # server, please enable gzip compression there instead.
  59. #filter-with = gzip
  60.  
  61. # If running behind a proxy server and Galaxy is served from a subdirectory,
  62. # enable the proxy-prefix filter and set the prefix in the
  63. # [filter:proxy-prefix] section above.
  64. #filter-with = proxy-prefix
  65.  
  66. # If proxy-prefix is enabled and you're running more than one Galaxy instance
  67. # behind one hostname, you will want to set this to the same path as the prefix
  68. # in the filter above.  This value becomes the "path" attribute set in the
  69. # cookie so the cookies from each instance will not clobber each other.
  70. cookie_path = /galaxyp
  71.  
  72. # -- Database
  73. # By default, Galaxy uses a SQLite database at 'database/universe.sqlite'.  You
  74. # may use a SQLAlchemy connection string to specify an external database
  75. # instead.  This string takes many options which are explained in detail in the
  76. # config file documentation.
  77. #database_connection = sqlite:///./database/universe.sqlite?isolation_level=IMMEDIATE
  78. database_connection = postgres://xxxxxxx:xxxxxx@localhost:5432/galaxy
  79.  
  80. # If the server logs errors about not having enough database pool connections,
  81. # you will want to increase these values, or consider running more Galaxy
  82. # processes.
  83. #database_engine_option_pool_size = 5
  84. #database_engine_option_max_overflow = 10
  85. database_engine_option_pool_size = 10
  86. database_engine_option_max_overflow = 20
  87.  
  88. # If using MySQL and the server logs the error "MySQL server has gone away",
  89. # you will want to set this to some positive value (7200 should work).
  90. #database_engine_option_pool_recycle = -1
  91.  
  92. # If large database query results are causing memory or response time issues in
  93. # the Galaxy process, leave the result on the server instead.  This option is
  94. # only available for PostgreSQL and is highly recommended.
  95. #database_engine_option_server_side_cursors = False
  96. database_engine_option_server_side_cursors = True
  97.  
  98. # Create only one connection to the database per thread, to reduce the
  99. # connection overhead.  Recommended when not using SQLite:
  100. #database_engine_option_strategy = threadlocal
  101. database_engine_option_strategy = threadlocal
  102.  
  103. # Log all database transactions, can be useful for debugging and performance
  104. # profiling.  Logging is done via Python's 'logging' module under the qualname
  105. # 'galaxy.model.orm.logging_connection_proxy'
  106. #database_query_profiling_proxy = False
  107.  
  108. # -- Files and directories
  109.  
  110. # Dataset files are stored in this directory.
  111. file_path = database/files
  112.  
  113. # Temporary files are stored in this directory.
  114. new_file_path = database/tmp
  115.  
  116. # Tool config file, defines what tools are available in Galaxy.
  117. tool_config_file = tool_conf.xml
  118.  
  119. # Path to the directory containing the tools defined in the config.
  120. tool_path = tools
  121.  
  122. # Directory where data used by tools is located, see the samples in that
  123. # directory and the wiki for help:
  124. # http://bitbucket.org/galaxy/galaxy-central/wiki/DataIntegration
  125. tool_data_path = tool-data
  126.  
  127. # Directory where chrom len files are kept, currently mainly used by trackster
  128. len_file_path = tool-data/shared/ucsc/chrom
  129.  
  130.  
  131. # Datatypes config file, defines what data (file) types are available in
  132. # Galaxy.
  133. datatypes_config_file = datatypes_conf.xml
  134.  
  135. # Each job is given a unique empty directory as its current working directory.
  136. # This option defines in what parent directory those directories will be
  137. # created.
  138. job_working_directory = database/job_working_directory
  139.  
  140. # If using a cluster, Galaxy will write job scripts and stdout/stderr to this
  141. # directory.
  142. cluster_files_directory = database/pbs
  143.  
  144. # External service types config file, defines what types of external_services configurations
  145. # are available in Galaxy.
  146. #external_service_type_config_file = external_service_types_conf.xml
  147.  
  148. # Path to the directory containing the external_service_types defined in the config.
  149. #external_service_type_path = external_service_types
  150.  
  151. # -- Mail and notification
  152.  
  153. # Galaxy sends mail for various things: Subscribing users to the mailing list
  154. # if they request it, emailing password resets, notification from the Galaxy
  155. # Sample Tracking system, and reporting dataset errors.  To do this, it needs
  156. # to send mail through an SMTP server, which you may define here (host:port).
  157. # Galaxy will automatically try STARTTLS but will continue upon failure.
  158. smtp_server = localhost
  159.  
  160. # If your SMTP server requires a username and password, you can provide them
  161. # here (password in cleartext here, but if your server supports STARTTLS it
  162. # will be sent over the network encrypted).
  163. #smtp_username = None
  164. #smtp_password = None
  165.  
  166. # On the user registration form, users may choose to join the mailing list.
  167. # This is the address of the list they'll be subscribed to.
  168. mailing_join_addr = galaxy-user-join@bx.psu.edu
  169.  
  170. # Datasets in an error state include a link to report the error.  Those reports
  171. # will be sent to this address.  Error reports are disabled if no address is set.
  172. error_email_to = xxxxxxxxxxxxxx
  173.  
  174. # -- Display sites
  175.  
  176. # Galaxy can display data at various external browsers.  These options specify
  177. # which browsers should be available.  URLs and builds available at these
  178. # browsers are defined in the specifield files.
  179.  
  180. # UCSC browsers: tool-data/shared/ucsc/ucsc_build_sites.txt
  181. #ucsc_display_sites = main,test,archaea,ucla
  182. ucsc_display_sites = main
  183.  
  184. # GBrowse servers: tool-data/shared/gbrowse/gbrowse_build_sites.txt
  185. #gbrowse_display_sites = wormbase,tair,modencode_worm,modencode_fly,yeast_sgd
  186. gbrowse_display_sites = wormbase,tair,modencode_worm,modencode_fly,yeast_sgd
  187.  
  188. # GeneTrack servers: tool-data/shared/genetrack/genetrack_sites.txt
  189. #genetrack_display_sites = main,test
  190. genetrack_display_sites = main
  191.  
  192. # -- Next gen LIMS interface on top of existing Galaxy Sample/Request management code.
  193.  
  194. use_nglims = False
  195. nglims_config_file = tool-data/nglims.yaml
  196.  
  197. # -- UI Localization
  198.  
  199. # Append "/{brand}" to the "Galaxy" text in the masthead.
  200. brand = UF HPC
  201.  
  202. # The URL linked by the "Galaxy/brand" text.
  203. #logo_url = /
  204.  
  205. # The URL linked by the "Galaxy Wiki" link in the "Help" menu.
  206. #wiki_url = http://bitbucket.org/galaxy/galaxy-central/wiki
  207. wiki_url = http://wiki.g2.bx.psu.edu/
  208.  
  209. # The URL linked by the "Email comments..." link in the "Help" menu.
  210. bugs_email = mailto:xxxxxxxxxxxxxx
  211.  
  212. # The URL linked by the "How to Cite..." link in the "Help" menu.
  213. #citation_url = http://bitbucket.org/galaxy/galaxy-central/wiki/Citations
  214. citation_url = http://wiki.g2.bx.psu.edu/Citing%20Galaxy
  215.  
  216. # Serve static content, which must be enabled if you're not serving it via a
  217. # proxy server.  These options should be self explanatory and so are not
  218. # documented individually.  You can use these paths (or ones in the proxy
  219. # server) to point to your own styles.
  220. static_enabled = True
  221. static_cache_time = 360
  222. static_dir = %(here)s/static/
  223. static_images_dir = %(here)s/static/images
  224. static_favicon_dir = %(here)s/static/favicon.ico
  225. static_scripts_dir = %(here)s/static/scripts/
  226. static_style_dir = %(here)s/static/june_2007_style/blue
  227.  
  228. # -- Advanced proxy features
  229.  
  230. # For help on configuring the Advanced proxy features, see:
  231. # http://usegalaxy.org/production
  232.  
  233. # Apache can handle file downloads (Galaxy-to-user) via mod_xsendfile.  Set
  234. # this to True to inform Galaxy that mod_xsendfile is enabled upstream.
  235. apache_xsendfile = True
  236.  
  237. # If using compression in the upstream proxy server, use this option to disable
  238. # gzipping of library .tar.gz and .zip archives, since the proxy server will do
  239. # it faster on the fly.
  240. upstream_gzip = True
  241.  
  242. # -- Logging and Debugging
  243.  
  244. # Verbosity of console log messages.  Acceptable values can be found here:
  245. # http://docs.python.org/library/logging.html#logging-levels
  246. #log_level = INFO
  247. log_level = DEBUG
  248. #log_level = ERROR
  249.  
  250. # Print database operations to the server log (warning, quite verbose!).
  251. #database_engine_option_echo = False
  252.  
  253. # Print database pool operations to the server log (warning, quite verbose!).
  254. #database_engine_option_echo_pool = False
  255.  
  256. # Turn on logging of application events and some user events to the database.
  257. #log_events = True
  258.  
  259. # Turn on logging of user actions to the database. Actions currently logged are
  260. # grid views, tool searches, and use of "recently" used tools menu.  The
  261. # log_events and log_actions functionality will eventually be merged.
  262. #log_actions = True
  263.  
  264. # Debug enables access to various config options useful for development and
  265. # debugging: use_lint, use_profile, use_printdebug and use_interactive.  It
  266. # also causes the files used by PBS/SGE (submission script, output, and error)
  267. # to remain on disk after the job is complete.  Debug mode is disabled if
  268. # commented, but is uncommented by default in the sample config.
  269. debug = False
  270. #debug = True
  271.  
  272. # Check for WSGI compliance.
  273. #use_lint = True
  274.  
  275. # Run the Python profiler on each request.
  276. #use_profile = True
  277.  
  278. # Intercept print statements and show them on the returned page.
  279. #use_printdebug = True
  280.  
  281. # Enable live debugging in your browser.  This should NEVER be enabled on a
  282. # public site.  Enabled in the sample config for development.
  283. #use_interactive = True
  284. use_interactive = False
  285.  
  286. # Write thread status periodically to 'heartbeat.log',  (careful, uses disk
  287. # space rapidly!).  Useful to determine why your processes may be consuming a
  288. # lot of CPU.
  289. #use_heartbeat = False
  290.  
  291. # Enable the memory debugging interface (careful, negatively impacts server
  292. # performance).
  293. #use_memdump = False
  294.  
  295. # -- Data Libraries
  296.  
  297. # These library upload options are described in much more detail in the wiki:
  298. # http://bitbucket.org/galaxy/galaxy-central/wiki/DataLibraries/UploadingFiles
  299.  
  300. # Add an option to the library upload form which allows administrators to
  301. # upload a directory of files.
  302. library_import_dir = /galaxy/data/admin_upload
  303.  
  304. # Add an option to the library upload form which allows authorized
  305. # non-administrators to upload a directory of files.  The configured directory
  306. # must contain sub-directories named the same as the non-admin user's Galaxy
  307. # login ( email ).  The non-admin user is restricted to uploading files or
  308. # sub-directories of files contained in their directory.
  309. user_library_import_dir = /galaxy/incoming
  310.  
  311. # Add an option to the admin library upload tool allowing admins to paste
  312. # filesystem paths to files and directories in a box, and these paths will be
  313. # added to a library.  Set to True to enable.  Please note the security
  314. # implication that this will give Galaxy Admins access to anything your Galaxy
  315. # user has access to.
  316. #allow_library_path_paste = False
  317.  
  318. # Users may choose to download multiple files from a library in an archive.  By
  319. # default, Galaxy allows users to select from a few different archive formats
  320. # if testing shows that Galaxy is able to create files using these formats.
  321. # Specific formats can be disabled with this option, separate more than one
  322. # format with commas.  Available formats are currently 'zip', 'gz', and 'bz2'.
  323. #disable_library_comptypes =
  324.  
  325. # Some sequencer integration features in beta allow you to automatically
  326. # transfer datasets.  This is done using a lightweight transfer manager which
  327. # runs outside of Galaxy (but is spawned by it automatically).  Galaxy will
  328. # communicate with this manager over the port specified here.
  329. #transfer_manager_port = 8163
  330.  
  331. # Search data libraries with whoosh
  332. #enable_whoosh_library_search = True
  333. # Whoosh indexes are stored in this directory.
  334. #whoosh_index_dir = database/whoosh_indexes
  335.  
  336. # Search data libraries with lucene
  337. #enable_lucene_library_search = False
  338. # maxiumum file size to index for searching, in MB
  339. #fulltext_max_size = 500
  340. #fulltext_noindex_filetypes=bam,sam,wig,bigwig,fasta,fastq,fastqsolexa,fastqillumina,fastqsanger
  341. # base URL of server providing search functionality using lucene
  342. #fulltext_url = http://localhost:8081
  343.  
  344. # -- Users and Security
  345.  
  346. # Galaxy encodes various internal values when these values will be output in
  347. # some format (for example, in a URL or cookie).  You should set a key to be
  348. # used by the algorithm that encodes and decodes these values.  It can be any
  349. # string.  If left unchanged, anyone could construct a cookie that would grant
  350. # them access to others' sessions.
  351. #id_secret = USING THE DEFAULT IS NOT SECURE!
  352. id_secret = xxxxxxxxxxxxxxxxxxxxxxxxxx
  353.  
  354. # User authentication can be delegated to an upstream proxy server (usually
  355. # Apache).  The upstream proxy should set a REMOTE_USER header in the request.
  356. # Enabling remote user disables regular logins.  For more information, see:
  357. # http://bitbucket.org/galaxy/galaxy-central/wiki/Config/ApacheProxy
  358. use_remote_user = True
  359. #use_remote_user = False
  360.  
  361. # If use_remote_user is enabled and your external authentication
  362. # method just returns bare usernames, set a default mail domain to be appended
  363. # to usernames, to become your Galaxy usernames (email addresses).
  364. # remote_user_maildomain =
  365.  
  366. # If use_remote_user is enabled, you can set this to a URL that will log your
  367. # users out.
  368. remote_user_logout_href = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  369.  
  370. # Administrative users - set this to a comma-separated list of valid Galaxy
  371. # users (email addresses).  These users will have access to the Admin section
  372. # of the server, and will have access to create users, groups, roles,
  373. # libraries, and more.  For more information, see:
  374. # http://bitbucket.org/galaxy/galaxy-central/wiki/Admin/AdminInterface
  375. admin_users = xxxxxxxxxxxxxx,xxxxxxxxxxxxxx
  376.  
  377. # Force everyone to log in (disable anonymous access).
  378. require_login = True
  379.  
  380. # Allow unregistered users to create new accounts (otherwise, they will have to
  381. # be created by an admin).
  382. allow_user_creation = True
  383.  
  384. # Allow administrators to delete accounts.
  385. #allow_user_deletion = False
  386. allow_user_deletion = True
  387.  
  388. # Allow users to remove their datasets from disk immediately (otherwise,
  389. # datasets will be removed after a time period specified by an administrator in
  390. # the cleanup scripts run via cron)
  391. allow_user_dataset_purge = True
  392.  
  393. # By default, users' data will be public, but setting this to True will cause
  394. # it to be private.  Does not affect existing users and data, only ones created
  395. # after this option is set.  Users may still change their default back to
  396. # public.
  397. new_user_dataset_access_role_default_private = True
  398.  
  399. # -- Beta features
  400.  
  401. # Enable Galaxy to communicate directly with a sequencer
  402. #enable_sequencer_communication = False
  403.  
  404. # Enable Galaxy's built-in visualization module, Trackster.
  405. enable_tracks = True
  406.  
  407. # Enable Galaxy Pages. Pages are custom webpages that include embedded Galaxy items,
  408. # such as datasets, histories, workflows, and visualizations; pages are useful for
  409. # documenting and sharing multiple analyses or workflows. Pages are created using a
  410. # WYSIWYG editor that is very similar to a word processor.
  411. enable_pages = True
  412.  
  413. # Enable authentication via OpenID.  Allows users to log in to their Galaxy
  414. # account by authenticating with an OpenID provider.
  415. enable_openid = False
  416.  
  417. # Enable the (experimental! beta!) Web API.  Documentation forthcoming.
  418. #enable_api = False
  419.  
  420. # Enable tool tags (associating tools with tags).  This has its own option
  421. # since its implementation has a few performance implications on startup for
  422. # large servers.
  423. #enable_tool_tags = False
  424.  
  425. # Enable Galaxy's "Upload via FTP" interface.  You'll need to install and
  426. # configure an FTP server (we've used ProFTPd since it can use Galaxy's
  427. # database for authentication) and set the following two options.
  428.  
  429. # This should point to a directory containing subdirectories matching users'
  430. # email addresses, where Galaxy will look for files.
  431. #ftp_upload_dir = None
  432.  
  433. # This should be the hostname of your FTP server, which will be provided to
  434. # users in the help text.
  435. #ftp_upload_site = None
  436.  
  437. # -- Job Execution
  438.  
  439. # If running multiple Galaxy processes, one can be designated as the job
  440. # runner.  For more information, see:
  441. # http://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling
  442. enable_job_running = True
  443.  
  444. # Should jobs be tracked through the database, rather than in memory.
  445. # Necessary if you're running the load balanced setup.
  446. track_jobs_in_database = True
  447.  
  448. # This enables splitting of jobs into tasks, if specified by the particular tool config.
  449. # This is a new feature and not recommended for production servers yet.
  450. #use_tasked_jobs = False
  451. #local_task_queue_workers = 2
  452.  
  453. # Enable job recovery (if Galaxy is restarted while cluster jobs are running,
  454. # it can "recover" them when it starts).  This is not safe to use if you are
  455. # running more than one Galaxy server using the same database.
  456. enable_job_recovery = True
  457.  
  458. # Setting metadata on job outputs to in a separate process (or if using a
  459. # cluster, on the cluster).  Thanks to Python's Global Interpreter Lock and the
  460. # hefty expense that setting metadata incurs, your Galaxy process may become
  461. # unresponsive when this operation occurs internally.
  462. set_metadata_externally = True
  463.  
  464. # Although it is fairly reliable, setting metadata can occasionally fail.  In
  465. # these instances, you can choose to retry setting it internally or leave it in
  466. # a failed state (since retrying internally may cause the Galaxy process to be
  467. # unresponsive).  If this option is set to False, the user will be given the
  468. # option to retry externally, or set metadata manually (when possible).
  469. #retry_metadata_internally = True
  470. retry_metadata_internally = False
  471.  
  472. # If (for example) you run on a cluster and your datasets (by default,
  473. # database/files/) are mounted read-only, this option will override tool output
  474. # paths to write outputs to the working directory instead, and the job manager
  475. # will move the outputs to their proper place in the dataset directory on the
  476. # Galaxy server after the job completes.
  477. #outputs_to_working_directory = False
  478.  
  479. # Number of concurrent jobs to run (local job runner)
  480. local_job_queue_workers = 10
  481.  
  482. # Jobs can be killed after a certain amount of execution time.  Format is in
  483. # hh:mm:ss.  Currently only implemented for PBS.
  484. #job_walltime = None
  485.  
  486. # Jobs can be killed if any of their outputs grow over a certain size (in
  487. # bytes).  0 for no limit.
  488. output_size_limit = 0
  489.  
  490. # Clustering Galaxy is not a straightforward process and requires some
  491. # pre-configuration.  See the the wiki before attempting to set any of these
  492. # options:
  493. # http://bitbucket.org/galaxy/galaxy-central/wiki/Config/Cluster
  494.  
  495. # Comma-separated list of job runners to start.  local is always started.  If
  496. # left commented, no jobs will be run on the cluster, even if a cluster URL is
  497. # explicitly defined in the [galaxy:tool_runners] section below.  The runners
  498. # currently available are 'pbs' and 'drmaa'.
  499. #start_job_runners = None
  500. start_job_runners = pbs
  501.  
  502. # The URL for the default runner to use when a tool doesn't explicitly define a
  503. # runner below.
  504. #default_cluster_job_runner = local:///
  505. default_cluster_job_runner = pbs:///galaxy/-l nodes=1:ppn=1,pmem=1gb,walltime=200:00:00
  506.  
  507. # The cluster runners have their own thread pools used to prepare and finish
  508. # jobs (so that these sometimes lengthy operations do not block normal queue
  509. # operation).  The value here is the number of worker threads available to each
  510. # started runner.
  511. cluster_job_queue_workers = 10
  512.  
  513. # ---- Tool Job Runners -----------------------------------------------------
  514.  
  515. # Individual per-tool job runner overrides.  If not listed here, a tool will
  516. # run with the runner defined with default_cluster_job_runner.
  517.  
  518. [galaxy:tool_runners]
  519.  
  520. upload1 = pbs:///galaxy/-l nodes=1:ppn=1,pmem=1gb,walltime=120:00:00
  521. fastq_groomer = pbs:///galaxy/-l nodes=1:ppn=1,pmem=1gb,walltime=240:00:00
  522. bowtie = pbs:///galaxy/-l nodes=1:ppn=5,pmem=2gb,walltime=336:00:00
  523.  
  524. #biomart = local:///
  525. #encode_db1 = local:///
  526. #hbvar = local:///
  527. #microbial_import1 = local:///
  528. #ucsc_table_direct1 = local:///
  529. #ucsc_table_direct_archaea1 = local:///
  530. #ucsc_table_direct_test1 = local:///
  531. #upload1 = local:///
  532. #biomart = pbs:///galaxy
  533. #encode_db1 = pbs:///galaxy
  534. #hbvar = pbs:///galaxy
  535. #microbial_import1 = pbs:///galaxy
  536. #ucsc_table_direct1 = pbs:///galaxy
  537. #ucsc_table_direct_archaea1 = pbs:///galaxy
  538. #ucsc_table_direct_test1 = pbs:///galaxy
  539. #upload1 = pbs:///galaxy
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement