All the VM information is stored in the instances table. This includes all the time related field like scheduled_at, launched_at etc.
After upgrading to Juno, I have noticed that my 'scheduled_at' field is not getting reflected at all in the database. I do see my VMs being spawned and running just fine. However, the 'launched_at' time does get reflected rightly. MariaDB [nova]> select created_at, deleted_at, host,scheduled_at, launched_at from instances; +---------------------+---------------------+-----------------------+--------------+---------------------+ | created_at | deleted_at | host | scheduled_at | launched_at | +---------------------+---------------------+-----------------------+--------------+---------------------+ | 2015-03-09 20:00:41 | 2015-03-10 17:12:11 | localhost | NULL | 2015-03-09 20:01:30 | | 2015-03-11 05:53:13 | NULL | localhost | NULL | 2015-03-18 19:48:12 | Can anyone let me know if this is a genuine issue or have there been a recent change in regard to updating this field ? I am basically trying to find as to how long a particular VM is running on a given host. I was using the current time - scheduled time for the same. Is there a better way to get this value ? Regards, __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
