Cloud Images

We are providing a few "batteries-included" images of various RCloud setups.

Base: Ubuntu 16.04.1 LTS cloud image

RCloud: develop branch 2017/01/25 (really RCloud 1.7 + minor cloud-related fixes)

Format: QCOW2 bare (tested and created using OpenStack)

• rcloud-1.8-dev-base.qcow2 - minimal setup - RCloud with Redis and SKS; gitgist back-end (local), no authentication, running as ubuntu. Note that this is should be used for testing only as users accessing RCloud have super-user powers (=root) - so do NOT deploy this image publicly.
• rcloud-1.8-dev-rcu.qcow2.bz2 - same as above but RCloud running as a separate user rcloud so it doesn't have super-user powers.
• rcloud-1.8-dev-rcu-proxy.qcow2.bz2 - same as above, but proxified setup with compute-separation. All RCloud services (proxy, scripts and QAP) are running as the user rcloud.
• rcloud-1.8.1-rcu-proxy.qcow2.bz2 - same as above, but latest stable version (RCloud 1.8.1, Ubuntu 16.04.3 LTS).

All above are setup with init.d script to start all services automatically, but you still have to edit the configuration as follows:

Edit /data/rcloud/conf/rcloud.conf - change the line Cookie.domain: to your external IP address or external host name. When done, restart using

sudo /etc/init.d/rcloud-qap restart
sudo /etc/init.d/rcloud-script restart

If you don't do that, you'll be spinning between login.R and edit.html forever since the cookies will never be set properly.

The RCloud service is bound to port 8080, so make sure you bind a floating IP and expose that port. You log into the instance the via http://ip-address:8080/login.R

You may also want to edit /etc/hosts to include your internal IP and name such that the hostname resolves locally, otherwise you may experience excessive lag for some operations as the system is trying to resolve the local hostname.