17:01:36 <LouisF> #startmeeting service_chaining
17:01:37 <openstack> Meeting started Thu Aug 10 17:01:36 2017 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:40 <openstack> The meeting name has been set to 'service_chaining'
17:01:51 <LouisF> hi all
17:01:55 <pcarver> hi
17:02:03 <igordcard> hi
17:02:03 <LouisF> pcarver: hi
17:02:07 <LouisF> igordcard: hi
17:02:11 <vks1> hi
17:02:16 <LouisF> vks1: hi
17:02:26 <bcafarel> hello
17:02:32 <LouisF> bcafarel: hi
17:02:47 <LouisF> #topic agenda
17:03:09 <LouisF> https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting
17:04:31 <LouisF> another item for discussion is chain monitoring and integration with ceilometer
17:05:10 <LouisF> pcarver: what is status on API reference
17:05:24 <LouisF> #topic API reference
17:05:58 <pcarver> nothing new. There's one test job it fails but I didn't spend very long trying to figure out why
17:06:06 <LouisF> pcarver: ok thanks
17:06:07 <pcarver> it passes tox locally
17:07:01 <LouisF> #topic Tap SF
17:07:09 <LouisF> vks1: what is status?
17:07:40 <LouisF> https://review.openstack.org/#/c/449954/
17:08:10 <vks1> LouisF: amotoki has given a comment to add 'tap_enabled' as extension. I have added that extension and tested it works fine
17:08:41 <vks1> but for testing code, I am facng issue to load the extension for DB
17:08:51 <vks1> means test_sfc_db.py
17:09:12 <vks1> wanted to know how I can load my or any extension there
17:09:13 <bcafarel> vks1: did you push an updated patchset with the new extension? I don't see it
17:09:31 <vks1> I can't push without adding test case
17:09:42 <vks1> that is the problem
17:10:39 <vks1> basically https://github.com/openstack/networking-sfc/blob/master/networking_sfc/tests/unit/db/test_sfc_db.py#L281 . I don't see a way to add extension here
17:11:20 <vks1> I added extension here but of no use
17:11:39 <vks1> any pointers on this will be helpful
17:12:09 <bcafarel> you can add it with failing tests, it may help to dig where's the problem
17:12:36 <vks1> bcafarel: are you suggesting to update the same patchset ?
17:12:44 <bcafarel> though no guarantee from me, I am leaving for a few days (yay holidays) soon
17:12:55 <mohankumar_> hi vks1,  sorry got busy with personal work . will check it tmrw !
17:13:18 <bcafarel> vks1: yep, that will end in the same patchset in the end right?
17:13:24 <vks1> bcafarel: mohankumar_ its alright, I will upload patchset then
17:14:17 <mohankumar_> vks1 , yes  , that help to check  py27 error traces
17:14:19 <amotoki> if your new feature is supported by 'sfc' service plugin, changing the line you mentioned looks good to me
17:14:30 <vks1> amotoki: :)
17:14:46 <amotoki> (though the current approach in test_sfc_db looks a bit weird from POV of testing code)
17:14:59 <igordc> amotoki: after changing the service plugin it will, but I thought the point was that API changes require API extensions?
17:15:36 <amotoki> API change and service plugin change are different thing
17:16:02 <amotoki> yeah, the point is a new API extension for API discoverability.
17:16:51 <amotoki> I will be online next week, so I think I can help it a bit
17:16:51 <igordc> amotoki: so the existing service plugin will have to now support a new API extension right?
17:16:53 <bcafarel> same old service plugin, new extensions
17:17:25 <vks1> amotoki: even I add the extension at the line mentioned above , its not getting loaded, that's weird. I will upload patchset, please have a look
17:17:31 <amotoki> igordc: yes, one of plugins must load a new API extension, so sfc plugin need to load the API extension
17:17:57 <igordc> amotoki: thanks, I get it
17:18:30 <amotoki> vks1: https://github.com/openstack/networking-sfc/blob/master/networking_sfc/tests/unit/db/test_sfc_db.py#L298-L304 might need to be changed as well.
17:18:32 <LouisF> amotoki: thanks, can you help vikash with this
17:18:47 <amotoki> (i haven't looked at the detail though)
17:19:20 <bcafarel> sorry folks, I have to leave, see you later all
17:19:23 <amotoki> i can take a look next week
17:19:35 <vks1> amotoki: will sync up with you probably next week
17:19:43 <LouisF> amotoki: thanks
17:20:10 <LouisF> #topic SFC graph
17:20:39 <igordc> mostly on hold until mid-september
17:20:55 <igordc> I'll be fixing the patches as reviews come
17:20:56 <LouisF> https://review.openstack.org/#/c/478668/
17:20:57 <igordc> and rebasing them
17:21:14 <LouisF> igordc: ok
17:21:15 <igordc> hoping I don't have to rebase too many times until it merges
17:21:34 <igordc> I'm on vacation first half of september
17:21:43 <LouisF> igordc: me too
17:22:05 <mohankumar_> LouisF , igordc : enjoy !
17:22:15 <igordc> thanks mohankumar_
17:22:37 <LouisF> mohankumar_: btw, thanks for your work on the OSC
17:22:57 <mohankumar_> LouisF :  :)
17:23:01 <LouisF> and getting it merged
17:23:31 <LouisF> #topic NSH dataplane
17:23:44 <igordc> on hold until mid-september
17:23:50 <LouisF> igordc: ok
17:24:14 <igordc> it might be possible that OVS 2.8 with the right kernel will have the kernel dataptah for NSH
17:24:35 <igordc> but anyway the feature freeze is past so only Queens will have NSH
17:24:38 <LouisF> igordc: yes i saw some emails on that
17:25:09 <LouisF> igordc: NSH work will be in Queens
17:25:20 <igordc> also NSH is about to become a standard, just a matter of time now
17:25:57 <LouisF> igordc: probably by  next IETF meeting
17:26:28 <LouisF> #topic OVN driver
17:26:43 <LouisF> john is not on
17:27:03 <LouisF> #topic chain monitoring
17:27:31 <LouisF> mohankumar_: you were looking  at this?
17:28:22 <mohankumar_> LouisF , no i havn't started ..  waiting for the mail reply
17:28:25 <LouisF> was there a blueprint on OAM Operation Manager for SFC
17:28:55 <mohankumar_> LouisF , will sync with rajeev next week
17:29:17 <igordc> I'm interested in this as well but have nothing in mind yet
17:29:34 <igordc> perhaps integrating somehow with aodh and gnocchi would be beneficial
17:29:47 <LouisF> maybe worthwhile creating a list of useful sfc statistics
17:30:05 <igordc> and some investigation should be made to know what would benefit an nfv orchestration layer
17:30:27 <LouisF> igordc: agree
17:30:30 <mohankumar_> igordc  , LouisF : yes
17:30:31 <igordc> LouisF: eyes
17:30:33 <vks1> we had this statistics engine internally
17:31:12 <mohankumar_> vks1 : specific to sfc chain ?
17:31:40 <vks1> Not SFC but yes similar to SFC service chain
17:31:56 <mohankumar_> vks1 : based on openstack metering ?
17:32:02 <vks1> mohankumar_: yeah
17:32:12 <mohankumar_> vks1 : ahh okay
17:32:39 <vks1> mohankumar_: will talk to you sometime
17:32:55 <mohankumar_> vks1 : sure , you can find me in IRC
17:34:37 <LouisF> there is some IETF work on sfc measurements https://tools.ietf.org/pdf/draft-mirsky-sfc-pmamm-01.pdf
17:36:10 <LouisF> anyway it will be useful to get this work underway in queens
17:36:19 <mohankumar_> LouisF , looks  it  used   NSH Mark Field
17:36:25 <LouisF> #topic other  items
17:37:02 <LouisF> mohankumar_: yes - we can start to use nsh in queens
17:37:20 <mohankumar_> LouisF: okay
17:38:05 <LouisF> all i have for now - anything else?
17:38:15 <mohankumar_> nothing from me !
17:38:19 <igordc> just be aware it's a not a primary sfc draft
17:38:31 <igordc> or "active"
17:38:34 <igordc> https://datatracker.ietf.org/wg/sfc/documents/
17:38:50 <mohankumar_> igordc : same running in my mind
17:39:16 <igordc> could become though
17:39:54 <LouisF> igordc: yes, can monitor it progress
17:40:15 <LouisF> ok thanks all
17:40:20 <vks1> bye
17:40:23 <LouisF> bye
17:40:26 <mohankumar_> bye
17:40:30 <igordc> bye all
17:40:31 <LouisF> #endmeeting