Arvbox » History » Version 8

« Previous - Version 8/14 (diff) - Next » - Current version
Peter Amstutz, 03/03/2016 04:20 PM


Arvbox

We recommend using Arvbox to set up self-contained Arvados development environment.

Running Arvados in development mode

$ arvbox reboot dev

This performs the following operations:

  1. Rebuild the arvbox-dev docker image (typically the layers are cached so this is a no-op unless you are working on arvbox itself)
  2. Create ~/.arvbox/arvbox to store arvbox state
  3. Clone the arvados git repository to ~/.arvbox/arvbox/arvados
  4. Place stateful container data in ~/.arvbox/arvbox/postgres and ~/.arvbox/arvbox/var
  5. Start the container
The container will then:
  1. Download and cache various packages (Ruby gems, Passenger)
  2. Compile and install Arvados server binaries
  3. Build and install Arvados SDK packages (such as arvados-python-client)
  4. Start the Arvados services

The directories inside ~/.arvbox/arvbox are all bind-mounted inside the container. This means that you may edit files on the host file system and the changes will be seen inside the container immediately. For example, if you edit a page template in ~/.arvbox/arvbox/arvados/apps/workbench/app/views you only need to reload the page in your browser to see the change.

You can restart individual services without restarting the whole container. For compiled services, the startup script always recompiles the server before starting it. For example, if you are working on keepproxy

$ arvbox sv restart keepproxy

If any service fails to come up, you can see the debug log using arvbox log. This log will include compilation or install errors:

$ arvbox log keepproxy

Finally, you can get a root shell inside the container using arvbox sh

$ arvbox sh

Running the test suite

Arvbox can also be used to run the Arvados test suite in an isolated manner.

$ arvbox restart test

You can pass parameters to the test suite as described in Running tests:

$ arvbox restart test --only services/keepproxy