#opnfv-copper: Copper Weekly Meeting

Meeting summary

1. 1. Bryan Sullivan (bryan_att, 14:57:06)
   2. No prepared agenda for today, open discussion if any has any topics following the OPNFV summit (bryan_att, 14:58:15)
   3. I'm focused on gettine a testbed off the ground (JIra: 2) (bryan_att, 15:00:01)
   4. https://jira.opnfv.org/browse/COPPER-2 (bryan_att, 15:00:05)
   5. this is the first key prerequisite to having a demo capability for the Nov summit and for Congress as part of the B release (bryan_att, 15:01:34)
   6. I am new to this project. I see lot of relevance between what we are trying to do with VNF Manager and COPPER requirements. Am i reading this right? (Prakash_DataTap, 15:03:29)
   7. No sure, what specific relation do you see? Clearly VNFM has a role (or there is a VNF management related role, more generally) for setting up resources per the needs of a NF (bryan_att, 15:05:10)
   8. as part of the upper MANO stack functions; but what specifically do you have in mind? (bryan_att, 15:05:53)
   9. there are several aspects to policy; the project broadly covers them, but will focus on the ones that are unique to it (bryan_att, 15:07:01)
   10. for example; knowing what is needed for a NF per resources, and what is needed for a NS as a chain of NFs, and then fulfilling those needs thru VIM APIs - that is "configuration intent" (bryan_att, 15:08:09)
   11. are we going to have GoToMeeting for this call? (Prakash_DataTap, 15:08:22)
   12. whereas making sure that things don't get done that violate some generic (VNF-independent) policy; that is "config enforcement" (bryan_att, 15:09:33)
   13. "config intent" definition and fulfillment is a broader topic that I am trying not to duplicate in Copper, though it clearly is a dependency for the system overall (bryan_att, 15:10:27)
   14. e.g. we need a mechanism for expressing intent "what" and "how" levels so we can also ensure that we can express what *should not* happen (config violations) (bryan_att, 15:11:20)
   15. is that clearer re the scope of Copper and VNFM? (bryan_att, 15:11:41)
   16. Do you see GBP as a place for 'config intent'? (Prakash_DataTap, 15:12:04)
   17. Yes, GBP is one mechanism that can fulfill grouping NFs for configuration into services (bryan_att, 15:12:58)
   18. but to avoid stretching the term; GBP really relates to "how" rather than "what"; when you hear others speak of intent they mean more the "what" (bryan_att, 15:13:43)
   19. i.e. "intent" means to them an implementaton-approach-independent express of what is wanted, rather than how it's achieved (bryan_att, 15:14:18)
   20. So you are saying intent 'what' and 'how' is what is covered in Copper? (Prakash_DataTap, 15:14:26)
   21. Both what and how are covered in Copper, but more focused on ensuring config policy violations are detectable and can be dealt with (bryan_att, 15:15:13)
   22. sounds like traditional PM in FCAPS but on policy - Policy Performance (Prakash_DataTap, 15:15:55)
   23. Re how things are supposed to be built and how that relates to what was originally expressed as a need (what), that's a broader topic that Copper will depend upon but not address specifically (bryan_att, 15:16:12)
   24. Unless its found that these are not being addressed by other projects... (bryan_att, 15:17:13)
   25. And then we will take config intent and fulfillment in Copper, e.g. as i have proposed for the summit demo on "A day in the life of a VNF" whch will touch on and demo VNFM and NFVO functions (bryan_att, 15:18:26)
   26. but for now, config enforcement is the prime focus; thus getting Congress into the OPNFV build is a first priority; ODL GBP/SFC is next; etc (all the dependent functions that can be used to define how things are *supposed* to work can also be useful for defining what *should not* happen) (bryan_att, 15:20:18)
   27. Is any one working on this already towards the Nov demo? (Prakash_DataTap, 15:21:09)
   28. I am working to get a lab setup - that's task #1 (bryan_att, 15:21:35)
   29. I can contribute as well. Please point me to the right resources to get started. (Prakash_DataTap, 15:22:05)
   30. It would be great to have that being done in multiple places - i.e. labs - some competition to getting Congress installed (bryan_att, 15:22:15)
   31. Do you have access to a Pharos lab? (bryan_att, 15:22:33)
   32. That's the first step - you need a lab that you can then install the latest stable Kilo and Lithium on, then enhance with Congress and SFC/GBP (enventually) (bryan_att, 15:24:17)
   33. will try to setup one in my company. Thanks for the info. Let me know if there are other ways I can contribute as well. Talk to you next Week. (Prakash_DataTap, 15:25:33)
   34. As I develop any extra docs needed to get Congress installed (beyond their docs) i will post them on the wiki (bryan_att, 15:25:44)

Action items

1. (none)

People present (lines said)

1. bryan_att (33)
2. Prakash_DataTap (13)
3. collabot (3)