15:04:52 #startmeeting Copper Weekly Meeting 15:04:52 Meeting started Wed Aug 26 15:04:52 2015 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:52 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:04:52 The meeting name has been set to 'copper_weekly_meeting' 15:05:03 #info Bryan Sullivan 15:05:14 #info Prakash Kanthi 15:05:14 #info Prakash Kanthi 15:05:21 too fast! 15:05:45 #info OK, here is a quick summary of status 15:06:08 #info the 19th call was cancelled and I sent an email 15:06:38 #info The latest docs build was completed and is now linked to the wiki 15:06:58 #link https://wiki.opnfv.org/copper 15:07:18 #info see "Current working draft of use cases, architecture, and requirements analysis" 15:07:51 #link http://artifacts.opnfv.org/copper/design_docs/index.html 15:08:13 #info I will move contend from the wiki into the doc as the work progresses 15:09:44 #info Anyone can propose additional content in the doc - there is still significant analysis to do on the config requirements capabilities of various VIMs 15:10:30 #info e.g. as they use Heat, flavors, Nova scheduler hints, MD-SAL, etc 15:11:50 #info What I plan to do is develop a use case demo and implement the various resource requirements as model data (e.g. TOSCA) or test driver code that exercise existing OpenStack and ODL etc functionality 15:12:31 #info The first step is still though getting a lab off the ground and I am working with Spirent to do that in their vctlab environment 15:12:53 #info Nothing more to share at the moment except perhaps some sense of the project planning for B release 15:12:58 any questions? 15:13:41 #info Tacker has a means to specify the TOSCA templates that Heat can understand and have the ability to hook in a mgmt and monitoring driver. 15:13:58 #info Do you see that as a viable part of the demo? 15:14:52 #info Yes, that will be part of it. Any work to create an example, e.g. using a Tacker standalone environment, would be helpful 15:15:23 #info For example, take a simple use case and describe how the TOSCA template would look 15:15:33 #info One advantage I see with this is, all the VNFs can be instructed on what mgmt/monitoring drivers find out when policies are breached 15:16:07 #Not sure I understand that point 15:16:15 #info Sure, I can try building TOSCA templates for the UseCases you can add to this list. 15:16:41 #info Tacker drivers can detect the policy breaches 15:17:13 #info As Tacker can also communicate with other VNFs, we will have that feedback loop open, if needed 15:17:19 #info A simple use case is a web server behind a firewall, with a cache between it and the firewall. 15:17:52 #info agree 15:18:03 #info It would be good to describe in the design doc how Tacker can detect policy breaches 15:18:26 #info I can take up that task 15:18:59 #info e.g. in the requirements section 15:19:02 #link http://artifacts.opnfv.org/copper/design_docs/requirements.html 15:19:22 #info there is a description of how various components can be used to implement the requirements 15:20:02 #info in the process of describing and validating the solutions we will uncover gaps 15:20:41 #info or in the best case end us with a clear description of how the Copper goals can be achieved today with existing components 15:21:11 #info So put any proposed changes in using git and I will review them in gerrit 15:21:13 #info agree 15:21:25 #topic AOB 15:21:47 ok, anything else? otherwise I will get back to building the lab... 15:22:14 #info nope, i will review the UseCases. Thanks 15:22:30 appreciate it. bye for now 15:22:35 #endmeeting