Comment 4 for bug 1708115

Hello, as we discussed I spent some time looking here today. My current proposal is:

* continue to use the tripleo_upgrade_node.sh to essentially replace the upgrade_tasks (i.e. stop the things, as we have started adding already).

* Add execution of the ansible playbook into the upgrade-non-controller.sh. Shardy reviews, esp I96ec09bc788836584c4b39dcce5bf9b80e914c71 makes it so we can get the deploy-steps as stack output. We can then use the config download to execute this on the undercloud (where upgrade-non-controller.sh is running anyway).

Relevant reviews here are https://review.openstack.org/490847 (download and execute the deploy-steps) and https://review.openstack.org/490852 so we can specify a named path.

An alternative we might consider is to get actual upgrade_tasks instead of using the tripleo_upgrade_node.sh, however the biggest obstacle to that right now is we'd need to re-write the upgrade_tasks and break the current composable-steps upgrade workflow. I proposed https://review.openstack.org/490848 for the discussion anyway.