OPNFV,

I'd like to provide an update on our effort to define a common
configuration file. We had some good F2F discussions at the OPNFV
Plugfest and have moved to splitting our efforts into two distinct efforts:

1) POD descriptor file

The below patch is an effort to define the hardware that is actually in
a Pharos POD. We spent two hours reviewing this patch and incorporating
feedback from the community. Defining the hardware is needed for several
efforts within OPNFV, such as the Pharos Dashboard, Lab as a Service
(LAAS), CI evolution, etc. In addition, testing projects (benchmarking)
would be able to use this information to compare results. In a nutshell,
this file mostly helps lab owners provide details to POD users on what
they are offering in their POD.

The Infra WG will take this to the TSC for feedback and approval. Then
work with lab owners to create these files for each OPNFV POD in the
community. Our target is to get this done for Danube release.

https://gerrit.opnfv.org/gerrit/#/c/23727/


2)  Intended usage

After getting the OPNFV community to approve of the POD descriptor file,
we will focus on defining "intended usage" of hardware. This came out of
the discussion we had at Plugfest. For example, if we look at the
current effort[1]of installers to create a common configuration file,
the focus seems to be more on defining what will run on the hardware
provided then the actual hardware provided. From the Infra WG
perspective, we have tried to tack this second effort with the scenario
descriptor file[2]. We will work with installer PTL to find common
ground between these two efforts. If we can get this done for Danube
release, that would be great. If not, we will focus on E Release time
frame.

[1] https://wiki.opnfv.org/display/genesis/Configuration-files-discussion
[2] https://gerrit.opnfv.org/gerrit/#/c/23725/

Please take a moment to provide feedback on these efforts.


Thanks,

-- 
Jack Morgan
OPNFV Pharos Intel Lab

_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to