17:30:14 <SumitNaiksatam> #startmeeting Networking Advanced Services
17:30:15 <openstack> Meeting started Wed Aug  6 17:30:14 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:30:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:30:18 <openstack> The meeting name has been set to 'networking_advanced_services'
17:30:27 <banix> hi
17:30:53 <SumitNaiksatam> so i wanted to clear out the priorities right at the outset
17:31:24 <SumitNaiksatam> so that we dont end up spending time here discussing only to be blocked by a -2 towards the end of J3
17:31:38 <SumitNaiksatam> this is not on the agenda
17:31:49 <SumitNaiksatam> does any one have objections to discussing this?
17:32:06 <SumitNaiksatam> or any other higher priority item to start the meeting?
17:32:49 <SumitNaiksatam> mestery: there?
17:32:59 <SumitNaiksatam> i would like to get the PTL’s opinion on this
17:33:10 <SumitNaiksatam> and provide us with direction here
17:33:44 <SumitNaiksatam> mestery: checking again
17:34:26 <SumitNaiksatam> i would have liked to check with markmcclain as well
17:34:40 <SumitNaiksatam> however he does not seem to be online either
17:35:18 <marios> SumitNaiksatam: just to be clear we're talking about the priorities of this group right?
17:35:51 <SumitNaiksatam> marios: i am talking about priorities for this group as well, the priorities of this group in the context of what is happening in neutron
17:35:53 <marios> (and how they align with neutron more generally)
17:35:57 <marios> right thx
17:35:59 <SumitNaiksatam> marios: yeah exactly
17:36:42 <s3wong> SumitNaiksatam: however on Monday Neutron meetings, adv-service is no longer even a line item for discussion. So I am worried that cores would not pay attention to us...
17:36:47 <SumitNaiksatam> if anyone is following the thread regarding GBP on the dev mailer, it was suggested by folks from outside the neutron team that Neutron should be solely focussing nova network parity
17:37:10 <marios> why was adv. services removed from the weekly meeting agenda
17:37:32 <SumitNaiksatam> s3wong marios: i dont think it was removed
17:37:43 <SumitNaiksatam> i did provide an update on it
17:37:51 <ivar-lazzaro1> SumitNaiksatam: yeah right, and saying that during J-3 is exactly the proper time :D
17:38:28 <SumitNaiksatam> i am trying to pull up the logs
17:38:49 <marios> SumitNaiksatam: so right now for j3 we have flavors and service insertion right?
17:39:00 <SumitNaiksatam> #link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-08-04-21.02.log.html
17:39:14 <SumitNaiksatam> marios: we have flavors, service insertion and service chaining
17:39:36 <SumitNaiksatam> these are in different stages
17:39:51 <SumitNaiksatam> flavors spec is not approved, but enikanorov_ has made good progress on the implementation
17:40:10 <songole> SumitNaiksatam: is there a relative priority of these 3 projects?
17:40:13 <SumitNaiksatam> service insertion spec is approved, and work is in progress, but not as far along as we would have liked
17:40:49 <SumitNaiksatam> and service chaining work is coming along well, i believe
17:41:08 <SumitNaiksatam> songole: i dont know the priority of flavors since its not approved yet
17:41:15 <SumitNaiksatam> songole: but i believe it would be high
17:41:40 <songole> I guess chaining is marked low
17:41:53 <SumitNaiksatam> the other two are at medium priority
17:42:08 <songole> ok
17:42:24 <SumitNaiksatam> since thet are part of the same launchpad bp
17:42:25 <dougwig> mestery has a bad cold today, fyi.  he might be a little less responsive.
17:43:54 <SumitNaiksatam> dougwig: yes i know
17:44:16 <SumitNaiksatam> dougwig: we chatted and asked me to ping him nevertheless in case he was feeling up to it
17:44:38 <dougwig> ok, good.
17:46:04 <SumitNaiksatam> ok we can go through the regular updates, i guess
17:46:10 <SumitNaiksatam> unless someone has other suggestions
17:46:52 <SumitNaiksatam> i wanted us to all be on the same page with the priorities before we spend more time on this
17:46:52 <SumitNaiksatam> #topic Flavors
17:46:52 <SumitNaiksatam> enikanorov_: hi
17:47:55 <s3wong> no one is on-line today :-)
17:47:59 <SumitNaiksatam> enikanorov_: any progress on the spec? :-)
17:48:17 <marios> s3wong: it's summer, maan :)
17:48:24 * SumitNaiksatam runs for cover to escape enikanorov_’s ire!
17:48:25 <garyduan> I think enikanorov updated his patch several times
17:48:44 <garyduan> I asked him about what need to be done for different services
17:48:49 <marios> SumitNaiksatam: are you trolling?
17:48:50 <SumitNaiksatam> the spec is not updated since July 3rd
17:49:11 <garyduan> right. He asked me to stay put too ...
17:50:01 <SumitNaiksatam> in the last meeting we were told by the PTL that the priority would be to get this approved end of last week
17:50:26 <SumitNaiksatam> i am one of the reviewers on this, but without an update on the spec i dont see how we can move forward on approving it
17:50:31 <SumitNaiksatam> enikanorov_: still there?
17:52:48 <SumitNaiksatam> perhaps we have lost enikanorov_ as well
17:53:08 <SumitNaiksatam> anything anyone else wants to discuss related to flavors?
17:53:37 <SumitNaiksatam> are the respective services’ patch owners already working on following up on enikanorov_’s flavor’s implementation?
17:54:04 <SumitNaiksatam> if things do progress, we would need lbaas, fwaas, and vpnaas to comply wiht the flavors framework (however that ends up being)
17:54:34 <SumitNaiksatam> if you have signed up to do the work, perhaps good to still stay in the loop (we havent given up on this yet!)
17:55:57 <SumitNaiksatam> ok moving on
17:56:04 <SumitNaiksatam> #topic service chaining
17:56:10 <SumitNaiksatam> songole hemanthravi: there?
17:56:20 <hemanthravi> hi
17:56:26 <songole> SumitNaiksatam: I will give an update
17:56:36 <SumitNaiksatam> songole: please go ahead
17:56:44 <songole> CLI patch and API extension is done.
17:56:56 <songole> plugin implemention is almost there
17:57:07 <songole> I am working on DB
17:57:20 <songole> I will post once I have DB in place
17:57:57 <SumitNaiksatam> songole: oh wow that is excellent progress
17:58:05 <SumitNaiksatam> songole: have you posted WIP patches?
17:58:16 <songole> SumitNaiksatam: not yet.
17:58:37 <songole> I will post after some testing
17:58:39 <SumitNaiksatam> songole: it will be good to do that at the earliest so that the rest of the team here can focus on thise
17:58:43 <SumitNaiksatam> *those
17:59:24 <SumitNaiksatam> focus on reviewing that is
17:59:26 <songole> ok. will post once I got DB working
17:59:47 <SumitNaiksatam> songole: actually if you tag it as WIP, it does not matter if its not fully functional
17:59:57 <SumitNaiksatam> songole: i think you should post it in the state that it is in
18:00:14 <songole> ok
18:00:36 <SumitNaiksatam> songole: any questions for songole?
18:00:53 <s3wong> songole has question for songole?
18:01:07 <marios> heh
18:01:28 <songole> SumitNaiksatam is multi tasking :-)
18:01:42 <SumitNaiksatam> fat fingered :-)
18:01:51 <SumitNaiksatam> any questions for songole?
18:01:59 <SumitNaiksatam> songole: any blockers for you?
18:02:14 <songole> None at this time.
18:02:16 <SumitNaiksatam> (actually i was going to ask that first, hence already songole typed in :-) )
18:02:27 <SumitNaiksatam> songole: alright great
18:02:35 <SumitNaiksatam> #topic Service insertion
18:02:47 <SumitNaiksatam> s3wong: there?
18:02:52 <s3wong> SumitNaiksatam: yes
18:03:03 <SumitNaiksatam> i believe kanzhe has still not returned from his vacation
18:03:10 <s3wong> Sometimes today (hopefully) I will post a WIP patch for service insertion API and DB
18:03:18 <marios> i put a wip out today
18:03:25 <marios> https://review.openstack.org/#/c/108049/
18:03:47 <s3wong> I have spent the morning changing kanzhe 's stuff to be more closely aligned with the final spec
18:03:52 <marios> (vpn side of things, will remove all the extraneous parts (like the serviceinterfacedb once the base is sent)
18:04:08 <s3wong> posting the WIP would also allow marios and SridarK to start their patches with an dependency
18:04:11 <SumitNaiksatam> marios: that is awesome
18:04:17 <SumitNaiksatam> marios: its good to be ahead of the curve
18:04:19 <s3wong> so I don't have to be a blocker
18:04:28 <SridarK> s3wong: thanks - we will need to sync up too
18:04:35 <SumitNaiksatam> s3wong: thanks for working on this in parallel, thats awesome
18:04:59 <marios> SumitNaiksatam: sure. started thinking a bit about tests today to
18:05:08 <marios> SumitNaiksatam: btw... will we be doing 'one more update' to the spec?
18:05:12 <SumitNaiksatam> marios: thats great
18:05:32 <marios> SumitNaiksatam: (eg removal of the 'router' attribute from the vpn db class)
18:05:47 <SumitNaiksatam> marios: oh i thought we will leave it in there, right?
18:05:48 <marios> SumitNaiksatam: or you think is unnecessary?
18:06:10 <marios> SumitNaiksatam: ok, wasn't sure about that one
18:06:27 <pcm_> isn't it neccessary?
18:06:32 <s3wong> marios: I think we have agreed to not remove it (in IRC meeting) - but the spec hasn't reflected it
18:06:44 <marios> s3wong: yes that is exactly what i mean
18:07:28 <s3wong> SumitNaiksatam is so mad that he left
18:07:32 <marios> SumitNaiksatam: 18:06 < s3wong> marios: I think we have agreed to not remove it (in IRC meeting) - but the spec hasn't reflected it
18:07:35 <marios> 18:06 < marios> s3wong: yes that is exactly what i mean
18:08:06 <marios> i c
18:09:15 <s3wong> Well, we lost SumitNaiksatam again
18:09:28 <s3wong> but luckily, I am done with my update :-)
18:09:35 * marios too
18:09:46 <marios> s3wong: will you be publishing to gerrit btw?
18:10:01 <marios> s3wong: last week you mentioned https://github.com/noironetworks/neutron-group-policy/tree/service-insertion
18:10:16 <s3wong> marios: yes
18:10:27 <s3wong> kanzhe made some initial changes there
18:10:54 <s3wong> and it is based on his changes that I am currently making changes to make the code more up-to-date with the latest spec
18:11:14 <marios> s3wong: ok thanks, i'll have a look when i revisit for my update next week
18:11:25 <SridarK> s3wong: so the current model is to introduce a new plugin ?
18:11:25 <marios> (or rather will look out for that review)
18:11:39 <s3wong> marios: my update will actually go to gerrit (WIP) patch (hopefully today)
18:11:49 <marios> ok thx
18:12:06 <s3wong> SridarK: well, the service interface class already has a pluginbase, so that is not new
18:12:53 <s3wong> the question has more to do with --- given that FW/VPN/LB instance creation happens on REST API on respective services, how would the serviceInterfacePlugin be able to know
18:13:14 <SridarK> s3wong: yes that was the discussion on the last mtg
18:13:28 <s3wong> SridarK: yes
18:13:39 <SumitNaiksatam_> hi, folks, for some reason i was not seeing any of your messages in my client
18:13:57 <SumitNaiksatam_> logged in from the web client now
18:13:58 <SridarK> SumitNaiksatam_: it seemed like u got bounced out
18:14:07 <s3wong> SridarK: marios: on the meantime, the notification system has more to do with plugin implementation, so just for API and DB, I can post a patch first to not block you guys
18:14:11 <SumitNaiksatam_> SridarK: ah ok
18:14:28 <SumitNaiksatam_> s3wong: that sounds like a good idea to make progress
18:15:01 <SridarK> s3wong: ok - need to dig thru some specifics so i get on the same page - missed some discussion on my PTO - will ping u offline
18:15:08 <marios> s3wong: SumitNaiksatam_ do we need to update the spec to describe these changes too?
18:15:27 <s3wong> SumitNaiksatam_: done with our updates
18:17:32 <marios> SumitNaiksatam: i promise i won't say 'update the spec' again if start talking to us again
18:17:41 <SumitNaiksatam> marios: lol
18:17:53 <SumitNaiksatam> i think there are network issues at my end
18:17:57 <marios> :)
18:18:02 <SumitNaiksatam> my sincere apologies to all!
18:18:21 <SumitNaiksatam> so have concluded on the service insertion discussion
18:18:24 <SumitNaiksatam> i only got parts of it
18:18:53 <marios> :/
18:19:08 <marios> when it rains...
18:20:48 <s3wong> Oh well, I guess cgoncalves and anil_rao will have to hold on for their updates on traffic steering and TapaaS
18:21:19 <marios> surely someone else can drive the meeting if we need to?
18:21:33 <marios> are cgoncalves and/or vinay about?
18:22:03 <anil_rao> Vinay is not here today, but I can give a brief update on Tap-aaS. :)
18:22:03 <marios> in which case moot point :)
18:22:24 <marios> #topic TAPaaS
18:22:40 <marios> does meetbot only respond to certain people?
18:22:51 <anil_rao> We (Vinay and I) are currently revising the spec
18:23:05 <s3wong> marios: yes, the chair (in this case, whoever did the #startmeeting)
18:23:21 <anil_rao> the idea is to remove some fo the confusion in the last version and to accomodate some of the comments into the body of the document
18:23:24 <marios> s3wong: i c thx
18:24:50 <regXboi> all: it is possible for a chair to add/remove other chairs via #chair/#unchair (if they so wish and the meetbot has that command compiled in)
18:24:58 <s3wong> SumitNaiksatam: anil_rao is doing update on TapaaS
18:25:23 <anil_rao> In addition, we also plan to put up some WIP code for early review shortly.
18:25:43 <regXboi> but, until Sumit comes back, we have to go to one of the ops to get the meeting unstuck
18:26:16 <marios> regXboi: we could still just continue through the agenda anyway
18:26:20 <marios> regXboi: this is all in the minutes
18:26:31 <s3wong> regXboi: meetbot from OpenStack channels will allow anyone to #endmeeting after one hour
18:26:39 <regXboi> yes, sorta...
18:26:44 <marios> OH, except the endmeeting
18:26:47 <regXboi> and I'm not saying we shouldn't go on
18:26:50 <marios> didn't think about that
18:26:53 <SumitNaiksatam> folks i am back, i think
18:27:03 <regXboi> just the minutes will look a little .... odd
18:27:11 <SumitNaiksatam> let me end the meeting, so in case i get bounced out, the meeting does not linger
18:27:15 <marios> regXboi: SumitNaiksatam you may want to endmeeting asap to at least capture the chat
18:27:23 <SumitNaiksatam> marios: exactly
18:27:25 <marios> err sorry regXboi that was meant for sumit
18:27:26 <SumitNaiksatam> #endmeeting