18:01:51 <tbachman> #startmeeting networking_policy
18:01:51 <openstack> Meeting started Thu Nov  8 18:01:51 2018 UTC and is due to finish in 60 minutes.  The chair is tbachman. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:55 <openstack> The meeting name has been set to 'networking_policy'
18:02:37 <tbachman> #topic Open Discussion
18:02:44 <tbachman> rkukura: you have the floor :)
18:03:34 <rkukura> I just wanted to bring up the idea of removing the SFC part of GBP if nobody is actively working on or using it
18:04:08 <rkukura> This would at least help the CI jobs run faster and not timeout as oftern
18:04:18 <tbachman> rkukura: you’re talking about the legacy SFC support, right?
18:04:26 <tbachman> (used by the legacy plugins)
18:04:43 <rkukura> tbachman: I’m talkng about the GBP SFC, not the Neutron service chaining
18:04:52 <tbachman> ack
18:06:03 <rkukura> tbachman: did that work with the legacy ACI GBP policy driver and not with newer “merrged” policy driver?
18:06:12 <tbachman> rkukura: correct
18:06:23 <tbachman> I’m not even sure what state it’s in now, tbh
18:06:27 <annakk> I don't really know much about it, so I'm all for it :)
18:07:00 <tbachman> I think with some of the more recent releases, there were things fixed in the GBP stuff but maybe some equivalent fixes weren’t applied to the SFC bits
18:07:01 <rkukura> was it intended to work with any PD, or does it need adaption to each PD it could work with?
18:07:26 <tbachman> I’d have to check with Sumit on that one
18:07:50 <rkukura> anyway, we 1st need to figure out if anybody involved with GBP is actively using it or planning to
18:08:20 <rkukura> then if we agree it can go, we need to decide whether some sort of deprecation cycle is needed, or it can be abdubtly dropped
18:08:31 <rkukura> abrubtly
18:08:39 <tbachman> what would be the best way to advertise something like this?
18:08:41 <tbachman> A patch?
18:08:45 <tbachman> something to a mailing list?
18:09:43 <rkukura> its API is a separate service plugn, so I don’t think removing it would require any major version bump for the GBP API
18:09:57 <rkukura> maybe an email to openstack-dev would be enough
18:10:58 <rkukura> annakk: any thoughts on this?
18:11:18 <rkukura> oh, I see you said you are all for it
18:11:35 <rkukura> that’s all from me
18:11:37 <tbachman> k
18:11:52 <tbachman> rkukura: I can send an email to the mailing list
18:12:01 <rkukura> ok
18:12:36 <tbachman> anything else?
18:13:04 <rkukura> not from me
18:13:18 <rkukura> is there a summit next week in Berlin?
18:13:57 * tbachman goes to google
18:14:14 <tbachman> rkukura: you’re right :)
18:14:17 <rkukura> I guess annak would know if she was going, so I won’t ask her
18:14:40 <rkukura> sorry, I keep leaving the last k off annakk
18:14:51 <tbachman> heh
18:14:59 <tbachman> tab-completion :)
18:15:34 <tbachman> I don’t think anyone from our team is attending
18:16:20 <tbachman> annakk: rkukura: if there’s nothing else, I’ll go ahead and end the meeting.
18:16:25 <rkukura> should we wrap up for this month?
18:16:36 <rkukura> bye
18:16:46 <tbachman> rkukura: works for me
18:17:17 <annakk> bye!
18:17:23 <tbachman> annakk: bye
18:17:25 <tbachman> #endmeeting