Add a configuration parameter to enable auto confirm for cold migration

[Guangya Liu (Jay Lau)]

http://<email address hidden>/msg13163.html
    >>> For resize, we need to confirm, as we want to give end user an opportunity
    >>> to rollback.
    >>>
    >>> The problem is cold migration, because cold migration and resize share
    >>> same code path, so once I submit a cold migration request and after the cold
    >>> migration finished, the VM will goes to verify_resize state, and I need to
    >>> confirm resize. I felt a bit confused by this, why do I need to verify
    >>> resize for a cold migration operation? Why not reset the VM to original
    >>> state directly after cold migration?
    >
    > I think the idea was allow users/admins to check everything went OK,
    > and only delete the original VM when the have confirmed the move went
    > OK.
    >
    > I thought there was an auto_confirm setting. Maybe you want
    > auto_confirm cold migrate, but not auto_confirm resize?

    I suppose we could add an API parameter to auto-confirm these things.
    That's probably a good compromise.

OK, will use auto-confirm to handle this.

[Matt Riedemann (mriedem)]

This isn't a bug, it would be a new blueprint since it's a new feature.

[Guangya Liu (Jay Lau) (jay-lau-513)]

A bp was logged to trace it. https://blueprints.launchpad.net/nova/+spec/auto-confirm-cold-migration