-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/build: Migrate to new network storage on MacStadium #33155
Comments
The new NFS-based storage in the new MacStadium datacenter is now available. I've been copying the vm base images ( Once these are up, we should be able to make a change to We'll probably want to roll this out on a night or a weekend to test. We should be able to verify by manually starting a VM for each image with the same command that makemac uses. The final step will be to move the bastion VM box as well. I haven't yet done enough research to determine the necessary steps there yet, but vSphere's snapshotting functionality seems solid. |
Change https://golang.org/cl/188219 mentions this issue: |
I was able to move the dns host / bastion / makemac vm to the new storage with vSphere's live migration tool. I cloned all the base VMs to the new storage, and ensured that a snapshot ran on each one for use by After https://golang.org/cl/188219, we should be able to restart makemac and see if the new VMs it creates (which it does regularly) work correctly. Once we've restarted all VMs on the new storage, we can unmount the old datastore in vSphere and allow it to be decommissioned. |
MacStadium is migrating off the current datastore. As part of the transition, we copied our base images to the new storage, adding _nfs as the suffix. The new images were snapshotted to allow for copy on write. New base image names were suffixed with _nfs to accommodate the migration. The new storage device was named GGLGLN-A-001-STV1 by MacStadium. Updated vmware-notes.txt to include manual instructions for a test run of this latest change. The VM started and successfully connected to the coordinator. Updates golang/go#33155 Change-Id: I69976ebc6faa4f95a0aefd4d2e4c8d6a5bcf8a0f Reviewed-on: https://go-review.googlesource.com/c/build/+/188219 Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
A new version of makemac has been deployed, using the new datastore. All running VMs are now on the new datastore. I'm working on deprovisioning the old datastore, as our hosting provider has given us a surprise deadline of August 9th. |
The old datastore (Pure1-1) is unmounted. Our hosting provider is working to remove it. |
Has this work been completed? |
Yes! The migration has been completed, and the old storage has been decommissioned. There are still some references to it in vSphere that I cannot figure out how to get rid of, but it does not seem to be causing any issue. |
MacStadium is migrating off the current datastore. As part of the transition, we copied our base images to the new storage, adding _nfs as the suffix. The new images were snapshotted to allow for copy on write. New base image names were suffixed with _nfs to accommodate the migration. The new storage device was named GGLGLN-A-001-STV1 by MacStadium. Updated vmware-notes.txt to include manual instructions for a test run of this latest change. The VM started and successfully connected to the coordinator. Updates golang/go#33155 Change-Id: I69976ebc6faa4f95a0aefd4d2e4c8d6a5bcf8a0f Reviewed-on: https://go-review.googlesource.com/c/build/+/188219 Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
MacStadium is deprecating the old storage SAN for a new NFS based storage. We should be able to automate moving the data over in
govc
, then updatingmakemac
to use the new vSphere datastore name.The text was updated successfully, but these errors were encountered: