Deploying and Managing GVL Analysis platform
Using the Default NeCTAR allocation
1. Access the Australian Research Cloud
- Login via the Dashboard https://dashboard.rc.nectar.org.au
- Only members of the Australian Access Federation (AAF) can access Australian Research Cloud resources. If you are not a member of AAF, GVL Help may be able to provide you with credentials.
- If this is the first time you have accessed the Australian Research Cloud, you must agree to some Terms and Conditions. You are then presented with your Default Project and Default Allocation.

2. Get Research Cloud credentials
- Go to https://dashboard.rc.nectar.org.au
- Click on 'Access & Security’ link in the left hand panel and then the ‘API Access’ tab
- Click on ‘Download EC2 Credentials’ at top right to download a zip archive of the credentials for that Project to your desktop.

- Unzip the downloaded archive. Open the file 'ec2rc.sh' with a text editor (Windows users: open the file with Wordpad)
You will need 'EC2_ACCESS_KEY’ and ‘EC2_SECRET_KEY’ each time you use the Launch page (next Section).
3. Launch the CloudBioLinux/Cloudman image
Go to launch.genome.edu.au, bringing you to the GVL BioCloudCentral launch page.

Cloud: Select default: ‘NeCTAR (Openstack)’
Access key and Secret key: Obtained in the previous Section.
- Make sure you copy and paste exactly (no extra spaces)
Institutional email: This is important for us to keep track of usage for funding & grant reporting
Cluster Name: Choose a name for your GVL instance. Whatever you want.
- Choose a unique name every time you use the Launch page; unless you are deliberately re-launching an instance that you have previously terminated. (Especially, don’t re-use a name from a previous failed launch).
Password: Choose any password - but please make it not obvious, as you are essentially creating a public server and, if it is up long enough, you will almost certainly get anonymous hacking attempts.
- Remember your password, as this is the password you will use to log into the CBL/Cloudman instance. You will get another chance to see you password when your server launch is done.
Instance Type: Choose default: Medium (2 vcpu / 8GB RAM) CPU/RAM size.
Press 'Start an Instance'. It will take 1-5 minutes to start. If you know how, you can use the NeCTAR dashboard to observe the node starting up on the cloud node.

The Launch is finished when an IP address is displayed

Click on the ip-address and you will be presented with the Dashboard of your simple GVL analysis server.
- you can access a lightweight GUI desktop via <ip-address>/vnc[1]
- you can ssh to the server using user “ubuntu” and the password you selected

4. Start a Galaxy instance
- Click on the Cloudman link

- Login, with User Name ubuntu and Password the one you entered on the Launch screen.

- Cloudman will ask which type of bioinformatics cluster you want to start.
- Select ‘Galaxy Cluster’ and ‘Transient Storage’
- Press “Choose Platform Type’.

- Cloudman will configure Galaxy on your GVL analysis server.
- The process will take around 2-5 minutes.
- Once completed, the ‘Access GVL’ button at top right will become available

- Click on the ‘Access GVL’, button. This will open your GVL analysis server Dashboard in a new browser tab.
- Click on the Galaxy link

- Register yourself as a Galaxy User (‘User’ menu option, top right), remembering the email address you use to register.
- You can use any password here, but you might like to choose the same one as you used for starting your GVL instance.

- Finished. You have a usable Galaxy server - a single node of 2 cores running Galaxy on CloudBioLinux with SunGridEngine!
5. Other Features
Also see: Galaxy and CloudMan Administration Manual - common administration tasks, including making yourself a Galaxy Administrator and managing your virtual cluster.
[1] Some networks will not allow access to <ip-address>/vnc. If this is the case, you can still access the GUI desktop via the console of your server on the NeCTAR Dashboard. The instruction for this is beyond the scope of this simple guide document. Refer to NeCTAR user guides.