Connecting to and logging into CloudBioLinux instance through GUI

[Shweta Purawat]

How can I connect to CloudBioLinux Instance on EC2 remotely via Graphically interface (GUI)? 

[Brad Chapman]

Shweta;

> How can I connect to CloudBioLinux Instance on EC2 remotely via Graphically
> interface (GUI)?

We currently support a FreeNX client to CloudBioLinux instances. The
recommended approach is to start an instance using BioCloudCentral:

http://biocloudcentral.org

then follow the instructions in the guide to connect using NX (section 2.3):

https://github.com/chapmanb/cloudbiolinux/blob/master/doc/intro/gettingStarted_CloudBioLinux.pdf?raw=true

Hope this helps,
Brad

[Purawat, Shweta]

Thank you Brad, this looks helpful.

I will follow the instructions and let you know about the status.

Best Regards,

Shweta

[Brad Chapman]

Shweta;

> I am able to access Graphically (GUI) the instance built with the
> cloudbiolinux image (ami-cb5419a2).

Great, glad to hear everything is working smoothly.

> Kindly let me know the version of cloudbiolinux on this image. Also what is
> the command to use to find cloudbiolinux version.

CloudBioLinux isn't versioned in this sense. It's rather a toolkit to
install a set of software, so the individual versions of software tools
are what the critical part. We just label the AMI build description with
the date. So that AMI is:

CloudBioLinux Ubuntu 13.04 2013-08-28 (ami-cb5419a2)

This page is a useful way to browse the AMIs:

http://thecloudmarket.com/search?search_term=cloudbiolinux&order=updated_at%20desc1

Hope that helps,
Brad

[Purawat, Shweta]

Thank you Brad for the information. 

I have a another question related to disk space. Though the volume of the instance built with image ami-cb5419a2 is 40 GB on EC2 console but when I am checking available disk space I see a /dev/xvdb size 394G. What does /dev/xvdb corresponds to ? Is 394GB also part of the instance ? Will it cost to us?  

~$ df -ah

Filesystem      Size  Used Avail Use% Mounted on

/dev/xvda1       40G   37G  1.3G  97% /

proc               0     0     0    - /proc

sysfs              0     0     0    - /sys

none            4.0K     0  4.0K   0% /sys/fs/cgroup

none               0     0     0    - /sys/fs/fuse/connections

none               0     0     0    - /sys/kernel/debug

none               0     0     0    - /sys/kernel/security

udev            1.9G   12K  1.9G   1% /dev

devpts             0     0     0    - /dev/pts

tmpfs           375M  668K  375M   1% /run

none            5.0M     0  5.0M   0% /run/lock

none            1.9G     0  1.9G   0% /run/shm

none            100M  4.0K  100M   1% /run/user

/dev/xvdb       394G  203M  374G   1% /mnt

binfmt_misc        0     0     0    - /proc/sys/fs/binfmt_misc

rpc_pipefs         0     0     0    - /run/rpc_pipefs

nfsd               0     0     0    - /proc/fs/nfsd

Thank you,

Best Regards,

Shweta 

[Brad Chapman]

Shweta;

> I have a another question related to disk space. Though the volume of the
> instance built with image ami-cb5419a2 is 40 GB on EC2 console but when I
> am checking available disk space I see a /dev/xvdb size 394G. What does
> /dev/xvdb corresponds to ? Is 394GB also part of the instance ? Will it
> cost to us?

That's the ephemeral/temporary space Amazon allocates with each
instance. It's local to the machine and not EBS, so is not persisted
when the system stops. It's useful for writing temporary files and does
not cost any extra:

http://superuser.com/questions/485360/large-volume-at-mnt-on-aws-instance

Hope this helps,
Brad

[Purawat, Shweta]

Hello Brad,

This is regarding Virtual Desktop access to the instance built with the cloudbiolinux image (ami-cb5419a2). The Nomachine client crashes as soon as it loads GNOME virtual desktop.

The instance type is m1.medium. I am using Nomachine 4.0 for Mac OS X.

Have you came across this issue? What could be the potential reason? Please let me know if you need any other details from my side.

Thank you,

Best Regards,

Shweta