Wednesday, 2016-05-18

*** kzaitsev_mb has quit IRC00:00
*** kzaitsev_mb has joined #openstack-meeting-300:04
*** kzaitsev_mb has quit IRC00:12
*** salv-orlando has joined #openstack-meeting-300:14
*** kzaitsev_mb has joined #openstack-meeting-300:25
*** piet has quit IRC00:27
*** cloudtra_ has quit IRC00:29
*** hoangcx has joined #openstack-meeting-300:30
*** hoangcx has left #openstack-meeting-300:30
*** armax_ has joined #openstack-meeting-300:31
*** piet has joined #openstack-meeting-300:32
*** armax has quit IRC00:33
*** armax_ is now known as armax00:33
*** donghao has quit IRC00:34
*** salv-orlando has quit IRC00:36
*** bpokorny has quit IRC00:36
*** kzaitsev_mb has quit IRC00:38
*** kzaitsev_mb has joined #openstack-meeting-300:42
*** aliadil has joined #openstack-meeting-300:43
*** ajnouri has joined #openstack-meeting-300:45
*** baoli has joined #openstack-meeting-300:46
*** kzaitsev_mb has quit IRC00:49
*** ivar-lazzaro has joined #openstack-meeting-300:55
*** piet has quit IRC00:55
*** hoangcx has joined #openstack-meeting-300:57
*** dimtruck is now known as zz_dimtruck01:00
*** mtanino has quit IRC01:00
*** aliadil has quit IRC01:01
*** banix has quit IRC01:02
*** mickeys has joined #openstack-meeting-301:03
*** armax has quit IRC01:07
*** ivar-lazzaro has quit IRC01:11
*** donghao has joined #openstack-meeting-301:12
*** ivar-lazzaro has joined #openstack-meeting-301:15
*** pvaneck has quit IRC01:18
*** salv-orlando has joined #openstack-meeting-301:18
*** ajmiller has quit IRC01:25
*** zz_dimtruck is now known as dimtruck01:28
*** ivar-lazzaro has quit IRC01:32
*** stanzgy has joined #openstack-meeting-301:34
*** armax has joined #openstack-meeting-301:34
*** yamahata has quit IRC01:34
*** iyamahat_ has quit IRC01:35
*** salv-orlando has quit IRC01:36
*** banix has joined #openstack-meeting-301:37
*** kzaitsev_mb has joined #openstack-meeting-301:38
*** kzaitsev_mb has quit IRC01:43
*** mickeys has quit IRC01:51
*** reedip__ has joined #openstack-meeting-301:53
*** s3wong has quit IRC01:53
*** tfukushima has joined #openstack-meeting-301:58
*** iyamahat_ has joined #openstack-meeting-302:04
*** bpokorny has joined #openstack-meeting-302:06
*** sdake has quit IRC02:06
*** salv-orlando has joined #openstack-meeting-302:12
*** sdake has joined #openstack-meeting-302:12
*** bpokorny_ has joined #openstack-meeting-302:14
*** zhurong has joined #openstack-meeting-302:16
*** bpokorny has quit IRC02:18
*** bpokorny_ has quit IRC02:19
*** sdake has quit IRC02:22
*** rossella_s has quit IRC02:23
*** rossella_s has joined #openstack-meeting-302:24
*** iyamahat_ has quit IRC02:24
*** salv-orlando has quit IRC02:32
*** toddjohn_ has joined #openstack-meeting-302:48
*** toddjohn_ has quit IRC02:53
*** baoli has quit IRC02:57
*** dimtruck is now known as zz_dimtruck02:58
*** iyamahat_ has joined #openstack-meeting-302:59
*** vishwanathj has quit IRC03:05
*** salv-orlando has joined #openstack-meeting-303:05
*** sdake has joined #openstack-meeting-303:09
*** tfukushima has quit IRC03:12
*** zz_dimtruck is now known as dimtruck03:14
*** dimtruck is now known as zz_dimtruck03:16
*** iyamahat_ has quit IRC03:17
*** iyamahat_ has joined #openstack-meeting-303:18
*** zz_dimtruck is now known as dimtruck03:18
*** coolsvap has joined #openstack-meeting-303:22
*** iyamahat_ has quit IRC03:24
*** salv-orlando has quit IRC03:28
*** sdake_ has joined #openstack-meeting-303:37
*** sdake has quit IRC03:40
*** mickeys has joined #openstack-meeting-303:51
*** piet has joined #openstack-meeting-303:53
*** njohnston-- is now known as njohnston__03:54
*** SridarK_ has joined #openstack-meeting-303:55
*** Poornima has joined #openstack-meeting-303:55
*** yushiro has joined #openstack-meeting-303:56
*** njohnston__ has quit IRC03:56
*** mickeys has quit IRC03:56
*** njohnston__ has joined #openstack-meeting-303:57
*** sdake_ has quit IRC03:58
*** chandanc has joined #openstack-meeting-303:58
*** armax has quit IRC03:59
*** mickeys has joined #openstack-meeting-304:00
SridarK_Hi FWaaS folks04:00
yushiroHi, good evening :)04:00
njohnston__#startmeeting fwaas04:00
openstackMeeting started Wed May 18 04:00:28 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston__. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
njohnston__#chair sridark04:00
openstackWarning: Nick not in channel: sridark04:00
openstackCurrent chairs: njohnston__ sridark04:00
njohnston__#chair xgerman04:00
openstackCurrent chairs: njohnston__ sridark xgerman04:00
SridarK_Hi All04:00
*** padkrish has joined #openstack-meeting-304:01
SridarK_thanks for joining and special thanks to njohnston__ , mfranc213 & shweta for accomodating a really late time on the US East coast04:01
SridarK_njohnston__: thanks for setting up the agenda04:01
SridarK_on the etherpad04:01
njohnston__Sure thing!04:01
SridarK_lets run thru things quickly and we can try to go quickly04:02
njohnston__sounds good04:02
SridarK_#topic Unbreaking FWaaS04:02
SridarK_njohnston__: could u pls set my IRC handle on the chair04:03
njohnston__Ah, sorry!  I didn;t notice the underscore04:03
njohnston__#chair SridarK_04:03
openstackCurrent chairs: SridarK_ njohnston__ sridark xgerman04:03
SridarK_#topic Unbreaking FWaaS04:03
*** openstack changes topic to "Unbreaking FWaaS (Meeting topic: fwaas)"04:03
SridarK_thx njohnston__04:03
*** pgadiya has joined #openstack-meeting-304:04
SridarK_so quick update on this - over last week - some events -quick recap04:04
SridarK_some of us made it out to the L3 team mtg and then subsequently the drivers mtg04:04
*** salv-orlando has joined #openstack-meeting-304:05
SridarK_we discussed #link
openstackLaunchpad bug 1580239 in neutron "[RFE] Add agent extension framework for L3 agent" [Wishlist,In progress] - Assigned to Nate Johnston (nate-johnston)04:05
SridarK_as an RFE for adding the right extensions to support service agents in L3 Agent04:05
SridarK_we have gotten support on this in the drivers mtg and has been approved04:06
njohnston__Please feel free to contribute to the RFE as well, where you see gaps.04:06
SridarK_we did bring up the issues on the breakage and got a quick workaround proposal from armax04:06
njohnston__praise be to armax :-)04:07
SridarK_essentially this is a fork of L3Agent with FWaaS on it - and should be enough to make some fwd progress04:07
*** iyamahat_ has joined #openstack-meeting-304:07
mfranc213SridarK_ I think you had some follow-up questions for armax on this.04:08
SridarK_for some reason even with the workflow - this did not merge - also had some queries for armax on things that are remaining04:08
SridarK_mfranc213: +104:08
SridarK_i had to be out so will follow up on this tomorrow04:08
SridarK_hopefully we can get this merged - even if there are limitations we would be in better shape04:09
SridarK_folks request to take a look at the patch too and see if there are things we need to fix - possibly as subsequent patches04:09
xgermanmmh,we tried recheck?04:09
*** sdake has joined #openstack-meeting-304:09
SridarK_tempest was happy and i also pulled a devstack and tested it04:09
SridarK_xgerman: i was waiting to wait to hear back on my questions to armax as well04:10
xgermanok, will remove my +W then04:10
SridarK_it almost seemed like it did not get queued to the pipeline at all04:10
SridarK_xgerman: ok - i am hoping we can merge this soon04:11
SridarK_Thanks to armax for a quick possible path fwd04:11
xgermanyeah, if you are waiting for an answer it’s probably best not to +W04:12
SridarK_yes i think he added a comment after u +W - so yes best to remove and wait04:12
SridarK_* ur +W04:12
SridarK_thx to njohnston__ for getting the bug filed and starting out the spec patch04:13
njohnston__no time like the present!04:13
mfranc213i think the L3 spec will be fleshed out considerably the more we understand the L2 agent extension implementation04:14
SridarK_thx are definitely looking better this week (i hope i dont jinx anything by saying that)04:14
SridarK_mfranc213: +104:14
SridarK_We could spend some time on going thru some sample workflows04:15
mfranc213can you say more?04:15
SridarK_and then compare that with the QoS work04:15
mfranc213when i have completed some other word for Comcast, my first task is to study the L2 QoS code more04:16
njohnston__we may need to modify the l2 agent extension04:16
mfranc213(for a few fwaas-related purposes)04:16
njohnston__at present it is intended to only make certain specific resources available04:16
xgermanyep, but we can add our fawns resources without changes according to dogwig04:17
mfranc213poor dogwig04:17
SridarK_what we really need on the L3 agent - is to be able to get access to the router info04:17
SridarK_so we can map router ids to namespaces04:17
mfranc213there were two things, right?04:17
yushiroSridarK_, How about 'router_port_id'? Can we also get this information by using L3 extension?04:19
SridarK_mfranc213: yes we can use the existing observer hierarchy for notifications04:19
mfranc213thank you04:19
SridarK_yushiro: router_port_id - we will get from the plugin04:19
SridarK_yushiro:  and we can map the ns for the router that owns that port04:20
njohnston__according to carl_baldwin, they don't use the term 'observer hierarchy' any more, they just call it a callback mechanism... but FYI there may be mines in that field, he said there were a number of bits left unimplemented04:20
SridarK_njohnston__: true, agreed04:21
yushiroSridarK_, I see. thanks.04:21
SridarK_njohnston__: if u think it makes sense - we can get the interested folks on a call for some discussions too04:21
SridarK_other thing on this topic folks would like to discuss ?04:23
njohnston__let's quiz the right folks on irc to start04:23
*** zhurong has quit IRC04:23
*** SarathChandraMek has joined #openstack-meeting-304:23
SridarK_njohnston__: sounds good whichever is easier04:24
*** iyamahat_ has quit IRC04:24
SridarK_Sorry i think i globbed multiple agenda topics on to this - but they are related04:25
*** salv-orlando has quit IRC04:25
mfranc213yep, they are! :)04:25
SridarK_#topic Observer Hierarchy04:26
*** openstack changes topic to "Observer Hierarchy (Meeting topic: fwaas)"04:26
*** amotoki has quit IRC04:26
SridarK_njohnston__: i know u asked for some more clarity - i will ping the contributor too04:26
*** amotoki has joined #openstack-meeting-304:26
*** pgadiya is now known as pgadiya|OSPBootc04:26
SridarK_i was thinking if he can make the patch dependent on the workaround patch and do some testing04:27
SridarK_then we can get a quick turnaround on this04:27
*** muawiakhan has joined #openstack-meeting-304:27
SridarK_#action SridarK_ to reach out to Bharath on Observer Hierarchy04:28
SridarK_Ok moving on04:28
SridarK_sorry pls go ahead mfranc21304:28
*** dimtruck is now known as zz_dimtruck04:29
mfranc213can you quickly say what the relationship is/might be between the observer hierachy and neutron's L2 RPC callback implementation?04:29
mfranc213"relationship" is the wrong word04:29
*** muawiakh_ has joined #openstack-meeting-304:29
mfranc213i mean: how they may or may not overlap functionally or architecturally04:29
SridarK_mfranc213: this is the callback on L3 Agent on router events04:30
*** yamamoto has quit IRC04:30
mfranc213yes, so the objects differ...04:30
SridarK_consumers (like fwaas) can register a call back and on router events - will get the callback to handle the event04:30
mfranc213but are the general approaches similar or the same, and if not, should they be?04:30
mfranc213SridarK_ yes, that sounds like the RPC callback implementation for L2 ;)04:31
SridarK_i dont know enough abt the L2 callbacks - but i think the idea is similar04:31
mfranc213at least at a high level04:31
SridarK_mfranc213: yes it seems so04:31
mfranc213so is there merit to stealing code?04:31
mfranc213or is the observer hierarchy close to being done?04:31
SridarK_mfranc213: shamelessly yes :-)04:31
SridarK_mfranc213: but i think it is mostly done04:32
mfranc213okay, thank you.04:32
SridarK_mfranc213: no prob thx for asking04:32
SridarK_ok then lets move on04:32
njohnston__"shamelessly" lol04:32
padkrishmfranc213, sridarK_: I am not sure or atleast i don't understand it yet, that L2 agent RPC is that way04:32
padkrishhopefully will get to the bottom of it in a day04:33
SridarK_padkrish: ok great04:33
*** muawiakhan has quit IRC04:33
SridarK_#topic SG changes in neutron04:34
*** openstack changes topic to "SG changes in neutron (Meeting topic: fwaas)"04:34
SridarK_mickeys: were u able to get some cycles on this04:35
mfranc213is this topic essentially the L2 FWaaS (i.e., port-level) functionality?04:35
mickeysThis is making changes to security groups so that L2 FWaaS can coexist with security groups on the same port04:35
SridarK_mfranc213: mickeys was looking at some neutron changes to clean things up so we can land our L2 stuff04:35
mickeysTwo separate issues04:35
mfranc213thank you04:35
njohnston__mfranc213: This is the topic with the wrapped chain versus the unwrapped chain that we talked about in the summit04:35
mfranc213excellent.  thanks for the clarification.04:36
mickeysOne is having a common chain that both security groups and fwaas can go off of to jump to interface specific chains. The ACCEPT needs to be in the common chain.04:36
mickeysI have not started on that, and it does not look like I will get any cycles for that in the next week.04:36
mickeysThe other is conntrack, moving some stuff into the conntrack part of security groups that sits in the base security groups firewall driver right now04:37
mickeysWe need access to common conntrack zone mappings for both security groups and fwaas04:37
xgermanI thought we could just use the same contrack...04:37
xgermanmickeys +104:37
mickeysThe mapping of interface to conntrack zones sits in the iptables-firewall security groups driver right now.04:37
mickeysWe want the mapping to be in the conntrack part, then make that conntrack part a singleton04:38
xgermanyep, those are neutron changes? Do we need an RfE?04:38
njohnston__there should at least be a bug, if there isn't one already04:39
mickeysBugs have not been opened yet04:39
mickeysAs RFEs?04:39
njohnston__Open it as a regular bug and let them come back and say "this looks big enough to merit an RFE"04:40
njohnston__My opinion, it isn't big enough to need an RFE but that's just me.04:41
SridarK_mickeys: perhaps as njohnston__ suggests, u can then bring it up for discussion in the drivers mtg if needed04:41
njohnston__if you want it discussed there, add the rfe tag and leave it in triaged state04:42
mickeysFor the conntrack part, it is moving some code from to and then making a singleton04:42
xgermanmy worry is that they have ideas they like us to follow...04:42
xgermanyeah, it’s straight forward but having it blessed might be good anyway04:43
mickeysFor the ip_conntrack piece, I don't see mcuh room for alternative solutions04:43
njohnston__better safe than sorry I suppose04:43
mickeysFor the piece that messes with iptables chain structures, there may be some discussion04:43
SridarK_getting a bug will atleast get it on the radar04:44
SridarK_sounds good then04:44
*** piet has quit IRC04:44
SridarK_other things folks want to discuss on this ?04:45
SridarK_chandanc: SarathChandraMek: did u guys also want to bring up discussion points or questions ?04:45
chandancSridarK: I am still going through the code in mikeys patch04:45
SarathChandraMekStill catching up..04:46
chandancwill need some time04:46
mickeysLet me know if you want to discuss any of this04:46
SridarK_chandanc: SarathChandraMek: ok that is fair, pls feel free to reach out if u have questions04:46
SarathChandraMeksure.. mickeys we will ping you offline04:46
SridarK_ok lets move on04:47
SridarK_#topic FWaaS V204:48
*** openstack changes topic to "FWaaS V2 (Meeting topic: fwaas)"04:48
SridarK_nothing much but hopefull we can pick things up04:48
mfranc213can you elaborate?04:48
SridarK_njohnston__: mfranc213: do u think we can try to push for a first level integration across Ext - > db -> plugin04:49
njohnston__yes, once armax's fix merges04:49
SridarK_mfranc213: sorry, meant with the workaround patch04:49
SridarK_njohnston__: +104:49
njohnston__then we can have a functioning way forward04:49
njohnston__I am waiting in catlike readiness04:49
SridarK_njohnston__: i know some cycles are getting spun out the L3 Agent refactor04:50
SridarK_but if we get some basic things in place, even if it is a bit hacky, yushiro: & padkrish: can start playing around on the agent pieces04:51
SridarK_ok sounds good - lets plan for that - we can continue discussions over the week04:52
SridarK_other things to discuss on v2 ?04:53
njohnston__I am enjoying the level of consensus04:53
*** dedery has joined #openstack-meeting-304:54
SridarK_njohnston__: as u stated on the agenda 2 weeks from N-104:54
njohnston__time flies when you're having fun :-)04:54
SridarK_we really need to aim to make the next 3 - 4 weeks very productive so we are in a good position for N-204:55
njohnston__completely agreed04:55
SridarK_#topic Open Discussion04:55
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:55
mfranc213there are several open action items on, most of them mine. i'm not allowed to edit the fwaas wiki.  do you know how i can get it?04:56
SridarK_mfranc213: yes u should be able to do it04:56
SridarK_mfranc213: if u have issues - lets sync tomorrow04:56
mfranc213i will ping you offline if i continue to have problems04:56
SridarK_mfranc213: and i believe i had to address some too - thx for the reminder04:56
njohnston__also check out the ML discussion titled 'wiki' - they're talking about how they need to turn off access rights to the wiki because of rampant spamming04:57
njohnston__we may want to move all that kind of stuff to etherpads for the time being04:57
*** zhurong has joined #openstack-meeting-304:57
SridarK_mfranc213: njohnston__ : thats right04:57
SridarK_mfranc213: i can proxy for u too04:57
mfranc213thank you.04:57
*** fawadkhaliq has joined #openstack-meeting-304:57
SridarK_so we can get things in04:57
yushiropadkrish, could you receive my e-mail ?04:58
*** muawiakh_ has quit IRC04:58
SridarK_but perhaps etherpad is the way to go04:58
padkrishyushiro# Yes, replied04:58
xgermantime: -204:58
mfranc213also, it would be helpful for me to know everyone's timezone along with their irc handle (i know some but not all)04:58
*** salv-orlando has joined #openstack-meeting-304:58
*** flwang1 has quit IRC04:58
chandancwill update etherpad04:59
njohnston__we can note those down in perhaps04:59
mfranc213thank you04:59
*** piet has joined #openstack-meeting-304:59
SridarK_ok folks04:59
njohnston__thanks everyone, this was very good04:59
yushiropadkrish, Thanks,04:59
SridarK_thx for joining and the discussion04:59
mfranc213thanks everyone04:59
yushiroThank you.04:59
SridarK_pls feel free to email if u need something04:59
njohnston__...and goodnight05:00
*** openstack changes topic to "OpenStack Meetings ||"05:00
openstackMeeting ended Wed May 18 05:00:05 2016 UTC.  Information about MeetBot at . (v 0.1.4)05:00
xgermangood  night05:00
openstackMinutes (text):
SridarK_Bye all05:00
*** matrohon has joined #openstack-meeting-305:00
*** njohnston__ has quit IRC05:01
*** mickeys has quit IRC05:01
*** chandanc has quit IRC05:06
*** padkrish has quit IRC05:07
*** mikal_ has joined #openstack-meeting-305:08
*** megm_ has joined #openstack-meeting-305:08
*** davidlenwell has quit IRC05:09
*** yushiro has left #openstack-meeting-305:09
*** lcastell_ has joined #openstack-meeting-305:11
*** ttrifonov_ has joined #openstack-meeting-305:11
*** sambetts has joined #openstack-meeting-305:11
*** sambetts|afk has quit IRC05:12
*** lcastell has quit IRC05:12
*** piet has quit IRC05:12
*** ttrifonov has quit IRC05:12
*** fnordahl has quit IRC05:12
*** mikal has quit IRC05:12
*** sergio_nubeliu has quit IRC05:12
*** vsaienko1 has quit IRC05:12
*** megm has quit IRC05:12
*** lcastell_ is now known as lcastell05:13
*** yamamoto_ has joined #openstack-meeting-305:13
*** sergio_nubeliu has joined #openstack-meeting-305:13
*** banix has quit IRC05:15
*** fnordahl has joined #openstack-meeting-305:15
*** vsaienko has joined #openstack-meeting-305:16
*** lpetrut has joined #openstack-meeting-305:17
*** davidlenwell has joined #openstack-meeting-305:17
*** salv-orlando has quit IRC05:18
*** salv-orlando has joined #openstack-meeting-305:18
*** numans has joined #openstack-meeting-305:24
*** soichi has joined #openstack-meeting-305:25
*** sdake has quit IRC05:26
*** egallen has joined #openstack-meeting-305:26
*** kaz has joined #openstack-meeting-305:28
*** sankarshan_away is now known as sankarshan05:28
*** matrohon has quit IRC05:29
fawadkhaliqhi soichi kaz05:33
soichilets start?05:34
fawadkhaliqyes please05:35
fawadkhaliqwho is moderating the meeting today?05:35
soichi#startmeeting taas05:36
openstackMeeting started Wed May 18 05:36:08 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:36
*** openstack changes topic to " (Meeting topic: taas)"05:36
openstackThe meeting name has been set to 'taas'05:36
soichiwe'd like to share a result of a preliminaly performance measurement05:36
*** padkrish has joined #openstack-meeting-305:38
kazThis is a result of performance measurement on a single compute node.05:38
fawadkhaliqhi kaz, soichi very cool05:40
fawadkhaliqcan you please give a quick summary of the performance results here05:40
*** padkrish has quit IRC05:42
kazI found that there is a performance impact of TaaS about 10-20%05:43
yamamoto_have you measured drop rate?05:44
kazWe did not count05:45
*** ccamacho has quit IRC05:46
*** ccamacho has joined #openstack-meeting-305:47
soichiwe observed several packet loss between Src VM and Dst VM, but almost no packet loss about mirroed packtes05:47
kazwe guess the performance is limited because of vhost-net (kernel thread) running in host become overload (CPU 100%)05:50
*** abhishekk has left #openstack-meeting-305:51
*** iyamahat has joined #openstack-meeting-305:52
soichilet's go on next topic: open discussion05:53
*** yushiro has joined #openstack-meeting-305:54
soichiAnyone else has any updates?05:54
yamamoto_i don't have anything05:55
soichifawadkhaliq: do you have nay topic?05:56
soichinay -> any05:57
fawadkhaliqnope, nothing05:57
soichiokay, i'd like to close today's meeting05:57
soichithank you05:57
*** openstack changes topic to "OpenStack Meetings ||"05:57
openstackMeeting ended Wed May 18 05:57:50 2016 UTC.  Information about MeetBot at . (v 0.1.4)05:57
openstackMinutes (text):
*** yushiro has quit IRC05:58
*** kaz has quit IRC05:59
*** soichi has left #openstack-meeting-305:59
reedip__the timing is causing confusion :(06:01
*** mickeys has joined #openstack-meeting-306:02
*** david-lyle has quit IRC06:05
*** mickeys has quit IRC06:07
*** jrist has quit IRC06:07
*** anilvenkata has joined #openstack-meeting-306:07
*** donghao has quit IRC06:12
*** hoangcx has left #openstack-meeting-306:15
*** irenab_ has joined #openstack-meeting-306:21
*** jrist has joined #openstack-meeting-306:22
*** jrist has quit IRC06:22
*** jrist has joined #openstack-meeting-306:22
*** irenab has quit IRC06:22
*** irenab_ is now known as irenab06:22
*** CaoWei has joined #openstack-meeting-306:27
*** salv-orlando has quit IRC06:30
*** sverma has joined #openstack-meeting-306:30
*** fwdit has joined #openstack-meeting-306:39
*** lpetrut has quit IRC06:41
*** egallen has quit IRC06:42
*** jtomasek has joined #openstack-meeting-306:45
*** tfukushima has joined #openstack-meeting-306:47
*** nkrinner_afk is now known as nkrinner06:47
*** CaoWei has quit IRC06:47
*** CaoWei has joined #openstack-meeting-306:48
*** andreas_s has joined #openstack-meeting-306:50
*** donghao has joined #openstack-meeting-306:51
*** lpetrut has joined #openstack-meeting-306:52
*** coolsvap has quit IRC06:53
*** coolsvap has joined #openstack-meeting-306:53
*** maishsk has quit IRC07:01
*** belmoreira has joined #openstack-meeting-307:02
*** jschwarz__ has joined #openstack-meeting-307:05
*** salv-orlando has joined #openstack-meeting-307:11
*** egallen has joined #openstack-meeting-307:18
*** egallen has quit IRC07:21
*** matrohon has joined #openstack-meeting-307:22
*** lpetrut has quit IRC07:23
*** jlanoux has joined #openstack-meeting-307:26
*** salv-orlando has quit IRC07:31
*** lpetrut has joined #openstack-meeting-307:35
*** salv-orlando has joined #openstack-meeting-307:35
*** c64cosmin has joined #openstack-meeting-307:37
*** ihrachys has joined #openstack-meeting-307:38
*** salv-orl_ has joined #openstack-meeting-307:48
*** salv-orlando has quit IRC07:52
*** fawadkhaliq has quit IRC07:52
*** fawadkhaliq has joined #openstack-meeting-307:52
*** david-lyle has joined #openstack-meeting-307:57
*** fawadkhaliq has quit IRC07:58
*** fawadkhaliq has joined #openstack-meeting-307:58
*** fawadkhaliq has quit IRC07:58
*** fawadkhaliq has joined #openstack-meeting-307:59
*** robcresswell has joined #openstack-meeting-307:59
*** fawadkhaliq has quit IRC07:59
*** fawadkhaliq has joined #openstack-meeting-308:00
robcresswell#startmeeting horizon08:00
openstackMeeting started Wed May 18 08:00:32 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: horizon)"08:00
openstackThe meeting name has been set to 'horizon'08:00
*** fawadkhaliq has quit IRC08:00
robcresswellAnyone around for Horizon meeting?08:01
*** fawadkhaliq has joined #openstack-meeting-308:01
*** jschwarz__ has quit IRC08:01
*** fawadkhaliq has quit IRC08:01
*** tsufiev has joined #openstack-meeting-308:01
*** fawadkhaliq has joined #openstack-meeting-308:01
*** fawadkhaliq has quit IRC08:02
*** fawadkhaliq has joined #openstack-meeting-308:02
*** aarefiev has joined #openstack-meeting-308:02
robcresswellPerhaps we should defer discussion points to the other time slot08:02
*** fawadkhaliq has quit IRC08:02
robcresswellSound okay to you tsufiev ?08:03
*** fawadkhaliq has joined #openstack-meeting-308:03
tsufievrobcresswell, what are the discussion points?08:03
*** fawadkhaliq has quit IRC08:03
tsufievI mean, do we have something specific?08:03
*** mickeys has joined #openstack-meeting-308:04
*** fawadkhaliq has joined #openstack-meeting-308:04
robcresswellYou had an item in there, assuming you wanted to discuss with a larger group?08:04
*** fawadkhaliq has quit IRC08:04
tsufievah yes, it makes no much sense discussing it between just you and me :)08:05
*** fawadkhaliq has joined #openstack-meeting-308:05
*** fawadkhaliq has quit IRC08:05
*** muawiakhan has joined #openstack-meeting-308:05
robcresswellJust going to post some stuff for sake of minutes than we can call it08:05
tsufievso, moving these things to an evening slot?08:06
robcresswellYep, we'll use the drivers time08:06
robcresswell#info Midcycle in San Jose, July 12th to 14th08:06
*** fawadkhaliq has joined #openstack-meeting-308:06
*** fawadkhaliq has quit IRC08:06
robcresswell#info Weekly bug report updated08:06
*** fawadkhaliq has joined #openstack-meeting-308:06
robcresswellThats all from me.08:07
*** openstack changes topic to "OpenStack Meetings ||"08:07
openstackMeeting ended Wed May 18 08:07:21 2016 UTC.  Information about MeetBot at . (v 0.1.4)08:07
openstackMinutes (text):
*** fawadkhaliq has quit IRC08:07
*** mkoushnir has joined #openstack-meeting-308:07
*** fawadkhaliq has joined #openstack-meeting-308:08
*** mkoushnir has left #openstack-meeting-308:08
*** mickeys has quit IRC08:09
*** lhartal has joined #openstack-meeting-308:11
*** qwebirc71936 has joined #openstack-meeting-308:11
*** andreas_s has quit IRC08:12
*** robcresswell has left #openstack-meeting-308:12
*** qwebirc71936 has quit IRC08:12
*** maishsk has joined #openstack-meeting-308:13
*** maishsk has quit IRC08:14
*** jschwarz__ has joined #openstack-meeting-308:16
*** wangbo has joined #openstack-meeting-308:22
*** kenji-i has joined #openstack-meeting-308:24
*** salv-orl_ has quit IRC08:27
*** mbound has joined #openstack-meeting-308:36
*** sverma has quit IRC08:39
*** dedery_ has joined #openstack-meeting-308:40
*** _milan_ has joined #openstack-meeting-308:40
*** stanzgy_ has joined #openstack-meeting-308:42
*** ediardo_ has joined #openstack-meeting-308:43
*** tdurakov_ has joined #openstack-meeting-308:43
*** carl_baldwin_ has joined #openstack-meeting-308:43
*** wendar_ has joined #openstack-meeting-308:43
*** igormarnat__ has joined #openstack-meeting-308:43
*** jraim_ has joined #openstack-meeting-308:44
*** eglute_s has joined #openstack-meeting-308:44
*** bapalm_ has joined #openstack-meeting-308:44
*** rmoe_ has joined #openstack-meeting-308:44
*** haleyb_ has joined #openstack-meeting-308:44
*** breton_ has joined #openstack-meeting-308:45
*** mfranc213_ has joined #openstack-meeting-308:45
*** igormarnat_ has quit IRC08:45
*** sigmavirus24_awa has quit IRC08:45
*** mfranc213 has quit IRC08:45
*** bharathm has quit IRC08:45
*** tdurakov has quit IRC08:45
*** carl_baldwin has quit IRC08:45
*** skath has quit IRC08:45
*** jraim has quit IRC08:45
*** med_ has quit IRC08:45
*** milan has quit IRC08:45
*** davidmichaelkarr has quit IRC08:45
*** ameade has quit IRC08:45
*** tpeoples has quit IRC08:45
*** zz_dimtruck has quit IRC08:45
*** bapalm has quit IRC08:45
*** melwitt has quit IRC08:45
*** leifz has quit IRC08:45
*** cloudnull has quit IRC08:45
*** pasquier-s has quit IRC08:45
*** dedery has quit IRC08:45
*** stanzgy has quit IRC08:45
*** briancurtin has quit IRC08:45
*** ediardo has quit IRC08:45
*** Adri2000 has quit IRC08:45
*** eglute has quit IRC08:45
*** aarefiev has quit IRC08:45
*** fwdit has quit IRC08:45
*** haleyb has quit IRC08:45
*** breton has quit IRC08:45
*** rmoe has quit IRC08:45
*** wendar has quit IRC08:45
*** vkmc has quit IRC08:45
*** melwitt has joined #openstack-meeting-308:45
*** Adri2000 has joined #openstack-meeting-308:45
*** skath has joined #openstack-meeting-308:45
*** leifz has joined #openstack-meeting-308:45
*** med_ has joined #openstack-meeting-308:45
*** vkmc has joined #openstack-meeting-308:45
*** igormarnat__ is now known as igormarnat_08:45
*** dimtruckl has joined #openstack-meeting-308:45
*** Adri2000 has quit IRC08:45
*** Adri2000 has joined #openstack-meeting-308:45
*** med_ has quit IRC08:45
*** med_ has joined #openstack-meeting-308:45
*** sigmavirus24_awa has joined #openstack-meeting-308:45
*** sigmavirus24_awa has quit IRC08:45
*** sigmavirus24_awa has joined #openstack-meeting-308:45
*** vkmc has quit IRC08:45
*** vkmc has joined #openstack-meeting-308:45
*** tdurakov_ is now known as tdurakov08:46
*** melwitt is now known as Guest3726408:46
*** dimtruckl is now known as dimtruck08:46
*** skath has quit IRC08:46
*** skath has joined #openstack-meeting-308:46
*** cloudkiller has joined #openstack-meeting-308:46
*** aarefiev has joined #openstack-meeting-308:46
*** carl_baldwin_ is now known as carl_baldwin08:47
*** ediardo_ is now known as ediardo08:47
*** jraim_ is now known as jraim08:47
*** bharathm has joined #openstack-meeting-308:47
*** serverascode has quit IRC08:47
*** dougwig has quit IRC08:48
*** sergek has quit IRC08:50
*** alanmeadows has quit IRC08:50
*** hayatb has quit IRC08:50
*** tpeoples has joined #openstack-meeting-308:52
*** jschwarz__ has quit IRC08:53
*** dtardivel has joined #openstack-meeting-308:55
*** ameade has joined #openstack-meeting-308:55
*** pasquier-s has joined #openstack-meeting-308:56
*** davidmichaelkarr has joined #openstack-meeting-308:56
*** fwdit has joined #openstack-meeting-308:58
*** ccamacho has quit IRC08:58
*** sergek has joined #openstack-meeting-308:59
*** serverascode has joined #openstack-meeting-308:59
*** dougwig has joined #openstack-meeting-308:59
*** hayatb has joined #openstack-meeting-309:00
*** ccamacho has joined #openstack-meeting-309:02
*** alanmeadows has joined #openstack-meeting-309:04
*** briancurtin has joined #openstack-meeting-309:05
*** jschwarz__ has joined #openstack-meeting-309:06
*** jschwarz__ is now known as jschwarz09:06
*** neiljerram has joined #openstack-meeting-309:07
*** salv-orlando has joined #openstack-meeting-309:09
*** CaoWei has quit IRC09:09
*** iyamahat has quit IRC09:11
*** jtomasek_ has joined #openstack-meeting-309:12
*** lpetrut has quit IRC09:13
*** donghao has quit IRC09:13
*** jtomasek_ has quit IRC09:32
*** zhurong has quit IRC09:43
*** SarathChandraMek has quit IRC09:43
*** stendulker has joined #openstack-meeting-309:46
*** cloudkiller is now known as cloudnull09:46
*** zhurong has joined #openstack-meeting-309:47
*** fawadkhaliq has quit IRC09:49
*** fawadkhaliq has joined #openstack-meeting-309:50
*** markvoelker has joined #openstack-meeting-309:56
*** matrohon has quit IRC09:59
*** neiljerram has quit IRC09:59
*** sdague has joined #openstack-meeting-310:01
*** neiljerram has joined #openstack-meeting-310:01
*** markvoelker has quit IRC10:02
*** ihrachys has quit IRC10:05
*** salv-orlando has quit IRC10:13
*** zhurong has quit IRC10:17
*** c64cosmin has quit IRC10:18
*** tfukushima has quit IRC10:19
*** salv-orlando has joined #openstack-meeting-310:20
*** tfukushima has joined #openstack-meeting-310:20
*** rossella_s has quit IRC10:23
*** rossella_s has joined #openstack-meeting-310:24
*** dimtruck is now known as zz_dimtruck10:36
*** ccamacho is now known as ccamacho|lunch10:41
*** kzaitsev_mb has joined #openstack-meeting-310:55
*** neil__ has joined #openstack-meeting-310:56
*** lpetrut has joined #openstack-meeting-310:57
*** neiljerram has quit IRC11:00
*** toddjohn_ has joined #openstack-meeting-311:01
*** cbouch has joined #openstack-meeting-311:04
*** toddjohn_ has quit IRC11:05
*** tfukushima has quit IRC11:06
*** toddjohn_ has joined #openstack-meeting-311:07
*** mickeys has joined #openstack-meeting-311:07
*** stendulker has quit IRC11:08
*** rtheis has joined #openstack-meeting-311:11
*** toddjohn_ has quit IRC11:12
*** mickeys has quit IRC11:12
*** andreas_s has joined #openstack-meeting-311:12
*** claudiub has joined #openstack-meeting-311:13
*** abhishekk has joined #openstack-meeting-311:13
*** neil__ has quit IRC11:17
*** neiljerram has joined #openstack-meeting-311:18
*** cartik has joined #openstack-meeting-311:18
*** neiljerram has quit IRC11:21
*** neiljerram has joined #openstack-meeting-311:22
*** abhishekk has left #openstack-meeting-311:23
*** neiljerram has quit IRC11:26
*** ccamacho|lunch is now known as ccamacho11:27
*** njohnsto_ has joined #openstack-meeting-311:28
*** cartik has quit IRC11:28
*** yamamoto_ has quit IRC11:38
*** julim has joined #openstack-meeting-311:40
*** baoli has joined #openstack-meeting-311:45
*** baoli_ has joined #openstack-meeting-311:46
*** abalutoiu has joined #openstack-meeting-311:47
*** cartik has joined #openstack-meeting-311:49
*** reedip__ has quit IRC11:50
*** baoli has quit IRC11:50
*** matrohon has joined #openstack-meeting-311:53
*** pavel_bondar has quit IRC11:56
*** andreas_s_ has joined #openstack-meeting-311:57
*** andreas_s_ has quit IRC11:57
*** dedery has joined #openstack-meeting-312:02
*** tellesnobrega is now known as tellesnobrega_af12:02
*** dedery has quit IRC12:03
*** dedery has joined #openstack-meeting-312:04
*** dedery_ has quit IRC12:05
*** c64cosmin has joined #openstack-meeting-312:08
*** dedery has quit IRC12:09
*** sigmavirus24_awa is now known as sigmavirus2412:12
*** fawadkhaliq has quit IRC12:17
*** fawadkhaliq has joined #openstack-meeting-312:18
*** dedery has joined #openstack-meeting-312:19
*** dedery_ has joined #openstack-meeting-312:20
*** dedery has quit IRC12:24
*** calbers has quit IRC12:29
*** njohnsto_ has quit IRC12:29
*** pavel_bondar has joined #openstack-meeting-312:32
*** zz_dimtruck is now known as dimtruck12:33
*** Poornima has quit IRC12:36
*** anteaya has joined #openstack-meeting-312:37
*** ihrachys has joined #openstack-meeting-312:40
*** pgadiya|OSPBootc has quit IRC12:41
*** salv-orlando has quit IRC12:42
*** cbouch_ has joined #openstack-meeting-312:45
*** cbouch has quit IRC12:45
*** Poornima has joined #openstack-meeting-312:52
*** neiljerram has joined #openstack-meeting-312:53
*** reedip__ has joined #openstack-meeting-312:54
*** sagar_nikam has joined #openstack-meeting-312:57
*** yamamoto has joined #openstack-meeting-312:58
*** kzaitsev_mb has quit IRC12:58
*** tellesnobrega_af is now known as tellesnobrega12:58
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed May 18 13:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
claudiubhello folks! :)13:00
claudiubsagar_nikam: anyone else joining us today from hpe?13:01
sagar_nikamsonu: should join.... we can start13:01
claudiub#topic monasca Windows / Hyper-V support13:02
*** openstack changes topic to "monasca Windows / Hyper-V support (Meeting topic: hyper-v)"13:02
domi007hi all13:02
*** atuvenie has joined #openstack-meeting-313:02
*** njohnston-- has joined #openstack-meeting-313:02
atuveniehi all13:02
atuvenielate to the party :)13:02
claudiubok, so, I've started working on this, I have a couple of patches up already13:02
claudiubstill plenty of work to go though.13:03
claudiubi'll also be attending the monasca meeting today, to get this bp approved.13:03
*** matrohon has quit IRC13:03
*** njohnston-- has quit IRC13:03
claudiubas for the patches that are already up, they are on the bp's whiteboard.13:03
claudiubor they can be seen here:13:04
sagar_nikamone thing which needs to be resolved is starting on windows13:04
claudiubsagar_nikam: it already does. :)13:04
sagar_nikamclaudiub: you had to fix anything to get it working ?13:04
claudiubthere are still a couple of things that have to be fixed. I didn't get a chance to fix them yet.13:05
*** njohnsto- has joined #openstack-meeting-313:05
claudiubsagar_nikam: yeah, there are quite a few Linux specific attributes that are being used in monasca13:05
*** njohnsto- is now known as njohnston--13:06
claudiubsagar_nikam: for example signal.SIGUSR1, or some cpu_stats, or os.statvfs. I've already mentioned them in the blueprint13:06
sagar_nikamclaudiub: the patch for that fix is already submitted ?13:06
claudiubsagar_nikam: yep, check the bp's whiteboard.13:07
sagar_nikamsure thanks13:07
claudiubfor example, this fixes the signal.SIGUSR1 issue:
sagar_nikamclaudiub: nice progress ......13:07
claudiubI've also fixed the cpu checker. I still have to fix disk checker.13:07
claudiubI have to see what wmi_checker actually does.13:07
claudiubaaand.. the biggest change that I'll have to do is the hyperv_checker13:08
claudiubthat will use the HyperVInspector13:08
sagar_nikamok... and what is the change ?13:08
claudiubat the moment, there's only the libvirt checker, meaning that the hyperv, vmware, and xenapi inspectors were never used.13:08
claudiubso, I'll have to refactor the libvirt checker, since it contains quite a lot of reusable code for any other hypervisor checker.13:09
claudiubthis is still work in progress:
claudiubwish they used oslo.config though... that would have made it easier for me. :)13:10
domi007haha that's true for so many other projects as well :)13:11
*** sverma has joined #openstack-meeting-313:11
claudiubdomi007: true, I have no idea why they don't use it. :)13:11
claudiubanyways, moving on13:11
claudiub#topic freezer support13:11
*** openstack changes topic to "freezer support (Meeting topic: hyper-v)"13:11
claudiublpetrut: hellou. :)13:11
lpetrutok, as mentioned before, we'll start with refactoring the existing code, to leverage os-win13:12
lpetrutafterwards, we'll add support for taking VM snapshots, using the Hyper-V VSS provider.13:13
sagar_nikamlpetrut: BP link ?13:13
sagar_nikamor is it still work in progress ?13:13
lpetruthaven't submitted the BP yet, wanted to see how the code gets shaped first13:14
lpetrutI guess I'll send BPs until the next meeting13:14
lpetrutwhile at it, I found a strange issue: on some nodes, I can't query for Win32_ShadowCopy, getting a provider initialize failure error. Tried reloading the VSS WMI provider, still nothing. The interesting thing is that it occurs only when using DCOM, while working when using WINRM as a protocol for MI. I'm still investigating the issue13:15
sagar_nikamWINRM is preferred ?13:16
claudiubyeah, we'll have to find a solution to this issue before we can proceed with this13:16
claudiubsagar_nikam: DCOM is the preferred and default protocol.13:16
domi007this sounds like a Microsoft/HyperV bug13:16
*** mbound has quit IRC13:17
claudiubI agree. we might have to ask them about it.13:17
claudiubif we don't find any solution to this.13:17
claudiub#topic magnum support13:18
*** openstack changes topic to "magnum support (Meeting topic: hyper-v)"13:18
claudiubatuvenie: hello. :)13:18
claudiubany good news? :)13:18
atuvenieso, magnum uses heat templates to deploy kubernetes or docker swarm13:18
atuveniethese heat templates use a lot of bash scripts13:19
claudiubso, not good news. :(13:19
atuvenienow, at this point I'm looking into how docker swarm works13:19
domi007it's time to build a bash to powershell compiler :D13:19
atuvenieand trying to check if it can work on Windows, or how difficult it can be to make it work13:20
atuvenieso the effort is concentrated on docker swarm now13:20
*** tellesnobrega is now known as tellesnobrega_af13:20
*** reedip__ has quit IRC13:20
claudiubdomi007: or just get windows 10. :D they're planning to add bash to windows 10. :)13:20
sagar_nikamWindows 2016 is supposed to have support for bash13:20
atuvenieafter that we'll concentrate on magnum13:20
*** tellesnobrega_af is now known as tellesnobrega13:21
domi007yes, but I'm doubting it could run any of these scripts since it's just a userland emulation kind of thing, not really serious imho13:21
atuveniewe can get rid of the bash stuff, but first thing first is to see how and if Docker Swarm works with Windows13:21
*** kzaitsev_mb has joined #openstack-meeting-313:22
domi007sounds good13:22
atuveniewe're concentrating on Docker Swarm for the moment, but from what I know there is an effort in place to make Kubernetes work with Windows Containers as well13:23
claudiubcool, I think we can move on.13:25
claudiubany topics you guys want to talk about?13:25
sagar_nikamclaudiub: cluster driver, FC and freerdp13:25
domi007yes I have some13:26
sagar_nikamin that order13:26
domi007FreeRDP is on my list as well13:26
claudiub#topic Hyper-V Cluster Driver13:26
*** openstack changes topic to "Hyper-V Cluster Driver (Meeting topic: hyper-v)"13:26
domi007and my other topic is VXLAN + WMI SecGroups and VXLAN + VLAN interoperability (hybrids)13:26
sagar_nikambp and patch submitted for newton ?13:26
sagar_nikami can pick it and check how it works13:27
sagar_nikami know that it was submitted in mitaka... has it changed since then13:27
claudiubThe Hyper-V cluster driver patch:
claudiubblueprint is approved13:28
claudiubas far as I know, it hasn't changed since we merged it in compute-hyperv13:28
claudiubright, atuvenie?13:29
atuvenieyes, no changes13:29
*** banix has joined #openstack-meeting-313:29
claudiubsooo... it just needs reviews. :)13:29
sagar_nikami would like to pick up from upstream. can you point me to the review13:29
claudiubposted the link above:
claudiubok, moving on. :)13:30
claudiub#topic Fibre Channel13:30
*** openstack changes topic to "Fibre Channel (Meeting topic: hyper-v)"13:30
*** tonytan4ever has joined #openstack-meeting-313:31
claudiubas you know, we're waiting to the os-brick patch to merge first, before the changes in nova can merge.13:31
*** matrohon has joined #openstack-meeting-313:31
sagar_nikamcode is all ready ?13:31
claudiubyep. the patch this depended on merged.13:31
sagar_nikamthere was a issue which denny found13:31
claudiubso, it should merge.13:31
*** ddieterly has joined #openstack-meeting-313:32
lpetrutsagar_nikam: you mean not being able to find attached disks?13:32
sagar_nikamlpetrut: you had a fix for it ... correct ?13:32
lpetrutsagar_nikam: there is a patch that may fix the issue, but I was hoping he could say whether it worked for him13:33
*** dedery_ has quit IRC13:34
sagar_nikamnova patches reviewed by hemna: ?13:35
claudiubanyways. sagar_nikam, can you ping hemna to review the os-brick change?13:35
claudiubawesome! :D13:35
lpetruthere's the nova patch:
*** cloudtrainme has joined #openstack-meeting-313:36
claudiubcool, moving on. :)13:36
claudiub#topic FreeRDP13:36
*** openstack changes topic to "FreeRDP (Meeting topic: hyper-v)"13:36
claudiubsoo, who wants to start? :)13:36
claudiubc64cosmin: hello. :)13:36
c64cosminhey ppl13:36
domi007hi :)13:36
domi007so what's the current status?13:37
c64cosminso, things are going well13:37
sagar_nikamc64cosmin: how is the work on making freerdp stable going ?13:37
c64cosminI have two more PR to be merged and think should go fine from there13:37
c64cosminas far as you know13:37
c64cosminwhen you use the nova-drivers13:38
*** ddieterly is now known as ddieterly[away]13:38
c64cosminwe also add a PowerShell command for easily opening a console13:38
c64cosminthat opens a FreeRDP console13:38
c64cosminsometimes the keyboard is stuck13:38
c64cosminit seems the same happens with web-connect too13:38
domi007and sometimes the daemon stucks as well, expecially when being checked regularly :(13:39
sagar_nikamyes... keyboard does not work... have seen that13:39
c64cosminso building with a stable branch might solve the issue13:39
c64cosminI'm testing/building against the stable branch13:40
c64cosminand and never could replicate13:40
domi007can't wait to see that in action13:40
c64cosminreplace the branch on our CI and it should be fine13:41
*** kzaitsev_mb has quit IRC13:41
sagar_nikamc64cosmin: there was some plans of rewriting some code ?13:41
c64cosminabout getting stuck if multiple request fire up13:41
sagar_nikamto make it more stable13:41
c64cosminalso with my build could not replicate13:41
*** aliadil has joined #openstack-meeting-313:41
domi007can you tell us when should we expect that branch-change to happen then? :)13:41
c64cosminI created 10 instances and opened the consoles at once13:42
c64cosminno issue there13:42
*** dimtruck is now known as zz_dimtruck13:42
*** hichihara has joined #openstack-meeting-313:43
c64cosminsagar_nikam: yes, my plans are to make a stable release and make a new version of WebConnect13:43
*** salv-orlando has joined #openstack-meeting-313:43
*** mtanino has joined #openstack-meeting-313:43
c64cosminweb serving will be stripped down from it13:43
sagar_nikamnew version of webconnect --- can you provide some more details please13:43
domi007stripping down webserving from it is great, that should really add some stability alone13:44
c64cosmindomi007: today, tomorrow13:44
c64cosmindon't know how to keep you posted13:44
c64cosminbut I will follow with an answer to the issues that were solved13:45
domi007that'd be great sure13:45
domi007maybe someone at cloudbase can write a blogpost or something as well13:45
domi007but if you answer to the issues that's also great13:45
sagar_nikami can pick up as soon as it is available13:45
*** moshele has joined #openstack-meeting-313:45
c64cosminso what I plan for webconnect is to strip down the webserving13:46
sagar_nikamdomi007: agree.. blogpost would be nice13:46
*** lpetrut has quit IRC13:46
c64cosmininvestigating on the cloudbase repo that we have13:46
c64cosminit seems that EHS (embedded HTML server) is the problem13:46
c64cosminit's not a programatical one apparently, but a runtime issue13:47
domi007I couldn't agree more13:47
domi007according to what we experienced13:47
c64cosminalso for the next version I plan to rewrite the client side of the console13:48
c64cosminit seems to be a bit slow13:48
c64cosminespecially for Windows machines13:48
sagar_nikamplans for debian or rpm ?13:49
*** ddieterly[away] is now known as ddieterly13:49
c64cosminI will do those after we change the CI scripts13:49
sagar_nikami think if we install in on controller like no-vnc proxy... it will be nice13:49
c64cosminyep, took that in account13:50
sagar_nikamc64cosmin: so deb is planned ?13:50
c64cosminI've tested webconnect on linux and it works just fine13:50
sagar_nikamdebian jesse ?13:50
c64cosminalso this new build will feature less CPU consumption13:50
*** dedery has joined #openstack-meeting-313:51
sagar_nikamc64cosmin: we are on debian... as soon as you have a DEB, let me know.. can test and let you know13:52
*** dedery_ has joined #openstack-meeting-313:52
c64cosminsagar_nikam: nope, but seems that we already have a PR for build scripts for Debian13:52
*** rbak has joined #openstack-meeting-313:53
c64cosminso returning to stability13:53
*** ccamacho has quit IRC13:53
c64cosminall the issues that were related, didn't happen on my env13:53
c64cosminso we have two .msi for windows13:53
c64cosminone is the "stable" one13:54
c64cosminit's a old version13:54
*** ccamacho has joined #openstack-meeting-313:54
c64cosminand also we have a "beta"13:54
*** toddjohn_ has joined #openstack-meeting-313:54
domi007yes indeed13:54
c64cosminprobably the new build will also be beta for a while13:54
*** irenab has quit IRC13:54
domi007okay, we'll keep trying the beta msi and see how it performs13:55
sagar_nikami used both ... found some issues in both13:55
claudiubsagar_nikam: domi007: What were your environments when you encountered this issue? OS, memory, cpu, guest VM OS? It might be helpful to know these details, in order to properly replicate the issue.13:55
c64cosminclaudiub: yes please do13:55
*** dedery has quit IRC13:55
c64cosminsagar_nikam: if you remember, please enumerate what you've encountered13:56
*** donghao has joined #openstack-meeting-313:56
domi007mine was independent from the guest OS, I had webconnect running on hyperv, and simply the login page wouldn't show up...just kept loading until the daemon was killed and restarted13:56
domi007when trying to hook it up with haproxy13:56
domi007or testing it with the curl script I mentioned earlier13:56
*** ostroverkhov has joined #openstack-meeting-313:57
*** doug-fish has joined #openstack-meeting-313:57
*** jmckind has joined #openstack-meeting-313:57
*** toddjohn_ has quit IRC13:58
*** cbouch__ has joined #openstack-meeting-313:58
domi007only 5 minutes left can we come back to freeRDP once we tested the new builds?13:58
claudiubwhat curl script? i don't see any in this meeting.13:58
domi007claudiub: it was the github link I posted13:59
claudiubah, ok, gotcha. ty. :)13:59
*** sagar_nikam has quit IRC13:59
*** sagar_niksm has joined #openstack-meeting-313:59
*** absubram has quit IRC13:59
sagar_niksmGot disconnected14:00
c64cosmindomi007: I think I'm cc-ed in a mail about freerdp14:00
sagar_niksmBack again14:00
*** njohnston-- is now known as njohnston__14:00
claudiubanyways, seems we have to end the meeting. we can continue in #openstack-hyper-v14:00
c64cosminis it ok, if I contact you with that?14:00
domi007c64cosmin: sure14:00
*** ostroverkhov is now known as xrollla14:00
*** toddjohn_ has joined #openstack-meeting-314:00
domi007claudiub: okay, I'll join that as well now :)14:00
c64cosminbye guys14:00
claudiubthanks c64cosmin for the help with free rdp stuff. :)14:00
claudiubthank you all for joining. :)14:01
*** cartik has quit IRC14:01
*** openstack changes topic to "OpenStack Meetings ||"14:01
openstackMeeting ended Wed May 18 14:01:08 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:01
openstackMinutes (text):
njohnston__#startmeeting neutron_qos14:01
openstackMeeting started Wed May 18 14:01:16 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston__. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** tmorin has joined #openstack-meeting-314:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
mosheleajo_: hi14:01
njohnston__#chair ajo_14:01
openstackCurrent chairs: ajo_ njohnston__14:01
ajo_o/ moshele njohnston_  :)14:01
moshelenjohnston__: hi14:01
njohnston__ok, lets get started14:01
ajo_thanks for chairing mr njohnston_ :)14:01
tmorinhi everyone (i'll be mostly listening)14:01
njohnston__#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"14:01
njohnston__I just want to note that we are now 2 weeks from N-1.  Tempus fugit!14:01
ajo_really fugit....14:02
*** edand has joined #openstack-meeting-314:02
*** cbouch_ has quit IRC14:02
njohnston__moving along smartly...14:02
njohnston__#topic Late-Breaking News14:02
*** openstack changes topic to "Late-Breaking News (Meeting topic: neutron_qos)"14:02
njohnston__moshele was wondering if we remove openflow rules when a VM is deleted.  I did not check this, did anyone else?14:02
*** sankarshan is now known as sankarshan_away14:02
*** toddjoh__ has joined #openstack-meeting-314:02
ajo_njohnston_, I didn't, moshele did you find it fail, or you just think it was a possibility ?14:03
ajo_in any case, we shall verify and provide a bug report14:03
njohnston__I plan to give it a go later today, but I have to recreate my testing environment.14:03
*** vishwanathj has joined #openstack-meeting-314:03
ajo_moshele, can you comment what you said on #openstack-neutron so we have it registered here on the meeting log?14:03
mosheleajo_: I don't know how to check ovs, but I saw that in the extention_manager we are passing port=None14:03
*** yamahata has joined #openstack-meeting-314:04
mosheleajo_: sure14:04
mosheledid you test the ovs qos when deleting vm ? does it remove the openflow rules?14:04
njohnston__I think we did, but my memory is hazy enough at this point that I want to recheck14:04
*** toddjohn_ has quit IRC14:05
*** toddjohn_ has joined #openstack-meeting-314:05
njohnston__This one should be relatively easy to prove or disprove experimentally.14:05
*** cloudtrainme has quit IRC14:05
mosheleso what I see is the in we are getting port=None14:05
njohnston__just compare the output of ovs-ofctl dump-flows pre and post VM deletion14:05
mosheleand I think  it is because we delete it in
ajo_ok, so let's get it tested, and report a bug if necessary,14:06
*** lpetrut has joined #openstack-meeting-314:06
mosheleok we will try it14:06
ajo_if moshele suspicions are right, we may need to introduce some sort of memory to keep the ofport/vif port, etc.. or any necessary detail for cleanup14:06
njohnston__#action Test ovs-ofctl dump-flows output pre and post VM deletion to make sure that QoS flows are removed. njohnston14:06
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0xa035210>14:07
ajo_#action njohnston Test ovs-ofctl dump-flows output pre and post VM deletion to make sure that QoS flows are removed.14:07
*** mrmartin has joined #openstack-meeting-314:07
*** toddjoh__ has quit IRC14:07
*** ralonsoh has joined #openstack-meeting-314:07
njohnston__moshele: If I verify that you are correct do you mind filing the bug with the proper references in the code?14:07
mosheleajo_: we just encounter this becuase we wanted to write l2 extention to ovs14:07
moshelenjohnston__: sure14:07
mosheleand on the delete port we got port=None14:08
njohnston__#action moshele File bug report after njohnston verifies bug truthiness.14:08
ajo_moshele, so probably, that's the case, I suspect we will have to make the cleanup process more robust14:08
njohnston__ok, let's move on.14:08
njohnston__#topic Bugs14:08
*** davidsha has joined #openstack-meeting-314:08
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:08
ajo_of bw limit it wasn't necessary, because things were cleaned up automatically when the vif was deleted.14:08
mosheleajo_: as you remember I had cleanup issues with SR-IOV14:09
njohnston__Congrats to slaweq for merging
*** salv-orlando has quit IRC14:09
*** slaweq has joined #openstack-meeting-314:09
openstackLaunchpad bug 1515533 in neutron "QoS policy is not enforced when using a previously used port" [Low,In progress] - Assigned to Ilya Chukhnakov (ichukhnakov)14:09
njohnston__This was just picked up by Ilya Chukhnakov (ichukhnakov)14:09
*** mickeys has joined #openstack-meeting-314:10
mosheleajo_: I see14:10
*** iyamahat has joined #openstack-meeting-314:10
njohnston__next bug is #link
openstackLaunchpad bug 1486607 in neutron "tenants seem like they were able to detach admin enforced QoS policies from ports or networks" [Medium,In progress] - Assigned to Nate Johnston (nate-johnston)14:11
njohnston__This is mine.  Since we don't test permutations of the server policies, we don't need a new API test.  This is now ready to merge I think.  After that I will look at backports.14:11
ajo_ohhh, thanks, she found the reason :) instead of doing a workaround :D14:11
njohnston__ajo_: Yeah, she got to the root of it I think, it's good work.14:11
ajo_njohnston_, were you able to verify manually ?14:12
njohnston__ajo_: yes, I was able to verify manually14:12
ajo_njohnston_, I should re-review and verify, probably it's good to go by my last look at the code14:12
ajo_njohnston_, thanks, wonderful :D14:12
njohnston__ajo_: thank you sir14:12
openstackLaunchpad bug 1507654 in neutron "Use VersionedObjectSerializer for RPC push/pull interfaces" [Low,In progress] - Assigned to Artur Korzeniewski (artur-korzeniewski)14:13
njohnston__I pinged Artur in the bug to provide a change he is working on.14:13
*** lblanchard has joined #openstack-meeting-314:14
njohnston__he responded with change so we can look at that14:14
ajo_it's unclear to me14:14
ajo_ihrachys,  ^14:14
*** sdake has joined #openstack-meeting-314:14
*** mickeys has quit IRC14:14
ajo_can you comment on that bug  and artur's response ?14:14
njohnston__Speaking of ihrachys...14:15
openstackLaunchpad bug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:15
njohnston__This one appears to be dead, with Ihar preferring a documentation change.  Time to abandon it?14:15
slaweqthis can't be solved for now14:15
ihrachysajo_: I think korzen described everything clearly there?..14:15
slaweqI made some note in docs14:15
ihrachysajo_: we don't plan to pursue it right now14:15
*** edand has left #openstack-meeting-314:15
slaweqand that's all what I can do with it14:15
ihrachysI think the bug should be closed for now14:15
ajo_ihrachys, so, the serializer will be switched when other rpc endpoints start sending ovos,14:15
ajo_did I get it right?14:15
*** bklei has joined #openstack-meeting-314:16
ihrachysajo_: when/if we send real objects (and not dicts that represent them, as we do with callbacks)14:16
ajo_I'd propose closing this as won't fix, until that's changed14:16
ajo_and then, we reconsider14:16
ihrachysif that's the case, we would be able to pass objects directly into oslo.messaging.14:16
ihrachysbut there is no use case for that right now14:16
*** sagar_niksm has quit IRC14:16
ajo_beyond rpc callbacks14:17
njohnston__#action njohnston close bug 1507654 as "won't fix"14:17
openstackbug 1507654 in neutron "Use VersionedObjectSerializer for RPC push/pull interfaces" [Low,In progress] - Assigned to Artur Korzeniewski (artur-korzeniewski)14:17
njohnston__back to bug 150776114:17
openstackbug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:17
*** mbound has joined #openstack-meeting-314:17
slaweqnjohnston__: as I said, change in docs is done14:18
slaweqand nothing else can be done here for now14:18
*** AlanClark has joined #openstack-meeting-314:18
*** iyamahat has quit IRC14:18
njohnston__slaweq: Time to abandon then?14:18
*** yamahata has quit IRC14:18
slaweqajo_: ihrachys: what You think?14:18
slaweqIMHO yes14:18
ajo_njohnston_, I have moved the bug into won't fix14:19
*** claudiub has quit IRC14:19
*** doug-fis_ has joined #openstack-meeting-314:19
ajo_yes slaweq , you can kill it for now14:19
njohnston__ajo_: Thanks!14:19
ajo_it's nice to clean bugs :P :)14:19
openstackLaunchpad bug 1515564 in neutron "Internal server error when running qos-bandwidth-limit-rule-update as a tenant" [Low,In progress] - Assigned to Liyingjun (liyingjun)14:19
njohnston__Change is
njohnston__This is in need of core reviews - it has no negative reviews, but nobody has reviewed it since April.14:20
ihrachysslaweq: yes14:20
ajo_ack, I will review14:21
njohnston__thanks ajo_14:21
*** doug-fish has quit IRC14:21
openstackLaunchpad bug 1558614 in neutron "The QoS notification_driver is just a service_provider, and we should look into moving to that" [Low,In progress] - Assigned to Ching Sun (ching-sun)14:21
ajo_as a note14:22
ajo_that will clash with mfranc213_ work on the qos plugin refactor14:22
njohnston__Duly noted, I'm not sure if she is watching but I'll make sure she's aware.14:22
*** mbound has quit IRC14:23
ajo_about service providers...14:23
ajo_I'm not sure that bug is really valid14:23
*** rhochmuth has joined #openstack-meeting-314:23
ajo_I believe service providers were made to allow serveral service providers at once,...14:23
*** vhoward has joined #openstack-meeting-314:23
ajo_and then you could be able to pick the right one when you create the resources14:23
*** rossella_s has quit IRC14:23
ajo_in the case of the qos plugin, this is only an interface to the backend inplementation(s)14:24
ajo_and the user can't pick nothing,14:24
*** rossella_s has joined #openstack-meeting-314:24
njohnston__I think we can mark it 'opinion' and move on14:24
ajo_njohnston_, makes sense14:24
ajo_I will do it, and put the explanation I just gave14:25
njohnston__ajo_: Thanks!14:25
openstackLaunchpad bug 1515533 in neutron "QoS policy is not enforced when using a previously used port" [Low,In progress] - Assigned to Ilya Chukhnakov (ichukhnakov)14:25
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x9cb9c90>14:25
*** sdake has quit IRC14:26
njohnston__#topic Approved RFEs14:26
*** openstack changes topic to "Approved RFEs (Meeting topic: neutron_qos)"14:26
openstackLaunchpad bug 1468353 in neutron "[RFE] QoS DSCP marking rule support" [Wishlist,Fix committed] - Assigned to David Shaughnessy (david-shaughnessy)14:26
njohnston__This is the RFE for DSCP.  It's just waiting on the fullstack change, which looks good to merge - just needs core reviews.14:26
njohnston__Change is:
*** sdake has joined #openstack-meeting-314:27
*** Swami has joined #openstack-meeting-314:27
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:27
*** atuvenie has quit IRC14:27
njohnston__Change is:
njohnston__looks like slaweq is working this with gsagie on that14:27
ajo_I will re-review, sorry for being a bit slow on this14:27
slaweqthis is going forward14:27
slaweqI have working ingress limit for both linuxbridge and ovs agents14:28
njohnston__slaweq: That's great14:28
slaweqI have some comments in review which I need to address14:28
slaweqand also I found that there is no functional tests for linuxbridge agent14:28
ajo_slaweq, keep an eye on mfranc213_ plugin refactor, you may need to adopt her changes, although it will be easy14:28
njohnston__I was shocked when I read that, slaweq14:29
slaweqso I started adding it in separate patch:
ajo_mfranc213_, : I suspect we should prioritize your patch, so everything lands on top of your refactor14:29
slaweqajo_: ofcourse I will rebase my patch when her will be merged14:29
ajo_and, said that, it was already on good condition IMHO, so I will do a final pass after meeting to see if here's something left14:29
slaweqI think that her patch is closer to merge14:29
njohnston__#topic RFEs that don't have the rfe-approved tag14:30
*** openstack changes topic to "RFEs that don't have the rfe-approved tag (Meeting topic: neutron_qos)"14:30
slaweqso maybe I will have to change mine littlebit :)14:30
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Confirmed] - Assigned to Reedip (reedip-banerjee)14:30
ajo_that one, I discussed it with reedip14:31
njohnston__I was unclear on whether amotoki's concerns had been addressed14:31
ajo_and needs a thought, as per my discussions with him on the summit, it was clear he wanted to leverage ECN, but the mechanisms were not clear14:31
njohnston__Ah, what did reedip say ajo_?14:31
ajo_how do you detect congestion, when, .. etc14:31
*** jschwarz_ has joined #openstack-meeting-314:31
ajo_njohnston_, I'd mark that as incomplete for now14:32
njohnston__I think that is all handled in the IP stack and in the intervening network devices between two ECN-enabled nodes14:32
ajo_until he provides more input, or we have more people willing to work on it14:32
njohnston__the congestion detection, I mena14:32
mfranc213_ajo_ ack (and sorry late)14:32
davidshaThats the impression I was under as well14:32
ajo_njohnston_, yes, but if we do something about ecn...14:32
ajo_the hypervisor, or the network nodes, become network devices14:32
ajo_which may act upon congestion14:32
ajo_one way could be ... altering bw limit rules, to trigger ECN over bw limits, instead of dropping14:33
*** jschwarz has quit IRC14:33
njohnston__this sounds like something that should be handled at the OVS layer (or LB equivalent)14:34
njohnston__because it's processing at a per-packet level14:34
ajo_my thinking, is that we wait for more feedback from reedip, or any other interested party on ECN14:34
njohnston__as opposed to just making sure that ECN is marked as enabled and letting whatever congestion behavior is built into OVS etc. handle it14:34
*** salv-orlando has joined #openstack-meeting-314:35
njohnston__ajo_: Do you mind commenting on the bug since you already have the dialogue with reedip?14:35
*** marios is now known as marios|call14:35
*** doug-fis_ has quit IRC14:35
ajo_njohnston_, correct, that makes sense14:35
*** abalutoiu has quit IRC14:35
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Reedip (reedip-banerjee)14:35
slaweqajo_: but isn't this ECN related to Your specs about openflows?14:36
*** hosanai has joined #openstack-meeting-314:36
davidshaslaweq: flow management is it?14:37
slaweqdavidsha: yep14:37
ajo_slaweq, eventually, it could be, yes14:37
davidshaslaweq: If it's done like dscp it shouldn't have a problem14:37
*** jmckind has quit IRC14:37
*** Poornima has quit IRC14:38
njohnston__And it should be done like DSCP, probably pretty well integrated into the DSCP implementation given that DSCP and ECN share the same byte in the IP header.14:38
slaweqok, I just though that if it is another flow in bridges then it will be harder and harder to maintenance14:38
slaweqwithout this flow management :)14:38
*** jmckind has joined #openstack-meeting-314:38
njohnston__no, it would just become a mod to DSCP14:38
ajo_davidsha, is right, the problem becomes more vicious when we have external extensions, but in-tree extension know about each other, generally14:38
njohnston__so if you set DSCP mark  16 the flow would set nw_tos to 6414:38
slaweqnjohnston__: ok, I'm not very familiar with that, thx for explanation14:39
njohnston__but if you set DSCP 16 and ECN enabled then the flow would set nw_tos to 6514:39
davidshaslaweq: dscp modifies the packet at the highest priority and the resubmits it back to the table for more processing.14:39
ajo_njohnston_, yes, we may need something that sets a bit,14:39
njohnston__so a single flow rule, with the correct nw_tos value that is the combination of ECN and DSCP values14:39
slaweqok, that sounds good easy then :)14:40
davidshanjohnston__: I think there is another command for setting the ecn bits14:40
mfranc213_that would be better, if there is14:40
njohnston__davidsha: I defer to your greater knowledge then :-)14:40
ajo_yeah, I think there was something like that14:40
davidshanjohnston__: I'll double check :)14:40
ajo_but, let's not use more minutes on ECN until that's clear :D14:40
njohnston__ok, back to
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Reedip (reedip-banerjee)14:41
njohnston__I don't have a good grasp on what the status and/or trajectory is for this14:41
ajo_      mod_nw_ecn:ecn14:41
ajo_                     Sets  the ECN bits in the IPv4 ToS or IPv6 traffic class field to ecn, which must be a value between 0 and 3, inclusive.  This action14:41
ajo_                     does not modify the six most significant bits of the field (the DSCP bits).14:41
davidshayup: mod_nw_ecn14:41
*** sdake_ has joined #openstack-meeting-314:42
davidshaIt can also set the congestion bit too which I didn't expect14:42
njohnston__moving on to14:42
openstackLaunchpad bug 1527671 in neutron "[RFE] traffic classification in Neutron QoS" [Wishlist,Incomplete]14:42
njohnston__Looks like this was split to be two bugs, and this one was reduced to just the traffic classification part.14:42
njohnston__I believe this has been an area of activity of late14:43
ajo_davidsha, was looking at this, and we had a meeting with the flow-classifier guys from SFC14:43
ajo_let me look for the meeting link14:43
*** sdake has quit IRC14:43
ajo_an RFE will be filled, to ask for flow classifier objects in the core14:44
*** haleyb_ is now known as haleyb14:44
ajo_and an API, I gues14:44
ajo_that discussion may take some time14:44
ajo_davidsha, did I miss anything?14:44
davidshaajo_: No thats pretty much it14:45
ajo_ok, njohnston_ , next? :)14:45
openstackLaunchpad bug 1557457 in neutron "[RFE] rate-limit external connectivity traffic." [Wishlist,Incomplete]14:45
njohnston__I guess this is already marked as incomplete, moving on14:46
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Confirmed] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:46
njohnston__Thanks Rodolfo for stepping in and taking this on!  r14:46
njohnston__Spec filed:
ralonsohPlease, take a look at the spec14:46
ajo_ohh, nice14:46
ajo_I didn't notice14:46
njohnston__It's good stuff14:47
hichiharaI guess that we need to propose anything(about generic resource pool) into nova so that VM is scheduled aware minimum bandwidth.14:47
hichiharaDo we have work items in nova side about minimum bandwidth feature?14:47
ralonsohNot now, but the scheduler will have the generic resource pool14:48
ajo_hichihara, we have another RFE for that14:48
ajo_I discussed with them14:48
ralonsohI will propose a spec for the scheduler14:48
hichiharaajo_: link?14:48
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,New]14:49
davidshaJust with the ingress bandwidth limit and bandwidth guarantees. If we mark the bandwidth limit on the QoS table, will that limit traffic going in and out of those Queues?14:49
hichiharaajo_: Thank you!14:49
ajo_hichihara, see link [3]14:49
ajo_to my understanding, we need their framework to be up14:49
ajo_and then we're just another resource14:49
ajo_I was lately thinking, that we can separate per direction14:49
ajo_and may be per physnet14:50
njohnston__last RFE14:50
openstackLaunchpad bug 1580149 in neutron "[RFE] Rename API options related to QoS bandwidth limit rule" [Wishlist,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:50
ajo_hichihara, , ralonsoh follow the thread and see if there's something missing,14:50
ajo_btw hi ralonsoh !!! I didnt' see you were on IRC :D14:50
ralonsohajo_: ok14:50
slaweqI didn't start work on it yet14:50
ajo_thanks for taking on the min bw :D !!!14:51
hichiharaajo_: Thanks, I will catch up it. and also I will review the spec.14:51
*** cloudtrainme has joined #openstack-meeting-314:51
ralonsohajo_: no problem!14:51
njohnston__Last comment on 1580149, slaweq seemed to defer to ajo_ and ihrachys to confirm his position14:51
njohnston__slaweq: Are you good to start regardless, or would it be better to get more comments in the bug?14:52
slaweqyes, it would be great if You can confirm it14:52
ajo_slaweq, about that (1580149) I see armax chimed In, I'll try to discuss with him14:52
ajo_to see if he has a different opinion14:52
slaweqI will start it soon14:52
slaweqok, thx ajo_14:52
njohnston__#topic Other Changes14:52
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"14:52
njohnston__That is the docs change slaweq mentioned earlier: "[networking] Add information about default burst value"14:53
*** coolsvap has quit IRC14:53
njohnston__#topic Open Discussion14:53
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:53
slaweqnjohnston__: earlier I mentioned other change (which is merged already) :)14:53
njohnston__slaweq: Ah yes I got them crossed in my head :-)14:53
slaweqthis one is related to patch:
*** coolsvap has joined #openstack-meeting-314:54
ajo_thanks again mfranc213_  ;)14:54
njohnston__Anything else that folks want to discuss?  Or any changes that aren't on my tracking radar?14:54
davidshaJust the previous comment I made:14:54
davidsha"Just with the ingress bandwidth limit and bandwidth guarantees. If we mark the bandwidth limit on the QoS table, will that limit traffic going in and out of those Queues?"14:55
ajo_davidsha, what do you mean?14:55
davidshaajo_: So the Queues are tied to the QoS table and I'm wondering if the bandwidth limit on the QoS table in slaweq patch will interfere with the min guarantee in ralonsoh14:57
ajo_ah, no14:57
ajo_davidsha, they are queues in different ponts14:57
*** tomasztrebski has joined #openstack-meeting-314:57
*** dedery has joined #openstack-meeting-314:58
*** koji has joined #openstack-meeting-314:58
ajo_btw, ralonsoh I have to share with you the ideas they're having in OVN,14:58
*** Kamil_ has joined #openstack-meeting-314:58
ajo_may be they have a way to do it without patch_ports -> veths14:58
*** fabiog has joined #openstack-meeting-314:58
* njohnston__ is interested in that as well14:58
ajo_instead of setting the queues in the veths, they set the queues in the physical interfaces of the host14:58
ralonsohthat could be a good solution14:59
ajo_and... I don't know how... they connect the queue to ovs/openflow (To have the queue id)14:59
*** FlintHPE has joined #openstack-meeting-314:59
ajo_ralonsoh, that works for egress, but for min bw ingress.. it may not work... :)14:59
ajo_it's better if we don't affect performance :)14:59
njohnston__time -1, any last minute items?14:59
ajo_we can make the veths if people has interest on min bw ingress14:59
ralonsohi know, I need to modify now the flows incoming in the OVS14:59
*** matrohon has quit IRC15:00
ajo_ralonsoh, lots of fun, I will try to help on that15:00
*** qwebirc214 has joined #openstack-meeting-315:00
ajo_I think we should endmeeting15:00
ralonsohajo_: no problem!15:00
njohnston__All right, that's time?  All right, have a wonderful day and talk to you in 2 weeks.15:00
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Wed May 18 15:00:28 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
ajo_thanks everybody  :D15:00
*** slaweq has quit IRC15:00
njohnston__thanks all!15:00
ajo_thank you njohnston_  :)15:00
*** shamail has joined #openstack-meeting-315:01
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed May 18 15:01:12 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmuthhi everyone15:01
rhochmuthagenda is at,
*** tonytan4ever has quit IRC15:01
rhochmuthAgenda for Wednesday May 18, 2016 (15:00 UTC)15:01
rhochmuth1. Using Severity#CRITICAL for so called "latched" alarms instead of extending data model15:01
rhochmuth2. Mid-cycle meetup15:01
rhochmuth3. Vitrage update (Syd)15:01
rhochmuth4. monasca-transform update15:01
rhochmuth5. monasca-analytics update15:01
*** dedery_ has quit IRC15:01
rhochmuth6. State of the gate?15:01
rhochmuth7. Update on dimensions resource?15:01
rhochmuth8. Update on api caching?15:01
fabiogis FlintHPE the Flint I know?15:01
*** slogan has joined #openstack-meeting-315:01
rhochmuthbefore we get started, is there anything left over from last weeek15:02
FlintHPEfabiog, yep!15:02
rhochmuththe last i recall i frantically ended the meeting15:02
*** jobrs has joined #openstack-meeting-315:02
rhochmuthok, then let's work through the agenda15:02
rhochmuthand maybe we'll have time left over this week15:03
rhochmuth#topic 1. Using Severity#CRITICAL for so called "latched" alarms instead of extending data model15:03
*** openstack changes topic to "1. Using Severity#CRITICAL for so called "latched" alarms instead of extending data model (Meeting topic: monasca)"15:03
rhochmuthtomasz: is that from you?15:03
*** tellesnobrega is now known as tellesnobrega_af15:03
*** anilvenkata has quit IRC15:04
*** mfranc213_ has quit IRC15:04
*** njohnston_ has quit IRC15:04
tomasztrebskiyes, it's mine15:04
*** CaoWei has joined #openstack-meeting-315:04
*** c64cosmin has quit IRC15:04
*** fawadkhaliq has quit IRC15:04
tomasztrebskiI've been thinking how to implement that and such suggestion came up - instead of extending alarm definition model15:04
*** numans has quit IRC15:05
rhochmuthhmmm, can't say i'm in favor of it15:05
rhochmuthseems like we are overriding a parameter15:05
*** banix has quit IRC15:05
*** jayahn has joined #openstack-meeting-315:05
tomasztrebskiwhy ? it's more like add some meaning to CRITICAL alarms15:05
*** cbouch_ has joined #openstack-meeting-315:05
*** salv-orlando has quit IRC15:05
*** cbouch__ has quit IRC15:05
*** hichihara has quit IRC15:05
tomasztrebskithe main idea is to have alarms that require operator attention to leave ALARM state15:06
*** Sukhdev has joined #openstack-meeting-315:06
*** armax has joined #openstack-meeting-315:06
tomasztrebskiattention is likely needed if something so bad happened that it'd be best to check and double check15:06
*** donghao has quit IRC15:07
tomasztrebskithus CRITICAL severity15:07
rhochmuththere are two things, the severity of an alarm, and whether it should stay in the ALARM state, after it has transitioned to it15:07
tomasztrebskianyway that's a suggestion that would follow severity quite nice15:07
rhochmuthseems like two different things that shouldn't be connected15:07
*** mfranc213 has joined #openstack-meeting-315:07
rhochmuthand break compatibilty, unless we added a CRITICLA_AND_LATCHED severity15:08
*** woodster_ has joined #openstack-meeting-315:08
rhochmuthdoes anyone else want to comment?15:09
rhochmuthor have any quesions?15:09
*** ralonsoh has quit IRC15:09
tomasztrebskiguess not, ok I will think on this a bit more - anyway idea of using severity here seems a nice one, thanks to recent schema changes it'd be easy to add new severity15:11
*** doug-fish has joined #openstack-meeting-315:11
*** ericksonsantos_ has joined #openstack-meeting-315:11
tomasztrebskiif that one is rejected, we will go with extending model directly15:11
*** mrmartin has quit IRC15:11
jayahnfor me, i would like have severity of an alarm as it is. IMHO, to decide it should be latched to get more attention up to operators to decide. it is not directly related to the severity. we have different process to do that outside of monasca.15:12
rhochmuthtomasz: i think we should extend the alarm definition with the "latched" field15:12
jayahna bit late.. sorry. i just joined. got some time to follow-up15:12
rhochmuthjayahn: i agree15:12
tomasztrebskinp, thx for comment15:12
*** mrmartin has joined #openstack-meeting-315:13
rhochmuthalthough, i'm not sure "latched" is a great name, but it is certainly better than existentialist15:13
*** MeganR has joined #openstack-meeting-315:13
tomasztrebskiok, so I guess that is settled - I am still learning what particular pieces means so this is nice comment about correct usage of specific properties15:13
*** andreas_s has quit IRC15:13
tomasztrebskiyes, latched isn't that great15:13
tomasztrebskiI will come up with better one :)15:13
jayahnget "right name" is always the most difficult thing. :)15:13
rhochmuthtomasz: i'm still trying to get used to deterministic15:14
rhochmuthjust check with us before making all the code changes, it is a bit easier that way15:14
tomasztrebskikk, I will discuss that15:14
rhochmuth#agenda Mid-cycle meetup15:15
rhochmuthi haven't heard back yet15:15
rhochmuthi'll need to ping my mgmt again on travel approval15:15
rhochmuththank you doodle master15:15
fabiogright now we have 5 people good to attend SJC and 5 good to attend Munich15:16
fabiogso we are in deadlockj15:16
jayahn:) we need tie braker.15:16
sloganmy manager said I can travel as long as I can get there by bicycle15:16
fabiogso slogan SJC is your only option :-)15:16
sloganI could do that15:16
fabiogyou can always hold to a truck on Interstate 5 :-)15:17
*** doug-fish has quit IRC15:17
rhochmuththat's a long bike ride from san diego15:17
fabiogslogan: I'll give you a yellow shirt if you do it :-)15:17
*** claudiub has joined #openstack-meeting-315:18
*** fwdit has quit IRC15:18
rhochmuthvery difficult to plan the mid-cycles15:18
rhochmuthwe don't have a huge eco-system15:18
*** marios|call is now known as marios15:19
rhochmuthso if we can't all get there, it becomes a relatively small meetup without enoguh representation15:19
* claudiub sneaks in and waves15:19
Kamil_i don't think that we (fujitsu) will get an approval to travel to SJC15:19
fabiogrhochmuth: the other option is to do virtual again15:19
sloganwith something like webex?15:20
fabiogI can host it15:20
rhochmuthyes, i would lean towards that as i think inclusion is more important15:20
jayahnI have to find three reasons to travel to SJC. I managed to find two till now. :)15:20
*** dedery has quit IRC15:20
rhochmuththe beer is better in munich15:20
Kamil_and bigger15:21
hosanaiand reasonable15:21
fabioglet's give a deadline15:21
*** ajmiller has joined #openstack-meeting-315:21
rhochmuthso, after teh barcelona summit we won't have to plan on mid-cycles15:21
fabiogend of month to cast your preferences15:21
rhochmuthit will all be planned15:21
rhochmuthfabiog: sounds good15:22
fabiogand then we decide where to happen. SJC, Munich or virtual15:22
rhochmuthanother two weeks to figure out, but it is looking like virtual at this point15:22
*** toddjohn_ has quit IRC15:22
rhochmuth#agenda 3. Vitrage update (Syd)15:23
*** xrollla has quit IRC15:23
fabiogwhat about we do it in SJC and we have morning sessions that are virtual15:23
*** fawadkhaliq has joined #openstack-meeting-315:23
fabiogI can get a Telepresence room15:23
sloganhad an information exchange meeting with nokia/vitrage yesterday morning15:23
*** fawadkhaliq has quit IRC15:23
bklei+1 on that15:23
sloganwhat they seem to be about is graphically rendering actual topologies of the network (down to the port level)15:23
rhochmuthsorry, changed topic too soon15:23
rhochmuthfabiog: that might be a good option too15:23
fabiogrhochmuth: let's plan for that if Munich does not materialize15:24
rhochmuthok, thanks fabiog15:24
*** ajmiller_ has joined #openstack-meeting-315:24
rhochmuthwill change topic now15:24
fabiogrhochmuth: np15:24
rhochmuthback to you slogan15:24
rhochmuthsorry for interrupt15:24
sloganhad an information exchange meeting with nokia/vitrage yesterday morning15:24
sloganwhat they seem to be about is graphically rendering actual topologies of the network (down to the port level)15:24
sloganand showing state (up, down, critical, etc) using colors15:24
sloganthere is a yaml language for defining rules/policy that leads to these state changes15:24
*** doug-fis_ has joined #openstack-meeting-315:25
sloganthey have an API that is of yet undocumented for pushing data into vitrage15:25
sloganmy idea - broadview-collector pushes raw data to monasca, and a second broadview-collector plugin pushes to vitrage15:25
*** doug-fis_ has quit IRC15:25
*** njohnston__ is now known as njohnston15:25
sloganvitrage yaml logic is used to define policy that is based on specific network deployments (hyper-converged, data storage network, tenant network) as needed to get a "color"15:25
sloganvitrage user sees a network switch go "yellow" and then refers to monasca-based grafana UI to get more details15:25
*** doug-fis_ has joined #openstack-meeting-315:25
sloganthat's it15:25
rhochmuthso, you don't end up pushing metrics to vitrage, just alarms, correct?15:25
*** toddjohn_ has joined #openstack-meeting-315:26
*** shamail has quit IRC15:26
sloganpossibly I do some pre-preocessing in broadview-collector and just send an alarm, yes15:26
sloganor, the yaml logic is used to determine that alarm15:26
slogannot sure yet15:26
rhochmuthi don't see a problem with broadview sending metrics to monasca15:26
rhochmuthmonasca evaluating an alarm15:26
rhochmuthand then notifying vitrage15:27
sloganand then that goes to vitrage?15:27
sloganI see, yes15:27
rhochmuththen vitrage evaluates rules15:27
sloganthat would work too15:27
*** ajmiller has quit IRC15:27
sloganwhat's interesting is their docuemntation page features networking, they are clearly interested in that ascpect ofg things15:27
rhochmuthso, i think it all would work well15:27
*** jschwarz_ has quit IRC15:28
*** toddjoh__ has joined #openstack-meeting-315:28
sloganI'm waiting for the documentation15:28
*** ccamacho has quit IRC15:28
sloganthey are pending on that15:28
rhochmuthhow do you specify to vitrage that this VM is somehow associated with a switch15:28
sloganthey have a way to specify graphs and relate things15:28
rhochmuthphysical switch that is15:28
sloganyeah, there is a topology language, yaml I think for doing that15:29
sloganyou define nodes/vertices and then dependencies/edges15:29
sloganI've only just glanced at it all15:29
*** abalutoiu has joined #openstack-meeting-315:30
*** notmorgan has joined #openstack-meeting-315:30
*** ujuc has joined #openstack-meeting-315:30
*** toddjohn_ has quit IRC15:30
rhochmuthit sounds like an interesting use case15:30
*** mhoppal has joined #openstack-meeting-315:30
rhochmuthbut getting all the data into vitrage i'm wondering about15:30
sloganso, I think next step is for me to look deeper, but let's continue to feature monasca in my work, if monasca has the raw data, and an alarm to trigger a push to vitrage, I'm great with that15:30
*** salv-orlando has joined #openstack-meeting-315:31
*** bklei has quit IRC15:31
sloganI'll take the lead to lean more about all of it15:31
sloganhelp them understand monasca as needed15:31
rhochmuthi'll try and start taking a closer look, as soon as i complete some reviews15:31
sloganthey're smart people, hopefully this isn't a big deal15:31
*** bklei has joined #openstack-meeting-315:31
sloganI mentioned it would be nice to have something for barcelona15:32
rhochmuthif they are smart, i don't want to work with them15:32
rhochmuthsorry, i don't think that is what you meant15:32
sloganI like very much the idea of a three-headed presentation that shows end to end what can be done15:32
*** belmoreira has quit IRC15:32
sloganwhat they are not about is doing any actions15:33
sloganit's just rendering the state15:33
sloganmaybe there is a fourth project like congress that plays a further role15:33
*** bklei has quit IRC15:33
rhochmuthwe had talked about vitrage creatign alarms back in monasca15:33
sloganhow did they receive it?15:33
*** bklei has joined #openstack-meeting-315:34
*** Sukhdev has quit IRC15:34
rhochmuthit seems like a general capability that we want/should have in monasca15:34
*** mbound has joined #openstack-meeting-315:34
rhochmuththey were pushing for the change15:34
sloganthe thing that seemed interesting about their yaml code was it might be a way to express various use cases for networking15:34
*** fawadkhaliq has joined #openstack-meeting-315:34
rhochmuthso, besides slogan and me, is anyone else interested in this topic?15:34
sloganlike, I could have yaml that is tuned to a specific networking use case like storage in a leaf spine CLOS network15:34
sloganzzzzzzzz :-)15:35
rhochmuthjust checking15:35
*** moshele has left #openstack-meeting-315:35
sloganokay, enough I suppose for now15:35
rhochmuthok, probably should wrap-up15:35
jayahnprobably us. we are developing an anlaytics platform to gether all the network related data (packet, flow, etc). we have a plan to push that data into monsca.15:35
rhochmuththanks slogan15:35
jayahnit sounds very similar to what virtage does.15:36
claudiubhi. I also have a request / set of questions.15:36
sloganjayahn: what is this platform, and where are you from?15:36
jayahnhi, i am from sk telecom.15:36
sloganhi :-)15:36
jayahnplatform is in-house development15:36
rhochmuthcladiub: just trying to get through some topics first15:37
slogansearch broadview in github if you want a background in what we are pushing off switch about our switching silicon15:37
jayahnall the network data - alnaytics platform - (push data) - monasca - (consum data) - visual app to show network statues in 3D.15:38
jayahni know. we are looking into broadview in github. :)15:38
*** ajmiller_ has quit IRC15:38
claudiubrhochmuth: sure, i thought that you were going to end the meeting. :)15:38
rhochmuthjayahn: slogan is the developer on broadview15:38
*** mhoppal has quit IRC15:39
*** mhoppal has joined #openstack-meeting-315:39
*** CaoWei has quit IRC15:39
rhochmuthi'm going to switch topics if that is ok?15:39
jayahnokay. that is great. I will contact you if we have any question on broadview-collector, or anyting related to that :)15:39
rhochmuth#topic monasca-transform15:39
*** openstack changes topic to "monasca-transform (Meeting topic: monasca)"15:39
*** CaoWei has joined #openstack-meeting-315:39
hosanaijayahn: why you push analyzed data to monasca?15:39
rhochmuththx jayahn15:39
*** ericksonsantos_ has quit IRC15:40
rhochmuthhas anyone looked at monasca-transform15:40
rhochmuthi'm jsut getting started15:40
FlintHPEhi all, Ashwin couldn't make the meeting today.  We have a Monasca-Transform review up, but it's currently set to "work in progress" while we wrap up a few things.15:41
rhochmuththanks FlintHPE15:41
rhochmuthi will hopeflly get this reviewed and running over today, tomorrow, friday15:41
*** salv-orlando has quit IRC15:41
*** ajmiller has joined #openstack-meeting-315:42
*** salv-orlando has joined #openstack-meeting-315:42
rhochmuthif there are no questions and/or comments, then we should move on15:42
rhochmuthnote, review is at,
rhochmuth#topic monasca-analytics15:43
*** openstack changes topic to "monasca-analytics (Meeting topic: monasca)"15:43
rhochmuthmonasca-analytics is in a similar state15:43
*** nkrinner is now known as nkrinner_afk15:43
*** catherineD has joined #openstack-meeting-315:43
rhochmuthi don't think any of the hpe labs folks are here15:43
rhochmuththanks for reviewing hosanai15:44
*** dwalleck has joined #openstack-meeting-315:44
rhochmuthit sounds like in general you are positive about the initial commit15:44
rhochmuthhave you tried running it15:44
*** jmckind_ has joined #openstack-meeting-315:44
hosanaiunittest worked but15:45
hosanaispark didn't start in my env now.15:45
rhochmuththat sounds like fun to debuf15:45
hosanaiI wrote a question on the comment to you.15:45
rhochmuthyou might be able to use the devstack plugin that monasca-transform has created as that install spark15:46
rhochmuthFlintHPE: does that sound correct15:46
FlintHPEseems like that might work15:46
hosanaii don't have a problem for installing spark15:46
hosanaiit seems to be setting of port...15:47
hosanaii would like to know conditions for merging initial code.15:48
*** mhoppal has quit IRC15:48
*** jmckind has quit IRC15:48
rhochmuthnot sure i've discussed, but i would like to see if few logitical issues addressed15:49
rhochmuthalso, i would like to have run it to see what it does15:49
rhochmuthand if it works15:49
hosanaii asked it in gerrit please check it.15:49
rhochmuthhosanai: ok15:49
rhochmuthhosanai, are you in favor of mergingin now then?15:50
rhochmuthor are you interested in seeing other areas addressed?15:50
*** zz_dimtruck is now known as dimtruck15:51
hosanairhochmuth: if possible, but i think some comments need to fix before merging.15:51
rhochmuthok, thanks, i'll look at your comments today15:51
hosanaithanks in advance :-)15:51
rhochmuthgoing to move on now15:51
rhochmuth#topic State of the gate?15:51
*** openstack changes topic to "State of the gate? (Meeting topic: monasca)"15:51
*** bpokorny has joined #openstack-meeting-315:51
rhochmuthDoes anyone know the state of the gate15:52
*** bpokorny has quit IRC15:52
*** vhoward has quit IRC15:52
rhochmuthwe had several issues impact us over the last few days15:52
rhochmuthglobal requirements moved the kafka-python and falcon libraries15:52
rhochmuthalso, we had an issue in DevStack with installing Kafka15:52
rhochmuthso, upstream gate was down15:53
rhochmuthi'm not sure if it is up yet15:53
tomasztrebskimy idea for fixing falcon was taken by Ryan I guess15:53
tomasztrebskiso that one is fixed15:53
*** tonytan4ever has joined #openstack-meeting-315:53
rhochmuthtomasz: i think joe, but he had to combine two reviews together to get gate to pass15:53
rhochmuthhe was able to get the combined review in15:54
tomasztrebskiyes, Joe :), anyway good thing that it passed15:54
rhochmuthhowever, it looked like there were still issues15:54
rhochmuthanyway, hoping it all gets fixed this morning15:54
*** Rockyg has joined #openstack-meeting-315:55
bkleihoping so15:55
rhochmuth#topic Update on dimensions resource?15:55
*** openstack changes topic to "Update on dimensions resource? (Meeting topic: monasca)"15:55
*** Sukhdev has joined #openstack-meeting-315:55
rhochmuthi'm not aware of anyone woriing on the dimensions resource yet15:55
bkleithat's me -- curious if anyone has started that?15:55
rhochmuthnot yet15:55
*** sverma has quit IRC15:56
rhochmuth#topic Update on api caching?15:56
bkleistill plans for that?15:56
*** openstack changes topic to "Update on api caching? (Meeting topic: monasca)"15:56
*** lhartal has quit IRC15:56
rhochmuththere are plans for dimensions resource, but no commitments yet15:56
rhochmuthhave you tried multipel metrics15:56
*** bpokorny has joined #openstack-meeting-315:57
bkleiyes -- but holding off on calling it for the concurrent exception fix15:57
*** gema has joined #openstack-meeting-315:57
rhochmuthi was hoping to get multiple metrics done and tested before looking at anythign like api caching15:57
rhochmuthahh yes, gate15:57
*** ccamacho has joined #openstack-meeting-315:57
rhochmuthwe can't get that bug resolved unless gate is fixed15:57
rhochmuthclaudiub: you still there?15:58
rhochmuthwe're going to run out of time15:58
rhochmuthwe might need to move to openstack-monasca15:58
rhochmuthbut please proceed15:59
claudiubwe've talked brifly during the Summit about adding WIndows support for monasca-agent. I've submitted a blueprint:
claudiubbasically, it's about solving differences between WIndows  and Linux, e.g. using stuff that doesn't exist on Windows that causes the services to die.15:59
*** catherineD has left #openstack-meeting-315:59
rhochmuthi'll review and also get several more from hpe to take a look that work on the agent a lot15:59
*** catherineD has joined #openstack-meeting-315:59
claudiube.g. signal.SIGUSR115:59
*** mbound has quit IRC16:00
*** ametts has joined #openstack-meeting-316:00
claudiubbut I do have a couple of questions16:00
claudiubon a few things16:00
rhochmuthso, i', going to have to end the meeting16:00
rhochmuthonly one hour16:00
claudiubbut we can talk about them in the #openstack-monasca chanel16:00
rhochmuthbut i'll move to #openstack-monasca16:00
rhochmuthok everyone, have to shut it down16:00
*** cjvolzka has joined #openstack-meeting-316:00
*** qwebirc214 has quit IRC16:00
hosanaithanks bye!16:01
*** openstack changes topic to "OpenStack Meetings ||"16:01
openstackMeeting ended Wed May 18 16:01:05 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:01
*** shamail has joined #openstack-meeting-316:01
openstackMinutes (text):
*** koji has quit IRC16:01
*** hosanai has left #openstack-meeting-316:01
hogepodge#startmeeting defcore16:01
*** bklei has quit IRC16:01
openstackMeeting started Wed May 18 16:01:28 2016 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
sloganjayahn: you can contact me at syd.logan@broadcom.com16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
*** Kamil_ has left #openstack-meeting-316:01
hogepodge#topic rollcall16:01
*** openstack changes topic to "rollcall (Meeting topic: defcore)"16:01
AlanClarko/ (wanting to listen in)16:02
hogepodgeNote that markvoelker and eglute are both out again this week, but will be returning soon.16:02
hogepodge#link agenda
*** FlintHPE has quit IRC16:02
hogepodge#topic test spec16:03
*** openstack changes topic to "test spec (Meeting topic: defcore)"16:03
hogepodgegema has written up a test spec proposal16:03
gemaI think I captured the overall consensus of the comments, but please review16:03
gemawe may be missing something16:03
gema(it feels short)16:04
*** davidsha has quit IRC16:04
dwalleckwill do, I'll have a look today16:04
*** fabiog has quit IRC16:04
gemadwalleck: thanks16:04
Rockygme too.16:04
gemaRockyg: thanks16:04
*** jobrs has quit IRC16:04
gemahogepodge: I don't have anything else to discuss16:04
Rockygalso, we can add more details later.  this can be a living doc.16:04
VanLI didn't see anything about atomicity16:05
gemaVanL: dwalleck requested to rephrase16:05
hogepodgeAnyone else have any comments on this for the meeting? Otherwise, leave reviews. I expect that we'll need to iterate on it.16:05
gemaand I did16:05
catherineDshould commends be added to the review patch and not  the etherpad from now on?16:05
*** jayahn has quit IRC16:05
gemacatherineD: yes, please16:05
catherineDcommends --> comments16:05
hogepodgecatherineD: yeah, comments should be in the review16:05
dwalleckI think "targetted to test and validate one capability" was the better translation of atomic16:05
gemadwalleck: I think so to, so went with it on the final version16:06
hogepodgeVanL: the work 'atom' has caused heartburn, but we can probably find a way to work it back in16:06
*** jlanoux has quit IRC16:06
VanLI like the "targeted...." language, but "atomic" has an outside meaning that I like and I think is useful in this context16:06
gemaVanL: the problem is that it is overloaded16:07
gemameans different things to different people16:07
catherineDI am not sure how DefCore would differentiate tests vs scenario tests --> to me they are all tests to test a certain capability16:07
*** CaoWei has quit IRC16:07
hogepodgegema: VanL: would it be useful to add a definition, either to the spec or to the defcore lexicon?16:07
gemacatherineD: we would when we choose the tests for the capabilities16:07
VanLhogepodge: Yes, I think that would be helpful16:07
hogepodgecatherineD: If I understand correctly, we're not choosing scenario tests right now, only api tests. Scenario would be a future addition16:08
gemahogepodge: probably, but I like the new wording better so I'd like to hear (in a gerrit comment) how VanL wants to change the wording to include atomicity again16:08
VanLcatherineD: I think that the way to address scenario vs functional tests is by separating out the fixture/teardown from the "test"16:08
catherineDgema: how?16:08
gemacatherineD: by reading the tests and understading them (I thought that's what we are supposed to do)16:09
shamailHi everyone o/16:09
VanLSo a scenario test includes >1 capability/API in the "test" portion16:09
gemashamail: o/16:09
dwalleckscenario tests also have a very specific meaning in Tempest terms16:09
catherineDdwalleck: + exactly ...16:09
*** tmorin has quit IRC16:10
dwalleckThere are CRUD tests that exist that are not in the scenario tests package, but one could argue are scenarios16:10
catherineDso since this is a spec we should be clear on  our terminology16:10
gemacatherineD: absolutely, so how do we make that part clearer16:10
RockygSo, a glossary is key/\.16:10
dwalleckBut I like the idea of handling those distinctions in the spec. It will save us future headaches  :-)16:11
VanLI think it makes for a clear distinction16:11
VanLAn "atomic" test involves only 1 API16:11
*** shamail has left #openstack-meeting-316:11
*** shamail has joined #openstack-meeting-316:11
catherineDdwalleck: exactly...16:11
VanLAny test with >1 API is a "scenario" test16:11
*** mbound has joined #openstack-meeting-316:11
gemaVanL: but is it?16:12
*** CaoWei has joined #openstack-meeting-316:12
Rockygany test that *validates* more than one api...16:12
gemaVanL: a scenario test is one that covers end to end functionality16:12
catherineDVanL: in that case the spec would be written that a test can teat one API or more16:12
hogepodgeI still think it's an ideal that we can't necessarily reach. Any API test that checks creation or deletion will require multiple API calls, including listing.16:12
catherineDget rid of the headache of tests vs scenario tests16:12
*** mbound has quit IRC16:13
VanLgema, catherineD: You can string together N atomic items (per definitions above) to address CRUD, end-to-end, etc.16:13
*** mbound has joined #openstack-meeting-316:13
catherineDhogepodge: foundamental issue here is do we allow testing of multiple APIs in a test16:13
VanLhogepodge: That is why setup/teardown are programmatically excluded from the definition of "test"16:13
gemacan we put this conversation on gerrit so I can get a better idea on what I should be writting?16:13
gemaI have the impression we are going around in circles again16:13
VanLAnd can be swapped as needed16:14
hogepodgeBut I don't want tests that reach outside the intent of the test, say image creation relying on volume operations. That would be a clear violation of what we're trying to accomplish16:14
dwalleckMy original point was that the test itself (not including fixtures) should test one API16:14
gemadwalleck: mine was that too16:14
dwalleckGoing by the tradition Arrange/Act/Assert model16:14
*** CaoWei has quit IRC16:14
Rockygdwalleck, gema ++16:14
gemahogepodge: that's a different point I think, I will capture it (but make sure it ends up in gerrit)16:15
dwalleckSo that the actual test function is doing one thing. I think we're all saying the same thing, but we may need to clarify setup vs actual test functions16:15
gemahogepodge: it's important16:15
gemaare we at a point where, relying only in required capabilities, we can set up and tear down all the tests?16:16
catherineDdwalleck: gema: so in the case of CRUD of compute ... we would have 4 tests 1) create server  2) list server  3) update server 4) remove ?  .. that is 4 tests to test CRUD capability16:16
gemacatherineD: yes16:16
*** iyamahat has joined #openstack-meeting-316:16
gemacatherineD: ideally there would be some test trying to create a server that fails16:17
gemasome wrong update call16:17
gemato make it better coverage16:17
catherineDthe 4 tests are independance16:17
dwalleckcatherineD: That is normally how I would do it, but at the summit I think we discussed making a special case for basic CRUD activity16:18
gemadwalleck: and that would be the scenario tests?16:18
catherineDthen do we still need to explicitely spell out item 3 in the spec ..16:18
*** ericksonsantos has joined #openstack-meeting-316:18
woodster_catherineD: just making all four tests in your example would start with one or more created servers, then each tear them down again correct?16:19
gemawoodster_: ideally16:19
dwalleckgema: Not necessarily. I know Neutron and I think some compute tests in the tempest.api package that do CRUD16:19
woodster_gema: cool make sense. Tests might take longer that way of course, but isolation is essential16:19
gemadwalleck: I still don't know why we are mixing CRUD apis with tests16:20
hogepodgewe have some tests that pair up capabilities, particularly create delete
*** anteaya has quit IRC16:21
gemadwalleck: to me a good scenario test would be one that crosses boundaries between APIs16:21
hogepodge(I just grabbed that as a random example based on name)16:21
dwalleckhogepodge: yes, that :-)16:21
catherineDhogepodge: so that test violate our spec?16:21
gemadwalleck: set up VM, assign floating ip, make sure you can connect, etc16:21
catherineDsince it is one test that tests more than one API16:22
hogepodgeqa might argue that pairing that doesn't significantly change the scope of the testing and improves gate performance (as a straw man argument)16:22
dwalleckgema: I agree, but we're mixing terms here. Tempest has a specific definition of a scenario test. I'm wanting to make sure the spec is clear16:22
gemadwalleck: ok, you want me to use the same terminology as tempest then?16:22
hogepodgeso it would violate the word of the spec, but not the spirit of what we're trying to do imo16:22
dwalleckIf we're using the general concept of a scenario test or a Tempest scenario test16:22
gemaor are we trying to make things better in the tempest arena as well?16:22
gemahogepodge: agreed, that test verifies two different capabilities16:23
Rockyggema, would love that, but that's heavy lifting ;-)16:23
VanLdwalleck: We should define what we mean for *our* purposes, then we can explain how that relates to tempest as appropriate16:23
gemaRockyg: I love crossfit :P16:23
catherineDhogepodge: gema: so once our spec merged ... would DefCore remove all tests that violate the test spec?16:23
*** jmckind_ has quit IRC16:23
dwalleckgema: Not necessarily. I think the Tempest team doesn't necessarily like their scenario tests. I just want the spec to be clear so people don't get confused. Adding "scenario" that to a lexicon for the doc would help16:24
gemacatherineD: we can fix them16:24
gemacatherineD: once we agree on what a good test looks like16:24
hogepodgecatherineD: I don't know. I think it would present a case for flagging them, but I would wait until a vendor requested it16:24
catherineDgema: ok16:24
gemacatherineD: which I don't think we are very close to yet :)16:24
gemadwalleck: ok, will try to make that clearer16:25
catherineDgema: that is what I would like to understand ... once the spec is in ... we need to abide to the spec ..16:25
dwalleckgema: No worries!16:25
gemacatherineD: sure, we can either say from now on all the tests we add need to abide by the rules or we can say, we have all these tests taht don't meet the standard and need fixing16:25
gemacatherineD: either way works, I think16:25
gemacatherineD: eventually we will get there16:26
catherineDback to the spec ... if we allow item 3 in the patch ... we would accept by calssifying it as a "scenario" test?16:26
hogepodgegema: I don't want to throw out tests that are valuable on technicalities.16:26
gemahogepodge: me neither16:26
hogepodgegema: and artificially weaken the standard16:26
Rockyggema,  ++16:26
gemahogepodge: I want to fix them16:26
gemaif they need fixing16:26
gemahogepodge: and if we feel they don't need fixing, we've done something wrong on the spec16:27
RockygFix or replace16:27
gemacatherineD: all those examples are useful, can you add them to gerrit16:27
dwalleckgema: I think we will need feedback from the QA team on the fixing bits. I'd like to make sure we're in alignment there16:27
gemaso I can think them through?16:27
*** dimtruck is now known as zz_dimtruck16:27
gemadwalleck: yep16:27
*** mrmartin has quit IRC16:27
VanLWe need to understand where we want to end up in order to understand what is broken, the way in which it is broken, and the steps needed to fix16:28
catherineDMy concern is with item 1, 2 and 3 included in the spec .... we could be business as usual because we could classify the current tests as a "atomic" test or "scenario" test16:28
hogepodgeIt's why I feel that testing of capabilities in the same grouping (CRUD) can coexist (even if on a formal basis we feel a bit icky about it)16:28
catherineDgema: will do16:28
dwalleckIt might be good to have oomichi and others review the spec as well16:28
hogepodgedwalleck: +116:28
shamailhogepodge: +116:28
gemacatherineD: and also what you think is wrong with those tests, so that I get a better understanding16:28
gemacatherineD: you got the experience with people running into trouble with them16:28
*** zz_dimtruck is now known as dimtruck16:29
catherineDgema: yup16:29
VanLhogepodge: -1, I think that takes us places that it would be better not to go. I don't like ickiness, as that translates to "brokenness" for me16:29
gemacatherineD: +1 thanks16:29
*** mickeys has joined #openstack-meeting-316:29
gemaVanL: what do you mean?16:29
VanLQuoting hogepodge: "It's why I feel that testing of capabilities in the same grouping (CRUD) can coexist (even if on a formal basis we feel a bit icky about it)"16:30
VanLEmphasizing my aversion to the ickiness16:30
gemaahh, ok16:30
RockygSo, if we define scenario test well, other apis in a tes are there for the specific purpose of the scenario.16:30
*** sdake_ has quit IRC16:31
hogepodgeRockyg: and maybe that's the answer, it goes away if we somehow define crud as a scenario16:31
VanLI would be ok with a CRUD test that was a scenario test built out of otherwise-tested atomic bits16:31
*** sdake has joined #openstack-meeting-316:31
hogepodgeand admit crud scenarios16:31
gemaand forget about all other scenario tests?16:31
VanLCRUD as scenario I'm ok with.16:31
Rockygno, we will need a number of scenario tests besides crud16:32
hogepodgegema: no, not forget all others, but I'm trying to see how to focus efforts and evaluate the current test list16:32
*** spzala has joined #openstack-meeting-316:33
gemahogepodge: trying to shoehorn the current tests into the spec, i.e. weaken the spec , is the wrong way around imo16:33
Rockyglike, add disk space to a vm is actually a scenario or part of one.16:33
gemahogepodge: we can be flexible on how to deal with the existing tests that don't meet the spec either16:33
hogepodgegema: we're enforcing a current standard, and I don't want to throw that work away16:33
catherineDOne thing we want to be clear is that there is not thing wrong on the Tempest tests ... It is just that some of the Tempest tests DefCore used is not written for interop testing ..16:33
gemahogepodge: we don't need to16:34
*** mickeys has quit IRC16:34
hogepodgegema: if the spec is too tightly written it can be used as a tool to argue for that16:34
*** slogan has quit IRC16:34
*** ddieterly is now known as ddieterly[away]16:34
dwalleckcatherineD: I wouldn't even say they're wrong for interop. They just may not target one capability16:34
gemahogepodge: ok, I see your point16:34
Rockygmaybe we should write a grandfather clause into the spec.16:34
Rockyguse wha we have until we have conforming tests16:35
VanLNo, no grandfather support16:35
dwalleckBut I thought part of that was handled when we defined some individual capabilities as crud16:35
hogepodgeThis is good discussion, but I'm going to time cap to 40 past the hour so we can reach some of the other topics.16:35
VanLdwalleck: Noooo!16:35
gemahogepodge: +116:35
dwalleckThen I misunderstood and need more caffeine :-)16:36
hogepodgedwalleck: that capability refactoring hasn't been approved16:36
gemaI wil wait for catherineD's examples and comments on gerrit before proposing a change16:36
hogepodge(indeed, not even defined yet...)16:36
dwalleck hogepodge: gotcha16:36
*** Swami has quit IRC16:36
Rockygif we don't have grandfather, then defcore needs a waiver process to allow tests, cycle by cycle until we have a conforming test to replace it.16:36
*** tomasztrebski has quit IRC16:36
VanLRockyg: Ok16:37
*** njohnston has quit IRC16:37
VanLBut I want to push us towards rationalized tests16:37
gemaVanL: stop throwing new words in, what are rationalized tests16:37
dwalleckRockyg: That's why we need to get the QA team involved. They would need to agree with our assessment16:37
catherineDRockyg: +1 ... if spec is merged we need to abide to it ...16:37
*** jmckind has joined #openstack-meeting-316:37
Rockyggema, ++ ;-)16:38
catherineDmaybe with a time target too ..else not much useful with the spec16:38
gemahogepodge: who can I add from QA to the review?16:38
hogepodgegema: tests that don't bleed way out of their intended scope I think?16:38
woodster_I'd be good to have canonical reference examples of in-spec tests at some point16:38
VanLgema: Not trying to define a new term, just using standard meaning16:38
*** tellesnobrega_af is now known as tellesnobrega16:38
gemaVanL: not standard where I live :)16:38
RockygcatherineD, that's why cycle by cycle.  Needs new waiver each cycle16:38
gemaVanL: I think I got it from hogepodge's explanation16:38
hogepodgegema: oomichi and mtreinish16:38
gemahogepodge: ack, will do16:38
hogepodgeOk, wrapping up the discussion. Thanks everyone, this is really valuable.16:39
Rockyggema, maybe we need to have a suggested readking list for non-testers16:39
hogepodgePlease, comment further on the review in gerrit16:39
catherineDhogepodge: +1 I think so ... thx gema: for  submitting the patch16:39
*** ddieterly[away] is now known as ddieterly16:40
hogepodge#topic Schema (1.4)16:40
*** openstack changes topic to "Schema (1.4) (Meeting topic: defcore)"16:40
hogepodgeThese are ready for review #link
hogepodgeThe first is formalization of the 1.4 schema, along with minor guideline changes to match the formalization16:41
hogepodgeAlong with linting and validation16:41
hogepodgeThe second makes linting and validation voting jobs in the gate to help make sure we don't accidentally break the guidelines in updates16:41
hogepodgePlease, check my work. :-D16:42
hogepodgeAny comments or questions?16:42
catherineDhogepodge: I know it is  format change for rst to json ..   I think it would be easier for RefStack if we make it versio n1.5 instead of remaining on 1.416:42
hogepodgecatherineD: ok, I can do that16:42
catherineDdo we remove the rst version from now on?16:42
hogepodgecatherineD: I think we should retain them for, but don't feel strongly about it16:43
catherineDhogepodge: thx that would help16:43
Rockygdeprecation?  Keep it for a cycle?16:43
hogepodgeI'm mainly concerned with updates (particularly when we have merge conflicts) that break the guidelines16:43
Rockygor two?  follow dev standards on deprecation16:43
hogepodgeYeah, we can remove them beginning 2017 from the repo too16:44
catherineDhogepodge: definitely retain the existing rst ... not sure we need for the future16:44
hogepodgeno rst for the future. the json schema is formal and gateable16:45
shamailhogepodge: I think you might need to switch line 5402 to after 5404 in this one?
catherineDsince the old rst  files will be used to render the guidlelines prior to 2015.07 ...16:45
*** mickeys has joined #openstack-meeting-316:45
hogepodgecatherineD: ok16:45
shamailsorry, meant move 5402 and 5407 to the top of their sections.. Jenkins failed on that patch.16:46
catherineDhogepodge:  thanks .. I will add those comments on the patch  ...16:47
hogepodgeshamail: I'll take a look16:47
hogepodgeany other comments?16:47
shamailAdded comments to the review.16:47
hogepodge#topic Schema (2.0)16:47
*** openstack changes topic to "Schema (2.0) (Meeting topic: defcore)"16:47
hogepodgeThis one needs a lot more work. Cover intent, and also needs to be formalized along the lines of 1.4/1.516:48
hogepodgeIf I understand correctly, it captures higher level metadata about the guideline itself.16:48
hogepodgecatherineD: do you know andrey's irc nick so he can comment?16:49
catherineDand also update it to JSON16:49
hogepodgeIf everyone can take a look and leave reviews, that would be helpful for guiding future discussion on the direction to take the guidelines in16:50
*** fawadkhaliq has quit IRC16:50
hogepodgeOk, moving on.16:51
*** fawadkhaliq has joined #openstack-meeting-316:51
catherineDAndrey's IRC andrey-mp16:51
catherineDwill let andrey-mp: know16:51
hogepodge#topic Interop Issues Report16:51
*** openstack changes topic to "Interop Issues Report (Meeting topic: defcore)"16:51
hogepodgejust a reminder, leave comments on this #link
*** Guest37264 is now known as melwitt16:51
hogepodgeMark and Egle are preparing this as a report to the board and community. We discussed it a lot in Austin16:51
hogepodge#topic Work in Progress16:52
*** openstack changes topic to "Work in Progress (Meeting topic: defcore)"16:52
*** banix has joined #openstack-meeting-316:53
hogepodge#link markvoelker has added some tests for neutron that we'll want to use for api discovery
hogepodgePlease review16:53
hogepodgeI still need to work on refactoring (where possible) the advisory tests that require admin16:54
hogepodgeAnd also do doc generation16:54
hogepodgeDoes anyone have links to work they want reviewed?16:54
*** iyamahat has quit IRC16:54
*** fawadkhaliq has quit IRC16:55
*** iyamahat has joined #openstack-meeting-316:55
hogepodgeOk, open discussion for the last few minutes.16:55
hogepodge#topic Open Discussion16:55
*** openstack changes topic to "Open Discussion (Meeting topic: defcore)"16:55
catherineDhogepodge: tempest.api.image.v2.test_images_member and tempest.api.image.v2.test_images_member_negative in advisory still need 2 users16:55
hogepodgecatherineD: I'll take a look at those16:55
catherineDhogepodge: do we flag them ?16:55
catherineDhogepodge: ok16:56
hogepodgethe name "member" suggests it'll require two users, so likely need to be removed (if they're advisory, flag if required)16:56
*** Swami has joined #openstack-meeting-316:56
catherineDI think we can merge
dwalleckThat feature may be tricky. I think that's the tenant visibility flag that lets you share images16:57
hogepodgecatherineD: can any be rewritten? that's something I wanted to look in to16:57
*** Sukhdev has quit IRC16:57
Rockyghogepodge, ++16:57
*** mickeys has quit IRC16:57
hogepodge(action item for me)16:57
catherineDhogepodge: it takes time to update tempest tests ... meanwhile user still waisting their time to debug tests that we know won't work without admin16:58
*** mickeys has joined #openstack-meeting-316:58
catherineDby flagging them  will save user's debug time16:58
hogepodgecatherineD: since they're advisory, I'd like just a bit more time to see if we can make that list smaller16:58
hogepodgeWe're out of time.16:59
*** shamail has quit IRC16:59
hogepodgeThanks everyone for the productive meeting. We can continue in #defcore16:59
*** mrmartin has joined #openstack-meeting-316:59
*** openstack changes topic to "OpenStack Meetings ||"16:59
openstackMeeting ended Wed May 18 16:59:56 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:59
openstackMinutes (text):
*** gema has left #openstack-meeting-317:00
*** dwalleck has left #openstack-meeting-317:00
*** catherineD has left #openstack-meeting-317:00
*** sarob has joined #openstack-meeting-317:01
*** claudiub has quit IRC17:04
*** mickeys has quit IRC17:05
*** ddieterly is now known as ddieterly[away]17:05
*** tonytan4ever has quit IRC17:08
*** lpetrut has quit IRC17:08
*** mrmartin has quit IRC17:10
*** absubram has joined #openstack-meeting-317:11
*** cjvolzka has left #openstack-meeting-317:11
*** sverma has joined #openstack-meeting-317:12
*** Rockyg has quit IRC17:17
*** mickeys has joined #openstack-meeting-317:20
*** mickeys has quit IRC17:20
*** mickeys has joined #openstack-meeting-317:21
*** iyamahat has quit IRC17:22
*** sarob has quit IRC17:29
*** sarob has joined #openstack-meeting-317:33
*** s3wong has joined #openstack-meeting-317:34
*** ivar-lazzaro has joined #openstack-meeting-317:35
*** ivar-lazzaro has quit IRC17:39
*** ivar-lazzaro has joined #openstack-meeting-317:39
*** lpetrut has joined #openstack-meeting-317:40
*** iyamahat has joined #openstack-meeting-317:42
*** anilvenkata has joined #openstack-meeting-317:43
*** spzala has quit IRC17:43
*** spzala has joined #openstack-meeting-317:43
*** lpetrut has quit IRC17:44
*** vhoward has joined #openstack-meeting-317:45
*** dimtruck is now known as zz_dimtruck17:50
*** cbouch_ has quit IRC17:50
*** piet has joined #openstack-meeting-317:51
*** zz_dimtruck is now known as dimtruck17:52
*** pvaneck has joined #openstack-meeting-317:55
*** dtardivel has quit IRC18:00
*** yamahata has joined #openstack-meeting-318:00
*** bpokorny has quit IRC18:00
*** bpokorny has joined #openstack-meeting-318:03
*** wendar_ is now known as wendar18:04
*** ddieterly[away] has quit IRC18:05
*** mickeys has quit IRC18:13
*** Sukhdev has joined #openstack-meeting-318:13
*** mickeys has joined #openstack-meeting-318:14
*** doug-fish has joined #openstack-meeting-318:16
*** evgenyf has joined #openstack-meeting-318:17
*** doug-fish has quit IRC18:17
*** doug-fish has joined #openstack-meeting-318:17
*** tonytan4ever has joined #openstack-meeting-318:18
*** mickeys has quit IRC18:18
*** ihrachys has quit IRC18:18
*** dimtruck is now known as zz_dimtruck18:19
*** coolsvap has quit IRC18:20
*** doug-fis_ has quit IRC18:20
*** bpokorny has quit IRC18:21
*** rossella_s has quit IRC18:23
*** rossella_s has joined #openstack-meeting-318:24
*** banix has quit IRC18:24
*** amit213 has quit IRC18:24
*** egafford has joined #openstack-meeting-318:26
*** muawiakhan has quit IRC18:26
*** muawiakhan has joined #openstack-meeting-318:27
*** amit213 has joined #openstack-meeting-318:27
*** isq has joined #openstack-meeting-318:27
*** muawiakhan has quit IRC18:27
*** ddieterly has joined #openstack-meeting-318:27
*** bpokorny has joined #openstack-meeting-318:28
*** sdake_ has joined #openstack-meeting-318:31
*** sdake has quit IRC18:33
*** MeganR has quit IRC18:41
*** rockyg has joined #openstack-meeting-318:44
*** lpetrut has joined #openstack-meeting-318:47
*** anteaya has joined #openstack-meeting-318:47
*** sambetts is now known as sambetts|afk18:47
*** flwang1 has joined #openstack-meeting-318:54
*** amotoki has quit IRC18:56
*** anteaya has quit IRC18:57
*** MeganR has joined #openstack-meeting-318:59
*** pt_15 has joined #openstack-meeting-319:03
*** MeganR has quit IRC19:04
*** piet has quit IRC19:05
*** piet has joined #openstack-meeting-319:06
*** mrmartin has joined #openstack-meeting-319:07
*** ducttape_ has joined #openstack-meeting-319:08
*** toddjoh__ has quit IRC19:10
*** doug-fish has quit IRC19:10
*** banix has joined #openstack-meeting-319:12
*** toddjohn_ has joined #openstack-meeting-319:12
*** doug-fish has joined #openstack-meeting-319:13
*** toddjohn_ has quit IRC19:14
*** toddjohn_ has joined #openstack-meeting-319:15
*** kbyrne has quit IRC19:16
*** Sukhdev has quit IRC19:16
*** flwang1 has quit IRC19:18
*** doug-fish has quit IRC19:18
*** kbyrne has joined #openstack-meeting-319:20
*** piet has quit IRC19:21
*** banix has quit IRC19:22
*** sdake_ has quit IRC19:23
*** mickeys has joined #openstack-meeting-319:26
*** mrmartin has quit IRC19:26
*** flwang1 has joined #openstack-meeting-319:26
*** njohnston has joined #openstack-meeting-319:27
*** piet has joined #openstack-meeting-319:27
*** jmckind has quit IRC19:31
*** baoli_ has quit IRC19:34
*** jmckind has joined #openstack-meeting-319:35
*** doug-fish has joined #openstack-meeting-319:40
*** jmckind has quit IRC19:40
*** doug-fish has quit IRC19:44
*** AlanClark has quit IRC19:47
*** sdake has joined #openstack-meeting-319:48
*** matrohon has joined #openstack-meeting-319:50
*** MeganR has joined #openstack-meeting-319:52
*** hurgleburgler has joined #openstack-meeting-319:54
*** mickeys has quit IRC19:54
*** fawadkhaliq has joined #openstack-meeting-319:54
*** fawadkhaliq has quit IRC19:54
*** mickeys has joined #openstack-meeting-319:54
*** fawadkhaliq has joined #openstack-meeting-319:55
*** anilvenkata has quit IRC19:55
*** yamamoto has quit IRC19:55
*** lhcheng_ has joined #openstack-meeting-319:56
*** robcresswell has joined #openstack-meeting-319:56
*** flwang1 has quit IRC19:58
*** mickeys has quit IRC19:59
*** doug-fish has joined #openstack-meeting-319:59
*** salv-orlando has quit IRC19:59
*** tyr_ has joined #openstack-meeting-320:00
tsufievevening, chat20:00
robcresswell#startmeeting horizondrivers20:01
openstackMeeting started Wed May 18 20:01:37 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:01
openstackThe meeting name has been set to 'horizondrivers'20:01
*** TravT has joined #openstack-meeting-320:01
robcresswellHere's the agenda for today20:02
robcresswellCouple things first20:02
robcresswell#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizondrivers)"20:02
*** MeganR has quit IRC20:03
robcresswellMidcycle details are there, and also in the room topic/ mailer. Add attendance, topics to etherpad, etc20:03
*** kashyap has left #openstack-meeting-320:03
robcresswellJust shy of 2 months off, so I hope thats enough time for travel approval etc.20:03
*** matt-borland has joined #openstack-meeting-320:03
TravTi'll add my name, but i don't have travel approval yet.20:04
hurgleburglerme too20:04
*** mickeys has joined #openstack-meeting-320:04
robcresswellNo immediate rush, its just so I can sort out wifi etc.20:04
ducttape_new to pre provision all the wifi ports needed ;)20:04
robcresswellI've updated the bugs. We've cleared out a good number of bugs in N-1 so far, but it'd be great to move on some of the larger bps. We've implemented 3 or 4 so far IIRC.20:05
robcresswellSo please get some reviews on those features.20:05
ducttape_ will likely be complete for N release I expect20:06
*** zz_dimtruck is now known as dimtruck20:06
robcresswellA well filled out bp as well I see :p20:06
robcresswellLets move on to the agenda items20:07
robcresswell#topic UI Text Guidelines20:07
*** openstack changes topic to "UI Text Guidelines (Meeting topic: horizondrivers)"20:07
*** nelsnelson has quit IRC20:08
*** tonytan4ever has quit IRC20:08
* tsufiev proposes to make a new voting job ;)20:08
*** toddjohn_ has quit IRC20:08
robcresswellWas this your item tsufiev ?20:08
tsufievrobcresswell, no, it wasn't me20:08
tsufievjust kidding, of course, about that job20:08
*** toddjohn_ has joined #openstack-meeting-320:08
* ducttape_ was worried20:09
tsufiev(would require some AI to actually check guidelines conformance)20:09
*** nelsnelson has joined #openstack-meeting-320:09
robcresswellWell, thats a mystery. It may be worth a read through, but it doesn't seem like anyone wants to own that :)20:09
robcresswellLets move on20:09
robcresswell#topic Glance V220:09
*** openstack changes topic to "Glance V2 (Meeting topic: horizondrivers)"20:09
david-lylelove guidelines we don't contribute to20:09
tsufievthat was mine20:09
hurgleburglerdavid-lyle: agreed20:09
robcresswelltsufiev: You're up :)20:09
*** toddjoh__ has joined #openstack-meeting-320:09
tsufievI was wondering is Glance v2 support is a thing someone is thinking about?20:10
bpokornyYep, I'm working on that for Newton.20:10
david-lyle ?20:10
tsufievbpokorny, oh, that's good! do you need some help on that?20:10
bpokornyYeah, help would be great on it. I think there are complexities with it that still need to be worked out.20:11
tsufievbpokorny, okay, count me in20:11
bpokornyI know there was a patch out for it that a few people had worked on already, so was planning to start with and improve that one.20:11
TravTbpokorny: you can add me to reviews for this20:11
bpokornytsufiev: TravT: Great!20:12
bpokornyI'll keep you guys posted as I make progress on it.20:12
tsufievcould use midcycle to push reviews for it...20:12
robcresswellWell, that went well :p20:12
robcresswellReady to move on? There's a few bps in the agenda.20:12
*** toddjo___ has joined #openstack-meeting-320:13
*** toddjohn_ has quit IRC20:13
robcresswell#topic Blueprint Review20:13
*** openstack changes topic to "Blueprint Review (Meeting topic: horizondrivers)"20:13
*** ametts has quit IRC20:13
hurgleburglerThai was interested in resurrecting this idea … theres already a review for it up, jones had some comments on it20:14
*** toddjoh__ has quit IRC20:14
*** fawadkhaliq has quit IRC20:15
TravTpardon my ignorance on the background for this one20:15
TravThow does this relate to plugins?20:15
robcresswellrichard had some patches on a related subject right? I wasnt sure if they were over the same thing or different approaches20:15
hurgleburglerrichard had some old patches that reworked the static stuff20:15
tsufievI like richard's concept of keeping entrypoints by default inside xstatic20:15
david-lyleTravT: if a plugin wants to use an xstatic package horizon proper doesn't already20:15
hurgleburglerI asked him to resurrect it so that I could make use of it for this BP20:15
hurgleburglerHis patch calls our some JS FILES directly, I still need to touch base with him on the comments, I think our solutions can live peacefully together somehow20:16
hurgleburglerour == out20:17
hurgleburglerI'm mostly interested in being able to pip install a theme20:17
* ducttape_ is under the impression that pipin is not easy20:17
hurgleburglerducttape_: lol20:18
* tsufiev is curious how js dependencies are solved in this semi-automatic way?20:18
* david-lyle saw that on tshirt, so it must be true20:18
tsufievshould we re-introduce npm-like dependencies into xstatic ;)?20:18
hurgleburglerthink that might be part of the comments left, but I'm not sure yet20:18
ducttape_the js dependacies are not really handled, unless the xstatic package enforces it20:18
tsufievI mean, sometimes scripts should be loaded in a particular order20:18
hurgleburglerbut, any thoughts on the BP itself?20:19
hurgleburglerdo people like the idea?20:19
hurgleburglertoo bad thai isn't here20:19
hurgleburgleri'd given up on it ages ago20:19
robcresswellYeah it makes sense to me20:19
hurgleburglercool beans20:20
robcresswellThoughts on approval/priority?20:20
ducttape_it seems like it is more of a developer / distro priority20:20
david-lyleso I believe app-catalog had wanted such a thing as well20:21
ducttape_as long stuff doesn't completely break and need a rewrite - wfm20:21
robcresswellI agree. It seems like a QOL change to me20:21
tsufievquality of life?20:22
TravT+1 on the BP20:22
robcresswellAs in, it makes setup easier, but its not like that setup is impossible to achieve20:22
hurgleburglerits true … I've heard some packagers rebuild the entire themselves wiht shell scripts20:23
robcresswell#info Approved20:23
hurgleburglerThis is the concept I brought up at the summit20:23
hurgleburglersomething that we might need internally, and something that would be cool to provide to everyone else20:23
david-lyle"simple cookie logic" ?20:24
ducttape_ah yeah, that is crazy20:25
david-lyleis that a thing?20:25
hurgleburglerdavid-lyle: LOL20:25
ducttape_it's interesting / cool.... but crazy20:25
hurgleburglerbasically, I'd like to be able to use functions, that simply return the theme value to load20:25
robcresswellI don't like the idea of changing the setting again, if its altering the existing setting20:25
tsufievducttape_, just imagine randomly generated theme based on a random cookie value!20:26
robcresswellAs long as it functions with the same config as today, extending is fine as far as Im concerned.20:26
hurgleburgleryou can write any logic, as long as it returns a theme 'key'20:26
ducttape_are there current places in horizon that don't adopt the current theme stuff all that well?  those seem higher priority20:26
david-lylerobcresswell: next cycle theming will stabilize20:26
ducttape_I thought I heard that last cycle20:26
david-lyleevery cycle :P20:26
hurgleburglerducttape_: sorry, there's only one of me20:26
robcresswelldavid-lyle: Hey, my response to him was that Liberty was more stable20:27
ducttape_yy.... but I think it should be recognized... there are spots right now that don't adopt theme stuff well / correctly.... and it's pretty ugly / obvious20:27
hurgleburglerWhich ones?20:27
david-lyleducttape_: those are on hurgleburgler's hunt and kill list20:27
hurgleburglerI'm cleaning up the stragglers now20:27
robcresswellSo, my thoughts on the actual bp is the idea is neat, as long as it doesnt change/break any existing config then its fine20:27
david-lylerobcresswell:  +120:28
ducttape_k.  I know mfisch was complaining, will get bugs filed to follow up with20:28
hurgleburglerrobcresswell: i promise20:28
robcresswellBut it isnt high priority. More interested in fixing the existing issues and making sure the angular content is also themable etc.20:28
david-lyleducttape_: that's surprising20:28
hurgleburglerducttape_: just shoot the bugs my way if possible20:28
ducttape_we like to give hurgleburgler a hard time.   no one has done more around the theme stuff... but it's never enough20:29
david-lyleI agree filling in the theming gaps is higher priority20:29
hurgleburglerIts never done!20:29
robcresswell#info Approved20:29
hurgleburglerdamn moving target20:29
david-lyleoverride all the things !20:29
hurgleburglerhere's a big one20:29
hurgleburglerI just did the spinner rework20:29
hurgleburglermaking the spinner overridable from the theme20:29
hurgleburglerthrough tempaltes20:29
hurgleburglerangular uses their own spinner20:29
hurgleburglerwhich is a problem20:29
*** ametts has joined #openstack-meeting-320:30
hurgleburglerright now … I restructured the angular to use a template (it was inline HTML within the JavaScript)20:30
hurgleburglerbut, there is no way to override the angular templates from a theme20:30
tsufievfrankly speaking, I don't find a bare spinner very UI-friendly20:30
tsufievwould be better to see progress bar in its place20:30
hurgleburglerbut now you can customize it anyways you want20:30
david-lyletsufiev: for the page?20:30
hurgleburglerprogress bar is sometimes impossible20:31
hurgleburglercause, you don't know percentages20:31
robcresswelltsufiev: Progress bars are difficult to make reliable, and frustrating if they aren't reliable.20:31
hurgleburgleror do you mean just an animated 100% width one?20:31
david-lyle14 hours left to load page20:31
tsufievoh yes, that's true :(20:31
hurgleburglerbut, anyways, off topic20:31
david-lyleoh wait it's done20:31
hurgleburglerright now, you can't override angular templates20:31
ducttape_so this is primarily supporting the spinner stuff?20:31
tsufievat least for file uploads where progress is trackable20:31
tyr_in any case...with this blueprint...your theme can make the spinner a progress bar20:31
hurgleburglerno, supporting ANY angular overrides20:31
robcresswellducttape_: No, one tiny piece is done :)20:31
hurgleburglerit just became apparent when I did this work20:31
robcresswellI think20:31
tsufievwhich imo the ones users wait the most time20:31
ediardoanimate until 99% -> then 100% until completed20:31
robcresswellediardo: UX ftw20:32
ducttape_I'm hunting for how to change new launch instance use of transfer table, and throw that thing overboard20:32
tsufievediardo, haha. Or better use 'windows files copy' approach20:32
robcresswellSo, one of the nice parts about the django templating is that we can do block and template level overrides20:32
tsufiev15 mins ... 30 mins ... 45 mins...20:32
hurgleburglerIts one of the most powerful pieces of the Theme functionality20:33
david-lyleone of the core design principles for Horizon is extensibility, so I am +2 on this bp20:33
hurgleburglerits how material is able to change the sidebar and the header20:33
robcresswellI think if we cant customise templates or HTML in any way, its a big step backwards in that regard.20:33
hurgleburglerI spoke it over with a few of the angular peeps20:33
hurgleburglermatt-borland and TravT20:33
hurgleburglerI threw up three idea on how to approach the problem from our meeting20:33
hurgleburglertyr_ too!20:33
hurgleburglerAny input or iteration on those ideas would be awesome too20:34
tyr_can you elaborate on your 2nd idea in the bp? I didn't grok that one20:34
tyr_in bp off-line is fine20:34
robcresswellAll okay with approval/ High?20:35
hurgleburglerWhen we do collectstatic, we look through the directory structure anyways, we can write a static json file and load that into angular20:35
TravT+ on approval... but not sure on which approach.20:36
ducttape_It would be nice to have a real use case / example for it to be high20:36
hurgleburglerI think several people can help implement too, if possible20:36
ducttape_the spinner is kinda lower priority20:36
robcresswellI think you're fixating on the spinner example a bit20:36
tyr_the use case is as we get angular appears to be a regression in themeability20:36
hurgleburglerducttape_: the spinner is just an example of why you would need to override tempaltes20:37
tyr_swift ui for example20:37
robcresswellI think the point hurgleburgler was making is that you can't override any angular templates right now. So you're just stuck with the layout.20:37
ducttape_sure, but it's not really impacting admins or users in a material way imo20:37
david-lyleducttape_: it's more about other widgets, that was just a simple one20:37
ducttape_sure ok... then take the flavor sort thing in the new launch instance.... something 3 operators brought up at the summit20:38
tsufiev+1 that this feature is needed20:38
ducttape_and use that as an example / proof point20:38
*** ddieterly is now known as ddieterly[away]20:38
tyr_it is worth noting that because angular templates may contain complex behavior and controller HTML overrides need to tread carefully.20:39
*** ddieterly[away] is now known as ddieterly20:39
robcresswellducttape_: These arent mutually exclusive goals though. I'd like to fix that too. I can't recall the priority we set on that, I think its assigned to me at the moment.20:39
matt-borlandducttape_, that example is arguably about functionality more than theming20:39
hurgleburglertyr_: the same is true of the django templates in some cases20:39
TravTducttape_: is this the setting that allows injecting a python function?20:39
ducttape_it used to work that way TravT, yes20:39
ducttape_but it could work in another way in the future20:39
*** lpetrut has quit IRC20:40
robcresswellWe can decide on implementation, but I think its a desirable to maintain the template flexibility20:41
matt-borlandyep, agreed20:41
*** lpetrut has joined #openstack-meeting-320:41
tyr_I think this is a useful bp, but it does add another " guys broke my customization" point. Any ideas how to provide an "api" of sorts...or versioning?20:42
robcresswellI'd like to look into how the schema form does it personally, they have a really nice way of doing it20:42
robcresswellWith their bootstrap provider20:42
robcresswellBut thts off topic20:42
hurgleburglerrobcresswell: would love it if you could provide a solution on the BP too20:42
robcresswell#info Approved, High20:42
matt-borlandyeah, it's definitely a 'here be dragons' use case20:42
tsufievrobcresswell, if you'd like to offload some part of schema research, ping me20:42
robcresswellhurgleburgler: I'll work out when I can next forgo sleep and add to it :)20:42
TravThurgleburgler: is your option 2 basically a resource registry?20:43
TravTthe json object?20:43
* matt-borland heh heh20:43
hurgleburglerrobcresswell: you need to build up your tolerence20:43
TravTi'm thinking more like message catalogs20:43
TravTwhere the key is the text inline and the value is what you should really use20:43
hurgleburglerTravT: probably … we just need to load it via a django template tag in the angular base template somehow20:43
hurgleburglerI think it might be the best of both the solutions we had discussed before20:44
hurgleburglerbut, approved!20:44
tyr_I'd be cautious about making it too angular specific. i think it might be better approached as a "static file override"20:44
robcresswellNothing else on the agenda for today20:45
robcresswell#topic Open Discussion20:45
*** openstack changes topic to "Open Discussion (Meeting topic: horizondrivers)"20:45
matt-borlandeslint warnings?20:45
tsufievI have a minor question about angular files location20:45
tsufievI do not want at all to start another file moving crusade, but...20:45
ducttape_there is already an option to have static file overrides, we use em... and would apply in case above... but not be theme specific20:45
lcastellI have a couple of BPs to advertise:
*** lpetrut has quit IRC20:46
*** absubram has quit IRC20:46
ducttape_nice lcastell20:46
tsufievI found it a bit confusing that, for example NG Images are inside openstack_dashboard/static/app/core/images while containers are inside openstack_dashboard/dashboards/project/static/containers20:46
tyr_tsufiev: images "base" code is theoretically shared by panels in two different dashboards20:47
robcresswelllcastell: We've discussed this one before, so we can approve it unless anyone has any strong objections20:47
matt-borlandyeah, I think that as we move toward things registered by resource type, they will fall into a logical registry, not dashboard-related20:47
matt-borland*logical directory system20:48
robcresswelllcastell: These two* even20:48
matt-borlandtsufiev, tyr and I were also looking at this, thinking of targeting newton-2 with a recommendation20:48
tsufievthen perhaps not use dashboard-oriented scheme at all?20:48
matt-borlandso we don't have 100 refactors20:48
tyr_lcastell: both of those bp's seem to swirl around use cases that searchlight addresses particularly well.20:48
matt-borlandperhaps, I think it's up to people to figure out the direction we want to go in with panels/actions/views20:49
*** mickeys has quit IRC20:49
tsufievmatt-borland, okay, it's always pleasant to hear that something bothers not only me :)20:49
*** mickeys has joined #openstack-meeting-320:49
matt-borlandindeed, it gnaws at my soul constantly20:49
tyr_I know we aren't at the searchlight is part of core horizon stage...but i'd be cautious about investing too much effort in a Horizon caching and pre-filtering code base.20:49
ediardoanother BP related to UX:
robcresswelltyr_: We're a long way off that stage.20:50
david-lyletyr_ nor would I bank on searchlight as the only solution20:50
lcastelltyr_  got it20:50
robcresswelllcastell: Please go ahead with the improvements20:50
ducttape_tyr_:  is searchlight deployed anyone at scale ?20:50
david-lylethe extreme in both cases is foolhardy20:50
lcastellrobcresswell cool!! thanks!20:51
ducttape_until searchlight is a valid choice - I think lcastell is very much on the right path, and won't take much effort20:51
tsufievducttape_, that thing interests me as well20:51
david-lylenor does it hurt searchlight20:51
* lcastell tears of joy20:51
* ducttape_ looks for why not both meme20:52
robcresswelltyr_, matt-borland: re: the images code, we should take some time about general architecture, because the porject/admin split is not that clear cut, and we may want to alter it20:52
robcresswellsome time to talk*20:52
robcresswellperhaps at mid cycle20:52
matt-borlandrobcresswell, yes, I think it's a good discussion, esp. once we get more examples20:52
hurgleburglerrobcresswell: will it be possible to dial people into the mid cycle?20:53
hurgleburglerofftopic, apologies20:53
robcresswellThere's a webex all set up I believe.20:53
robcresswellJust wanted to check details before I put out the info though.20:53
hurgleburglercisco has some rather fancy conference technology if I remember correctly20:53
robcresswellShould be a proper conference room with decent audio handling too.20:53
david-lylehurgleburgler: that's for customers20:53
robcresswellNah, they have big telepresence rooms on every floor.20:54
hurgleburglerdavid-lyle: 。゜゜(´O`)°゜。20:54
tsufievhurgleburgler, do they have time distortion machine to fight TZ differences :)?20:54
robcresswelltyr_ hurgleburgler matt-borland:
david-lylehurgleburgler: I'm not even sure what that was20:54
tsufiev(I hope I won't need it)20:54
matt-borlandyeah, robcresswell20:54
robcresswellthats how schema form does its template handling ^^20:54
robcresswellIf you could do something like that, I think that would be really cool.20:55
matt-borlandhey, we didn't get to my suggested topic! :)20:55
robcresswellmatt-borland: :o sorry, what was it?20:55
matt-borlandcopious eslint warnings20:55
matt-borlandnotably 'quote-props'20:56
matt-borlanddo we really want that rule?20:56
*** lblanchard has quit IRC20:56
matt-borlandI don't. :)20:56
david-lylematt-borland: all javascript is warning according to eslint20:56
*** yamamoto has joined #openstack-meeting-320:56
matt-borlandactually, it's just all quote-props20:56
tsufievdavid-lyle, lol )20:56
TravTdavid-lyle: lol20:56
hurgleburglerdavid-lyle: it was a crying person20:56
david-lylematt-borland: do we just have to disable rules?20:56
david-lyleor are you proposing fixing all the nits?20:57
matt-borlandyeah, we can set that quote-props rule to 0 unless someone really wants it20:57
TravTeslint warnings provide zero value until that is done20:57
hurgleburglerwe can disable all the nits :-D20:57
matt-borlandit's "you should say {'a': 'apple'} rather than {a: 'apple'}20:57
robcresswellFine by me. I have no strong feelings about anything above basic linting.20:57
tsufievmatt-borland, do you think we need to disable it in eslint-config-openstack?20:57
matt-borlandwe can override in .eslintrc I think20:57
matt-borlandI did the other day20:57
*** abalutoiu has quit IRC20:58
hurgleburglerwe don't have to actually follow every rule they push20:58
david-lyleI say disable and if someone wants to reenable, they can fix all the warnings with that patch20:58
matt-borlandI'll put up a patch...thanks!20:58
TravTdavid-lyle: +220:58
tsufievyes, it's always possible, but it just looks... not aligned with common sense20:58
hurgleburglerdavid-lyle: +220:58
matt-borlandthanks :)20:58
*** mriedem has joined #openstack-meeting-320:58
* tsufiev dreams about starting using ES2015 in Horizon JS20:59
hurgleburglernits aren't 'common sense' all the time20:59
robcresswellWe're at time21:00
robcresswellThanks everyone!21:00
*** alaski has joined #openstack-meeting-321:00
*** openstack changes topic to "OpenStack Meetings ||"21:00
openstackMeeting ended Wed May 18 21:00:15 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:00
*** ducttape_ has left #openstack-meeting-321:00
david-lyleThanks robcresswell21:00
openstackMinutes (text):
*** hurgleburgler has left #openstack-meeting-321:00
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed May 18 21:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
*** robcresswell has left #openstack-meeting-321:00
openstackThe meeting name has been set to 'nova_cells'21:00
*** tsufiev has left #openstack-meeting-321:00
* bauzas waves21:00
bauzasbroken arm ?21:01
melwitta salute21:01
melwittis my guess21:01
alaskidansmith has requested a full hour meeting so let's see what we can do21:01
bauzaso~ then21:01
alaski#topic testing21:01
*** openstack changes topic to "testing (Meeting topic: nova_cells)"21:01
alaskiany news from anyone here?21:01
alaskiccarmack isn't around21:02
melwittI don't know if anyone's mentioned in the meeting before but the cells job seemed more prone to fail on the fernet token bug21:02
melwittwhich I saw mriedem reverted the change today, right? I saw an ML post21:02
alaskiI was not aware of that21:02
alaskithe increase in failures21:02
mriedemthe revert merged hours ago21:03
melwittthe bug was affecting the gate in general but it seemed to be more frequent in the cells job for some reason21:03
mriedemi was so gd tired of that21:03
alaskimelwitt: did you do any digging on cause, or just noticed the correlation?21:03
*** yamamoto has quit IRC21:03
*** matt-borland has left #openstack-meeting-321:03
melwittjust noticed a correlation unscientifically21:03
mriedemalaski: it's a token revocation race, not sure why cells v1 would make it worse21:03
mriedemsince it's totally a keystone test21:03
mriedemdoesn't hit nova21:03
mriedemwe could use logstash to get a scientific correlation21:04
mriedemoutside of this meeting21:04
alaskiokay. something to keep an eye out for when fernet tokens come back as the default21:04
*** lhcheng_ has left #openstack-meeting-321:04
mriedemit's not actually special to the cells job21:04
mriedemaccording to logstash21:04
alaskiI need to check in with ccarmack on testing, but I'm not aware of anything to mention here21:05
melwittokay. just me being paranoid then. sorry for the noise21:05
alaskiso we'll move on21:05
mriedemccarmack isn't really working on this anymore as far as i know21:05
mriedemhe's been reassigned21:05
alaskimelwitt: it was worth checking out21:05
alaskimriedem: ahh21:05
*** ddieterly is now known as ddieterly[away]21:05
*** ctrath has joined #openstack-meeting-321:06
*** ccarmack has joined #openstack-meeting-321:06
alaskithen I'll look into pulling together what he had and dumping it for someone else to look at if they wish21:06
alaskihis plan I mean21:06
alaski#topic Open Reviews21:06
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:06
alaskias always
mriedemoh what rebase?!
alaskiI feel like there's been an increase in reviews recently which is great21:07
*** ametts has quit IRC21:07
alaskiyeah, merge conflict21:08
alaskione of doffms patches I think21:08
dansmiththe last patch of the keypair set never landed due to a merge conflict, but it's good to go now:21:08
mriedemok, +2 on again21:08
dansmithand I got the patches up to move and undo some of the inventory stuff, but the principals should probably look at those first and I've already pinged them21:09
alaskidansmith: okay, I'll take a look again after21:09
alaskidansmith: great21:09
*** sverma has quit IRC21:09
alaski#topic Open Discussion21:10
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:10
doffmI finally got around to updating the quota migration spec with the things we discussed last week.21:10
doffmI also added an instance groups migration spec. Both are on the priorities page.21:10
doffmIntending to start on the quotas when the aggregates stuff starts merging.21:10
alaskiokay. I was thinking of starting on it once my scheduler interaction patches are all up21:11
alaskibut I can grab something else21:11
doffmInstance groups is for grabs. :)21:11
alaskiI feel like I need to help with migrations or testing next21:11
*** piet has quit IRC21:11
*** tyr_ has left #openstack-meeting-321:11
melwittI wanted to mention to the group about the oslo.messaging transport_url thing, I proposed a spec to oslo-specs and it turned out the impl-specific transport options are not recommended to use and are being deprecated21:11
alaskidoffm: cool, I'll look at that one then21:12
doffmmelwitt: So they will all be going to transport urls?21:12
*** mickeys has quit IRC21:12
*** ccarmack has left #openstack-meeting-321:12
*** Sukhdev has joined #openstack-meeting-321:12
*** mickeys has joined #openstack-meeting-321:12
melwittdoffm: yes. CONF.transport_url is the recommended way. sileht mentioned there isn't yet total support for it in the zmq driver but he will fix that21:12
alaskimelwitt: I noticed that the other options aren't marked with deprecate_for_removal yet21:13
*** spzala has quit IRC21:13
melwittso, alaski and I were thinking for the nova-manage command we'll try to use CONF.transport_url if it's there and if not, error out saying to pass --transport-url21:13
*** banix has joined #openstack-meeting-321:13
*** spzala has joined #openstack-meeting-321:13
melwittalaski: yeah, I mentioned that in the review, I -1'ed it because I thought all the options would go deprecated at the same time. but probably there will be follow on patches21:14
melwittI'll keep an eye out over there and follow up about it with sileht21:15
alaskithat also brought to light that devstack isn't using transport_url right? So that's something we'll want to fix21:15
mriedemthat could be fixed today right?21:15
melwittright. we'll want to get devstack generating nova.conf with transport_url21:15
alaskimriedem: yes21:15
mriedemaction item?21:15
mriedemwho wants it21:15
mriedemnot it21:15
melwittI can do it. hopefully. I know it's not possible for zeromq yet but I don't even know if you can setup a devstack that way anyhow21:16
alaski#action melwitt update devstack to use transport_url for messaging config21:16
doffmalaski: Thinking of devstack.. do you have a patch up to add your 'one_command_to_rule_them_all'. I have an old devstack change to add cell0 setup, I should probably abandon.21:16
alaskimelwitt: looks like there's a zmq plugin21:17
*** mickeys has quit IRC21:17
melwittalaski: ah, right. I feel like I've seen ML posts regarding the plugin before21:17
alaskidoffm: I don't yet21:17
*** shamail has joined #openstack-meeting-321:17
*** ccamacho has quit IRC21:18
*** spzala has quit IRC21:18
alaskidoffm: but it still hasn't merged21:18
alaskiI can throw something up with a depends-on though21:18
melwittalaski: I'm not sure if it's an option to convert the ones that are possible now and then update zmq when a version of oslo.messaging gets released that can handle connection expressed as transport_url21:19
*** evgenyf has quit IRC21:19
alaskimelwitt: okay. I have no idea either. It''ll just mean devstack has to pass in transport_url with the nova-manage command for a bit21:20
mriedemmelwitt: you can case stuff in devstack generally21:20
*** salv-orlando has joined #openstack-meeting-321:21
alaskibut this also implies that cells isn't going to work with zmq until this is fixed21:21
mriedemwith a TODO to add zmq later21:21
mriedemanyone run cells with zmq?21:21
mriedemanyone run zmq, period?21:21
alaskinot that I know of21:21
melwittwell, I think it also means cells doesn't work with zmq now21:21
doffmThe driver is 10 months old. (The new one)21:21
alaskimelwitt: yep21:21
bauzasI thought zmq was a bit defunct21:21
bauzasoh, there is a new one?21:22
doffmI think someone in mirantis is trying to bring it back to life.21:22
alaskithere seems to be a bit of a revival around it21:22
dansmiththis is a minor thing, right?21:22
alaskiI know it's being tested heavily21:22
dansmithit'll work when that is fixed/updated, no need to worry about it right now I think21:22
*** spzala has joined #openstack-meeting-321:22
alaskiyep, just calling it out21:22
mriedemzmq, the amqp backend for hipsters21:23
melwittyeah, so I'll convert for the ones now and put the TODO for zmq21:23
mriedemre: revival21:23
alaskiwell it sounds like we're all pretty much on the same page overall, and have plenty to work on21:23
*** kzaitsev_mb has joined #openstack-meeting-321:23
alaskiso I'll wrap up here unless dansmith wants to continue21:23
mriedemif i have procedural -2s on anything let me know in the next 24 hours21:23
* dansmith is not amused21:23
alaskicool. thanks all!21:24
*** openstack changes topic to "OpenStack Meetings ||"21:24
*** mriedem has left #openstack-meeting-321:24
openstackMeeting ended Wed May 18 21:24:23 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:24
openstackMinutes (text):
*** shamail has quit IRC21:26
*** TravT has left #openstack-meeting-321:27
*** toddjo___ has quit IRC21:29
*** mickeys has joined #openstack-meeting-321:29
*** ajmiller has quit IRC21:30
*** ajmiller has joined #openstack-meeting-321:30
*** doug-fish has quit IRC21:30
*** piet has joined #openstack-meeting-321:32
*** aliadil has quit IRC21:32
*** toddjohn_ has joined #openstack-meeting-321:33
*** ddieterly[away] is now known as ddieterly21:34
*** matrohon has quit IRC21:34
*** toddjoh__ has joined #openstack-meeting-321:34
*** rockyg has quit IRC21:35
*** flwang1 has joined #openstack-meeting-321:35
*** toddjohn_ has quit IRC21:37
*** matrohon has joined #openstack-meeting-321:38
*** ctrath has quit IRC21:40
*** ctrath has joined #openstack-meeting-321:40
*** cloudtrainme has quit IRC21:46
*** rtheis has quit IRC21:47
*** markvoelker has joined #openstack-meeting-321:51
*** markvoelker has quit IRC21:52
*** markvoelker has joined #openstack-meeting-321:53
*** toddjoh__ has quit IRC21:56
*** matrohon has quit IRC21:57
*** piet has quit IRC21:57
*** alaski has left #openstack-meeting-321:59
*** ctrath has quit IRC21:59
*** bpokorny_ has joined #openstack-meeting-322:00
*** SridarK_ has quit IRC22:02
*** bpokorny has quit IRC22:04
*** julim has quit IRC22:04
*** anteaya has joined #openstack-meeting-322:14
*** yantarou has quit IRC22:21
*** rossella_s has quit IRC22:23
*** rossella_s has joined #openstack-meeting-322:24
*** yantarou has joined #openstack-meeting-322:24
*** bpokorny_ has quit IRC22:33
*** cloudtrainme has joined #openstack-meeting-322:33
*** cloudtrainme has quit IRC22:36
*** ddieterly is now known as ddieterly[away]22:41
*** rhochmuth has quit IRC22:42
*** pt_15 has quit IRC22:46
*** ujuc has quit IRC22:47
*** kzaitsev_mb has quit IRC22:48
*** kzaitsev_mb has joined #openstack-meeting-322:53
*** mbound has quit IRC22:54
*** bpokorny has joined #openstack-meeting-322:55
*** donghao has joined #openstack-meeting-322:56
*** yamahata has quit IRC22:58
*** kzaitsev_mb has quit IRC22:58
*** anteaya has quit IRC23:01
*** rhochmuth has joined #openstack-meeting-323:02
*** rhochmuth has joined #openstack-meeting-323:03
*** ddieterly[away] is now known as ddieterly23:05
*** rhochmuth has joined #openstack-meeting-323:05
*** markvoelker_ has joined #openstack-meeting-323:05
*** markvoelker_ has quit IRC23:05
*** markvoelker_ has joined #openstack-meeting-323:06
*** markvoelker has quit IRC23:09
*** kzaitsev_mb has joined #openstack-meeting-323:10
*** salv-orl_ has joined #openstack-meeting-323:10
*** ddieterly has quit IRC23:12
*** sarob has quit IRC23:12
*** salv-orlando has quit IRC23:13
*** sdague has quit IRC23:14
*** spzala has quit IRC23:15
*** spzala has joined #openstack-meeting-323:16
*** spzala has quit IRC23:21
*** kzaitsev_mb has quit IRC23:26
*** kzaitsev_mb has joined #openstack-meeting-323:30
*** mickeys has quit IRC23:35
*** mickeys has joined #openstack-meeting-323:35
*** kzaitsev_mb has quit IRC23:37
*** kzaitsev_mb has joined #openstack-meeting-323:38
*** toddjohn_ has joined #openstack-meeting-323:40
*** rhochmuth has quit IRC23:40
*** nelsnels_ has joined #openstack-meeting-323:41
*** toddjohn_ has quit IRC23:41
*** toddjohn_ has joined #openstack-meeting-323:42
*** Sukhdev has quit IRC23:42
*** nelsnelson has quit IRC23:43
*** toddjohn_ has quit IRC23:45
*** toddjohn_ has joined #openstack-meeting-323:46
*** salv-orl_ has quit IRC23:46
*** kzaitsev_mb has quit IRC23:47
*** kzaitsev_mb has joined #openstack-meeting-323:47
*** Sukhdev has joined #openstack-meeting-323:48
*** toddjohn_ has quit IRC23:49
*** toddjohn_ has joined #openstack-meeting-323:49
*** Swami has quit IRC23:49
*** toddjohn_ has quit IRC23:53
*** markvoelker has joined #openstack-meeting-323:53
*** kzaitsev_mb has quit IRC23:54
*** toddjohn_ has joined #openstack-meeting-323:54
*** doug-fish has joined #openstack-meeting-323:54
*** mbound has joined #openstack-meeting-323:55
*** markvoelker_ has quit IRC23:56
*** toddjohn_ has quit IRC23:58
*** doug-fish has quit IRC23:58

Generated by 2.14.0 by Marius Gedminas - find it at!