yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

If I do the following:

nova server-group-create --policy affinity affinitygroup
nova boot --flavor=1 --image=cirros-0.3.1-x86_64-uec --hint group=<group_uuid> cirros0
nova resize cirros0 2

The cirros0 server will be resized but when the scheduler runs it
doesn't take into account the scheduling policy of the server group.

I think the same would be true if we migrate the server.

Lastly, when doing migration/evacuation and the user has specified the
compute node we might want to validate the choice against the group
policy.  For emergencies we might want to allow policy violation with a
"--force" option or something.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

- If we try to resize/migrate a server that is part of a server group, the
- server group policy should be applied when scheduling the server.
+ If I do the following:
+ 
+ nova server-group-create --policy affinity affinitygroup
+ nova boot --flavor=1 --image=cirros-0.3.1-x86_64-uec --hint group=<group_uuid> cirros0
+ nova resize cirros0 2
+ 
+ The cirros0 server will be resized but when the scheduler runs it
+ doesn't take into account the scheduling policy of the server group.
+ 
+ I think the same would be true if we migrate the server.
+ 
+ Lastly, when doing migration/evacuation and the user has specified the
+ compute node we might want to validate the choice against the group
+ policy.  For emergencies we might want to allow policy violation with a
+ "--force" option or something.

-- 
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/1298513

Title:
  nova server group policy should be applied when resizing/migrating
  server

Status in OpenStack Compute (Nova):
  New

Bug description:
  If I do the following:

  nova server-group-create --policy affinity affinitygroup
  nova boot --flavor=1 --image=cirros-0.3.1-x86_64-uec --hint group=<group_uuid> cirros0
  nova resize cirros0 2

  The cirros0 server will be resized but when the scheduler runs it
  doesn't take into account the scheduling policy of the server group.

  I think the same would be true if we migrate the server.

  Lastly, when doing migration/evacuation and the user has specified the
  compute node we might want to validate the choice against the group
  policy.  For emergencies we might want to allow policy violation with
  a "--force" option or something.

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