Wednesday, 2016-03-16

*** sdake has quit IRC00:01
*** baojg has quit IRC00:01
*** Swami has quit IRC00:03
*** iyamahat has quit IRC00:05
*** ivar-lazzaro has joined #openstack-meeting-300:07
*** dims has joined #openstack-meeting-300:08
*** sdake_ has quit IRC00:08
*** MarkAtwood has joined #openstack-meeting-300:10
*** sdake has joined #openstack-meeting-300:11
*** yamamoto_ has quit IRC00:12
*** vtech has quit IRC00:13
*** armax has joined #openstack-meeting-300:14
*** armax has quit IRC00:14
*** SumitNaiksatam has quit IRC00:15
*** yuntongjin has joined #openstack-meeting-300:17
*** spzala has joined #openstack-meeting-300:17
*** sdague has joined #openstack-meeting-300:22
*** spzala has quit IRC00:22
*** openstack has joined #openstack-meeting-300:25
*** ChanServ sets mode: +o openstack00:25
*** sdague has quit IRC00:26
*** baoli has joined #openstack-meeting-300:27
*** mtanino has quit IRC00:28
*** fawadkhaliq has quit IRC00:30
*** sheeprine has quit IRC00:30
*** yuntongjin1 has joined #openstack-meeting-300:32
*** fawadkhaliq has joined #openstack-meeting-300:33
*** MarkAtwood has quit IRC00:33
*** sheeprine has joined #openstack-meeting-300:34
*** yuntongjin has quit IRC00:34
*** MarkAtwood has joined #openstack-meeting-300:36
*** MarkAtwood has quit IRC00:38
*** yuntongjin has joined #openstack-meeting-300:40
*** yuntongjin1 has quit IRC00:42
*** baoli has quit IRC00:42
*** yuntongjin1 has joined #openstack-meeting-300:43
*** yuntongjin has quit IRC00:45
*** dims has joined #openstack-meeting-300:45
*** zz_dimtruck is now known as dimtruck00:49
*** toddjohn has joined #openstack-meeting-300:52
*** hoangcx has joined #openstack-meeting-300:52
*** docaedo has quit IRC00:55
*** toddjohn has quit IRC00:57
*** fawadkhaliq has quit IRC00:58
*** docaedo has joined #openstack-meeting-301:01
*** fawadkhaliq has joined #openstack-meeting-301:02
*** fawadkhaliq has quit IRC01:02
*** zhurong has joined #openstack-meeting-301:03
*** david-lyle has joined #openstack-meeting-301:04
*** fawadkhaliq has joined #openstack-meeting-301:06
*** fawadkhaliq has quit IRC01:06
*** dims has quit IRC01:07
*** SumitNaiksatam has joined #openstack-meeting-301:09
*** banix has quit IRC01:10
*** dims has joined #openstack-meeting-301:12
*** yamamoto has joined #openstack-meeting-301:13
*** spzala has joined #openstack-meeting-301:18
*** fawadkhaliq has joined #openstack-meeting-301:18
*** fawadkhaliq has quit IRC01:19
*** yamamoto has quit IRC01:20
*** spzala has quit IRC01:23
*** docaedo has quit IRC01:24
*** dims has quit IRC01:29
*** dims has joined #openstack-meeting-301:29
*** fawadkhaliq has joined #openstack-meeting-301:30
*** docaedo has joined #openstack-meeting-301:30
*** fawadkhaliq has quit IRC01:31
*** iyamahat has joined #openstack-meeting-301:34
*** vishwanathj has joined #openstack-meeting-301:37
*** fawadkhaliq has joined #openstack-meeting-301:42
*** stanzgy has joined #openstack-meeting-301:43
*** s3wong has quit IRC01:44
*** banix has joined #openstack-meeting-301:45
*** iyamahat has quit IRC01:48
*** fawadkhaliq has quit IRC01:51
*** fawadkhaliq has joined #openstack-meeting-301:51
*** ivar-lazzaro has quit IRC01:52
*** dims has quit IRC01:52
*** yamahata has joined #openstack-meeting-301:53
*** baoli has joined #openstack-meeting-301:55
*** dims has joined #openstack-meeting-301:56
*** tfukushima has joined #openstack-meeting-301:57
*** tfukushima has quit IRC01:58
*** baojg has joined #openstack-meeting-301:59
*** ddieterly is now known as ddieterly[away]01:59
*** dims has quit IRC02:03
*** dims has joined #openstack-meeting-302:05
*** fawadkhaliq has quit IRC02:06
*** woodster_ has quit IRC02:07
*** ddieterly[away] is now known as ddieterly02:11
*** baoli_ has joined #openstack-meeting-302:11
*** fitoduarte has quit IRC02:12
*** JieLi has joined #openstack-meeting-302:13
*** baoli has quit IRC02:14
*** ddieterly is now known as ddieterly[away]02:16
*** baojg has quit IRC02:17
*** rmoe_ has quit IRC02:18
*** spzala has joined #openstack-meeting-302:19
*** yamamoto_ has joined #openstack-meeting-302:19
*** baojg has joined #openstack-meeting-302:20
*** yamahata has quit IRC02:21
*** spzala has quit IRC02:22
*** spzala has joined #openstack-meeting-302:22
*** baoli_ has quit IRC02:23
*** baoli has joined #openstack-meeting-302:23
*** fawadkhaliq has joined #openstack-meeting-302:25
*** ddieterly[away] has quit IRC02:26
*** baoli has quit IRC02:29
*** yamahata has joined #openstack-meeting-302:30
*** fawadkhaliq has quit IRC02:32
*** ativelkov_ has quit IRC02:32
*** tqtran-afk has quit IRC02:32
*** baoli has joined #openstack-meeting-302:35
*** rmoe has joined #openstack-meeting-302:35
*** ativelkov has joined #openstack-meeting-302:36
*** yamahata has quit IRC02:39
*** fitoduarte has joined #openstack-meeting-302:55
*** krtaylor has quit IRC02:58
*** tfukushima has joined #openstack-meeting-303:02
*** tfukushima has quit IRC03:04
*** baojg has quit IRC03:08
*** JieLi has quit IRC03:09
*** krtaylor has joined #openstack-meeting-303:10
*** baojg has joined #openstack-meeting-303:10
*** neelashah has joined #openstack-meeting-303:10
*** fitoduarte has quit IRC03:15
*** yamamoto_ has quit IRC03:25
*** dimtruck is now known as zz_dimtruck03:25
*** yuntongjin1 has quit IRC03:28
*** neiljerram has joined #openstack-meeting-303:30
*** dims has quit IRC03:37
*** neelashah has quit IRC03:38
*** baoli has quit IRC03:39
*** spzala has quit IRC03:39
*** baojg has quit IRC03:42
*** baojg has joined #openstack-meeting-303:43
*** devkulkarni has joined #openstack-meeting-303:45
*** tfukushima has joined #openstack-meeting-303:50
*** tfukushima has quit IRC03:52
*** watanabe_isao has joined #openstack-meeting-303:57
*** vishwanathj has quit IRC04:05
*** yamamoto_ has joined #openstack-meeting-304:06
*** tfukushima has joined #openstack-meeting-304:07
*** fawadkhaliq has joined #openstack-meeting-304:14
*** banix has quit IRC04:24
*** tqtran-afk has joined #openstack-meeting-304:29
*** anilvenkata has joined #openstack-meeting-304:31
*** tqtran-afk has quit IRC04:33
*** tfukushima has quit IRC04:43
*** baojg has quit IRC04:45
*** sdake has quit IRC04:50
*** devkulkarni has quit IRC04:56
*** yamahata has joined #openstack-meeting-305:08
*** anilvenkata has quit IRC05:11
*** rmoe has quit IRC05:11
*** FallenPegasus has joined #openstack-meeting-305:18
*** rmoe has joined #openstack-meeting-305:19
*** tfukushima has joined #openstack-meeting-305:23
*** alex_xu has quit IRC05:25
*** numans has joined #openstack-meeting-305:26
*** rmoe has quit IRC05:26
*** sc68cal has joined #openstack-meeting-305:26
*** tqtran-afk has joined #openstack-meeting-305:30
*** vishwanathj has joined #openstack-meeting-305:31
*** alex_xu has joined #openstack-meeting-305:31
*** vishwanathj has quit IRC05:31
*** neiljerram has quit IRC05:34
*** rmoe has joined #openstack-meeting-305:35
*** tqtran-afk has quit IRC05:35
*** Poornima has joined #openstack-meeting-305:40
*** rmoe has quit IRC05:41
*** fawadkhaliq has quit IRC05:42
*** rmoe has joined #openstack-meeting-305:42
*** fawadkhaliq has joined #openstack-meeting-305:43
*** david-lyle has quit IRC05:45
*** vgridnev has joined #openstack-meeting-305:45
*** david-lyle has joined #openstack-meeting-305:45
*** rmoe has quit IRC05:46
*** vishwanathj has joined #openstack-meeting-305:48
*** vishwanathj has quit IRC05:51
*** mrmartin has joined #openstack-meeting-305:52
*** rmoe has joined #openstack-meeting-305:52
*** fawadkhaliq has quit IRC05:52
*** fawadkhaliq has joined #openstack-meeting-305:53
*** toddjohn has joined #openstack-meeting-305:57
*** toddjohn has quit IRC06:02
*** rmoe has quit IRC06:02
*** mrmartin has quit IRC06:03
*** rmoe has joined #openstack-meeting-306:05
*** FallenPe_ has joined #openstack-meeting-306:09
*** FallenPegasus has quit IRC06:10
*** rmoe has quit IRC06:12
*** rmoe has joined #openstack-meeting-306:20
*** soichi has joined #openstack-meeting-306:21
*** anil_rao has joined #openstack-meeting-306:23
*** kaz has joined #openstack-meeting-306:26
*** rmoe has quit IRC06:29
*** anilvenkata has joined #openstack-meeting-306:29
anil_rao#startmeeting taas06:30
openstackMeeting started Wed Mar 16 06:30:08 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.06:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:30
*** openstack changes topic to " (Meeting topic: taas)"06:30
openstackThe meeting name has been set to 'taas'06:30
anil_raoHi06:30
kazhi06:30
soichihi06:30
anil_raosoichi: Can you kindly send the email address you registered with OpenStack. We need to give you core permissions.06:31
*** pgadiya has joined #openstack-meeting-306:31
yamamoto_hi06:31
irenabhi06:31
*** rmoe has joined #openstack-meeting-306:31
soichianil_rao: okay, i will send my e-mail address to you06:31
reediphi06:31
anil_raosoichi: Thanks.06:32
anil_raoLet's get started06:32
anil_rao#topic: Spec Discussion06:32
*** openstack changes topic to ": Spec Discussion (Meeting topic: taas)"06:32
reedipirenab posted some comments to the questions which I shared06:32
reedipfor the spec06:33
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html06:33
fawadkhaliqhello guys!06:34
anil_raoreedip: Sorry for being a little bit behind. I'll add some thoughts to that email thread soon.06:34
reedipanil_rao: sure .. fawadkhaliq: hi06:34
*** vishwanathj has joined #openstack-meeting-306:34
anil_raoThere was one question that I was curious about.06:34
*** vishwanathj is now known as vishwanathj_zzz06:35
reedipso irenab gave her comments on #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/089207.html , and she is here today for the discussion, so any concerns from her end can be closed early on06:35
anil_raoIs there anything in the current API definition that is OVS dependent?06:35
reedipanil_rao : shoot ...06:35
anil_raoI can't think of what that might be06:35
irenabreedip: I gues maybe it was for limiting the spec to what only possible with OVS06:36
*** sc68cal has quit IRC06:36
*** jtomasek has joined #openstack-meeting-306:36
reedipanil_rao : not in the API, but as discussed in some of the earlier meeting logs, we need to split the implementation to allow other vendors like bigswitch and other third party to create thier own versions ( yamamoto_ : I am reading up the ml2 spec, maybe it would help here )06:36
reedipirenab : maybe we can let the API stay , but in the Release notes, mention the limitation to OVS06:37
reedip?06:37
irenabreedip: sounds good06:37
*** rmoe has quit IRC06:37
reedipanil_rao : any suggestions ?06:37
anil_raoThe current implementation is just a reference implementation. I don't see any reason why other backends cannot be implemented by interested parties.06:38
*** vgridnev has quit IRC06:39
reedipanil_rao : you are right.... it is a reference implementation. But when we share the code for review with other neutron reviewers, let make this aspect clear...  ( that this is a reference implementation) , else we might be subjected to a pretty grilling review06:39
reedipanil_rao: thats my point of view ( maybe I could be wrong )06:40
anil_raoBy reference implementation I meant that it is one implementation, which we expect will work in production deployments. So a grilling review is fair game.06:40
anil_raoI also agree that we can make the implementation more friendly to other variants.06:41
*** rmoe has joined #openstack-meeting-306:41
reedipanil_rao: yes , but for this release, we can limit the scope, and let it expand in the future06:41
anil_raoreedip: Agree06:42
reedipthat would definitely require rework in the future, but allow us to provide a working software06:42
reedipin the demo in Austin06:42
irenabreedip: As long as the layering is good and API/Plugin are backend agnostic, this should be ok. but maybe its beyond the spec which in my opinion should focus on generic stuff06:42
*** FallenPe_ has quit IRC06:42
yamamoto_vlan_range_start config seems a little implementation specific.06:42
fawadkhaliqyamamoto_: +106:43
anil_raoyamamoto_: I agree about that. I would consider that more implementation dependent than a portion of the API spec.06:43
reedipirenab : yes, API may not require this information... however, this was one of the points which I observed cross-referencing different links, so thought of putting it up in the discussion, maybe it should have been a separate point06:44
anil_raoAlso, vlan_range is a stop gap measure until the community comes to an agreement on how to share resources in OVS.06:44
*** vgridnev has joined #openstack-meeting-306:45
anil_raoApparently the ML2 driver extensions work does not address this crucial issue06:45
yamamoto_maybe those options can be moved into a separate group eg. [taas_ovs]06:45
anil_raoyammamoto_: That should be fine.06:46
reedipyamamoto_ +106:46
anil_raoI am still worried though on how different projects plan to simultaneously work with OVS flows at the same time.06:46
anil_raoNot sure where to bring this up?06:46
anil_raoAny thoughts?06:47
reedipML , and Austin summit06:48
yamamoto_i guess ML is best for the topic06:48
reedipwe should actually have a discussion with all the neutron core ... this may be a good point for discussion06:48
anil_raoreedip,yamamoto_: ok06:48
*** rmoe has quit IRC06:49
anil_raoLet's move to the next topic, if that's okay.06:49
anil_rao#topic Spec Discussion06:51
*** openstack changes topic to "Spec Discussion (Meeting topic: taas)"06:51
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html06:51
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html06:51
soichianil_rao: thank you for your comments06:52
anil_raosoichi: You are welcome. The TaaS UI looks very nice. :-)06:52
soichii'm preparing to share source code06:53
anil_raosoichi: Awesome!06:53
*** rmoe has joined #openstack-meeting-306:53
anil_raosoichi: I have a few questions on your reply.06:53
soichiyes06:53
*** evgenyf has joined #openstack-meeting-306:54
anil_raoI wasn't sure about the part where you mentioned there being a lot of ports being shown. Can you kindly explain?06:55
soichiif an instance is selected by user, we can list ports associated with the instance06:55
soichiotherwise all ports can be a candidate06:56
anil_raosoichi: Ok, I got it.06:56
anil_raoWouldn't the same be the case for the tap-service-create operation though.06:57
anil_raowe do allow the the user to specify the (destination) port for the tap-service-create call06:57
*** vgridnev has quit IRC06:58
soichianil_rao: yes, I think so06:58
soichii guess destination port should be created with a name06:59
*** hoangcx has quit IRC06:59
soichithen, a uesr can select an appropriate port by seeing name06:59
anil_raosoichi: Let me think about this some more. If I have a better idea I'll add to the email thread.07:00
soichiyes, thank you07:00
*** tqtran-afk has joined #openstack-meeting-307:01
anil_raoThere is an aspect of the API that still bothers me. Let me try to explain.07:01
reedip??07:01
anil_raoThe current API only returns a failure due to some prelimiary checks carried out by the TaaS plugin. After the control is dispatched to the TaaS agent/driver, we have not mechanism of notifying the front-end that a call failed.07:02
*** fawadkhaliq has quit IRC07:03
anil_raoI think we need to fix this, otherwise we will end up in a situation where the front-end thinks that a tap-service/tap-flow is correctly instantiated when it might not acutally be the case.07:03
*** ihrachys has joined #openstack-meeting-307:03
*** hoangcx has joined #openstack-meeting-307:04
*** fawadkhaliq has joined #openstack-meeting-307:04
anil_raoMy suggestion is to add the concept of a status field, similar to other OpenStack operations.07:04
*** rmoe has quit IRC07:04
anil_raoThis status could be in-progress, succeed or failed.07:04
reedipanil_rao : similar to what has already been done in LBaaS07:04
anil_raoIt will also help in the situations where the backend logic takes a while to complete a call.07:05
*** tqtran-afk has quit IRC07:05
anil_raoreedip: Yes. Actually many OpenStack projects work in this fashion.07:05
reediplike Start -> Pending-Create -> Failure or Start -> Pending-Create -> Success07:05
anil_raoYes, something like that. :-)07:05
*** rmoe has joined #openstack-meeting-307:06
reedipanil_rao : actually this is a pretty common design pattern ... we can ( and from what you said we should) implement it07:06
anil_raoThis will affect the UI work that Soichi and Kaz are doing too.07:06
anil_raoreedip: Agree07:06
*** ihrachys has quit IRC07:06
yamamoto_+1 for having status07:07
anil_raoLet me write up a description on the ML and also submit a bug .07:07
soichi+107:07
kazreedip: +107:07
reedipanil_rao: you have now 3 emails for ML :)07:08
*** rmoe has quit IRC07:08
anil_raoYes, I will be on it tomorrow morning. After the time change here (daylight savings) its now midnight. :-(07:08
anil_raoAny other thoughts on the TaaS Dashboard work?07:11
*** vgridnev has joined #openstack-meeting-307:12
anil_raook, next topic then.07:12
anil_rao#topic Discussion over Summit presentation07:13
*** openstack changes topic to "Discussion over Summit presentation (Meeting topic: taas)"07:13
*** rmoe has joined #openstack-meeting-307:13
reedipSo I wanted to know how and when we could meet up07:13
reediphow to proceed with the presentation07:13
anil_raoHere are some thoughts.07:13
reedipwhat matter would we present07:13
anil_raoWe can set up a WebEx session next week (on Fawad's request) to discuss this.07:14
anil_raoFawad will be preparing a template.07:14
fawadkhaliqanil_rao: yes, let's do it07:14
anil_raoWe should essentially cover the things we mentioned in the abstract of the proposal.07:14
fawadkhaliqanil_rao: reedip I will come up with template, that we can all fill in and divide07:15
fawadkhaliqanil_rao: +!07:15
fawadkhaliqanil_rao: +107:15
anil_raoI will also share some thoughts on the demo. Please feel free to debate and discuss07:15
reedipanil_rao: sounds like a plan07:15
*** lpetrut has joined #openstack-meeting-307:15
anil_raoI am putting together a new DevStack env with all of the latest code changes (there have been quite a few recently). :)07:16
*** rmoe has quit IRC07:16
reedipanil_rao : Honest Request ... please keep the session on a day when there is no T20 match for India :D07:16
fawadkhaliqreedip: lol07:16
pgadiyareedip: lol :)07:17
reedip:D07:17
anil_raoSure. :-)07:17
reedipthanks07:17
*** nkrinner has joined #openstack-meeting-307:17
*** rmoe has joined #openstack-meeting-307:17
anil_raoI think it will be nice to incorporate both the Neutron client and the TaaS UI in the demo to show progress over the past Tech Talk.07:18
soichianil_rao: i agree07:19
reedipanil_rao : +107:19
anil_raoNext topics:07:20
anil_rao#topic Announcement: New Core Reviewers07:20
*** openstack changes topic to "Announcement: New Core Reviewers (Meeting topic: taas)"07:20
anil_raoBased on all the +ve votes received yamamoto_ and soichi are our new core reviewers.07:21
yamamoto_thank you07:22
soichithank you07:22
reedip+107:23
kaz+107:23
reedipsorry, now you guys would give  +2 :D07:23
*** rmoe has quit IRC07:23
anil_rao#topic Study up ML2 extension07:23
*** openstack changes topic to "Study up ML2 extension (Meeting topic: taas)"07:23
fawadkhaliqcongrats yamamoto_ soichi07:23
fawadkhaliq:)07:24
reedipyeah, I have started to study the extension implementation, have some confusions. I would ask yamamoto_ and fawadkhaliq once I read it a bit more07:24
reedipit was mentioned basically as a progress report07:25
*** fawadkhaliq has quit IRC07:25
anil_raoThat's good.07:25
anil_rao#topic Issue observed for empty tap-service/tap-flow listing07:26
*** openstack changes topic to "Issue observed for empty tap-service/tap-flow listing (Meeting topic: taas)"07:26
*** fawadkhaliq has joined #openstack-meeting-307:26
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html07:26
*** fawadkhaliq has quit IRC07:26
anil_raoreedip: I belive this is now closed.07:26
reedipanil_rao : yup07:27
*** fawadkhaliq has joined #openstack-meeting-307:27
reedipI think soichi carried it forward while editing the agenda for today, and I forgot to remove it07:27
anil_raoLooks like we covered all of the agenda items today. :-)07:27
*** rmoe has joined #openstack-meeting-307:27
anil_raoAny other open issues for discussion. We have a couple of minutes07:27
soichioh, excuse me07:27
anil_raosoichi: Yes07:28
soichijust copy and paste last week agenda07:28
reedipsoichi : I guessed so, no issues, I also forgot :)07:29
soichi:)07:29
anil_raoOK, time's up.07:30
anil_rao#endmeeting07:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:30
openstackMeeting ended Wed Mar 16 07:30:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-16-06.30.html07:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-16-06.30.txt07:30
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-16-06.30.log.html07:30
anil_raoThanks everyone.07:30
soichibye07:30
kazbye all07:30
anil_raoBye07:30
*** kaz has quit IRC07:31
reedipcheeriyo everyone :)07:32
*** soichi has left #openstack-meeting-307:32
*** anil_rao has quit IRC07:33
*** rmoe has quit IRC07:33
*** FallenPegasus has joined #openstack-meeting-307:33
*** rmoe has joined #openstack-meeting-307:34
*** vtech has joined #openstack-meeting-307:34
*** FallenPegasus has quit IRC07:38
*** rmoe has quit IRC07:39
*** rmoe has joined #openstack-meeting-307:40
*** vtech has quit IRC07:42
*** amotoki has joined #openstack-meeting-307:46
*** rmoe has quit IRC07:47
*** rmoe has joined #openstack-meeting-307:48
*** klkumar has joined #openstack-meeting-307:54
*** vgridnev has quit IRC07:54
*** rmoe_ has joined #openstack-meeting-307:56
*** mkovacik has joined #openstack-meeting-307:57
*** rmoe has quit IRC07:57
*** belmoreira has joined #openstack-meeting-307:58
*** toddjohn has joined #openstack-meeting-307:58
*** vtech has joined #openstack-meeting-308:01
*** toddjohn has quit IRC08:03
*** lpetrut has quit IRC08:04
*** ihrachys has joined #openstack-meeting-308:04
*** rmoe_ has quit IRC08:05
*** rmoe has joined #openstack-meeting-308:06
*** matrohon has joined #openstack-meeting-308:11
*** rmoe has quit IRC08:12
*** dslevin has joined #openstack-meeting-308:12
*** dslevin has quit IRC08:13
*** rossella_s has joined #openstack-meeting-308:13
*** rmoe has joined #openstack-meeting-308:14
*** hoangcx has quit IRC08:14
*** rmoe has quit IRC08:19
*** hoangcx has joined #openstack-meeting-308:19
*** rmoe has joined #openstack-meeting-308:20
*** kbyrne has joined #openstack-meeting-308:22
*** rmoe has quit IRC08:24
*** jschwarz has joined #openstack-meeting-308:27
*** FallenPegasus has joined #openstack-meeting-308:28
*** rmoe has joined #openstack-meeting-308:30
*** iyamahat has joined #openstack-meeting-308:31
*** mrmartin has joined #openstack-meeting-308:32
*** FallenPegasus has quit IRC08:32
*** yamahata has quit IRC08:33
*** rmoe has quit IRC08:36
*** ig0r_ has quit IRC08:39
*** rmoe has joined #openstack-meeting-308:41
*** iyamahat has quit IRC08:41
*** rmoe has quit IRC08:45
*** andymaier has joined #openstack-meeting-308:45
*** rmoe has joined #openstack-meeting-308:45
*** cartik has joined #openstack-meeting-308:47
*** watanabe_isao has quit IRC08:52
*** rmoe has quit IRC08:52
*** vgridnev has joined #openstack-meeting-308:52
*** rmoe has joined #openstack-meeting-308:52
*** safchain has joined #openstack-meeting-308:54
*** rmoe has quit IRC08:59
*** lhartal has joined #openstack-meeting-308:59
*** elisha_r has joined #openstack-meeting-309:00
*** toddjohn has joined #openstack-meeting-309:00
*** idan_hefetz has joined #openstack-meeting-309:00
elisha_r#startmeeting vitrage09:00
openstackMeeting started Wed Mar 16 09:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is elisha_r. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
elisha_rHi everyone :-)09:00
lhartalhello :)09:01
idan_hefetzgood morning elisha_r and everyone!09:01
*** alexey_weyl has joined #openstack-meeting-309:01
*** rmoe has joined #openstack-meeting-309:02
*** dedery has joined #openstack-meeting-309:02
elisha_rOur agenda: * Current status * Review action items * Next steps  * Open Discussion09:03
elisha_rOur agena:09:03
elisha_r* Current status09:03
elisha_r* Review action items09:03
alexey_weylhello09:03
elisha_r* Next steps09:03
elisha_r* Open Discussion09:03
*** emalin has joined #openstack-meeting-309:04
emalinhi09:04
*** amir_gur has joined #openstack-meeting-309:04
elisha_rHi09:05
*** toddjohn has quit IRC09:05
elisha_r#topic Current status09:05
*** openstack changes topic to "Current status (Meeting topic: vitrage)"09:05
elisha_rI'll start.09:05
elisha_rSo this week was very productive. We completed the scenario evaluator, with three actions (raise_alarm, set_state and add_causal_relationship). This effectively gives us support for deduced alarms, deduced states and RCA.09:05
elisha_rFor all of these we have support in the Vitrage Horizon09:06
elisha_rWe plan on uploading a demo of these features this week.09:06
*** danoffek has joined #openstack-meeting-309:06
elisha_rAlso, ifat and ohad presented all of this at the OPNFV Hackfest this week, which went very well to the best of my understanding.09:06
emalinBravo09:06
*** jlanoux has joined #openstack-meeting-309:07
elisha_rWe're finalizing the documentation for this feature, hope to upload it by the end of the week.09:07
elisha_rThat's it from me.09:08
elisha_rAnyone else have updates?09:08
danoffekRPC chapter finished for now. We have everything supported except for the schedualer / conductors which will not be in this phase.09:09
elisha_rsounds great!09:09
*** mbound has joined #openstack-meeting-309:10
elisha_rdanoffek - is there a clear idea of when the remaining features will be supported?09:11
*** salv-orlando has joined #openstack-meeting-309:11
*** rmoe has quit IRC09:12
danoffekI have a clear idea when it won't. in the near 2 months I see no future development in this area09:12
elisha_rok. thanks09:12
idan_hefetzI'll update09:12
idan_hefetzCurrently on the Notifiers and Aodh notifier blueprint.09:13
idan_hefetzBus messaging infra is ready, so that the evaluator sends messages to the bus regarding deduced alarms.09:13
idan_hefetzAlso, I've added a 'vitrage-notifier' service that listens to these messages.09:13
idan_hefetzCurrently working on the vitrage-notifier so it will have Ceilometer client to create and update aodh alarms.09:13
*** rmoe has joined #openstack-meeting-309:13
idan_hefetzTo create the client i'm adding the 'service credentials' to the configuration so that we have a keystone client to create the other clients (such as nova and ceilometer)09:14
idan_hefetzThat's it09:14
elisha_rgreat progress!09:15
elisha_rso, what remains in order for the notifier to be fully operational?09:16
idan_hefetzI need to address the actual creation of the aodh alarms by the client09:17
idan_hefetzand do some refactoring so syncronizers use the keystone client09:17
elisha_rcool.09:18
elisha_ranyone else?09:18
emalinI will update09:20
emalinWe are going to use vitrage in nfvo system09:20
emalinWe would need ability to load new plugins that are not part of vitrage oprigianl code09:20
*** rmoe has quit IRC09:21
*** nadav_yakar has joined #openstack-meeting-309:21
emalinI'm meaning they porbably won't be part of vitrage repository since the nfvo system is not part of openstack at all09:21
*** ayaho has joined #openstack-meeting-309:22
elisha_rso, do you plan on adding a blueprint for vitrage to support this?09:22
ayahohi09:22
emalinWe may also want plugable authorization method09:22
emalin@elisha_r regards plugin - we still need to learn the current capabilities of vitrage09:23
emalinIf it's not supported yet, we will create new blueprint09:23
elisha_rok. sounds good09:23
emalinRegards authorization, I pretty sure we will need new blueprint09:24
*** kzaitsev_mb has joined #openstack-meeting-309:24
emalinWe heard there thoughts about changing the transformers to yaml files09:24
emalinIs it going to happen in the coming days?09:25
*** rmoe has joined #openstack-meeting-309:26
lhartalI have done POC on that and hopefully in the near future (not coming days) I will insert it09:26
*** Eva-i has left #openstack-meeting-309:27
emalinOK09:28
elisha_rok. any more updates?09:28
elisha_r#topic Review action items09:30
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:30
elisha_relisha_r upload documentation for evaluator09:31
elisha_rThis will hopefully take place this week09:31
elisha_r#topic Next Steps09:32
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:32
*** JeanBriceCombebi has joined #openstack-meeting-309:32
*** dedery_ has joined #openstack-meeting-309:32
elisha_rThe evaluator is done for basic functionality of deduced an RCA. However, there are several important features we still need to get a more stable and robust evaluator09:32
elisha_rThe main two we should consider next are support for NOT in the scenario condition, and dealing with template overlap09:33
elisha_rI think it would be a good idea to plan for these, perhaps add relevant blueprints for this.09:35
elisha_rthat;s it from me09:35
elisha_ranyone else?09:35
*** zhurong has quit IRC09:35
*** rmoe has quit IRC09:36
lhartalI have whish list: I want to add Template Content Validation and templates API09:36
danoffekI'm adding new templates to the basic templates list09:36
*** dedery has quit IRC09:37
elisha_r#action support template validation09:38
elisha_r(not sure I'm using the hash sign correctly...)09:38
*** wojdev has joined #openstack-meeting-309:38
elisha_r#topic Open Discussion09:39
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:39
elisha_ranyone have something to discuss?09:39
*** tfukushima has quit IRC09:39
*** danoffek has left #openstack-meeting-309:39
amir_gurbye09:39
*** amir_gur has left #openstack-meeting-309:39
elisha_rok. bye everyone...09:40
lhartalbye bye09:41
*** rmoe has joined #openstack-meeting-309:41
elisha_r#endmeeting09:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:41
openstackMeeting ended Wed Mar 16 09:41:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-16-09.00.html09:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-16-09.00.txt09:41
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-16-09.00.log.html09:41
*** wojdev has quit IRC09:42
*** sdague has joined #openstack-meeting-309:43
*** alexey_weyl has quit IRC09:43
*** amotoki has quit IRC09:43
*** lhartal has quit IRC09:44
*** rmoe has quit IRC09:45
*** rmoe has joined #openstack-meeting-309:46
*** nadav_yakar has quit IRC09:47
*** emalin has quit IRC09:47
*** tfukushima has joined #openstack-meeting-309:48
*** dims has joined #openstack-meeting-309:51
*** sdague has quit IRC10:00
*** rmoe has quit IRC10:01
*** tqtran-afk has joined #openstack-meeting-310:01
*** sdague has joined #openstack-meeting-310:03
*** neiljerram has joined #openstack-meeting-310:05
*** tqtran-afk has quit IRC10:06
*** lpetrut has joined #openstack-meeting-310:09
*** JeanBriceCombebi has quit IRC10:09
*** rmoe has joined #openstack-meeting-310:10
*** sdague has quit IRC10:11
*** sdague has joined #openstack-meeting-310:12
*** rmoe has quit IRC10:13
*** hoangcx has quit IRC10:13
*** rmoe has joined #openstack-meeting-310:15
*** rmoe has quit IRC10:19
*** rmoe has joined #openstack-meeting-310:20
*** fwdit has joined #openstack-meeting-310:21
*** sambetts|afk is now known as sambetts10:22
*** rmoe has quit IRC10:27
*** rmoe has joined #openstack-meeting-310:28
*** rmoe has quit IRC10:33
*** rmoe has joined #openstack-meeting-310:33
*** dedery has joined #openstack-meeting-310:37
*** rmoe has quit IRC10:38
*** dedery_ has quit IRC10:40
*** rmoe has joined #openstack-meeting-310:40
*** davidsha has joined #openstack-meeting-310:41
*** dedery has quit IRC10:41
*** rmoe has quit IRC10:45
*** rmoe has joined #openstack-meeting-310:48
*** rmoe has quit IRC10:52
*** rmoe has joined #openstack-meeting-310:53
*** toddjohn has joined #openstack-meeting-310:53
*** dims has quit IRC10:53
*** salv-orlando has quit IRC10:56
*** rmoe has quit IRC10:57
*** rmoe has joined #openstack-meeting-310:58
*** toddjohn has quit IRC10:58
*** dims has joined #openstack-meeting-310:59
*** kzaitsev_mb has quit IRC10:59
*** numans has quit IRC11:02
*** FallenPegasus has joined #openstack-meeting-311:02
*** numans has joined #openstack-meeting-311:04
*** yamamoto_ has quit IRC11:05
*** rmoe has quit IRC11:06
*** rmoe has joined #openstack-meeting-311:06
*** FallenPegasus has quit IRC11:07
*** tfukushima has quit IRC11:12
*** tfukushima has joined #openstack-meeting-311:13
*** rmoe has quit IRC11:13
*** tfukushima has quit IRC11:13
*** rmoe has joined #openstack-meeting-311:15
*** klkumar has quit IRC11:15
*** numans has quit IRC11:16
*** numans has joined #openstack-meeting-311:16
*** rmoe has quit IRC11:20
*** rmoe has joined #openstack-meeting-311:21
*** rtheis has joined #openstack-meeting-311:24
*** numans has quit IRC11:29
*** klkumar has joined #openstack-meeting-311:29
*** davidsha has quit IRC11:31
*** rmoe has quit IRC11:32
*** vgridnev has quit IRC11:34
*** rmoe has joined #openstack-meeting-311:39
*** ihrachys has quit IRC11:42
*** ihrachys has joined #openstack-meeting-311:42
*** ihrachys has quit IRC11:42
*** kzaitsev_mb has joined #openstack-meeting-311:44
*** rmoe has quit IRC11:51
*** rmoe has joined #openstack-meeting-311:52
*** primeministerp has joined #openstack-meeting-311:52
*** vtech has quit IRC11:55
*** vtech has joined #openstack-meeting-311:56
*** rmoe has quit IRC11:57
*** salv-orlando has joined #openstack-meeting-311:57
*** r1chardj0n3s has joined #openstack-meeting-311:57
*** rmoe has joined #openstack-meeting-311:57
*** tsufiev has joined #openstack-meeting-311:59
*** claudiub has joined #openstack-meeting-311:59
*** ayaho has quit IRC12:00
*** robcresswell has joined #openstack-meeting-312:00
david-lyle#startmeeting Horizon12:00
openstackMeeting started Wed Mar 16 12:00:55 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: Horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
robcresswello/12:01
tsufievhi12:01
*** abalutoiu has joined #openstack-meeting-312:01
r1chardj0n3so/12:01
*** itoader has joined #openstack-meeting-312:01
*** dedery has joined #openstack-meeting-312:01
*** atuvenie has joined #openstack-meeting-312:02
doug-fish\o12:02
* david-lyle tries to fight through the crowd to the front12:03
mrungeo/12:03
david-lyleLet's get started12:03
david-lyleRC-1 should happen this week12:03
david-lylethat's my primary concern right now12:03
david-lyleI've moved one bp out of RC-1 as it wasn't going to close12:04
*** dedery has quit IRC12:04
david-lyleThe consistency group one is also at risk12:04
david-lyleand the launch instance one needs a little more work12:04
robcresswellI don't think volumes is going to make it; still have a concern with some parts, and there's been no other core reviews on it.12:04
*** rmoe has quit IRC12:05
robcresswellPorts I'm just updating, that should be good to go in a couple hours12:05
david-lylerobcresswell: ok thanks12:05
david-lyleso I think one bp realistically is still in play12:06
david-lylethen the remaining bugs12:06
*** cartik has quit IRC12:07
*** rmoe has joined #openstack-meeting-312:07
*** baoli has joined #openstack-meeting-312:07
david-lylethere's only one or two bugs in the RC list that look worthy of slowing the RC for12:07
*** yamamoto has joined #openstack-meeting-312:08
doug-fishI assume you are thinking https://bugs.launchpad.net/horizon/+bug/1543891 ?12:09
openstackLaunchpad bug 1543891 in OpenStack Dashboard (Horizon) "Launch instance from Volumes Snapshot Page opens LEGACY launch instance, even if LEGACY is set to False in local_settings" [High,In progress] - Assigned to Matt Borland (palecrow)12:09
tsufievI would say every one of third High bugs is nice to see fixed in M12:09
tsufiev*of three12:09
robcresswellhttps://bugs.launchpad.net/horizon/+bug/1553314 This one is quite important and a small fix.12:10
openstackLaunchpad bug 1553314 in OpenStack Dashboard (Horizon) "Attempting to create a volume after deleting one fails" [High,In progress] - Assigned to Timur Sufiev (tsufiev-x)12:10
david-lyleyes those two12:10
*** vgridnev has joined #openstack-meeting-312:10
tsufievhaven't looked at Angular actions after jQuery refresh recently, does it work already?12:10
tsufievI mean https://bugs.launchpad.net/horizon/+bug/151462712:11
openstackLaunchpad bug 1514627 in OpenStack Dashboard (Horizon) "Angular actions not evaluated properly when dependent on row update." [Medium,In progress] - Assigned to Tyr Johanson (tyr-6)12:11
*** rmoe has quit IRC12:11
robcresswellNo, and Tyr has only put up a partial fix and no others.12:11
doug-fishthere is a patch merged I think12:11
doug-fishoh12:11
*** rmoe has joined #openstack-meeting-312:11
david-lylewhat views are actually impacted?12:11
david-lylejust images? or objects as well12:12
robcresswellThe angular actions one?12:12
david-lylesorry, yes12:12
tsufievevery table with Update Metadata Actions, every table with Launch Instance NG action12:12
robcresswellAnything that can do launch instance (volumes, images, snapshots)12:12
david-lyleok, that is a high then12:13
david-lyle:(12:13
robcresswellIf oyu create one, then try and launch an instance, the button doesnt work.12:13
tsufievI invented an ugly ad-hoc solution for that issue: https://review.openstack.org/#/c/289849/112:13
tsufievif we need some desperate measures :)12:13
robcresswellNo, that involves undoing the strict-di bp from earlier12:14
david-lyleso what did the merged patch help, anything?12:14
tsufievyep, that's why I called them desperate12:14
robcresswellSomething to do with images, which isnt even enabled12:14
david-lylesuper12:14
david-lyleso that one is not in progress12:15
david-lylelooks like we have an opportunity12:15
david-lylemoved to unassigned and confirmed12:16
david-lyleplease take if you have an idea12:16
*** ihrachys has joined #openstack-meeting-312:16
tsufiev robcresswell: but if we could find a way to inject $injector into legacy JS without undoing ng-strict-di, my solution would be less ugly12:16
*** rmoe has quit IRC12:16
robcresswellSure12:16
robcresswellThe thing is, there are 2 outstanding bugs against LI behaviour that I would consider blocking issues12:16
r1chardj0n3sI'm having trouble following that, I'll have to look into it tomorrow ;-)12:17
david-lyleso the other option is go back to legacy, which isn't ideal12:17
robcresswellIf we can't get these sorted in the next day, we'll likely have to consider reverting LI-default.12:17
robcresswellYes.12:17
tsufievoh12:18
david-lylelet's see if we can make progress12:18
tsufiev:(12:18
david-lyleare there any other issues that people want to mention leading into the RC?12:18
robcresswellI'll reviews tsufievs patch for https://bugs.launchpad.net/horizon/+bug/1553314 and get Ports updated, then see what I can do about the other bugs.12:18
openstackLaunchpad bug 1553314 in OpenStack Dashboard (Horizon) "Attempting to create a volume after deleting one fails" [High,In progress] - Assigned to Timur Sufiev (tsufiev-x)12:18
robcresswellOops, sorry for speaking over you there :)12:19
*** rmoe has joined #openstack-meeting-312:19
david-lylenot over me, you're good12:19
david-lylethe other thing is please continue to test12:19
david-lyleif we find other issues we have RC-2 to correct if need be12:19
tsufievactually this one https://bugs.launchpad.net/horizon/+bug/1528465 could be annoying as well12:20
openstackLaunchpad bug 1528465 in OpenStack Dashboard (Horizon) "dashboard project network column display duplicate default public network randomly (with admin)" [Medium,In progress] - Assigned to Akihiro Motoki (amotoki)12:20
tsufievI can confirm it12:20
robcresswelltsufiev: Patch is in the gate12:21
robcresswellSeems its already fixed?12:21
david-lyleyeah that one is in the gate12:21
tsufievrobcresswell, never mind then :)12:21
tsufievneed new status for LP: Patch is in gate12:21
david-lylepatch is 3/4 through gate and no failing tests12:22
robcresswelldon't jinx it12:22
*** sonu has joined #openstack-meeting-312:22
david-lylewould be a helpful status in LP :)12:22
david-lyleok, that's the RC12:23
david-lyle#topic summit space12:24
*** openstack changes topic to "summit space (Meeting topic: Horizon)"12:24
*** kzaitsev_mb has quit IRC12:24
david-lyleI was informed there may potentially be extra fishbowl or working session space at the summit12:24
david-lyledo we desire any additional space?12:25
david-lylewe were 1 fishbowl and 7 working session12:25
r1chardj0n3sit'd be really good if we could get a cross-project yelling space to sort out xstatic ...12:25
david-lylethat's a different pool generally12:25
r1chardj0n3swe got *so* close last week12:25
r1chardj0n3sok12:25
*** kzaitsev_mb has joined #openstack-meeting-312:25
tsufievis the stable/mitaka branch cut with with the first RC or with the final one?12:26
david-lyleif we use one of our times I think we'll have lots of people with conflcts12:26
david-lyletsufiev: first one12:26
doug-fishhave we started collecting topics for the summit yet?12:26
david-lyledoug-fish: not yet12:26
david-lylewe should probably get the etherpad rolling12:26
david-lyleI can post today12:27
doug-fishMight be easier to sort out space needs if we knew the topics. My suspicion is that 8 is plenty, but a topic list might show otherwise12:27
tsufievjfyi: I won't be in Austin this summit :/12:27
doug-fish:-(12:28
robcresswell:(12:28
r1chardj0n3s:( tsufiev12:28
*** salv-orlando has quit IRC12:28
*** pcaruana has quit IRC12:28
david-lyle?12:28
*** rmoe has quit IRC12:29
david-lylewell then worse performance is back on the agenda12:29
david-lyle;-)12:29
david-lylesorry to hear that tsufiev12:29
tsufievjust more tight budget this time, hope it's the only time I was notified too late to apply for Travel Support program12:30
david-lylethat's unfortunate12:30
*** rmoe has joined #openstack-meeting-312:30
david-lylesounds like we're ok on space12:31
david-lylemoving on12:31
tsufievwill use the free time to finish OSProfiler work, there are always side benefits :)12:31
david-lyletsufiev: a week of uninterrupted work isn't bad12:31
*** fawadkhaliq has quit IRC12:31
david-lyle#topic PTL election12:32
*** openstack changes topic to "PTL election (Meeting topic: Horizon)"12:32
*** itoader has quit IRC12:32
tsufievseems that Rob has no competitors :)12:32
david-lylewe're in the final 40  or so hours of nominations12:32
david-lyleand yes Rob is the only brave soul to step up12:32
robcresswells/brave/stupid :)12:33
r1chardj0n3sawesome12:33
tsufievrobcresswell, aren't you afraid that you'll have to bear this for another 4 cycles ;)?12:33
david-lyletsufiev: don't scare him off12:33
tsufievhaha, okay, I'm shutting up12:34
david-lyle#topic Horizon and not-sanitized data from other OpenStack services - how should we handle it?12:34
*** openstack changes topic to "Horizon and not-sanitized data from other OpenStack services - how should we handle it? (Meeting topic: Horizon)"12:34
david-lylethis was the only item on the agenda12:35
tsufievah, yes, that one is mine12:35
r1chardj0n3sI think we should sneer a lot at the services12:35
robcresswellr1chardj0n3s: +112:35
tsufievwe've got a bug recently with some Cinder data being displayed by Horizon - but it hadn't been filled in in Horizon, so it hadn't been sanitized12:35
doug-fishlink?12:36
* tsufiev searching12:36
david-lyletsufiev: sanitized in what sense? embedded JS?12:36
david-lyleor something less sinister12:36
tsufievoops, it's a private security bug12:37
doug-fishok understood12:37
tsufievlet me describe it briefly12:37
tsufievone can put JS injection into Cinder db using CLI12:38
tsufievthen it is displayed by Horizon12:38
*** rmoe has quit IRC12:38
david-lylethis is not a horizon security bug?12:38
doug-fishdisplayed  = executed?12:38
doug-fishas in, it runs the javascript?12:39
*** fwdit has quit IRC12:39
tsufievdoug-fish, yes12:39
r1chardj0n3sah, whoopsie12:39
doug-fishsounds like a Horizon security bug to me12:39
david-lyledoug-fish: I just don't see it12:39
tsufievdavid-lyle, we've been discussing (internally) who should sanitize it12:39
david-lyleah so not even upstream bug yet12:39
*** fwdit has joined #openstack-meeting-312:39
*** rmoe has joined #openstack-meeting-312:39
tsufievas of now this a our downstream repo bug, I'll file it as Horizon security12:39
tsufievsorry, should have done this in advance12:40
david-lyletsufiev: you can assign both cinder and horizon upstream and have those teams weigh in12:40
r1chardj0n3sthat poses a question: do we have cores who are allows to deal with secret security bugs?12:40
david-lylebut horizon should sanitize it12:40
tsufievok12:40
david-lyler1chardj0n3s: horizon-sec12:40
r1chardj0n3sthx12:40
david-lyleis a subset of horizon-core12:40
david-lyleif there are cores interested please ping me or the next PTL depending on your timing of wanting in12:41
david-lyleprocess is a bit different, so the group is limited12:41
tsufievwill update bug's status in a couple of minutes, once I discuss it with our security guy12:42
david-lyletsufiev: make sure when you file it to mark as private security12:43
doug-fishand don't put it out for normal review!12:43
*** rmoe has quit IRC12:43
robcresswellIf there's time, we should also discuss the new Swift UI.12:44
david-lyledoug-fish: ++12:44
david-lyleall reviews happen as attachments to the bug12:44
*** rmoe has joined #openstack-meeting-312:44
david-lyleonce there is a review in jenkins the bug is no longer private12:44
david-lyleand will be set as such12:44
*** yamamoto has quit IRC12:45
*** elisha_r has quit IRC12:45
david-lyletsufiev: we have lots of areas where we sanitize data, so we must be missing one12:45
david-lyle#topic swift views12:45
*** openstack changes topic to "swift views (Meeting topic: Horizon)"12:45
david-lylego robcresswell12:45
robcresswellSo the angular swift views have all merged12:47
*** abalutoiu_ has joined #openstack-meeting-312:47
r1chardj0n3s(thanks everyone)12:47
tsufiev:)12:47
robcresswellLast I checked we hadnt quite decided what to do w/ regards to moving over.12:47
robcresswellI'm in favour of holding the python content, but making the angular content default.12:47
david-lylethat was my opinion as well12:47
r1chardj0n3sI have a WIP with what I think is the most palatable approach https://review.openstack.org/#/c/293168/12:48
robcresswellAs it can't not be better.12:48
r1chardj0n3sI didn't get to work on it today, due to needing to look into the ironic ui and another internal thing12:48
tsufiev+112:48
*** rmoe has quit IRC12:49
r1chardj0n3sI hope to complete it tomorrow, though I wonder if that's not pushing the deadline a bit12:49
r1chardj0n3s(noting that "tomorrow" is in 7 hours ;-)12:50
*** alexpilotti has joined #openstack-meeting-312:51
david-lyleI may have time to fix up too12:51
*** FallenPegasus has joined #openstack-meeting-312:51
r1chardj0n3sif someone else wants to grab that patch and run with it while I'm asleep, be my guest.12:51
*** yamamoto has joined #openstack-meeting-312:52
david-lyler1chardj0n3s: ok12:52
*** jlvillal has quit IRC12:52
*** jlvillal has joined #openstack-meeting-312:52
david-lyleany other swifty toughts?12:52
david-lyle*thoughts12:53
*** rmoe has joined #openstack-meeting-312:53
robcresswellnothing from me, other than thanks for the work r1chardj0n3s12:53
*** numans has joined #openstack-meeting-312:53
r1chardj0n3slots more to do!12:53
robcresswelland for persevering with my reviews :)12:53
david-lyleyes thanks r1chardj0n3s12:53
r1chardj0n3s:-)12:53
david-lyle#topic hurgleburgler is a new horizon core12:54
*** openstack changes topic to "hurgleburgler is a new horizon core (Meeting topic: Horizon)"12:54
r1chardj0n3s\o/12:54
robcresswell\o/12:54
doug-fishwell deserved12:54
tsufievmore reviews \o/ :)12:54
robcresswell*.scss -112:55
robcresswellI'm sure she has that scripted somewhere.12:55
david-lyleso congrats to her and welcome12:55
*** ddieterly has joined #openstack-meeting-312:56
*** FallenPegasus has quit IRC12:56
david-lyle#topic Open Discussion12:56
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:56
david-lyle4 minutes for your deepest thoughts12:56
r1chardj0n3sisn't Horizon looking mighty pretty these days?12:56
tsufievr1chardj0n3s, on devstack it is :)12:57
tsufiev*does12:57
*** sagar_nikam has joined #openstack-meeting-312:57
tsufievnext station is Scale Performance12:58
*** abalutoiu_ has quit IRC12:58
*** abalutoiu_ has joined #openstack-meeting-312:58
robcresswellOn that note, I think your nva calls patch is in the gate tsufiev12:58
robcresswellnova*12:58
tsufievrobcresswell, r1chardj0n3s: thank you for that, that's a beginning of a loong way :)12:59
*** rmoe has quit IRC12:59
tsufievwill keep going there12:59
*** rmoe has joined #openstack-meeting-313:00
david-lyleThanks everyone let's wrap up the RC13:00
david-lyle#endmeeting13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Wed Mar 16 13:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-16-12.00.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-16-12.00.txt13:00
*** r1chardj0n3s has left #openstack-meeting-313:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-16-12.00.log.html13:00
*** sagar_nikam_ has joined #openstack-meeting-313:00
*** tsufiev has left #openstack-meeting-313:01
*** robcresswell has left #openstack-meeting-313:01
*** vtech_ has joined #openstack-meeting-313:01
*** vtech has quit IRC13:01
*** vtech_ has quit IRC13:01
*** dtardivel has joined #openstack-meeting-313:02
*** sagar_nikam has quit IRC13:02
*** vtech has joined #openstack-meeting-313:02
alexpilotti#startmeeting hyper-v13:02
openstackMeeting started Wed Mar 16 13:02:22 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: hyper-v)"13:02
atuveniehy all13:02
openstackThe meeting name has been set to 'hyper_v'13:02
abalutoiuo/13:02
*** itoader has joined #openstack-meeting-313:02
alexpilottihello folks13:02
sagar_nikam_hi13:02
sonuhi13:02
itoaderhi13:03
alexpilottilet's start with the first item on the agenda13:03
alexpilotti#topic Hyper-V cluster13:03
*** openstack changes topic to "Hyper-V cluster (Meeting topic: hyper-v)"13:03
*** abalutoiu_ has quit IRC13:03
alexpilottiatuvenie: would you like to give us a status update?13:03
*** abalutoiu_ has joined #openstack-meeting-313:04
alexpilottialso if you could please add a link to the patches for review13:04
*** domi_ has joined #openstack-meeting-313:04
atuvenieyeah. Well, the patch in os-win has 2 +2 and workflow, it's waiting patiently in the gate13:04
domi_hi all!13:04
atuveniehttps://review.openstack.org/#/c/276190/13:04
atuveniethis is for os-win13:04
*** qwebirc64341 has joined #openstack-meeting-313:04
*** rmoe has quit IRC13:05
atuvenieand this is the patch on compute #link https://review.openstack.org/#/c/281115/13:05
*** ducttape_ has joined #openstack-meeting-313:05
*** ducttape_ has left #openstack-meeting-313:05
*** rmoe has joined #openstack-meeting-313:05
alexpilotticool tx13:06
lpetrutHi guys13:06
atuveniethe gate unfortunately is clogged atm and it's taking some time for things to merge13:06
alexpilottiin short this is pretty close to be merged in compute-hyperv13:06
sagar_nikam_nice13:06
sagar_nikam_i hope we can get it merged in Newton upstream13:07
domi_i'd like to mention in this rdp console bug, has anyone seen this?  http://paste.openstack.org/show/e1bCNzN2s6QUJvU5jZvb/13:08
*** domi_ has quit IRC13:08
alexpilottisagar_nikam_: we'll push the patches as usual, we'll resubmit the BPs as soon as window opens, etc13:08
sagar_nikam_alexpilotti: thanks13:08
alexpilottidomi got disconnected13:08
*** qwebirc64341 has quit IRC13:09
alexpilottirather interesting trace indeed13:09
*** atuvenie__ has joined #openstack-meeting-313:09
alexpilotticlaudiub: ^13:09
*** domi__ has joined #openstack-meeting-313:09
*** e0ne has joined #openstack-meeting-313:10
claudiubweird13:10
claudiubseems like a wmi object got out13:10
*** ddieterly has quit IRC13:10
*** rmoe has quit IRC13:11
alexpilottiquestion is, how?13:12
*** rmoe has joined #openstack-meeting-313:12
claudiubRDP console: 10.1.5.24:2179, <wmi._Method object at 0x05589BF0>13:14
claudiubthat wmi_Method is supported to be the vm_id13:14
lpetrutif an attribute is not found, it is treated as a method by PyMI13:14
claudiubexecuting that in my local env yields a proper vm_id13:14
*** neelashah has joined #openstack-meeting-313:15
*** kro_sinus_hell is now known as krot_sinus_purga13:15
*** krot_sinus_purga is now known as kro_sniffles13:15
alexpilottiyou sure it couldnt be the console port? https://github.com/openstack/compute-hyperv/blob/stable/liberty/hyperv/nova/rdpconsoleutilsv2.py#L3113:16
alexpilottilpetrut: we could always match it agains the class method tables, but that'd be an expensive lookup13:16
*** rmoe has quit IRC13:17
domi__thanks for looking into this13:17
alexpilottidomi__: thanks for reporting it13:17
claudiubalexpilotti: the debug message matches this as a format: https://github.com/openstack/compute-hyperv/blob/stable/liberty/hyperv/nova/rdpconsoleops.py#L3713:17
claudiubso, the port is 217913:17
alexpilottidomi__: as a general rule, we need to put it on the agenda, during the meeting13:18
domi__that was my original intention, but I needed to switch to my phone's irc client which sucks :(13:18
alexpilottibest thing would be if you could send an email in advance, but even during the meeting we can just schedule it as a topic13:19
*** rmoe has joined #openstack-meeting-313:19
alexpilottiit this case I was waiting for you to reconnect, so we started looking at it13:19
*** lblanchard has joined #openstack-meeting-313:19
alexpilottianyway, worth taking it offline and looking into it13:19
domi__okay, thanks for describing the process, in the future we will email you an hour before the meeting latest with any agenda items we might have13:20
sagar_nikam_alexpilotti: i have some questions for domi_ on freerdp, if you are fine, can ask it13:20
alexpilottisagar_nikam_: sure, I'm currently looking at some links for the next topic (Rally tests), so please go ahead13:21
domi__hit me :)13:21
sagar_nikam_domi_: where is freerdp running ? on hyperv host where nova-compute is running or on some other host ?13:22
domi__the same host currently13:22
sagar_nikam_ok.. and what are the networks on the hyperv host ?13:23
domi__well it has a mgmt network, storage network (iscsi) multipath and an smb network interface if I remember correctly13:24
*** ig0r_ has joined #openstack-meeting-313:24
sagar_nikam_ok13:24
domi__currently freerdp goes through the mgmt network13:24
*** dslevin has joined #openstack-meeting-313:24
*** Poornima has quit IRC13:24
sagar_nikam_and on which network is horizon access done ?13:24
*** dslevin has quit IRC13:25
*** numans has quit IRC13:25
domi__on the mgmt network, although there is a haproxy first to balance between 2 horizon instances13:25
*** dslevin has joined #openstack-meeting-313:26
sagar_nikam_ok13:26
sagar_nikam_so tenant users access horizon on mgmt-network13:26
sagar_nikam_and since the hyperv host has the mgmt network13:26
sagar_nikam_freerdp works fine13:26
*** dslevin has quit IRC13:26
domi__but it is possible that there is routing involved inbetween13:26
*** pgadiya has quit IRC13:26
*** jpomeroy has joined #openstack-meeting-313:27
sagar_nikam_routing is required ? since horizon access is done on mgmt network13:27
*** e0ne has quit IRC13:27
domi__that's what was changed recently if I'm correct, I need to ask my colleague13:28
sagar_nikam_sure, lets discuss this offline13:28
sagar_nikam_or in the next meeting13:28
*** dslevin has joined #openstack-meeting-313:28
sagar_nikam_you can let me know more details13:28
*** dslevin has quit IRC13:29
*** fawadkhaliq has joined #openstack-meeting-313:29
*** salv-orlando has joined #openstack-meeting-313:29
sagar_nikam_alexpilloti: we can move to next topic13:29
alexpilotticool thanks13:29
*** pgadiya has joined #openstack-meeting-313:30
domi__ok thanks13:30
*** dslevin has joined #openstack-meeting-313:30
alexpilotti#topic Mitaka Rally tests13:30
*** openstack changes topic to "Mitaka Rally tests (Meeting topic: hyper-v)"13:30
*** dslevin has quit IRC13:30
alexpilottiSo we just finished running a new batch of Rally tests on Mitaka, to see how we compare to LIberty13:30
alexpilottiresults are rather impressive, so far:13:30
alexpilotti#link https://dl.dropboxusercontent.com/u/9060190/KVM_vs_PyMI_Mitaka.html13:31
alexpilottiThis is the spawn / destroy test13:31
*** rmoe has quit IRC13:31
sagar_nikam_almost same as kvm... nice13:32
alexpilottiLiberty ones, for comparison: #https://dl.dropboxusercontent.com/u/9060190/PyMI_KVM_ESXi_Liberty.html13:32
*** dslevin has joined #openstack-meeting-313:32
domi__good news!13:32
sonuwould like to see similar results with Neutron13:33
*** dslevin has quit IRC13:33
*** sdake has joined #openstack-meeting-313:33
alexpilottisonu: we're running now a run with ssh guest access13:33
domi__sonu: in our tests neutron is fast but applying the security groups that takes a lot of time13:33
alexpilottiand next a run with Hadoop workloads13:33
sonugreat.13:34
alexpilottithis is very early results of course13:34
claudiubdomi__: the neutron-hyperv-agent is a lot faster in mitaka, btw. :)13:34
*** dslevin has joined #openstack-meeting-313:34
sagar_nikam_alexpilotti: sonu : the patches which were merged for security groups.. does it not fix the issue ?13:34
alexpilottiabalutoiu: sent them while we already started the meeting, so fresh :)13:34
domi__glad to hear that :) although in the end we'd prefer ovs with vxlans :)13:34
*** stanzgy has quit IRC13:35
*** dslevin has quit IRC13:35
sonudomi__: security rules had always been hard to handle in hyper-v. But with many perf improvement patches from Claudiu and Me had yielded better results.13:35
*** d0ugal has quit IRC13:35
*** d0ugal has joined #openstack-meeting-313:35
domi__that's excellent, thank you guys!13:35
sonuwow. OVS is also my pick for HyperV13:35
alexpilottisagar_nikam_ sonu: yes those networking-hyperv patches have a big role in the performance improvements13:35
*** rmoe has joined #openstack-meeting-313:35
*** itoader has quit IRC13:35
*** dslevin has joined #openstack-meeting-313:35
alexpilottiso, we'll get more updates for the next meeting13:36
sagar_nikam_alexpilotti: so why is SG not performing as well ... you mentioned it earlier... am i missing something ?13:36
sonualexpilotti:  Is there any chance we can get them back-ported to Liberty. We have few customers planning to using them with Liberty.13:36
*** vgridnev has quit IRC13:36
*** vgridnev has joined #openstack-meeting-313:37
domi__+1 on that13:37
*** numans has joined #openstack-meeting-313:37
sonuJust asking out of curiosity, since many are on Liberty/stable13:37
alexpilottisonu, we might most probably do that after release, but just remember that BPs cannot be backported upstream13:37
sonuthe native thread patch, and enhanced RPC patch13:37
*** ddieterly has joined #openstack-meeting-313:38
*** vgridnev has quit IRC13:38
sonusure. I understand that process.13:38
alexpilottiwe're focused now on getting Mitaka released, as soon as that is done we'll focus on backports13:38
alexpilottiwe still have lots of users and customers on Kilo or Liberty, so we try to backport as much as we can13:39
sonuthanks. I feel relaxed :)13:39
*** doug-fish has quit IRC13:39
*** salv-orlando has quit IRC13:40
alexpilottinext topic!13:40
alexpilotti#topic OVN13:40
*** openstack changes topic to "OVN (Meeting topic: hyper-v)"13:40
*** alinbalutoiu__ has joined #openstack-meeting-313:41
alexpilottiOVN, is the OVS' team attempt to have a controller that fixes some of the issues that Neutron has, especially when involving the OVS agent13:42
*** doug-fish has joined #openstack-meeting-313:42
sonuit was introduced in vancouver summit if I remember.13:42
alexpilottiit reached a maturity status that allows us to evaluate it as a viable strategy for OVS networking (VXLAN, GRE, etc)13:42
alexpilottione of the advantages is that it's agentless, so no need to bother with the OVS agent on the hyper-v nodes :)13:43
*** rmoe has quit IRC13:43
*** yamamoto has quit IRC13:43
alexpilottiflos and configurations are applied via ovs-db over TCP13:43
alexpilotti*flows13:44
domi__sounds interesting, how would the flow look like with ovn? neutron-node talks to ovn or ovn plugs in directly to openstack?13:44
sonuon windows 2016 I believe13:44
*** abalutoiu has quit IRC13:44
*** rmoe has joined #openstack-meeting-313:44
alexpilottiOVS needs to run on the Hyper-V nodes, so Windows Server 2012+13:45
alexpilotti2016 has some ovsdb support, but it's more like a translation mapping to the new controller that comes with 201613:45
sonubut for that we must have conntrack on OVS for use in hyperv13:45
*** ddieterly is now known as ddieterly[away]13:45
*** abalutoiu_ has quit IRC13:46
sonusince security group rules will get into OVSDB13:46
alexpilottithe general architecture is: Neutron -> OVN plugin -> ovsdb -> ovs-vswitchd on hyper-v nodes13:46
*** pgadiya has quit IRC13:46
domi__alexpilotti: thanks I understand now13:46
*** doug-fish has quit IRC13:46
alexpilottisonu: for that, conntrack support is currently under development in OVS13:47
domi__and then it will be ported by you for windows?13:47
alexpilottiso with OVS 2.6, we should be able to say goodbye to the Hyper-V WMI ACL :)13:47
*** bklei has joined #openstack-meeting-313:47
sonutarget is OVS 2.6 I would say.13:47
sonuyeah13:47
alexpilottiI mean, conntrack on hyper-V is planned for 2.613:47
*** galstrom_zzz is now known as galstrom13:48
domi__okay13:48
alexpilottion linux it's already supported13:48
domi__oh I see :)13:48
alexpilottiso reason to bring this up now is to show the direction that we are investigating13:48
sonuAnd OVS firewall has made it to M313:48
alexpilottiwe'll do more tests with OVN soon, and give you some updates13:49
alexpilottion a sligtly related topic, we are releasing OVS 2.5 for hyper-v this month / early next month13:50
domi__can't wait to see this in action13:50
alexpilottiany questions?13:50
sonureleasing OVS2.5, I did not get it.13:50
domi__is there an updated documentation as well?13:50
sonucertification you meant?13:50
domi__because we still couldn't figure out some stuff...like is the interface in ovs called ehternet1 or the full name etc.13:51
alexpilottiwe dont have a signed OVS 2.5 out yet13:51
*** rmoe has quit IRC13:51
alexpilottiit just got released last month upstream13:51
alexpilottiso wer'e currently packaging etc13:51
alexpilottidocumentation will also be updated13:52
domi__thanks13:52
sonuso we can use it with WMI firewall driver.13:52
sonuor is it we use it w/o security groups13:52
alexpilottiat the moment we dont have any choice: OVS for SDN and WMI ACL for SGs13:52
sonuI did succeed in using WMI firewall driver with OVS implementation13:53
domi__so the ovs agent handles currently sg using wmi?13:53
sonufor VXLAN use case.13:53
alexpilottidomi__: nop, we use both agents13:53
domi__sonu: nice :) we failed on that road13:53
alexpilottisonu: glad to hear that!13:53
alexpilottiwe will surely provide better guidance on how to proceed on that13:53
domi__great thanks13:54
*** mtanino has joined #openstack-meeting-313:54
alexpilottithat was my last topic for today13:54
alexpilotti#topic open discussion13:54
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:54
*** ddieterly[away] is now known as ddieterly13:54
*** armax has joined #openstack-meeting-313:54
alexpilotti6' to go13:54
sagar_nikam_alexpilotti: one topic from me13:55
*** banix has joined #openstack-meeting-313:55
sagar_nikam_certs13:55
alexpilottisure13:55
*** vgridnev has joined #openstack-meeting-313:55
alexpilottianything in particular?13:55
sagar_nikam_http://paste.openstack.org/show/490711/13:55
alexpilottiok13:55
sagar_nikam_the cert is the same from controller13:56
sagar_nikam_no changes13:56
sagar_nikam_just copied to desktop13:56
sagar_nikam_and add these entries in nova.conf13:56
domi__alexpilotti: sidenote - could you provide email addresses for sagar and sonu, so I can ask them about freerdp and ovs? then they don't need to post their addresses here publicly13:56
sagar_nikam_it should all work correctly ?13:56
*** rbak has joined #openstack-meeting-313:56
*** rmoe has joined #openstack-meeting-313:56
*** toddjohn has joined #openstack-meeting-313:56
alexpilottidoes it work with verify = False?13:56
sagar_nikam_not tried that13:57
sagar_nikam_what entry in nova.conf for verify false ?13:57
sagar_nikam_can check it and see if that also works13:57
*** itoader has joined #openstack-meeting-313:57
alexpilottishould still be cafile = False, need to check that13:58
*** rossella_s has quit IRC13:58
alexpilottilet me add ibalutoiu13:58
alexpilottihe recently did exactly that13:58
sagar_nikam_if both work Ie. false and actual cafile13:58
sagar_nikam_then it is fine ?13:59
*** mhoppal has joined #openstack-meeting-313:59
alexpilottiwe need to end the meeting unfortunately13:59
sagar_nikam_we are almost done with the time13:59
alexpilottiI'm starting n email thread13:59
sagar_nikam_sure thanks13:59
*** domi__ has quit IRC13:59
sagar_nikam_it helps13:59
alexpilottithank you all for joining!13:59
alexpilotti#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Mar 16 13:59:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-16-13.02.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-16-13.02.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-16-13.02.log.html14:00
*** sonu has quit IRC14:00
*** doug-fish has joined #openstack-meeting-314:00
*** doug-fish has quit IRC14:01
*** doug-fish has joined #openstack-meeting-314:01
*** mhoppal has quit IRC14:03
*** mhoppal has joined #openstack-meeting-314:03
*** tqtran-afk has joined #openstack-meeting-314:03
*** [1]evgenyf has joined #openstack-meeting-314:04
*** rmoe has quit IRC14:04
*** rmoe has joined #openstack-meeting-314:05
*** sigmavirus24_awa is now known as sigmavirus2414:06
*** devkulkarni has joined #openstack-meeting-314:06
*** toan has quit IRC14:07
*** evgenyf has quit IRC14:07
*** [1]evgenyf is now known as evgenyf14:07
*** tqtran-afk has quit IRC14:08
*** banix_ has joined #openstack-meeting-314:08
*** toan has joined #openstack-meeting-314:08
*** banix has quit IRC14:09
*** banix_ is now known as banix14:09
*** rmoe has quit IRC14:10
*** rmoe has joined #openstack-meeting-314:10
*** absubram has joined #openstack-meeting-314:11
*** absubram_ has joined #openstack-meeting-314:12
*** yamamoto has joined #openstack-meeting-314:12
*** itoader has quit IRC14:13
*** pc_m has joined #openstack-meeting-314:13
*** tfukushima has joined #openstack-meeting-314:14
*** salv-orlando has joined #openstack-meeting-314:15
*** absubram has quit IRC14:15
*** absubram_ is now known as absubram14:15
*** tsufiev has joined #openstack-meeting-314:18
*** tsufiev has left #openstack-meeting-314:18
*** rbrndt has joined #openstack-meeting-314:20
*** rmoe has quit IRC14:20
*** rbrndt has left #openstack-meeting-314:20
*** galstrom is now known as galstrom_zzz14:23
*** rmoe has joined #openstack-meeting-314:24
*** mhoppal has quit IRC14:25
*** dslevin has left #openstack-meeting-314:26
*** sdake has quit IRC14:27
*** devkulkarni has quit IRC14:27
*** galstrom_zzz is now known as galstrom14:27
*** Swami has joined #openstack-meeting-314:29
*** rmoe has quit IRC14:29
*** vhoward has joined #openstack-meeting-314:29
*** zz_dimtruck is now known as dimtruck14:29
*** fawadkhaliq has quit IRC14:30
*** jschwarz_ has joined #openstack-meeting-314:30
*** fawadkhaliq has joined #openstack-meeting-314:30
*** rmoe has joined #openstack-meeting-314:31
*** baojg has joined #openstack-meeting-314:31
*** jschwarz has quit IRC14:32
*** sc68cal has joined #openstack-meeting-314:33
*** dedery has joined #openstack-meeting-314:33
*** sagar_nikam_ has quit IRC14:35
*** rmoe has quit IRC14:36
*** dedery has quit IRC14:36
*** atuvenie__ has quit IRC14:37
*** absubram has quit IRC14:40
*** vijendar has joined #openstack-meeting-314:42
*** absubram has joined #openstack-meeting-314:43
*** rmoe has joined #openstack-meeting-314:45
*** vijendar has left #openstack-meeting-314:46
*** devkulkarni has joined #openstack-meeting-314:51
*** rmoe has quit IRC14:51
*** rmoe has joined #openstack-meeting-314:51
*** cloudtrainme has joined #openstack-meeting-314:55
*** rhochmuth has joined #openstack-meeting-314:55
*** galstrom is now known as galstrom_zzz14:55
*** fabiog has joined #openstack-meeting-314:56
*** ho_away has joined #openstack-meeting-314:57
*** iyamahat has joined #openstack-meeting-314:57
*** rmoe has quit IRC14:58
*** rmoe has joined #openstack-meeting-314:58
*** rbrndt has joined #openstack-meeting-314:58
*** jpomeroy has quit IRC14:58
*** mhoppal has joined #openstack-meeting-314:59
*** witek has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Mar 16 15:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
witekhello15:00
bkleio/15:00
rbrndto/15:00
ho_awayo/15:00
*** mhoppal has quit IRC15:01
rhochmuthi'm sort of out this week on spring break, and haven't been checking up on things15:01
*** mhoppal has joined #openstack-meeting-315:01
shinya_kwbto/15:01
rhochmuthlooks like there are several agenda items at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthAgenda for Wednesday March 16, 2016 (15:00 UTC)15:01
rhochmuth1. Periodic metrics support15:01
rhochmuth1.https://review.openstack.org/29275315:01
rhochmuth2.https://review.openstack.org/29275815:01
rhochmuth2. monasca-log-api specifiction15:01
rhochmuth1.https://review.openstack.org/27305815:01
rhochmuth3. vertica/api reduction of inner joins patch15:01
rhochmuth  3.1 https://review.openstack.org/#/c/287507/15:02
*** galstrom_zzz is now known as galstrom15:02
*** numans has quit IRC15:02
*** numans has joined #openstack-meeting-315:02
rhochmuthSo, i'll go though the list15:02
rhochmuth#topic period metrics support15:02
*** openstack changes topic to "period metrics support (Meeting topic: monasca)"15:02
rhochmuthi'm assuming that is tomasz15:03
witekTomasz has started working on periodic metrics15:03
*** rmoe has quit IRC15:03
rhochmuthyes, i see15:03
rhochmuthlooks like ben is the only reviewer so far15:03
witekhe doesn't have much experience with monasca-thresh and storm15:03
fabioghi15:04
rhochmuthhi fabiog15:04
rhochmuthso, i think gettign some eyes on that15:04
witekif someone could take a look, we would be very thankfull15:04
rhochmuthi wont' review this week15:04
rhochmuthbut, i'll get back to it next week15:04
*** oheydorn has joined #openstack-meeting-315:04
witekrhochmuth: thanks15:04
rhochmuthalso our expert in this area craig is alos out htis week15:04
rhochmuthon spring break too15:05
*** bmotz has joined #openstack-meeting-315:05
rhochmuthbut when he returns next hopefully he can review too15:05
witekgreat15:05
rhochmuthunfortuanately, he is a slacker and doesn't show up to meetings when he is on break15:05
rhochmuth:-)15:05
witekhaha15:05
*** vgridnev has quit IRC15:05
*** arturb has joined #openstack-meeting-315:05
rhochmutheither that or he is smarter than me15:06
*** tgraichen has joined #openstack-meeting-315:06
bkleino comment15:06
*** yamamoto has quit IRC15:06
rhochmuthi guess it isn't a lot of code to make those changes15:07
rhochmuthso, the reviews should go prety quickly15:07
*** dhague_ has joined #openstack-meeting-315:07
rhochmuth#topic monasca-log-api specifiction15:07
*** openstack changes topic to "monasca-log-api specifiction (Meeting topic: monasca)"15:07
rhochmuthSo, it looks like we are trying to wrap-up on, https://review.openstack.org/#/c/273058/15:08
*** devkulkarni has left #openstack-meeting-315:08
fabiogI think is good to go15:08
rhochmuthlooks like there are several +1s and 2s, so agree15:08
fabiogrhochmuth: press the +1 workflow ;-)15:08
witek:)15:08
rhochmuthso, then i'm assuming tsv will wrap-up the implementation15:09
rhochmuthi think he was the last one in there15:09
rhochmuthhis review is in merge conflict right now, but if we fixes that up, then it should get merged soon15:10
rhochmuthas well as making sure the implementation is correct15:10
rhochmuthi'm going to let witold merge it15:11
witekyou mean implementation?15:11
rhochmuthactually, i meant the spec, but since you started the spec that wouldn't be best15:11
rhochmuthi can +2 it15:11
rhochmuthtsv still needs to wrap the implementation15:12
rhochmuthassiming he is going to do that15:12
witeki can merge the spec if we agree so here15:13
rhochmuthi agree15:13
rhochmuthone of these days i'll figure out how to do votes in irc15:13
*** mrmartin has quit IRC15:13
rhochmuth#topic vertica/api reduction of inner joins patch15:13
*** openstack changes topic to "vertica/api reduction of inner joins patch (Meeting topic: monasca)"15:13
bkleithat's me15:14
rhochmuthyes, i'm assuming you want to get this merged15:14
bkleii think it's ready -- anyone disagree?15:14
rhochmuthi haven't been able to test15:14
bkleiyep15:14
rhochmuthbut the code looks fine15:14
rhochmuthrbrandt might be able to help15:14
rhochmuthhe should be here15:14
rhochmuthrbrndt: u there?15:15
bkleisounds like he pulled in kaiyan to test15:15
*** david-lyle has quit IRC15:15
rbrndtI tested it a little myself and kayak ran the tempest tests against it15:15
*** david-lyle has joined #openstack-meeting-315:15
*** yamahata has joined #openstack-meeting-315:15
rbrndtI was hoping to go over it once more before approving15:15
bkleisure -- np15:15
bkleithx rbrndt15:15
rbrndtapologies to kaiyan whose name apparently auto corrects to kayak15:15
bklei:)15:16
rhochmuthlol15:16
rhochmuthok, then i'm assuming that will get merged relatively soon15:16
bkleisweet15:16
rhochmuth#topic https://review.openstack.org/#/c/287507/15:16
*** openstack changes topic to "https://review.openstack.org/#/c/287507/ (Meeting topic: monasca)"15:16
rhochmuthsorry thought that was a new topic the way the indenting worked out15:17
rhochmuth#topic 4. multiple metric and group_by15:18
*** openstack changes topic to "4. multiple metric and group_by (Meeting topic: monasca)"15:18
rhochmuthI started this review last wek https://review.openstack.org/#/c/289675/15:18
rhochmuthrbrndt is working on it now because i'mout15:18
*** jpomeroy has joined #openstack-meeting-315:18
rhochmuthbasically, we would like to add a group_by query parameter to the measurmeents and statistics resources15:18
rhochmuthinitially, we would like to only support "group_by=*", to group_by all unique dimensions15:19
rhochmuththis would impact the vertica and influxdb repos15:19
bkleiearly testing of it was good at TWC -- rbrndt ping me when more baked and i'll retest15:19
rhochmuththe goal is to return multiple metrics in a single query15:19
rhochmuthdid you look at performance15:20
bkleino -- just in my sandbox, that'd be tough until it merges and deploys15:20
bkleibut it's gonna scream by design :)15:20
rhochmuthso, is everyone ok with this change15:20
*** jobrs has joined #openstack-meeting-315:21
rhochmuthi don't think we submitted a blueprint to explicitly cover what this is about15:21
rhochmuthbut the review is in progress, although will probably be a couple of weeks until it is complete15:21
*** rmoe_ has joined #openstack-meeting-315:21
rhochmuthdoes anyone want to discuss further?15:21
rhochmuththe reasons/motiviation for the change, the syntax, ...15:22
*** mbound has quit IRC15:22
*** galstrom is now known as galstrom_zzz15:22
rhochmuthimplications, …15:22
witekI haven't take a look before, but please explain15:23
rhochmuthcurrently, when querying measurments or statistics, only one metric is returned15:23
rhochmuthyou can use the merge_metrics, to merge metrics, but in that case, it is still "one metric"15:24
rhochmuthwe are starting to see that this is becoming a performance bottleneck15:24
*** vgridnev has joined #openstack-meeting-315:25
rhochmuthfor example, at twc where they are displaying multiple vm metrics per tenant, let's say 10-20 VMs, and 10 separate graphs, that results in 100-220 separte queries of the API15:25
rhochmuthThere is also a use case that we are seeing in Ceilosca15:25
*** dedery has joined #openstack-meeting-315:25
*** sdake has joined #openstack-meeting-315:25
rhochmuththe group_by parameter will allow you to get multiple independent metrics back in a single query15:26
rhochmuthwe would like to support group_by=region, zone, hostname, ...15:26
rhochmuthwhere region, zone, hostname are dimension keys/names15:26
bkleionce ^^ merges, rbak will make some corresponding grafana2 changes to parse the multiple metrics returned15:27
rhochmuthin the short-term however, we would just like to support group_by=*15:27
fabiogrhochmuth: would the group_by allow several params in a single group or is only ine?15:27
rhochmuthwhere "*" is a wildacard for all dimensions15:27
rhochmuthin other words, return all the unique metrics15:27
shinya_kwbtthat's interesting15:27
rhochmuthit would allow several, fabiog15:28
rhochmuththat is the end-goal, anyway15:28
fabiogrhochmuth: ok15:28
rhochmuthso, the review is up and you can follow the progress of it15:28
rhochmuthand comment on it15:28
*** TomEros has joined #openstack-meeting-315:28
rhochmuthi'm expecting a very significant performance increase as a result15:29
rbakrhochmuth: Any idea what the timeline for supporting params other than * would be?15:29
rhochmuthrbrndt: u there still?15:29
*** christian_ has joined #openstack-meeting-315:29
fabiogrhochmuth: is only java, is still WIP or no plans to add Python?15:30
rhochmuthwe will add python too15:30
rbrndtI'm still here15:30
rhochmuthgoal is too support java/python influxdb and vertica15:30
rhochmuthall variations15:30
fabiogbtw, are we supporting Influx 0.10?15:30
rhochmuthrbrndt: now that you've looked at this for a couple of days, do you have a time-line15:30
rhochmuthfor the complete java/python vertica/influxdb implementation?15:31
rhochmuthno pressure15:31
rbrndtI've begun work on the pagination issues we discussed for vertica, so I expect that will be done or close to done today15:31
rbrndtI have some idea about the influx implementation, but I've yet to test them15:31
rhochmuthso, 2-3 weeks maybe15:32
rbrndtThe python should follow pretty easily once the java is done15:32
rbrndtI would say 2 would be sufficient to get a pretty good attempt done15:32
*** dedery has quit IRC15:32
rhochmuthso, it will be past the mitaka release date15:32
*** dedery has joined #openstack-meeting-315:32
*** fawadkhaliq has quit IRC15:33
rbrndtmostly likely15:33
rhochmuthanymore questions on that topic15:33
rhochmuthwitek: did that answer your questions?15:33
jobrswhat about cassandra support?15:33
witekyes, I have an idea :)15:33
*** numans has quit IRC15:34
rhochmuthjobrs:  let's talk about next, related to the influxdb discussion15:34
rhochmuththanks witek15:34
*** fawadkhaliq has joined #openstack-meeting-315:34
rhochmuthlet me know if you have any further questions, and please comment on review if any conerns15:34
*** david-lyle_ has joined #openstack-meeting-315:34
rhochmuth#topic infuxdb 0.10.X15:34
*** openstack changes topic to "infuxdb 0.10.X (Meeting topic: monasca)"15:34
jobrsyou were just mentioning influx and vertica above. influxdb will stop giving away versions with cluster support for free soon.15:34
*** david-lyle has quit IRC15:34
rhochmuthmhoppal, are you there15:35
mhoppalyes here15:35
rhochmuthjobrs: oh no15:35
rhochmuthso, we've been doing a lot of influxdb analyis again15:35
jobrsdefinitely15:35
rhochmuthmhoppal can give an update15:36
shinya_kwbtthat too bad ;-(15:36
mhoppalyes so we run some scale testing with influx 9.5 and the new version of 1015:36
mhoppallooking to see if there were any differences between the two15:36
mhoppalwe saw a significant improvements in 1015:37
mhoppalwe are still going through the testing but have scaled 10 up to around 9000 measurements per a second15:37
bkleiis that clustered -- or single node?15:37
mhoppalclustered15:37
jobrswhich storage engine?15:37
mhoppaltsm15:37
mhoppalfor 1015:37
rhochmuthtsm is default in 1015:37
*** vishwanathj_zzz is now known as vishwanathj15:38
mhoppalyes15:38
rhochmuthhow is stability?15:38
*** tfukushima has quit IRC15:38
mhoppalgreat15:38
*** fawadkhaliq has quit IRC15:38
rhochmuthhow is disk utilization?15:38
mhoppalabout 10x better then 9.515:38
rhochmuthso, disk utilization is 1/1015:39
mhoppalalso in 9.5 we run into issues geting past 5000 measurements per a second we were recieving timeouts from influxdb and 10 had no issues with that15:39
mhoppaland yes15:39
*** arturb has quit IRC15:39
rhochmuthso, summary, performance is looking good, hitting 9000 metrics/sec in test, but we haven't pushed harder yet15:40
rhochmuthstability is great15:40
mhoppalyes we are going to push it up further15:40
rhochmuthcompression is 10X better that 0.9.515:40
mhoppaland then start to do ha fail over testing15:40
mhoppalbut it is looking a lot better15:40
christian_did you test failure scenarios like split brain, remove one node and bring it back into the cluster?15:40
rhochmuthadditioanlly, compressions is 2X better than vertica15:40
mhoppaland the memory is a lot better as well15:40
mhoppalwe have not done much failure scenarios yet15:41
mhoppalin the plan for the next week15:41
*** alinbalutoiu__ has quit IRC15:41
*** jroll has quit IRC15:41
rhochmuthchristian_: we've done some initial ha testing, but more is planned15:41
*** jroll has joined #openstack-meeting-315:41
*** jroll has quit IRC15:41
*** jroll has joined #openstack-meeting-315:41
rhochmuthso far, we haven't seen any issues15:41
christian_thanks...please keep us up to date :-)15:41
rhochmuthso, based on that, we are rethinking our work on Cassandra15:42
rhochmuthjobrs: do you have a link on the clustering15:42
*** bpokorny has joined #openstack-meeting-315:42
bkleiyou mean moving up or pushing out work on cassandra?15:42
jobrshttps://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/15:43
bmotzI was just about to post that...15:43
jobrssry15:43
bmotzno problem! :)15:43
bmotzit was just to say that we are rethinking our plans around Influx15:43
bmotzsupport is priced around $500/server/month15:44
bmotzhttps://influxdata.com/pricing/#product-subscriptions15:44
jobrscassandra scaleability may be another pro (after looking at what netflix is doing with it)15:44
rhochmuththe reason why we started with cassandra is due to the problems with influxdb15:45
rhochmuthnow that influxdb is looking good, we have much less of a reason to do cassandra15:45
bmotzare there any blueprints or specs about the Cassandra thoughts?15:45
rhochmuthwe still haven't made the final decision thgouth15:46
rhochmuththere is a cassandra blueprint15:46
bkleidoes the fact that clustering won't be free with influxdb add another dimension to the cassandra support decision rhochmuth?15:46
rhochmuthyes it does15:46
jobrsthis is what they plan exactly: "Next week we’ll be cutting the first release candidate for the 0.11.0 release. While this release includes significant improvements in the query engine and the clustering code base, it will be the last open source version that includes clustering."15:46
rhochmuththat is really bad news15:47
jobrsbut two maintenance releases are released before at least (0.10.3 and 0.11)15:47
bmotzI've been pointed towards KairosDB, which is built on Cassandra, but I haven't had a chance to look yet15:48
rhochmuthi'll read the post more thoroughly after this meeting15:48
rhochmuthmaybe we should fork influxdb?15:48
rhochmuththanks mhoppal for the update15:49
mhoppalof course15:50
rhochmuth#topic Shinya's notification methods 15:50
*** openstack changes topic to "Shinya's notification methods  (Meeting topic: monasca)"15:50
shinya_kwbtthat's me15:50
rhochmuththanks for the review15:50
rhochmuthi just wanted to give you change to let folks know what you are working on15:50
bmotzthanks15:50
shinya_kwbtIm planning to change pagination style to Horizon style.15:51
shinya_kwbtThis needs sort parameter to api. So I added.15:51
rhochmuthand this applies to notification methods?15:52
shinya_kwbtIm writing selenium integration test.15:52
shinya_kwbtAlarm Defs and Alarms already have sort parameter.15:52
*** gema has joined #openstack-meeting-315:52
rhochmuththanks15:53
shinya_kwbtIt is difficult for me to write selenium test for current implementation of pagination.15:53
shinya_kwbtSo I planned to change pagination style.15:54
rhochmuththe paginiation style changes impact the monaca-ui15:54
rhochmuthcorrect?15:55
shinya_kwbtyes Horizon standard style.15:55
*** cjvolzka has joined #openstack-meeting-315:55
*** catherineD has joined #openstack-meeting-315:55
shinya_kwbtIt is able to change num of list.15:56
shinya_kwbtBy setting page.15:56
shinya_kwbtCurrent implementaion is hard corded 10.15:56
*** jschwarz_ has quit IRC15:57
*** evgenyf has quit IRC15:57
shinya_kwbtIf big screen you have, it is convinient.15:57
rhochmuthok, will checout out the review15:58
rhochmuthprobably need to wrap-up15:58
rhochmuthone other think, i'll be applying tags for the mitaka release in the next week or two15:58
rhochmuthtags need to be applied by March 31st,15:58
*** dedery has quit IRC15:59
rhochmuththis will be the first "official" monasca release in-sync with openstack15:59
rhochmuthso, we need to be careful about stability risky changes15:59
rhochmuthfor the next couple of weeks15:59
rhochmuthok, eveyrone meeting is done16:00
rhochmuthit always creeps up to fast16:00
rhochmuthbye16:00
bkleicya16:00
witekthanks Roland16:00
rbrndtbye16:00
witekbye16:00
ho_awaythanks & bye16:00
*** bklei has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Mar 16 16:00:40 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-03-16-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-16-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-16-15.00.log.html16:00
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Mar 16 16:00:47 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
*** ho_away has left #openstack-meeting-316:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
egluteo/16:00
hogepodgeo/16:00
catherineDo/16:00
gemao/16:01
tgraichenbye16:01
markvoelker#link https://etherpad.openstack.org/p/DefCoreRing.15 Today's agenda16:01
shinya_kwbtbye16:01
*** rbrndt has left #openstack-meeting-316:01
markvoelker#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
*** tgraichen has quit IRC16:01
*** e0ne has joined #openstack-meeting-316:01
markvoelkerPlease have a look at today's agenda and note any late additions16:01
*** klkumar has quit IRC16:01
*** luzC has joined #openstack-meeting-316:01
markvoelkerGlad to see you all made it in spite of the DST change here in the US. =)16:02
*** brunssen has joined #openstack-meeting-316:02
*** rhochmuth has quit IRC16:02
*** fabiog has quit IRC16:02
luzChello16:02
*** mhoppal has quit IRC16:02
*** mjturek1 has joined #openstack-meeting-316:02
egluteI like DST, i just dont like the switching!16:02
eglutehello luzC!16:02
markvoelker#topic Midcycle recap16:02
*** openstack changes topic to "Midcycle recap (Meeting topic: defcore)"16:02
brunssenHello everyone.16:02
*** witek has quit IRC16:03
markvoelker#link  https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle Etherpad from DefCore midcycle meetup16:03
*** dmellado has joined #openstack-meeting-316:03
*** bmotz has left #openstack-meeting-316:03
*** dwalleck has joined #openstack-meeting-316:03
markvoelkerThanks to everyone who came down to Texas, and special thanks to Vince and IBM for hosting us16:03
dwallecko/16:03
*** baojg has quit IRC16:03
markvoelkerIf you took action items from the sessions, they should hopefully be reflected in the Etherpad16:03
markvoelkerI know I have several. =)16:03
egluteshould we review who has what and decide on timelines?16:04
*** TomEros has quit IRC16:04
markvoelkereglute: We could, but that could take a while...it's a long list.  Maybe we should just ask first if anyone is unclear on their AI's or timelines?16:04
*** fawadkhaliq has joined #openstack-meeting-316:04
*** matrohon has quit IRC16:05
eglutethat sounds like a good idea16:05
brunssen@markvoelker, you are welcome16:05
brunssenIt was our pleasure to host.16:05
markvoelkerOn my end, I think the first thing I owe is a 2016.07 draft.  I should get that pushed up for review later tonight.16:05
markvoelkerThat should u16:05
eglutethanks markvoelker16:05
markvoelkernblock a few other things16:05
markvoelkerDoes anyone else need clarification on AI's or timing?16:06
*** jschwarz_ has joined #openstack-meeting-316:06
*** vgridnev has quit IRC16:06
*** mlavalle has joined #openstack-meeting-316:06
*** yamamoto has joined #openstack-meeting-316:07
eglutei am good for now16:07
markvoelkerOk, hearing nothing then...the next big thing for several folks is scoring, which is due soon.  And is the next topic on our agenda today, as luck would have it.16:07
markvoelker=)16:07
markvoelker#topic Scoring16:07
*** openstack changes topic to "Scoring (Meeting topic: defcore)"16:07
markvoelkerWe need to get scoring patches submitted ASAP.  Our deadline is only about a week and a half away now, so the sooner the better.16:08
markvoelker#info Scoring patches due March 2716:08
markvoelkerHopefully each of you have had a chance by now to reach out to PTL's and others to solicit input...if you need help on that front, please let us know!16:09
catherineDLet me know when it is time for me to discuss Heat scoring16:09
*** jobrs has quit IRC16:10
markvoelkerAny other scoring stuff before we get to Heat?16:10
markvoelkerOk then: catherineD, let's talk about Heat.  The floor is yours. =)16:11
catherineDThx markvoelker:16:11
catherineDSo I have discussed scoring with the Heat team16:11
*** belmoreira has quit IRC16:11
*** cloudtrainme has quit IRC16:12
catherineDbasically, they have not implemented tempest plugin interface for their in-tree test yet16:12
catherineDas a result of the discussion , a BP was created16:12
* markvoelker sees that as a positive16:13
catherineD#link Heat BP for tempest plugin https://blueprints.launchpad.net/heat/+spec/tempest-plugin-support .. target for Newton16:13
markvoelkerSo I guess the question is: if that isn't going to land until Newton, where does that leave us for this coming Guideline?16:13
catherineDquestion: does it make sense to request for scoring Heat now or should wait for the BP implemation?16:13
markvoelkerE.g., are there tests in Tempest today that are reasonable in the interim?16:13
eglutewe cant add those tests to defcore until the patch lands16:13
*** dwalleck has quit IRC16:14
catherineDmarkvoelker: They do not think what are in Tempest today is a good representative of Heat features16:14
catherineDI was planning to have a face-2-face working session with them at the Austin summit16:15
markvoelkercatherineD: Ok.  I personally haven't looked through the ones in Tempest lately so I'll trust their judgement.  Kinda disappointing not to have anything for this Guideline though.16:15
catherineDto at least get the in-tree test list and capabilities16:15
*** dwalleck has joined #openstack-meeting-316:15
dmelladocatherineD: besides this exact case for Heat, how're you dealing with the test split in tempest? I mean that when it comes from the tempest plugins in other repos and moved tests16:16
catherineDwe do have the capabilities in https://review.openstack.org/#/c/216983/16:16
dmellado?16:16
*** yamamoto has quit IRC16:16
*** dslevin has joined #openstack-meeting-316:17
catherineDdmellado: if the in-tree tests are implemented with tempest plugin... testr list test will give a complete test list including the test in tempest and those with plugin16:17
*** dslevin has quit IRC16:17
catherineDso from testing we should be OK16:17
dmelladocatherineD: I know, but my question is about the projects who lacks tempest plugin16:18
*** dslevin has joined #openstack-meeting-316:18
dmelladoand tests have been already moved16:18
dmelladoi.e. neutron api tests16:18
*** dslevin has quit IRC16:18
*** Swami has quit IRC16:19
catherineDI belieev DefCore's stand is DefCore test must be able to initiate test byTtempest.  Right? markvoelker: eglute:16:19
hogepodgedmellado: moved? into or out of tempest?16:19
dmelladohogepodge: some neutron tempest tests were moved out of tempest to the neutron repo16:19
eglutecatherineD is correct. dmellado are you talking about current defcore tests that were already moved?16:19
markvoelkercatherineD: yes.  Mechanically that's the easiest way to pick those up today.16:19
eglutedmellado can you provide examples? this is news to us16:20
dmelladoeglute: not current in defcore, but for the future16:20
dmelladosorry if I was alarming ;)16:20
*** dslevin has joined #openstack-meeting-316:20
*** david-lyle_ is now known as david-lyle16:20
*** paul-carlton1 has quit IRC16:20
eglutedmellado ah in that case it is ok!16:20
dmelladoI'm currently working, or trying to, in the neutron tempest plugin16:21
dmelladoand thus was interested ;)16:21
egluteare you planning on moving current defcore tests into the plugin?16:21
*** dslevin has quit IRC16:21
*** cloudtrainme has joined #openstack-meeting-316:21
*** dwalleck has quit IRC16:21
egluteor all of the neutron tests into the plugin?16:21
*** toddjohn has quit IRC16:21
dmelladoeglute: neutron moved quite some tests to their own repo16:21
*** dslevin has joined #openstack-meeting-316:22
dmelladobasically I need the plugin to run them from tempest16:22
eglutedo you already have a working plugin? if not, how far away are you?16:22
dmelladoi.e. https://github.com/openstack/neutron/blob/master/neutron/tests/api/test_networks.py16:22
*** dslevin has quit IRC16:22
dmelladoI'm working on it and probably not too far, but most probably won't be landing in mitaka16:23
dmellado(just too many things xD)16:23
catherineDdmellado: I think the project needs to be aware that if the tests are targeted as DefCore plugin then they needed to be able to run from Tempest16:23
*** dslevin has joined #openstack-meeting-316:23
catherineDDefCore plugin --> DefCore tests :-)16:24
dmelladoI'm not sure about defcore, pretty new to it16:24
hogepodgeqa has indicated that they would like defcore tests to stick around in tempest where possible16:24
dmelladoso sorry if I ask too many maybe known things16:24
catherineDhogepodge: thx16:24
*** dslevin has quit IRC16:24
dmelladoat any case as of today they run just fine, just was thinking about the next movements16:24
dmelladothanks hogepodge for pointing that out16:25
eglutedmellado you are at the right place! and we definitely want to know about this as early as possible16:25
catherineDmarkvoelker: eglute: hogepodge: back to Heat scoring ...16:25
*** dedery has joined #openstack-meeting-316:25
hogepodgeplugin is a compromise, but if those tests could move back (I know), that's a course to consider16:25
catherineDdo we still want to work with the test they have in Tempest today or wait?16:25
eglutewe do need to consider the plugin route though16:25
markvoelkercatherineD: I think that I'd need to look into what's in Tempest for Heat today before I can really have an opinion.16:26
*** dslevin has joined #openstack-meeting-316:26
eglutecatherineD i think if they suggest not using the tempest tests, we should not use them.16:26
markvoelkercatherineD: That said, if the Heat folks feel those are so insufficient that they'd rather have nothing for this Guideline...16:26
*** vtech has quit IRC16:27
*** vtech has joined #openstack-meeting-316:27
*** dslevin has quit IRC16:27
catherineDmarkvoelker: seems like so .. because without the plugin ... we can not run the tests ..16:28
markvoelkercatherineD: In your conversations with the Heat folks, did they understand that without a plugin we have to use the in-Tempest tests or nothing this time around?16:28
*** dslevin has joined #openstack-meeting-316:28
catherineDmarkvoelker: they do so they would like to implement the plugin in Newton16:29
catherineDby defining BP and owner16:29
markvoelkerOk.  So they're ok with not having anything in the next Guideline then?16:29
*** dslevin has quit IRC16:29
*** fwdit has quit IRC16:30
catherineDmarkvoelker: Let me double check with them on the fact that whether they are OK witj not having anything in the next Guideline16:30
eglutethanks catherineD16:30
markvoelkerOk.  If they're willing to wait another six months I have no real problem with that.  It's fine to continue working on identifying candidate capabilities, but obviously no pressure on the March 27 date.16:31
*** dslevin has joined #openstack-meeting-316:31
markvoelkerAny work you do now will simply help ensure adequate test coverage exists and make scoring easier down the line. =)16:31
catherineDmarkvoelker: +116:32
*** dslevin has quit IRC16:32
markvoelkerOk, anything else on scoring before we move on?16:32
*** fawadkhaliq has quit IRC16:32
*** dslevin has joined #openstack-meeting-316:33
markvoelkerok, moving on then16:33
*** dedery has quit IRC16:33
markvoelker#topic RefStack16:33
*** openstack changes topic to "RefStack (Meeting topic: defcore)"16:33
* markvoelker turns the floor back over to catherineD16:33
*** fawadkhaliq has joined #openstack-meeting-316:33
*** fawadkhaliq has quit IRC16:33
catherineDopenstack: Thx16:33
*** dslevin has quit IRC16:34
catherineDfor     https://review.openstack.org/#/c/290689/16:34
catherineDit was updated with patch#2 to add the tests instead of renaming ...16:34
catherineDbut I think we need to think of the long term solution because the test lists are dynamic16:35
eglutecatherineD what do you propose?16:35
*** dslevin has joined #openstack-meeting-316:35
catherineDOut plan is to provide a REST API in RefStack to let user download the test list16:35
catherineDThe REST API would reconstruct the list everytime the user requests16:36
*** dslevin has quit IRC16:36
catherineDso it is a live test list with many options that the user can choose (list only required, or with alias , or advisory ...)16:36
catherineDwe will also provide a link at the RefStack server UI16:37
dmelladowould that also affect the tempest tag that the refstack client will be downloading?16:37
*** Swami has joined #openstack-meeting-316:37
catherineDdmellado: the test list is constructed from the guideline JSON files16:38
catherineDand not from testr test list of tempest16:38
*** toddjohn has joined #openstack-meeting-316:38
dmelladocatherineD: I see, thanks for the clarification16:38
*** dedery has joined #openstack-meeting-316:38
catherineDbut the guideline files do change overtime due to flagged tests etc ...16:39
catherineDso it is dynamic16:39
hogepodgethis only gets more difficult once out of tree tests are admitted16:39
dmelladoso how does the guideline JSON files get built? from the scoring that mentioned before?16:40
markvoelkerdmellado: yep.  I'll dig up an example patch review for you to peruse if you like16:40
dmelladothat'd be great markvoelker, thanks!16:40
*** anilvenkata has quit IRC16:41
luzCplease count me in for the example as well please16:41
catherineDbut for the immediate issue, https://review.openstack.org/#/c/290689/ should be merged16:42
markvoelkerdmellado: luzC: here's the patch that added networking capabilities...I'll use it as an example since I wrote it and since it got a lot of discussion =) https://review.openstack.org/#/c/210080/16:42
*** matrohon has joined #openstack-meeting-316:42
markvoelkercatherineD: makes sense16:42
*** kzaitsev_mb has quit IRC16:42
dmelladothanks markvoelker ;)16:42
markvoelkercatherineD: anything further?16:43
*** jschwarz_ has quit IRC16:43
catherineDnot for this topic ...16:44
catherineDcould we discuss the next RefStack topic16:44
*** jlanoux has quit IRC16:44
markvoelkercatherineD: absolutely, go for it16:44
catherineDI am really sorry that this is the third times we discuss the "List RefStack Users" topic16:45
*** spzala has joined #openstack-meeting-316:45
catherineD#link http://lists.openstack.org/pipermail/defcore-committee/2016-March/001066.html16:45
*** cloudtrainme has quit IRC16:46
catherineDduring the RefStack meeting , it was suggested that I send the email16:46
egluteI think ONLY foundation members should be able to list users in refstack16:46
*** e0ne has quit IRC16:47
*** e0ne_ has joined #openstack-meeting-316:47
markvoelkerOk, so we've been over this a few times but I think we're getting new info as we unravel the ball of yarn a bit so it's fine to bring it back up.16:47
hogepodgeI'm torn on this issue16:48
markvoelkerOne thing that it might be useful to clarify: it feels like part of the resistance here is that not allowing normal users to list user data is that doing so creates extra work/complexity for you guys. =)  And that's a valid concern.  Is that true?16:48
hogepodgeOn one hand we're open and all this information is available anyway. On the other, I don't want to give someone a simple API to generate a spam list.16:48
*** vgridnev has joined #openstack-meeting-316:49
catherineDmarkvoelker: I think we need to look at the principal ... how we implement should not affect the principal16:49
*** e0ne has joined #openstack-meeting-316:50
*** dedery has quit IRC16:50
*** fawadkhaliq has joined #openstack-meeting-316:50
*** e0ne_ has quit IRC16:50
catherineDhogepodge: We get the user infor for openstackid  which own by Foundation16:50
gemacatherineD: +116:50
*** fawadkhaliq has quit IRC16:51
*** fawadkhaliq has joined #openstack-meeting-316:51
*** vgridnev has quit IRC16:52
markvoelkercatherineD: I don't disagree, but what I'm sort of meandering toward is kind of what hogepodge is getting at: if it's really burdensome to do it this way and 90% of that info is available already anyway...maybe I could be convinced the costs outweigh the benefits.  But if it's not a ton of extra work, I'd prefer we stick to the original intent, which is to disclose the least info necessary to do the job.16:52
hogepodgemarkvoelker: +116:53
markvoelkercatherineD: That's why I'm curious how much work this adds up to.16:53
eglutemarkvoelker +116:53
gemaless than the amount of time we've spent discussing this, for sure16:53
gemaspecially for catherineD  :)16:53
*** e0ne has quit IRC16:53
catherineDmarkvoelker: how much work is depending on individual opinion,s16:53
catherineDgema: haha16:54
*** oheydorn has quit IRC16:54
*** nkrinner has quit IRC16:54
markvoelkercatherineD: I think probably the RefStack team is best situated to figure out a reasonable level of effort estimate...unfortunately we're probably not.16:54
markvoelkerSo what I'd suggest...16:54
catherineDMy concern is once the data is exposed we can not get it back ... I hate to see RefStack being the one who does that ...16:54
*** FallenPegasus has joined #openstack-meeting-316:55
markvoelkerIs that we once again re-iterate our assertion that our preference is to disclose the least amount of information necessary to perform the required tasks.  That's our guiding recommendation.16:55
egluteUnless there is a really good reason to list ALL registered users for any logged in user, Refstack should not be displaying it16:55
*** kzaitsev_mb has joined #openstack-meeting-316:55
*** spzala has quit IRC16:55
markvoelkerIf RefStack decides to go a different route because the effort is too much...I'm probably ok with that call.16:55
markvoelkerWe can give the guidance, but the implementation is ultimately up to those who are writing the code, really.16:56
*** spzala has joined #openstack-meeting-316:56
markvoelkerDoes that sound reasonable to folks?16:56
*** mriedem has joined #openstack-meeting-316:56
catherineDeglute: markvoelker: hogepodge: gema: I would appreciate if you all can response to the email http://lists.openstack.org/pipermail/defcore-committee/2016-March/001066.html16:56
eglutewill do, sorry haven't yet!16:57
markvoelkercatherineD: can do.16:57
gemacatherineD: will do16:57
catherineDeglute: no problem at all ....16:57
*** spzala has quit IRC16:57
*** alaski has joined #openstack-meeting-316:57
catherineDthank you all... I hope this would be the last time I bring this issue here :-)16:57
*** vgridnev has joined #openstack-meeting-316:58
dmelladoit's an interesting topic, though16:58
dmelladoif we assume this is all 'open', then yeah16:58
dmelladoanyway, I'll try to find some time to reply ;)16:58
catherineDdmellado: thank you!16:58
eglutecatherineD, please do bring things up as they come up16:58
catherineDeglute: thank you16:59
markvoelker#action all please respond to http://lists.openstack.org/pipermail/defcore-committee/2016-March/001066.html16:59
markvoelkerAnything further?  We're about out of time16:59
catherineDnope from me17:00
markvoelkerOk then, thanks folks!17:00
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Mar 16 17:00:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-16-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-16-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-16-16.00.log.html17:00
*** brunssen has quit IRC17:00
*** pc_m has left #openstack-meeting-317:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Mar 16 17:00:32 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** cjvolzka has left #openstack-meeting-317:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
mriedemo/!17:00
doffmo/17:00
alaskibauzas: ping17:00
melwitto/17:00
*** e0ne has joined #openstack-meeting-317:00
mriedembauzas is at a bday party for the mrs17:00
*** FallenPegasus is now known as MarkAtwood17:00
alaskiahh, okay17:01
mriedemor so he says17:01
alaski#topic Cells testing17:01
*** openstack changes topic to "Cells testing (Meeting topic: nova_cells)"17:01
*** piet has joined #openstack-meeting-317:01
*** banix has quit IRC17:01
*** dedery has joined #openstack-meeting-317:01
alaskieverything seems quiet17:01
melwittagreed17:01
*** vtech has quit IRC17:01
alaskitraditionally this topic has been about v1 testing but I'd like to expand it to include v2 testing as well, beyond unit tests I mean17:01
alaskimelwitt: excellent17:02
*** banix has joined #openstack-meeting-317:02
alaskimainly I'd like to start thinking about grenade and upgrade testing in this portion of the meeting17:02
*** sigmavirus24 is now known as sigmavirus24_awa17:02
alaskisince melwitts nova-manage command merged in M we can use that for grenade testing once the branches switch17:03
*** mlavalle has left #openstack-meeting-317:03
*** spzala has joined #openstack-meeting-317:03
alaskibut until that happens there's not much we can do17:03
alaskibut if anyone has ideas on what/how to test bring them forward17:04
mriedemwell,17:04
mriedemnvm17:04
doffmAt some point we will need a multi cell test, but we arn't there yet.17:04
alaskidoffm: agreed17:04
mriedemi'm not sure how the nova-manage command fits into grenade really17:05
mriedemi.e. do you populate some stuff in mitaka and then run the command in newton?17:05
alaskiI did not do a good job updating the agenda so we'll skip the next planned topic "Open reviews"17:05
alaskimriedem: yes17:05
mriedemalaski: then we didn't really need the command to land in mitaka right?17:05
alaskibut I believe grenade only has access to it if it lands in current-117:05
alaskigrenade only updates computes I think17:06
mriedemso you run the command in mitaka side of grenade too?17:06
mriedemthere are different ways to grenade, there is the all upgrade, and the partial upgrade17:06
alaskino, the command just runs on N17:06
mriedempartial upgrades everything but n-cpu17:06
mriedemgate-grenade-dsvm is full upgrade of everything17:06
*** ddieterly is now known as ddieterly[away]17:06
mriedemwhat used to be the n-cpu job was upgrade all but n-cpu, that's now the multinode grenade job17:07
alaskiokay, my details are off then. but I know I've hit the issue in the past where grenade couldn't run a nova-manage thing from the current branch17:07
*** spzala has quit IRC17:07
alaskimaybe it's fixed17:07
*** lpetrut has quit IRC17:07
alaskioh, maybe it's that devstack runs the same for both? and errors if the command isn't in current-117:08
mriedemyes,17:09
mriedemwell,17:09
mriedemit'll be devstack n-1 for old, then devstack n17:09
mriedemso if you need to run a thing in n-1, it has to exist17:09
mriedem:)17:09
alaskiheh. either way the thing merged so we're good :)17:10
mriedemright, plus it doesn't sound like you need the cli there anyway17:10
mriedemwere there any data migrations that needed testing?17:10
mriedem*any other17:11
doffmWe might need to add cell0 commands that didn't make it. But... as mriedem described we should be ok running them just on 'n'17:11
alaskiright. though we could test mapping cells then upgrading, though it's not realistic as noone should be mapping cells yet17:11
*** primeministerp has quit IRC17:11
alaskimriedem: just the cell0 one from doffm17:11
mriedemi'd think at some point we use the multinode job where cell0 is one node and the other is not17:12
mriedembut,17:12
mriedemthen do we require a 3 node job/17:12
mriedem?17:12
mriedemlike for live migration17:12
mriedemcell0 but 2 nodes for actually migrating things17:12
alaskiyou could coexist the api with a cell17:12
*** aspiers has quit IRC17:12
mriedeminfra is going to looove that17:12
mriedembut still,17:12
mriedem2 compute cells, right?17:12
mriedem+cell017:12
doffmYep.17:12
mriedemso 3 nodes17:13
mriedem3 hosts i should say17:13
alaskito do it right, yeah17:13
doffmProbably best theat way.17:13
mriedemi'll let alaski break that to sdague17:13
mriedemcan you run cell0 on one of those?17:13
doffmYes.17:13
alaskiheh, good things there's plenty of beer in Austin17:13
mriedemok17:13
alaskicell0 is just a db17:13
mriedemtrue, so yeah, nvm17:13
mriedemi always think of cell0 as another service17:14
*** kzaitsev_mb has quit IRC17:14
doffmIts not really. Its a paper tiger of a cell.17:14
*** mjturek1 has left #openstack-meeting-317:14
mriedemsay that to cell0's face17:14
alaskidoffm: where were you when we were naming this thing? :)17:15
doffm:)17:15
mriedemagain,17:15
mriedemwhy not jailcell?17:15
alaskithat would have worked, I don't remember it being proposed17:15
alaskigraveyard was the other contender I recall17:15
mriedemgeez17:15
mriedemvoid17:15
mriedemnull17:16
doffmThats macarbre.17:16
melwittthe only other migration we added recently was flavor table. the active migration part isn't there yet17:16
alaskimriedem: null was ruled out for being overloaded17:16
alaskidoffm: that's why we didn't go with it17:16
alaskimelwitt: yeah, we need to push on sdagues flavor API thing first17:16
mriedemand jaypipes threw a wrench in the mix for that spec17:17
alaskithis segues nicely into the next topic17:17
alaski#topic Open Discussion17:17
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:17
alaskimriedem: what now?17:17
mriedemhttps://review.openstack.org/#/c/265282/17:17
mriedemjay went all resource provider on it's ass17:17
*** aspiers has joined #openstack-meeting-317:17
doffmHa. Thats a pretty big wrench.17:18
*** ddieterly[away] is now known as ddieterly17:18
doffm"all of this is useless! bwahaha"17:18
alaskihmm, I agree with him on that17:18
alaskiI think it's just a representation issue though, so may not be too bad17:19
jaypipessorry.17:19
mriedemso,17:19
*** mickeys has joined #openstack-meeting-317:19
mriedemif representing the flavor depends on the capabilities stuff17:19
doffmjaypipes: You arn't neccessarily wrong, but it predicates the flavor migration on an api change.17:19
*** dedery has quit IRC17:19
mriedemand the cells flavor migration depends on the flavor spec,17:19
mriedemi don't think we can block like that right now17:20
jaypipesdoffm: I don't understand what you mean by that.17:20
alaskimriedem: ignoring the capabilities stuff, I think we can move forward on what he suggested17:20
alaskiand then microversion in the capabilities later. I need to look closer at it17:21
mriedemwell,17:22
mriedemwe're probably going to need a design session o nthis17:22
doffmjaypipes: A microversion change. The server representation is changing just to list resources and removing flavor.17:22
alaskimriedem: +117:22
*** piet has quit IRC17:22
jaypipesdoffm: oh, yes, no disagreement.17:23
alaskifor now let's all go loudly agree/disagree with jaypipes on the spec17:23
*** madhu_ak has joined #openstack-meeting-317:23
mriedemi punted :)17:24
mriedemlike a true politician17:24
alaskior that17:24
jaypipesalaski: sorry to throw the wrench in the mix :(17:24
mriedem"let's wait until after the midterms"17:24
mriedemalaski: you had a series of changes that was looking good but hit FF17:24
mriedemi don't think those had blockers, just ran out of time17:24
mriedemwe could queue those up early for newton, would have to re-propose the spec/blueprint17:24
alaskijaypipes: it's cool. I think we might need to partway follow what you suggested or we'll be blocked for a cycle.17:25
mriedemthe build request stuff i think17:25
alaskiright17:25
alaskiI will tidy all of that back up as soon as N opens17:25
jaypipesalaski: I will have the capabilities proposal written up by the summit.17:25
jaypipeswhich reminds me, I should probably book a flight and find a cheap hotel in austin..17:26
alaskime too...17:26
doffmGood luck with cheap.17:26
mriedemi thought mirantis all stayed at the same fancy place?17:26
jaypipesalaski: well, *you* get yours paid for so you don't need to worry about the hotel ;)17:26
*** cloudtrainme has joined #openstack-meeting-317:26
melwittI'm planning to write a spec for the message queue switching and get my patch ready for review for N17:26
jaypipesmriedem: I'm paying my own way in order to get an additional engineer to the summit.17:27
alaskijaypipes: ahh, didn't realize you were going dutch17:27
jaypipesya17:27
doffmmelwitt: Sounds good. I guess I was wondering if you were going to get the spec up for that.17:27
mriedemjules doesn't count as an engineer right? :)17:27
jaypipesmriedem: no, she isn't goin.17:27
alaskimelwitt: great.17:27
melwittdoffm: yeah, my bad on that. I had meant to do it earlier than now17:28
doffmI have 3 specs up for DB api migration. I'm still working on a 4th and FINAL one.17:28
*** lpetrut has joined #openstack-meeting-317:28
doffmhttps://review.openstack.org/#/c/291382/17:28
alaskiso let me ask a question of the room on specs, how would you all like to be notified of new ones going up?17:28
alaskiadvertise in this meeting, add each other to reviews, ...?17:29
*** jwarendt has joined #openstack-meeting-317:29
doffmI was thinking of putting them in the 'work to be done' document.17:29
doffmhttps://etherpad.openstack.org/p/cellsV2-remaining-work-items17:29
doffmBut another etherpad / in here would be fine by me.17:29
melwittI was thinking maybe the priorities etherpad in the cells section?17:29
mriedemas long as it's clear on the order somewhere, i'm happy17:29
doffmmelwitt: That makes sense.17:30
xgermano/17:30
alaskicool, let's use the priority etherpad then17:30
*** e0ne has quit IRC17:30
alaskipotential future PTL mriedem, any idea when a new one of those might go up?17:30
*** Aish has joined #openstack-meeting-317:30
mriedemalaski: i'll talk to john, i don't see why we couldn't start creating one now17:30
alaskicool17:31
*** vtech has joined #openstack-meeting-317:31
*** idan_hefetz_ has joined #openstack-meeting-317:31
alaskiI guess technically we don't decide priorities until Summit, but...17:31
melwittI feel like I want to add the https://etherpad.openstack.org/p/cellsV2-remaining-work-items to the cells section too. I didn't know about it until now17:31
mriedemalaski: i think cellsv2 is a given17:31
alaskimelwitt: +1, I mean I knew but forgot17:31
mriedemmelwitt: +117:31
*** idan_hefetz has quit IRC17:31
melwittdone17:32
alaskidoffm: do you feel like db migrations are going to fill the cycle for you?17:33
doffmThey would If I did all of them. I'm hoping to get some help around here.17:33
doffmBut yes, they ar at least one full person.17:33
alaskimelwitt: do you feel that message queue switching is all you might get to this cycle?17:34
alaskidoffm: okay17:34
melwittalaski: no, I've got bandwidth for more work actually17:34
alaskiI'd like to get a sense of if plates are full or we need to think ahead to what else could be done17:34
alaskimelwitt: awesome17:34
*** SumitNaiksatam has quit IRC17:35
alaskiI haven't heard from belmeiora or vineet recently to know if CERN will have much involvement this cycle17:35
melwittdoffm: did you get anywhere with the oslo.messaging "assemble transport url from ConfigOpts" by chance?17:36
*** idan_hefetz has joined #openstack-meeting-317:36
doffmmelwitt: I haven't started. If you want to try then... go ahead. Otherwise I will try and get around to it soon.17:36
melwittdoffm: no, was just curious17:36
doffmImplementation wise i'm working on this spec. https://review.openstack.org/#/c/288084/17:37
*** armax has quit IRC17:37
*** idan_hefetz_ has quit IRC17:37
doffmIts the aggregate db move. I want to get it done early beacuse the resource provider cells work will depend on it.17:37
alaskinice17:37
mriedemfyi https://etherpad.openstack.org/p/newton-nova-priorities-tracking17:38
dansmiththe flavor move is still a thing we need right?17:38
alaskiyes17:38
mriedemdansmith: yeah17:38
mriedembut it's held up17:38
dansmithon?17:38
mriedemhttps://review.openstack.org/#/c/265282/17:38
melwittjaypipes17:38
melwitt:)17:38
mriedemtechnically sdague,17:38
mriedemwho is held up on jaypipes17:38
mriedemit's a turducken17:38
dansmithI don't understand jaypipes' thing there17:39
*** johnthetubaguy_ has joined #openstack-meeting-317:39
melwitthaha nice17:39
dansmithwe have flavors codified in instances already17:39
dansmithand we have that link already17:39
madhu_akdo we have fwaas meeting?17:40
alaskidansmith: my read is that his goal is to remove all of that, and this is a first step towards that rather than codifying it further17:40
alaskimadhu_ak: there's another meeting here atm17:40
*** idan_hefetz has quit IRC17:40
dansmithalaski: I'm not sure who the he is in that statement exactly17:40
*** atuvenie has quit IRC17:40
alaskijaypipes17:40
dansmithalaski: maybe we can appease jay by changing the resource name to "resources" or something17:40
madhu_aksorry alaski didnt account for daylight saving..17:41
alaskimadhu_ak: no worries17:41
alaskidansmith: maybe. I do think it's really just a representation issue, shouldn't be too hard to workaround17:41
*** johnthetubaguy has quit IRC17:41
*** johnthetubaguy_ is now known as johnthetubaguy17:41
alaskiI just don't want to block on waiting for capabilities to be expressable17:41
dansmithyeah17:42
dansmithI'll look over that spec and the comments in a bit17:42
*** lpetrut has quit IRC17:43
alaskifor divvying up work how about we all link our specs, or mention specs we want to propose, in https://etherpad.openstack.org/p/newton-nova-priorities-tracking and then get together on what we have the bandwidth for as a group17:43
melwittokay17:44
doffmalaski: Good idea.17:44
*** vishwanathj is now known as vishwanathj_chow17:45
alaskicool17:45
*** sdague has quit IRC17:46
*** dhague_ has quit IRC17:46
alaskiI know bauzas is interested in rethinking the meeting times. I am going to take a look at what's available and look at alternates to the current times17:46
alaskiand we can vote on changing it or now17:46
alaski*not17:46
* jaypipes leading a meeting :(17:47
*** SridarK has joined #openstack-meeting-317:47
*** ddieterly is now known as ddieterly[away]17:47
alaskijaypipes: no worries17:47
alaskialong those lines, do you all want to meet next week or wait two weeks again?17:47
*** s3wong has joined #openstack-meeting-317:48
doffmWill anyone be reviewing specs by next week?17:48
melwitteither way works for me17:48
*** fawadkhaliq has quit IRC17:49
mriedemi'm fine either way17:49
alaskidoffm: usually there aren't many reviews until RC2 is out17:49
doffmCould probably leave it then. I don't mind.17:49
alaskibut reviews might start to trickle soon17:49
alaskicool. let's skip again then17:49
alaski#info Skip next weeks cells meeting17:50
alaskiany other topics for today?17:50
*** fawadkhaliq has joined #openstack-meeting-317:50
doffmNot here.17:50
*** primeministerp has joined #openstack-meeting-317:51
alaskigreat17:51
alaskiuntil next time17:51
alaski#endmeeting17:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:51
*** mriedem has left #openstack-meeting-317:51
openstackMeeting ended Wed Mar 16 17:51:23 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:51
alaskithanks all17:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-16-17.00.html17:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-16-17.00.txt17:51
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-16-17.00.log.html17:51
*** sdague has joined #openstack-meeting-317:52
*** salv-orl_ has joined #openstack-meeting-317:54
*** rossella_s has joined #openstack-meeting-317:54
*** safchain has quit IRC17:55
*** salv-orlando has quit IRC17:56
*** toddjohn has quit IRC17:57
*** alexpilotti has quit IRC17:58
*** toddjohn has joined #openstack-meeting-317:58
*** idan_hefetz has joined #openstack-meeting-318:01
*** baoli has quit IRC18:04
*** spzala has joined #openstack-meeting-318:04
*** ihrachys has quit IRC18:04
*** tqtran-afk has joined #openstack-meeting-318:05
*** lpetrut has joined #openstack-meeting-318:05
*** SumitNaiksatam has joined #openstack-meeting-318:06
*** sigmavirus24_awa is now known as sigmavirus2418:07
*** tqtran-afk has quit IRC18:10
*** kzaitsev_mb has joined #openstack-meeting-318:10
*** ddieterly[away] is now known as ddieterly18:21
*** tqtran-afk has joined #openstack-meeting-318:22
*** mrmartin has joined #openstack-meeting-318:22
*** anilvenkata has joined #openstack-meeting-318:26
*** annp has joined #openstack-meeting-318:27
sc68calhi all18:31
jwarendthi18:31
sc68cal#startmeeting networking_fwaas18:32
openstackMeeting started Wed Mar 16 18:32:08 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:32
annphi sc68cal, all18:32
sc68cal#chair SridarK18:32
openstackCurrent chairs: SridarK sc68cal18:32
sc68cal#chair xgerman18:32
openstackCurrent chairs: SridarK sc68cal xgerman18:32
SridarKHi All18:32
sc68calToday I think is mostly just working on the actual release of mitaka18:33
SridarKsc68cal: i think there is nothing pending w.r.t the release18:34
sc68calagreed18:34
sc68calso I think once the release happens, hopefully capacity will open back up and development can resume on the v2 api18:36
SridarKsc68cal: yes hope so too18:36
SridarKi guess the branch should open up for Newton real soon ?18:37
*** ivar-lazzaro has joined #openstack-meeting-318:39
sc68calI would assume so. I think part of the problem is that none of the cores have done a release, it's always been handled for us, by either mestery or ihar18:39
*** ivar-lazzaro has quit IRC18:39
SridarKok18:40
sc68calIt appears we have a stable/mitaka branch cut18:40
*** vgridnev has quit IRC18:40
*** vgridnev has joined #openstack-meeting-318:41
sc68calso, I assume that we're open for newton based on that fact18:41
SridarKok cool18:41
SridarKIn terms of the N release,  we should get #link https://review.openstack.org/#/c/278863/ for observer hierarchy18:41
SridarKthe submitter it seems also got sucked into other things18:42
SridarKbut will be good to close it out early as a long standing thing18:42
*** MarkAtwood has quit IRC18:43
sc68calyes, that patch is very important. SridarK or jwarendt - do you think you guys could push revisions if the submitter does not reappear?18:43
*** ddieterly is now known as ddieterly[away]18:43
SridarKsc68cal: yes will do so18:43
*** ivar-lazzaro has joined #openstack-meeting-318:44
jwarendtYes18:44
xgermano/18:45
*** rossella_s has quit IRC18:45
SridarKjwarendt: i think u have been looking at the neutron (L3Agent) side of things18:45
*** mrmartin has quit IRC18:46
*** neelashah has quit IRC18:46
jwarendtCorrect, but the agent.py on neutron side has direct calls right now into FWaaS class - instead of decoupled observer.  I have made the lookup dynamic, but observer would be much better.18:47
SridarKjwarendt: yes agreed18:48
SridarKi will reach out the submitter again to check on his availability and we can move forward accordingly18:48
SridarK*reach out to the ..18:48
*** ddieterly[away] is now known as ddieterly18:48
jwarendtPlus for some reason there is a router_add but no router_delete on L3 agent side; hoping observer will properly listen to delete so fwaas can change state appropriately.18:49
*** baoli has joined #openstack-meeting-318:49
*** vtech has quit IRC18:49
*** fawadkhaliq has quit IRC18:49
SridarKjwarendt: yes the router delete - earlier there was not much to do as the iptables will get cleaned out18:49
*** vgridnev has quit IRC18:50
xgermanwell, we still need to remove it from the DB18:50
SridarKjwarendt: now with router insertion things are a bit different - but yes that is a clean up18:50
SridarKxgerman: yes i believe we have Foreign Key constraint18:51
SridarKbut let me look at that code again18:51
xgermanok, that would work18:51
SridarKfrom the agent side of the world18:51
*** vtech has joined #openstack-meeting-318:51
SridarKOkay good i think we are all on the same page18:52
*** sambetts is now known as sambetts|afk18:52
*** mrmartin has joined #openstack-meeting-318:53
*** vgridnev has joined #openstack-meeting-318:53
jwarendtAn update blocks if router in use, but can delete the router underneath the FWaaS without the FWaaS changing from ACTIVE state - even if the DB cleans up.18:53
jwarendtObservers will help straighten that out.18:54
SridarKjwarendt: yes agreed18:54
xgerman+118:54
*** amit2131 has quit IRC18:55
*** amit213 has joined #openstack-meeting-318:55
sc68calcool18:56
SridarKone other patch i wanted to discuss: #link https://review.openstack.org/#/c/291822/18:56
sc68calThe other thing I wanted to bring up, is the state of 3rd party drivers18:56
SridarKsc68cal: u read my mind :-)18:56
sc68cal:)18:56
sc68calNow - macafee's driver, they actually have a CI job that passes reliably18:56
sc68calbut the code itself needs a maintainer - to fix pylint issues18:57
SridarKsc68cal: on this, i reached out to intel - there is some churn in ownership of McAfee - so things are in a bit of flux18:57
SridarKI asked if they could take care of the pylint issues - which was one of ur main concerns18:57
sc68calyep18:58
*** ivar-lazzaro has quit IRC18:58
SridarKhopefully they can help with transtioning this to the new maintainers18:58
sc68calIf they fix the issues, then that would be a positive step18:58
sc68calbut what do we do about drivers like varmor and cisco?18:59
SridarKwe can consider giving some time until they sort out the maintainers - i will stay in touch with intel folks to help transition18:59
sc68caldoes the cisco driver have a 3rd party CI?18:59
SridarKsc68cal: yes but i will be first to admit - the reliability is a bit suspect18:59
sc68calI haven't seen it report on a recent patch.18:59
sc68calor any, really.18:59
SridarKsc68cal: i think we can start having vendors pull out to their own rep19:00
SridarK*repo19:00
*** tyr_ has joined #openstack-meeting-319:00
jwarendt+119:00
sc68calyeah, that would be good. The main thing is that we're supposed to vouch for the quality of these drivers, that are in tree - and to be honest the only one we can vouch for is the l3reference, since that gets tested at the openstack gate19:01
SridarKsc68cal: yes earlier - we had some control on the ownership of the CI - now its in another part of Cisco19:01
SridarKsc68cal: +119:01
*** vishwanathj_chow is now known as vishwanathj19:01
*** TravT has joined #openstack-meeting-319:01
SridarKand most vendors do have their networking-vendor repos19:01
*** neelashah has joined #openstack-meeting-319:01
*** Swami has quit IRC19:02
*** claudiub has quit IRC19:03
*** Swami has joined #openstack-meeting-319:03
*** anilvenkata has quit IRC19:03
SridarKWould it be reasonable to ask if vendors can move their drivers out by N-2 ?19:04
sc68calthat sounds good to me19:04
*** TravT has left #openstack-meeting-319:04
xgerman+119:05
SridarKok i will ping the vendor contacts as the first step19:06
xgermanthough in LBaaS we decided to leave them in19:07
xgermansome vendors see it important to be part of the repo...19:07
SridarKxgerman: hmm ok19:07
xgermanwe should ping them anyway and if they resist we can revisit19:07
SridarKi am not religious on this, i thought in neutron in general the direction with vendor decomp - we want to ease vendors out19:07
SridarKxgerman: yes sounds good to me19:08
sc68calI'm not religious either, but the pylint thing just highlighted a driver that needs an owner19:08
xgermanagreed.19:09
*** vgridnev has quit IRC19:11
SridarKok those were some things i wanted to discuss - did not have anything else - i can think of right now.19:11
*** vgridnev has joined #openstack-meeting-319:11
sc68calthat's all from me too. Anyone else?19:12
*** alaski has left #openstack-meeting-319:12
xgermanwell, we should mention that PTL proposals are open.. so if anyone wants to run...19:12
*** toddjohn has quit IRC19:12
xgermanfor the PTL of Neutron...19:12
sc68calI wish anyone who wants to, all the best19:13
* sc68cal leans back in his lazy boy chair and sips his drink19:13
SridarK+119:13
*** salv-orl_ has quit IRC19:15
sc68calunless there is anything else, I think we can close this out and give everyone 15 back19:15
xgerman+119:16
SridarK+119:16
sc68cal#endmeeting19:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:16
openstackMeeting ended Wed Mar 16 19:16:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-16-18.32.html19:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-16-18.32.txt19:16
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-16-18.32.log.html19:16
SridarKThx and Bye all19:16
annpbye all19:16
*** vgridnev has quit IRC19:17
*** mrmartin has quit IRC19:20
*** vgridnev has joined #openstack-meeting-319:21
*** ryansb has joined #openstack-meeting-319:21
*** ryansb has quit IRC19:21
*** ryansb has joined #openstack-meeting-319:21
*** ryansb has left #openstack-meeting-319:22
*** mrmartin has joined #openstack-meeting-319:22
*** anilvenkata has joined #openstack-meeting-319:24
*** irenab_ has joined #openstack-meeting-319:26
*** kro_sniffles is now known as kro_mnckn_doc19:27
*** irenab has quit IRC19:28
*** irenab_ is now known as irenab19:28
*** piet has joined #openstack-meeting-319:28
*** vgridnev has quit IRC19:28
*** eliqiao has quit IRC19:29
*** eliqiao has joined #openstack-meeting-319:29
*** yamahata has quit IRC19:34
*** iyamahat has quit IRC19:34
*** vgridnev has joined #openstack-meeting-319:37
*** cloudtrainme has quit IRC19:41
*** annp has quit IRC19:43
*** MarkAtwood has joined #openstack-meeting-319:44
*** e0ne has joined #openstack-meeting-319:46
*** ryansb has joined #openstack-meeting-319:49
*** ryansb has quit IRC19:49
*** ryansb has joined #openstack-meeting-319:49
*** toddjohn has joined #openstack-meeting-319:49
*** kzaitsev_mb has quit IRC19:50
*** pt_15 has joined #openstack-meeting-319:53
*** galstrom_zzz is now known as galstrom19:54
*** toddjohn has quit IRC19:54
*** ig0r_ has quit IRC19:55
*** rockyg has joined #openstack-meeting-319:56
*** rockyg has quit IRC19:57
*** rockyg has joined #openstack-meeting-319:57
*** TravT has joined #openstack-meeting-320:00
*** salv-orlando has joined #openstack-meeting-320:01
*** cloudtrainme has joined #openstack-meeting-320:02
*** claudiub has joined #openstack-meeting-320:03
*** claudiub|2 has joined #openstack-meeting-320:05
*** robcresswell has joined #openstack-meeting-320:08
*** robcresswell has left #openstack-meeting-320:08
*** claudiub has quit IRC20:08
*** r1chardj0n3s has joined #openstack-meeting-320:10
*** r1chardj0n3s has left #openstack-meeting-320:10
*** bpokorny_ has joined #openstack-meeting-320:12
*** bpokorny has quit IRC20:13
*** gema has left #openstack-meeting-320:13
*** cloudtrainme has quit IRC20:14
*** toddjohn has joined #openstack-meeting-320:15
*** bpokorny_ has quit IRC20:15
*** bpokorny has joined #openstack-meeting-320:15
*** ivar-lazzaro has joined #openstack-meeting-320:16
*** kzaitsev_mb has joined #openstack-meeting-320:16
*** cloudtrainme has joined #openstack-meeting-320:16
*** neiljerram has quit IRC20:20
*** bpokorny has quit IRC20:20
*** rtheis has quit IRC20:20
*** bpokorny has joined #openstack-meeting-320:20
*** spzala has quit IRC20:25
*** hurgleburgler has joined #openstack-meeting-320:27
*** toddjohn has quit IRC20:28
*** toddjohn has joined #openstack-meeting-320:29
*** baoli has quit IRC20:32
*** toddjohn has quit IRC20:34
*** mickeys has quit IRC20:37
*** MarkAtwood has quit IRC20:37
*** andymaier has quit IRC20:41
*** lpetrut has quit IRC20:44
*** banix has quit IRC20:45
*** dtardivel has quit IRC20:48
*** e0ne has quit IRC20:58
*** safchain has joined #openstack-meeting-320:59
*** annegentle has joined #openstack-meeting-320:59
*** woodster_ has joined #openstack-meeting-321:00
*** ddieterly is now known as ddieterly[away]21:01
*** bpokorny has quit IRC21:03
*** bpokorny has joined #openstack-meeting-321:03
*** ddieterly[away] is now known as ddieterly21:05
*** lblanchard has quit IRC21:08
*** primeministerp has quit IRC21:09
*** annegent_ has joined #openstack-meeting-321:10
*** annegentle has quit IRC21:11
*** doug-fish has quit IRC21:11
*** DericHorn-HP has joined #openstack-meeting-321:12
*** DericHorn-HP has quit IRC21:12
*** doug-fish has joined #openstack-meeting-321:12
*** iyamahat has joined #openstack-meeting-321:13
*** ddieterly is now known as ddieterly[away]21:17
*** kro_mnckn_doc has quit IRC21:19
*** anteaya has quit IRC21:19
*** annegent_ has quit IRC21:23
*** kebray has joined #openstack-meeting-321:24
*** darrenc is now known as darren_afk21:31
*** lkoranda has quit IRC21:32
*** kebray has quit IRC21:32
*** e0ne has joined #openstack-meeting-321:37
*** lkoranda has joined #openstack-meeting-321:38
*** e0ne has quit IRC21:40
*** annegentle has joined #openstack-meeting-321:43
*** neelashah has quit IRC21:44
*** matrohon has quit IRC21:45
*** darren_afk is now known as darrenc21:46
*** ddieterly[away] is now known as ddieterly21:47
*** iyamahat has quit IRC21:48
*** sigmavirus24 is now known as sigmavirus24_awa21:48
*** annegentle has quit IRC21:48
*** absubram has quit IRC21:49
*** absubram has joined #openstack-meeting-321:50
*** piet has quit IRC21:50
*** mickeys has joined #openstack-meeting-321:53
*** rockyg has quit IRC21:53
*** primeministerp has joined #openstack-meeting-321:53
*** alex_xu has quit IRC21:56
*** vhoward has quit IRC21:58
*** alex_xu has joined #openstack-meeting-321:58
*** sambetts|afk has quit IRC21:59
*** mrmartin has quit IRC21:59
*** sambetts has joined #openstack-meeting-322:02
*** annegentle has joined #openstack-meeting-322:03
*** alex_xu has quit IRC22:06
*** mickeyspiegel has joined #openstack-meeting-322:06
*** piet has joined #openstack-meeting-322:07
*** mickeys has quit IRC22:09
*** jpomeroy has quit IRC22:09
*** alex_xu has joined #openstack-meeting-322:09
*** MarkAtwood has joined #openstack-meeting-322:12
*** MarkAtwood has quit IRC22:13
*** vgridnev has quit IRC22:13
*** SergeyLukjanov2 has joined #openstack-meeting-322:15
*** SergeyLukjanov has quit IRC22:16
*** SergeyLukjanov2 is now known as SergeyLukjanov22:16
*** dims_ has joined #openstack-meeting-322:16
*** Aish has quit IRC22:16
*** idan_hefetz has quit IRC22:16
*** dims has quit IRC22:18
*** anilvenkata has quit IRC22:19
*** yamahata has joined #openstack-meeting-322:21
*** annegentle has quit IRC22:26
*** galstrom is now known as galstrom_zzz22:29
*** toddjohn has joined #openstack-meeting-322:30
*** Aish has joined #openstack-meeting-322:31
*** ddieterly has quit IRC22:31
*** toddjohn has quit IRC22:35
*** safchain has quit IRC22:36
*** doug-fis_ has joined #openstack-meeting-322:47
*** yamahata has quit IRC22:48
*** ryansb has quit IRC22:49
*** doug-fish has quit IRC22:50
*** doug-fis_ has quit IRC22:51
*** ryansb has joined #openstack-meeting-322:52
*** ryansb has quit IRC22:52
*** ryansb has joined #openstack-meeting-322:52
*** rbak has quit IRC22:54
*** yamahata has joined #openstack-meeting-322:57
*** Aish has quit IRC22:58
*** tyr_ has quit IRC23:03
*** vishwanathj has quit IRC23:06
*** primeministerp has quit IRC23:10
*** krotscheck has joined #openstack-meeting-323:11
*** sdague has quit IRC23:14
*** karlamrhein has joined #openstack-meeting-323:14
*** annegentle has joined #openstack-meeting-323:14
*** dimtruck is now known as zz_dimtruck23:15
*** qwebirc47761 has joined #openstack-meeting-323:15
*** qwebirc47761 has quit IRC23:17
*** yamahata has quit IRC23:18
*** piet has quit IRC23:18
*** fawadkhaliq has joined #openstack-meeting-323:19
*** annegentle has quit IRC23:19
*** bryan_att has joined #openstack-meeting-323:19
*** qwebirc50458 has joined #openstack-meeting-323:19
*** qwebirc50458 has quit IRC23:19
*** anteaya has joined #openstack-meeting-323:21
*** karlamrhein has quit IRC23:25
*** toddjohn has joined #openstack-meeting-323:30
*** toddjohn has quit IRC23:35
*** cloudtrainme has quit IRC23:35
*** SumitNaiksatam has quit IRC23:35
*** toddjohn has joined #openstack-meeting-323:35
*** toddjohn has quit IRC23:40
*** Aish has joined #openstack-meeting-323:41
*** doug-fish has joined #openstack-meeting-323:43
*** annegentle has joined #openstack-meeting-323:45
*** annegentle has quit IRC23:52
*** piet has joined #openstack-meeting-323:53
*** salv-orl_ has joined #openstack-meeting-323:54
*** pt_15 has quit IRC23:55
*** salv-orlando has quit IRC23:57

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