Make `--teardown none` the default behavior

[Flavio Percoco]

This can be seen as a bug, feature, or enhancement request.

The current default behavior for oooq is to teardown the undercloud every time it's run. Unfortunately, this is not an intuitive behavior and it does not reflect one of the features of the tool it's using (ansible), which is being idempotent.

I believe the default behavior should be to not destroy the undercloud, which is safer and more intuitive. That means, oooq should not treat undercloud deployments as being completely ephemeral. I've been bitten by this and other folks have too.

One more practical example for this is having to re-run quickstart to add more nodes to the undercloud, run a playbook again (or run a new playbook because one forgot to add it in the first run), etc.

I'm filing this to start the discussion and hopefully come to a wider consensus of whether this should or shouldn't be changed.

[Ronelle Landy (rlandy)]

Moving this to RFE.
Suggestion to offer an interactive prompt to get around the defaults. (like dev-mode)

[John Trowbridge (trown)]

moved to tripleo launchpad with quickstart tag

The problem here is that there is not really a good default. In the past, we had a "teardown none" type default behavior, but this can lead to a very bad new user experience. The user could get "stuck" with a bad configuration from the first run, and fail to be able to fix things in subsequent runs because all of the bad configuration persisted.

I think there are a couple of other defaults we have that are like this as well, and it would be cool to require them instead. To keep things relatively simple for someone just getting started, we could have an interactive prompt if nothing was specified for a required option. This prompt could provide some explanation of the tradeoffs, and provide the option string at the end to skip the prompt in the future.