Each day of the XNAT Workshop agenda will be split into two types of sessions: Lectures in the morning, and Practicals in the afternoon. To participate in the practical sessions, attendees are expected to bring a sufficiently powered laptop to run XNAT virtual machines. There will be wi-fi connections available in the conference center, but users are also strongly encouraged to download necessary components prior to the start of the Workshop to minimize delays and setup time. Please contact us if you have questions about the required hardware.
Operating Systems:
Hard Drive: At least 40 GB of free hard drive space available, SSD preferred for performance
Processor: 2 gHz and up recommended
RAM: 8 GB and up recommended
Many of the practical sessions and hackathon sessions presume the use of Vagrant to create virtual machines that run the XNAT application. The XNAT team has created a Vagrant base box that has many of the services required to run XNAT already installed, greatly reducing the time required to build new instances. This is the xnatstack Vagrant base box. You should download and install this base box before leaving for XNAT Workshop 2017: this is a fairly large download (~1Gb) and will be even slower if all attendees are trying to download it at the same time on the same wireless connection!
To download the box, run the following command:
vagrant box add nrgxnat/xnatstack-ubuntu1604 --provider virtualbox
This will download the base box and cache it in your Vagrant data folder.
You can check for available updates to the xnatstack Vagrant base box by running the following command:
vagrant box update --box nrgxnat/xnatstack-ubuntu1604 --provider virtualbox
Taking care of this ahead of time will leave you more time to focus on the important parts of the sessions and practical exercises. If for some reason you don't get it downloaded ahead of the workshop, don't worry – we'll have it available on USB thumbdrives when you arrive.
You can also download the XNAT Vagrant base box by creating a new Vagrant project that references the box, then creating a VM instance from that project. Run these commands to do this:
$ vagrant init nrgxnat/xnatstack-ubuntu1604
$ vagrant up
The first command creates a very basic Vagrantfile. After deleting all the comments in that file, you're left with this:
Vagrant.configure(2) do |config|
config.vm.box = "nrgxnat/xnatstack-ubuntu1604"
end
When you run the vagrant up command, this will reference the Vagrantfile and create a new virtual machine based on the XNAT base box.
If you want to further configure your virtual machine, you can have a look at the Part 1 Installing XNAT practical session documentation from the 2016 XNAT Workshop or use the XNAT Vagrant project to automate a great deal of the setup and configuration.
If you’ve previously set up the XNAT Vagrant project, you should check to make sure your XNAT Stack box is updated to the latest version (1.1.1). You can check whether you have the latest version by running the following command:
vagrant box outdated --global
If this does indicate that your XNAT Stack box is out of date, you can update it with this command:
vagrant box update --box nrgxnat/xnatstack-ubuntu1604 --provider virtualbox
You can remove any older versions as well:
$ vagrant box remove nrgxnat/xnatstack-ubuntu1604 --box-version 1.1
$ vagrant box update --box nrgxnat/xnatstack-ubuntu1604 --provider virtualbox
We have documented several common (and a few uncommon) problems that Windows users have run into with installing and using Vagrant. Running Vagrant from Cygwin or MobaXterm will likely help. Here are some more helpful hints: Troubleshooting XNAT Vagrant Installation for Windows Use. We highly recommend running through the Vagrant's "Getting Started" sequence before the Workshop to make sure you're able to run Vagrant on your local machine.