Reviewers:
Technical: Joan Francesc Gilabert Navarro
Peer: [Writer name]
QE: [name]
Is this feature fully supported or technical preview?

• Mostly fully supported: Documentation will be published on the customer portal
• Change type and migrate pool are fully supported, migrate and change type is technology preview, and may not be fully tested by GA

Does the procedural content need to be tested by QE?

• Yes: It is being tested now

Does the documentation epic need a release note in addition to the feature?

• No

What stage of the user journey are you targeting?

• *Adopt: Adoption or Greenfield feature (Early stage customer use)*

Who is your target persona?

• *OpenStack admin: Cloud Administrator*

What type of information does the user need to know in order to use the feature?

• None
• Procedures to verify that the feature has worked as expected
• Check the instances and volumes and see if they moved hosts.
• They should be able to look at the volume and see if it moved.
• Concepts that need to be explained or planning decisions that must be made before the user can perform any of these procedures: Certain prerequisites are required, such as a volume store, volume types, & the clusters ability to perform migrations.
• Known issues, limitations, or troubleshooting guidance:
• Change type and migrate pool are fully supported, migrate and change type together is technology preview.
  There is note in upstream documentation that is not correct: "Currently, the strategy will not generate both volume migration and instance migrations in the same audit. If both are requested, only volume migrations will be included in the action plan." This is no longer true.

Are there any existing upstream or internal resources that the writer can use for planning and drafting the content? Consider the situational context of the existing content. Do a Google search for any possible resources that might help.

• https://etherpad.opendev.org/p/zone_migration_volume_migration_parameters
• https://docs.openstack.org/watcher/latest/strategies/zone_migration.html

Does the content require input from multiple DFGs?

• No: Stories are not required unless the epic needs to be divided to user stories that can be delivered separately (for personal use, consider sub-tasks instead)

Does the content need to be included in any of Validated architecture (VA) guide, Planning guide, Deployment/Customization guide, Adoption/minor updates guide?

• No

(Optional) Are there any additional content improvements you can also implement for the user when documenting this goal? Consider any additional actions that might also improve content. For example, restructuring content to better suit the user story.
Possibly a demo with screenshots.

Documentation optimize for volume migration

• Create required user-focused information for volume migration for optimize
• Identify all user required information for administration, updates, use-cases, goals and best practices.