...
3. You are now logged in and will then be presented with the Message Of The Day and a shell prompt:
| No Format |
|---|
----------------------------
Cloud Image Helper Scripts
----------------------------
To enable automatic updates please run:
/usr/local/bin/enableAutoUpdate
To install the latest OpenStack tools please run:
/usr/local/bin/installOpenStackTools
To use the local software update proxy please run:
/usr/local/bin/localSUS
To remove this message from your message of the day please run:
sudo rm /etc/motd
ubuntu@<your_instance_name>:~$ |
----------------------------
...
Convert OpenStack private key to puTTY compatible key
Launch PuTTYGen, installed as part of the PuTTY suite.
Click Conversions from the “PuTTY Key Generator” menu and select Import key.
Navigate to the OpenStack private key (*.pem) used in the instance you would like to connect to and click “Open”.
Under Actions / Save the generated key, select Save private key.
Choose an optional passphrase to protect the private key.
Save the private key to the desktop as a *.ppk.
Connect to instance with PuTTY
Open the main PuTTY application.
Enter the remote server IP address under the “Session” category in left-hand panel.
Navigate to the “Connection” category, then “Data”.
Under Login details, enter the username to log in with. For ubuntu instances on the Rapid Access Cloud, the default is
ubuntu.In the “Connection” category in the left-hand menu, select “SSH” and then “Auth”.
Click “Browse…” under “Authentication parameters / Private key file” for authentication.
Locate the *.ppk private key you generated above and click “Open”.
Navigate back to the “Session” category to name the session and then click “Save”.
Click “Open” to log into the remote server with key pair authentication.
...
Log-in to the Rapid Access Cloud dashboard at https://cloud.cybera.ca.
In the left-hand panel under “Compute”, click “Volumes”.
Click the Action drop-down button on the right-hand side and select “Manage Attachments”.
Under “Attach to Instance” select the instance the volume is be attached to, then click the blue “Attach Volume” button.
After a few moments, the volume will be attached. Take note of the “Attached to” column on the summary screen, it will list where it is attached like “/dev/sdc”.
...
Use a volume
...
Log into your instance via ssh.
Format the volume:
$ sudo mkfs.ext4 /dev/sdc
Note: attached volumes will typically be assigned device names in sequential order (i.e. /dev/sdc, /dev/sdd, /dev/sde, etc.) List all disks from within the instance with
$ sudo fdisk -l
...
/dev/sda and /dev/sdb are the system volumes that make up the instance.
3. Create a mount point for the volume:
$ sudo mkdir /mnt/<mount_point_name>
4. Mount the volume device to the mount point:
$ sudo mount /dev/sdc /mnt/<mount_point_name>
5. Permissions may need to be changed on the new volume, as they are initially set to root:
$ sudo chown ubuntu:ubuntu /mnt/<mount_point_name>
...
...
Backups
The Cybera Rapid Access Cloud is offered on a best-effort basis and it is the users’ responsibility to ensure appropriate backups of all their data are made. While Cybera’s record for uptime and data-loss is very good, we strongly encourage all of our users to ensure regular backups are made.
Snapshots
Snapshots are point-in-time copies of your instances. You can snapshot your instance and then either download that snapshot as a backup or use that snapshot as a “cookie cutter” template to build new instances based off of it. This has the advantage that you will not have to reconfigure your virtual machine after launching from the snapshot, as opposed to launching from the image. Also, you can use this to resize your instance: if you want your instance to have different resources assigned to it (e.g. CPU or RAM) you can re-launch from the snapshot according to your preferred configuration (note that the root disk cannot be smaller than in the original instance).
To snapshot your instance:
Log-in to the Rapid Access Cloud dashboard at https://cloud.cybera.ca.
In the left-hand panel under “Compute”, click “Instances”
For the instance you want to snapshot, make sure it is in a shut-off state.
Click on the “Create snapshot” button.
Select a name to save the snapshot as
OpenStack will then navigate to the Images section. The snapshotting process can take considerable time depending on the size of the instance.
You should verify that the snapshotting process has worked following completion. Check the size of the snapshot as it should be at least several hundred MB in size. Also consider test launching an instance from the snapshot in order to ensure the process concluded successfully.
...
Object storage
...
Users may also use the Object Storage service to back-up their data. See this document for more information.
...
Conclusion
Congratulations! You now have enough knowledge of Cybera’s Rapid Access Cloud and OpenStack to deploy instances, manage networking and data on and amongst them. This encompasses a majority of use cases for cloud and may very well be enough for your needs. However, the true potential of cloud architecture is realized once you move beyond manual creation and automate the creation and destruction of instances, while maintaining data integrity in volumes. These topics and more are covered in the Advanced Guide.