Managing your cloud resources with OpenStack: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
OpenStack is an operating system that controls hardware resources such as compute, storage and networking. It allows the creation and management of virtual machines, which act like separate individual machines, by emulation in software. This allows users complete control over their computing environment, from choosing an operating system to software installation and configuration. This flexibility facilitates diverse usage cases, from hosting websites and to create a computing cluster by configuring multiple VMs to work together. See official documentation [http://docs.openstack.org/ http://docs.openstack.org/] for more details about OpenStack.
This page describes how to perform common tasks which might be encountered while working with OpenStack.
==Working with Volumes==
==Working with Volumes==
Volumes provide storage which is not destroyed when an VM is terminated (unless explicitly told to do so). On the Compute Canada clouds volumes use Ceph storage (see [https://en.wikipedia.org/wiki/Ceph_(software) https://en.wikipedia.org/wiki/Ceph_(software)] ) which has a 3X replication factor which provides safety against hardware failure. See OpenStack documentation for further details about volumes [http://docs.openstack.org/user-guide/common/cli_manage_volumes.html http://docs.openstack.org/user-guide/common/cli_manage_volumes.html].
Volumes provide storage which is not destroyed when an VM is terminated (unless explicitly told to do so). On the Compute Canada clouds volumes use Ceph storage (see [https://en.wikipedia.org/wiki/Ceph_(software) https://en.wikipedia.org/wiki/Ceph_(software)] ) which has a 3X replication factor which provides safety against hardware failure. See OpenStack documentation for further details about volumes [http://docs.openstack.org/user-guide/common/cli_manage_volumes.html http://docs.openstack.org/user-guide/common/cli_manage_volumes.html].
Line 135: Line 139:
{{Command|qemu-img convert -f qcow2 vdisk.qcow2 -O vmdk vdisk.vmdk}}
{{Command|qemu-img convert -f qcow2 vdisk.qcow2 -O vmdk vdisk.vmdk}}


Then you can create a new vritual machine and attach the vmdk image to it see [http://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/] for detailed instructions on this.
Then you can create a new virtual machine and attach the vmdk image to it see [http://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/] for detailed instructions on this.
cc_staff
1,486

edits

Navigation menu