Hey all, During the summit session on the the VMWare driver roadmap, a topic of validating the passed configuration prior to starting services came up (see [1] for more detail on how it's connected to that specific topic).
Several ideas were thrown around during the session mostly documented in [1]. There are a few more cases when something like this could be useful (see bug [2] and related patch [3]), and I was wondering if a slightly different approach might be useful. For example use an already existing validation hook in the service class [4] to call into a validation framework that will potentially stop the service with proper logging/notifications. The obvious benefit would be that there is no pre-run required from the user, and the danger of running a misconfigured stack is smaller. Since there is already a blueprint raised based on the etherpad [1]- I am bringing this up here so that we can agree on the approach, before raising another one to solve the same problem. Thanks, Nikola [1] https://etherpad.openstack.org/p/T4tQMQf5uS [2] https://bugs.launchpad.net/nova/+bug/1243614 [3] https://review.openstack.org/#/c/53303/ [4] http://git.openstack.org/cgit/openstack/nova/tree/nova/service.py#n283 _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
