06:33:12 #startmeeting taas 06:33:12 Meeting started Wed Jan 27 06:33:12 2016 UTC and is due to finish in 60 minutes. The chair is yamamoto_. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:33:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:33:15 The meeting name has been set to 'taas' 06:33:26 #link https://wiki.openstack.org/wiki/Meetings/taas agenda 06:33:41 #topic spec 06:33:50 #link https://review.openstack.org/#/c/256210/ 06:33:57 i updated the spec review 06:34:14 i think i applied all feedback. sorry if i missed yours! 06:34:52 does anyone have anything particular about the spec to discuss? 06:35:10 i think fawadkhaliq mentioned about Policy Based packet mirroring 06:35:11 yamamoto_: thanks for updating the spec 06:35:20 I just look a quick look 06:35:27 I am not sure if we covered that yet 06:35:45 so maybe we can discuss that and the incorporate in the spec. 06:36:00 #agreed 06:36:01 s/and the/and then/ 06:36:14 yamamoto_ : from a use case point of view, would policy based mirroring be required ? 06:36:38 Since we are defining the API 06:36:44 do you have any idea how api for policy thing would look like? 06:36:45 I had the following thoughts: 06:37:14 We cover all the potential use cases and define the API to be able to support them. 06:37:20 The implementation can come in pieces. 06:37:51 Similar to how ipv6 works, not everything is implemented and expected to work but API definition is complete and can be consumed by different backends. 06:37:55 fawadkhaliq +1 , but we need to formalize use-cases 06:38:02 reedip: Agree 06:38:10 my impression is it's better to wait neutron classifier stuff settle and try to leverage it, rather than trying to invent our own right now. 06:38:11 I can take a stab at adding patch to yamamoto_ spec 06:38:48 yamamoto_: can you please elaborate a bit about Neutron classifier support for everyone's benefit? 06:39:58 Reference: https://github.com/openstack/neutron-classifier 06:40:34 #link https://github.com/openstack/neutron-classifier 06:40:39 my understanding is that it's trying to define something which can be shared among projects like fwaas sg etc 06:40:57 yamamoto_: yes, I think so too. 06:41:09 yamamoto_: so the classificaiton mechanism will be added as lib to neutron 06:41:16 yamamoto_: we will need the API definition 06:41:38 I am not sure how active this project is btw 06:41:46 does anyone know if this is being actively worked on? 06:42:45 i have no idea 06:42:58 I see this was last updated 2 months ago :( 06:43:03 fawadkhaliq : I think this is on a slow burner ... 06:43:11 reedip: exactly 06:43:12 might take some time 06:43:51 so maybe we move on and think about what's there today and make it happen with the existing primitives and if/when classifiers arrive, we can think about potential changes with an upgrade path 06:44:17 +1 06:44:21 reedip: yamamoto_ muawiakhan soichi: thoughts? 06:44:22 Anyways, I think keeping dependancy on neutron classifier is more towards the API definition, which can be followed up once a list of definitive use-cases are finalized 06:44:47 fawadkhaliq +1 on thinking about classifiers later 06:45:23 fawadkhaliq: +1 06:45:37 sure, we can/should feed our requirements to neutron classifer. 06:45:59 reedip: soichi muawiakhan yamamoto_. perfect! 06:46:21 so next step should be to update the spec with use cases? I can help there. 06:46:50 fawadkhaliq : +1 06:47:04 I will also look into it, and if possible update the same. 06:47:45 okay cool. yamamoto_ you can assign me an action item on that, I will be happy to help. 06:48:01 #action fawadkhaliq update the spec with use cases 06:48:15 :) 06:48:36 thanks yamamoto_ \o/ I like work :) 06:48:51 :) 06:49:11 There are some ideas on the spec as well , like (1) Network monitoring, instead of port (2) Policy based monitoring (3) tenant based monitoring(?) 06:49:56 reedip: yes, nicely summarized in one line. 06:51:38 lots of silence in the room :-) 06:51:39 anything else ? 06:51:42 *plays music* 06:51:48 yeah, it tends to be a bit quiet :) 06:51:55 lets move on 06:52:04 #topic Open discussion 06:52:27 L2 extnesion for taas is currently on hold, once vyadav comes back , will look into it 06:52:56 so from the governance perspective, can someone please summarize a bit whats the status of taas? 06:53:03 is it a subproject in neutron etc 06:53:29 it isn't neutron subproject. 06:53:34 fawadkhaliq : Nope , its still under discussion 06:53:53 #link https://review.openstack.org/#/c/229869/ 06:53:58 yamamoto_: reedip thanks. what are your thoughts around it? I am assuming we have a proposal 06:54:02 oh perfect 06:54:15 I will take a look 06:54:16 thanks 06:54:19 fawadkhaliq, its currently on hold, mainly because of the spec finalization 06:54:32 reedip: I see. thanks. 06:54:44 and "Evolving the stadium concept" 06:55:00 got it 06:55:10 thanks guys. that's all from my side. 06:55:49 yamamoto_ and all, nothing from my side as well . 06:56:25 it seems we've done 06:56:31 fawadkhaliq: the 4th comment from Armando on the governance commit is an important one, JFYI 06:56:47 reedip: thanks. Will take a look. 06:57:01 thank you for attending 06:57:08 #endmeeting