Wednesday, 2016-02-24

*** piet has joined #openstack-meeting-300:01
*** FallenPegasus has quit IRC00:02
*** sdake has quit IRC00:04
*** darrenc_afk is now known as darrenc00:05
*** yamamoto_ has joined #openstack-meeting-300:05
*** _sarob has joined #openstack-meeting-300:07
*** _sarob has quit IRC00:11
*** yamamoto_ has quit IRC00:14
*** markvoelker has quit IRC00:15
*** Sukhdev has quit IRC00:16
*** Sukhdev has joined #openstack-meeting-300:17
*** Sukhdev has quit IRC00:18
*** tej has quit IRC00:22
*** kzaitsev_mb has quit IRC00:23
*** vhoward has joined #openstack-meeting-300:31
*** markvoelker has joined #openstack-meeting-300:46
*** lblanchard has joined #openstack-meeting-300:49
*** bpokorny_ has joined #openstack-meeting-300:51
*** bpokorny_ has quit IRC00:51
*** Aish has quit IRC00:53
*** bpokorny has quit IRC00:54
*** hoangcx has joined #openstack-meeting-300:58
*** bmoss has joined #openstack-meeting-301:01
*** bmoss has left #openstack-meeting-301:07
*** dtardivel has quit IRC01:08
*** Sukhdev has joined #openstack-meeting-301:14
*** yamamoto_ has joined #openstack-meeting-301:14
*** baohua has joined #openstack-meeting-301:14
*** shwetaap has joined #openstack-meeting-301:15
*** shwetaap has quit IRC01:19
*** yamamoto_ has quit IRC01:19
*** yamamoto_ has joined #openstack-meeting-301:20
*** kzaitsev_mb has joined #openstack-meeting-301:20
*** stanzgy has joined #openstack-meeting-301:20
*** vhoward has quit IRC01:21
*** armax has joined #openstack-meeting-301:21
*** kzaitsev_mb has quit IRC01:26
*** shwetaap has joined #openstack-meeting-301:27
*** sgordon has quit IRC01:36
*** sgordon has joined #openstack-meeting-301:37
*** sdake has joined #openstack-meeting-301:51
*** piet has quit IRC01:53
*** sdake_ has joined #openstack-meeting-301:55
*** sdake has quit IRC01:56
*** baoli has joined #openstack-meeting-301:58
*** iyamahat has quit IRC01:58
*** Sukhdev has quit IRC01:59
*** dims has quit IRC01:59
*** yamamoto_ has quit IRC02:00
*** yamahata has quit IRC02:00
*** Sukhdev has joined #openstack-meeting-302:01
*** Sukhdev has quit IRC02:01
*** vishwanathj has quit IRC02:06
*** zhurong has joined #openstack-meeting-302:06
*** pcaruana has quit IRC02:07
*** sdake_ has quit IRC02:10
*** pcaruana has joined #openstack-meeting-302:19
*** sdake has joined #openstack-meeting-302:20
*** lblanchard has quit IRC02:21
*** kzaitsev_mb has joined #openstack-meeting-302:22
*** vishwanathj has joined #openstack-meeting-302:26
*** kzaitsev_mb has quit IRC02:27
*** vishwana_ has joined #openstack-meeting-302:28
*** vishwanathj has quit IRC02:31
*** ivar-lazzaro has quit IRC02:32
*** tfukushima has joined #openstack-meeting-302:33
*** sdake has quit IRC02:43
*** zz_dimtruck is now known as dimtruck02:47
*** yamamoto_ has joined #openstack-meeting-302:47
*** Aish has joined #openstack-meeting-302:51
*** Aish has left #openstack-meeting-302:51
*** shwetaap has quit IRC02:54
*** s3wong has quit IRC03:00
*** pcaruana has quit IRC03:01
*** hoangcx has quit IRC03:06
*** baohua has quit IRC03:12
*** sdake has joined #openstack-meeting-303:13
*** dims has joined #openstack-meeting-303:13
*** baohua has joined #openstack-meeting-303:13
*** baohua_ has joined #openstack-meeting-303:15
*** pcaruana has joined #openstack-meeting-303:16
*** sdake_ has joined #openstack-meeting-303:16
*** baohua_ has quit IRC03:16
*** baohua has quit IRC03:17
*** baohua has joined #openstack-meeting-303:17
*** sdake has quit IRC03:18
*** iyamahat has joined #openstack-meeting-303:23
*** kzaitsev_mb has joined #openstack-meeting-303:23
*** salv-orlando has joined #openstack-meeting-303:26
*** tfukushima has quit IRC03:27
*** tfukushima has joined #openstack-meeting-303:28
*** salv-orlando has quit IRC03:28
*** kzaitsev_mb has quit IRC03:28
*** salv-orl_ has quit IRC03:29
*** tfukushima has quit IRC03:39
*** hoangcx has joined #openstack-meeting-303:41
*** shwetaap has joined #openstack-meeting-303:47
*** watanabe_isao has quit IRC03:53
*** iyamahat has quit IRC03:54
*** baoli has quit IRC03:55
*** irenab has quit IRC03:59
*** irenab has joined #openstack-meeting-304:00
*** pcaruana has quit IRC04:01
*** sdake_ has quit IRC04:01
*** baoli has joined #openstack-meeting-304:03
*** neelashah has joined #openstack-meeting-304:04
*** pcaruana has joined #openstack-meeting-304:15
*** baohua has quit IRC04:21
*** baohua_ has joined #openstack-meeting-304:21
*** baohua_ has quit IRC04:22
*** baohua has joined #openstack-meeting-304:23
*** baoli has quit IRC04:28
*** baoli has joined #openstack-meeting-304:29
*** dimtruck is now known as zz_dimtruck04:35
*** hoangcx has quit IRC04:35
*** spzala has joined #openstack-meeting-304:37
*** baoli has quit IRC04:39
*** piet has joined #openstack-meeting-304:52
*** neelashah has quit IRC04:55
*** sdake has joined #openstack-meeting-304:59
*** Poornima has joined #openstack-meeting-305:00
*** amotoki has joined #openstack-meeting-305:05
*** spzala has quit IRC05:09
*** sdake has quit IRC05:14
*** kzaitsev_mb has joined #openstack-meeting-305:24
*** iyamahat has joined #openstack-meeting-305:25
*** hoangcx has joined #openstack-meeting-305:26
*** kzaitsev_mb has quit IRC05:29
*** salv-orlando has joined #openstack-meeting-305:36
*** pcaruana has quit IRC05:38
*** chhavi has joined #openstack-meeting-305:40
*** dims has quit IRC05:48
*** salv-orlando has quit IRC05:49
*** pcaruana has joined #openstack-meeting-305:53
*** piet has quit IRC06:00
*** galstrom_zzz is now known as galstrom06:05
*** irenab_ has joined #openstack-meeting-306:14
*** baohua has quit IRC06:15
*** baohua has joined #openstack-meeting-306:15
*** fawadkhaliq has joined #openstack-meeting-306:15
*** nkrinner has joined #openstack-meeting-306:16
*** irenab has quit IRC06:17
*** irenab_ is now known as irenab06:17
*** numans has joined #openstack-meeting-306:19
*** openstack has joined #openstack-meeting-313:22
*** ChanServ sets mode: +o openstack13:22
claudiubnot really sure, isn't there supposed to be a proxy for this?13:22
sagar_nikamwe can do it by running freerdp-webconnect on controller, but linux version of FreeRDP does not seem to be stable, as well as there are no RPMs or DEBs for it13:23
sagar_nikammay be we can discuss this in a meeting when alexpilotti: is available13:24
lpetrutone possible scenario would be to have another proxy, outside the Hyper-V node, which mediates the access to the FreeRDP web connect service, although I'm not sure this is the recommended workflow13:25
sagar_nikamwe can discuss it on HyperV channel sometime this week when alexpilotti: is available instead of waiting for next week's IRC meeing13:25
*** vgridnev has joined #openstack-meeting-313:25
sagar_nikamlpetrut: we can do it by running it on another windows node and use NLB to configure HA13:25
sagar_nikambut from what i remember in our discussion on this topic in a previous meeting13:26
sagar_nikamthe recommended approach is to run FreeRDP on HyperV host13:26
sagar_nikamrunning nova-compute13:26
sagar_nikamclaudiub: lpetrut: when is alexpilotti: available13:27
sagar_nikamcan we discuss on HyperV channel when he is back ?13:27
lpetrutsure13:27
sagar_nikamlpetrut: can you let us know when we can have the meeting after discussing with alexpiltti:13:28
*** dslevin has joined #openstack-meeting-313:29
lpetrutsure13:29
*** dslevin has quit IRC13:29
claudiubsagar_nikam: don't know when he will be available, but he should be back for the next meeting. anyways, moving on.13:30
claudiubSince M-3 will be next week, after that, we will start running thousands of tests, making sure that there are no regressions for 2012, 2012 r2 and 2016.13:31
*** dslevin has joined #openstack-meeting-313:31
claudiubAfter a few final patches merge in os-win, networking-hyperv and compute-hyperv.13:31
claudiubincluding the hyper-v cluster driver.13:31
*** dslevin has quit IRC13:31
claudiubthat's pretty much it from me. Anyone else has anything else to discuss?13:32
sagar_nikamlpetrut:FC patches merged in compute-hyperv ?13:33
*** dslevin has joined #openstack-meeting-313:33
lpetrutnot yet, I was hoping to get the os-brick patch in, but as that got postponed to N, I guess I'll have to take that code to compute-hyperv13:33
sagar_nikamok13:34
*** AndChat|94569 has joined #openstack-meeting-313:34
lpetrutI'll do the same for the iSCSI MPIO related code13:34
sagar_nikamsonu: anything to discuss from your end ? OVS related ?13:34
sagar_nikamwe have time to discuss it13:34
sonunothing as of today13:35
*** AndChat|94569 has quit IRC13:35
sagar_nikamok13:35
sonuClaudiu I am reviewing the cluster driver spec13:35
sonuI will include comments on the spec as appropriate.13:36
lpetruthave you guys got to test the FC patches?13:36
*** atuvenie_ has joined #openstack-meeting-313:36
sagar_nikamclaidiub: since we have time, would you like to let us know any new BPs planned for N13:36
claudiubsonu: Sure, it was previously approved, so I don't think any changes to it would be necessary. It would just delay its reapproval. :)13:37
sagar_nikamlpetrut: the team to test FC patches identified, they are creating the setup13:37
lpetrutsagar_nikam: that's great13:37
*** sankarshan is now known as sankarshan_away13:37
sagar_nikamhow about discussing any new BPs planned13:38
sonuI will post the questions and comments to you then.13:38
sagar_nikamespecially to take new features of WIN 201613:38
claudiubsagar_nikam: As for new blueprints for N, from my side, I have quite a few. Probably the biggest one I'm currently working on is the instance live-resize feature. Basically, using nova live-resize <instance> <new-flavor> will resize the given instance while it is still running - no shutdown / restart necessary.13:38
sagar_nikamok13:39
claudiubwhich means that the vm can continue its work uninterrupted.13:39
claudiubcan be live-resized: memory, vcpus, disk. Maybe even hot-plug pci devices using live-resize (still being debated).13:40
*** dims has joined #openstack-meeting-313:40
*** itxaka is now known as itxaka|afk13:40
claudiubwe will also have the shielded vms for windows server 2016.13:40
sonudo you have any blueprint for consuming OVS 2.613:41
sonuincluding - evolving OVS firewall for hyper-v.13:41
claudiubthen there's the host capabilities spec - each compute node will be able to report its own hypervisor / host capabilities, then certain host / hypervisor capabilities will a lot easier to request and properly schedule.13:42
*** atuvenie__ has joined #openstack-meeting-313:42
*** rtheis has quit IRC13:43
claudiubsonu: it hasn't been discussed yet, we should see what changes would actually be necessary for it to work on hyper-v13:43
sonudo you think my team here can take that part of the work?13:43
claudiubsonu: it might not need a blueprint, if the changes are trivial, a bug report should suffice, IMO.13:43
*** rtheis has joined #openstack-meeting-313:43
sonuSure! let it evolve13:44
*** amotoki has joined #openstack-meeting-313:44
claudiubsonu: no objections from my part, plus, it's on the neutron side. :)13:44
*** vhoward has joined #openstack-meeting-313:44
sonuclaudiub: thanks13:45
*** atuvenie has quit IRC13:45
claudiubas far as other features, I'm open to suggestions. :)13:46
*** vgridnev has quit IRC13:47
*** vgridnev has joined #openstack-meeting-313:47
*** sonu has quit IRC13:47
*** rtheis has quit IRC13:48
claudiubIf there are no more topics to be disccussed, we can end this meeting at :50. :)13:49
*** kmb has quit IRC13:49
sagar_nikamsure, no topics from my end, let us discuss FreeRDP at the earliest13:50
*** shwetaap2 has quit IRC13:50
claudiubok, thanks for joining!13:50
claudiub#endmeeting13:51
*** rtheis has joined #openstack-meeting-313:51
*** abalutoiu has quit IRC13:52
*** kvinod has quit IRC13:52
*** itoader has quit IRC13:53
*** rtheis has quit IRC13:53
*** rtheis has joined #openstack-meeting-313:53
*** atuvenie_ has quit IRC13:53
*** mrmartin has quit IRC13:55
*** rtheis has quit IRC13:57
*** rtheis has joined #openstack-meeting-313:57
*** shwetaap has joined #openstack-meeting-313:58
*** atuvenie__ has quit IRC13:58
*** rtheis has quit IRC13:58
*** sagar_nikam has quit IRC13:58
*** rtheis has joined #openstack-meeting-313:59
jschwarzsomehow I have mondays and not wednesdays14:01
*** salv-orlando has joined #openstack-meeting-314:01
ihrachysoy14:01
njohnstono/14:02
ajo:)14:02
irenabhi14:02
ajostill not started14:02
ajolet's give 1 minute or so14:02
ajoand I'm looking for a link in the meanwhile14:02
*** shwetaap has quit IRC14:02
jschwarzso every 2 weeks on wednesdays?14:02
ajoyeah14:02
jschwarzokies14:02
ihrachysjschwarz: just use .ical file from eavesdrop14:02
ihrachysand don't trust anything else14:03
ihrachyseven me14:03
ihrachys:)14:03
*** davidsha has joined #openstack-meeting-314:03
*** shwetaap has joined #openstack-meeting-314:03
ajo:D14:03
ajook, so I guess we can start14:03
*** omer_etrog has joined #openstack-meeting-314:03
jschwarzihrachys, ah yes, the eavesdrop mentions the right time and I misread14:03
ajo#startmeeting neutron_qos14:03
openstackMeeting started Wed Feb 24 14:03:42 2016 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:03
ajoHi everybody! ;)14:03
ihrachyso/14:03
jschwarz\o/14:03
irenabhi14:04
davidshahi!14:04
ajo#link http://eavesdrop.openstack.org/#Neutron_QoS_Meeting14:04
njohnstono/14:04
*** piet has joined #openstack-meeting-314:04
ajoo/ :)14:04
ajoI wanted to start raising the topic of our roadmap14:04
ajoon last drivers meetings there were concerns about our roadmap, status, and the amount of RFEs they were finding14:05
*** dimtruck is now known as zz_dimtruck14:05
ajo#link http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-02-18-22.01.log.html#l-5214:05
irenabajo: so qos features have high request14:05
ajoSo I thought we may clarify that14:05
ajo#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087360.html14:05
ajoI sent this email to the mailing list14:06
*** neelashah has joined #openstack-meeting-314:06
ihrachysirenab: yeah, but it's not like you post an RFE and it magically happen14:06
ajoand, to be right, armax was partly right, because I haven't been doing a good review of new RFEs, because I was focused on the mitaka bits14:06
ihrachyswe should consider available resources, current roadmap...14:06
irenabihrachys: the intent should be approved so the one who proposes can move on14:07
ajoand I guess, they felt overwhelmed by RFEs they didn't understand how exactly fit in the architecture we designed14:07
armaxajo: I am always 100% right!14:07
armax:)14:07
armaxajo: jokes aside, I saw your email…but I haven’t had the chance to reply yet…I’ll do that today14:07
ajoarmax++14:07
ajolol14:07
ihrachysirenab: you can't effectively move forward without having reviewers on board14:07
*** omer_etrog has quit IRC14:07
ihrachysthat's why we have approvers for blueprints14:07
irenabihrachys: so intent and review commitmentm right?14:08
ihrachys(we don't have them for RFEs and I believe that's a bug)14:08
ajoarmax: I wanted to discuss the current status on the meeting, and then send a detailed report, I'm sorry I haven't been communicating to you properly, and actively reviewing new RFEs, consider that changed from now on14:08
ihrachysarmax: btw do we plan to have approvers for RFEs?14:08
*** salv-orlando has quit IRC14:08
armaxihrachys: something to consider/experiment next cycle. We’ll do a postmortem once mitaka is out of the way14:08
njohnstonSo I think we take the list of all QoS features that could be implemented - BW limiting, DSCP, ECN, 802.1p/q, and minimum bandwidth guarantees - and the possible implementations for each - OVS, LB, SR-IOV - and we can provide a matrix of all the QoS items between us and full implementation.  Some of them will be empty spots - DSCP on SR-IOV is an impossibility - but at least we can say "this is the comp14:09
njohnstonlete roadmap", and show which 1-3 items we're targeting this cycle and next cycle14:09
ajoyes,14:09
ajoI have brought up this:14:09
ajo#link https://etherpad.openstack.org/p/qos-roadmap14:09
ajoto discuss during the meeting14:09
ihrachysthe matrix idea seems like a good idea14:09
ajoAnd I was thinking of the same14:09
ajoone important thing, is that we don't need to fill RFEs for specific ref-arch implementations14:10
ajoprobably a bug is enough14:10
ihrachys+14:10
ajoonly if the implementation is a huge change to the specific implementation, then that could be a matter of an spec/rfe/devref14:10
ajoto have a better understanding of how is it going to be implemented14:11
njohnstonThat sounds fair to me.14:11
*** ifat_afek has joined #openstack-meeting-314:11
ajoSo, in the tiny etherpad,14:11
ajoI have detailed r current status14:11
ajothe documentation we have,14:11
ajoand what we're doing for mitaka14:12
ajobasically, we don't have a *lot* of things in mitaka, because, doing things right, we need to cover a lot of related dependencis14:12
ihrachysirenab: my understanding is that posting an RFE without having anyone to implement and approve the code is a waste of drivers time14:12
ajoyeah14:12
* jschwarz thinks that aside from listing features, etc, you guys may want to assign them to people (so drivers will feel comfortable and will know who to ask when things go south)14:12
ajoI agree too14:12
ajowe can discuss new ideas in the meeting14:12
ihrachysjschwarz: and that's where approvers for RFE should come to help14:13
ajobut I'd say, let's only fill RFEs if we have people willing, and with the ability to implement14:13
irenabajo: ihrachys : sounds reasonable14:13
ajoWe still won't have control over the RFEs people fill, but I will monitor that14:14
ajoon a weekly basis14:14
ajo#action ajo sets a calendar reminder for himself before driver's meeting to check any new QoS related RFE14:14
*** julim has joined #openstack-meeting-314:15
irenabInitially I thought that RFE was for users to express requirements14:15
*** piet has quit IRC14:15
*** sdake has joined #openstack-meeting-314:15
ajoyes, in fact I understand that's the thing14:15
*** piet has joined #openstack-meeting-314:16
ajobut if we can globally do some filtering ourselves here, we're as developers proposing features, so we can discuss it in advance14:16
*** shwetaap has quit IRC14:16
*** primeministerp has quit IRC14:16
ajoto have a more filtered RFE14:16
irenab+114:16
ajoor higher quality RFE, know that we have backers to write the code, etc..14:16
ihrachysirenab: well kinda. are users posting the RFEs in question though? for the most part, it's people who are in the community, so a more informal means of tracking ideas could be less harsh for drivers. but maybe it's just me ranting and we should post more RFEs.14:16
ajoI guess the general workflow is14:16
ajocustomer -> openstack-related-company -> developer -> RFE14:17
ajoand in some cases14:17
ihrachysthe thing is, I see that some RFEs are actually closed on drivers meetings because there is no one to back the implementation up.14:17
ajoopenstack-user/contributor-company -> developer -> RFE14:17
*** moshele has joined #openstack-meeting-314:17
moshelehi14:17
ajonjohnston, and vhoward seem to be in a good TZ for the drivers meeting14:18
ajoand they helped so far by being there and answering :)14:18
njohnstonWe're happy to represent :)14:18
ihrachysI usually try to join too, but that time I was off14:18
ajoso I guess we could pre-analize here, and if they can represent us, that's great14:18
ajoI used too, and I will try from now on, but I will be quite random14:19
ajonjohnston++14:19
ajothanks14:19
*** bklei has joined #openstack-meeting-314:19
ihrachysyes, let's have US folks on board with representing the group there :)14:19
ajoI guess that from now on, we could have a meeting section for qos-related-rfes14:20
*** alexpilotti has joined #openstack-meeting-314:20
njohnstonsounds good14:20
ajoif you find anything missing or you believe something is wrong, please update https://etherpad.openstack.org/p/qos-roadmap when you have time14:20
*** woodster_ has joined #openstack-meeting-314:20
ajoI think VLAN marking, Ingress QoS rate limiting,  are probably quite straight forward14:21
*** lblanchard has joined #openstack-meeting-314:22
ajoin fact, when we implemented  the low levels of vm-egress , we did vm-ingress by mistake14:22
ajoand had to switch the implementation14:22
ihrachys:D we could close two features in one go14:22
davidshaVLAN marking is the same way as dscp for openvswitch.14:22
ajogal-sagie implementation is still there in gerrit14:22
ajodavidsha, exactly, it's almost the same14:23
ajoone tackles L3, and the other tackles L214:23
ihrachysstill two separate rule types14:23
ajoexactly14:23
ajothen, we have the ECN RFE, which makes sense IMO, but there are a few things to clarify14:24
*** itxaka|afk is now known as itxaka14:24
*** baohua has quit IRC14:24
ajobasically, ECN seems to be a mechanism that can be used in combination with TCP/IP to throttle the other host end dinamically14:24
*** alexpilotti has quit IRC14:24
ajoif your ingress is getting congested14:24
ajobut I believe we need to clarify how congestion is detected, and how we model the rules14:25
irenabajo: I have a suggestion14:25
davidshawould that be something to use with traffic classification then?14:25
ajoirenab, shot :D14:25
njohnston"Conventionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a mark in the IP header instead of dropping a packet in order to signal impending congestion. The receiver of the packet echoes the congestion indication to the sender, which reduces its transmission rate as if it detected a dropped packet."14:25
irenabI think each RFE should present relevant use case(s)14:25
*** evgenyf has quit IRC14:26
ajodavidsha, no, that's more related to your other RFE :)14:26
irenabso it will be clear how the requested functionality is used14:26
ajoirenab: +114:26
davidshaajo: Ah ok.14:26
ajoI see use cases for ECN now that I understood it,14:26
ajobut, yes, that's not well addressed14:26
ajowe should ask vikram and reedip_ reedip for that14:27
irenabI think neutron implementation details much less important and can be resolved later14:27
ihrachysis there a case when you have ECN supported but you want to disable it?14:27
ajoyes14:27
ajoihrachys, like filter ECN flags?14:27
irenabI beleive this can be the case, since it should be across the fabric14:28
njohnstonMy question is, ECN is negotiated, it isn't something that is supposed to be administratively enabled or disabled.  And the thing doing the negotiation won't be neutron, it will be the TCP stack implementation itself.14:28
*** ifat_afek has quit IRC14:28
ajonjohnston, as far as I undestood, switches, and mid-point network devices can modify the flags14:28
ajoon flight14:28
ihrachysajo: yeah but who's going to decide the flag to be set?14:29
ajoso they're able to throttle traffic going through it14:29
ajobut I'm not 100% sure, we may ask vikram and reedit14:29
njohnston"When both endpoints support ECN they mark their packets with ECT(0) or ECT(1). If the packet traverses an active queue management (AQM) queue (e.g., a queue that uses random early detection (RED)) that is experiencing congestion and the corresponding router supports ECN, it may change the codepoint to CE instead of dropping the packet."14:29
ajoI'm not an ECN expert by any mean, totally new to me14:29
ajonjohnston, ahh, exactly, I got it right then14:29
ajoihrachys, : that's one of the question I had for them14:29
ajoihrachys, it could be the agent, inspecting the ports sustained BW, the host load, the host br-* interfaces bw... etc14:30
ihrachysit's clearly not well understood in the team. let's do some homework reading docs before we decide anything on its feasibility.14:30
njohnston+114:30
davidsha+1`14:30
ajoyeah,14:30
ajoit's the time to read, and ask the RFE proposers14:30
ajoI'm still on that proccess14:30
ajoI see possible value in it14:31
ajoas something softer/more effective than policing14:31
ajobut, policing is fully automatic14:31
irenabajo: ihrachys : general question regarding RFE. Lets say there something that cannot be impemented by Ref implementation, it should not be proposed?14:31
ajoirenab, it's my understanding that "no", but, well, we have things that are only cisco implemented14:32
ajowhat was the name of it...14:32
ajohmm14:32
ihrachysirenab: I think otherwise, I believe it can be proposed.14:32
ihrachysthough I really wonder what can't be implemented in ovs.14:32
ajoI believe it could be proposed, if some SDN vendor implements it, but we'd have to discuss with drivers & core team14:32
irenabgot it, thanks14:33
ajoihrachys, I start to grasp the limits sometimes,14:33
ihrachysyes, that would require some exception process, but I believe it may have place for itself14:33
ajoyes, if the use case is well funded, as you said, and it can be modeled, we may try14:33
ajoThen14:34
ajowe have davidsha's RFE #link https://etherpad.openstack.org/p/qos-roadmap  about neutron QoS priority queing rules14:34
ajodavisha, if I didn't get it wrong14:34
*** dedery_ has joined #openstack-meeting-314:34
ihrachysajo: wrong link14:34
ajosorry14:34
ajo:/14:34
*** vhoward has quit IRC14:34
ajo#link https://bugs.launchpad.net/neutron/+bug/152767114:35
openstackLaunchpad bug 1527671 in neutron "[RFE]Neutron QoS Priority Queuing rule" [Wishlist,Triaged]14:35
ajoIf I didn't get it wrong14:35
ajoyou propose to have filters for traffic, so different traffic can be limited in different ways14:35
ajoright?14:35
davidshacorrect14:35
ajook14:35
ihrachysdoes it rely on traffic classifier?14:35
ihrachysI assume yes14:35
ajothat was foreseen  in our initial brainstorms14:36
ajoand we thought we could model such thing14:36
ihrachysI don't see the dep mentioned there14:36
ajoby attaching rules to traffic classifiers14:36
davidshait was originally going to use ovs flows and then I was looking into tc14:36
ajoihrachys, I commented in #1214:36
ihrachysoh I see14:36
ihrachyswas looking at original description14:36
ajoI believe14:36
ajothe user case is clear,14:36
ajoand the modeling, needs some eye on this: http://git.openstack.org/cgit/openstack/neutron-classifier14:37
ajo#link http://git.openstack.org/cgit/openstack/neutron-classifier14:37
ajothe RFE should probably be refactored to something like that14:37
njohnstondavidsha: Can we talk after this meeting about this?  I would like to understand how "the least likelihood of being rejected due to a queue reaching its maximum capacity" is different from DSCP.  That's kind of what DSCP is all about.14:37
*** vhoward has joined #openstack-meeting-314:37
*** idan_hefetz has quit IRC14:37
*** dedery has quit IRC14:38
davidshanjohnston: kk, I'm free to talk.14:38
njohnstonthanks14:38
ajonjohnston, the idea is that you assign different bw limits to different kinds of traffic14:38
ajoso you have different likelihoods14:38
ajobut let's expand later :)14:38
irenabajo: what is the state of neutron-classifier?14:38
*** vhoward_ has joined #openstack-meeting-314:38
ajodavidsha, does it seem reasonable for you to change that RFE into: integrating QoS rules to neutron-classifiers ?14:39
ajothat is something we should investigate, definitely14:39
ajoI thought we'd end up with some common REST API to manage the classifiers14:39
ajobut I don't see that, just libs14:39
ihrachysirenab: I believe it's on hold14:39
ajoand DB moles14:39
ajomodels14:39
ajook, may be they need help on that14:39
ihrachysirenab: probably starving for implementers14:39
davidshaajo: would it be ok if I looked into neutron classifier a bit more first?14:39
ajodavidsha, makes total sense14:40
ajo#action davidsha to look into neutron-classifiers state14:40
irenabI do not remember seeing anything on the mailing list or any dedicated sub-team14:40
*** rtheis has quit IRC14:40
ihrachysirenab: I believe it was just an experiment from Sean Collins that never delivered much14:41
ajolet's investigate, and bring up the topic to see how it is.14:41
ihrachysI suspect Sean would appreciate help14:41
*** rtheis has joined #openstack-meeting-314:41
ajoihrachys, when it was proposed the call was to make it a separate library14:41
ajoyes14:41
ajook14:42
*** vhoward has quit IRC14:42
ajoand, the last RFE(s) in place are for bandwidth guarantees14:42
*** shwetaap has joined #openstack-meeting-314:42
*** dedery_ has quit IRC14:42
ajowhen we talk about BW guarantees, it's about minimum bandwidth on ports14:42
ajowe can have strict, or best-effort14:42
*** dedery has joined #openstack-meeting-314:42
*** rtheis has quit IRC14:42
*** rtheis has joined #openstack-meeting-314:43
ajostrict requires coordination with nova-scheduler, so no interface is oversubscribed ....14:43
ajoI'm trying to fight on that battle, but ... to be fair, I'm far from success,14:43
ajothere's a spec from Jaypipes which could satisfy what we need in that regard, but It doesn't look to me as dynamic as I think it could be14:43
ajoif we could use that mechanism they're designing, it could be awesome14:44
ajo(generic resource pools)14:44
* ajo looks for the link14:44
irenabajo: meaning nova will manage BW counting?14:44
ajo#link https://review.openstack.org/#/c/253187/14:44
ajoirenab, nope14:44
ajonot by itself14:44
*** rhochmuth has joined #openstack-meeting-314:44
ajoI mean yes, sorry14:44
irenabrefer the counting done by 3rd party (neutron?)14:45
ajobut our dynamic way of modifying policies I'm unsure it plays well with that14:45
ajowe may need to some sort of process to sync to that API14:45
ajoany of our changes in policies14:45
ajoso the nova database is always up to date14:45
ajowhat bugs me, is that to make that possible, we could need to create one resource pool (or several) per compute node14:46
ajobecause those resources are consumed  in the compute nodes itselves14:46
ajothemselves14:46
ajo(sorry) :)14:46
ajoI guess that could also help model things like TOR switch bandwidth, and things like that14:46
ajobut ok, I'm trying to explore that14:47
ajo..14:47
ajoIn the other hand, and I finish,14:47
ajois best-effort14:47
ajothat basically, is... do what we can within the hosts/hypervisors14:47
ajoto guarantee that14:47
*** armax has quit IRC14:47
ajoovs and TC have mechanisms for that14:47
ajoI explored them, and I think davidsha did it too14:48
ajothey seem to work14:48
irenabajo: any summary you can share on your findings?14:48
ajothe OVS/OF ones require a total refactor or our openflow rules14:48
ajoof our14:48
ajobecause NORMAL rules don't work to queue traffic (we need to use queues)14:48
ajoand...14:48
*** jmckind has joined #openstack-meeting-314:49
ajoTC mixes technologies for filtering traffic (TC and OF...) (a bit like mixing linuxbridge and iptables with openflow)14:49
ajoso14:49
ajothere's no golden path14:49
ajoit can be done14:49
ajomay be we could start by TC,and then upgrade to something better in the future (OF only)14:49
ajoit worked pretty well on my testings14:50
ajobut ok14:50
ajoI can dive in the details on another meeting, probably not important now14:50
*** claudiub|2 has joined #openstack-meeting-314:50
ajoI will switch to checking the status of the ongoing patches if there's no objection14:50
ihrachysYES14:51
njohnstonno objection14:51
ajo#topic status14:51
*** openstack changes topic to "status (Meeting topic: neutron_qos)"14:51
ajonjohnston, how's DSCP? and L2 api, any blocker?14:51
ajoI made a comment on the RPC patch so you can test the upgrade mechanism14:51
njohnstonThe L2 agent patch has Ihar's +2 and just needs another https://review.openstack.org/#/c/267591/14:51
ajoI'm not sure if I fully clarified it14:51
ajo#action ajo review L2 agent patch!!! :]14:52
ihrachysnjohnston: there is a concern from yamamoto there. are we going to handle that?14:52
njohnstonRPC rolling upgrades has some concerns https://review.openstack.org/#/c/268040/14:52
ajonjohnston, yes will address it tonight I guess, I was focusing on the roadmap this morning :)14:52
irenabajo: just wanted to raise the discussion at neutron channel today regarding max_burst parameter misleading name in bw_limit rule14:52
njohnstonihrachys: I don't know how we can properly account for that14:53
*** Kamil has joined #openstack-meeting-314:53
davidshaihrachys: I don't think it's a problem, any project that used the agent_uuid_stamp was using it for flows.14:53
*** claudiub has quit IRC14:53
njohnston+1 ^^14:53
ihrachysdavidsha: I am good. just wanted to clarify.14:53
njohnstonSo once those 2 patches get merged the main DSCP patch looks good, it only has one nit from Vikram https://review.openstack.org/#/c/25173814:54
*** ho_away has joined #openstack-meeting-314:54
ajoirenab, I agree it's missleading :/ can we talk about it after meeting? :)14:54
*** tej has joined #openstack-meeting-314:54
irenabif the is agreed to be the bug slawek mentioned he would like to fix it14:54
irenabajo: sure14:54
njohnstonand then the python-neutronclient change for DSCP also looks to be in good shape: https://review.openstack.org/#/c/25428014:54
*** rhagarty_ has quit IRC14:55
ajook, that's great :)14:55
njohnstonThe documentation changes associated with DSCP already have 2 +2s, so I think they can go as soon as the patch they depend on merges14:55
njohnstonhttps://review.openstack.org/#/c/27363814:55
ajonjohnston, great , side note, the QoS API docs got re-injected, it seems the coauthor removed it by error14:55
ajohttps://review.openstack.org/#/c/284059/114:56
ajonjohnston, we need to contribute it to the common API guide ^14:56
njohnstond'oh14:56
*** s-kawabata_ has joined #openstack-meeting-314:56
*** fabiog has joined #openstack-meeting-314:56
ajoit's a hell, XML :)14:56
njohnstonajo: There is an API guide change as well: https://review.openstack.org/#/c/275253 with one +2 already14:57
ajoI must admit for QoS somebody from the doc team helped14:57
ajoohhh14:57
ajoawesome njohnston !!!14:57
*** safchain has quit IRC14:57
ajogood work14:57
njohnstonajo: All of the gaggle of DSCP changes are listed explicitly in the main patch's commit message: https://review.openstack.org/#/c/25173814:57
njohnstonand they all depend on the main patch14:57
*** rossella_s has quit IRC14:58
*** thatsdone has joined #openstack-meeting-314:58
ajoyikes14:58
ihrachysnice work14:58
ajo2 minutes to the end of the hour :/14:58
ajoany other important updates?14:58
*** rbak has joined #openstack-meeting-314:58
*** rossella_s has joined #openstack-meeting-314:58
*** dslevin has left #openstack-meeting-314:58
ajoI saw the LB support was making good progress too14:58
ajowe have fullstack tests now :)14:58
ihrachysI believe it's ready to merge14:58
ajook14:58
ajoso another action for me14:58
*** sigmavirus24_awa is now known as sigmavirus2414:58
ajo#action ajo review Linux bridge related patches for QoS14:59
ihrachysI wonder whether everyone is fine that two redhat cores merge stuff14:59
*** shinya_kwbt has joined #openstack-meeting-314:59
*** s-kawabata_ has left #openstack-meeting-314:59
*** witek has joined #openstack-meeting-314:59
* ajo tries to clone himself: raise CloneError()14:59
ajoihrachys, that's a good question14:59
*** mtanino has joined #openstack-meeting-314:59
ihrachysajo: maybe it's fine to review and then ask someone else to rubber stamp it14:59
ajogive that LB is not our main thing in redhat14:59
ajowe're doing it for the community mostly :)14:59
njohnstonlink for the LB change: https://review.openstack.org/23621015:00
ihrachysok we need to wrap up15:00
ajoyeah, may be asking for a third +2 and +W15:00
ajoyes15:00
ajook, wrapping up,thanks everybody15:00
* njohnston has no religion on +2s from y'all15:00
ajolet's keep discussing on #openstack-neutron (who cans)15:00
*** rtheis has quit IRC15:00
ajo#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Feb 24 15:00:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-02-24-14.03.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-02-24-14.03.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-02-24-14.03.log.html15:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Feb 24 15:01:02 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
rhochmutho/15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
fabiogo/15:01
rhochmuthhi everyone15:01
Kamilo/15:01
rbako/15:01
shinya_kwbto/15:01
rhochmuthAgenda is posted at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** rtheis has joined #openstack-meeting-315:01
*** armax has joined #openstack-meeting-315:01
*** mhoppal has joined #openstack-meeting-315:01
*** tgraichen has joined #openstack-meeting-315:01
rhochmuthAgenda for Wednesday February 24, 2016 (15:00 UTC)15:01
rhochmuth1.Log API15:01
rhochmuth1.Resolve whether dimensions per log message or per http request body? https://review.openstack.org/#/c/273058/15:01
rhochmuth2.Anything else15:01
rhochmuth2.Potential discussion about Broadview.15:01
rhochmuth3.Potential discussion on clustering and anomaly detection.15:01
rhochmuth4.Re-organizing the directory layout of the API, Log API and monasca-common.15:01
rhochmuth5.Reviews that need to be addressed.15:01
rhochmuth6.Monasca/devstack may need to update.15:01
rhochmuth7.sqlalchemy https://review.openstack.org/#/c/273058/15:01
rhochmuth8.java tempest tests / hibernate support15:01
ho_awayo/15:01
bkleio/15:01
rhochmuthWe can also discuss other topics too15:01
witekhello15:01
rhochmuth#topic log-api15:02
*** openstack changes topic to "log-api (Meeting topic: monasca)"15:02
*** jobrs has joined #openstack-meeting-315:02
tgraichenhi15:02
rhochmuthSo, I was wondering what we should do with the dimensions as well as any other items before getting the recent changes merged15:02
*** krtaylor has quit IRC15:02
jobrshi15:02
rhochmuthhi everyone, sorry, i'm not being so courteous today15:03
*** rtheis has quit IRC15:03
*** rtheis has joined #openstack-meeting-315:03
rhochmuthanyway, witek, sounds like you want dimensions per log message15:03
rhochmuthi can make that change15:03
witekyes, I though it is a good idea to keep dimensions consistent for logs and metrics15:03
*** betherly_ has joined #openstack-meeting-315:03
rhochmuthwell, i can't think of any downsides, other than a little extra data per log message15:04
witekand so, agent could have different dimensions for every file monitored15:04
rhochmuthmy assumption was taht the dimensions woudl be constant per log15:04
*** brunograz has joined #openstack-meeting-315:04
*** brunograz has left #openstack-meeting-315:04
rhochmuthand the aganet would only be processing one log at a time15:04
rhochmuthso, that doesn't sound like a valid assumption on my part15:04
*** omer_etrog has joined #openstack-meeting-315:05
*** mrmartin has joined #openstack-meeting-315:05
witekthen we would need agent instance per log file15:05
witekI don't think it's good15:05
rhochmuthok, i'll make the change15:05
rhochmuthshould go quick15:05
*** betherly_ is now known as betherly15:06
rhochmuthis there anything else that come to mind that i might need to address right now15:06
witekok, thanks a lot15:06
rhochmuthanything else related to log api we need to discuss?15:06
witeki don't think15:06
*** slogan_r_ has joined #openstack-meeting-315:06
rhochmuthok, moving on then, thanks witek15:06
*** betherly has left #openstack-meeting-315:06
rhochmuth#topic broadview15:07
*** openstack changes topic to "broadview (Meeting topic: monasca)"15:07
rhochmuththis is a potential topic15:07
rhochmuthnot sure if syd is here or anyone else from broadview15:07
slogan_r_yep :-)15:07
slogan_r_here15:07
rhochmuthhi15:07
slogan_r_so, we are currently working on 3 projects15:07
*** salv-orlando has joined #openstack-meeting-315:08
rhochmuthso there is broadview-lib, broadview-collector and broadview-ui15:08
slogan_r_the basic idea is that there is interesting networking underlay data to push into monasca as metrics15:08
slogan_r_right15:08
slogan_r_lib has landed15:08
slogan_r_collector is a service that will use lib to push metrics into monasca15:08
slogan_r_ui is a panel in horizon to configure it all15:09
*** omer_etrog has quit IRC15:09
rhochmuthso, i think if you have the metrics dump you sent me, that woudl be cool to post here15:09
slogan_r_ah, unable to do that this meeting15:09
rhochmuthnp15:09
slogan_r_not near the data15:09
*** ddieterly has joined #openstack-meeting-315:09
rhochmuthso, is there a list of vendors that we can get that broadview is applicaple too15:10
slogan_r_but the short story is that network switches have buffers, and buffers have all sorts of iteresting data that can help detect issues that you normally don't see15:10
rhochmuthi was hoping it worked for the hpe 5930 switch15:10
slogan_r_the vendor list is hue, HP among them, but most switch vendors are using our silicon15:10
slogan_r_I look into that, you mentioned it would be nice to have one of those switches, right?15:11
rhochmuthabsolutely15:11
slogan_r_let me take that up15:11
rhochmuthbut i was hoping that hpe was planning on using a switch that had support for broadview15:11
slogan_r_so in the coming week I should have a gerrit review up for the collector15:11
rhochmuthcool15:12
slogan_r_appreciate anyone who is interested in reviewing to look, particularly the monasca plugin part15:12
rhochmuthplease add me to the review15:12
rhochmuthas well as anyone else that is interested15:12
slogan_r_one issue I am facing is how to gain access to IP address and ports for talking to monasca from pthon API15:12
*** jobrs_ has joined #openstack-meeting-315:13
slogan_r_there is a yaml file with all the data, but it is read only except for root and mon-api ?? group I think15:13
*** jobrs has quit IRC15:13
slogan_r_that's an issue for the code review maybe15:13
rhochmuththat is the default install15:13
slogan_r_creating a monasca Client object takes some of that config as kwargs15:14
*** jobrs has joined #openstack-meeting-315:14
fabiogslogan_r_: how lib access the data in the switch? is it using snmp traps?15:14
slogan_r_fabiog: for our trident2 and later chips, there is an agent running switch side15:14
*** krtaylor has joined #openstack-meeting-315:14
*** Swami has joined #openstack-meeting-315:14
slogan_r_that agent talks HTP 1.1 to our collector when thresholds are crossed15:14
fabiogslogan_r_: so the agent is pushing the data out at a fixed interval?15:15
slogan_r_it can, or as thresholds reached15:15
slogan_r_it can be polled as well15:15
slogan_r_longer tem, we want to see data that resolves what is happening in hardware with, say, a virtual network that is bound to tenant in neutron15:15
*** JOlsen has joined #openstack-meeting-315:16
*** numans has quit IRC15:16
slogan_r_that would be very useful, say, if an operator were to experience problems in his virtual network -- if we can see issues in the hardware, and we can tie the two together, then we can maybe isolate to a switch in a datacenter and it can be looked at15:17
rhochmuthwould virtual network include support for ovs15:17
slogan_r_what I am doing now with these projects is just that start of it15:17
*** jobrs_ has quit IRC15:17
slogan_r_yes, I mean OVS15:17
rhochmuthawesome15:17
*** atuvenie__ has joined #openstack-meeting-315:18
*** christian_ has joined #openstack-meeting-315:18
rhochmuthi'm very interested in this area15:18
slogan_r_me too :-)15:18
rhochmuthas i've had a few requests over that last couple of weeks to start looking at support for vswitch15:18
bkleislogan_r_: we were thinking about the same thing at twc -- a libvirt style plugin that would post virtual router bw15:19
slogan_r_OVS is the obvious place to start15:19
rhochmuththis is coming up as one of our big requests15:19
bkleiand cross post to the admin project, like libvirt plugin15:19
slogan_r_but segementation IDs are a neutron/nova thing, so it is not limited to OVS15:19
slogan_r_yep15:19
*** rhagarty has joined #openstack-meeting-315:19
bkleiwe've got ovs specific code here that does that -- i can put a monasca-agent patch up and see what you guys think15:20
slogan_r_cool15:20
rhochmuthbklei: thanks, interested too15:20
bkleicool, will include you on the review -- any anyone else interested15:20
slogan_r_again, what we have now for our part is early stage, we are not attempting to address this overlay/underlay resolution but that will come15:21
slogan_r_the underlying agent has several boxes, so to speak, each covering a class of data that the switch might expose15:21
slogan_r_the contrbution at this stage is about buffer threshold events that lead to packet drops in the silicon15:22
slogan_r_the ability to even tie together underlay with a segmentation ID is work to be done15:22
slogan_r_but it is obviously somewhat of a holy grail15:22
*** haleyb has joined #openstack-meeting-315:22
slogan_r_important to set expectations15:22
slogan_r_anyway, I think monasca rocks and it is why we are here15:23
rhochmuththx sysd15:23
rhochmuthsyd15:23
slogan_r_looking forward to working with you all15:23
rhochmuthsorry15:23
*** iyamahat has joined #openstack-meeting-315:23
rhochmuthi'm wondering about interest from folks on working on this15:23
rhochmuthalso, seeing how to best coordinate15:24
rhochmuthmight be best to have a broadview specific meeting15:24
slogan_r_okay, we could do that15:24
rhochmuthif there is enough interest15:24
slogan_r_I was thinking it might be good as a pseudo PTL (what do you call people who lead unofficial projects?) to maybe be more present in irc on a channel at least15:25
slogan_r_maybe #openstack-broadview or something15:25
rhochmuthyes, i think that makes sense15:25
*** rtheis has quit IRC15:25
rhochmuthok, leet's wrap up on this topic15:25
slogan_r_btw, monasca-api has been a big influence on my docs and currently, my devstack hacking15:25
*** rtheis has joined #openstack-meeting-315:26
slogan_r_s/my/our/15:26
slogan_r_yep, thanks for the time15:26
rhochmuththanks syd15:26
rhochmuthlet's discuss off-line15:26
slogan_r_k15:26
rhochmuthso options, and see what makes sense15:26
*** rtheis has quit IRC15:26
rhochmuth#topic analytics15:27
*** openstack changes topic to "analytics (Meeting topic: monasca)"15:27
*** rtheis has joined #openstack-meeting-315:27
rhochmuthso, i just want to give and update15:27
rhochmuthis anyone from bristol hpe here15:27
rhochmuthanyway, it looks like we are getting some interest in alarm clustering and anomaly detection algorithms15:28
*** zz_dimtruck is now known as dimtruck15:28
ho_awaycool :-)15:28
rhochmuthho_away: I would like to get some discussions with you and the team15:29
ho_awaywhat is the relationship b/w bristol hpe and this topic?15:29
rhochmuthso i'll work on brokering that and keepign you in the loop15:29
*** dims has quit IRC15:29
*** salv-orlando has quit IRC15:29
rhochmuththere is lab there that is doing some potential work in this area15:29
ho_awayi will be in bristol hpe next week.15:29
ho_awayto attend other meeting.15:30
rhochmuthi can get you introduced15:30
ho_awaygreat!15:30
*** dims has joined #openstack-meeting-315:30
rhochmuthso, since not everyone is here, i'll defer to another day15:30
rhochmuthbut we're going to have to start planning and coordinating in this area15:31
rhochmuthi thihnk15:31
rhochmuththink15:31
fabiogrhochmuth: let's plan to have that as a topic for the summit15:31
rhochmuthso, we might have to have some additional sessions on this topic15:31
rhochmuthsounds good15:31
rhochmuthand that isn't too far off at this point15:31
ho_awaysounds nice!15:31
rhochmuthho_away, will you be in austin15:31
ho_awaynot decided yet but i will negociate it with my boss15:32
slogan_r_:-)15:32
rhochmuthi'll check with the other folks15:32
rhochmuthgood lock15:32
*** atuvenie__ has quit IRC15:32
rhochmuthok, next topic, unles more to discuss?15:33
rhochmuth#re-factoring15:33
rhochmuthso, i was planning on a proposal, but i didn't get to it15:33
*** alexpilotti has joined #openstack-meeting-315:34
rhochmuthin general, i just think our file organization for the python code could be improved a little15:34
rhochmuthi'll try and get somethign written up for next time15:34
rhochmuthsorry, i'm wasting folks time on this15:34
*** rtheis has quit IRC15:34
*** alexpilotti has quit IRC15:34
rhochmuth#topic review15:34
*** openstack changes topic to "review (Meeting topic: monasca)"15:34
rhochmuth#tpoic reviews15:34
*** dims has quit IRC15:34
*** krtaylor has quit IRC15:34
rhochmuthso, if there are any reivews that need attending to please let me know15:35
*** rtheis has joined #openstack-meeting-315:35
rhochmuthwe are still a little backed up15:35
witekI put sqlalchemy as a separate point15:35
rhochmuthyes, I +1'd that review15:35
*** rhagarty_ has joined #openstack-meeting-315:36
rhochmuthTHis one, https://review.openstack.org/#/c/266922/15:36
fabiogrhochmuth: https://review.openstack.org/#/c/251674/ needs some love from Infra core15:36
*** pradipm has joined #openstack-meeting-315:36
fabiogso we can finally get the client in the global reqs ...15:36
*** tsv has joined #openstack-meeting-315:37
rhochmuthSo, relative to https://review.openstack.org/#/c/266922/, the ORM/SQLAlchemy, it would be good to have some more eyes and +1s. I hate holding up this review15:37
rhochmuthIn general, i'm ok switching over to sqlalchemy15:37
rhochmuthand keeping mysql around jsut in case15:37
rhochmuthhopefully backing out the mysql repo over time15:37
witekbut sqlalchemy would become default, right?15:37
rhochmuththat is fine with me15:37
*** rhagarty has quit IRC15:37
witekcool15:38
rhochmuthwe dont' have any production concerns with the python15:38
* slogan_r_ will try and code review that one15:38
rhochmuthso, i think getting it in the pipe asap to get more testing on it is best15:38
rhochmuththanks syd15:38
rhochmuthit is a biggie15:38
rhochmuthit doesnt' help that i'm not a sqlalchemy expert15:38
rhochmuthso i'm learnign this area15:38
slogan_r_nod15:38
rhochmuthi'l try and lobby some resources from hpe15:39
rhochmuthfabiog: what do you need from us15:39
*** yamahata has joined #openstack-meeting-315:39
rhochmuththat review is taking forever15:39
witekthanks Roland!15:39
rhochmuthfabiog?15:40
*** vijendar has joined #openstack-meeting-315:40
fabiogrhochmuth: it would be good if Doug will +2 it again. He did before but I had to rebase15:40
fabiogalso it will be good if many Monasca people will +1 this will generate interest around the patch15:41
fabiogto get other infra committers to merge it15:41
rhochmuthis everything else resolved then15:41
fabiogyes, I did a second patch that added the tempest check for requirements and that has been merged. I added as dependency to the reqs patch15:41
rhochmuthOK, So if folks can +1, https://review.openstack.org/#/c/251674/, that would be great15:42
fabiogthanks, all15:42
rhochmuthprobably should ping doug15:42
rhochmuthAnye other pressing review?15:43
*** vijendar1 has joined #openstack-meeting-315:43
rhochmuth#topic devstack15:43
*** openstack changes topic to "devstack (Meeting topic: monasca)"15:43
rhochmuthsounds like devstack is broken again15:44
*** nkrinner has quit IRC15:44
shinya_kwbtYes.15:44
slogan_r_how so?15:44
shinya_kwbtmonasca-vagrant provisioning is currently success.15:44
*** slogan_r_ is now known as slogan15:44
*** dslevin has joined #openstack-meeting-315:44
shinya_kwbtBut I can't log into Horizon UI. Roland and Witold are neither.15:44
*** dslevin has quit IRC15:44
shinya_kwbtI doubt keystone because log in processing raises error.15:45
rhochmuthso, there is a bug that was introduced in the monasca-ui15:45
rhochmuthnot sure when15:45
rhochmuththat is preventing the horizon login from working15:45
witekI think it is dependencies issue15:45
*** dslevin has joined #openstack-meeting-315:45
shinya_kwbtI think so too.15:45
rhochmuthso, can you resolve15:45
witekwould updating devstack box help?15:46
*** dslevin has quit IRC15:46
sloganwhen you say devstack bug, are you referring to devstack code in monasca-api?15:46
rhochmuthno, devstack and monasca-vagrant are entirely separate15:46
shinya_kwbtI tried to update devstack box15:46
*** vijendar has quit IRC15:46
*** dslevin has joined #openstack-meeting-315:46
rhochmuththere is the monasca-vagrant repo15:46
rhochmuthand then there is monasca-api/devstack15:47
*** dslevin has quit IRC15:47
rhochmuthand there is a Vagrantfile in the devstack directory15:47
sloganyes15:47
witekshinya_kwbt: any success?15:47
*** krtaylor has joined #openstack-meeting-315:47
*** dslevin has joined #openstack-meeting-315:47
shinya_kwbtThen I tried to make monasca/devstack which has latest keystone by using ds-build. This image doesn't have admin_token,15:48
shinya_kwbtthen I patched this(https://review.openstack.org/284010/), I finally successfully log in.15:48
*** dslevin has quit IRC15:48
*** vgridnev has quit IRC15:49
shinya_kwbtmonasca-repo's devstack seem to be old15:49
*** dslevin has joined #openstack-meeting-315:49
rhochmuthohh, now i understand15:49
rhochmuththe devstack vm that is in monasca-vagrant is out of sync15:50
witekshinya_kwbt: so it seems to solve the problem, right?15:50
*** galstrom_zzz is now known as galstrom15:50
*** dslevin has quit IRC15:50
shinya_kwbtmade at July 2015, liberty version.15:50
sloganI noticed when I tried vagrant that python monasca-client failed to install15:51
sloganI had to hand install it afterwards15:51
rhochmuthso, what is the status now then15:51
shinya_kwbtwitek: I can log into Horizon.15:51
rhochmuthshinya: does your review get things working again?15:52
*** dslevin has joined #openstack-meeting-315:52
rhochmuthand do we need to update the devstack image?15:52
*** Sukhdev has joined #openstack-meeting-315:52
*** dslevin has quit IRC15:52
witekrhochmuth: I think we need an update15:53
*** dslevin has joined #openstack-meeting-315:53
KamilThe current version was created 8 months ago15:53
rhochmuthi'll check with the developer to see what is involved15:53
shinya_kwbtI think needs to update. Because current image is liberty.15:53
*** mhoppal has quit IRC15:54
rhochmuththe other option is to move completely to the devstack in monasca-api/devstack15:54
*** dslevin has quit IRC15:54
rhochmuthhow do folks feel about that15:54
rhochmuthsecond option15:55
*** dslevin has joined #openstack-meeting-315:55
bklei+1 on that15:55
sloganwhy would there need to be anything other than the monasca-api devstack? It's the only one I considered when I went looking15:55
rhochmuthit is mostly historical/legacy15:55
witekwe still are using ansible roles15:56
sloganI'm not sure why there is a monasca-vagrant, can someone explain that and the difference between the monasca-api devstack vagrant file?15:56
witekbut want to write devstack plugin for log-part15:56
rhochmuthwe started with our own Vagrant env and a lot of Ansible15:56
*** matrohon has quit IRC15:56
Kamilfor testing purposes monasca-vagrant is fast and easy15:56
*** qwebirc38287 has joined #openstack-meeting-315:57
rhochmuthi'll talk with the developer about a devstack image to see what is involved15:57
*** CatherineD_ has joined #openstack-meeting-315:57
sloganthere is a Chinese saying: the tiger that chases two rabbits will catch neither15:57
rhochmuthlol15:57
*** thatsdone_ has joined #openstack-meeting-315:57
slogans/rabbits/devstacks/15:57
rhochmuthso, we only have 2 minutes15:58
*** vgridnev has joined #openstack-meeting-315:58
ho_awayfyi: admin token is deprecated and found the commit https://github.com/openstack/keystone/commit/5286b4a297b5a94895a311a9e564aa87cb54dbfd15:58
*** baoli has quit IRC15:58
*** baoli has joined #openstack-meeting-315:59
pradipmIs there a document that describes how to integrate ELK (elastic-search, logstash,kibana) with Monasca?15:59
witekthere is a change in gerrit15:59
*** thatsdone has quit IRC16:00
rhochmuthwe've reached the end folks16:00
rhochmuthgot to end the meeting16:00
*** cjvolzka has joined #openstack-meeting-316:00
rhochmuthhead over to #openstack-monasca for more follow-up16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Feb 24 16:00:32 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-02-24-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-24-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-24-15.01.log.html16:00
eglute#startmeeting defcore16:00
openstackMeeting started Wed Feb 24 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
*** ho_away has left #openstack-meeting-316:00
*** jschwarz has quit IRC16:00
markvoelkero/16:00
eglutechair markvoelker16:00
*** Kamil has quit IRC16:01
*** tgraichen has quit IRC16:01
*** pradipm has left #openstack-meeting-316:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
eglute#link  https://etherpad.openstack.org/p/DefCoreRing.1316:01
egluteHello Everyone, let us know if you are here for the defcore meeting16:01
CatherineD_o/16:01
*** christian_ has quit IRC16:01
eglutealso, please review the agenda and add/edit as needed16:02
*** safchain has joined #openstack-meeting-316:02
eglutedwalleck is not able to make today's meeting, so we will move his agenda items to next week16:02
eglutehogepodge are you around?16:02
*** dims has joined #openstack-meeting-316:03
gemajo/16:03
hogepodgeo/16:03
eglute#topic Multi-tenant tests16:04
*** openstack changes topic to "Multi-tenant tests (Meeting topic: defcore)"16:04
eglutehogepodge i saw you were talking to Mike in defcore channel about it, are you ready to go over this?16:04
hogepodgeA bit yeah.16:04
hogepodgeMy original assertion is that multi-tenant tests get in the way of one of our goals of interoperability tests being user-runnable.16:05
*** hdaniel has quit IRC16:05
hogepodgeAnd what many of those tests are measuring is more security related than interoperability related.16:05
hogepodgeI had proposed a large number of tests be flagged as a straw-man proposal, but it looks like that number will diminish significantly16:06
egluteright16:06
*** jmckind has quit IRC16:07
hogepodgeHere's a bit of status, the list I flagged: https://etherpad.openstack.org/p/multi-tenant-defcore-tests16:07
hogepodge18 have a patch that removes the unnecessary multi-tenant requirement. https://review.openstack.org/#/c/283819/16:07
*** randybias has joined #openstack-meeting-316:07
*** jmckind has joined #openstack-meeting-316:08
*** salv-orlando has joined #openstack-meeting-316:08
eglutethat looks good16:08
markvoelker#link https://etherpad.openstack.org/p/multi-tenant-defcore-tests multitenant test list16:08
hogepodgeThe authorization tests are scheduled to be removed from Tempest, which will only leave a few.16:08
markvoelker#link https://review.openstack.org/#/c/283819/ patch removing unnecessary multi-tenancy16:09
hogepodgebut at the mid-cycle, I'd like us to consider a policy that restricts us from adding other multi-tenant tests from consideration.16:09
eglutehogepodge i like that idea16:09
*** shinya_kwbt has left #openstack-meeting-316:09
markvoelkerhogepodge: is that on the midcycle etherpad?  https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:10
*** yamahata has quit IRC16:10
hogepodgemarkvoelker: just added it. Thanks16:11
eglutehogepodge so this would make your patch a lot smaller, correct?16:12
hogepodgeeglute: correct16:13
*** cbouch has joined #openstack-meeting-316:14
hogepodgethat patch was intended to provoke discussion and action to review the tests, which I finally got around to this week :-D16:14
eglutethanks hogepodge. it would be good if you submitted a new patch. in the mean time, i assume you would like for us to review the tests in that ehterpad?16:14
eglute:)16:14
hogepodgeeglute: it's not necessary, that's more of a working document which I'm going to use to build out defcore patches16:15
eglutecool16:15
egluteany other comments on this topic?16:15
*** jobrs has quit IRC16:15
eglute#topic Add 2016.01 required test list16:16
*** openstack changes topic to "Add 2016.01 required test list (Meeting topic: defcore)"16:16
eglute#link https://review.openstack.org/#/c/283743/16:16
eglutethanks CatherineD_ for adding those16:16
CatherineD_But the total number16:16
eglutethese are required for RefStack correct16:16
eglutesorry CatherineD_ ... looks like you were in the middle of the comment?16:17
CatherineD_Of flagged tests would remain the same?16:17
*** mrmartin has quit IRC16:17
* CatherineD_ sorry my internet is slow. 16:18
eglutehogepodge?16:19
hogepodgeCatherineD_: when I was creating those files I was including flagged tests, but it may make sense to not, as vendors have found it a bit confusing. On one hand, if they pass flagged tests it's nice to know, on the other hand many vendors think they've failed when they're actually ok16:19
*** dedery_ has joined #openstack-meeting-316:19
CatherineD_Ok thx16:20
eglutethanks hogepodge16:20
hogepodgewe should make required.py a generic tool and include instructions on how vendors can use it. We have more test refactoring happening this week and it would be better to generate that list dynamically rather than use a static version16:20
hogepodgeI was on that path at Vancouver last year, but then other work took me away16:21
egluteis that something that we also need to add to the midcycle?16:21
hogepodgeI can pick that work up again, but not until late next week at earliest.16:22
*** FallenPegasus has joined #openstack-meeting-316:22
eglutethat works for me16:22
egluteok, next topic Add 2016.01 required test list16:22
eglutethanks CatherineD_ for adding that16:22
*** dedery has quit IRC16:22
eglutethis is required for refstack, so we need to make sure to add it each time we pass a guideline16:23
CatherineD_A user was asking for the required let on #refstack16:23
*** rockyg has joined #openstack-meeting-316:23
rockygo/16:23
hogepodgeCatherineD_: Can refstack parse the defcore project for new guidelines?16:24
eglutei think we need to document somewhere all the things that need to happen for each new guideline. Maybe in a Hacking file?16:24
*** slogan has quit IRC16:24
*** dedery_ has quit IRC16:24
*** banix has joined #openstack-meeting-316:24
*** bpokorny has joined #openstack-meeting-316:24
markvoelkerI'd suggest we etherpad it first, and then see if we can't simplify it.16:25
eglutemarkvoelker sounds good. i like simplifying things16:25
rockyg++16:25
eglute#action markvoelker and eglute to work on simplifying things required after each guideline is passed16:26
egluteeveryone, please review https://review.openstack.org/#/c/283743/16:26
*** vijendar1 has quit IRC16:26
CatherineD_Right now parsing of the guideline is at the server side.  We will need to see whether it make sense for client side16:26
eglutethanks CatherineD_ let me know what you find out16:27
eglute#action CatherineD_ to check whether it makes sense to parse guidelines on refstack's client side16:28
egluteany other comments on this topic?16:28
eglute#topic RefStack questions16:28
*** openstack changes topic to "RefStack questions (Meeting topic: defcore)"16:28
*** jmckind_ has joined #openstack-meeting-316:28
eglute#link http://lists.openstack.org/pipermail/defcore-committee/2016-February/001035.html16:28
eglutethanks markvoelker for responding to those. i agree with your responses, but would like to hear from others16:29
*** ajmiller_ has joined #openstack-meeting-316:29
markvoelkerIn particular, Alex had a couple of questions in his reply that would be best answered by someone from the Foundation I believe16:29
*** ajmiller has quit IRC16:29
eglutehogepodge did you have a chance to look at the questions?16:31
*** belmoreira has quit IRC16:31
*** catherineD has joined #openstack-meeting-316:31
*** jmckind has quit IRC16:31
hogepodgea bit, a marketplace link shouldn't be a requirement for refstack. I do want to make links to refstack a part of the marketplace, and setting up that code on our side right now16:32
*** tsv has quit IRC16:32
*** ihrachys has quit IRC16:33
* eglute wishes she could see if someone is typing 16:33
*** jmckind_ has quit IRC16:33
hogepodgeI don't have too strong of opinions on how user-management happens on the refstack side. using openstack id is preferred for a number of things, just because it centralizes identity across other projects16:33
*** vhoward_ has quit IRC16:33
*** vijendar has joined #openstack-meeting-316:33
egluteCatherineD_ do you have any other RefStack related questions besides what was in the email?16:34
*** hichihar_ has joined #openstack-meeting-316:34
catherineDeglute: yes16:34
eglutecatherineD go ahead!16:35
*** CatherineD_ has quit IRC16:35
*** hichihar_ has quit IRC16:35
*** hichihara has joined #openstack-meeting-316:35
catherineDI think the discussion point is should anyone being able to list the users in RefStack16:35
catherineDFrom last meeting , I think the direction is no..16:36
markvoelker+116:36
eglute+116:36
catherineDsome of the RefStack team member was questioning why someone can do that in gerrit and not in RefStack16:36
*** Poornima has joined #openstack-meeting-316:37
markvoelkerMy larger question would be "why would we need to do it in RefStack, regardless of what some other tools do?"16:37
hogepodgemarkvoelker: +116:37
catherineD+116:37
eglutei agree with markvoelker16:37
markvoelkerE.g. if there's a real use case for being able to do it, I'm not necessarily opposed...but there doesn't seem to be one.16:37
markvoelkerSo my tendency is to keep it private.16:38
*** atuvenie__ has joined #openstack-meeting-316:38
rockygone reason for no is that many of the individuals are actually proxies for the companies hey work for16:38
*** fawadkhaliq has joined #openstack-meeting-316:38
egluteagreed, can always be added once a real use case comes up16:38
catherineD++16:38
*** jmckind has joined #openstack-meeting-316:38
eglutebut rockyg also has another great point for not having it16:39
eglutecatherineD any other questions?16:39
rockygplus, anonymous submitters need to stay anon for everyone bu foundation16:40
*** cbouch has quit IRC16:40
eglute+116:40
catherineDthat is it for me ... I just need to confirm the user list privacy topic16:40
*** cbouch has joined #openstack-meeting-316:40
eglutethank you catherineD!16:41
eglute#topic ID'ing new capabilities for 2016.0716:41
*** openstack changes topic to "ID'ing new capabilities for 2016.07 (Meeting topic: defcore)"16:41
catherineDthank you all !!!16:41
eglutewe still need volunteers for scoring capabilities16:41
egluteany takers for Cinder, Swift, and Glance?16:42
*** 32NAAC6RR has quit IRC16:42
markvoelkerI'll double up and help with glance16:42
hogepodgeI can do Cinder and Swift16:42
eglutethank you markvoelker16:42
eglutethank you hogepodge!16:42
hogepodgeI should know this, but do we have a work timeline anywhere?16:43
markvoelkerhogepodge: see bottom of etherpad.16:43
eglutefor scoring?16:43
*** iyamahat has quit IRC16:43
markvoelkerIdeally if we can get a first pass done before the midcycle that would be best (so we can discuss in person)16:43
rockygso, looks like glance v2 won't make it into nova for mitaka.  so glance remains as is.16:43
markvoelkerDoens't have to be complete, but something we can start iterating on16:43
hogepodgeyes :-D16:44
*** qwebirc38287 has quit IRC16:44
gemamarkvoelker: I have a question, I have been reading the keystone api and was wondering what's the criteria to call something "a capability"16:44
hogepodgeget-me-an-ip will land partially in mitaka in neutron, but the cross-project work is expected to be done early N16:44
gemaother than not needing admin to use it16:45
rockygGlance is done :-016:45
hogepodgewe should consider the impact of that on our network capabilities, as it is being written specifically to address networking interoperability16:45
markvoelkergema: This might help. =) https://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.rst16:45
hogepodgegema: for defcore, a capability needs a non-admin test. that's the current bar16:46
gemamarkvoelker: thank you, I was lost16:46
gemahogepodge: ack, thanks16:46
markvoelkerIn plainer terms, I think of a capability as something an end user of a cloud can expect to use.  Usually that means an API that's user-facing16:46
*** baoli_ has joined #openstack-meeting-316:46
eglutethanks markvoelker and hogepodge16:46
markvoelkerCapabilities also have to have tests, so you can look through tempest to get a rough idea of what capabilities are out there16:47
hogepodgeI don't think we have a great mapping between tests and how to translate that into user actionable API calls, but we're working with what we have16:47
egluteanything else regarding scoring?16:47
gemanot from me, thanks for the tips16:48
eglute#topic midcycle16:48
*** openstack changes topic to "midcycle (Meeting topic: defcore)"16:48
*** moshele has quit IRC16:48
egluteNext week, I would like to go over the agenda for the midcycle, and time-box different topics16:48
*** brunssen has joined #openstack-meeting-316:48
egluteas well as prioritize the,16:48
*** baoli has quit IRC16:48
eglutethem16:49
markvoelker+1, I'm planning to work up a strawman schedule that we can discuss16:49
eglutewe will have some people call in for specific topics, so times will be helpful16:49
eglutethanks markvoelker16:49
eglute#action markvoelker  to work up a strawman schedule for midcycle that we can discuss16:49
egluteso if there is a topic that is not on the midcycle etherpad that you would like to have discussed, please add it16:50
eglute#link https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:50
egluteand put your name by your topics16:50
eglutealso, today is your last chance to respond to the dietary restrictions poll: http://doodle.com/poll/ewsiepmhv9p6r8e7,16:51
eglutebut i think everyone here has responded16:51
egluteso thank you!16:51
*** piet has quit IRC16:51
egluteanother important topic for midcycle: Tuesday night. do we want something formal organized? if so, what?16:52
*** vgridnev has quit IRC16:52
*** piet has joined #openstack-meeting-316:52
markvoelkerI think dinner is in order. =)16:52
egluteanyone else interested in dinner?16:53
hogepodgeWe're out at the Domain, which has a number of restaurants that are easy to get to from the venue. We're a ways away from downtown.16:53
eglutewe will need reservations16:53
*** FallenPegasus has quit IRC16:53
rockyg++  I also suggest an informal gathering at the lonestar....great place for that16:53
brunssenFor a large group at a restaurant in the Domain we will want to have reservations.16:53
eglutebrunssen right, will try to make them this week16:54
brunssenI am happy to set something up if you want me to do so?16:54
eglutebrunssen can you suggest several good restaurants in the area? i only know of one!16:54
eglutebrunssen that would be great!16:54
eglute#action brunssen to book dinner for Tuesday night16:54
brunssenOK, no problem.  I will send out a list of restaurants to the group and we can take an informal poll16:55
eglutethank you!16:55
brunssenThen I can make the reservation for Tuesday March 816:55
eglutethat works for me :)16:56
eglute2 minutes remaining... any last words?16:56
brunssenOK, consider it done.16:56
eglutethank you brunssen!16:56
eglutethanks everyone!16:57
rockygword16:57
*** Sukhdev has quit IRC16:57
eglute#endmeeting16:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:57
openstackMeeting ended Wed Feb 24 16:57:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-24-16.00.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-24-16.00.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-24-16.00.log.html16:57
rockygthanks!16:57
*** catherineD has left #openstack-meeting-316:57
*** lbragstad has quit IRC16:58
*** itxaka has quit IRC16:58
*** dims has quit IRC17:00
*** iyamahat has joined #openstack-meeting-317:00
*** amotoki has quit IRC17:00
*** FallenPegasus has joined #openstack-meeting-317:01
*** lbragstad has joined #openstack-meeting-317:02
*** hichihara has quit IRC17:02
*** galstrom is now known as galstrom_zzz17:03
*** atuvenie__ has quit IRC17:03
*** dims has joined #openstack-meeting-317:03
*** mjturek1 has joined #openstack-meeting-317:04
*** mjturek1 has left #openstack-meeting-317:05
*** kzaitsev_mb has quit IRC17:05
*** rockyg has quit IRC17:06
*** yamahata has joined #openstack-meeting-317:06
*** belmoreira has joined #openstack-meeting-317:06
*** gema has left #openstack-meeting-317:10
*** jlanoux has quit IRC17:20
*** jmckind_ has joined #openstack-meeting-317:20
*** jmckind has quit IRC17:21
*** thatsdone has joined #openstack-meeting-317:22
*** thatsdone has quit IRC17:22
*** thatsdone_ has quit IRC17:23
*** vijendar has left #openstack-meeting-317:25
*** ihrachys has joined #openstack-meeting-317:26
*** kzaitsev_mb has joined #openstack-meeting-317:29
*** ihrachys has quit IRC17:29
*** davidsha has quit IRC17:32
*** rtheis has quit IRC17:32
*** rtheis has joined #openstack-meeting-317:33
*** rtheis has quit IRC17:39
*** randybias has quit IRC17:41
*** spzala has quit IRC17:42
*** spzala has joined #openstack-meeting-317:42
*** spzala has quit IRC17:43
*** spzala has joined #openstack-meeting-317:43
*** kzaitsev_mb has quit IRC17:44
*** fabiog has quit IRC17:45
*** _sarob has joined #openstack-meeting-317:46
*** moshele has joined #openstack-meeting-317:48
*** yamamoto has quit IRC17:49
*** sambetts is now known as sambetts|afk17:49
*** rtheis has joined #openstack-meeting-317:50
*** alexpilotti has joined #openstack-meeting-317:55
*** rtheis has quit IRC17:56
*** rtheis has joined #openstack-meeting-317:56
*** moshele has quit IRC17:57
*** brunssen has quit IRC18:00
*** claudiub|2 has quit IRC18:00
*** rtheis has quit IRC18:01
*** safchain has quit IRC18:01
*** sigmavirus24 is now known as sigmavirus24_awa18:01
*** evgenyf has joined #openstack-meeting-318:03
*** julim has quit IRC18:03
*** julim has joined #openstack-meeting-318:07
*** alexpilotti has quit IRC18:07
*** alexpilo_ has joined #openstack-meeting-318:07
*** FallenPegasus has quit IRC18:10
*** ajmiller_ is now known as ajmiller18:11
*** rmoe has quit IRC18:11
*** rmoe has joined #openstack-meeting-318:11
*** dedery has joined #openstack-meeting-318:14
*** dedery_ has joined #openstack-meeting-318:18
*** dedery has quit IRC18:19
*** alexpilotti has joined #openstack-meeting-318:19
*** alexpilo_ has quit IRC18:20
*** jtomasek has quit IRC18:21
*** dconde has joined #openstack-meeting-318:22
*** belmoreira has quit IRC18:23
*** dconde has quit IRC18:25
*** tej is now known as toddjohn_18:27
*** lpetrut has quit IRC18:29
*** Poornima has quit IRC18:30
*** neelashah has quit IRC18:33
*** jmckind_ has quit IRC18:41
*** betherly has joined #openstack-meeting-318:42
*** cloudtrainme has joined #openstack-meeting-318:42
*** irenab_ has joined #openstack-meeting-318:42
*** alexpilotti has quit IRC18:43
*** alexpilotti has joined #openstack-meeting-318:43
*** irenab has quit IRC18:44
*** irenab_ is now known as irenab18:44
*** spzala has quit IRC18:46
*** spzala has joined #openstack-meeting-318:46
*** irenab_ has joined #openstack-meeting-318:48
*** mrmartin has joined #openstack-meeting-318:48
*** yamamoto has joined #openstack-meeting-318:50
*** irenab has quit IRC18:50
*** irenab_ is now known as irenab18:50
*** Aish has joined #openstack-meeting-318:51
*** rtheis has joined #openstack-meeting-318:53
*** sdake has quit IRC18:55
*** ivar-lazzaro has joined #openstack-meeting-318:56
*** yamamoto has quit IRC18:56
*** toddjohn_ has quit IRC18:56
*** toddjohn_ has joined #openstack-meeting-318:59
*** jmckind has joined #openstack-meeting-319:01
*** evgenyf has quit IRC19:03
*** neelashah has joined #openstack-meeting-319:04
*** lpetrut has joined #openstack-meeting-319:08
*** sdake has joined #openstack-meeting-319:09
*** Sukhdev has joined #openstack-meeting-319:10
*** neelashah has quit IRC19:10
*** sigmavirus24_awa is now known as sigmavirus2419:11
*** neelashah has joined #openstack-meeting-319:14
*** mrmartin has quit IRC19:14
*** FallenPegasus has joined #openstack-meeting-319:19
*** belmoreira has joined #openstack-meeting-319:20
*** irenab_ has joined #openstack-meeting-319:23
*** irenab has quit IRC19:25
*** evgenyf has joined #openstack-meeting-319:25
*** irenab has joined #openstack-meeting-319:26
*** irenab_ has quit IRC19:28
*** claudiub|2 has joined #openstack-meeting-319:28
*** ddieterly has quit IRC19:31
*** irenab has quit IRC19:39
*** rockyg has joined #openstack-meeting-319:39
*** fawadkhaliq has quit IRC19:40
*** iyamahat has quit IRC19:40
*** irenab has joined #openstack-meeting-319:41
*** yamahata has quit IRC19:41
*** rtheis has quit IRC19:42
*** rtheis has joined #openstack-meeting-319:43
*** toddjohn_ has quit IRC19:44
*** toddjohn_ has joined #openstack-meeting-319:45
*** rtheis has quit IRC19:47
*** dslevin has left #openstack-meeting-319:49
*** songole has joined #openstack-meeting-319:49
*** songole has quit IRC19:50
*** neelashah1 has joined #openstack-meeting-319:51
*** qwebirc89236 has joined #openstack-meeting-319:51
*** rtheis has joined #openstack-meeting-319:51
*** qwebirc89236 has quit IRC19:52
*** neelashah has quit IRC19:53
*** bklei has quit IRC19:54
*** cloudtrainme has quit IRC19:54
*** rtheis has quit IRC19:56
*** rtheis has joined #openstack-meeting-319:56
*** neelashah has joined #openstack-meeting-319:57
*** ducttape_ has joined #openstack-meeting-319:58
*** neelashah1 has quit IRC19:58
*** alexpilotti has quit IRC19:58
*** irenab_ has joined #openstack-meeting-319:58
*** irenab has quit IRC19:59
*** irenab_ is now known as irenab19:59
*** neelashah1 has joined #openstack-meeting-320:00
*** rtheis has quit IRC20:01
*** alexpilotti has joined #openstack-meeting-320:01
*** alexpilotti has quit IRC20:01
*** neelashah has quit IRC20:01
*** hurgleburgler17 has joined #openstack-meeting-320:02
*** irenab has quit IRC20:02
*** irenab has joined #openstack-meeting-320:04
*** ivar-lazzaro has quit IRC20:05
*** dedery_ has quit IRC20:05
*** dslevin has joined #openstack-meeting-320:06
*** dslevin has quit IRC20:06
*** dslevin has joined #openstack-meeting-320:07
*** dslevin has quit IRC20:07
*** alexpilotti has joined #openstack-meeting-320:08
*** jmckind has quit IRC20:08
*** tsufiev_ has joined #openstack-meeting-320:08
*** dslevin has joined #openstack-meeting-320:08
*** jmckind has joined #openstack-meeting-320:08
*** dslevin has quit IRC20:09
*** dslevin has joined #openstack-meeting-320:09
*** dslevin has quit IRC20:09
*** dslevin has joined #openstack-meeting-320:11
*** alexpilotti has quit IRC20:12
*** rhagarty_ has quit IRC20:16
*** rhagarty_ has joined #openstack-meeting-320:16
*** alexpilotti has joined #openstack-meeting-320:17
*** neiljerram has quit IRC20:18
*** iyamahat has joined #openstack-meeting-320:20
*** toddjohn_ has quit IRC20:21
*** ivar-lazzaro has joined #openstack-meeting-320:22
*** irenab_ has joined #openstack-meeting-320:24
*** irenab has quit IRC20:25
*** irenab_ is now known as irenab20:25
*** iyamahat has quit IRC20:26
*** irenab_ has joined #openstack-meeting-320:30
*** irenab has quit IRC20:32
*** irenab_ is now known as irenab20:32
*** FallenPegasus has quit IRC20:33
*** kzaitsev_mb has joined #openstack-meeting-320:35
*** alexpilotti has quit IRC20:36
*** jmckind has quit IRC20:37
*** dtardivel has quit IRC20:38
*** spzala has quit IRC20:40
*** hurgleburgler17 has quit IRC20:43
*** cloudtrainme has joined #openstack-meeting-320:45
*** ihrachys has joined #openstack-meeting-320:47
*** Sukhdev has quit IRC20:48
*** belmoreira has quit IRC20:53
*** alaski has joined #openstack-meeting-320:55
*** iyamahat has joined #openstack-meeting-320:56
*** mriedem has joined #openstack-meeting-320:59
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed Feb 24 21:00:14 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
mriedemo/21:00
doffmo/21:00
alaskicool, let's get going21:00
melwitto/21:00
*** piet has quit IRC21:00
alaski#topic Testing21:00
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"21:00
alaskiany news on this front?21:00
mriedemccarmack isn't here21:01
alaskiokay21:01
alaskihe has a +2 and -1 on his review21:01
alaskibut seems to be moving forward21:02
mriedemidk21:02
alaskiI'll have to look at the objections after this to see what's up21:02
alaski#topic Open Reviews21:02
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:02
alaskihttps://etherpad.openstack.org/p/mitaka-nova-priorities-tracking as always21:02
alaskitake a peek in there at some point21:03
alaski#topic Open Discussion21:03
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:03
mriedemon reviews21:03
mriedem...21:03
*** mlavalle has joined #openstack-meeting-321:03
mriedemfor the flavor db thing,21:03
alaski#undo21:03
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xaf5f690>21:03
mriedemwe were waiting on that root_gb flavor spec21:03
mriedemdid that move forward at all?21:03
alaskinot yet21:04
doffmmriedem: Which spec?21:04
alaskiI don't expect much from the spec until N is open though21:04
*** ducttape_ has quit IRC21:04
alaskidoffm: https://review.openstack.org/#/c/267673/21:04
mriedemdoffm: https://review.openstack.org/#/c/267673/21:04
mriedemdamn!21:04
mriedemlaski21:04
alaskiheh21:04
mriedemwell,21:04
mriedemdo we want to land the flavors tables things in mitaka?21:04
mriedemif we want to punt,21:04
mriedemwe leave root_gb nullable=True21:05
*** evgenyf has quit IRC21:05
alaskiright, I think that's what we do for now21:05
mriedemwe could always make it non-nullable with  a migration later21:05
alaskiI can comment on the flavor table review with that21:05
alaskibut if there's no opposition I think that leaves us the most options for now21:05
*** rtheis has joined #openstack-meeting-321:06
alaski#topic Open Discussion21:06
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:06
mriedemi did21:06
doffmmriedem: We added something about Neutron?21:06
mriedemdoffm: i did21:07
alaskimriedem: great21:07
mriedemi do it all!21:07
doffmBwahhahah.21:07
melwittI have a couple of things I wanted to ask21:07
alaskiokay21:07
alaskilet's start with mriedem21:07
melwittone is for the CellMapping, do we want to consider making transport_url nullable or will cell0 be a special thing where it sets it as empty string and we make our code know not to switch mq in that case?21:08
melwittoops sorry21:08
mriedemi don't have the agenda sitting in front of me21:08
mriedemalaski: want to just paste the question21:08
alaskimriedem: sure, but you're at the back of the line now21:08
doffmmelwitt: The latter option is what I'm assuming right now.21:08
doffmmelwitt: But if you are opposed...21:08
alaskiyeah, the latter option seemed fine with me21:09
melwittI don't have a strong opinion either way but wanted to see if anyone else had wondered about nullable as a way21:09
melwittbecause what that means is CellMapping must have a transport_url to make sense. except cell021:09
melwitt(non-nullable means that)21:10
mriedemif it's non-nullable i guess you set a sentinel value21:10
*** pcaruana has quit IRC21:10
doffmmriedem: Thats what we are doing now.21:10
mriedemif mapping.transport_url == 'special-unicorn': do x21:10
alaskimelwitt: my thinking was that we would know not to attempt an RPC call if the instance was in cell0. I guess it depends on where we want to have that check21:11
doffmUnicorn = none:///21:11
alaskishould we check for cell0 before attempting RPC, or have RPC raise an exception if cell0?21:11
mriedemwouldn't the latter be more performant?21:12
melwittalaski: I was imagining access to the instance is inside the with statement for the "target_cell" and then "if not transport_url: no-op" or something?21:12
* mriedem actually has no idea what this whole discussion is about so should shut up21:12
melwittalaski: the check being inside the target_cell call21:13
alaskimriedem: it's the same lookups either way, just about where the if statement goes21:13
melwittmy other topic was, the potential oslo.messaging function we could write that assembles a transport_url from the various opts to various rpc backends21:13
doffmI was imagining that if transport_url=unicorn, don't create or switch transport. Then later we could add something more complicated to check if transport is used to cell0. Create a transport that emits warnins.21:13
*** ivar-lazzaro has quit IRC21:14
doffmmelwitt: I'd like to do that.21:14
doffmOr someone do it.21:14
doffmI think its generally useful.21:14
doffmEspecially for our nova-manage commands.21:14
alaskithe reason I leaned towards a unicorn transport is that if for some reason it does get passed to oslo.messaging hopefully it would fail gracefully, not blowup like None might do21:15
alaskidoffm: +121:15
melwittdoffm: sounds good to me21:15
doffmOk.21:15
melwittthat's it from me, sorry for cutting in line21:16
doffmmriedem? We are at the neutron-midcycle so we have some updates from there.21:16
alaskiheh, mriedem didn't have his papers in order21:17
doffmWe discussed cells.21:17
alaskiI think we're still open on the unicorn transport vs None thing21:17
*** ihrachys has quit IRC21:17
doffm* goes to the back of the line. :)21:17
*** iyamahat has quit IRC21:17
melwittalaski: well, it can't be None I think because non-nullable. so empty string vs sentinel?21:17
melwittalaski: or am I wrong on what nullable means.. I get confused21:18
alaskiwe could make it nullable21:18
* bauzas waves late21:18
alaskino, you're right on that21:18
alaskiI would prefer None or sentinel21:18
alaskiand sentinel works without a further migration21:19
doffmI'd prefer sentinel. Because it will parse the oslo.messaging Transport stuff.21:19
melwittokay, so None is not a valid value for a non-nullable field. is that right?21:19
alaskimelwitt: right21:19
*** lpetrut has quit IRC21:19
mriedemalaski: technically my thing is last in open discussion21:19
mriedemit's not really mine either, more from armax21:20
mriedemi'm just a proxy21:20
alaskidoffm: I agree21:20
alaskimelwitt: are you okay with the sentinel or do you have an argument for None21:20
melwittyeah, I think the main thing is I wouldn't want to make transport_url nullable for just one case21:22
melwittwhen for everything except cell0 a CellMapping absolutely has to have a transport_url21:22
alaskiyeah21:22
alaskiokay. if you change your mind let doffm know with an angry -1 on his patch21:23
melwitthaha21:23
alaskidoffm: sorry, your turn21:23
doffmI guess just an update from the neutron meetup.21:23
alaskigreat21:24
doffmWe briefly discussed `routed networks` and `resource pools` as a scaling solution.21:24
doffmThe general opinion was that that is an option, but only deals with data-plane scaling.21:24
alaskiyeah21:25
doffmSomething like `cells` for neutron could work for control-plane scaling.21:25
doffmAnd we agreed to .... have some talks about that in the future.21:25
alaskiheh, sounds good21:25
alaskiis that a nebulous future or are there ideas on when/where?21:25
mriedemi think armax is just curious to be in the loop on any requirements for neutron21:25
mriedemso it's not a surprise to them later21:25
mriedemor what the recommended deployment with cells v2 + neutron is going to be21:26
doffmalaski: I could try to do it this week, but we will see.21:26
doffmYeah he wanted more deployment docs, earlier rather than later.21:26
alaskiokay21:26
mriedemso,21:26
mriedemi don't know if that could fit into the upgrade doc?21:27
*** salv-orl_ has joined #openstack-meeting-321:27
mriedemor something separate,21:27
mlavallealaski: is your concern mostly the data plane?21:27
mriedemlike, with cells v2 this is how we think thinks will work for networking21:27
mriedem*things21:27
alaskiright now there are no requirements for neutron, but with multiple cells the use cases that CERN/Rackspace/GoDaddy have about network partitioning will come up21:27
mlavallealaski: that was the assumption it was made in the neutron mid-cycle21:27
mriedemalaski: maybe just having their use cases doc'ed somewhere would be helpful?21:28
mriedemidk21:28
alaskimlavalle: yes, that's where current deployers have faced scaling issues21:28
alaskimlavalle: well, mostly. but they've overcome control plane issues21:28
mlavallealaski: we think that routed networks will help with the data plane issues21:29
alaskimriedem: that's a great idea21:29
alaskimlavalle: that's my hope as well21:29
mriedemalaski: is it also a great idea if you doc those? :P21:29
mriedemb/c i don't know the details21:29
*** salv-orlando has quit IRC21:29
mriedemor we could ask those guys to doc them in an etherpad21:29
mriedemand we distill that into somtehing else21:29
doffmmlavalle: Want to help out with the routed networks docs for that?21:30
alaskiheh, I don't either(just some about rax). But I can reach out to people to ask them to write some things21:30
mlavallealaski: I am part of that effort. and i'll continue attending this meeting, a cocnluesion is reached that we need to tackle also from the control plane21:30
mlavalledoffm: yeah21:30
alaskimriedem: +1. I'd like to get everyone to doc it in their own words21:30
alaskithen distill21:30
mriedem#action get CERN/Rackspace/GoDaddy to doc their cells + networking use cases somewhere (etherpad most likely)21:30
mriedemi can poke people21:31
alaskiokay, you know who at each place?21:31
*** cloudtrainme has quit IRC21:31
mriedemklindgren at godaddy, belmoria at cern, you at rax :)21:31
mriedemi don't know a specific rax networking person21:32
alaskihah, close enough for now21:32
alaskitbh I don't know either right now21:32
alaskijohnthetubaguy might21:32
alaskiI would've said mlavalle not too long ago21:32
mriedemi'll also post to the ops list21:32
mlavallealaski: in RAX, ping Ryan Clevenger (clev)21:33
mriedemand poke some specific people21:33
alaskimlavalle: great, thanks21:33
mlavallealaski: clev doesn't know, but the people who know work for him21:33
mlavallealaski: most likely, ahill21:33
alaskimlavalle: for control plane scaling I would love to be involved in any conversations on the Neutron side. But I also think we can keep those details hidden from Nova, and just rely on routed networks for coordination21:34
*** ekarlso- has quit IRC21:34
*** ekarlso- has joined #openstack-meeting-321:34
mlavallealaski: there is no scaling up work taking place in Neutron's control plane right now21:34
doffmmlavalle: Get together with russellb to discuss control plane scaling this week?21:35
mriedemhttps://etherpad.openstack.org/p/cells-networking-use-cases21:35
mlavallealaski: what I meant earlier is that I am working on Routed Networks and I will monitor your work on Nova side, in case we need to re-visit on the Neutron side21:35
alaski#link https://etherpad.openstack.org/p/cells-networking-use-cases21:35
alaskimlavalle: okay21:36
alaskithat was essentially your agenda item right mriedem?21:37
mriedemyeah21:37
alaskicool21:37
alaskianything else today?21:37
mriedemthere were other things in the agenda21:37
mriedemdb migrations and summit talks21:37
mriedemor are those old?21:37
alaskithey're old21:37
alaskidoffm: you mentioned some specs yesterday21:38
bauzasI guess that we'll be calling the wrap due to FF next week ?21:38
mriedembauzas: i hope so :)21:38
bauzasso I'd like to know which changes are really prio21:38
mriedemwe can get the flavors db thing in this week21:38
bauzasfor Mitaka I mean21:38
doffmalaski: I did, but I don't have those specs finished. Might as well discuss when they are. I'm working on db migrations specs for Newton.21:38
mriedemi don't know the other changes21:38
alaskibauzas: start here https://review.openstack.org/#/c/263926/11 :)21:38
alaskidoffm: okay21:38
*** cloudtrainme has joined #openstack-meeting-321:38
bauzasmriedem: I saw the convo by scrollbacking21:38
bauzasmriedem: so the consensus is to not wait for the flavor spec ?21:39
bauzasalaski: ack, right in my pipe21:39
mriedembauzas: we're going to mark root_gb as nullable=True21:39
mriedembauzas: we're going to punt on the decision21:39
mriedemdoffm can update the patch and i'll +221:39
bauzasokay, I should read the logs carefully21:39
alaskibauzas: flavor db migration, nova-manage changes, and my series. I think those are the prio unless I'm forgetting something21:39
bauzasokay, nice21:39
doffmmriedem: Hokay.21:39
bauzasalaski: okay, we can sprint those21:40
*** iyamahat has joined #openstack-meeting-321:40
alaskithis does remind me. after FF we'll probably want to back off to less regular meetings while RC1 is being worked21:41
*** krtaylor has quit IRC21:41
bauzasfair point21:41
bauzasRC1 will probably take me a lot of time21:41
alaskidoffm: mriedem last cycle we went to every other week due to the slowdown that occurs21:42
alaskibecause outside of some specs and summit prep not much happens21:42
doffmSounds good.21:42
mriedemyeah21:42
mriedemops email sent for networking21:42
*** iyamahat has quit IRC21:42
mriedemklindgren pinged21:42
mriedemmy job is done21:42
alaskiwe'll workout the weeks and timeslot when FF hits21:42
alaskimriedem: excellent work21:43
alaskianything else?21:43
*** iyamahat has joined #openstack-meeting-321:43
mriedemnope21:43
doffmNo.21:43
alaskigreat21:43
alaskiI can go watch for the tornadoes supposedly headed this way21:43
alaskithanks all!21:43
doffmThanks.21:43
alaski#endmeeting21:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:43
openstackMeeting ended Wed Feb 24 21:43:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-24-21.00.html21:43
*** mriedem has left #openstack-meeting-321:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-24-21.00.txt21:43
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-24-21.00.log.html21:43
*** bpokorny has quit IRC21:45
*** cloudtrainme has quit IRC21:48
*** sdake has quit IRC21:51
*** sdake has joined #openstack-meeting-321:52
*** Sukhdev has joined #openstack-meeting-321:54
*** krtaylor has joined #openstack-meeting-321:55
*** reedip_ has quit IRC21:56
*** banix has quit IRC21:57
*** ivar-lazzaro has joined #openstack-meeting-321:57
*** ivar-lazzaro has quit IRC21:58
*** ivar-lazzaro has joined #openstack-meeting-322:03
*** Sukhdev has quit IRC22:03
*** sdake has quit IRC22:13
*** Sukhdev has joined #openstack-meeting-322:14
*** dims has quit IRC22:14
*** lblanchard has quit IRC22:14
*** shwetaap1 has joined #openstack-meeting-322:14
*** iyamahat has quit IRC22:16
*** Sukhdev has quit IRC22:17
*** kzaitsev_mb has quit IRC22:17
*** ivar-lazzaro has quit IRC22:17
*** ifat_afek has joined #openstack-meeting-322:17
*** Sukhdev has joined #openstack-meeting-322:17
*** spzala has joined #openstack-meeting-322:18
*** shwetaap has quit IRC22:19
*** spzala has quit IRC22:20
*** neelashah1 has quit IRC22:25
*** Sukhdev has quit IRC22:29
*** bpokorny has joined #openstack-meeting-322:32
*** julim has quit IRC22:33
*** cbouch has quit IRC22:37
*** vishwana_ is now known as vishwanathj22:39
*** rtheis has quit IRC22:42
*** ifat_afek has quit IRC22:43
*** rtheis has joined #openstack-meeting-322:45
*** safchain has joined #openstack-meeting-322:48
*** sigmavirus24 is now known as sigmavirus24_awa22:54
*** safchain has quit IRC23:03
*** claudiub|2 has quit IRC23:05
*** dims has joined #openstack-meeting-323:08
*** yamamoto_ has joined #openstack-meeting-323:08
*** sdake has joined #openstack-meeting-323:12
*** Sukhdev has joined #openstack-meeting-323:15
*** rockyg has quit IRC23:16
*** rtheis has quit IRC23:16
*** rtheis has joined #openstack-meeting-323:16
*** rtheis has quit IRC23:17
*** rtheis has joined #openstack-meeting-323:17
*** rtheis has quit IRC23:17
*** mlavalle has left #openstack-meeting-323:20
*** Swami has quit IRC23:24
*** sdake has quit IRC23:25
*** armax has quit IRC23:27
*** armax has joined #openstack-meeting-323:28
*** armax has quit IRC23:28
*** dimtruck is now known as zz_dimtruck23:28
*** hichihara has joined #openstack-meeting-323:28
*** haleyb has quit IRC23:30
*** mestery has quit IRC23:30
*** cloudtrainme has joined #openstack-meeting-323:31
*** shwetaap1 has quit IRC23:32
*** toddjohn_ has joined #openstack-meeting-323:35
*** mestery has joined #openstack-meeting-323:35
*** safchain has joined #openstack-meeting-323:36
*** kzaitsev_mb has joined #openstack-meeting-323:38
*** yamamoto_ has quit IRC23:38
*** toddjohn_ has quit IRC23:39
*** iyamahat has joined #openstack-meeting-323:48
*** rbak has quit IRC23:59
*** safchain has quit IRC23:59

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