|
Yujun,
Thanks for raising this issue. This is a longer term issue to
solve but for now I've added it as a topic for to the Infra WG
weekly meeting. I'm hoping to solve this for the D release and
been tasked by the TSC to help drive this effort. Please join
the Infra WG meeting to provide your input.
On 09/05/2016 12:11 AM, Yujun Zhang
wrote:
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.
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--
Jack Morgan
OPNFV Pharos Intel Lab
|
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
