18:01:32 <SumitNaiksatam> #startmeeting networking_policy
18:01:34 <openstack> Meeting started Thu Oct 16 18:01:32 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:37 <openstack> The meeting name has been set to 'networking_policy'
18:01:41 <SumitNaiksatam> #info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy
18:01:56 <s3wong> glebo is gone...
18:02:08 <SumitNaiksatam> any big announcements or info that anyone would like to share upfront?
18:02:17 <SumitNaiksatam> s3wong: he will back soon :-)
18:02:37 <SumitNaiksatam> one piece of information i wanted to share was the GBP design summit session
18:02:51 <SumitNaiksatam> #link http://kilodesignsummit.sched.org/event/98dc4255384e340682137c8a7ee7e60d#.VD_6XIt4r4w
18:03:15 <SumitNaiksatam> this is a separate session in the “other projects” track (in the design summit)
18:03:48 <SumitNaiksatam> i am of course talking in the context of the upcoming Paris summit (should have mentioned that before) ;-)
18:03:50 <s3wong> cool
18:03:56 <SumitNaiksatam> s3wong: yeah :-)
18:04:04 <s3wong> SumitNaiksatam: do we know if we are getting Neutron design summit slots?
18:04:13 <SumitNaiksatam> s3wong: not sure
18:04:27 <SumitNaiksatam> s3wong: we will leave that to community to decide the neutron priority
18:04:37 <SumitNaiksatam> okay we can discuss the details of the session in a separate agenda topic
18:04:40 <s3wong> SumitNaiksatam: sure
18:05:01 <SumitNaiksatam> any other info/announcements?
18:05:36 <SumitNaiksatam> #topic Specs in review
18:05:43 <SumitNaiksatam> #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy-specs+branch:master,n,z
18:06:11 <SumitNaiksatam> some of the ones mentioned above already have implementation patches posted against them
18:06:24 <SumitNaiksatam> we are little behind on the reviews
18:06:56 <rkukura> SumitNaiksatam: I should be able to make some progress on these today.
18:07:04 <rms_13> It took time for jenkins to be happy... Glad he is smiling now :)
18:07:15 <SumitNaiksatam> rkukura: thanks
18:07:35 <rkukura> SumitNaiksatam: Sorry, I actually meant the code reviews, but I need to review the specs as well.
18:07:38 <SumitNaiksatam> rms_13: yes, but we are currently discussing the specs, implementation patches are next :-)
18:07:47 <SumitNaiksatam> rkukura: yeah, this is the specs review
18:08:14 <SumitNaiksatam> LouisF: good to see your specs, thanks for posting promptly!
18:08:15 <hemanthravi> need review of the gbp chaining spec https://review.openstack.org/#/c/125876/
18:08:41 <SumitNaiksatam> hemanthravi: sorry i am behind on that
18:08:56 <hemanthravi> SumitNaiksatam, when you get some time
18:09:38 <SumitNaiksatam> i see that only kevinbenton has reviewed
18:09:44 <SumitNaiksatam> the ones that were assigned to him
18:09:57 <SumitNaiksatam> ivar-lazzaro: rkukura do you have issues with kevinbenton’s comments?
18:09:59 <LouisF> SumitNaiksatam: thanks
18:10:20 <SumitNaiksatam> LouisF: you want to update the commite message title to reflect the name of the spec
18:10:21 <ivar-lazzaro> SumitNaiksatam: nope, I'm going to push the new version of the patch in seconds :)
18:10:26 <SumitNaiksatam> ivar-lazzaro: sweet
18:10:39 <LouisF> SumitNaiksatam: i will be updating them
18:10:43 <rkukura> SumitNaiksatam: I think I clarified kevinbenton’s concern about L2P, and am updaing the extension driver spec.
18:10:49 <SumitNaiksatam> LouisF: great, thanks
18:10:56 <SumitNaiksatam> rkukura: ok great
18:11:07 <SumitNaiksatam> rkukura: sorry i was not following the discussion thread
18:11:15 <SumitNaiksatam> glebo: welcome back!
18:11:25 <Guest96350> *sorry he's late, irc client connectivity issues, dkw*
18:12:11 <Guest96350> #nick glebo
18:12:15 <SumitNaiksatam> can i also plug a request to review the spec update that i put: #link https://review.openstack.org/127913
18:12:56 <SumitNaiksatam> i am happy to spend a few minutes here if someone wants to dig deeper on the specs that are in review currently
18:13:08 <SumitNaiksatam> on -> into
18:13:23 <SumitNaiksatam> if not we will move to the implementation patches
18:14:07 <SumitNaiksatam> ok moving on
18:14:19 <SumitNaiksatam> #topic Implementation patches in review
18:14:36 <SumitNaiksatam> wait
18:14:38 <SumitNaiksatam> #undo
18:14:39 <openstack> Removing item from minutes: <ircmeeting.items.Topic object at 0x3399490>
18:14:52 <SumitNaiksatam> #topic Current DB approach: SSDC
18:15:09 <SumitNaiksatam> want to bring this to everyone’s notice since this patch was already approved
18:15:42 <s3wong> SumitNaiksatam: so no problem with the release folks?
18:16:04 <SumitNaiksatam> per discussion in the last meeting (and on friday in the review meeting), ivar-lazzaro posted a new patch for the single schema different series approach (SSDS)
18:16:10 <SumitNaiksatam> s3wong: i am not sure
18:16:20 <SumitNaiksatam> ivar-lazzaro: rkukura: s3wong’s question ^^^
18:16:43 <ivar-lazzaro> s3wong: we don't know yet, but we needed this to be in place to fix dependency issues
18:16:50 <rkukura> ivar-lazzaro: +1
18:17:01 <SumitNaiksatam> yes, installation was broken without a fix
18:17:13 <SumitNaiksatam> so in the interest of expediency, i approved this patch
18:17:21 <ivar-lazzaro> s3wong: we can always go back to the DSDC approach if the problem arises
18:17:31 <SumitNaiksatam> i believe at least rkukura approves of this
18:17:40 <SumitNaiksatam> please let us know if there are concerns
18:17:52 <s3wong> ivar-lazzaro: sure
18:17:55 <ivar-lazzaro> But in general I would suggest to start investigating the issue with the packagers before it's too late :)
18:17:57 <SumitNaiksatam> i have tested that devstack install now works with the fix in place
18:18:42 <SumitNaiksatam> ivar-lazzaro: can you quickly summarize for the benefit of everyone what the current approach is?
18:18:54 <ivar-lazzaro> SumitNaiksatam: sure
18:18:55 <SumitNaiksatam> ivar-lazzaro: sorry to put you on the spot
18:19:23 <ivar-lazzaro> The current approach is to use a different "version table" in the same database/schema Neutron is using
18:19:47 <ivar-lazzaro> so we are basically still tied to the Neutron's database, but we run a completely different migration chain
18:19:54 <SumitNaiksatam> ivar-lazzaro: good summary
18:20:06 <ivar-lazzaro> which means that Neutron can upgrade just fine as long as table names are unique
18:20:16 <ivar-lazzaro> (same goes for gbp ofc)
18:20:17 <SumitNaiksatam> ivar-lazzaro: and thanks so much for working on this so expeditiously, it was a blocking issue
18:20:38 <SumitNaiksatam> okay any more questions on the current approach?
18:20:51 <SumitNaiksatam> so for anyone posting a new migration, nothing changes
18:21:03 <ivar-lazzaro> Nope
18:21:12 <SumitNaiksatam> just change the HEAD in the gbp repo, and point to the right down migration
18:21:24 <ivar-lazzaro> this approach is much cleaner than DSDC
18:21:29 <SumitNaiksatam> ivar-lazzaro: did I summarize it correctly?
18:21:38 <ivar-lazzaro> but less safe packaging wise
18:21:45 <ivar-lazzaro> SumitNaiksatam: that's perfect :)
18:21:47 <rkukura> Why less safe?
18:22:12 <SumitNaiksatam> certainly simpler!
18:22:20 <ivar-lazzaro> rkukura: because we don't know if using the same database is acceptable overall
18:22:39 <ivar-lazzaro> rkukura: once we know that for sure I'll be happier :-)
18:22:43 <rkukura> I think that is more of an architectural issue than a packaging issue
18:22:50 <rkukura> But we can ask around
18:22:55 <SumitNaiksatam> rkukura: sure
18:22:57 <SumitNaiksatam> ok moving on
18:23:08 <rkukura> For Juno, this is a service plugin within neutron-server, after all
18:23:08 <SumitNaiksatam> ivar-lazzaro: thanks again!
18:23:15 <SumitNaiksatam> rkukura: agreed!
18:23:16 <ivar-lazzaro> SumitNaiksatam: np! :-)
18:23:21 <SumitNaiksatam> #topic Implementation patches in review
18:23:34 <SumitNaiksatam> so we had a long review meeting (i believe it was Oct 14th)
18:23:55 <Guest96350> nick/ glebo_
18:23:56 <SumitNaiksatam> this was an IRC meeting, you can find the logs here: #link https://wiki.openstack.org/w/images/7/7f/Gbp-patch-reviews-10142014.pdf
18:24:14 <SumitNaiksatam> we got out of the meeting with some AI and review owners
18:24:45 <SumitNaiksatam> this has been captured here: #link https://docs.google.com/spreadsheets/d/1VAcYODD5fA_t2yleb95pTlIxD-btnUllZTN-uhNrsh4/edit#gid=0
18:25:30 <Guest96350> lo mestery
18:25:55 <SumitNaiksatam> so we are still a bit behind on the reviews here
18:26:07 <SumitNaiksatam> we merged GPM-RMD-1, did we?
18:26:15 <Guest96350> all: having serious irc issues this morning, so Guest96350 = glebo
18:26:34 <Guest96350> *hope y'all can live w/ it*
18:26:37 <SumitNaiksatam> Guest96350: np
18:26:51 <SumitNaiksatam> ok we did
18:27:07 <SumitNaiksatam> on GP-API-2, rms_13 you have a -1
18:27:08 <Guest96350> *will repost the mapping once in a while to help any new-comers*
18:27:19 <SumitNaiksatam> i believe i have addressed your comments
18:27:20 <rkukura> I just updated the gpm-rmd-1 review with links to the LP bugs I filed.
18:27:35 <rms_13> Ok. Will take a look
18:27:44 <SumitNaiksatam> rkukura: thanks
18:28:04 <SumitNaiksatam> rms_13: i addressed them yesterday evening :-P
18:28:06 <s3wong> rkukura: gpm-rmd-1 is already merged, right?
18:28:11 <SumitNaiksatam> s3wong: yes
18:28:19 <hemanthravi> ivar-lazzaro, does hierachical contracts patch need a rebase
18:28:22 <rkukura> s3wong: yes, just wanted to record that the bugs were filed
18:28:24 <SumitNaiksatam> s3wong: i think rkukura added as record
18:28:31 <s3wong> rkukura: sure
18:28:40 <hemanthravi> ivar-lazzaro, service-chain patches dependent on this are failing too
18:28:41 <ivar-lazzaro> hemanthravi: yep
18:28:48 <SumitNaiksatam> hemanthravi: i believe it does, i did not rebase it yesterday when i was rebasing others
18:29:00 <SumitNaiksatam> hemanthravi: okay i did not realize that
18:29:13 <ivar-lazzaro> hemanthravi: there are merge conflicts, will address right after the meeting
18:29:13 <SumitNaiksatam> i can do it later in the day if ivar-lazzaro doesnt get to it
18:29:22 <hemanthravi> ivar-lazzaro, thanks
18:29:47 <SumitNaiksatam> for GP-DB-2
18:30:17 <SumitNaiksatam> hemanthravi: and ivar-lazzaro you +2’ed
18:30:33 <SumitNaiksatam> if no one has objections, can someone +A this?
18:30:47 <ivar-lazzaro> SumitNaiksatam: there's still a dict/set issue (just like the contract patch) but didn't want to block it
18:30:50 <SumitNaiksatam> sorry to get into the weeds here with the specific patches
18:31:05 <ivar-lazzaro> SumitNaiksatam: I can approve it
18:31:38 <SumitNaiksatam> ivar-lazzaro: ah okay, i believe you added that comment a couple of mins back :-)
18:31:47 <ivar-lazzaro> SumitNaiksatam: yes :)
18:31:53 <SumitNaiksatam> ivar-lazzaro: but my bad, i should have checked for it when i was fixing the other stuff
18:31:59 <SumitNaiksatam> ivar-lazzaro: you can file a bug
18:31:59 <Guest96350> reminder: Guest96350 = glebo *suffering from irc client disfunction syndrome this morning*
18:32:08 <SumitNaiksatam> Guest96350: ;-)
18:32:21 <SumitNaiksatam> Guest96350: we at least know you are not masquerading! ;-)
18:32:33 <ivar-lazzaro> \ME starts doubting that Guest96350 really is glebo :-)
18:32:43 <SumitNaiksatam> ivar-lazzaro: i can assure you he is
18:32:52 <SumitNaiksatam> GP-PLG-3
18:32:52 <ivar-lazzaro> SumitNaiksatam: j/k :)
18:32:58 <Guest96350> SumitNaiksatam: well, reverse masquerading, aka parading
18:33:03 <SumitNaiksatam> who is the second core on this?
18:33:30 <SumitNaiksatam> sorri, i meant GP-PLG-2
18:33:43 <SumitNaiksatam> rkukura: that would be you ;-)
18:33:53 <Guest96350> ivar-lazzaro: who is glebo anyway, really?
18:33:53 <rkukura> yep
18:34:02 <SumitNaiksatam> hopefully you can take a quick look at it
18:34:17 <ivar-lazzaro> Guest96350: maybe we all are!
18:34:30 <SumitNaiksatam> GP-API-3
18:34:35 <rkukura> SumitNaiksatam: Yes, I hope to make some progress on the code reviews today
18:34:42 <SumitNaiksatam> rms_13: you are guilty again ;-P
18:34:55 <rms_13> what did I do now?
18:35:03 <rms_13> :)
18:35:09 <SumitNaiksatam> rms_13: just pulling your leg
18:35:57 <SumitNaiksatam> rms_13: you put the -1 saying that jenkins was not happy, except that jenkins had not voted
18:36:06 <SumitNaiksatam> rms_13: but it has now and its happy :-)
18:36:22 <Guest96350> ivar-lazzaro: *hears familiar tune, then lyrics, "your own... personal... glebo"
18:36:41 <SumitNaiksatam> rkukura: i believe you will be looking at GP-API-3 as well
18:37:03 <rms_13> May be the session was not upto date... Ya its passing so I will do +2.
18:37:16 <rkukura> SumitNaiksatam: yes
18:37:26 <SumitNaiksatam> for GP-DB-3 i believe i have addressed the comments, ivar-lazzaro and rms_13 can you take a look?
18:37:35 <ivar-lazzaro> SumitNaiksatam: sure
18:37:37 <rms_13> Rebase after Rebase and that after +2 ... :)
18:37:40 <rms_13> Sure I will
18:37:53 <SumitNaiksatam> rms_13: great, thanks!
18:38:14 <SumitNaiksatam> GP-PLG-3
18:38:46 <SumitNaiksatam> i think this is good to go, we can wait for the preceeding patches to merge and then +A this
18:39:05 <SumitNaiksatam> btw, lets merge the patches in order (when we come to it) ;-)
18:39:24 <SumitNaiksatam> i am not sure Jenkins will allow a merge otherwise
18:39:36 <SumitNaiksatam> that brings us to GPM-RMD-SG
18:39:53 <rms_13> Ya that is the reason I did not +A after Hemanth did another +2 on one of them.
18:39:57 <SumitNaiksatam> so myself and rkukura are on the hook, we will get to it once the backlog clears
18:40:11 <SumitNaiksatam> rms_13: sure
18:40:35 <SumitNaiksatam> and we also have the hierarchical contracts patch
18:40:45 <SumitNaiksatam> thats Hemanth and me
18:40:52 <SumitNaiksatam> i think hemanth has reviewed to some extent
18:40:56 <SumitNaiksatam> i havent
18:40:58 <SumitNaiksatam> will get to that
18:41:18 <SumitNaiksatam> so once we are done with these foundation patches, we have a bunch of service chain patches to get to
18:41:33 <SumitNaiksatam> perhaps doesnt make sense to spend time on discussing those right now
18:41:47 <SumitNaiksatam> but please keep those patches in mind as well
18:42:00 <ivar-lazzaro> SumitNaiksatam: there's another one
18:42:04 <ivar-lazzaro> SumitNaiksatam: lost in the bunch
18:42:11 <SumitNaiksatam> ivar-lazzaro: ah sorry, did i miss something
18:42:13 <ivar-lazzaro> SumitNaiksatam: which rkukura will certainly appreciate :)
18:42:23 <ivar-lazzaro> #link https://review.openstack.org/#/c/128148/
18:42:51 <ivar-lazzaro> since we are now depending from Neutron only for UTs, we can forget about pypi and directly pull from their repo
18:42:56 <SumitNaiksatam> ivar-lazzaro: oh my bad, yeah that is critical bug fic
18:42:58 <ivar-lazzaro> the official one
18:42:59 <SumitNaiksatam> *fix
18:43:23 <rkukura> ivar-lazzaro: So it does work?
18:43:48 <ivar-lazzaro> rkukura: yeah now it does, because we don't need to pull the repo anymore when running the installation script
18:44:00 <ivar-lazzaro> rkukura: it's only needed for UTs which have always worked
18:44:11 <ivar-lazzaro> rkukura: need to point to stable/juno though
18:44:12 <SumitNaiksatam> ivar-lazzaro: oh sorry, i mixed up
18:44:24 <rkukura> ivar-lazzaro: was just going to mention stable-juno
18:44:29 <SumitNaiksatam> ivar-lazzaro: i thought you were referring to the delete object chain bug
18:44:50 <ivar-lazzaro> SumitNaiksatam: that's another one, I didn't have the chance to test it yet
18:44:51 <SumitNaiksatam> #link https://review.openstack.org/#/c/126740
18:45:15 <SumitNaiksatam> yes, we have lots of things in flight, if you are still wondering! :-)
18:45:24 <SumitNaiksatam> okay, so moving on
18:45:40 <SumitNaiksatam> #topic GBP Design Summit session
18:45:54 <SumitNaiksatam> as i mentioned earlier - #link http://kilodesignsummit.sched.org/event/98dc4255384e340682137c8a7ee7e60d#.VD_6XIt4r4w
18:46:00 <SumitNaiksatam> we need to plan for this
18:46:17 <SumitNaiksatam> not sure that we need to discuss this today
18:46:34 <SumitNaiksatam> we have time until the summit
18:46:57 <SumitNaiksatam> s3wong: you were mentioning something about this earlier?
18:47:26 <Guest96350> SumitNaiksatam: 2 wks away now, not too much time, really
18:47:35 <SumitNaiksatam> fyi, the GBP conference track session is #link https://openstacksummitnovember2014paris.sched.org/popular#.VD5YAYvF_3B
18:47:39 <SumitNaiksatam> Guest96350: true
18:47:49 <SumitNaiksatam> Guest96350: we just got notification that we have been allocated this slot
18:48:11 <SumitNaiksatam> Guest96350: so in the process of planning, and the rest of the team just got to know about it as well
18:48:16 <SumitNaiksatam> Guest96350: but point well taken
18:48:30 <SumitNaiksatam> Guest96350: in general, this will be a “design” discussion
18:48:36 <SumitNaiksatam> Guest96350: i will get the etherpad started for it
18:48:47 <SumitNaiksatam> Guest96350: so that we can start adding the topics that we want to discuss
18:49:10 <SumitNaiksatam> and over time we can add structure
18:49:17 <SumitNaiksatam> does that sound good to everyone? :-)
18:49:29 <rkukura> SumitNaiksatam: +1
18:49:29 <SumitNaiksatam> my earlier comments not specifically targeted at Guest96350 :-)
18:49:34 <s3wong> SumitNaiksatam: sorry, was out for a moment
18:49:34 * Guest96350 sees SumitNaiksatam take his 842nd action item of the mtg ;-)
18:49:43 <SumitNaiksatam> Guest96350: :-)
18:50:07 <s3wong> SumitNaiksatam: we should plan for the conference presentation, as it happens on the first day of the summit :-)
18:50:11 <SumitNaiksatam> s3wong: no worries
18:50:16 <SumitNaiksatam> s3wong: ah on that
18:50:26 <SumitNaiksatam> s3wong: i was planning to bring that up in the open discussion
18:50:33 <SumitNaiksatam> s3wong: i did update the slides
18:50:40 <SumitNaiksatam> s3wong:  at least with those from the policy summit
18:50:44 <SumitNaiksatam> s3wong: i will send them out
18:50:47 <s3wong> SumitNaiksatam: and of course the "other project" design summit also :-)
18:50:55 <s3wong> SumitNaiksatam: OK
18:50:56 <SumitNaiksatam> s3wong: i believe others are working on the slides as well
18:51:09 <SumitNaiksatam> s3wong: so will send it as soon as i get that input
18:51:12 <s3wong> SumitNaiksatam: others? I am not :-)
18:51:22 <SumitNaiksatam> s3wong: mandeep and mikeC
18:51:44 <SumitNaiksatam> ok thats a good way to segue to the open discussion
18:51:48 <SumitNaiksatam> #topic Open Discussion
18:51:50 <Guest96350> SumitNaiksatam: so those will be sent to ML?
18:52:07 <Guest96350> SumitNaiksatam: slides, I meant
18:52:18 <SumitNaiksatam> Guest96350: perhaps not the ML right away, they will posted on the openstack site after the presentation
18:52:47 <SumitNaiksatam> Guest96350: we expect to iterate until the presentation day, so might not be worthwhile sending the draft versions to the ML in advance
18:53:00 <SumitNaiksatam> Guest96350: can certainly share within the team for feedback and review
18:53:03 <Guest96350> SumitNaiksatam: so, sent unicast to "interested parties for reivew"?
18:53:11 <SumitNaiksatam> Guest96350: yes, absolutely
18:53:24 <SumitNaiksatam> ok we are in open discussion
18:53:26 <Guest96350> SumitNaiksatam: cross-talk; ack
18:53:45 <SumitNaiksatam> LouisF: i noticed you and cathy_ were following up on the Congress integration?
18:53:54 <SumitNaiksatam> LouisF: thanks for following up on that thread
18:54:06 <SumitNaiksatam> LouisF: any update you would like to give to the rest of the team
18:54:24 <SumitNaiksatam> or perhaps on the blueprints you posted?
18:55:24 <SumitNaiksatam> perhaps LouisF is away
18:56:07 <SumitNaiksatam> s3wong: you have any updates on that front?
18:56:26 <SumitNaiksatam> s3wong: you mentioned the operators track as well for socializing GBP?
18:57:23 <SumitNaiksatam> i think we lost a few people since we are getting close to lunch time here on the west coast :-)
18:57:36 <nbouthors> We are dividing the propose BluePrint in 3 parts.
18:57:37 <ivar-lazzaro> SumitNaiksatam: ahah
18:57:53 <SumitNaiksatam> nbouthors: nice to know, and good to see you here :-)
18:58:46 <nbouthors> hi
18:59:05 <nbouthors> I work with Louis on the BP
18:59:23 <SumitNaiksatam> nbouthors: yes of course, sorry i did not realize you were in the meeting today
18:59:47 <nbouthors> Also, it is nice to see that OVS is starting to implement L7 classification.
18:59:48 <SumitNaiksatam> so the blueprint which LouisF posted is a joint work between nbouthors LouisF and cathy_
18:59:55 <SumitNaiksatam> nbouthors: right?
19:00:00 <nbouthors> SumitNaiksatam: yes
19:00:20 <SumitNaiksatam> nbouthors: yes, noticed your pointer earlier today regarding the OVS work
19:00:25 <SumitNaiksatam> nbouthors: will follow up
19:00:41 <nbouthors> THought it could be of interest
19:00:59 <SumitNaiksatam> nbouthors: i think the team will be happy to get some pointers to docs or references if you have any
19:01:11 <SumitNaiksatam> nbouthors: we can take it offline
19:01:13 <SumitNaiksatam> okay we are over time
19:01:15 <nbouthors> SumitNaiksatam:  Wil do
19:01:16 <SumitNaiksatam> thanks everyone
19:01:19 <SumitNaiksatam> nbouthors: thanks
19:01:22 <nbouthors> Bye
19:01:24 <s3wong> SumitNaiksatam: sorry, again stepping out
19:01:35 <SumitNaiksatam> until next week (we might have another review meeting if we dont make enough progress)
19:01:41 <SumitNaiksatam> bye all
19:01:45 <rkukura> bye
19:01:45 <SumitNaiksatam> #endmeeting