VM Best Practices: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Marked this version for translation)
No edit summary
Line 1: Line 1:
<translate>
<translate>
<!--T:1-->
<!--T:1-->
This page is to provide some guidance based on user experiences with Compute Canada's cloud instances.  Your mileage may vary.
This page provides some guidance based on user experiences with Compute Canada's cloud instances.  Your mileage may vary.


== Volumes == <!--T:2-->
== Volumes == <!--T:2-->
Line 8: Line 8:


<!--T:4-->
<!--T:4-->
It is very difficult to expand a root volume, so for any VM which does not have bounded storage requirements, '''consider creating a second volume for data'''.  If more space is needed, and your allocation has enough remaining volume storage, it is fairly straightforward to expand the data volume using OpenStack and then expanding the logical volume, if any, and filesystem within your VM.
It is very difficult to expand a root volume, so for any VM which does not have bounded storage requirements, '''consider creating a second volume for data'''.  If more space is needed, and your allocation has enough remaining volume storage, it is fairly straightforward to expand the data volume using OpenStack and then to expand the logical volume, if any, and filesystem within your VM.


=== Maximum volumes per VM === <!--T:5-->
=== Maximum volumes per VM === <!--T:5-->
rsnt_translations
56,430

edits

Navigation menu