| 2016-07-08 07:05:55 |
PanFengyun |
description |
1. Magnum use the get_removal_nodes() of scale_manager.py to get the nodes which need to be removed, but the get_removal_nodes() can not get the nodes which has pods or containers.
So Magnum just remove the nodes which has not pods or containers.
2. I get "Magnum can remove the nodes which has pods or containers" from the following URL:
http://docs.openstack.org/developer/magnum/dev/dev-quickstart.html
----
If you choose to reduce the node_count, magnum will first try to remove empty nodes with no pods running on them. If you reduce node_count by more than the number of empty nodes, magnum must remove nodes that have running pods on them. This action will delete those pods. We strongly recommend using a replication controller before reducing the node_count so any removed pods can be automatically recovered on your remaining nodes.
----
1 is conflict to 2.
Is the get_removal_nodes() of scale_manager.py wrong? or... |
1. Magnum use the get_removal_nodes() of scale_manager.py to get the nodes which need to be removed, but the get_removal_nodes() can not get the nodes which has pods or containers.
So Magnum just remove the nodes which has not pods or containers.
2. I get "Magnum can remove the nodes which has pods or containers" from the following URL:
http://docs.openstack.org/developer/magnum/dev/dev-quickstart.html
----
If you choose to reduce the node_count, magnum will first try to remove empty nodes with no pods running on them. If you reduce node_count by more than the number of empty nodes, magnum must remove nodes that have running pods on them. This action will delete those pods. We strongly recommend using a replication controller before reducing the node_count so any removed pods can be automatically recovered on your remaining nodes.
----
1 is conflict to 2.
Is the get_removal_nodes() of scale_manager.py wrong? or...
Should we let get_removal_nodes() get nodes without checking pods? |
|
