yahoo-eng-team team mailing list archive

[Jay Lau <jay.lau.513@xxxxxxxxx>]

Public bug reported:

http://www.mail-archive.com/openstack-dev@xxxxxxxxxxxxxxxxxxx/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.

** Affects: nova
     Importance: Undecided
     Assignee: Jay Lau (jay-lau-513)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Jay Lau (jay-lau-513)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1267386

Title:
  Add a configuration parameter to enable auto confirm for cold
  migration

Status in OpenStack Compute (Nova):
  New

Bug description:
  http://www.mail-archive.com/openstack-dev@xxxxxxxxxxxxxxxxxxx/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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1267386/+subscriptions