I think the post install script of the RPM/DEB package starts the service *right after* a package has been installed. While this might be ok for other services CentOS/Ubuntu ship (Apache/MySQL/etc), I'm not sure this works for us as before nova-api is started we need to make sure that:
1. nova-api.conf with correct settings is there
2. nova-manage db sync has been executed
If those requirements aren't satisfied, we may end up with nova-api either simply configured incorrectly (e.g. using a default sqlite database) or working in parallel with db sync, in which case we can't guarantee migration scripts will be applied correctly.
I think the post install script of the RPM/DEB package starts the service *right after* a package has been installed. While this might be ok for other services CentOS/Ubuntu ship (Apache/MySQL/etc), I'm not sure this works for us as before nova-api is started we need to make sure that:
1. nova-api.conf with correct settings is there
2. nova-manage db sync has been executed
If those requirements aren't satisfied, we may end up with nova-api either simply configured incorrectly (e.g. using a default sqlite database) or working in parallel with db sync, in which case we can't guarantee migration scripts will be applied correctly.