Wednesday, 2016-07-13

*** piet has quit IRC00:00
*** yamamoto has joined #openstack-meeting-300:02
*** markvoelker has quit IRC00:02
*** ddieterly has joined #openstack-meeting-300:04
*** yushiro has joined #openstack-meeting-300:10
*** yushiro has left #openstack-meeting-300:10
*** markvoelker has joined #openstack-meeting-300:11
*** markvoelker has quit IRC00:14
*** markvoelker has joined #openstack-meeting-300:14
*** galstrom is now known as galstrom_zzz00:28
*** Sukhdev has quit IRC00:29
*** sarob has joined #openstack-meeting-300:31
*** ddieterly is now known as ddieterly[away]00:32
*** toddjohn has quit IRC00:33
*** asettle has joined #openstack-meeting-300:36
*** ddieterly[away] has quit IRC00:36
*** pvaneck has quit IRC00:37
*** Swami has quit IRC00:37
*** hoangcx has joined #openstack-meeting-300:38
*** spzala has joined #openstack-meeting-300:38
*** asettle has quit IRC00:40
*** kzaitsev_mb has quit IRC00:42
*** spzala has quit IRC00:43
*** mtanino has quit IRC00:53
*** ddieterly has joined #openstack-meeting-300:55
*** piet has joined #openstack-meeting-300:57
*** dimtruck is now known as zz_dimtruck00:59
*** sarob has quit IRC00:59
*** zz_dimtruck is now known as dimtruck01:01
*** zhurong has joined #openstack-meeting-301:06
*** ddieterly has quit IRC01:08
*** piet has quit IRC01:17
*** markvoelker has quit IRC01:25
*** baoli has joined #openstack-meeting-301:25
*** dimtruck is now known as zz_dimtruck01:27
*** xiaohhui has quit IRC01:28
*** xiaohhui has joined #openstack-meeting-301:29
*** sarob has joined #openstack-meeting-301:33
*** honghuixiao_ has joined #openstack-meeting-301:33
*** xiaohhui has quit IRC01:33
*** toddjohn has joined #openstack-meeting-301:34
*** sarob has quit IRC01:37
*** s3wong has quit IRC01:37
*** toddjohn has quit IRC01:38
*** spzala has joined #openstack-meeting-301:39
*** kzaitsev_mb has joined #openstack-meeting-301:42
*** honghuixiao_ has quit IRC01:42
*** baoli has quit IRC01:42
*** ociuhandu has quit IRC01:43
*** spzala has quit IRC01:43
*** xiaohhui has joined #openstack-meeting-301:44
*** zz_dimtruck is now known as dimtruck01:51
*** ccamacho has joined #openstack-meeting-301:53
*** xiaohhui has quit IRC02:17
*** xiaohhui has joined #openstack-meeting-302:18
*** xiaohhui has quit IRC02:21
*** xiaohhui has joined #openstack-meeting-302:22
*** ddieterly has joined #openstack-meeting-302:23
*** ddieterly has quit IRC02:28
*** ddieterly has joined #openstack-meeting-302:32
*** rossella_s has quit IRC02:40
*** rossella_s has joined #openstack-meeting-302:40
*** vishwanathj has quit IRC02:41
*** vishwanathj has joined #openstack-meeting-302:42
*** baoli has joined #openstack-meeting-302:42
*** ddieterly is now known as ddieterly[away]02:44
*** ddieterly[away] has quit IRC02:45
*** mdbooth has quit IRC02:46
*** mdbooth has joined #openstack-meeting-302:48
*** ajo has quit IRC03:00
*** spzala has joined #openstack-meeting-303:00
*** coolsvap has joined #openstack-meeting-303:02
*** ajo has joined #openstack-meeting-303:03
*** iyamahat has quit IRC03:04
*** toddjohn has joined #openstack-meeting-303:05
*** spzala has quit IRC03:05
*** coolsvap has quit IRC03:10
*** toddjohn has quit IRC03:11
*** vishwanathj has quit IRC03:17
*** vishwanathj has joined #openstack-meeting-303:18
*** woodster_ has quit IRC03:19
*** Rockyg has quit IRC03:25
*** xiaohhui has quit IRC03:44
*** xiaohhui has joined #openstack-meeting-303:46
*** Sukhdev has joined #openstack-meeting-303:48
*** chandanc_ has joined #openstack-meeting-303:50
*** SarathMekala has joined #openstack-meeting-303:52
*** markvoelker has joined #openstack-meeting-303:55
*** yushiro has joined #openstack-meeting-303:57
njohnstonhi all03:59
yushironjohnston, hi !03:59
njohnstonyushiro: Hello my friend, how are you?03:59
SarathMekalahi all03:59
yushironjohnston, fine thanks :)03:59
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Jul 13 04:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
chandanc_hello all04:00
njohnston#chair xgerman SridarK04:00
openstackWarning: Nick not in channel: SridarK04:00
openstackCurrent chairs: SridarK njohnston xgerman04:00
xgermanO/04:00
*** SridarK has joined #openstack-meeting-304:00
*** padkrish has joined #openstack-meeting-304:00
mickeysHi04:00
SridarKHi All04:00
njohnstonHello, everyone!  I apologize for missing the last meeting, I was at a family gathering.  Thanks xgerman for chairing!04:00
padkrishhi all04:01
xgermanY.w.04:01
*** yamamoto has quit IRC04:01
*** spzala has joined #openstack-meeting-304:01
njohnstonHello, SridarK!  Welcome back.04:01
*** fawadkhaliq has joined #openstack-meeting-304:01
SridarKnjohnston: can u pls run the mtg - still travelling04:01
*** sarob has joined #openstack-meeting-304:01
njohnstonSridarK: Of course04:01
SridarKnjohnston: not sure on connectivity04:01
njohnston#topic announcements04:01
*** openstack changes topic to "announcements (Meeting topic: fwaas)"04:01
njohnstonTomorrow, 7/14, is the date for N-204:02
xgerman+104:02
njohnstonarmax said in the last Neutron team meeting that end of August was the practical cutoff for anything that needs to into g-r, like any client commands or neutron-lib04:02
njohnstonI don't think that affects us too badly though... hopefully.04:02
*** vishwanathj has quit IRC04:02
SridarKsome actions on vendor stuff - i will follow up on that, for cisco - i am working with some folks and will take care of it04:02
SridarKfor varmor - will sync with s3wong04:03
njohnstonExcellent.  I saw one vendor already moved their stuff out.04:03
*** sarob has quit IRC04:03
SridarKnjohnston: +1 on the Aug cut off04:03
njohnston#topic FWaaS v204:03
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:03
njohnstonLet04:04
njohnstonLet's start with Paddu, you sent out a few emails.04:04
njohnstonpadkrish04:04
padkrishnjohnston# yes, to summarize, i was asking if we can combine the versioned object patch with the infra changes like queue04:05
padkrishsorry, like notification driver manager, notification queue etc like what's there for QoS04:05
SridarKpadkrish: also is the plan that there is a good common chunk across L2 and L3 ?04:06
*** spzala has quit IRC04:06
njohnstonpadkrish: Is it going well?  Do you feel close to having a change you can put into gerrit?04:06
padkrishthis portion should be common, what from whatever i can see...others can correct me...04:06
padkrishi will try to put a WIP by this week04:06
padkrishstill unit test code is not there yet04:07
njohnstonpadkrish: Thanks, I look forward to seeing it04:07
SridarKpadkrish: there could be some differences based on L2 or L3 port differences04:07
njohnstonpadkrish: Don't wait on getting unit tests done, put it up there and perhaps we can help with unit tests04:07
padkrishnjohnston# sure, me too ;)04:07
SridarKpadkrish: if it is easier - u can also commonize as a refactor04:07
padkrishnjohnston# absolutely, thats the plan04:08
SridarKas the next step04:08
njohnstonok, good.04:08
*** armax has quit IRC04:08
padkrishSridarK# sure, it certainly needs to be refactored...since i don't believe we need separate notif mgrs/queues for QoS and FWaaS04:08
SridarKpadkrish: ok04:08
njohnstonSarathMekala and chandanc_: How is your work going?04:09
padkrishbut, i need to think through this a bit more...may be as a first step, let's have it separate to get the functionality in?04:09
SridarKpadkrish: i think that is reasonable04:09
*** tonytan4ever has joined #openstack-meeting-304:09
*** armax has joined #openstack-meeting-304:09
yushiropadkrish, would you please sync with me after discussion?  Maybe I think its affect to my WIP.04:10
SarathMekalaWe hit some issues where SG and FW were clobbering the ACCEPT rules of each other04:10
chandanc_njohnston: we are at the second patch for the iptables manager.04:10
padkrishyushiro# sure...04:10
njohnstonchandanc_: I see https://review.openstack.org/#/c/333338/ doesn't look like it's had anything happen in July... anything we can do to help?04:10
yushiropadkrish, Thanks.04:10
SarathMekalaand a new solution which solves both the clobbering and ordering issues was arrived at04:10
SarathMekalathe same has been updated in the doc04:11
SridarKSarathMekala: that is good04:11
njohnstonSarathMekala: Excellent!04:11
mickeysThe mechanism in the doc looks like it will work, so you have all the ideas that you need to make it work. I don't think the actual organization of the chains is nailed down yet.04:12
mickeysDid you have code changes around the last idea?04:12
chandanc_I have one comments from Sarath, do you have any review comments ? any enhancement ?04:12
mickeysI replied by email directly.04:12
SarathMekalawe will work on the idea this week.. and post a WIP review04:13
mickeysRegarding the chains themselves, the jump from FORWARD to neutron-openvswi-FORWARD happens in IptablesManager. I don't think you can change that. You have to work with it or around it.04:13
njohnstonNext, yushiro please tell us how your WIP is going?04:14
SarathMekalathanks Mickey... will check it out today04:15
yushironjohnston, yes, currently, my patch is slow progress(sorry...) Yesterday, I've just updated my patch for reflecting chandanc_ and SarathMekala's comment.04:15
njohnstonI haven't seen shwetaap recently, I will probably ping her change to see how it's going04:17
njohnstonSridarK: I know you're travelling, any thoughts on your end-to-end testing?04:17
SridarKnjohnston: i think she had made some progress b4 i left on PTO04:17
SridarKnjohnston: yes i have some changes to the db patch - was trying to get this to a logical point and push some code up04:18
SridarKi am trying to create a firewall - group04:18
SridarKbut last week things have been tough for me to get something done04:18
SridarKi will target to find some time this week to get that taken care off04:18
SridarKand i am back home on Tue04:19
SridarKnext week04:19
njohnstonSridarK: OK.  Please let us know if there is any part of it that we can handle while you're out.04:19
*** baoli has quit IRC04:20
njohnstonor that you could transition to us, to keep the velocity going04:20
*** piet has joined #openstack-meeting-304:20
SridarKnjohnston: on the db patch once i push a skeleton up for Create - u will have some work04:20
SridarKnjohnston: will do04:20
njohnstonSridarK: Sounds good - push to the db change as soon as you feel comfortable.04:20
SridarKnjohnston: ok thx04:20
njohnstonOK, did I miss anyone?04:21
njohnstonOK, moving on then.04:22
njohnston#topic L3 aget extension04:22
*** openstack changes topic to "L3 aget extension (Meeting topic: fwaas)"04:22
njohnstonThe first patch, to make the l2 agent extension framework generic, looks like it is close: https://review.openstack.org/32970104:22
*** sdake has joined #openstack-meeting-304:22
njohnstonajo and ihrachys both said nice things about it04:23
SridarKnjohnston: great04:23
yushironjohnston, awesome!04:23
SridarKnjohnston: on the L3 agent - just before the long week - had a call with padkrish and mfranc213_ - to go over fwaas L3 things04:23
SridarKnjohnston: i think i have answered all open questions on that front04:24
njohnstonSridarK: Yes, I believe you have, and mfranc213_ and I have been working since then :-)04:24
njohnstonit was very helpful, mfranc213_ told me04:24
SridarKnjohnston: great - let me know if there are any missing pieces and we can talk04:24
njohnstonBut that change doesn't change much code, it just rearranges code that is there.  I have filed the second patch in the sequence, https://review.openstack.org/339246/ "Implement L3 Agent Extension Manager", to add the new code04:24
*** Poornima has joined #openstack-meeting-304:25
SridarKnjohnston: i believe so too -04:25
SridarKnjohnston: i will look at this change set04:25
yushironjohnston, If your patch(https://review.openstack.org/#/c/339246) will be merged,  l3 agent extension is also necessary at FWaaS side, isn't it?04:26
*** julim has quit IRC04:26
njohnstonyushiro: Yes; this is just the code on the agent side, the last part is the code on the FWaaS side to plug in to the agent's extension capability04:26
njohnstonyushiro: Am I recalling correctly that you were working on that?04:26
yushironjohnston, Yes. I'm trying to push L3 agent side patch.  But I'm not sure about other resources dependency.04:27
njohnstonyushiro: Just push your patch, and then let's work on resolving the dependencies together. :-)04:28
yushironjohnston, Sure:)  I'll push ASAP.  However, I'd like to sync some works with you and padkrish.  Would you have some time to discuss after this IRC meeting?04:29
njohnstonyushiro: sure, I'll be awake for a little while :-)04:29
padkrishyushiro# sure04:29
*** yamamot__ has joined #openstack-meeting-304:29
njohnstonok04:30
njohnston#topic client04:30
*** openstack changes topic to "client (Meeting topic: fwaas)"04:30
njohnstonGiven that the client libraries close earlier than the others, I wanted to checkpoint and see for FWaaS v2 if we have a need to get client commands in place04:31
njohnstonBecause if so we need to start putting effort into that very soon04:31
SridarKnjohnston: we will need to04:31
SridarKnjohnston: as our resource definitions have changed04:31
njohnstonOK; I know that the change to make poython-neutronclient a plugin for openstack client either just merged or is about to04:32
njohnstonso we should get that change going in python-neutronclient soon04:32
SridarKnjohnston: are we allowed to make client changes before we have the backend in place ?04:32
njohnstonSridarK: We should be working on it in tandem, so the client change is ready.  I can tell you from experience, that no matter the state of the back-end, if we hit the early library freeze date and the client stuff is not merged, then the feature won't get into Newton, full-stop04:33
*** yamamot__ has quit IRC04:33
SridarKnjohnston: that i agree completely04:34
SridarKbut now should the library freeze date be the date for us to make sure we have some parts of the backend in place04:34
SridarKif we are allowed to have the client pieces in with some stubs or no backend then that can proceed to completion04:35
njohnstonyes, it should be the target date for at least a basic end-to-end so the CLI has something to use04:35
SridarKnjohnston: ok04:35
njohnstonSo SridarK knows what changes need to happen at the CLI level, does anyone else have that knowledge so we can start working on this?04:35
* njohnston respects Sridar's PTO 04:36
SridarKnjohnston: essentially the spec should outline this04:36
*** fawadkhaliq has quit IRC04:37
*** yamamot__ has joined #openstack-meeting-304:37
SridarKnjohnston: but some with some CLI experience can help us push things faster so we know how to plug in to the basic structure04:37
SridarK*someone with CLI experience ^^04:37
njohnstonI have a little, I can jump in and at least start roughing it in in a few days unless someone jumps in before me04:38
*** iyamahat has joined #openstack-meeting-304:38
SridarKmaybe if a few of us get together to figure this out and then whoever has bandwidth can jump in04:39
SridarKi am open to spending half a day with anyone next week after i am back04:39
SridarKto get a feel for the basic structure04:39
*** Fdaisuke_ has joined #openstack-meeting-304:39
njohnstonSounds good.  Whoever wants to, drop your name on the "client" section of the agenda: https://etherpad.openstack.org/p/fwaas-meeting04:39
njohnstonand we'll figure out a time that works for all04:40
*** Fdaisuke has quit IRC04:40
SridarKnjohnston: i can help u if someone is not picking this up this week04:40
SridarKnjohnston: perfect04:40
yushironjohnston, SridarK I'd like to help it.  Please let me call.04:40
SarathMekalaIf we can make some progress on the driver area .. I can chip in a bit..04:40
SridarKok perfect04:40
njohnstonExcellent, I love the interest! :-)04:40
njohnstonOK, we will talk about it again next meeting, since you will have just returned, yes?04:41
njohnston^ SridarK04:41
SridarKnjohnston: yes04:41
SridarKi get back on next Tue afternoon04:41
*** yamamot__ has quit IRC04:42
njohnston#topic Open Discussion04:42
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:42
njohnstonSchedule reminders: yushiro will be out for the 7/20 meeting, and I will be out for the 7/27 meeting04:42
SridarKnjohnston: thx04:42
chandanc_i will be out next week04:42
yushironjohnston, Thanks.04:42
SridarKshall we talk abt the virtual coding sprint04:43
mickeysYou all might want to check out https://bugs.launchpad.net/neutron/+bug/157748804:43
openstackLaunchpad bug 1577488 in neutron "[RFE]"Fast exit" for compute node egress flows when using DVR" [Wishlist,Triaged]04:43
mickeysThe way the discussion was going at the end, late May, early June, they are leaning towards moving away from symmetric routing of the gateway port in DVR.04:43
mickeysThat means even the gateway router port will not work for FWaaS (v1 or v2) with DVR04:44
mickeysEast/west router ports have long been a lost cause04:44
mickeysVIF ports will always work with DVR04:44
SridarKmickeys: thx hmm that will be a problem04:44
SridarKalthough right now v1 does not use the gw port - uses all the internal router ports04:45
njohnstonmickeys: Thanks, that is good to track04:45
mickeysFor DVR? I thought it was only the gateway port?04:45
SridarKbut that could be a problem as well04:45
*** pt_15 has quit IRC04:46
SridarKv1 puts the rules on qr*04:46
SridarKof the specified router04:46
mickeysInternal router ports are asymmetric, conntrack would only see one direction of traffic04:46
yushiromickeys, correct.04:47
SridarKon E - W04:47
njohnstonYeah, tough to tell between an established connection and a maliciously spoofed established connection when you only see one side of the conversation04:47
mickeysI thought you changed v1 so that it is internal router ports for centralized, but gateway port for DVR?04:47
*** piet has quit IRC04:47
SridarKno we did not use gw ports because of pre NAT post NAT specification of ip04:48
SridarKthere was some talk on that04:48
mickeysFIP?04:48
SridarKyes04:48
mickeysWith fast exit, you won't have symmetry across FIP either04:48
SridarKso the change was to target only the ns on the network node04:48
SridarKmickeys: yes will need to look more into this - thx for ptr04:49
*** flwang1 has quit IRC04:49
njohnstonok, so back to the topic of the virtual sprint04:50
SridarKyes04:50
*** sdake has quit IRC04:50
njohnstonI know we talked about a possible time period for it, but I don't recall when that was04:50
*** mrmartin has joined #openstack-meeting-304:50
SridarKi think a 2 or 3 1/2 day type thing could work well04:50
njohnstonagreed04:50
SridarKwe can have a couple of them over the next weeks04:50
SridarKnjohnston: i think u are out week of 7/25 ?04:51
SridarKi think chandanc_ is out week of 7/18 ?04:51
njohnstonhow soon do you think we can start?  Is like 7/21 to 7/22 too early, if we're going to try for more than one?04:51
chandanc_yes sridark04:52
SridarKi was initially thinking 7/21, 7/2204:52
njohnstonYes, I am out the entire weel of 7/25 to 7/29.  But if you can make progress without me please don't let me stop you! :-)04:52
njohnstons/weel/week/g04:52
SridarKbefore njohnston heads out on PTO04:52
njohnstonHow does everyone feel about that?  Who would be interested in attending?04:53
SridarKmay be we can keep that, at least to shake up things on the db, plugin agent04:53
SridarKso it is ok if chandanc_ is out04:53
njohnstonI'll put up an etherpad for it, and send it out on email, so people can put their names on if they are interested04:54
SridarKI am up for this for sure, with njohnston mfranc213_ padkrish yushiro and shwetaap04:54
padkrishnjohnston# +104:54
njohnstonand we can outline what we want to get accomplished there as well04:54
SridarKwe could move things04:54
yushiro+104:54
SridarKthen on the follwing sprint we can work thru the driver pieces04:54
njohnston#action njohnston to put up an etherpad for 7/21-22 virtual sprint, and send it out on email, so people can put their names on if they are interested04:55
SridarKit does not have to be too formal - just a block of time - where we all can focus and be available to each other for questions04:55
SridarKnjohnston: +104:55
njohnstonExcellent!  Well, we have 3.5 minutes left, does anyone have anything else?04:56
*** anilvenkata has joined #openstack-meeting-304:56
padkrishvery fundamental :), do we have a NoOP driver, if not do we require one?04:56
SridarKApologies have to take care of multiple things on this bit of travel and have struggled to stay connected with almost continuous travel.04:57
njohnstoninteresting question, padkrish.  AFAIK we do not have such a driver.04:57
xgermanNo04:57
SridarKLook fwd to get back.04:57
njohnstonSafe travels, SridarK!04:57
xgermanBut I think we are good without04:57
SridarKpadkrish: i think not too - if we are not configured then no effect.04:57
yushiroSridarK, have a good travels :)04:57
SridarKxgerman: +104:58
SridarKThx04:58
xgermanNjohns04:58
xgermanSafe travels04:58
SridarKthx04:58
SridarKxgerman: now a midwesterner ? :-)04:58
padkrishsridarK, xgerman# ok, thanks...thought, will help in testing...but agree, there are other ways..LBaaS used to have a NoOP...04:58
njohnstonxgerman: At the end of the month?  I'm not going anywhere, just volunteering for the county fair. :-)04:59
xgermanYes'04:59
SridarKnjohnston: watch out for all that food04:59
SridarK:-)04:59
xgermanLBaaS did to make driver development easier04:59
njohnstonSridarK: I will try, but history says I will not be very successful.04:59
njohnston#endmeeting05:00
*** openstack changes topic to " (Meeting topic: ops_guide)"05:00
SridarK:-)05:00
openstackMeeting ended Wed Jul 13 05:00:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-13-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-13-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-07-13-04.00.log.html05:00
SridarKBye all05:00
xgermanBye05:00
padkrishbye05:00
chandanc_Bye05:00
mickeysbye05:00
yushirobye bye05:00
njohnstonyushiro: Let's hop on #openstack-fwaas to chat05:00
yushiroYes. Sure.05:00
SarathMekalabye05:00
yushironjohnston, padkrish #openstack-fwaas05:00
yushiroJump!05:00
*** spzala has joined #openstack-meeting-305:01
*** spzala has quit IRC05:06
*** mickeys has quit IRC05:10
*** mickeys has joined #openstack-meeting-305:11
*** anil_rao has joined #openstack-meeting-305:12
*** asettle has joined #openstack-meeting-305:14
*** dedery has joined #openstack-meeting-305:14
*** dedery has quit IRC05:15
*** njohnston is now known as njohnston|sleep05:17
*** mickeys has quit IRC05:18
*** asettle has quit IRC05:18
*** SridarK has quit IRC05:19
*** nkrinner_afk is now known as nkrinner05:22
*** lpetrut has joined #openstack-meeting-305:22
*** mohankumar has joined #openstack-meeting-305:23
*** soichi has joined #openstack-meeting-305:24
*** kaz has joined #openstack-meeting-305:26
*** irenab has joined #openstack-meeting-305:26
*** amotoki has joined #openstack-meeting-305:26
anil_rao#startmeeting taas05:30
openstackMeeting started Wed Jul 13 05:30:10 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.05:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:30
*** openstack changes topic to " (Meeting topic: taas)"05:30
openstackThe meeting name has been set to 'taas'05:30
soichihi05:30
anil_raoHi05:30
kazhi05:30
anil_rao#topic Finalize and submit Barcelona Summit Presentation proposal05:31
*** openstack changes topic to "Finalize and submit Barcelona Summit Presentation proposal (Meeting topic: taas)"05:31
*** mrmartin has quit IRC05:31
reediphi05:31
anil_raoHi05:32
*** fawadkhaliq has joined #openstack-meeting-305:32
soichireedip: hi05:32
*** fawadkhaliq has quit IRC05:32
*** yamamot__ has joined #openstack-meeting-305:32
soichireedip: thank you for your modification to abstract05:32
*** fawadkhaliq has joined #openstack-meeting-305:32
anil_raosoichi,reedip: I just saw your suggested modifications to the abstract05:32
*** fawadkhaliq has quit IRC05:33
yamamot__hi05:33
reedipsoichi: it was minor05:33
*** _SarathMekala_ has joined #openstack-meeting-305:33
reediphi yamamot__05:33
anil_raoone thing to keep in mind is that we have a 1000 character limit. The one I sent out yesterday was alerady at 995 chars.05:33
*** fawadkhaliq has joined #openstack-meeting-305:33
anil_raoI'll reword it some more tomorrow and incorporate the changes from both of you.05:33
anil_raoHi yamamot__05:34
soichianil_rao: my proposal is minor modification, so you can ignore it05:34
*** yushiro is now known as yushiro_afk05:35
*** SarathMekala has quit IRC05:35
*** padkrish has quit IRC05:35
anil_raosoichi: I think I can include it because it is a nice point. I'll just changes the words a little bit to make it all fit in 1000 chars. :-)05:35
soichithank you05:35
*** fawadkhaliq has quit IRC05:36
soichiwe need to ansewer two questions:05:36
*** fawadkhaliq has joined #openstack-meeting-305:36
-soichi- What is the problem or use case you're addressing in this session?05:36
anil_raoYes, let's discuss this a bit.05:36
reediplemme try and reword it05:36
soichi1) What is the problem or use case you're addressing in this session?05:36
anil_raoReedip, I have it done mostly. so I'll make final adjustments just before submitting tomorrow morning. :-)05:37
reedipUmm, okay :)05:37
anil_raosoichi: We will elaborate that section by listing the following items.05:37
reedipanil_rao: I have shared the speaker details on the email (JFYI)05:38
anil_rao1. The plugin/agent/driver architecture which allows platform specific and vendor extension to be implemented.05:38
anil_raoreedip: Thanks you. :-)05:38
anil_rao2. The need for isolation between production and mirrored traffic in the underlay network and some techniques to address this.05:38
anil_rao3. Performance analysis and lessons learnt from it. Steps to improve performance going forward.05:39
anil_raoAny other thoughts?05:39
*** vnyyad has joined #openstack-meeting-305:40
soichiIt looks fine for me.05:41
reedipWe should keep it light enough. Going to omuch into technicality can overload the users and operators in the audience05:41
reedipso I think we can keep the information limited the ones specified above05:42
anil_raoreedip: sounds good.05:42
anil_raoFor the section on what attendees expect to learn, I was thinking about the following:05:43
anil_rao1. Discover that the TaaS architecture lends itself to multiple backend solutions to meet different needs.05:44
anil_rao2. Several service providers had indicated an interest in having a completely separate data path for monitored traffic. So now they can learn about how this may be achieved.05:44
anil_raoOthers can also learn why separating the production and mirrored traffic can be beneficial for them.05:45
*** paul-carlton2 has joined #openstack-meeting-305:45
anil_rao3. The performance analysis is long overdue. We have been asked about TaaS performance during both our previous presentations.05:45
vnyyadare we going to provide a demo this time? oor a prersentation05:46
*** sheeprine has quit IRC05:46
anil_raovnyyad: I think we can skip a demo but provide real data from performance experiments.05:46
vnyyadok.05:46
*** pgadiya has joined #openstack-meeting-305:46
anil_raowhat do you think?05:47
soichianil_rao: agree05:47
kazsounds good for me05:47
yamamot__anil_rao: sounds good05:47
vnyyadyes i guess going into more tech detaill of the solution to get more people develop back ends might be good05:47
anil_raovnyyad: Yes will have a section on the plugin/agent/driver architecture showing how it facilitates writing vendor/platform specific backends.05:48
vnyyadthat will be great05:48
*** sheeprine has joined #openstack-meeting-305:49
soichi+105:49
anil_raoWell, let's hope we get picked. :-)05:50
soichisure05:50
vnyyadIn the interest of full disclosure, we from Ericsson in partner with a customer have also submitted a tech talk on applying TaaS to monitor in Telco NFV05:50
soichiit sounds great!05:50
vnyyadbut its purely application of taas as a solution05:50
vnyyadits in the telco track05:51
anil_raovnyyd: We are submitting in the Network section so having a TaaS presentation in the Telco section is great!05:51
vnyyadyes.... that would be great!05:51
*** amotoki has quit IRC05:51
vnyyadwe will have more representation one on the technical siide and the other on application of it05:52
*** yushiro_afk has left #openstack-meeting-305:52
soichii think it is very noce to have a actical use case05:52
soichinoce -> nice05:52
anil_rao+105:52
*** amotoki has joined #openstack-meeting-305:53
anil_raosoichi,kaz: Do you want to discuss the perf results you had posted a few weeks back?05:53
kazexcuse me, we can not have a time for prepearaton, so we would like to discuss next week.05:54
anil_raokaz: Sure, no problem. We can cover that topic next week.05:54
kazthank you.05:55
vnyyadi guess we should also bring up the agenda of separating data path for Taas in the comming metings as well05:56
soichisure05:56
*** amotoki has quit IRC05:57
soichicurrently, Kaz is working to implement by using flow based tunneling05:57
vnyyadthanks!05:57
vnyyadthat is good05:58
vnyyaddoes that involve any tunneling protocol like GRE or VxLAN05:58
kazVXLAN05:59
vnyyadok thanks Kaz05:59
*** amotoki has joined #openstack-meeting-305:59
vnyyadso i guess the idea is to setup tunnels out of band to the existing overlay tunnels05:59
*** mrmartin has joined #openstack-meeting-305:59
soichii'm not sure, we will explain our design in next week IRC06:01
vnyyadanil: sorry for hijacking the discussion, please continue the agenda as proposed06:01
vnyyadsoichi: sure... thanks06:01
*** spzala has joined #openstack-meeting-306:02
anil_raovnyyad: Our remaining agenda for today is Open Discussion so this is appropriate06:02
anil_rao#topic Open Discussion06:02
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:02
vnyyadWe will also be working on a TaaS driver for VLAN based neutron network06:03
vnyyadso i guess a separate tunnel based datapath would be good to have for that as well06:04
anil_raovnyyad: Yes.06:04
*** mohankumar has quit IRC06:05
*** spzala has quit IRC06:06
*** lpetrut has quit IRC06:06
anil_raoWe need to consider TaaS requirements from two angles:06:07
anil_rao1. Using the existing tunnels or separate tunnels for the overlay06:07
*** Sukhdev has quit IRC06:07
anil_rao2. Using existing interfaces or separate interfaces (and possibly a separate switching fabric) for the underly.06:08
vnyyadanil_rao: +106:08
kaz+106:08
vnyyadi guess flexibility to have both is the best06:08
soichi+106:08
kaz+106:08
anil_raoIn some cases, it might be shared at one level but isolated at the other. In some cases it might be shared in both or even isolated in both.06:09
vnyyad+106:11
soichiI have another topic.06:13
anil_raoSure.06:13
soichiI think we need to examine the bug(?) report:06:13
soichi#link: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html06:13
anil_raosoichi: I am not sure if this happens when both VMs are on the same host. I know we have a problem when using a single-node setup and trying to reach a VM from outside the host.06:14
anil_raosoichi,kaz: I wanted to ask you this. Since your perf tests are done on a single node setup and you are passing traffic between two VMs on the same host you have it working correctly.06:15
*** andymaier has joined #openstack-meeting-306:15
kazwe modified a flow of TapFlow to disable "dl_vlan=..."06:18
anil_raokaz: Thanks!06:18
anil_raoLet me look into this problem.06:18
soichiokay, thank you.06:19
vnyyadthanks06:19
anil_raoFYI, we are using the vlan check here because we didn't want to assume that mac address are unique across virtual networks that may be sharing a host.06:19
soichithank you for your information06:20
vnyyadanil: +106:21
anil_raoI'll check this out and if there is a problem try to get it fixed.06:21
*** mohankumar has joined #openstack-meeting-306:21
soichiwe will report if we find something new06:22
anil_raosoichi: Thanks06:23
vnyyadthanks06:23
*** sarob has joined #openstack-meeting-306:24
soichii have no more topic.06:26
anil_raoLook forward to next week's meeting to discuss perf and separate data-path for TaaS06:26
soichisure06:27
*** ociuhandu has joined #openstack-meeting-306:27
*** sarob has quit IRC06:28
anil_rao#endmeeting06:29
*** openstack changes topic to " (Meeting topic: ops_guide)"06:29
openstackMeeting ended Wed Jul 13 06:29:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-13-05.30.html06:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-13-05.30.txt06:29
anil_raoBye06:29
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-07-13-05.30.log.html06:29
soichii hope we will have TaaS presentations in Barcelona!!06:29
yamamot__bye06:29
soichibye06:29
vnyyadbye all06:29
kazbye06:29
*** anil_rao has quit IRC06:29
*** soichi has left #openstack-meeting-306:30
*** andreas_s has joined #openstack-meeting-306:31
*** mrmartin has quit IRC06:31
*** vnyyad has quit IRC06:32
*** baoli has joined #openstack-meeting-306:32
*** dimtruck is now known as zz_dimtruck06:35
*** pcaruana has joined #openstack-meeting-306:35
*** kaz has quit IRC06:36
*** baoli has quit IRC06:36
*** revon has quit IRC06:40
*** rossella_s has quit IRC06:40
*** rossella_s has joined #openstack-meeting-306:40
*** cartik has joined #openstack-meeting-306:42
*** pgadiya has quit IRC06:43
*** pgadiya has joined #openstack-meeting-306:43
*** amotoki has quit IRC06:48
*** mrmartin has joined #openstack-meeting-306:55
*** zz_dimtruck is now known as dimtruck06:56
*** amotoki has joined #openstack-meeting-307:01
*** spzala has joined #openstack-meeting-307:02
*** egallen has joined #openstack-meeting-307:03
*** thatsdone has joined #openstack-meeting-307:04
*** dimtruck is now known as zz_dimtruck07:06
*** chandanc_ has quit IRC07:06
*** spzala has quit IRC07:07
*** lpetrut has joined #openstack-meeting-307:15
*** jed56 has joined #openstack-meeting-307:16
*** markvoelker has quit IRC07:19
*** markvoelker has joined #openstack-meeting-307:21
*** egallen has quit IRC07:25
*** egallen has joined #openstack-meeting-307:26
*** thatsdone has quit IRC07:28
*** _Fdaisuke_ has joined #openstack-meeting-307:28
*** jlanoux has joined #openstack-meeting-307:28
*** Fdaisuke_ has quit IRC07:29
*** fawadkhaliq has quit IRC07:33
*** markvoelker has quit IRC07:39
*** amotoki has quit IRC07:40
*** lpetrut has quit IRC07:43
*** tonytan4ever has quit IRC07:47
*** egallen has quit IRC07:47
*** tonytan4ever has joined #openstack-meeting-307:47
*** asettle has joined #openstack-meeting-307:47
*** kzaitsev_mb has quit IRC07:48
*** tmazur has joined #openstack-meeting-307:49
*** amotoki has joined #openstack-meeting-307:50
*** tonytan_brb has joined #openstack-meeting-307:51
*** asettle has quit IRC07:52
*** mickeys has joined #openstack-meeting-307:52
*** ralonsoh has joined #openstack-meeting-307:53
*** tonytan4ever has quit IRC07:54
*** yamahata has quit IRC07:56
*** chandanc_ has joined #openstack-meeting-307:59
*** pcaruana has quit IRC08:00
*** dtardivel has joined #openstack-meeting-308:01
*** d0ugal has joined #openstack-meeting-308:02
*** spzala has joined #openstack-meeting-308:03
*** mickeys has quit IRC08:04
*** mickeys has joined #openstack-meeting-308:04
*** spzala has quit IRC08:08
*** flwang1 has joined #openstack-meeting-308:08
*** mickeys has quit IRC08:09
*** asettle has joined #openstack-meeting-308:12
*** pcaruana has joined #openstack-meeting-308:14
*** jrist_ has joined #openstack-meeting-308:14
*** jlanoux has quit IRC08:14
*** jlanoux has joined #openstack-meeting-308:15
*** mbound has joined #openstack-meeting-308:16
*** mbound has quit IRC08:17
*** lpetrut has joined #openstack-meeting-308:18
*** markvoelker has joined #openstack-meeting-308:20
*** jtomasek__ has joined #openstack-meeting-308:22
*** markvoelker has quit IRC08:25
*** oshidoshi has joined #openstack-meeting-308:30
*** askb_ has joined #openstack-meeting-308:33
*** cartik has quit IRC08:36
*** amotoki has quit IRC08:38
*** oshidoshi has quit IRC08:47
*** numan_ has quit IRC08:53
*** zz_dimtruck is now known as dimtruck08:56
*** andymaier has quit IRC09:03
*** spzala has joined #openstack-meeting-309:04
*** iyamahat has quit IRC09:05
*** dimtruck is now known as zz_dimtruck09:06
*** spzala has quit IRC09:09
*** toddjohn has joined #openstack-meeting-309:11
*** tonytan_brb has quit IRC09:13
*** markvoelker has joined #openstack-meeting-309:15
*** toddjohn has quit IRC09:15
*** mbound has joined #openstack-meeting-309:17
*** pcaruana has quit IRC09:18
*** askb_ has quit IRC09:18
*** asettle has quit IRC09:19
*** markvoelker has quit IRC09:20
*** chandanc_ has quit IRC09:20
*** andymaier has joined #openstack-meeting-309:21
*** mbound has quit IRC09:22
*** zz_dimtruck is now known as dimtruck09:26
*** numan_ has joined #openstack-meeting-309:27
*** amotoki has joined #openstack-meeting-309:30
*** pcaruana has joined #openstack-meeting-309:31
*** amotoki has quit IRC09:34
*** chandanc_ has joined #openstack-meeting-309:35
*** dimtruck is now known as zz_dimtruck09:35
*** akasatkin has left #openstack-meeting-309:37
*** pt_15 has joined #openstack-meeting-309:42
*** kzaitsev_mb has joined #openstack-meeting-309:45
*** pcaruana has quit IRC09:48
*** pcaruana has joined #openstack-meeting-309:48
*** pcaruana has quit IRC09:50
*** pcaruana has joined #openstack-meeting-309:50
*** chandanc_ has quit IRC09:50
*** kzaitsev_mb has quit IRC09:51
*** pcaruana has quit IRC09:51
*** andymaier has quit IRC09:55
*** pcaruana has joined #openstack-meeting-309:57
*** jrist_ has quit IRC10:01
*** spzala has joined #openstack-meeting-310:05
*** zhurong has quit IRC10:06
*** markvoelker has joined #openstack-meeting-310:09
*** spzala has quit IRC10:09
*** asettle has joined #openstack-meeting-310:09
*** Poornima has quit IRC10:11
*** kzaitsev_mb has joined #openstack-meeting-310:12
*** Poornima has joined #openstack-meeting-310:13
*** markvoelker has quit IRC10:13
*** tonytan4ever has joined #openstack-meeting-310:14
*** SarathMekala_ has joined #openstack-meeting-310:15
*** _SarathMekala_ has quit IRC10:18
*** tonytan4ever has quit IRC10:19
*** radek_ has joined #openstack-meeting-310:20
*** yamamot__ has quit IRC10:21
*** jed56 has quit IRC10:25
*** rossella_s has quit IRC10:40
*** rossella_s has joined #openstack-meeting-310:41
*** SarathMekala_ has quit IRC10:42
*** hoangcx has quit IRC10:44
*** SarathMekala_ has joined #openstack-meeting-310:45
*** jrist has joined #openstack-meeting-310:49
*** jrist has quit IRC10:49
*** jrist has joined #openstack-meeting-310:49
*** Poornima has quit IRC10:52
*** Poornima has joined #openstack-meeting-310:52
*** ccamacho is now known as ccamacho|lunch10:56
*** kzaitsev_mb has quit IRC10:59
*** baoli has joined #openstack-meeting-310:59
*** markvoelker has joined #openstack-meeting-311:03
*** sambetts|afk is now known as sambetts|catinbo11:03
*** SarathMekala_ has quit IRC11:03
*** sambetts|catinbo is now known as sambetts|cat11:03
*** spzala has joined #openstack-meeting-311:05
*** baoli has quit IRC11:06
*** markvoelker has quit IRC11:07
*** spzala has quit IRC11:10
*** tellesnobrega is now known as tellesnobrega_af11:12
*** toddjohn has joined #openstack-meeting-311:13
*** toddjohn has quit IRC11:17
*** andymaier has joined #openstack-meeting-311:24
*** zz_dimtruck is now known as dimtruck11:26
*** rossella_s has quit IRC11:33
*** dimtruck is now known as zz_dimtruck11:36
*** sergio_nubeliu has joined #openstack-meeting-311:42
*** sdake has joined #openstack-meeting-311:48
*** yamamoto has joined #openstack-meeting-311:49
*** sdake_ has joined #openstack-meeting-311:50
*** jrist has quit IRC11:51
*** jrist has joined #openstack-meeting-311:51
*** jrist has quit IRC11:51
*** jrist has joined #openstack-meeting-311:51
*** sdake has quit IRC11:54
*** kzaitsev_mb has joined #openstack-meeting-311:59
*** ccamacho|lunch is now known as ccamacho11:59
*** tonytan4ever has joined #openstack-meeting-312:00
*** sergio_nubeliu has quit IRC12:03
*** tonytan4ever has quit IRC12:05
*** spzala has joined #openstack-meeting-312:06
*** ralonsoh has quit IRC12:06
*** abalutoiu has joined #openstack-meeting-312:09
*** spzala has quit IRC12:11
*** toddjohn has joined #openstack-meeting-312:13
*** mbound has joined #openstack-meeting-312:13
*** toddjohn has quit IRC12:18
*** tmazur has quit IRC12:20
*** egallen has joined #openstack-meeting-312:24
*** qwebirc9786 has joined #openstack-meeting-312:25
*** pt_15 has quit IRC12:26
*** qwebirc9786 has quit IRC12:27
*** jed56 has joined #openstack-meeting-312:30
*** Poornima has quit IRC12:30
*** pt_15 has joined #openstack-meeting-312:32
*** markvoelker has joined #openstack-meeting-312:38
*** mickeys has joined #openstack-meeting-312:38
*** belmoreira has joined #openstack-meeting-312:39
*** ociuhandu has quit IRC12:41
*** zhurong has joined #openstack-meeting-312:43
*** mickeys has quit IRC12:43
*** claudiub has joined #openstack-meeting-312:44
*** mrmartin has quit IRC12:46
*** sdake_ has quit IRC12:47
*** c64cosmin has joined #openstack-meeting-312:48
*** sdake has joined #openstack-meeting-312:49
*** ddieterly has joined #openstack-meeting-312:50
*** atuvenie_ has joined #openstack-meeting-312:50
*** mrmartin has joined #openstack-meeting-312:52
*** lblanchard has joined #openstack-meeting-312:55
*** irenab has quit IRC12:56
*** itoader has joined #openstack-meeting-312:56
*** irenab has joined #openstack-meeting-312:56
*** ypen has joined #openstack-meeting-312:56
*** rossella_s has joined #openstack-meeting-312:57
*** woodster_ has joined #openstack-meeting-312:58
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Jul 13 13:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
atuvenie_Hi all13:00
claudiubhello13:00
abalutoiuhi13:00
claudiubsuch a lovely day today13:00
ypenHi13:01
*** egallen has quit IRC13:01
*** sagar_nikam has joined #openstack-meeting-313:01
c64cosmino/13:01
claudiubok, I think we've waited enough for people to join13:02
sagar_nikamHi13:02
claudiub#topic nova feature freeze13:02
*** openstack changes topic to "nova feature freeze (Meeting topic: hyper-v)"13:02
*** zz_dimtruck is now known as dimtruck13:02
claudiubsoo, typically nova feature freeze happens in the milestone N-2.13:02
claudiubwhich is in 2 days.13:03
claudiubthere is only one more patch that was deemed worthy of a feature freeze exception, which is the hyper-v device tagging.13:03
claudiub#link hyper-v device tagging: https://review.openstack.org/#/c/331889/13:03
claudiubso, I'm expecting it to merge in the following days.13:04
claudiubother than that, everything is pretty much frozen.13:04
sagar_nikamcluster driver and FC in O release now ?13:05
sagar_nikamcorrect13:05
claudiubit seems that the hyper-v ovs vif plug driver would be considered an "os-vif" priority, so we can still hope on merging that.13:05
claudiubsagar_nikam: indeed. for the cluster driver it seems that we'll have to have a conversation with nova core about it next week at the midcycle.13:05
*** gouthamr has joined #openstack-meeting-313:05
*** egallen has joined #openstack-meeting-313:06
*** galstrom_zzz is now known as galstrom13:07
claudiubanyways. IMO, there were quite a few patches merged in the hyper-v driver in newton, so I'd say it was a productive cycle in this regard.13:07
claudiub\o/13:07
*** spzala has joined #openstack-meeting-313:07
lpetrutHi guys13:07
*** galstrom is now known as galstrom_zzz13:07
*** radek_ has quit IRC13:08
sagar_nikamclaudiub: agree.. quite a bit of hyperv patches merged13:08
claudiubwe'll probably have to submit new blueprints and features for O, otherwise that "nova  hyper-v priority list" might get too empty. :)13:08
claudiubmoving on.13:08
claudiub#topic networking-hyperv status13:09
*** openstack changes topic to "networking-hyperv status (Meeting topic: hyper-v)"13:09
claudiub#action lpetrut atuvenie_ to review: https://review.openstack.org/#/c/328210/13:09
*** ypen_ has joined #openstack-meeting-313:10
*** zhurong has quit IRC13:10
claudiubother than that, there are no other outstanding commits.13:10
claudiub#topic designate status13:10
*** openstack changes topic to "designate status (Meeting topic: hyper-v)"13:10
*** zhurong has joined #openstack-meeting-313:11
claudiubthere has been some reviews on the patch, but mostly os-win 1.1.0 had to be released.13:11
claudiubstill have to.13:11
claudiubos-win 1.1.0 wasn't released yet as there was a bug that we had to take care of it first.13:11
claudiubthat has been dealt with, will request release again. thus, the designate patch won't be blocked on this.13:12
claudiubabalutoiu: anything else to add?13:12
sagar_nikamclaudiub: designate is planned for newton ?13:13
claudiubsagar_nikam: yep.13:13
*** ubuntu has joined #openstack-meeting-313:13
*** ubuntu is now known as atuvenie13:13
sagar_nikamok ... nice13:13
claudiubsagar_nikam: only nova and cinder have the feature freeze in the milestone N-2.13:13
abalutoiuclaudiub not really, I'm fixing the comments now, and I'm going to do some tests with python 3.4 as well13:13
claudiubsagar_nikam: the rest of the projects have feature freeze somewhere close to N-313:13
*** ypen has quit IRC13:13
claudiubabalutoiu: cool, thanks. :)13:14
claudiubmoving on.13:14
claudiub#topic os-brick status13:14
*** openstack changes topic to "os-brick status (Meeting topic: hyper-v)"13:14
claudiubseems we are blocked here.13:14
*** baoli has joined #openstack-meeting-313:14
claudiubthe cinder core want to have a voting ci before they merge any more patches, it seems.13:15
claudiubsooo, getting the ci up and running will be a must.13:15
*** egallen has quit IRC13:15
*** sdake has quit IRC13:16
sagar_nikamwe have the CI setup13:16
sagar_nikamalready at microsoft13:16
sagar_nikamwhere 3par is available13:16
sagar_nikamis that not in use for the os-brick  ci ?13:17
claudiubbut that might take some time. seems that some infra upgrades will be necessary for it13:17
sagar_nikamok13:18
sagar_nikamso till that time, we cant get os-brick merged ?13:18
*** ddieterly has quit IRC13:18
claudiubsagar_nikam: from what I've talked with the ci team, setting up a new ci for a new project isn't that easy.13:18
claudiubsagar_nikam: yep.13:18
sagar_nikamok13:18
sagar_nikamso this will also move to O13:19
sagar_nikamnow13:19
*** baoli_ has joined #openstack-meeting-313:19
sagar_nikamhopefully we have the CI by that time13:19
claudiubnot necessarely. still hoping for N.13:19
claudiubbut this is something I have little control over.13:20
sagar_nikamthat would be good .. if it is N13:20
claudiubI'll help however I can though.13:20
*** pgadiya has quit IRC13:20
sagar_nikamclaudiub: thank you13:20
claudiubnp. :)13:20
claudiub#topic open discussion13:20
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:20
sagar_nikammonasac13:21
sagar_nikamwanted some discussion on monasca13:21
sagar_nikamhow is it going ?13:21
sagar_nikamare the patches reviewed and merged ?13:21
claudiubsagar_nikam: yeah. no updates there I'm afraid. I was the person responsible for that project, didn't have the time to keep working on it, since I've allocated all my time to nova, getting things merged.13:22
claudiubsagar_nikam: will have to resume, now that nova is frozen. :)13:22
*** baoli has quit IRC13:22
sagar_nikamclaudiub: no problem....13:23
*** cleong has joined #openstack-meeting-313:23
sagar_nikamlet us know when it is ready13:23
sagar_nikamwe will pick and check it13:23
claudiubalso, another note.13:23
claudiub#note claudiub won't attend next week's meeting, due to the nova midcycle event13:23
*** piet has joined #openstack-meeting-313:24
sagar_nikamare we having the meeting next week ?13:24
sagar_nikamalso one more question on monasca ... is it planned for N ?13:24
claudiubso, someone else will have to chair the meeting next week.13:25
*** c64cosmin_ has joined #openstack-meeting-313:25
claudiubsagar_nikam: if there are people attending, yes.13:25
*** c64cosmin has quit IRC13:25
claudiubsagar_nikam: yes, still planned for N. :)13:25
*** c64cosmin_ is now known as c64cosmin13:26
*** julim has joined #openstack-meeting-313:26
sagar_nikamif required... we can not have it next week... if lot of your team members will attend the mid-cycle...13:26
sagar_nikami can attend the meeting, if it is there13:26
sagar_nikamok... monasca planned for N... nice, we will pick up as soon as it is available13:26
claudiubwell, we can post-pone next week's meeting to the next-next one.13:27
claudiubanyways, any more topics for today? :)13:28
ypen_anybody has information of the cassandra database development?13:28
sagar_nikamyes... 2 more topics from me...13:29
claudiubypen_: well, we don't have anything related to cassandra. or at least, not directly.13:29
sagar_nikamcluster driver ... iscsi supprt, any more discussion since we last chatted on this13:29
*** tonytan4ever has joined #openstack-meeting-313:30
atuveniesagar_nikam: not really13:30
atuveniesagar_nikam: I've talked with alessandro, but this is something we need to put some thought into13:31
ypen_What I mean is the plugin metric database13:31
sagar_nikamatunenie: sure... thanks for the update13:31
atuveniesagar_nikam: for the moment I'm working on containers, and haven't focused that much on the cluster part13:31
sagar_nikamatuvenie: ok .... is iscsi support for cluster planned in N ?13:31
sagar_nikamatleast in compute-hyperv ?13:32
claudiubypen_: you mean like, cassandra database metrics?13:32
*** julim has quit IRC13:32
atuveniesagar_nikam: I think at this point that having a custom cluster provider will be the way to go, but we have to analyse the full impact of that13:32
ypen_yes13:32
ypen_we can help if nobody is responsible for that13:32
sagar_nikamatuvenie: custom cluster provider .... some more info please... this is new to me13:33
claudiubypen_: that sounds like something that should be brought up to the monasca meeting. This is the hyper-v meeting. :)13:33
claudiubypen_: the monasca meeting is in 90 minutes, if I'm not mistaken.13:33
*** julim has joined #openstack-meeting-313:33
atuveniesagar_nikam: we talked about it at the last meeting13:33
ypen_Deutsche telekom13:33
*** julim has quit IRC13:34
sagar_nikamok... the same... i will check it again13:34
ypen_Sorry about this. this is our first time13:34
atuveniesagar_nikam: we said we considered writing a custom provider for MSFT cluster that will take care of loging targets when a failover is triggered13:34
claudiubypen_: no problem. :)13:34
*** julim has joined #openstack-meeting-313:34
*** tonytan4ever has quit IRC13:34
*** ddieterly has joined #openstack-meeting-313:35
*** tonytan4ever has joined #openstack-meeting-313:36
sagar_nikamatuvenie: thanks... keep us posted on how things progress, we can check and let you know13:37
*** ociuhandu has joined #openstack-meeting-313:37
claudiubanything else for today?13:37
claudiubjust fyi, the dealine for the openstack summit talks and presentations is pretty close. if you have any presentations you want to submit, you'll have to hurry. :)13:38
*** ddieterly has quit IRC13:39
*** mbound_ has joined #openstack-meeting-313:39
sagar_nikamyes13:40
claudiubwell, if there's nothing else, will close this meeting soon. :)13:40
sagar_nikamone final topic.... freerdp... as of now it is on hold... correct ?13:41
*** tonytan_brb has joined #openstack-meeting-313:41
sagar_nikamthe bug we raised13:41
*** yamamoto has quit IRC13:41
claudiubc64cosmin: hello. it is your time to shine. :)13:41
sagar_nikamit will be worked later13:41
*** tonytan_brb is now known as tonytan4ever_13:41
*** c64cosmin_ has joined #openstack-meeting-313:42
c64cosmin_sagar: Yes, I haven't forgot about you guys13:42
sagar_nikamc64cosmin: thanks ...13:42
c64cosmin_unfortunately work on FreeRDP-WebCOnnect is delayed a bit13:42
c64cosmin_but will  come back right to it, when I can, no worries13:43
sagar_nikamthe reason i asked... since this is postponed, we will also start on other things13:43
c64cosmin_sounds reasonable13:43
*** tonytan4ever has quit IRC13:43
*** mbound has quit IRC13:43
sagar_nikamwill let my QA team member know about it.. so that he can test other features13:43
sagar_nikamjust for our planning13:43
c64cosmin_I will write to you to skype when I have news13:43
*** slaweq has joined #openstack-meeting-313:43
*** amotoki has joined #openstack-meeting-313:43
sagar_nikamc64cosmin: sure... thanks... so we will stop freerdp till you get back to us... and we focus on other hyperv checks13:44
*** tonytan4ever_ has quit IRC13:44
*** andymaier has quit IRC13:44
*** tonytan4ever has joined #openstack-meeting-313:45
*** c64cosmin has quit IRC13:45
claudiubwell, if there's nothing else, we can end it soon. :)13:45
*** yamamoto has joined #openstack-meeting-313:45
sagar_nikamclaudiub: have you seen this https://github.com/python-beaver/python-beaver ?13:45
sagar_nikamthis is for sending any logs to logstash13:46
sagar_nikamnova-compute logs etc13:46
claudiubno, I haven't, but it certainly has a funny description. :D13:46
sagar_nikamcan be sent to logstash using rabbitmq or kafka13:47
claudiubsagar_nikam: kinda' sounds like what monasca-logging does13:47
sagar_nikamclaudiub: you may be right13:47
sagar_nikamwe started checking how nova-compute logs on hyperv can be sent using beaver13:47
*** davidsha has joined #openstack-meeting-313:48
claudiubit seems that it has been quite actuve, having 46 releases, but it hasn't been updated for 3 months.13:48
sagar_nikambut ... no windows support13:48
claudiubWondering if it's still alive.13:48
*** atuvenie has quit IRC13:48
sagar_nikamjust wanted to check if claudbase has seen this...13:48
claudiubsagar_nikam: seems there is a pull request to port to Windows: https://github.com/python-beaver/python-beaver/pull/29313:49
sagar_nikamyes... that is the patch submitted by my team mate13:49
*** toddjohn has joined #openstack-meeting-313:49
*** nandal has joined #openstack-meeting-313:49
*** galstrom_zzz is now known as galstrom13:49
sagar_nikamwe submitted the patch to supprt windows13:50
claudiubsagar_nikam: no, we haven't, but I'd prefer making monasca-logging work on Windows. it probably has more synnergy with other openstack components.13:50
claudiubsagar_nikam: I see. it seems that the ci fails on that pull request though.13:51
sagar_nikamok... let me check with some monasca experts here.... need to understand monasca-logging13:51
sagar_nikamclaudiub: that patch was submitted when beaver used rabbitmq13:51
sagar_nikamnow it used kafka13:51
*** amotoki has quit IRC13:51
sagar_nikamwe could not get the patch merged then.. since not many people in beaver understood windows13:51
*** jlanoux has quit IRC13:51
claudiubsagar_nikam: yeah, understandable. Windows is not a common specimen in the Ops community. :)13:52
sagar_nikamclaudiub: agree....13:52
*** PollyZ has joined #openstack-meeting-313:53
claudiubsagar_nikam: well, let us know how the discussion about monasca-logging goes. :)13:53
claudiubuntil then, we can close the meeting. :)13:54
sagar_nikamclaudiub: sure13:54
claudiubthanks folks for joining, see you next-next week!13:54
sagar_nikamif monasca-logging is useful.. we should use it13:54
sagar_nikamthanks... so no meeting next week ?13:54
claudiubsagar_nikam: yep. :)13:54
sagar_nikamok .... meet you all 2 weeks from now13:55
claudiubsagar_nikam: yeah, there won't be a lot of people attending next week, and there won't be any updates, since the preparation ofr the midcycle takes time.13:55
sagar_nikamclaudiub: and hopefully you have a nice meeting at mid-cycle meetup13:55
sagar_nikamespecially on cluster driver13:56
claudiubsagar_nikam: yeah, I really hope so. they tend to over-analyze everything. :)13:56
*** zhurong has quit IRC13:57
claudiubwell, bye folks!13:57
sagar_nikami am done with topics..13:57
sagar_nikambye..13:57
itoaderbye13:57
claudiub#endmeeting13:57
*** openstack changes topic to " (Meeting topic: ops_guide)"13:57
openstackMeeting ended Wed Jul 13 13:57:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-13-13.00.html13:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-13-13.00.txt13:57
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-13-13.00.log.html13:57
*** amotoki has joined #openstack-meeting-313:58
*** zhurong has joined #openstack-meeting-313:58
*** rbak has joined #openstack-meeting-313:59
*** neiljerram has quit IRC13:59
njohnston|sleep#startmeeting neutron_qos14:00
openstackMeeting started Wed Jul 13 14:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston|sleep. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:00
*** njohnston|sleep is now known as njohnston14:00
openstackThe meeting name has been set to 'neutron_qos'14:00
njohnston#endmeeting14:00
*** njohnston is now known as njohnston|sleep14:00
njohnston|sleep#endmeeting14:00
*** openstack changes topic to " (Meeting topic: ops_guide)"14:00
openstackMeeting ended Wed Jul 13 14:00:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.txt14:00
*** njohnston|sleep is now known as njohnston14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.log.html14:00
*** itoader has quit IRC14:00
njohnston#startmeeting neutron_qos14:00
openstackMeeting started Wed Jul 13 14:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:00
openstackThe meeting name has been set to 'neutron_qos'14:00
njohnstonok, that's better14:00
slaweqhello14:01
njohnston#chair ajo14:01
openstackCurrent chairs: ajo njohnston14:01
davidshaHey14:01
slaweqI thought that I missed it when You made "endmeeting" :)14:01
njohnstonIt gets all screwed up when I use the wrong nick14:01
njohnston#topic announcements14:01
*** openstack changes topic to "announcements (Meeting topic: neutron_qos)"14:01
njohnston#link http://releases.openstack.org/newton/schedule.html - N-2 is tomorrow!14:02
*** ralonsoh has joined #openstack-meeting-314:02
*** c64cosmin_ has quit IRC14:02
njohnstonI don't know what changes we have that require alterations in python-neutronclient, neutron-lib, etc. but keep in mind those have an earlier close date than everything else14:02
njohnstonalso14:03
njohnstonI have filed a spec in python-openstackclient to support the QoS commands14:03
njohnston#link https://blueprints.launchpad.net/python-openstackclient/+spec/neutron-client-qos14:03
*** amotoki has quit IRC14:03
njohnstonI only went with currently implemented commands in python-neutronclient.  My thought was that once this is in, we can keep up with it as part of the natural course of things.14:03
njohnstonI'll see if I can get it approved at the openstackclient meeting tomorrow at 1300 UTC.14:03
davidshathanks!14:04
njohnstonany other announcements?14:04
slaweqnjohnston: I can help with implementation of it :)14:04
njohnstonYes, I am guessing it will be a fair amount of work given the number of commands there are, but I don't know how different the openstackclient environment is from python-neutronclient14:05
njohnstonideally things like the tests should be able to copy over pretty seamlessly I hope14:05
njohnston#topic RFEs14:06
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:06
njohnston#link https://bugs.launchpad.net/neutron/+bug/158605614:06
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:06
njohnstonHow goes this one, slaweq?14:06
slaweqthis one is still waiting for approval14:06
njohnstonI am distressed that it still doesn't have approval, yes14:06
slaweqon last neutron_driver meeting they didn't talk about it14:06
slaweqbecause there was no enough time14:07
slaweqI hope that tomorrow it will be discussed14:07
slaweqalso ajo sent email about it yesterday14:07
slaweqso waiting :/14:07
njohnston#link http://lists.openstack.org/pipermail/openstack-dev/2016-July/099107.html Ajo's email on the validation change14:07
slaweqbtw: njohnston can You change status from "in progress" to "triaged" again?14:07
njohnstondone14:08
slaweqthx14:08
njohnston#link https://bugs.launchpad.net/neutron/+bug/156096114:09
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:09
slaweqthis one is in fact waiting for validation of rules14:09
njohnstonslaweq, looks like you just uploaded a change to work on this: https://review.openstack.org/#/c/341186/14:09
slaweqbut I'm working on it littlebit14:09
slaweqpatch for db and API changes is (almost) done14:09
slaweqyesterday I started working on ovs implementation also14:09
*** yamahata has joined #openstack-meeting-314:09
slaweqso it's moving forward slowly14:10
*** iyamahat has joined #openstack-meeting-314:10
*** iyamahat has quit IRC14:10
slaweqalso this one: https://review.openstack.org/#/c/303626/ is related to this RFE14:10
njohnstonOther than beating the drivers team with a rolled-up newspaper, let us know if there is anything we can to do help.14:11
*** neiljerram has joined #openstack-meeting-314:11
*** alex_xu has quit IRC14:11
*** dasanind has joined #openstack-meeting-314:11
slaweqok, I will tell You if will be something like that14:11
*** sdake has joined #openstack-meeting-314:11
njohnston#link https://bugs.launchpad.net/neutron/+bug/156096314:11
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:11
njohnstonAny notes on this one?14:11
njohnston^^ ralonsoh14:12
ralonsohThe spec is almost aproved14:12
ralonsohhttps://review.openstack.org/#/c/316082/14:12
*** sagar_nikam has quit IRC14:12
njohnstonexcellent!  I have been watching the feedback go back and forth14:12
*** alex_xu has joined #openstack-meeting-314:12
njohnstonFYI14:13
njohnston#link http://tinyurl.com/qos-rfe-unapproved A number of other not-approved RFEs went expired, check it out14:13
*** paul-carlton2 has quit IRC14:14
njohnston#topic Bugs14:14
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:14
njohnston#link https://bugs.launchpad.net/openstack-manuals/+bug/160031314:14
openstackLaunchpad bug 1600313 in openstack-manuals "Using OpenStack Networking with QoS in Networking Guide" [Undecided,In progress] - Assigned to David Shaughnessy (david-shaughnessy)14:14
*** rossella_s has quit IRC14:14
njohnstonand14:15
njohnstonhttps://launchpad.net/bugs/158862114:15
openstackLaunchpad bug 1588621 in openstack-manuals "Using OpenStack Networking with QoS in Networking Guide" [Low,In progress] - Assigned to David Shaughnessy (david-shaughnessy)14:15
njohnstonare both being taken care of by davidsha, thanks for that!14:15
davidshaHopefully the last PS for those has been put up. No problem!14:15
njohnston#link https://review.openstack.org/#/c/339432/14:15
njohnston#link https://bugs.launchpad.net/neutron/+bug/151556414:16
openstackLaunchpad bug 1515564 in neutron "Internal server error when running qos-bandwidth-limit-rule-update as a tenant" [Low,In progress] - Assigned to Liyingjun (liyingjun)14:16
*** iyamahat has joined #openstack-meeting-314:16
njohnstonThe change to fix this has been going since November https://review.openstack.org/#/c/244680/14:16
njohnstonit looks like there was something unnecessary put in there, so once that gets removed perhaps this can get merged14:17
njohnstonand we got a new bug in, which actually has the 'low-hanging-fruit' tag (rare for QoS)14:17
njohnston#link https://bugs.launchpad.net/neutron/+bug/160070814:17
openstackLaunchpad bug 1600708 in neutron "Update ‘--max-kbps’ and ‘--max-burst-kbps’ parameter to 2147483648 or greater than 2147483648 using qos-bandwidth-limit-rule-update command,Neutron server thrown an exception" [Low,Confirmed] - Assigned to QunyingRan (ran-qunying)14:17
njohnstonit has the low hanging fruit tag, but it looks like it may require a change to the definition of an existing database column... not sure but I think that is a 'contract' migration14:18
slaweqif it would be change from signed to unsigned int then maybe not14:19
slaweqbut I'm not sure14:19
davidshanjohnston: this is a change from 32 bit to 64bit14:19
davidshasorry *slaweq14:20
njohnstonright14:20
slaweqok14:20
davidshait could be a signed 64, or an unsigned 32 atm, since it's non-negative I think it's the latter.14:20
njohnstonThe other point made is, perhaps kbits was a bad choice for units to express this in, in the days of 40 Gb interface cards14:20
slaweqnjohnston: but how to change it now14:21
slaweqand what with existing rules which useres could already create? :)14:21
davidshaThis is the same problem we had we changing max-burst-kbps to max-burst-kb/14:21
njohnstonYeah, I didn't think that comment was especially helpful, it seemed more in the realm of "wistful thinking".14:22
slaweqnot exactly davidsha14:22
slaweqthen it was "only" change of option name in API14:22
slaweqnow is change of meaning for existing values14:22
slaweqbut maybe adding column with units would be kind of solution?14:22
slaweqand kbps would be default for existing records14:22
slaweqand new would have different unit14:23
njohnstonPerhaps.  I see drawbacks to every fix I can imagine.14:23
*** jlanoux has joined #openstack-meeting-314:23
davidshayou would need to make max-kbps and max-burst-kbps return strings then right?14:23
slaweqdavidsha: probably yes14:24
slaweqand also problem with changing names of API parameters then14:24
*** ddieterly has joined #openstack-meeting-314:24
slaweqbut maybe it's worth to consider it by ralonsoh on his specs about minimum bw limiting?14:25
njohnstonYou'd almost want to have a new parameter, something that would look like "--max-burst=4mbps" in practice and then parse the unit part of the string.14:25
*** mtanino has joined #openstack-meeting-314:25
slaweqnjohnston: it can be solution IMHO14:26
ralonsohslaweq: ok, so I need to change it again14:26
slaweqralonsoh: I don't know, just saying maybe :)14:26
*** markvoelker has quit IRC14:26
ralonsohI'll wait for the final decission14:26
njohnstonAre there other parameters that get expressed as large integers at the command line elsewhere in openstack?  We could see how others do it.14:27
*** paul-carlton2 has joined #openstack-meeting-314:28
*** jruano has joined #openstack-meeting-314:28
slaweqor I have another (maybe stupid) idea: change column type to varchar14:28
slaweqand store values as string :)14:28
njohnstonIt makes me think of the -L argument to lvresize: http://linux.die.net/man/8/lvresize14:29
njohnstonok, so we definitely don't have consensus on this, let's keep thinking about it14:29
davidshaslaweq: would need a lot more validating, but it's an option14:29
njohnston#topic Open Discussion14:30
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:30
davidshanjohnston: would the storage projects have this issue with requesting blocks of memory?14:30
njohnstonI will be on PTO on 7/27 FYI.14:30
slaweqdavidsha: I know but then You don't have to change API or something what used can see :)14:30
njohnstondavidsha: Perhaps, I will check with my ops folks to see what they do with cinder/glance/etc in this regard.14:30
*** sdake has quit IRC14:31
*** nandal has quit IRC14:31
*** sdake has joined #openstack-meeting-314:31
davidshaslaweq: true, that's a good point. Also good catch on the dscp follow up patch on missing DSCP_MARK in the functional test!14:31
slaweqdavidsha: thx14:32
njohnstonAre any of you going to the neutron mid-cycle?  My travel was denied, sadly.14:32
*** toddjohn has quit IRC14:32
slaweqFYI: I reported presentation about new features in QoS in Newton14:32
slaweqtogether with ajo and ralonsoh14:32
njohnstonslaweq: Very nice!  Like DSCP! :-D14:32
* njohnston will be in the front row14:33
slaweqyes, DSCP is one of new features14:33
slaweqnjohnston: thx but please vote for it first :)14:33
njohnstonOf course14:33
davidshaSame, looking forward to seeing it!14:33
ralonsohthanks!14:33
*** nkrinner is now known as nkrinner_afk14:34
davidshaWe'll ask all the technical DSCP questions >:)14:34
slaweqdavidsha: no way :P14:34
* njohnston chuckles evilly14:34
njohnstonOK, that's all I have for today.    Does anyone have anything else?14:34
*** dasanind_ has joined #openstack-meeting-314:35
*** dasanind has quit IRC14:35
davidshaOh14:35
davidshaPS 2 of the flow classifier is up if people want to check it out14:35
njohnstonurl?14:36
davidshahttps://review.openstack.org/#/c/323963/14:36
davidsha*flow manager14:36
njohnstonI will definitely take a look14:36
davidshathanks14:36
slaweqme also14:36
ralonsohme too14:36
davidshathanks14:37
njohnstonAlso my change to take the l2 agent extension stuff out of l2 and make it general, so there can be l3 agent extensions, is here: https://review.openstack.org/#/c/32970114:37
njohnstonthat has tangential impacts on QoS code, mostly in the form of changing the locations where files are imported from14:37
slaweqI will take a look on it too14:38
*** Fdaisuke has joined #openstack-meeting-314:38
njohnstonOK, sounds like we have covered everything.  I'll make sure ajo can cover the next meeting, on 7/27.14:39
njohnstonThanks all!14:39
*** jruano has quit IRC14:39
slaweqI will not be on next meeting14:39
njohnston#endmeeting14:39
*** openstack changes topic to " (Meeting topic: ops_guide)"14:39
openstackMeeting ended Wed Jul 13 14:39:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:39
ralonsohbye!14:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.html14:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.txt14:39
davidshaThanks!14:39
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-07-13-14.00.log.html14:39
slaweqbye14:39
davidshacya14:39
*** slaweq has quit IRC14:39
*** amotoki has joined #openstack-meeting-314:40
*** marst has joined #openstack-meeting-314:40
*** vishwanathj has joined #openstack-meeting-314:42
*** nandal has joined #openstack-meeting-314:42
*** jruano has joined #openstack-meeting-314:42
*** markvoelker has joined #openstack-meeting-314:44
*** atuvenie has joined #openstack-meeting-314:44
atuvenieexit14:44
*** atuvenie has quit IRC14:44
*** coolsvap has joined #openstack-meeting-314:46
*** ralonsoh has quit IRC14:49
*** uxdanielle has joined #openstack-meeting-314:49
*** witek has joined #openstack-meeting-314:51
*** sergio_nubeliu has joined #openstack-meeting-314:51
*** nandal has quit IRC14:53
*** numan_ has quit IRC14:53
*** armax has joined #openstack-meeting-314:55
*** bklei has joined #openstack-meeting-314:56
*** koji has joined #openstack-meeting-314:57
*** igorn has joined #openstack-meeting-314:59
*** mars_toktonaliev has joined #openstack-meeting-314:59
*** cbellucci has joined #openstack-meeting-314:59
*** tomasztrebski has joined #openstack-meeting-315:00
*** rhochmuth has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Jul 13 15:01:03 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
rhochmutho/15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
bkleio/15:01
iurygregoryo/15:01
shinya_kwbto/15:01
kojio/15:01
rhochmuthagenda: https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
witeko/15:01
cbelluccio/15:01
Fdaisukeo/15:01
rhochmuthAgenda for Wednesday July 13, 2016 (15:00 UTC)15:01
rhochmuth1. Discrepancy in devstack - some tarballs downloaded to /root, some to /opt/monasca_download_dir.15:01
rhochmuth2. Reviews:15:01
rhochmuth2.1 https://review.openstack.org/#/c/337901/15:01
rhochmuth2.2 https://review.openstack.org/#/c/327000/ - accept ?15:01
rhochmuth2.3 https://review.openstack.org/#/c/327481/ - accept ?15:01
rhochmuth2.4 https://review.openstack.org/#/c/333009/ - discuss constraint issue15:01
rhochmuth3. Mascot15:01
rhochmuth4. Mid-cycle: https://etherpad.openstack.org/p/monasca_newton_midcycle15:01
rbako/15:01
*** vishwanathj has quit IRC15:02
tomasztrebskio/15:02
igorno/15:02
*** slogan_ has joined #openstack-meeting-315:02
rhochmuthhi everyone15:02
*** vishwanathj has joined #openstack-meeting-315:02
bkleihola15:02
igornhi :)15:02
rhochmuthlooks liek the agenda is reasonably light today15:02
slogan_morning15:03
slogan_(or evening)15:03
*** ericksonsantos_ has joined #openstack-meeting-315:03
rhochmuth#topic Discrepancy in devstack15:03
*** openstack changes topic to "Discrepancy in devstack (Meeting topic: monasca)"15:03
ericksonsantos_\o15:03
*** vishwanathj has quit IRC15:03
rhochmuthdid someone add that topic15:04
*** ezpz has joined #openstack-meeting-315:04
witektomasz i think15:04
tomasztrebskiI did, open question to understand why not all tarballs are downloaded into single location15:04
*** vishwanathj has joined #openstack-meeting-315:04
witekwhen reviewing my change he spoted15:04
rhochmuthprobably just an oversight15:04
rhochmuthi think monasca_download_dir is the correct location, from what i recall15:05
witekshould we take /root or designated dir?15:05
witekok15:05
rhochmuthi think designated directory would be better15:05
rhochmuthroot sounds a little messy15:05
*** zhurong has quit IRC15:05
tomasztrebski+115:05
*** nandal has joined #openstack-meeting-315:05
witekI also introduced the variable which controlls if the tarballs should always be downloaded15:06
rhochmuth#topic reviews15:06
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:06
rhochmuthhttps://review.openstack.org/#/c/337901/15:06
bkleithat's me15:06
slogan_witek: there is an OFFLINE variable in devstack too15:06
*** banix has joined #openstack-meeting-315:07
bklei^^ review ready for scrutiny/testing -- tomasz had some good comments -- and i'll add tempest tests15:07
bkleithx for the review tomasz15:07
rhochmuthok, did you ever submit a bp?15:07
bkleisi15:07
rhochmuthis that yes or no15:07
bkleiit's linked from the review -- https://blueprints.launchpad.net/monasca/+spec/dimensions-api15:07
bkleiyes :)15:08
rhochmuthok, i guess i'm a little out-of-sync15:08
tomasztrebskibklei: always a pleasure ;-)15:08
bkleii'm proposing to do dimension-values and dimension-names separately15:08
tomasztrebski+115:08
rhochmuthok, i'll try and get to looking at this one again15:08
bkleiit's a pretty big change all by itself -- across two dbs, two languages...15:08
bkleithx15:08
rhochmuthas well as get rbrandt to take a look15:08
bkleiperfect15:09
rhochmuthhttps://review.openstack.org/#/c/327000/15:09
rhochmuthmonitoring for monasca-log-api15:09
rhochmuthassuming that is tomasz and witek15:09
*** mars_toktonaliev has quit IRC15:09
witeki have added minor comment today15:10
tomasztrebskiguess, Witek spotted some issue, so will need to patch that, because looks like overlook from my side15:10
witeklooks good15:10
tomasztrebskiwitek spotted that after I submitted it to agenda15:10
*** laszloh has joined #openstack-meeting-315:10
rhochmuthwell, i think it is mainly ready to go.15:11
rhochmuthone question, shoudl we make the prefix "monasca.logs" plural15:11
rhochmuthinstead of monasca.log15:11
*** paul-carlton2 has quit IRC15:11
witekI undersand monasca.log refers the monasca-log-api component15:12
rhochmuthi see15:12
rhochmuthsounds good15:12
*** davidsha has left #openstack-meeting-315:12
tomasztrebskiwell it is now, but if more metrics would come in place from area of log monitoring we could think on reusing that prefix15:12
rhochmuthso, i'll look at the overall review again, i haven't in a while15:12
tomasztrebskistill either monasca.log or monasca.logs fits IMHO15:12
rhochmuthalso, will try and have tsv review again15:13
rhochmuthnot sure he is here right now15:13
tomasztrebskithe actual component is described by component dimension15:13
rhochmuthtomasz: yep, i saw that15:13
rhochmuthi think i'm good15:13
tomasztrebskiso, monasca.log stays, I need to patch the names according to Witek's comment and that should cut it15:14
*** Chason has joined #openstack-meeting-315:14
witek+215:14
rhochmuthwe will be integrating the new log-api metrics into our distrobution really soon15:14
tomasztrebskiok, so optimize is based in top of monitoring, so I will need to rebase that after, apart from it should be ready to go15:15
tomasztrebskinice to hear ;-)15:15
*** toddjohn has joined #openstack-meeting-315:15
rhochmuthhttps://review.openstack.org/#/c/327481/15:16
*** Kamil_ has joined #openstack-meeting-315:16
rhochmuththat is also tomasz and witek15:16
*** vishwanathj has quit IRC15:17
tomasztrebskiI already mentioned that change above15:17
*** vishwanathj has joined #openstack-meeting-315:17
rhochmuthhttps://review.openstack.org/#/c/333009/15:17
tomasztrebskithat's me, but I just wanted to brought up the small issue with constraint that this feature will surely encounter15:18
tomasztrebskipluggable notifications15:18
tomasztrebskiok...let's say 'small'15:18
rhochmuthi saw your comments, but haven't looked at code15:20
*** chandanc_ has joined #openstack-meeting-315:20
rhochmuthyes, that is a problem15:21
tomasztrebskiwell I can only tell you that since we (Fujitsu) joined monasca notification types were constrained in the database (by enum and now by seperate table + foreign key)15:21
tomasztrebskiso most likely this will end up as the change that affect database itself which will require some level of migration15:22
rhochmuthi'm wondering why haneef hasn't encountered this problem already15:22
tomasztrebskihe's using the same notification types that were part of the enum thus were also inserted into notification_types table15:22
rhochmuthif the type is constrained on specific values, then should the insert not been allowed15:22
tomasztrebskiI think that's the main reason15:22
rhochmuthhe wrote a plugins for slack and hipchat15:23
rhochmuthbut those types aren't defined in the mysql15:23
rhochmutham i confused?15:23
tomasztrebskihttps://github.com/openstack/monasca-api/blob/master/devstack/files/schema/mon_mysql.sql#L27415:23
*** paul-carlton2 has joined #openstack-meeting-315:23
tomasztrebskithis is current content of that table, and no - those values aren't there15:24
rhochmuthso, if the type isn't in that table, the insert shouldn't be allowed, right?15:24
tomasztrebskias you can see validNotificationTypes (https://review.openstack.org/#/c/333009/12/devstack/files/monasca-api/api-config.yml) match the content of the table15:24
*** andreas_s has quit IRC15:25
tomasztrebskiI don't think that it is possible15:25
rhochmuthsure, but he theoretically tested his new plugins, which have new types associated with them15:25
rhochmuthanyway, he must have added those types independently15:26
rhochmuthso, in addition to adding the plugin15:26
rhochmuththe schema needs to be modified15:27
rhochmuthor, the schema is fine15:27
rhochmuthbut the new types need to be inserted15:27
rhochmuthinto that table15:27
tomasztrebskiI'll run some tests tommorow to make sure15:27
bkleiand hopefully if a migration is required, a script will be provided as part of the patch?15:27
*** pcaruana has quit IRC15:28
rhochmuthi don't think a migration is required15:28
rhochmuthbut, the new types need to be at least added to the table at some point15:28
rhochmuthcurrently, they are hard-coded in the mysql that we use15:28
bkleior even documentation of the correct columns/tables insert statement15:28
rhochmuthpossibly, they should be inserted when the api or notification starts-up15:29
bkleisomething operators can copy/paste and not all figure it out15:29
rhochmuthas another option15:29
rhochmuthi'm just throwning out15:29
tomasztrebskibut if you keep schema and you keep configuration entry (validNotificationTypes), these are two places where something is defined, my concern here is that someone can remove entry from configuration15:29
rhochmuthnotification engine on start-up coudl check to see if all types are defined in the table15:29
tomasztrebskiit should follow with removing data from table15:30
shinya_kwbtas You can see https://review.openstack.org/#/c/333009/12/monasca_api/v2/common/schemas/notifications_request_body_schema.py I think we should write notification type in config file.15:30
rhochmuthtomasz: i agree, the configs need to be kept in-sync15:30
tomasztrebskiand if constraint is kept removing data for disabled notification types will be problamatic15:30
*** bpokorny has joined #openstack-meeting-315:30
*** toddjohn has quit IRC15:31
*** sarob has joined #openstack-meeting-315:31
rhochmuthif you disable a notification type in the api, it won't be allowed, and if the plugin disables it, then the plugin will just ignore i'm assuming15:31
*** toddjohn has joined #openstack-meeting-315:32
tomasztrebskiok, but what should happen with those notification methods that's type is the one you just disabled ?15:32
tomasztrebskiif still keeping schema and config in sync is in order15:32
shinya_kwbtoh sorry tomasz already mentiond.15:33
rhochmuththinking off the top of my head, maybe it shouldn't be removed from the db15:33
rhochmuthbut, just ignore by notification engine15:33
rhochmuthif notifications are defined that use a type that has been disable by the api and engine, i don't think it should be removed from the db, as that woudl result i'm assumin in a constraint violation15:34
rhochmuthhow about if we discuss further in the ticket15:35
tomasztrebskiok15:35
rhochmuthhaneef isn't gettign all this15:35
*** mordred has quit IRC15:35
rhochmuththanks for bringing this to our attention15:35
*** sarob has quit IRC15:36
*** toddjohn has quit IRC15:36
rhochmuthi hadn't looked at the schema and assumed it was just a string15:36
rhochmuthbad assumption on my part15:36
*** jruano has quit IRC15:36
tomasztrebskiit used to be enum, that was kind of contraint on its own15:36
tomasztrebskinow it is the table, only constraint part did not change actually15:36
rhochmuth#topic mascot15:37
*** openstack changes topic to "mascot (Meeting topic: monasca)"15:37
*** banix_ has joined #openstack-meeting-315:37
rhochmuthwe have a request from openstack committee for a monasca mascot15:37
*** toddjohn has joined #openstack-meeting-315:37
witek:)15:38
iurygregorynice :D15:38
Kamil_cool15:38
rhochmuthThe idea is to create a family of logos for OpenStack projects that are unique, yet immediately identifiable as part of OpenStack. We’ll be using these logos to promote your project on the OpenStack website, at the Summit and in marketing materials.  We’re15:38
rhochmuth asking project teams to choose a mascot to represent as their logo. Your team can select your own mascot, and then we’ll have an illustrator create the logo15:38
rhochmuth for you (and we also plan to print some special collateral such as stickers for your team in Barcelona).15:38
rhochmuthYour mascot can be anything from the natural world—an animal, fish, plant, or natural feature such as a mountain or waterfall. We ask that you don’t choose a mascot15:38
rhochmuth that another company or project in the ecosystem is already using. To facilitate this, we suggest your team choose and prioritize a few mascot candidates by July 27.15:38
slogan_Well, UC Santa Cruz already took the banana slug, so can't use that15:38
*** ericksonsantos_ has quit IRC15:39
rhochmuthwe can put as a topic for nex weeks mid-cycle15:39
*** jtomasek__ has quit IRC15:39
rhochmuthcurrently, i have a dog, cat, monitor (lizard), and mammoth15:39
*** ericksonsantos_ has joined #openstack-meeting-315:39
tomasztrebskiofftopic....just was looking for inspiration and found that -> https://cdn.meme.am/instances/500x/63908613.jpg15:40
*** piet has quit IRC15:40
*** piet has joined #openstack-meeting-315:40
*** banix has quit IRC15:40
*** banix_ is now known as banix15:40
iurygregoryneed to be animal/something from nature i think15:40
bkleieagle!15:40
rhochmuthyo dawg15:41
Kamil_an alpaca15:41
slogan_heh15:41
rhochmuthi thought an alpaca was a vegetable15:41
*** mickeys has joined #openstack-meeting-315:41
*** atuvenie_ has quit IRC15:41
bkleii've got it -- monasca is a mismash of different stuff -- okapi?15:41
slogan_given it only needs to be unique in the ecosystem, banana slug is actually back on the table15:41
bkleihttps://en.wikipedia.org/wiki/Okapi#/media/File:Okapi2.jpg15:42
*** iurygregory has left #openstack-meeting-315:42
*** iurygregory has joined #openstack-meeting-315:42
slogan_(sorry, I am still astonished a college would pick such a mascot)15:42
rhochmuthslogan_: We are not going to use a banana slug15:42
*** watanabe_isao has joined #openstack-meeting-315:42
bklei+1 roland15:42
slogan_lol15:42
iurygregoryo.o15:43
rhochmuthok, next topic15:43
tomasztrebskihttp://i.telegraph.co.uk/multimedia/archive/03133/the-eye-of-sauron_3133429b.jpg15:43
rhochmuthbring your ideas next week15:43
tomasztrebskiis that an option ?15:43
rhochmuthsounds like we have some good ones15:43
tomasztrebskikind of nice fit for monitoring15:43
tomasztrebski:)15:43
rhochmuthvery cool15:43
bkleilike the analogy -- monasca==visibility into openstack15:44
rhochmuth#topic Mid-cycle: https://etherpad.openstack.org/p/monasca_newton_midcycle15:44
*** ericksonsantos_ has quit IRC15:44
*** openstack changes topic to "Mid-cycle: https://etherpad.openstack.org/p/monasca_newton_midcycle (Meeting topic: monasca)"15:44
rhochmuthso, hopefully everyone remembers that next week is the mid-cycle15:44
rhochmuththe link is above15:44
*** anilvenkata has quit IRC15:44
rhochmuthif folks can start filling in with topics, that woudl be great15:45
rhochmuthright now it is mostly open15:45
rhochmuthi'lll start filling into15:45
*** bpokorny has quit IRC15:45
*** mickeys has quit IRC15:46
*** jrist has quit IRC15:46
*** d0ugal has quit IRC15:46
*** mrmartin has quit IRC15:46
rhochmuthok, just a reminder that CFP for openstack deadline is today15:48
slogan_yep15:48
rhochmuthso, we have a bit of time left15:48
rhochmuthi'll just open it up15:48
slogan_I can still add you as a speaker if you end up with only 2 talks15:49
slogan_let me know by e-mail15:49
*** iyamahat has quit IRC15:49
rhochmuthslogan_: sure, i'll let you know later today, thx15:49
slogan_we're now pushing packet trace data into monasca15:49
rhochmuthwow15:50
*** yamahata has quit IRC15:50
bkleislogan_ maybe a demo of that during next week's midcycle -- would like to see that?15:50
rhochmuthyes, that is a great idea15:50
slogan_I could certainly talk about what we've added15:50
rhochmuthplease add to agenda15:50
slogan_ok15:50
rhochmuthi was wondering about connections to other projects, like congress, vitrage, watcher15:51
*** Sukhdev_ has joined #openstack-meeting-315:51
*** jruano has joined #openstack-meeting-315:51
slogan_me too :-)15:51
rhochmuthslogan_: ooops, sorry, broadview15:51
*** belmoreira has quit IRC15:51
*** dasanind_ has quit IRC15:52
slogan_would a discussion on the issues they may face with a firehose of obscure data be good for the midcycle15:52
slogan_some of the stuff broadview pushes is really domain specific - seems like we have to play a role in ways beyod just dimensions15:52
slogan_if they can effectively use the data15:53
slogan_they kinda have to know what it means15:53
rhochmuththat would be a good topic15:53
*** chandanc_ has quit IRC15:53
*** watanabe_isao has quit IRC15:54
rhochmuthcassandra update15:54
rhochmuththat would be another good topic15:54
shinya_kwbtit's me ?15:54
*** revon has joined #openstack-meeting-315:54
witek+115:54
bkleigood idea15:54
*** vishwanathj has quit IRC15:54
rhochmuthshinya_kwbt: yes, that would be you, and whatver updates that fujitsu have15:55
*** catherineD has joined #openstack-meeting-315:55
rhochmuthin the same area based on their investigations15:55
witeki will speak with Matthias15:55
*** vishwanathj has joined #openstack-meeting-315:55
rhochmuththanks witek15:55
shinya_kwbtI'm working to add support java implementation15:56
rhochmuthi also have some general logistical topics related to the project to discuss15:56
rhochmuthsuch as deployment documentation, and cleaning up repo readmes15:56
*** ddieterly is now known as ddieterly[away]15:56
rhochmuthso, i'll add them15:57
*** Rockyg has joined #openstack-meeting-315:57
*** watanabe_isao has joined #openstack-meeting-315:57
*** julim_ has joined #openstack-meeting-315:57
rhochmuthso, i think for the first 1/2 hour to hour we can orhganize the topics and remainder of the agenda for th emid-cycle15:57
bkleisounds good15:58
*** dimtruck is now known as zz_dimtruck15:58
rhochmuthso, unless anyone has anything else, i think this meeting is wrapping up15:58
rhochmuththanks everyone15:58
bkleithx roland!15:58
witekthank you Roland15:58
rhochmuthsee you next tuesday15:59
shinya_kwbtthanks15:59
rhochmuthand wednesday15:59
witeksee you15:59
kojisee you15:59
*** koji has quit IRC15:59
*** baoli_ has quit IRC15:59
*** cbellucci has quit IRC15:59
tomasztrebskicya15:59
*** amotoki has quit IRC15:59
iurygregorytomasztrebski, can you take a look at https://review.openstack.org/#/c/341214/2/docs/monasca-log-api-spec.md ? o/15:59
*** julim has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to " (Meeting topic: ops_guide)"16:00
openstackMeeting ended Wed Jul 13 16:00:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-13-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-13-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-13-15.01.log.html16:00
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Jul 13 16:00:23 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
topolo/16:00
egluteo/16:00
catherineDo/16:00
hogepodgeo/16:00
*** Fdaisuke has quit IRC16:00
*** gema has joined #openstack-meeting-316:00
markvoelker#chair eglute16:00
woodster_o/16:00
gemao/16:00
openstackCurrent chairs: eglute markvoelker16:00
markvoelker#chair hogepodge16:00
openstackCurrent chairs: eglute hogepodge markvoelker16:00
*** ezpz has left #openstack-meeting-316:01
*** Kamil_ has quit IRC16:01
markvoelker#link https://etherpad.openstack.org/p/DefCoreLunar.11 Today's etherpad16:01
luzCo/16:01
markvoelkerDo we have Brad to talk about the IBM interop challenge?16:02
*** witek has left #openstack-meeting-316:02
topolyes I am here16:02
markvoelker#topic IBM Interop Challenge16:02
*** openstack changes topic to "IBM Interop Challenge (Meeting topic: defcore)"16:02
markvoelkerTake it away sir16:02
*** ddieterly[away] is now known as ddieterly16:02
*** dwalleck has joined #openstack-meeting-316:02
topolThanks markvoelker! Hi everyone16:02
dwalleck(late) o/16:02
topolAt OpenStack Austin, our GM Don Rippert kicked off an OpenStack Interoperability Challenge.16:03
*** rbak_ has joined #openstack-meeting-316:03
*** galstrom is now known as galstrom_zzz16:03
topolThe goal of this challenge was to prove/highlight that OpenStack is interoperable at a solution level (work builds upon existing DefCore/RefStack efforts).16:03
topolWe have been defining this challenge effort and reviewing it with many OpenStack sponsor companies. An incredibly large number of folks have agreed to participate in our Interoperability Challenge and have agreed to show interoperability at the Barcelona Summit.16:03
*** slogan_ has quit IRC16:04
topolWe have a   kickoff meeting next week and would like participation from DefCore/RefStack16:04
*** laszloh has left #openstack-meeting-316:04
topolThis work is meant to build on and showcase DefCore/RefStack16:04
hogepodgetopol: do yo have any links for this?16:05
markvoelkertopol: When's the meeting and what do you need from us?16:05
*** rbak has quit IRC16:05
Rockygo/16:05
*** brunssen has joined #openstack-meeting-316:05
brunsseno/16:05
topolI have a slide deck I can make available to you all16:05
gemathat'd be great16:06
topolIdeally would like someone from DefCore/RefStak to partcipate and be informed. I believe Rockyg will be there but we are happy to have others16:06
*** bklei has left #openstack-meeting-316:06
topolThis is an open invitation16:06
eglutetopol could a calendar invite be sent to the defcore mailing list?16:07
RockygYup.  I'm there.  I think catherineD is, too.16:07
markvoelkertopol: Sure, we can probably have some folks join in...once we know when it is. =)  Thanks for making us aware.16:07
topolOur  first kickoff meeting is this Monday at 2pm EST.  We can send all the details to the defcore mailing list16:08
*** rbak__ has joined #openstack-meeting-316:08
*** banix_ has joined #openstack-meeting-316:08
markvoelker#action topol to send out slide deck and meeting info to defcore ML16:08
markvoelkertopol: cool.  Anything else you want to discuss today?16:09
topolPerfect.  we will do that.  Im not sure if the meeting time on monday is 100% confiremd but I will get it confirmed befre I mail the list16:09
catherineDyes  I will be at the meeting16:09
topolThat is all I have. We look forward to working with all of you.16:09
eglutethank you topol!16:10
markvoelkerThanks Brad.16:10
markvoelkerMoving on then....16:10
topolThanks16:10
markvoelker#topic Flag test that depend o os-networks extension16:10
*** openstack changes topic to "Flag test that depend o os-networks extension (Meeting topic: defcore)"16:10
*** rbak_ has quit IRC16:10
markvoelker#link https://review.openstack.org/#/c/329220/16:10
markvoelkerdwalleck: want to speak to this one?16:11
dwalleckSure16:11
*** banix has quit IRC16:12
*** banix_ is now known as banix16:12
dwalleckThere was some good feedback on this last week from mtreinish and andreaf. It's possible that the issue I've been encountering is a bug/feature add for their credentials provider16:12
dwalleckI opened a PR with Tempest to address this: https://review.openstack.org/#/c/341592/16:12
hogepodgeI'm good with flagging based on the information and response from QA16:13
dwalleckIt might be the case that the Tempest credential provider was trying to be extra helpful, but maybe too helpful in certain cases. I'm waiting for feedback from the QA folks on this change16:13
*** david-lyle has joined #openstack-meeting-316:14
markvoelkerYeah, I think that's fair.  One request: could we actually get that bug added to the text of the flag?  Really helps with tracking.16:14
dwalleckmarkvoelker: Can do16:14
markvoelkerdwalleck: Thanks.  If you need an example: https://github.com/openstack/defcore/blob/master/2016.01.json#L80416:14
markvoelkerCool.  Anything else on this one today?16:15
dwalleckThat's all I have. Thanks for the patience and discussion on this point16:15
markvoelkerThanks dwalleck.16:15
markvoelkerOk, moving on16:15
markvoelker#topic Flag request for Hard Reboot Capability16:16
*** openstack changes topic to "Flag request for Hard Reboot Capability (Meeting topic: defcore)"16:16
markvoelkerhogepodge: take it away16:16
hogepodgeThis should be pretty simple.16:16
*** rhagarty has joined #openstack-meeting-316:16
*** paul-carlton2 has quit IRC16:16
hogepodgeA vendor was having problems with this test and asked for a flag on it.16:16
hogepodgeAfter talking with the qa team, it seems like the fix is fairly simple.16:16
hogepodgeTheir reboots were happening too fast for keys to be synched to the drive, so the test was failing.16:16
*** tellesnobrega_af is now known as tellesnobrega16:16
dwalleckv3rm!llion16:17
dwalleckgah16:17
hogepodgeThe fix is adding a sync call in the guest before the hard reboot.16:17
hogepodgeBut, I wanted to make sure everyone was aware of the situation and have a chance to give feedback. They've been really good about filing bugs and engaging with the QA team.16:18
hogepodge#link https://bugs.launchpad.net/defcore/+bug/158401916:18
openstackLaunchpad bug 1584019 in defcore "Non working hard reboot test listed in spec 2016.01.required" [Medium,New] - Assigned to Chris Hoge (hoge)16:18
hogepodge#link https://bugs.launchpad.net/tempest/+bug/158398716:18
openstackLaunchpad bug 1583987 in tempest "reboot_server_hard - can trigger loss of pub key data which fails test" [Undecided,In progress] - Assigned to Ken'ichi Ohmichi (oomichi)16:18
hogepodge#link https://review.openstack.org/#/c/340723/16:18
hogepodgeMy suggestion is to not flag given a fix is in progress.16:19
*** coolsvap has quit IRC16:19
markvoelkerGood to know.  I think I missed notification on that bug being filed somehow (probably because I was mostly internet-less all last week) so thanks for bringing it up.16:19
*** hrito has joined #openstack-meeting-316:19
catherineDhogepodge: is that vendor able to pass the test and thus certify without the flag?16:19
*** iyamahat has joined #openstack-meeting-316:20
markvoelkerI'll make a note to look it over.  Just for clarity: no actual flag patch has been filed, right?  Just the bug?16:20
*** asettle has quit IRC16:20
*** hrito has left #openstack-meeting-316:20
hogepodgecatherineD: they have a workaround that involves setting a delay to 30 seconds. It makes their test run take a long time, but they can get the test to pass.16:20
*** asettle has joined #openstack-meeting-316:20
*** jlanoux has quit IRC16:21
hogepodgemarkvoelker: right, they asked me for a flag bug haven't filed a patch for it16:21
markvoelkerhogepodge: got it, thanks16:21
markvoelkerOk, anything else on this one?16:22
hogepodgenot from me16:22
markvoelkerMoving right along...16:22
markvoelker#topic Admin Credential Tests16:22
*** openstack changes topic to "Admin Credential Tests (Meeting topic: defcore)"16:22
markvoelkerNot much to update on this one: basically there are two different problem classes here.  We have some tests that genuinely need admin creds, and a bunch that don't.16:23
catherineDfor https://review.openstack.org/#/c/299491/16:23
*** yamahata has joined #openstack-meeting-316:23
markvoelkerhttps://review.openstack.org/#/c/300608/ would get rid of tests that deal with extended port attributes, which really do usually need admin and therefore aren't good candidates for us16:23
catherineDI file that to raise the awareness of the testcases involve ...since then we got many patches that eithe rmove or flag the tests ... so the purpose is served ... I will abandon this patch16:24
markvoelkerhogepodge: eglute: I think you had both +2'd that one on earlier patchsets, so may just need a quick recheck from you?16:24
*** sdake has quit IRC16:24
markvoelkerhttps://review.openstack.org/#/c/300608/ that is16:24
catherineDhttps://review.openstack.org/#/c/299491/ will be abandon16:24
eglutedone16:24
*** asettle has quit IRC16:25
markvoelkercatherineD: thanks.  To be clear, 300608 does raise some valid concerns.  There's a bunch of neutron tests using admin creds today that don't need to, so thanks for finding them. =)16:25
hogepodgemarkvoelker: does that patch need to include anything for next.json?16:25
markvoelkerI have submitted https://review.openstack.org/#/c/335558/ to Tempest to deal with those...it just needs reviews16:26
*** coolsvap has joined #openstack-meeting-316:26
markvoelkerhogepodge: which patch?  Sorry, too many links. =)16:26
hogepodgemarkvoelker: catherineD: https://review.openstack.org/#/c/300608/5 , does this need to be applied to next.json16:26
catherineDI believe those tests had already been removed from next.json ... but I will check16:27
hogepodgemarkvoelker: are there any other tests that need attention?16:27
*** paul-carlton2 has joined #openstack-meeting-316:27
*** zz_dimtruck is now known as dimtruck16:27
markvoelkerhogepodge: I think those are the only neutron ones, so we should be in good shape when/if that tempest patch lands16:28
*** mickeys has joined #openstack-meeting-316:28
luzCmarkvoelker I tested your tempest patch and it worked perfectly (no admin credentials) :)16:28
markvoelkerluzC: thanks. =)16:28
luzCalready +1 it16:28
hogepodgeluzC: awesome, thanks!16:29
*** tomasztrebski has quit IRC16:29
markvoelkerIf others want to provide feedback on that patch, you're more than welcome.16:30
markvoelkerok, anything else we need to talk about on this topic today?16:30
catherineDconfirm the tests in https://review.openstack.org/#/c/300608/    were already removed from  next.json https://review.openstack.org/#/c/324892/16:30
markvoelkerthanks catherineD16:30
markvoelkerMoving on then...16:31
markvoelker#topic Additional Properties16:31
*** openstack changes topic to "Additional Properties (Meeting topic: defcore)"16:31
markvoelkerhogepodge: go for it16:31
hogepodgeI'm not sure I have much more to add, just checking to see if we have consensus and can move on it.16:31
hogepodgemarkvoelker: I saw your review and can address those points16:32
catherineDhogepodge: how is the .py file being used?16:32
hogepodge#link https://review.openstack.org/#/c/333067/16:32
hogepodgecatherineD: good catch, I need to update the information on that16:32
catherineDhogepodge: thx16:32
markvoelkerhogepodge: Thanks.  I think looking at how we're communicating these things is going to be a useful exercise to prevent this situation again in the future.16:32
*** piet has quit IRC16:33
hogepodgecatherineD: I've been speaking with mtreinish about it, vendors are going to have to run it against their subunit output, and will likely need to rerun the test with a modified tempest-lib to disable tests that have problems16:33
hogepodgecatherineD: the tests can fail from strict checking before the action is tested.16:34
hogepodge(capability that is)16:34
hogepodgecatherineD: markvoelker: I'll send a new patch clarifying today.16:34
*** coolsvap_ has joined #openstack-meeting-316:34
hogepodgemarkvoelker: regarding the communinication, yes, I see these things as growing pains.16:35
catherineDhogepodge: thx16:35
markvoelkerhogepodge: Ewww.  Can we make that easier somehow?  E.g. maybe provide the necessary lib patch somewhere?16:35
*** mohankumar has quit IRC16:36
hogepodgemarkvoelker: I'm not sure. It's not great, but also the least invasive. The lib patch would have to happen on a case by case basis, since properties are added in different api calls16:36
hogepodgemarkvoelker: but I can have the vendor give me a diff16:36
catherineDwould it be easier if refstack-client jsut uses this lib patch all the time?16:37
markvoelkerHmm...ok.  I'll try to pick through that a little this week to understand it better.  I'd like to make this an easily repeatable process if we can.16:37
*** coolsvap has quit IRC16:37
luzCI can help to modify refstack-client if needed16:37
dwalleckI'm glad to be a guinea pig wherever it might be helpful16:37
markvoelkercatherineD: probably not.  I think we want most people to use the real tests.  It's only a relatively small number that need the waiver program.16:37
RockygI'm sure hogepodge  would,too16:37
hogepodgecatherineD: could be a refstack client feature that generates the patch. I think it should be automateable.16:37
markvoelkerhogepodge: that would be neat16:38
hogepodgeluzC: want to work together on that?16:38
dwalleckhogepodge: ++ to automatable16:38
catherineDhogepodge: yea it would be much more repeatable16:38
luzCyes totally :)16:39
catherineDat least the process is repeatable16:39
luzChogepodge yes we can work together :)16:39
hogepodgeIs the Foundation ok for working with vendors, with the assumption we're working out the fine details of the patch?16:39
*** banix_ has joined #openstack-meeting-316:39
hogepodgemarkvoelker: eglute: (my previous question)16:40
egluteYes,16:40
markvoelkerYeah, I think they're generally onboard.16:40
hogepodgeThanks16:41
eglutei would like to see the waiver merged, so that hogepodge can move forward with certifying companies16:41
*** nandal has quit IRC16:41
hogepodgeeglute: I'll get the new patch up today.16:42
eglutethank you hogepodge16:42
markvoelkerFYI, the next BoD meeting is August 23 and I'm sure this will make the agenda. =)16:42
egluteI am sure it will!16:42
markvoelkerOk, anything further on this today?16:42
*** banix has quit IRC16:42
*** banix_ is now known as banix16:42
hogepodgeno, thanks16:43
*** abalutoiu has quit IRC16:43
markvoelkerMuy bueno.  Thanks for your work on this hogepodge, and everyone else for their feedback.16:43
hogepodgeHappy to help. Thanks everyone.16:43
egluteindeed, thanks everyone!16:43
markvoelker#topic DefCore Sprint/Midcycle16:43
*** openstack changes topic to "DefCore Sprint/Midcycle (Meeting topic: defcore)"16:43
markvoelker#link https://etherpad.openstack.org/p/DefCoreSummer2016Sprint Midcycle planning etherpad16:43
egluteI sent out calendar invites16:44
markvoelkerWe had a few suggestions for additional topics16:44
markvoelkerthanks eglute16:44
markvoelkerhogepodge, do we know when the Foundation folks are coming/would like to present?16:44
markvoelkerShould be fairly easy to accommodate them.16:44
markvoelkerOr, alternately: who should I coordinate with to figure out a good timeslot for them?16:44
hogepodgemarkvoelker: I don't know for certain yet. They're in China right now, but I'll chase them down for an answer.16:45
markvoelkerOk, thanks16:45
*** coolsvap_ has quit IRC16:45
hogepodgeLikely Tuesday or Thursday, since I think I'll be traveling with them to/from Austin to work on some other items.16:45
*** paul-carlton2 has quit IRC16:46
markvoelkerSounds good, just let me know when you find out and we'll work something out.16:46
markvoelkerOn the additionalAttributes session suggestion: it looks like we're very close to landing the waiver patches.  Still think we need to budget time for it?16:46
hogepodgeok16:46
eglutemarkvoelker i would not think so16:46
hogepodgemarkvoelker: maybe? depends on how the second patch goes.16:46
markvoelkerOk.  Maybe the thing to do here is leave it for Fudge Time for the moment and we'll budget additional time if we don't end up landing the patches this week.16:47
markvoelkerSound reasonable?16:47
hogepodgesounds reasonable, put it in pencil :-D16:47
markvoelker=)16:47
markvoelkerThe last suggestion we had was for a bug triage/squashing session.  I'm ok with that if we have time for it, but it's also the sort of thing we could do at a weekly meeting or set up a triage day.16:48
gemamarkvoelker: like we have a lot of free time on weekly meetings to do that?16:49
eglutemarkvoelker would those be tempest bugs? or?16:49
gemaoh, you mean schedule a separate one16:49
markvoelkergema: =)  Well, we're doing patch reviews fairly regularly in meetings so I think we could do bug triage one week if necessary.  But yeah, I separate is fine with me too.16:50
gema:D16:50
hogepodgeCould be useful for wrapping up next. It could be good to do pairs of next against clouds we have access to, so we can shake out any final issues before going to the board.16:50
hogepodges/pairs/tests/16:50
markvoelkerThere are only 10 bugs in LP for DefCore right now, so it should be relatively quick.16:50
dwalleckhogepodge: ++, very good idea16:50
eglutedo we have time scheduled to wrap up 2016.08?16:51
catherineDhogepodge: I have a full test of next,json against a few of my existing clouds ... looks good after all the next,json related patches are merged16:51
hogepodgecatherineD: +116:51
markvoelkercatherineD: hogepodge: I have a couple of results against some of my lab clouds too16:51
hogepodgecatherineD: Can you send me the RefStack links? :-D16:51
hogepodgeI'm setting up a little Mitaka cloud right now to test against also.16:52
*** coolsvap has joined #openstack-meeting-316:52
catherineDoh I did not send up to RefStack ... send to my own server ... but I can do that16:52
*** mohankumar has joined #openstack-meeting-316:52
*** dasanind has joined #openstack-meeting-316:52
*** vishwanathj has quit IRC16:52
eglutemarkvoelker will we need to do anything else to finalize 2016.08?16:53
*** piet has joined #openstack-meeting-316:53
*** vishwanathj has joined #openstack-meeting-316:53
markvoelkereglute: I think we're in pretty good shape once we get the admin credential stuff landed, but I'll look it over again this week. I suspect we won't need to dedicate (much?) time to it at the midcycle.16:54
eglutethanks markvoelker. i dont think there is currently any time scheduled for it16:54
*** nandal has joined #openstack-meeting-316:54
markvoelkerWhen we get a little closer to the BoD meeting I'll put up a patch finalizing it for the BoD to review prior to the meeting.16:54
eglutegreat, thank you16:55
markvoelkerOne other thing on the midcycle: if you haven't added your name and employer to the etherpad and are planning to attend in-person, please do so.  RAX needs that info a day beforehand to be ready for us.16:56
*** sdake has joined #openstack-meeting-316:56
markvoelkerOk, anything else on the midcycle today?  We're down to a few minutes remaining16:57
egluteAlso, regarding dinners: i would suggest Riverwalk, but it is a bit of a drive from the Castle16:57
catherineDeglute: yay!!16:57
gema:D16:57
*** yamamoto has quit IRC16:57
hogepodgeeglute: I know, I want to stay downtown, but also want to be practical :-D16:57
* markvoelker doesn't mind a drive down to the riverwalk personally16:57
eglutewell, the Castle is not downtown, but i do not recomend staying very close to the castle16:58
dwalleckOne does not simply drive to the riverwalk...16:58
markvoelkerOk, one final topic with our two remaining minutes16:58
catherineDnow we have local tour guides :-)16:58
*** julim_ has quit IRC16:58
hogepodgeBefore the meeting closes, I want to make one note about the agenda. I've been make a best guess effort as to how to order everything, but if you have an item that you want to appear earlier in the meeting, please feel free to move it. I generally get the agenda out the night before the meeting, and don't regard it as set in stone.16:58
markvoelkerdwalleck: ain't that the truth. =p16:58
markvoelkerhogepodge: thanks for that16:58
markvoelker#topic Session submissions for Barcelona16:58
*** openstack changes topic to "Session submissions for Barcelona (Meeting topic: defcore)"16:58
*** nandal_ has joined #openstack-meeting-316:58
markvoelkerThe deadline to submit talks is tonight just before midnight PDT.  Get those talks in!16:59
markvoelkerAnd with that we're out of time...16:59
eglutehogepodge is yours defcore 101 type?16:59
markvoelkerThanks everyone!  Back to #openstack-defcore....16:59
hogepodgelink to talks you've sumitted16:59
*** paul-carlton2 has joined #openstack-meeting-316:59
hogepodgeeglute: yeah16:59
eglutecool thanks!16:59
*** julim has joined #openstack-meeting-316:59
markvoelker#endmeeting16:59
*** openstack changes topic to " (Meeting topic: ops_guide)"16:59
openstackMeeting ended Wed Jul 13 16:59:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-13-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-13-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-13-16.00.log.html16:59
*** gema has left #openstack-meeting-317:00
*** nandal has quit IRC17:01
*** sambetts|cat is now known as sambetts17:03
*** dwalleck has quit IRC17:04
*** Sukhdev_ has quit IRC17:05
*** jruano has quit IRC17:05
*** sambetts is now known as sambetts|cat17:06
*** PollyZ has quit IRC17:06
*** baoli has joined #openstack-meeting-317:07
*** brunssen has quit IRC17:08
*** banix_ has joined #openstack-meeting-317:10
*** banix has quit IRC17:13
*** banix_ is now known as banix17:13
*** dwalleck has joined #openstack-meeting-317:16
*** ddieterly is now known as ddieterly[away]17:17
*** Chason has quit IRC17:18
*** marios is now known as marios|gone17:19
*** marios|gone is now known as marios17:19
*** dasanind has quit IRC17:21
*** galstrom_zzz is now known as galstrom17:23
*** PollyZ has joined #openstack-meeting-317:24
*** dwalleck has quit IRC17:24
*** dwalleck has joined #openstack-meeting-317:26
*** dwalleck has quit IRC17:26
*** mrmartin has joined #openstack-meeting-317:27
*** lpetrut has quit IRC17:28
*** PollyZ has quit IRC17:29
*** PollyZ has joined #openstack-meeting-317:37
*** banix_ has joined #openstack-meeting-317:41
*** ddieterly[away] is now known as ddieterly17:43
*** PollyZ has quit IRC17:43
*** banix has quit IRC17:45
*** banix_ is now known as banix17:45
*** dtardivel has quit IRC17:47
*** SumitNaiksatam has joined #openstack-meeting-317:48
*** PollyZ has joined #openstack-meeting-317:51
*** rhochmuth has quit IRC17:51
*** sarob has joined #openstack-meeting-317:51
*** vishwanathj has quit IRC17:52
*** vishwanathj has joined #openstack-meeting-317:53
*** PollyZ has quit IRC17:56
*** nandal has joined #openstack-meeting-317:58
*** yamamoto has joined #openstack-meeting-317:58
*** nandal_ has quit IRC18:00
*** ddieterly is now known as ddieterly[away]18:00
*** egallen has joined #openstack-meeting-318:01
*** ALUVial has joined #openstack-meeting-318:01
*** ALUVial has quit IRC18:02
*** ALUVial has joined #openstack-meeting-318:02
*** egallen has quit IRC18:03
*** s3wong has joined #openstack-meeting-318:04
*** yamamoto has quit IRC18:04
*** rhochmuth has joined #openstack-meeting-318:04
*** PollyZ has joined #openstack-meeting-318:05
*** PollyZ has quit IRC18:09
*** pcaruana has joined #openstack-meeting-318:09
*** banix_ has joined #openstack-meeting-318:12
*** dimtruck is now known as zz_dimtruck18:13
*** igorn has quit IRC18:13
*** ccamacho has quit IRC18:15
*** toddjohn has quit IRC18:15
*** banix has quit IRC18:15
*** banix_ is now known as banix18:15
*** toddjohn has joined #openstack-meeting-318:16
*** sambetts|cat is now known as sambetts18:16
*** sambetts is now known as sambetts|afk18:16
*** toddjohn_ has joined #openstack-meeting-318:17
*** mrmartin has quit IRC18:19
*** mordred has joined #openstack-meeting-318:19
*** neil_ has joined #openstack-meeting-318:20
*** toddjohn has quit IRC18:21
*** asettle has joined #openstack-meeting-318:21
*** vishwanathj has quit IRC18:22
*** neiljerram has quit IRC18:23
*** banix has quit IRC18:23
*** asettle has quit IRC18:25
*** rhochmuth has quit IRC18:26
*** mbound_ has quit IRC18:26
*** zz_dimtruck is now known as dimtruck18:28
*** mbound has joined #openstack-meeting-318:28
*** mbound has quit IRC18:29
*** rhochmuth has joined #openstack-meeting-318:29
*** dasanind has joined #openstack-meeting-318:30
*** mickeys has quit IRC18:33
*** dasanind has quit IRC18:33
*** ccamacho has joined #openstack-meeting-318:34
*** dasanind has joined #openstack-meeting-318:35
*** toddjohn_ has quit IRC18:36
*** toddjohn has joined #openstack-meeting-318:37
*** Swami has joined #openstack-meeting-318:37
*** jruano has joined #openstack-meeting-318:39
*** tonytan4ever has quit IRC18:40
*** toddjohn has quit IRC18:41
*** toddjohn_ has joined #openstack-meeting-318:41
*** dasanind has quit IRC18:41
*** Sukhdev has joined #openstack-meeting-318:42
*** dasanind has joined #openstack-meeting-318:42
*** toddjohn has joined #openstack-meeting-318:42
*** toddjoh__ has joined #openstack-meeting-318:45
*** toddjohn_ has quit IRC18:45
*** PollyZ has joined #openstack-meeting-318:45
*** toddjohn has quit IRC18:47
*** PollyZ has quit IRC18:50
*** PollyZ has joined #openstack-meeting-318:52
*** david-lyle has quit IRC18:53
*** baoli has quit IRC18:54
*** ociuhandu has quit IRC18:57
*** sdake has quit IRC18:58
*** gouthamr has quit IRC18:59
*** mordred has quit IRC18:59
*** bpokorny has joined #openstack-meeting-319:00
*** nandal has quit IRC19:00
*** yamamoto has joined #openstack-meeting-319:00
*** baoli has joined #openstack-meeting-319:01
*** mrmartin has joined #openstack-meeting-319:01
*** yamamoto has quit IRC19:05
*** banix has joined #openstack-meeting-319:06
*** nandal has joined #openstack-meeting-319:14
*** kzaitsev_mb has quit IRC19:14
*** jed56 has quit IRC19:15
*** mrmartin has quit IRC19:15
*** mrmartin has joined #openstack-meeting-319:18
*** banix has quit IRC19:21
*** sdake has joined #openstack-meeting-319:22
*** mrmartin has quit IRC19:25
*** ALUVial has quit IRC19:25
*** banix has joined #openstack-meeting-319:25
*** rhochmuth has quit IRC19:27
*** ddieterly[away] is now known as ddieterly19:29
*** mbound has joined #openstack-meeting-319:30
*** rhochmuth has joined #openstack-meeting-319:31
*** dasanind has quit IRC19:33
*** flwang1 has quit IRC19:34
*** mbound has quit IRC19:35
*** pcaruana has quit IRC19:35
*** Rockyg has quit IRC19:37
*** galstrom is now known as galstrom_zzz19:41
*** ddieterly is now known as ddieterly[away]19:49
*** nandal has quit IRC19:52
*** ddieterly[away] is now known as ddieterly19:52
*** vishwanathj has joined #openstack-meeting-319:54
*** nandal has joined #openstack-meeting-319:56
*** sdake has quit IRC19:57
*** dasanind has joined #openstack-meeting-319:59
*** yamamoto has joined #openstack-meeting-320:02
*** tyr_ has joined #openstack-meeting-320:04
*** yamamoto has quit IRC20:07
*** dasanind has quit IRC20:08
*** dasanind has joined #openstack-meeting-320:09
*** tonytan4ever has joined #openstack-meeting-320:17
*** kzaitsev_mb has joined #openstack-meeting-320:17
*** mickeys has joined #openstack-meeting-320:18
*** mickeys has quit IRC20:18
*** mickeys has joined #openstack-meeting-320:19
*** bpokorny has quit IRC20:22
*** lpetrut has joined #openstack-meeting-320:23
*** dasanind has quit IRC20:25
*** piet has quit IRC20:28
*** bpokorny has joined #openstack-meeting-320:28
*** julim has quit IRC20:30
*** xgerman has quit IRC20:30
*** dasanind has joined #openstack-meeting-320:30
*** xgerman has joined #openstack-meeting-320:31
*** nandal_ has joined #openstack-meeting-320:33
*** nandal has quit IRC20:34
*** ddieterly is now known as ddieterly[away]20:35
*** PollyZ_ has joined #openstack-meeting-320:36
*** PollyZ has quit IRC20:37
*** banix has quit IRC20:40
*** dasanind has quit IRC20:41
*** nandal has joined #openstack-meeting-320:42
*** nandal_ has quit IRC20:43
*** david-lyle has joined #openstack-meeting-320:43
*** piet has joined #openstack-meeting-320:45
*** piet has quit IRC20:46
*** piet has joined #openstack-meeting-320:46
*** david-lyle has quit IRC20:47
*** banix has joined #openstack-meeting-320:49
*** sergio_nubeliu has quit IRC20:49
*** david-lyle has joined #openstack-meeting-320:49
*** auggy has joined #openstack-meeting-320:51
*** banix has quit IRC20:54
*** marst has quit IRC20:57
*** cleong has quit IRC20:57
*** marst has joined #openstack-meeting-320:57
*** julim has joined #openstack-meeting-320:58
*** ddieterly[away] is now known as ddieterly20:58
*** galstrom_zzz is now known as galstrom20:59
*** ddieterly has quit IRC20:59
*** sarob has quit IRC21:00
*** rbak_ has joined #openstack-meeting-321:00
*** ddieterly has joined #openstack-meeting-321:01
*** david-lyle__ has joined #openstack-meeting-321:02
*** rbak__ has quit IRC21:03
*** yamamoto has joined #openstack-meeting-321:04
*** paul-carlton2 has quit IRC21:06
*** paul-carlton2 has joined #openstack-meeting-321:06
*** sankarshan_away has quit IRC21:07
*** yamamoto has quit IRC21:09
*** rbak_ has quit IRC21:09
*** rbak_ has joined #openstack-meeting-321:11
*** ddieterly is now known as ddieterly[away]21:12
*** yamahata has quit IRC21:12
*** lblanchard has quit IRC21:12
*** neil_ has quit IRC21:13
*** neiljerram has joined #openstack-meeting-321:14
*** auggy has left #openstack-meeting-321:14
*** sankarshan_away has joined #openstack-meeting-321:15
*** galstrom is now known as galstrom_zzz21:16
*** Swami has quit IRC21:17
*** ociuhandu has joined #openstack-meeting-321:20
*** rbak_ has quit IRC21:22
*** flwang1 has joined #openstack-meeting-321:22
*** vishwanathj has quit IRC21:25
*** nandal has quit IRC21:25
*** watanabe_isao has quit IRC21:25
*** vishwanathj has joined #openstack-meeting-321:25
*** paul-carlton2 has quit IRC21:26
*** david-lyle__ has quit IRC21:28
*** rossella_s has joined #openstack-meeting-321:31
*** marst has quit IRC21:32
*** baoli has quit IRC21:33
*** rbak has joined #openstack-meeting-321:33
*** ddieterly[away] has quit IRC21:34
*** asettle has joined #openstack-meeting-321:35
*** tonytan4ever has quit IRC21:35
*** claudiub has quit IRC21:36
*** jruano has quit IRC21:38
*** vishwanathj has quit IRC21:41
*** ypen_ has quit IRC21:41
*** vishwanathj has joined #openstack-meeting-321:41
*** Swami has joined #openstack-meeting-321:45
*** ociuhandu has quit IRC21:46
*** kbyrne has quit IRC21:47
*** kbyrne has joined #openstack-meeting-321:51
*** ddieterly has joined #openstack-meeting-321:53
*** rossella_s has quit IRC21:53
*** vishwanathj has quit IRC21:57
*** asettle has quit IRC21:59
*** asettle has joined #openstack-meeting-322:01
*** iyamahat has quit IRC22:02
*** asettle has quit IRC22:03
*** iyamahat has joined #openstack-meeting-322:04
*** yamamoto has joined #openstack-meeting-322:05
*** toddjoh__ has quit IRC22:06
*** toddjohn has joined #openstack-meeting-322:07
*** mickeys has quit IRC22:08
*** mickeys has joined #openstack-meeting-322:08
*** ddieterly is now known as ddieterly[away]22:10
*** yamamoto has quit IRC22:11
*** toddjohn has quit IRC22:11
*** mickeys has quit IRC22:13
*** sarob has joined #openstack-meeting-322:24
*** neil_ has joined #openstack-meeting-322:28
*** sarob has quit IRC22:28
*** lpetrut has quit IRC22:29
*** jrist has joined #openstack-meeting-322:29
*** neiljerram has quit IRC22:32
*** coolsvap_ has joined #openstack-meeting-322:34
*** tonytan4ever has joined #openstack-meeting-322:35
*** mickeys has joined #openstack-meeting-322:36
*** coolsvap has quit IRC22:38
*** tonytan4ever has quit IRC22:41
*** ddieterly[away] is now known as ddieterly22:42
*** bpokorny has quit IRC22:42
*** jrist has quit IRC22:46
*** bpokorny has joined #openstack-meeting-322:47
*** iyamahat has quit IRC22:47
*** chandanc_ has joined #openstack-meeting-322:48
*** egallen has joined #openstack-meeting-322:53
*** sarob has joined #openstack-meeting-322:54
*** PollyZ_ has quit IRC22:58
*** sarob has quit IRC22:59
*** revon has quit IRC23:00
*** iyamahat has joined #openstack-meeting-323:03
*** sarob has joined #openstack-meeting-323:04
*** asettle has joined #openstack-meeting-323:04
*** _sarob has joined #openstack-meeting-323:05
*** ionutbalutoiu has quit IRC23:05
*** bradjones has quit IRC23:06
*** yamamoto has joined #openstack-meeting-323:07
*** bradjones has joined #openstack-meeting-323:07
*** bradjones has quit IRC23:07
*** bradjones has joined #openstack-meeting-323:07
*** chandanc_ has quit IRC23:07
*** uxdanielle has quit IRC23:08
*** sarob has quit IRC23:08
*** ionutbalutoiu has joined #openstack-meeting-323:08
*** tonytan4ever has joined #openstack-meeting-323:08
*** ddieterly is now known as ddieterly[away]23:09
*** asettle has quit IRC23:09
*** piet has quit IRC23:10
*** mickeys has quit IRC23:10
*** mickeys has joined #openstack-meeting-323:10
*** ddieterly[away] has quit IRC23:11
*** mickeys has quit IRC23:12
*** mickeys has joined #openstack-meeting-323:13
*** yamamoto has quit IRC23:13
*** tonytan4ever has quit IRC23:15
*** tonytan4ever has joined #openstack-meeting-323:15
*** spzala has quit IRC23:16
*** spzala has joined #openstack-meeting-323:17
*** spzala has quit IRC23:21
*** piet has joined #openstack-meeting-323:21
*** kzaitsev_mb has quit IRC23:22
*** tyr_ has quit IRC23:26
*** sdake has joined #openstack-meeting-323:26
*** egallen has quit IRC23:26
*** yamahata has joined #openstack-meeting-323:27
*** sdake__ has joined #openstack-meeting-323:28
*** sdake has quit IRC23:32
*** piet has quit IRC23:33
*** piet has joined #openstack-meeting-323:33
*** dimtruck is now known as zz_dimtruck23:33
*** sdake__ has quit IRC23:36
*** watanabe_isao has joined #openstack-meeting-323:41
*** mtanino has quit IRC23:44
*** lblanchard has joined #openstack-meeting-323:46
*** rhochmuth has quit IRC23:53
*** tonytan4ever has quit IRC23:54
*** Sukhdev has quit IRC23:58
*** toddjohn has joined #openstack-meeting-323:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!