We talked about this one during the openstack sync call last week. The consensus was that the goal was to help tell when a system was coming up from a cold boot (e.g. the system was restarted, not the agent or the service). The idea is that if the cloud were to shut down it was important to know it was coming up from a cold start situation. The discussion was to leverage the start hook as a promised "first hook on reboot, as long as not in a series-upgrade or other defined situation". In this way logic could be handled on the start hook to help manage this cold start situation.
We agreed that the openstack team would put together some defined scenarios they want to make sure are covered and we'd make sure that this start hook on reboot would cover those in a sufficient manner and look at adding to the next cycle roadmap.
We talked about this one during the openstack sync call last week. The consensus was that the goal was to help tell when a system was coming up from a cold boot (e.g. the system was restarted, not the agent or the service). The idea is that if the cloud were to shut down it was important to know it was coming up from a cold start situation. The discussion was to leverage the start hook as a promised "first hook on reboot, as long as not in a series-upgrade or other defined situation". In this way logic could be handled on the start hook to help manage this cold start situation.
We agreed that the openstack team would put together some defined scenarios they want to make sure are covered and we'd make sure that this start hook on reboot would cover those in a sufficient manner and look at adding to the next cycle roadmap.