...
Community: Atul Purohit Saad Ullah Sheikh David Perez CaparrosguochuyiRyan Hallahan cl664y@att.com Olivier Augizeau Vincent Colas Herbert Damker Guy Meador
Guests: cl664y@att.com
LFN: David McBride Jim Baker
...
Summary: The El Alto release could be shortened and focus on internal (tech) debt and defect backlogs. A proposed release cycle is presented.
Next steps: Reviewing at the ONAP TSC call 2019-04-11
Some e2e use cases are useful but too specific - would like to build our own use cases - would like more "ala carte" use cases (modularity) - is this a possible component of El Alto? Olivier Augizeau
- Yes, this is exactly the type of info that the EUAG should be providing - please continue to provide this type of feedback.
Chat log
...
| View file | ||||
|---|---|---|---|---|
|
Chat log
09:00:08 From Guy Meador (Cox) : Sorry that I joined late today. Here is a perspective on the EUAG “Proposed Re-Boot” topic. If we in the EUAG have members who desire to create and support the activities outlined for a sub-working group focused on “ONAP/OPNFV”, that is a good sub-team to create as a part of the LFN EUAG; doing so would not require a re-chartering of LFN EUAG; would prefer not re-chartering LFN EUAG
09:02:43 From Guy Meador (Cox) : Re: “EUAG Re-Chartering”: to be clear, and in summary, I would support the creation of a sub-team/activity of “ONAP/OPNFV EUAG Working Group” but not re-chartering of LFN EUAG. Having the sub-group would be of value to the ONAP/OPNFV community and allow the operator community to engage at a more tactical level with ONAP/OPNFV.
09:03:05 From Guy Meador (Cox) : ONAP “tic-to” releases makes sense to me
09:03:08 From Atul Purohit (Vodafone) : That is the idea, not to re-chart LFN EUAG, but within the confines of current - start a reboot to make it more meaningful. Thanks Guy
09:03:14 From Guy Meador (Cox) : “Tic-Toc”
...