Page History

...

• M1 class flavors are General Purpose Instances. This family provides a balance of compute, memory, and network resources, and it is a good choice for many applications. 

  Flavor	VCPUs	Root Disk (GB)	RAM (MB)	Swap (MB)
  m1.tiny	1	5	512	512
  m1.micro	1	5	1,024	1,024
  m1.small	2	20	2,048	2,048
  m1.medium	2	40	4,096	4,096
  m1.large	4	40	8,192	4,096
  m1.xlarge	8	40	16,384	4,096

  
  

• G1 instances are intended for general-purpose GPU compute applications. Use cases include machine learning, rendering, and other server-side GPU compute workloads. (see GPU-Enabled Instances for more on how to launch GPU instances.) 

  Flavor	VCPUs	Root Disk (GB)	RAM (MB)	Swap (MB)
  g1.medium.auto-destruct	8	40	8,192	4,096
  g1.large.auto-destruct	8	40	32,768	4,096
  g1.xlarge.auto-destruct	16	40	32,768	4,096

  
  

Resizing instances

Currently the option to resize instances (change flavor) is not functional in RAC. A workaround to to snapshot an instance and then create a new instance, of the desired flavor, based on the snapshot.

Accessing instances

Having an instance up and running is one thing, and perhaps just a single Linux ‘sandbox’ to run some code is all that is needed, however the real power of computers, virtual or otherwise, is in connectivity, and that means networks. The instances in the Rapid Access Cloud can be connected to and accessed in a variety of ways, permitting users to create an environment with multiple instances networked together in the same way a bare-metal environment can be built, but in this case with virtual machines providing the routing, switching and other network functions along with the expected servers running applications on top of operating systems like Linux and Windows.on top of operating systems like Linux and Windows. In the RAC web client there is an option to access your instance via a web console. Windows instances can be accessed with the console. Linux instances will prompt for a password and can not be accessed via the console without first logging into the instance (SSH) to configure a password. For this reason it is recommended to only use SSH and a private key to access a Linux instances. Create a keypair before creating a Linux instance then when creating a Linux instance, assign the key for access. See this page for instructions on how to create a key pair.

IP addresses 

Once an instance is provisioned, it is automatically given two addresses: a private IPv4 address, and a public IPv6 address.

...

1. Log-in to the Rapid Access Cloud dashboard at https://cloud.cybera.ca.

2. In the left-hand panel under “Compute”, click “Instances”.

3. Click the Action drop-down button on the right-hand side and select “Associate Floating IP”.

4. Click on the “+” sign next to “Select an IP address”.

5. There is only one pool of addresses available (novaPublic) and the quota shows only one IP address from that pool, so simply click “Allocate IP”.

6. After the IP address has been allocated, click the “Associate” button the the right hand side. Under the Instances summary, your Instance should now have three IP addresses, including a publicly accessible IPv4 address.

...

To make IPv6 addresses more friendly, instances are given an automated DNS name that maps to your IPv6 address and if applicable your floating IP address. The autogenerated domain can be found on your instance's details page under the Metadata section. (eg. 12345.yyc.cybera.ca)

From Linux, UNIX, or BSD (including

...

macOS)

The simplest way to use ssh from these operating systems is:

...

Description: <your_description>

Volume Source: No source, empty volume

Type: LVM

Size (GB): 25

Availability Zone: (Any availability zone)

...