Activity log for bug #1248022
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2013-11-05 03:36:46 | Mark McLoughlin | bug | added bug | ||
2013-11-05 03:42:58 | Mark McLoughlin | tags | baremetal | ||
2013-11-05 03:43:22 | Mark McLoughlin | nova: status | New | Triaged | |
2013-11-05 03:43:25 | Mark McLoughlin | nova: importance | Undecided | High | |
2013-11-07 03:39:07 | Qiu Yu | bug | added subscriber Qiu Yu | ||
2014-07-10 17:46:53 | Joe Gordon | bug task added | ironic | ||
2014-07-22 16:41:52 | aeva black | ironic: status | New | Triaged | |
2014-07-22 16:41:57 | aeva black | ironic: importance | Undecided | Medium | |
2014-07-22 16:43:07 | aeva black | tags | baremetal | baremetal nova-driver | |
2014-09-05 09:05:30 | Dmitry Tantsur | ironic: milestone | juno-rc1 | ||
2014-09-11 12:36:52 | Dmitry Tantsur | summary | Nova scheduler not updated immediately when a baremetal node is added | Nova scheduler not updated immediately when a baremetal node is added or removed | |
2014-09-11 12:38:18 | Dmitry Tantsur | description | In compute manager, the update_available_resource() periodic task is responsible for updating the scheduler's knowledge of baremetal nodes: @periodic_task.periodic_task def update_available_resource(self, context): ... nodenames = set(self.driver.get_available_nodes()) for nodename in nodenames: rt = self._get_resource_tracker(nodename) rt.update_available_resource(context) update_available_resource() is also called at service startup This means that you have to wait up to 60 seconds for a node to become available | With the Ironic driver, if a baremetal node is added/deleted, it is not removed from pool of available resources until the next run of update_available_resource(). During this window, the scheduler may continue to attempt to schedule instances on it (when deleted), or report NoValidHosts (when added) leading to unnecessary failures and scheduling retries. In compute manager, the update_available_resource() periodic task is responsible for updating the scheduler's knowledge of baremetal nodes: @periodic_task.periodic_task def update_available_resource(self, context): ... nodenames = set(self.driver.get_available_nodes()) for nodename in nodenames: rt = self._get_resource_tracker(nodename) rt.update_available_resource(context) update_available_resource() is also called at service startup This means that you have to wait up to 60 seconds for a node to become available/no longer available. | |
2014-09-11 12:38:26 | Dmitry Tantsur | tags | baremetal nova-driver | ironic nova-driver | |
2014-09-13 01:05:52 | aeva black | ironic: milestone | juno-rc1 | ||
2015-03-23 12:00:57 | Davanum Srinivas (DIMS) | nova: importance | High | Medium | |
2015-03-30 16:28:21 | Sean Dague | nova: status | Triaged | Invalid | |
2015-03-30 16:28:49 | Sean Dague | nova: status | Invalid | Opinion | |
2015-05-22 09:27:31 | Zhenguo Niu | bug | added subscriber Zhenguo Niu | ||
2015-10-30 15:38:11 | milan k | ironic: assignee | milan k (vetrisko) | ||
2015-11-07 14:28:18 | milan k | attachment added | simple watchdog implementation preview https://bugs.launchpad.net/ironic/+bug/1248022/+attachment/4514750/+files/watchdog.py | ||
2015-11-09 12:50:29 | milan k | ironic: assignee | milan k (vetrisko) | ||
2016-04-28 16:54:18 | Marc Aubry | bug | added subscriber Marc Aubry | ||
2017-04-01 06:16:15 | Seamanhanshan | bug | added subscriber Seamanhanshan |