In the OSP 16 to 17 upgrade there will be no interim containers to facilitate the database migrations like we did for 13 to 16. The database migrations for OSP 17.x must be able to migrate directly from OSP 16.x.
I think this is going to be a dev task, so assigning it to neutron DFG. If we are sure no DB changes are going to there, and we need to directly test 16 -> 17, we will do that. but NFV FFU jobs from 16 -> 17 are going to be later ie most probably by 17.1 timelines.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days