16:04:18 #startmeeting tacker 16:04:18 Meeting started Thu Jul 30 16:04:18 2015 UTC and is due to finish in 60 minutes. The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:04:22 The meeting name has been set to 'tacker' 16:04:31 #chair bobh 16:04:32 Current chairs: bobh sridhar_ram 16:04:41 #topic Announcements 16:05:07 Agenda at https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_July_29.2C_2015 16:06:16 Currently ETSI NFV #11 conference / meeting is in progress in San Jose 16:06:23 #link http://webapp.etsi.org/MeetingCalendar/MeetingDetails.asp?mid=15918 16:07:04 Tacker was introduced this forum in Tuesday's Plenary session 16:07:17 *to this forum 16:07:44 sridhar_ram: cool 16:08:00 Great 16:08:17 the subgroup handling MANO is IFA WG and it was interesting to see how the next revision (Phase 2) of MANO is evolving 16:08:33 sripriya_: Rajkumar_: thanks 16:09:18 Tacker Midcycle meetup is on Aug 20 - 21st 16:09:20 http://lists.openstack.org/pipermail/openstack-dev/2015-July/070948.html 16:09:36 Please update the etherpad if you planning to attend 16:10:06 anything else to announce from the team 16:10:08 ? 16:11:11 BTW, it was nice to see we came a full circle with the engagement with ETSI NFV IFA working group 16:11:37 #topic Health Monitoring 16:11:57 bobh: please take over.. 16:12:21 I split the health monitoring into two specs - just uploaded this morning 16:12:37 I realized I probably should have put them in different reviews, so let me know if you want me to do that 16:12:45 Hi - Please share us the link 16:13:05 where its uploaded. 16:13:28 #link https://review.openstack.org/202126 16:13:44 bobh: yes, it should go into two separate review 16:14:10 sridhar_ram: ok, I'll split it up 16:14:27 bobh: thanks 16:14:39 the driver module basics should be pretty easy to implement - just copying from the mgmt_driver and changing as needed 16:14:55 bobh: agree 16:15:03 I'd like to get started on that, so please review and let me know if there are any glaring holes or errors 16:15:53 the "interfaces" between the main life-cycle piece and the health-mon is what I'm curious about 16:16:50 team -please review the spec! 16:16:52 sridhar_ram: I'll need to take a look at the existing interface and see if it can be extended easily 16:17:27 bobh: yeah, we should even atleast callout the existing interface for the record 16:17:36 sridhar_ram: ok - will do 16:18:35 btw - there is a setting called "boot_wait" in tacker .. this is a param that is used as a cool-down timer before monitoring starts 16:18:47 currently this is a tacker.conf setting 16:19:05 I believe it should move to something that is per VNF .. 16:19:12 .. or even per VDU 16:19:37 Is there a documentation link that explains these settings? 16:19:40 probably VDU, though it could be inherited 16:20:14 vishwana_: no, that's a whole different talk we need to talk .. about Documentation 16:20:20 ok 16:21:03 we need something by end of Liberty...hopefully coinciding with our L-release 16:22:02 bobh: agree, inheritable is possible for some VNF with uniform VDUs 16:22:29 BTW, ETSI IFA has a whole section on Healing ... 16:23:04 Sat through that session yesterday where they talk about Remediation and Recovery... 16:23:28 I'll try to get some pointers .. may be added to our wiki 16:23:30 sorry, very late today 16:23:42 * sridhar_ram is now the official ETSI-Tacker liason :) 16:23:49 s3wong: np 16:24:04 sridhar_ram: will read the log after meeting ended 16:24:13 s3wong: sure 16:24:21 sridhar_ram: at least ETSI NFV team is now aware of Tacker :-) 16:24:46 +1 16:24:48 +1 16:24:57 absolutely.. had a nice discussion w/ the IFA co-chairs yesterday 16:25:31 I'm still digesting the boat of materials ... will try to bring them back to this team 16:25:39 *boat load 16:26:05 bobh: anything else on health-mon ? 16:26:16 I think that's it for now 16:26:31 alright ... 16:27:06 btw, as it is emerging, health-mon is probably one of the key Tacker L release deliverable.. 16:27:27 so no pressure.... 16:27:31 it will be cool to demo healing happening using multiple "methods" 16:27:36 bobh: :) 16:27:45 :-) 16:27:59 bobh: we have enough hands here to help .. so don't worry ;-) 16:28:22 alright, now w/ that (!) .. let move on .. 16:28:32 #topic MANO API update 16:28:50 sripriya_: any update from your side ? 16:29:32 sridhar_ram: i need to read through the link you posted in the comment of the spec review 16:29:34 http://docbox.etsi.org/ISG/NFV/Open/Published/gs_NFV-SWA001v010101p%20-%20Virtual%20Network%20Functions%20Architecture.pdf 16:30:17 if you can give a brief overview of the VNF states and how it affects REST API that will be great 16:30:44 sridhar_ram: i will read through the doc this week 16:31:20 sripriya_: yes. Related to this API work, I think we need to document Tacker's VNF life-cycle flow as a state-machine diagram .. 16:31:45 many of those state transition would end up as an API 16:32:28 at least we would be doing the MANO API work with come context vis-à-vis the ETSI's view of things 16:33:53 sridhar_ram: how would the states transition as an API end-point? right now it is vnf and vnfd and CRUD on these two resources 16:34:54 APIs always operate on Resource objects 16:35:43 IMO the state transition will just turn into the "action" 16:36:08 not all, but many of them.. 16:36:54 lets move on.. 16:37:03 anything else Sripriya ? 16:37:18 * sridhar_ram that came in the reverse order 16:37:39 sridhar_ram: so the API response would contain the action state 16:38:12 API response would contain the action "outcome" 16:38:56 sridhar_ram: i will look in to the doc and try to understand how that would map to the current implementation of response 16:39:11 sripriya_: sounds good 16:39:22 sridhar_ram: as we are going to just write a wrapper around servicevm 16:39:51 team - please comment on the MANO API spec. if you are satisfied leave a +1 as an ack 16:40:09 sripriya_: sure, understood 16:40:25 sripriya_, do you mind sharing the link to the spec heer 16:40:30 heer --> here 16:40:38 Yes please 16:41:04 #link https://review.openstack.org/#/c/204926/ 16:42:10 sripriya_: btw, looks finally that jenkins error got fixed 16:42:41 thanks to bobh perhaps ? 16:42:51 lets move on 16:43:05 sridhar_ram: thanks to bobh for fixing the liberty spec error, i just did a recheck on my spec and it got fixed 16:43:16 cool 16:43:18 #topic Testing Update 16:44:10 First, update my side... well, mostly apologies ;-) 16:44:42 I've been doing these conference runs last many weeks... 16:45:15 will try to get the skeleton test run soon 16:45:36 we also need some volunteers to contribute tests to Tacker 16:45:47 please reach out if you've some bandwidth 16:46:26 sridhar_ram: i plan to take some 16:46:45 sripriya_: thanks a lot 16:47:31 in fact we would soon start accepting patchsets only with tests ... 16:47:51 sridhar_ram: we should do that for sure 16:48:01 sridhar_ram: +1 16:48:19 sridhar_ram: but since we haven't gotten the framework in place, kind of unreasonable for us to reject patches without UT... 16:48:51 there is no easy answer to go back the existing code and add testcases ... given we have so much in the backlog 16:49:38 s3wong: well, I think we were in that super sprint towards Vancouver 16:50:14 sridhar_ram: py27 hasn't even been enabled yet in tox.ini :-) 16:50:18 now we got to pull back and get back into the best practices wagon 16:50:38 s3wong: yeah, I'll enable it soon with some skeletal tests 16:50:47 sridhar_ram: OK 16:51:27 bobh: please plan some test coverage for the health-mon piece as well 16:51:34 sridhar_ram: will do 16:51:59 * sridhar_ram noting it is 10 mins mark 16:52:16 anything else to talk on Testing ? 16:53:04 #topic Bugs 16:53:16 we have a problem here.. 16:53:48 the bug count is too low .. given many of them got knocked off ;-) 16:54:14 big problem indeed... 16:54:22 I can make it even lower if I get a couple of my patchsets submitted 16:54:29 LOL 16:54:30 bobh is the cause :P 16:54:48 I'm on vacation next week so you can get it back up again :-) 16:55:08 my side conversions show there are lot more people trying out Tacker .. 16:55:21 I'd welcome any bugs they would write.. 16:55:25 truly appreciated 16:55:29 lets move on 16:55:35 #topic Open Discussion 16:55:46 yeah, it would be great to get users to file some bugs... 16:55:52 quick shout out to any new folks joining Tacker .. 16:56:17 please introduce yourself.. 16:57:10 nobody? :-) 16:57:45 s3wong: they might be busy writing new bugs.. ;-) 16:57:56 that's it .. lets wrap up 16:57:59 sridhar_ram: that would be good :-) 16:58:15 have a nice rest of the week folks! 16:58:28 #endmeeting