Dear TSC, We have encountered some issues on the openstack environment configuration for some projects and it could not be resolved within the project scope. So I have to escalate it to TSC to look for a solution.
Some OPNFV project requires *dedicated* configuration on *common* services. But the environment deployed by the installers may not always come with a valid configuration. For example, doctor project requires `notifier://?topic=alarm.all` in ceilometer event pipeline configuration. But the default deployed environment by fuel does not include this configuration. There has been a long debates between the two teams on where the modification should be made [1][2]. The contradiction is that if we enable this notifier topic, doctor will work, but nobody can guarantee that other projects are not affected. OPNFV is targeting to deliver a "de facto standard open source NFV platform for the industry" [3]. The platform on software part includes not only the services installed but also a common configuration for all projects to run. So the first step should be working out a *harmonized configuration** set* which will allow all existing projects to run normally. Then it can be used to validate the deployed environment from each installer. I'm sincerely hoping TSC can help to resolve this issue and lead OPNFV to a success. [1] https://gerrit.opnfv.org/gerrit/#/c/18285/ [2] https://jira.opnfv.org/browse/FUEL-159 [3] https://wiki.opnfv.org/ -- Yujun Zhang
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
