Comment 3 for bug 1588888

Note that we don't want to put the migration.status in the os-migrations api-ref docs because we want to avoid codifying the migration status in the API until we have an actual state machine for migrations. The migration.status today is really just meant to be informative and client applications shouldn't base logic off of the value.