vSphere datastore migration CPI timeout section out of date

[kpschuck]

Per the release notes , the timeout issue has been fixed since v20 of the vSphere CPI. In addition, the link to the KB article is broken, but this section should probably be removed all-together.

See vsphere/vsphere_migrate_datastore.html.md.erb

Step 3: Modify CPI Timeout Value (Optional)

The default timeout for the BOSH CPI is 60 minutes. When performing a datastore migration, BOSH must copy all of the data from the old disks to the new disks within this time limit. In general, most copy operations should fit within this time limit, but it ultimately depends on the hardware in your deployment and the size of your existing persistent disks.

To determine whether 60 minutes is sufficient for the datastore migration, estimate how long it takes to copy 100 GB of data. Then, based on the size of your persistent disks, determine whether 60 minutes is sufficient time to copy that amount of data.

If you have previously encountered out of sync errors when modifying your PCF deployment, you should increase the timeout value of the CPI before migrating the datastores.

To modify the default BOSH CPI timeout, follow the instructions in the following KB article.

• How to increase timeout on BOSH CPI command calls

For more information about resolving the error after migrating your datastore, see After the Migration.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[pspinrad]

Thanks @kpschuck -- just raised issue on #sme-pcf-vsphere Pivotal Slack