yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

So that behaviour is as designed.

Disabled only stops new instances landing on that host. You can still
manage your existing instances. The intent is to allow an admin to
migrate or live-migrate instances off the host.

I think we probably want some extra level of disabled to signal that
existing VMs should not bar allowed to have any action performed.

FWIW stopping nova-compute might be what you want to do. That would stop
instance from running again. In fact if you configure nova correctly,
when you start nova-compute it will start back up only the VMs that were
running when it shutdown.

** Changed in: nova
   Importance: Undecided => Wishlist

** Changed in: nova
       Status: Confirmed => Opinion

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

Title:
  It´s not possible to disable the nova compute service on one compute
  node

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  I have multiple nova compute nodes and for maintenance reasons I want
  to disable one of them.

  Migration of a virtual machine is not possible, due to bug
  https://bugs.launchpad.net/cinder/+bug/1348811, so it would be ok, if
  it is not possible, to start a machine on that compute node.

  I stopped virtual machine "foo" on compute node "bar"
  $ nova stop 86db11f7-a1e4-4be0-880c-0720cd24c3aa

  disabled nova-compute service
  $ sudo nova-manage service disable bar nova-compute

  and checked it with 
  $ sudo nova-manage service list --host bar
  ------------------------------------------
  Binary           Host                                 Zone             Status     State Updated_At
  nova-compute     bar                            Cluster X        disabled   :-)   2015-08-10 12:29:10
  ------------------------------------------

  Expected result:
  VM foo is not able to run on that host

  Actual result:
  VM foo is able to run on that host

  $ nova start 86db11f7-a1e4-4be0-880c-0720cd24c3aa
  The machine is running 

  I tested, if its possible to create new virtual machines on that compute node bar with the disabled nova-compute service
  $ nova boot --image "c196615d-d3ed-49d7-8bc6-c65f8360aa02" --flavor m1.smaller --nic net-id=6a38402f-4a5b-4239-a683-ceb4ae220c30 --availability-zone "Cluster X":bar foo2

  This machine is also running.

  Versions:

  $ dpkg -l | grep nova
  ii  nova-common                         1:2014.1.4-0ubuntu2.1                 all          OpenStack Compute - common files
  ii  nova-compute                        1:2014.1.4-0ubuntu2.1                 all          OpenStack Compute - compute node base
  ii  nova-compute-kvm                    1:2014.1.4-0ubuntu2.1                 all          OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt                1:2014.1.4-0ubuntu2.1                 all          OpenStack Compute - compute node libvirt support
  ii  python-nova                         1:2014.1.4-0ubuntu2.1                 all          OpenStack Compute Python libraries
  ii  python-novaclient                   1:2.17.0-0ubuntu1.2                   all          client library for OpenStack Compute API

  $ dpkg -l | grep ceph
  ii  ceph-common                         0.94.1-1trusty                        amd64        common utilities to mount and interact with a ceph storage cluster
  ii  ceph-fs-common                      0.94.1-1trusty                        amd64        common utilities to mount and interact with a ceph file system
  ii  ceph-fuse                           0.94.1-1trusty                        amd64        FUSE-based client for the Ceph distributed file system
  ii  libcephfs1                          0.94.1-1trusty                        amd64        Ceph distributed file system client library
  ii  python-cephfs                       0.94.1-1trusty                        amd64        Python libraries for the Ceph libcephfs library

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