cc_staff
44
edits
VM Best Practices: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(First wack at a best practices document) |
mNo edit summary |
||
| Line 9: | Line 9: | ||
=== Maximum volumes per VM === | === Maximum volumes per VM === | ||
'''Avoid attaching more than three volumes to a VM'''. | '''Avoid attaching more than three volumes to a VM'''. This has been observed to lead to kernel timeouts which can affect any disk operations on those volumes and may have a cascading effect, and can render the VM effectively inoperative. While using a data volume is advisable (see above), use only one and you can carve it up into multiple filesystems inside your VM, and expand it as necessary. | ||
This has been observed on Arbutus (west.cloud.computecanada.ca) by multiple users, although it may be somewhat dependent on volume size. In one case, 3 x 100GB volumes attached to a p4-6gb VM caused kernel timeouts whenever disk operations of any magnitude were attempted. It was very difficult to copy more than 500MB of data between two filesystems, for example. | |||
As of 27 November 2017 it is being tested on East Cloud (east.cloud.computecanada.ca). | |||