Arvados is migrating to a centralized configuration file for all components. The centralized Arvados configuration is /etc/arvados/config.yml. Components that support the new centralized configuration are listed below. Components not listed here do not yet support centralized configuration. During the migration period, legacy configuration files will continue to be loaded and take precedence over the centralized configuration file.
The legacy API server configuration is stored in config/application.yml and config/database.yml. After migration to /etc/arvados/config.yml, both of these files should be moved out of the way and/or deleted.
Change to the API server directory and use the following commands:
$ RAILS_ENV=production bundle exec rake config:migrate > config.yml $ cp config.yml /etc/arvados/config.yml
This will print the contents of config.yml after merging with legacy application.yml. It may then be redirected to a file and copied to /etc/arvados/config.yml.
If you wish to update config.yml configuration by hand, or check that everything has been migrated, use config:diff to print configuration items that differ between application.yml and the system config.yml.
$ RAILS_ENV=production bundle exec rake config:diff
This command will also report if no migrations are required.
Currently only reads InstanceTypes from centralized configuration. Still requires component-specific configuration file.
Currently only reads RemoteClusters from centralized configuration. Still requires component-specific configuration file.
Only supports centralized config file. No migration needed.
Only supports centralized config file. No migration needed.
The content of this documentation is licensed under the
Creative
Commons Attribution-Share Alike 3.0 United States licence.
Code samples in this documentation are licensed under the
Apache License, Version 2.0.