This guide aims at helping you if you find yourself in the situation that you need to bring an existing
image from the old HPC Cloud to the new one. Among other changes, the most notable one is that you are likely to have to contextualise your VM so that it will have its network configured.
The steps we will follow are the following:
imageon the old HPC Cloud
imageinto the new HPC Cloud
imageyou are going to bring over. Make sure that there are no VM(s) running at the moment that may be using that
image. Shut VM(s) down that may be using your intended
imagebefore you proceed any further. Once the VM(s) have disappeared from the list of VMs, proceed to the next step.
imageon the table of
image, so that a panel with extended information shows at the bottom of the screen.
image will now be copied to VirDir. Depending on its size, it may take quite some time. A pop-up dialogue will tell you this and which name your
image will have.
imageinto the new HPC Cloud
In these steps you will be exposing your VirDir to the outside world. Make sure you understand the risks, and destroy the new VM you will be making as soon as you are finished importing the
cd wget https://doc.hpccloud.surfsara.nl/assets/setup_bridge_vm.sh chmod +x ./setup_bridge_vm.sh
On the Bridge VM: Run this file giving your Group name as a parameter:
image. A from will pop up.
imageto be Persistent
imagefile, pointing to the web server running in your Bridge VM, which will be something like:
http://145.100.X.X/vd/2015MMDD:hh:mm_sometext(you need to use the right IP instead of the X.X and the actual name of the file, including the colons)
imagewith the name you wrote on the form will appear on the images table, in status LOCKED. It will remain in that status until the UI has finished copying the file from your Bridge VM to the new HPC Cloud. Then it will change to READY.
imageon the new HPC Cloud shows as READY, if you do not need to bring any more images over, then now is a good time to destroy your Bridge VM. You can delete it along with its associated
You need to put that
image that you imported into a
template. We will do that now.
imagefor the Disk 0 disk.
nicInterface 0, and add a new
nic, which will get name Interface 1 to assign it to your internal network.
Fileswhose name begins with one-context. You should see 2 of them: one ending in .deb and another one ending in .rpm. If your
imageis a CentOS one (or another Red-Hat-based one), you will want to check the box next to the .rpm
file. If your
imageis a Ubuntu one (or another Debian-based one), you will want to check the box next to the .deb
template. Click on the green Create button on the top-left of the screen.
template. This creates what we will further call new VM. On the VNC console, make sure the new VM boots.
mount -t iso9660 -L CONTEXT -o ro /mnt
yum install /mnt/one-context*.rpm
dpkg -i /mnt/one-context*.deb
reboot now). Your VM should now be in a useable state (among other things, the network should be working).
When you see that the contextualization is working (e.g.: the network works on the new VM), and if you made the
imagepersistent, then you can delete the one-context* .deb or .rpm
filewill still be visible in your VM until you re-create the VM.