Re: AWS gp2 -> gp3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



FYI

after I moved manually most of the big volumes to gp3 at the beginning of summer, I finally get to write script that converts all the remaining volumes.

I run it for two minor regions:

ap-south-1
Migrating volume vol-0dbcb65fadcadfd56 in region ap-south-1 from gp2 to gp3...
Volume vol-0dbcb65fadcadfd56 in region ap-south-1 migrated to gp3
Migrating volume vol-0058e60aaa125e5d2 in region ap-south-1 from gp2 to gp3...
Volume vol-0058e60aaa125e5d2 in region ap-south-1 migrated to gp3
Migrating volume vol-0a105d78b59ce2c23 in region ap-south-1 from gp2 to gp3...
Volume vol-0a105d78b59ce2c23 in region ap-south-1 migrated to gp3
Migrating volume vol-0d9419cdad700549a in region ap-south-1 from gp2 to gp3...
Volume vol-0d9419cdad700549a in region ap-south-1 migrated to gp3
Migrating volume vol-0e15a552fdd51a391 in region ap-south-1 from gp2 to gp3...
Volume vol-0e15a552fdd51a391 in region ap-south-1 migrated to gp3
Migrating volume vol-07c8e6df4ad605935 in region ap-south-1 from gp2 to gp3...
Volume vol-07c8e6df4ad605935 in region ap-south-1 migrated to gp3
Migrating volume vol-0526490438425fae8 in region ap-south-1 from gp2 to gp3...
Volume vol-0526490438425fae8 in region ap-south-1 migrated to gp3

ca-central-1
Migrating volume vol-067b5f163d2320171 in region ca-central-1 from gp2 to gp3...
Volume vol-067b5f163d2320171 in region ca-central-1 migrated to gp3
Migrating volume vol-07a41964b391cbe75 in region ca-central-1 from gp2 to gp3...
Volume vol-07a41964b391cbe75 in region ca-central-1 migrated to gp3
Migrating volume vol-05fa6f0557ab1e44b in region ca-central-1 from gp2 to gp3...
Volume vol-05fa6f0557ab1e44b in region ca-central-1 migrated to gp3
Migrating volume vol-00d79ef4b4e1f92e8 in region ca-central-1 from gp2 to gp3...
Volume vol-00d79ef4b4e1f92e8 in region ca-central-1 migrated to gp3
Migrating volume vol-0712085157d0bade9 in region ca-central-1 from gp2 to gp3...
Volume vol-0712085157d0bade9 in region ca-central-1 migrated to gp3
Migrating volume vol-037fb93e199476ee1 in region ca-central-1 from gp2 to gp3...
Volume vol-037fb93e199476ee1 in region ca-central-1 migrated to gp3

But then I realized I may accidentally touched volumes that belongs to set under Fedora 39 Beta Freeze.

So I will postpone any other action till 2023-09-12. When the freeze will be over I plan to run it for all remaining regions.

The script is here https://github.com/xsuchy/fedora-infra-scripts/blob/main/gp2-to-gp3.py

-- 
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux