17:01:00 #startmeeting network_common_flow_classifier 17:01:01 Meeting started Tue Dec 6 17:01:00 2016 UTC and is due to finish in 60 minutes. The chair is igordcard. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:05 The meeting name has been set to 'network_common_flow_classifier' 17:01:08 hi all 17:01:10 Hi 17:01:11 let's wait 3 minutes to improve the chances of everyone being around 17:01:49 kk 17:04:15 agenda: 17:04:18 #link https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Discussion_Topic_6_December_2016 17:04:30 #topic Continue discussion on user-facing API vs. Classification mixins. 17:04:34 #link https://review.openstack.org/#/c/333993 17:05:11 alright, I am supposed to update the current spec to add more information to the api-based approach and the mixin-based approach 17:05:52 it's in progress and should get an update soon this week 17:06:18 kk 17:06:31 meanwhile I will start working on a PoC for the api-based approach 17:07:09 Kk, I can try and help. 17:07:14 thanks davidsha 17:07:43 anyone free feel to join the effort - I'm always on IRC so just ping me 17:08:11 it would also be interesting to have a PoC for the mixin-based approach, but I am focusing on the api-based approach 17:08:47 besides the PoCs, I will try to keep the spec up to date with the latest efforts, both from the IRC discussions and the PoC(s) 17:09:30 It could be included as well, though it was intended for neutron_lib if I recall, but for testing we could include it in that repo 17:10:00 in the neutron_classifier repo I mean 17:10:16 davidsha: +1 17:10:35 which set of protocols are you going to include in this POC? 17:10:54 how future new protocols are going to be accepted? 17:10:57 davidsha: the models part is already aligned with most of what is common to either the api-based approach or mixin-based approach 17:11:58 ralonsoh: initially for the PoC I'm thinking about something extremely simple, e.g. a "L1" classification type which would allow us to match on neutron ports or neutron networks 17:12:07 Will we refer to api/mixin as resource/descriptive? just to stay consistent from last meeting. 17:12:44 ralonsoh: then we could extend QoS to consume these classifications and demonstrate how the classifications are telling the QoS service where the policy should be applied 17:12:59 igordcard: thanks! 17:13:14 ralonsoh: or likewise for networking-sfc for example... for logical source ports or logical destination ports 17:13:22 something simple like that 17:14:57 adding protocols in the future would be done by adding more types to the list of models underneath the classification framework... and consuming services would become compatible with the new protocols whenever they need (after the protocols are added to the framework/API) 17:15:51 davidsha: right david, resource-based and definition-based 17:16:01 igordcard: thats the one! 17:16:54 so resource-based classification approach is the one where there is a single API for classification resources (api-based as I said earlier) 17:17:11 An an extension would consume that resource 17:17:17 And an* 17:17:42 definition-based classification approach is the one where the services inherit the definitions of classifications and expose them in their own API, potentially by the use of mixins in their respective extensions (mixin-based as I said earlier) 17:18:22 davidsha: yes, an extension would consume resources from the single, common classifications API in the resource-based approach 17:18:47 any questions or thoughts about the duality of approaches and next-steps around them? 17:19:26 No, I'm good 17:19:57 moving on... 17:20:00 #topic Call for contributors 17:20:11 I guess I've already gone through this topic 17:20:28 So do I need to withdraw my earlier application and resubmit it? :P 17:20:59 no no, you can officially submit it now, like this: :p 17:21:09 :O 17:21:16 #action igordcard will contribute to the resource-based (api-based) approach PoC 17:21:51 :P 17:22:21 anyone else can just join 17:22:27 any questions or thoughts? 17:23:04 kk, no I'm good, the neutron_classifier repo already has the database definitions so we just need to make the service plugin. 17:23:35 exactly 17:23:40 Maybe make a patch for an extension that could use it to test it out too. 17:23:57 yeah 17:24:39 alright team 17:24:45 moving on... 17:24:47 #topic Open discussion 17:24:49 anything else we need to discuss? 17:25:23 I'm good, we have a good Idea what we need to do. 17:26:04 alright! I guess it's all for today then 17:26:09 thank you all 17:26:16 Thanks, cya! 17:26:18 bye 17:26:45 bye 17:27:18 #endmeeting