cc_staff
12
edits
Arbutus Migration Guide: Difference between revisions
Jump to navigation
Jump to search
added some estimated times for copying volumes
(added clarifications on volumes greater than 150GB) |
(added some estimated times for copying volumes) |
||
| Line 43: | Line 43: | ||
#: <code>openstack security group list</code> to list the available security groups. | #: <code>openstack security group list</code> to list the available security groups. | ||
#: <code>openstack security group rule list</code> to view the rules in the group. | #: <code>openstack security group rule list</code> to view the rules in the group. | ||
# Plan an outage window. Generally, shutting down services and then shutting down the instance is the best way to avoid corrupt or inconsistent data after the migration. Smaller volumes can be copied over fairly quickly, | # Plan an outage window. Generally, shutting down services and then shutting down the instance is the best way to avoid corrupt or inconsistent data after the migration. Smaller volumes can be copied over fairly quickly, e.g. a 10GB volume will copy over in less than 5 minutes, but larger volumes, e.g. 100GB can take 30 to 40 minutes. Plan for this. Additionally, floating IP addresses will change, so ensure the TTL of your DNS records is set to a small value so that the changes propagate as quickly as possible. | ||
There are three general migration scenarios to consider. | There are three general migration scenarios to consider. | ||