06:27:46 #startmeeting taas 06:27:47 Meeting started Wed Jan 20 06:27:46 2016 UTC and is due to finish in 60 minutes. The chair is reedip. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:27:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:27:50 The meeting name has been set to 'taas' 06:28:41 hi 06:28:44 Hello 06:28:55 #topic Agenda 06:29:06 Agenda for this meeting has been defined in https://wiki.openstack.org/wiki/Meetings/taas 06:30:21 Can everyone go through it, if not done already ? 06:31:10 As per the discussion which we had in the last meeting, mail has to be dropped so that the Spec can be reviewed in more depth 06:31:52 #action Reedip: Drop a mail on the ML inviting Neutron Core to comment and review the Spec and have a discussion on Gerrit/ Next week team meeting 06:32:51 yamamoto_ also proposed https://review.openstack.org/#/c/229869/ , which would allow integration of Tap-as-a-Service into stackalytics. But in my opinion, it would be taken care of once the Spec is confirmed 06:33:26 Currently TaaS is not a part of Stackalytics/governance 06:34:48 #link https://review.openstack.org/#/c/229869/ 06:37:20 Moving on, work has to be initiated for L2 extension of TaaS 06:37:29 #link https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion 06:37:55 yamamoto_ suggested in earlier meeting that this link needs to be updated along with the work for L2. 06:38:18 Vinay ( vyadav) and I would be taking up this work . 06:38:40 #action : reedip, vyadav : start work on L2 extension for TaaS 06:39:11 #link https://bugs.launchpad.net/tap-as-a-service/+bug/1535993 06:39:12 Launchpad bug 1535993 in tap-as-a-service "Convert TaaS to a Neutron L2 extension" [Undecided,New] - Assigned to Reedip (reedip-banerjee) 06:44:25 Next Item is requirement for an individual IRC channel, but I guess it would need some inputs from anil_rao and vyadav who would be joining us from next week 06:45:05 +1 06:46:22 Hi! Excuse me, I'm late. 06:46:30 hi soichi , no issues 06:46:42 reedip: +1 06:47:35 moving on , the next topic is a bit important 06:48:01 Inclusion of more core reviewers in gerrit and core members in Launchpad. 06:49:07 currently several projects follow two +2 rule to get their changes committed. But TaaS uses one +2 only. So we need to implement the two +2 rule here as well so that it allows a better review prospect 06:49:28 for that we may need to include more members in the TaaS core team 06:49:30 +1 for the desire but i guess it's something for anil and vyadav to decide. 06:50:16 yamamoto_ : Yes, they are the current core members. They will decide if the two +2 are required or not. But inclusion of more members in the core reviewer and core member team is necessary 06:51:25 sure, let's leave an action for them :-) 06:51:40 yamamoto_ : currently TaaS is not able to create feature requirements( Blue prints) . That can be done by only vyadav for now as he is the owner of the project. If the owner is a group of people ( for eg, neutron drivers), then it would be easier for some one to implement these changes 06:52:02 #action anil_rao, vyadav: take a call on two +2 rule for Gerrit 06:52:44 #action vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS 06:52:56 #action vyadav, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS 06:53:49 Next item is #link https://review.openstack.org/#/c/248043/ 06:54:18 kaz, yamamoto_ requested an update for this. Is there any inputs to be given for the same ? 06:56:58 i guess the implementation ofs this will be simpler once we made the agent an l2 extension, 06:57:38 I think so. 06:57:57 yamamoto_ : ok, so we would start working on the L2 extension sooner 06:59:28 kaz : can you put a -1 on the workflow , with the message that https://review.openstack.org/#/c/248043/ would be restarted once work on L2 extension is complete? It would help us and other reviewers to track what is required/blocking a patch 07:00:11 ok 07:00:27 kaz thanks . 07:00:45 The topics from the agenda is complete . 07:00:56 #topic Open Discussion 07:02:56 #link https://review.openstack.org/#/c/257285/ 07:02:58 yamamoto_: thank you for your "+1" review comment. 07:03:33 kaz: do you have any plan on it? 07:04:34 Currently, i think no additional update for it. 07:06:37 can you reply to rossella and kevin's comments? 07:07:51 ok, I will check the comemnts and reply. 07:08:13 kaz: thank you 07:08:38 is anyone here working on tempest tests? 07:09:10 yamamoto_ not on TaaS yet, but can start on it . Have some bandwidth right now 07:10:37 one difficulty is that to make meaningful tests for taas we likely need some "tap" functionality in VMs 07:11:07 and the default VM image doesn't seem to have tcpdump etc. 07:14:10 can such tests be mapped onto the functional tests ? 07:16:15 reedip: i guess some parts of it can be 07:16:55 but it doesn't replace the need of tempest tests 07:17:06 yamamoto_ , yeah thats right 07:19:31 10 minutes left, anything else to discuss, or should we wrap up early 07:20:21 nothing from me 07:20:22 yamamoto_ : lets discuss tempest tests in depth once the full team is here next week 07:20:34 reedip: sure 07:21:12 #action reedip, yamamoto_ : discuss testing related scenarios next week 07:22:02 kaz, soichi , anything ? 07:22:18 no, i don't have. 07:22:33 no, i do not have. 07:22:49 Ok, then I can wrap it up .. 07:22:54 Thanks for your time everyone 07:22:57 #endmeeting