Wednesday, 2016-07-06

*** ddieterly has joined #openstack-meeting-300:02
*** kzaitsev_mb has quit IRC00:04
*** iyamahat has joined #openstack-meeting-300:08
*** salv-orlando has joined #openstack-meeting-300:08
*** salv-orlando has quit IRC00:22
*** spzala has quit IRC00:24
*** mtanino has quit IRC00:27
*** ddieterly has quit IRC00:30
*** VW has joined #openstack-meeting-300:32
*** ivar-lazzaro has quit IRC00:32
*** bpokorny_ has joined #openstack-meeting-300:34
*** bpokorny has quit IRC00:38
*** bpokorny_ has quit IRC00:39
*** tonytan4ever has joined #openstack-meeting-300:42
*** tonytan4ever has quit IRC00:47
*** piet has joined #openstack-meeting-300:47
*** salv-orlando has joined #openstack-meeting-300:48
*** kenji-i has quit IRC00:48
*** amotoki has joined #openstack-meeting-300:50
*** pvaneck has quit IRC00:51
*** dkehn__ has joined #openstack-meeting-300:53
*** dkehn_ has quit IRC00:56
*** kzaitsev_mb has joined #openstack-meeting-301:02
*** mickeys has quit IRC01:03
*** salv-orlando has quit IRC01:03
*** mickeys has joined #openstack-meeting-301:03
*** mickeys has quit IRC01:08
*** piet has quit IRC01:13
*** kenji-i has joined #openstack-meeting-301:15
*** spzala has joined #openstack-meeting-301:17
*** hoangcx has joined #openstack-meeting-301:17
*** stanzgy has joined #openstack-meeting-301:23
*** stanzgy_ has joined #openstack-meeting-301:23
*** mtanino has joined #openstack-meeting-301:28
*** salv-orlando has joined #openstack-meeting-301:29
*** mickeys has joined #openstack-meeting-301:31
*** banix has joined #openstack-meeting-301:31
*** mickeys has quit IRC01:36
*** zhurong has joined #openstack-meeting-301:39
*** VW has quit IRC01:39
*** stanchan has quit IRC01:39
*** sarob has quit IRC01:40
*** sarob has joined #openstack-meeting-301:41
*** uxdanielle has quit IRC01:42
*** s3wong has quit IRC01:43
*** salv-orlando has quit IRC01:45
*** spzala has quit IRC01:48
*** hoangcx has quit IRC02:01
*** tonytan4ever has joined #openstack-meeting-302:02
*** tonytan4ever has quit IRC02:07
*** amotoki has quit IRC02:09
*** amotoki has joined #openstack-meeting-302:10
*** salv-orlando has joined #openstack-meeting-302:11
*** iyamahat has quit IRC02:12
*** hoangcx has joined #openstack-meeting-302:14
*** salv-orlando has quit IRC02:26
*** tonytan4ever has joined #openstack-meeting-302:31
*** tonytan4ever has quit IRC02:48
*** emagana has joined #openstack-meeting-302:49
*** tonytan4ever has joined #openstack-meeting-302:49
*** salv-orlando has joined #openstack-meeting-302:52
*** emagana has quit IRC02:53
*** woodster_ has quit IRC02:59
*** banix has quit IRC03:00
*** wangbo has quit IRC03:05
*** yamamoto has joined #openstack-meeting-303:05
*** tonytan_brb has joined #openstack-meeting-303:06
*** salv-orlando has quit IRC03:07
*** tonytan4ever has quit IRC03:09
*** banix has joined #openstack-meeting-303:10
*** emagana has joined #openstack-meeting-303:15
*** julim has quit IRC03:21
*** spzala_ has joined #openstack-meeting-303:25
*** amotoki has quit IRC03:26
*** wangbo has joined #openstack-meeting-303:26
*** spzala_ has quit IRC03:26
*** salv-orlando has joined #openstack-meeting-303:33
*** zhurong has quit IRC03:35
*** amotoki has joined #openstack-meeting-303:35
*** zhurong has joined #openstack-meeting-303:36
*** VW has joined #openstack-meeting-303:41
*** kzaitsev_mb has quit IRC03:44
*** emagana has quit IRC03:48
*** salv-orlando has quit IRC03:49
*** amotoki has quit IRC03:55
*** banix has quit IRC03:55
*** SarathMekala has joined #openstack-meeting-303:56
*** yushiro has joined #openstack-meeting-303:56
*** banix has joined #openstack-meeting-303:56
*** chandanc_ has joined #openstack-meeting-303:58
xgerman#startmeeting networking_fwaas04:00
openstackxgerman: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.04:00
xgerman#endmeeting04:00
*** openstack changes topic to " (Meeting topic: ops_guide)"04:00
openstackMeeting ended Wed Jul  6 04:00:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-07-05-18.44.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-07-05-18.44.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-07-05-18.44.log.html04:00
chandanc_Hello All04:00
xgerman#startmeeting networking_fwaas04:00
openstackMeeting started Wed Jul  6 04:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is xgerman. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
*** padkrish has joined #openstack-meeting-304:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: networking_fwaas)"04:00
openstackThe meeting name has been set to 'networking_fwaas'04:00
xgermanthat was weird had to finish another meeting04:00
xgermanHi, all04:00
yushiroHi!04:00
padkrishhi xgerman04:00
SarathMekalaHi o/04:00
padkrishhi all04:00
chandanc_o/04:00
xgermanboth Nate and Sridar are traveling so they asked me to run the meeting ;-)04:01
xgerman#topic Announcements04:01
*** openstack changes topic to "Announcements (Meeting topic: networking_fwaas)"04:01
xgermanNewton-2 is next week - #link http://releases.openstack.org/newton/schedule.html04:02
xgermantime is flying!!04:02
xgermanany other announcements?04:02
*** banix has quit IRC04:03
xgerman#topic progress reports04:03
*** openstack changes topic to "progress reports (Meeting topic: networking_fwaas)"04:03
xgermanI have seen the devstack plugin merge while I was gone — great job everybody!!04:05
xgermananything we should review?04:05
chandanc_xgerman: I have posted an update of the driver patch and description04:06
chandanc_would like your comments plz04:06
*** kenji-i has quit IRC04:06
SarathMekalahttps://docs.google.com/document/d/1yGsGwVNZuptPCzMMgBH4AHVkdoeWvQxsT5Wql7-jtHI/edit?pref=2&pli=104:06
xgermanthat’s a great document. I will make sure to have a look04:07
chandanc_Me and Sarath will be concentrating on in v2 driver and test case this week, will push out something by next week04:08
yushirochandanc_, great!04:09
xgerman+104:09
chandanc_thanks :), will wait for comments04:09
xgermanwill sure have some ;-)04:09
SarathMekala:)04:10
*** dimtruck is now known as zz_dimtruck04:11
xgermanI also have seen Magret making great progress on the L3 extension work04:12
xgermananything else?04:12
* xgerman is feeling this will be a short meeting ;-)04:12
xgermanif not04:13
chandanc_Can we get a status on the l2 agent side ?04:13
chandanc_just curious04:13
chandanc_I will have to read the code for the driver part04:13
yushiroxgerman, chandanc_ L2-agent side, sorry for the slow progress. I was illness last Friday.04:14
padkrishchandanc_# Yushiro's patch is out at https://review.openstack.org/#/c/323971/04:14
*** amotoki has joined #openstack-meeting-304:14
xgermanno worries, I have been out the last 7 days...04:14
padkrishso, with your driver patch, the south bound progress will proceed :)04:15
chandanc_no problems, just want it for my referance04:15
xgermanyushiro there was some confusion if the extension should go into neutron lib or neutron. I think that got settled towards putting it into neutron04:15
padkrishthe versioned object change is pending at my side :)04:15
*** salv-orlando has joined #openstack-meeting-304:15
xgermanotherwise the extension is pretty similar to the L3 one — there are even cut&paste errors ;-)04:15
xgermanpadkrish great!!04:16
yushiroxgerman, Yes.  I'm just confusing about that.  I hope the extension will keep in neutron.04:16
xgermanthe extensions frameworks will all move to neutron-lib but the timeline is unclear04:17
yushiroxgerman, Ah,  I understand.04:17
xgermanbasically development is in neutron and when it matures it should be promoted to neutron-lib04:17
xgermanat the end (and as a criteria to stay in the stadium) FWaaS should only interface with lib04:18
yushiroI see.04:18
xgermanyeah, but with all the parts moving we decided to just tackle Neutron + FWaaS for now...04:18
xgerman#topic Open Discussion04:20
*** openstack changes topic to "Open Discussion (Meeting topic: networking_fwaas)"04:20
xgermanI think we had some discussion around the iptables/chains we should use —04:21
xgermanBasically chandanc_ proposed:04:22
xgermanhttps://www.irccloud.com/pastebin/7UVhpjqz/04:22
xgermanBTW: that whole chain thing is ripe for some extension mechanism as well but let’s not overdo it :-)04:23
chandanc_xgerman: yes, but after a little more study I think the common framework is already in place. I have some explanation in the google doc04:23
*** flwang1 has quit IRC04:23
xgermanok, so we have a plan ;-)04:23
SarathMekalaWe do not need to create a new chain04:24
chandanc_we sure have a plan :)04:24
SarathMekalaas per the new thoughts :)04:24
xgermanNice!!04:24
*** amotoki has quit IRC04:25
xgermanI just remember we broke in LBaaS or FWaaS the metering plugin (which was basically counting bytes)04:25
*** zhurong has quit IRC04:25
xgermanso there are other things which change the chains...04:25
chandanc_can I get some context of what happened ?04:26
chandanc_you mean the l3 metering part ?04:27
xgermanyeah, I think that was the plugin.04:27
SarathMekalaxgerman the main top level chains such as neutron-openvswi-FORWARD/INPUT/OUTPUT do not change04:27
SarathMekalaeach service such as SG, FWaaS inserts its related chains under them04:27
SarathMekalacorrect me if I am wrong here04:28
chandanc_I will check the metering part just to be sure04:28
SarathMekalaas per the code iptables_manager creates these top level chains04:28
SarathMekalaand are used by SG driver04:29
*** dasanind has joined #openstack-meeting-304:29
xgermanyeah, things work usually quite well but once we have the test we need to check on exotic combination like no SG and only FW and so on04:30
xgermanhave the code test exotic combinations...04:30
SarathMekalaYes.. there is also one area which is not clear04:30
*** salv-orlando has quit IRC04:30
SarathMekalaSG worked if a port was associated with multiple SGS because it did not have a deny rule04:31
SarathMekalafor FWaaS this introduces rule ordering problem04:31
chandanc_xgerman: +104:31
SarathMekalaand the need for having some priority associated04:31
*** amotoki has joined #openstack-meeting-304:31
xgermanI remember we have priorities but deny would always win and we deny by default(?)04:33
*** dasanind has quit IRC04:33
yushiroxgerman, Correct. In FWaaS v2 SPEC, it is described "deny wins" when SG and FW are mixtured.04:34
SarathMekalaYes.. deny wins across stratum04:34
SarathMekalabut in the same stratum allow wins04:34
xgermanmmh, SG would be a different stratum so...04:35
SarathMekalaam thinking of the scenario where a port is associated with two firewall groups and one allows while other denies04:36
chandanc_the confusion was, if there are more then one firewall group associated with the port, and one of them allows another denies04:36
chandanc_:) carry on04:36
SarathMekala:)04:36
xgermangot it so per our logic it would allow but it might feel funny for the user...04:36
SarathMekalaactually we dont know .. until we have some rule ordering :(04:37
chandanc_actually , it will depend on the order the iptable rules are applied on the port04:37
chandanc_:(04:37
SarathMekala:)04:37
SarathMekalaI was thinking that we should have a field called priority in the FW group04:38
SarathMekalawhich can help us in the ordering04:38
chandanc_I thnk the spec was not very clear on this, or we are missing something04:38
xgermanyeah,  groups are not ordered04:39
yushirochandanc_, SarathMekala Are you talking about following situation?  fwg1( 1.deny SSH), fwg2(1. allow HTTP, 2.deny SSH)   port is associated fwg1 and fwg2.04:39
yushiroIn this situation, what happened SSH communication?  allowed or dropped ?04:40
chandanc_yes similar, with fgw2 allow SSH04:40
chandanc_yes04:40
SarathMekalabasically contradicting FW policies on a port04:40
padkrishThen, can priority even help? since priority can also be set to same? :)04:41
*** kzaitsev_mb has joined #openstack-meeting-304:41
chandanc_good one :)04:41
SarathMekala:) yeah.. but that it will be users discretion...04:41
SarathMekalathe system can become deterministic with priority04:42
chandanc_should probably send a mail, with the explanation of the situation and give everyone some time to think through ?04:42
SarathMekalaits captured in the doc04:42
padkrishSarathMekala# Agree04:43
SarathMekalaso please provide any feedback in the comments04:43
xgerman+104:43
chandanc_my bad, will await comments04:43
xgermanchandanc_ no worries I was also hoping we could resolve tonight04:43
xgermanbut this is more complex :-(04:43
xgermananyhow, anything else?04:44
chandanc_ya, the situation is better for SG, as they only deal with allow rules04:44
*** zhurong has joined #openstack-meeting-304:45
xgerman+104:45
*** kzaitsev_mb has quit IRC04:46
xgermanI will close then04:46
xgerman#endmeeting04:47
*** openstack changes topic to " (Meeting topic: ops_guide)"04:47
openstackMeeting ended Wed Jul  6 04:47:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-07-06-04.00.html04:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-07-06-04.00.txt04:47
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-07-06-04.00.log.html04:47
yushirochandanc_,  Is it difficult to create chain per firewall-group?04:47
xgermansorry, jumped the gun04:47
yushiroxgerman, OK.04:47
chandanc_no thats not the issue04:47
chandanc_any lets catchup after the comments on the doc04:48
SarathMekalaits the ordering between the chains :)04:48
chandanc_bye for now :)04:48
yushiroOK. I'll comment it.04:48
yushirobye04:48
SarathMekalabye all o/04:48
xgermanbye + thanks everybody!!04:48
padkrishbye04:48
*** padkrish has quit IRC04:49
*** mrmartin has joined #openstack-meeting-304:50
*** _SarathMekala_ has joined #openstack-meeting-304:50
*** emagana has joined #openstack-meeting-304:53
*** SarathMekala has quit IRC04:54
*** SarathMekala_ has joined #openstack-meeting-304:56
*** salv-orlando has joined #openstack-meeting-304:57
*** yushiro has quit IRC04:58
*** _SarathMekala_ has quit IRC04:59
*** stanchan has joined #openstack-meeting-305:01
*** salv-orlando has quit IRC05:01
*** salv-orlando has joined #openstack-meeting-305:06
*** yamamoto has quit IRC05:14
*** hoangcx has quit IRC05:14
*** lpetrut has joined #openstack-meeting-305:18
*** VW has quit IRC05:26
*** asettle has joined #openstack-meeting-305:29
*** kenji-i has joined #openstack-meeting-305:33
*** mtanino has quit IRC05:34
*** asettle has quit IRC05:34
*** nkrinner_afk is now known as nkrinner05:34
*** irenab has joined #openstack-meeting-305:37
*** wangbo has quit IRC05:40
*** mrmartin has quit IRC05:41
*** zhenguo_ has joined #openstack-meeting-305:48
*** numans has quit IRC05:48
*** numans has joined #openstack-meeting-305:49
*** hoangcx has joined #openstack-meeting-305:50
*** hoangcx has left #openstack-meeting-305:51
*** armax has quit IRC05:54
*** wangbo has joined #openstack-meeting-305:54
*** yamamoto has joined #openstack-meeting-305:57
*** SarathMekala_ has quit IRC06:02
*** anilvenkata has joined #openstack-meeting-306:03
*** wangbo has quit IRC06:04
*** emagana has quit IRC06:04
*** pcaruana has joined #openstack-meeting-306:05
*** paul-carlton2 has joined #openstack-meeting-306:08
*** tonytan_brb has quit IRC06:14
*** andreas_s has joined #openstack-meeting-306:15
*** wangbo has joined #openstack-meeting-306:18
*** lpetrut has quit IRC06:23
*** sarob has quit IRC06:29
*** sarob has joined #openstack-meeting-306:30
*** sarob has quit IRC06:32
*** lpetrut has joined #openstack-meeting-306:35
*** flwang1 has joined #openstack-meeting-306:40
*** sdake has joined #openstack-meeting-306:40
*** sdake_ has joined #openstack-meeting-306:41
*** kzaitsev_mb has joined #openstack-meeting-306:43
*** sdake has quit IRC06:46
*** kzaitsev_mb has quit IRC06:48
*** bryan_att has quit IRC06:53
*** oshidoshi has joined #openstack-meeting-306:58
*** ccamacho has joined #openstack-meeting-307:03
*** amotoki has quit IRC07:03
*** lpetrut has quit IRC07:08
*** dtardivel has joined #openstack-meeting-307:09
*** salv-orlando has quit IRC07:10
*** amotoki has joined #openstack-meeting-307:12
*** tonytan4ever has joined #openstack-meeting-307:14
*** abalutoiu has joined #openstack-meeting-307:17
*** mrmartin has joined #openstack-meeting-307:18
*** tonytan4ever has quit IRC07:20
*** tmazur has joined #openstack-meeting-307:20
*** jlanoux has joined #openstack-meeting-307:26
*** jlanoux has quit IRC07:26
*** jlanoux has joined #openstack-meeting-307:27
*** chandanc_ has quit IRC07:31
*** amotoki has quit IRC07:49
*** kzaitsev_mb has joined #openstack-meeting-307:53
*** amotoki has joined #openstack-meeting-307:54
*** robcresswell has joined #openstack-meeting-307:55
*** numans has quit IRC07:57
robcresswell#startmeeting horizondrivers08:00
openstackMeeting started Wed Jul  6 08:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"08:00
openstackThe meeting name has been set to 'horizondrivers'08:00
robcresswellJust in case anyone is around:08:01
robcresswell#topic 800 UTC Meeting Cancellation08:02
*** openstack changes topic to "800 UTC Meeting Cancellation (Meeting topic: horizondrivers)"08:02
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-June/098515.html08:02
robcresswellThere's been no response to this email thread, so I'll be cancelling this meeting slot going forward08:03
robcresswell#info 800 UTC slot to be cancelled, as there were no responses to the email sent out, nor the previous IRC discussions.08:03
*** eyalb has joined #openstack-meeting-308:03
robcresswell#info Horizon Drivers and Horizon meeting will be combined in to one meeting slot, every Wednesday at 2000 UTC08:03
*** eyalb has left #openstack-meeting-308:04
*** mickeys has joined #openstack-meeting-308:04
robcresswell#info Email confirming cancellation (and link to patch updating the calendar) will be sent out later today08:04
robcresswell#endmeeting08:05
*** openstack changes topic to " (Meeting topic: ops_guide)"08:05
openstackMeeting ended Wed Jul  6 08:05:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-07-06-08.00.html08:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-07-06-08.00.txt08:05
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-07-06-08.00.log.html08:05
*** robcresswell has left #openstack-meeting-308:05
*** mickeys has quit IRC08:08
*** iyamahat has joined #openstack-meeting-308:12
*** emagana has joined #openstack-meeting-308:17
*** itxaka has joined #openstack-meeting-308:21
*** emagana has quit IRC08:21
*** ttrifonov has quit IRC08:21
*** kzaitsev_mb has quit IRC08:22
*** ttrifonov has joined #openstack-meeting-308:23
*** RuiChen has quit IRC08:23
*** iyamahat has quit IRC08:30
*** asettle has joined #openstack-meeting-308:35
*** asettle has quit IRC08:36
*** asettle has joined #openstack-meeting-308:36
*** lpetrut has joined #openstack-meeting-308:37
*** asettle has quit IRC08:44
*** kashyap has left #openstack-meeting-308:47
*** asettle has joined #openstack-meeting-308:47
*** neiljerram has joined #openstack-meeting-308:50
*** neiljerram has quit IRC08:51
*** ostroverkhov has joined #openstack-meeting-308:56
*** neiljerram has joined #openstack-meeting-308:58
*** sdake_ has quit IRC08:59
*** tonytan4ever has joined #openstack-meeting-309:16
*** tonytan4ever has quit IRC09:21
*** amotoki has quit IRC09:24
*** numans has joined #openstack-meeting-309:30
*** kzaitsev_mb has joined #openstack-meeting-309:30
*** sambetts|afk is now known as sambetts09:30
*** ociuhandu has joined #openstack-meeting-309:36
*** RuiChen has joined #openstack-meeting-309:39
*** zhurong has quit IRC09:44
*** ociuhandu has quit IRC09:48
*** tonytan4ever has joined #openstack-meeting-309:52
*** numans has quit IRC09:57
*** ostroverkhov has quit IRC10:00
*** kenji-i has quit IRC10:23
*** tmazur has quit IRC10:30
*** salv-orlando has joined #openstack-meeting-310:31
*** tmazur has joined #openstack-meeting-310:34
*** mrmartin has quit IRC10:36
*** rossella_s has quit IRC10:39
*** rossella_s has joined #openstack-meeting-310:39
*** wangbo has quit IRC10:40
*** jed56 has joined #openstack-meeting-310:41
*** salv-orlando has quit IRC10:42
*** salv-orlando has joined #openstack-meeting-310:45
*** vsaienko1 has left #openstack-meeting-310:47
*** wangbo has joined #openstack-meeting-310:53
*** yamamoto has quit IRC10:54
*** ociuhandu has joined #openstack-meeting-310:55
*** amotoki has joined #openstack-meeting-310:55
*** amotoki has quit IRC10:56
*** asettle has quit IRC10:57
*** rtheis has joined #openstack-meeting-311:00
*** ubuntu has joined #openstack-meeting-311:02
*** itxaka has quit IRC11:02
*** ubuntu is now known as Guest3801511:02
*** coolsvap has joined #openstack-meeting-311:05
*** Marcellin_ has quit IRC11:06
*** emagana has joined #openstack-meeting-311:17
*** emagana has quit IRC11:21
*** asettle has joined #openstack-meeting-311:25
*** wangbo has quit IRC11:37
*** irenab has quit IRC11:38
*** mrmartin has joined #openstack-meeting-311:41
*** kzaitsev_mb has quit IRC11:42
*** yamamoto has joined #openstack-meeting-311:42
*** chandanc_ has joined #openstack-meeting-311:48
*** wangbo has joined #openstack-meeting-311:51
*** kzaitsev_mb has joined #openstack-meeting-311:57
*** salv-orl_ has joined #openstack-meeting-311:59
*** sergio_nubeliu has quit IRC12:01
*** salv-orlando has quit IRC12:01
*** yamamoto has quit IRC12:02
*** banix has joined #openstack-meeting-312:03
*** salv-orl_ has quit IRC12:03
*** banix has quit IRC12:05
*** kzaitsev_mb has quit IRC12:06
*** vgridnev has quit IRC12:10
*** yuikotakadamori has joined #openstack-meeting-312:10
*** yamamoto has joined #openstack-meeting-312:10
*** yamamoto has quit IRC12:18
*** yamamoto has joined #openstack-meeting-312:19
*** stanzgy_ has quit IRC12:21
*** stanzgy has quit IRC12:21
*** ccamacho has quit IRC12:24
*** ccamacho has joined #openstack-meeting-312:25
*** irenab has joined #openstack-meeting-312:26
*** kzaitsev_mb has joined #openstack-meeting-312:27
*** tonytan4ever has quit IRC12:27
*** yamamoto has quit IRC12:31
*** yamamoto has joined #openstack-meeting-312:31
*** yamamoto has quit IRC12:32
*** yamamoto has joined #openstack-meeting-312:34
*** tonytan4ever has joined #openstack-meeting-312:38
*** zz_dimtruck is now known as dimtruck12:39
*** bryan_att has joined #openstack-meeting-312:43
*** tmazur has quit IRC12:44
*** claudiub has joined #openstack-meeting-312:53
*** kzaitsev_mb has quit IRC12:54
*** sdake has joined #openstack-meeting-312:56
*** VW has joined #openstack-meeting-312:56
*** kzaitsev_mb has joined #openstack-meeting-312:56
*** sagar_nikam has joined #openstack-meeting-312:58
*** VW has quit IRC12:58
*** lblanchard has joined #openstack-meeting-312:59
*** VW has joined #openstack-meeting-312:59
claudiub#startmeeting hyper-v12:59
openstackMeeting started Wed Jul  6 12:59:56 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.12:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:59
*** itoader has joined #openstack-meeting-312:59
*** openstack changes topic to " (Meeting topic: hyper-v)"12:59
openstackThe meeting name has been set to 'hyper_v'13:00
Guest38015hi all13:00
claudiubhello13:00
abalutoiuhi13:00
itoaderhi13:00
sagar_nikamHi13:00
*** yamamoto has quit IRC13:00
claudiubanyone else joining today?13:00
*** Guest38015 is now known as atuvenie13:00
atuvenie\o13:00
sagar_nikamnot sure.. today is a holiday in india...13:01
claudiuboh, I see.13:01
sagar_nikamwe can start13:01
claudiub#topic os-brick patches status13:01
*** openstack changes topic to "os-brick patches status (Meeting topic: hyper-v)"13:01
claudiubsooo... the iSCSI connector patch is merged13:02
sagar_nikamgood.... so that leaves only the nova patch ?13:02
claudiubthe fibre channel and smb ones are still pending. they got a review from hemna, to include a release note13:02
sagar_nikamok13:02
sagar_nikamthose 2 would also get merged soon ? what are the chances13:03
claudiubso, other than that, I hope they get in soon.13:03
claudiubbut it's not really up to me. :)13:03
claudiubwill ping hemna again later today,13:03
*** nkrinner is now known as nkrinner_afk13:03
sagar_nikamok13:03
claudiub#topic networking-hyperv patches status13:04
*** openstack changes topic to "networking-hyperv patches status (Meeting topic: hyper-v)"13:04
sagar_nikamone point13:04
*** woodster_ has joined #openstack-meeting-313:04
sagar_nikambefore we go to next topic13:04
*** uxdanielle has joined #openstack-meeting-313:04
sagar_nikamwe started testing this https://review.openstack.org/#/c/301233/13:05
sagar_nikamworks well atleast for nova operations... nice work13:05
sagar_nikamnow my question13:05
sagar_nikamsince the topic is on cinder13:05
sagar_nikamfor us to test cinder attach in mitaka13:05
sagar_nikamwith cluster driver13:05
claudiub#undo13:05
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f2b35e4a110>13:05
sagar_nikamare all patches that are required already merged in mitaka ?13:06
atuveniethe cluster driver atm works only with the cinder smb driver13:06
claudiubsagar_nikam: hm, not really sure what you mean. what other patches?13:06
sagar_nikamclaudiub: i meant ... any patches required in nova or os-brick13:07
*** kzaitsev_mb has quit IRC13:07
sagar_nikamthat are required for testing cluster driver for attaching volumes13:07
*** jtomasek_ has joined #openstack-meeting-313:08
sagar_nikamatuvenie: only smb volumes ? what about iscsi... we use iscsi only13:08
claudiubhm, as far as I know, there aren't any other patches, other than that.13:08
atuveniesagar_nikam: yes, atm only smb13:08
atuveniesagar_nikam: we are looking into iscsi as well, but it's a little more complicated13:08
sagar_nikamatuvenie: oh... we dont have smb as of now... nor planned in near future13:09
sagar_nikamwe only have iscsi13:09
atuveniesagar_nikam: since we can't predict where a machine will failover to, it's complicated to ensure that the target in loged in on that particular host13:09
sagar_nikambut... when i last discussed this topic many months back.. alexpilotti: mentioned that iscsi, fc and smb will all work and will be supporrted13:10
sagar_nikamatuvenie: why dont we present the iscsi volumes to all hosts in the cluster13:10
sagar_nikam?13:10
lpetrutHi guys13:10
sagar_nikamas part of attach volumes13:11
atuveniesagar_nikam: That is one option we thought about, but it can get complicated pretty fast13:11
sagar_nikamlpetrut: hi.... nice time to join... the cinder expert is here13:11
sagar_nikamwhat issues ?13:11
atuveniesagar_nikam: another thing we were considering is building a custom provider for the cluster service in hyperv that does this13:11
atuveniesagar_nikam: I think it's a little bit overkill to all the targets exposed to every host in the cluster13:14
sagar_nikamonly presented... not attached13:14
sagar_nikamas and when the vm moves to a new host in a cluster due to host failure13:15
sagar_nikammscluster will automatically attach the volume agaon13:15
sagar_nikamagain13:15
lpetrutwell, for iSCSI/FC we do passthru, so for this to happen, the volume would have to be attached to all of the hosts13:16
sagar_nikamit is a iscsi connection... should be fine i think13:16
*** mrmartin has quit IRC13:16
sagar_nikamlpetrut: yes that is the suggestion13:16
sagar_nikampresented to als the hosts13:17
lpetrutthere is another reason why simply exposing the disk to all the hosts of the cluster wouldn't solve the issue. Hyper-V identifies the disks attached to instances by the drive number, which may differ among hosts for the same shared volume13:17
*** zhurong has joined #openstack-meeting-313:18
lpetrutso, as atuvenie mentioned, the only feasible way of doing this would involve a custom cluster service provider13:18
sagar_nikamlpetrut: let me get back to you on this... my team mate bharath has done some checks on this13:19
sagar_nikamwhat is the custom cluster service provider ?13:19
lpetrutthe idea would be to have our own hooks, controlling what happens  when an instance is failed over, before being started13:20
*** cleong has joined #openstack-meeting-313:21
lpetrutstill, there may be another approach13:21
*** aserdean has joined #openstack-meeting-313:21
atuveniesagar_nikam: basically a custom provider that would be do exactly what the hyper-v one does, just that it also deals with the volumes when the machine is failed over to the host new host13:22
lpetrutif an instance having iSCSI/FC attached is failed over, it will enter an error state after being moved, as the disks are not accessible. We could just this error-state instance, attach all the disks at this stage, and then power it back on13:22
atuvenielpetrut: yeah, but that defeats the purpose of the cluster. The way it works we have minimum downtime at a failover13:23
lpetruts/just this/just take this13:23
lpetrutthat may just add a few seconds, but I think that's reasonable13:23
claudiubatuvenie: it would still be pretty minimal, imo. you'd have a few seconds downtime.13:23
*** sigmavirus_away is now known as sigmavirus13:24
lpetrutsagar_nikam: what's your view on this?13:24
sagar_nikami thought the connection_info got from cinder13:24
sagar_nikamwill have the disk number13:24
atuvenielpetrut, claudiub: I don't know, this should be investigated, but I feel that that downtime may be more than that.13:24
sagar_nikamand all the details which can help us to attach the volumes13:25
*** banix has joined #openstack-meeting-313:25
*** yuikotakadamori has quit IRC13:25
sagar_nikamalso presenting the volumes as a clustered disk.. means it gets presented to all hosts13:25
lpetrutthat's the target side LUN, but hyper-v cares about the client side disk number13:26
*** tonytan4ever has quit IRC13:26
atuvenielpetrut, claudiub: also, we are dealing with a cluster resource not a virtual machine, so when it gets in error state it may not be recoverable like a normal vm. Again, this should be investigated13:26
lpetrutatuvenie: yep, I agree, just saying that this is one possible approach13:26
sagar_nikamcluster driver not having iscsi/fc support is a major drawback13:26
*** tonytan4ever has joined #openstack-meeting-313:27
claudiubatuvenie: from my experience, you could simply reattach the disks and restart it.13:27
sagar_nikammost cloud instances will have volumes13:27
*** banix has quit IRC13:27
*** tonytan_brb has joined #openstack-meeting-313:27
*** kzaitsev_mb has joined #openstack-meeting-313:27
*** tonytan4ever has quit IRC13:28
sagar_nikamwe need to find a way to solve this issue13:28
lpetrutsagar_nikam: sure, that's why we thought that for the beginning, we'd support only SMB backed volumes, while investigating for a proper solution for iSCSI/FC volumes13:28
sagar_nikamlpetrut: ok13:28
atuvenieclaudiub: restarting it is a no no in my oppinion. If it's in a saved state, then yes, it may be ok to start it again, but restarting it is really a no no.13:28
sagar_nikamclaudiub: you mean restart the instance after failover13:29
*** vishwanathj has joined #openstack-meeting-313:29
sagar_nikam?13:29
sagar_nikambut ... failover should be transparent to the user13:29
atuvenie^ exactly13:29
claudiubatuvenie: i don't remember exactly, but if the vm couldn't start after failover, it was ending up in stopped state13:30
sagar_nikamrestarting may not be fine for tenant users13:30
*** yamamoto has joined #openstack-meeting-313:30
atuvenieclaudiub: then that is not a solution.13:30
sagar_nikamclaudiub: how is it done in nova.. other drivers ?13:30
sagar_nikamlibvirt driver13:30
sagar_nikamdoes it restart the instances ?13:30
lpetrutI think that the only way in which a reboot may be avoided is using Hyper-V replicas (which we may have to consider)13:30
claudiubsagar_nikam: as far as i know, there's only vmware that has a cluster driver.13:31
atuveniesagar_nikam: how does libvirt do what?13:31
sagar_nikami have worked on vmware driver... the volume is a vm disk there13:31
atuveniesagar_nikam: are you talking about a vmware cluster driver?13:32
sagar_nikamclaudiub: atuvenie: i meant migration trigered from nova api13:32
*** njohnston_ is now known as njohnston13:32
sagar_nikamatuvenie: vmware driver only supprts vcenter cluster13:32
atuveniesagar_nikam: I see13:32
sagar_nikamwhen migration is triggered from nova api... does it end up in rebooting the vm ?13:33
claudiubsagar_nikam: you mean cold / live migration triggered from nova api? the volumes are mounted on both source and destinaton nodes before starting the migration.13:33
atuveniesagar_nikam: claudiub: but again, in that case we know the destination beforehand13:33
claudiubbut in the case of failover, the mscluster chooses the destination node.13:33
sagar_nikamyes... live and cold migration13:33
*** dkehn__ is now known as dkehn_13:34
sagar_nikamsince we are waiting for cluster events for us to identify the vm has moved13:34
claudiubyep13:34
sagar_nikamwe use those events and update nova db13:34
sagar_nikamwith the new hostname13:34
sagar_nikamcant we do something similar here... present that volume to the moved host13:35
sagar_nikamon getting the event from mscluster13:35
lpetrutyou get the event that the instance was moved, but meanwhile it gets into an error state as it does not have the disks13:35
atuvenieyes, but by the time we get the event from mscluster, the machine is on the new host and started, which without the volumes will be in error state13:35
*** tellesnobrega_af is now known as tellesnobrega13:36
claudiubsagar_nikam: yeah, we basically get the event that the failover already happened, not that it will happen.13:36
*** tenobreg__ has joined #openstack-meeting-313:36
sagar_nikamok.. got it... then the only possibly solution.. we need to present the lun to all hosts... and find a way to get the correct disk number13:36
*** tenobreg__ has quit IRC13:36
*** asettle has quit IRC13:37
atuveniesagar_nikam: I'm not a fan of that solution, we considered it13:37
*** amotoki has joined #openstack-meeting-313:37
*** asettle has joined #openstack-meeting-313:37
sagar_nikamatuvenie: ok .. but we need some way to support iscsi and fc volumes with cluster driver13:38
*** pt_15 has joined #openstack-meeting-313:40
claudiubyeah, there has to be anyways.13:40
*** kzaitsev_mb has quit IRC13:41
claudiubspeaking of hyper-v cluster..13:41
claudiub#topic hyper-v cluster status13:42
*** openstack changes topic to "hyper-v cluster status (Meeting topic: hyper-v)"13:42
claudiubwell, it seems that nova-core has some more concerns about this feature and how it works13:42
sagar_nikamcan the patch be moved up the priority for core reviewers ?13:42
sagar_nikamoh ...ok13:42
claudiuband potential race conditions13:42
claudiubwhich is why they've decided for it to be a topic for the next nova midcycle meetup13:43
claudiubwhich will happen in 2 weeks13:43
sagar_nikamok13:43
claudiubI will be attending, armed to the teeth with answers. :)13:43
*** dimtruck is now known as zz_dimtruck13:43
sagar_nikamnice... as far as the code goes... it works as seen in our tests13:43
*** kzaitsev_mb has joined #openstack-meeting-313:44
sagar_nikamso hopefully claudiub: has all the answers and ir gets merged soon13:44
claudiubyeah, but there might be a few race conditions that we didn't / couldn't take into account13:44
sagar_nikamlike ...13:44
sagar_nikamcan you let me know where it can fail ?13:44
*** yuikotakadamori has joined #openstack-meeting-313:45
claudiubfor example, if an instance is scheduled to start on a host A, and it would fit, if a vm failovers to host A faster, the scheduled instance might not fit anymore.13:45
*** cartik has joined #openstack-meeting-313:45
sagar_nikamok13:45
claudiubplus, we have to make sure that the resource claims are also moved to the new host, in order to ensure that the scheduler has a proper resource view on the nodes.13:46
*** irenab has quit IRC13:46
sagar_nikamok....13:47
sagar_nikamin vmware driver13:47
sagar_nikamwe dont hit such issues13:47
sagar_nikamsince one compute -- one cluster13:47
*** irenab has joined #openstack-meeting-313:47
claudiubanyways, until then, we'll have to get this in: https://review.openstack.org/#/c/335114/13:47
sagar_nikamhere we have n computes for n hosts in a cluster13:47
claudiubit improves host the driver handles shared storage, which is a must for the cluster driver anyways.13:48
sagar_nikamok13:48
claudiubsagar_nikam: yeah, that's true, but on the vmware there are other issues regarding this13:49
*** mrmartin has joined #openstack-meeting-313:49
sagar_nikamclaudiub: any thoughts on having a single nova-compute for a cluster ?13:49
sagar_nikami meant mscluster13:49
sagar_nikamone main question... where do we run it13:49
claudiubsagar_nikam: for example, on a vmware cluster, the scheduler might see that the cluster has 128 GB memory free, but that doesn't mean you can spawn an isntance with 128 gb memory there13:50
claudiubas that 128 gb free is spread across the whole cluster.13:50
sagar_nikamagree.... i have seen this issue in vmware driver13:50
sagar_nikamnot just memory, same problem for disk as well13:51
claudiubsagar_nikam: the mscluster is a clustered service, meaning it will run in the cluster. anywhere / everywhere.13:51
claudiubsagar_nikam: if at one point it is on host A, if host A goes down, it restarts on host B.13:51
claudiubsagar_nikam: same as any other clustered service / resouce.13:51
sagar_nikamno ... i meant where do we run nova-compute13:52
claudiubsagar_nikam: ah, gotcha. on each compute node.13:52
sagar_nikamif we go with the option of one novacompute per mscluster13:52
sagar_nikamjust got a idea... but too many issues... may not be a good option13:53
claudiubsagar_nikam: there was a discussion about this before this spec was approved in the first place. and having a nova-compute on each node was the most favorable one13:53
sagar_nikamok13:53
*** rbak has joined #openstack-meeting-313:53
claudiubmoving on, as we are short on time.13:53
*** azemlyanov has joined #openstack-meeting-313:54
claudiub#topic networking-hyperv patches status13:54
*** openstack changes topic to "networking-hyperv patches status (Meeting topic: hyper-v)"13:54
claudiub#link https://review.openstack.org/#/c/332715/13:54
claudiub^ this merged on master13:54
sagar_nikamwe have almost used most time of this meeting for cluster driver. nice discussion... we need to find a way to slve iscis spport13:54
claudiubit fixes the issue when the security group is changed on a port.13:54
*** jlanoux has quit IRC13:54
claudiubbackported it to mitaka.13:54
sagar_nikamok nice13:54
sagar_nikamwill let vinod know about it13:55
sagar_nikam5 mins only13:55
claudiubduring last week's meeting, vinod said that he couldn't replicate the bug on liberty.13:55
sagar_nikamok13:55
claudiubso, it seems it doesn't affect liberty.13:55
claudiub#link https://review.openstack.org/#/c/328210/13:55
sagar_nikamwe are slowly moving to mitaka13:55
claudiubthis has a few comments, but hyper-v ci is passing, which is good.13:56
sagar_nikamwe will check this patch13:56
claudiubsagar_nikam: cool, sounds good. :)13:56
sagar_nikamlast topic.. before time ends13:56
*** dasanind has joined #openstack-meeting-313:56
sagar_nikamwhat's happening on freerdp13:56
claudiubso, if the comments are addressed, +2 from my part.13:56
claudiub#topic open discussion13:56
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:56
sagar_nikamwe raised a defect13:56
sagar_nikamfreerdp does not support tls enabled keystone endpoint13:57
*** c64cosmin has joined #openstack-meeting-313:58
claudiubc64cosmin: ohai13:58
c64cosminhi13:58
*** cartik has quit IRC13:58
sagar_nikamhi13:58
sagar_nikamhow is freerdp work ?13:58
sagar_nikamany new solution for the issue we found ?13:59
c64cosminwell, this are going well, just that I must delay that work for a bit13:59
*** yuikotakadamori has quit IRC13:59
c64cosminI've been asigned a new project13:59
sagar_nikamok13:59
c64cosminbut it seems that the problem you have is solvable13:59
sagar_nikamok13:59
c64cosminthe https keystone I suppose14:00
sagar_nikamalmost end of time14:00
claudiubyeah..14:00
sagar_nikamwe can discuss offline14:00
claudiubi'll have to end it here14:00
sagar_nikamthanks all14:00
claudiubthanks folks for joining, see you next week!14:01
claudiub#endmeeting14:01
*** openstack changes topic to " (Meeting topic: ops_guide)"14:01
openstackMeeting ended Wed Jul  6 14:01:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-06-12.59.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-06-12.59.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-07-06-12.59.log.html14:01
*** dasanind has quit IRC14:01
*** geo__ has joined #openstack-meeting-314:01
*** atuvenie has quit IRC14:02
*** julim has joined #openstack-meeting-314:03
*** zz_dimtruck is now known as dimtruck14:05
*** vhoward has joined #openstack-meeting-314:06
*** sagar_nikam has quit IRC14:10
*** jtomasek_ has quit IRC14:12
*** VW has quit IRC14:13
*** amotoki has quit IRC14:15
*** marst has joined #openstack-meeting-314:15
*** c64cosmin has quit IRC14:24
*** zhurong has quit IRC14:24
*** rbrndt has joined #openstack-meeting-314:27
*** aarefiev has quit IRC14:28
*** aserdean has quit IRC14:30
*** aarefiev has joined #openstack-meeting-314:30
*** oshidoshi has quit IRC14:31
*** emagana has joined #openstack-meeting-314:31
*** sdake has quit IRC14:33
*** sdake has joined #openstack-meeting-314:33
*** amotoki has joined #openstack-meeting-314:34
*** azemlyanov has quit IRC14:36
*** emagana has quit IRC14:36
*** rossella_s has quit IRC14:39
*** rossella_s has joined #openstack-meeting-314:39
*** yamahata has joined #openstack-meeting-314:39
*** VW has joined #openstack-meeting-314:39
*** iyamahat has joined #openstack-meeting-314:40
*** Fdaisuke_ has joined #openstack-meeting-314:40
*** rhochmuth has joined #openstack-meeting-314:49
*** ezpz has joined #openstack-meeting-314:50
*** armax has joined #openstack-meeting-314:51
*** galstrom_zzz is now known as galstrom14:52
*** Kamil has joined #openstack-meeting-314:55
*** bklei has joined #openstack-meeting-314:56
*** Swami has joined #openstack-meeting-314:58
*** hosanai has joined #openstack-meeting-314:58
*** Swami_ has joined #openstack-meeting-314:58
*** witek has joined #openstack-meeting-314:59
*** cbellucci has joined #openstack-meeting-315:00
*** emagana has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jul  6 15:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rbrndto/15:01
*** tsv has joined #openstack-meeting-315:01
rbako/15:01
bkleio/15:01
Kamilo/15:01
witekhello15:01
ezpzo/15:01
tsvo/15:01
shinya_kwbto/15:01
rhochmutho/15:01
Fdaisuke_o/15:01
hosanaio/15:01
*** koji has joined #openstack-meeting-315:01
rhochmuthagenda at: https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthAgenda for Wednesday July 6, 2016 (15:00 UTC)15:02
rhochmuth1. https://blueprints.launchpad.net/monasca/+spec/delete-metrics15:02
rhochmuth2. https://blueprints.launchpad.net/monasca/+spec/read-only-api-user15:02
rhochmuth3. Beaver log agent, status?15:02
rhochmuthFairly light agenda today15:02
rhochmuthso we can leave time at the end for general discussion15:02
rhochmuth#topic delete metrics15:02
rhochmuthhttps://blueprints.launchpad.net/monasca/+spec/delete-metrics15:02
*** openstack changes topic to "delete metrics (Meeting topic: monasca)"15:02
bkleithat's me15:02
*** abalutoiu has quit IRC15:03
bkleihave we discussed this before?  it's use-case we really need here at charter.  the ability for our MaaS customers to delete their own metrics15:03
bkleiwe've found it's an iterative process when pushing metrics in -- don't get it right the first tiem15:03
bkleitime15:04
bkleiwe'd like our customers to be able to do their own cleanup15:04
rhochmuthDELETE /v2.0/metrics15:04
bkleiright15:04
rhochmuthjust use that15:04
bkleiwait -- that's there? :)15:04
*** itoader has quit IRC15:05
rhochmuthDELETE /v2.0/metrics/measurements15:05
*** ddieterly has joined #openstack-meeting-315:05
rhochmuthso are those the proposals15:05
ddieterlyo/15:05
rhochmuththe two proposals15:05
*** pcaruana has quit IRC15:06
*** Christian_ has joined #openstack-meeting-315:06
rhochmuththe first one would delete the entire metric and all measurements15:06
*** banix has joined #openstack-meeting-315:06
bkleiwould like both i guess -- but if i had to pick one, i'd prefer DELETE /v2.0/metrics if it cleans up measurements15:07
*** silvamatteus has joined #openstack-meeting-315:07
*** dasanind has joined #openstack-meeting-315:07
*** emagana has quit IRC15:07
bkleias long as DELETE /v2.0/metrics supported specifying dimensions15:07
rhochmuththe first one, with support for metric name, dimensions, as filter options would seems to make sense to me15:08
rbrndtThis is just for deleting historical data?15:08
rhochmuthmetrics measurements15:08
bkleiyeah -- i agree.  our current prune script supports more granularity of measurements by timestamp range, but i think we wouldn't need that for our customers15:08
bkleiyes -- both bogus metrics/dimensions, and corresponding historical measurements15:09
rhochmuthhave you looked at performance15:09
rhochmuththis used to run very slow in vertica for example15:09
rhochmuthbut i think you mentioned they improved perforamance15:09
bkleiyes -- on the vertica side.  we run a prune job nightly15:09
rhochmuthi'm not sure about influxdb15:09
*** dasanind has quit IRC15:09
rhochmuthor cassandra15:09
bkleii'm not sure about either of those either15:10
rhochmuthso, you don't see performance hit in vertica when deleting metrics15:10
rhochmuthin vertica deletes were slow and involved a full table lock as row locks weren't supported15:10
rhochmuthso, the db would be locked out while vertica did it15:10
bkleivertica 7.2 works fine -- the performance depends on what % of the measurements table you are deleting15:10
rhochmuthit's thing15:11
rhochmuthdoes it lock out the db when deleting15:11
bkleiwe do see brief kafka lag during the prune job -- but it's only a couple of minutes, and we're deleting a large amount of data across all projects nightly15:11
bkleiyes15:11
rhochmuthhow would you prevent potential customer abuse15:12
rhochmuthinadvertent dos attack for example, non-malicious15:12
rhochmuthcustomer says, delete all metrics,15:12
rhochmuththen the db is taken out for a while15:12
rhochmuthor locked out15:12
bkleiit's a potential issue15:13
rhochmuthi guess i was thinking about implementation15:13
rhochmuththe simple implementatino is a direct invocation of truncate or whatever in the db, directly from the API15:14
rhochmuthbut, i'm wondering if a separate micro-service would be a better approach, so that deletes could be schedule and occur async over some longer time-period15:14
bkleiyes -- in terms of vertica implementation -- it's a DELETE from.. https://github.com/openstack/puppet-monasca/blob/master/templates/vertica/prune_vertica.py.erb15:15
bkleihmm.  a separate service that batches things up.  that could alleviate the dos concern15:16
rhochmuthI see15:16
rhochmuthmonasca-delete15:16
rhochmuthanyway, i think there needs to be some discussion on implementation15:17
bkleii like that idea -- i can expand the blueprint and discuss implementation alternatives15:17
rhochmuthis this one we should cover at the mid-cycle15:17
rhochmuththx15:17
bkleiyeah -- i think that's appropriate, i'll beef up the blueprint15:17
bkleiprior to that15:17
*** emagana has joined #openstack-meeting-315:17
rhochmuthprobably should add as an agenda item to the mid-cycle15:18
*** Swami__ has joined #openstack-meeting-315:18
rhochmuthshould we move onto the next topic then?15:18
bkleisure -- will add it when i find the link :)15:18
*** kzaitsev_mb has quit IRC15:18
bkleigot it15:18
*** tonytan_brb is now known as tonytan4ever15:18
rhochmuth#topic https://blueprints.launchpad.net/monasca/+spec/read-only-api-user15:19
*** openstack changes topic to "https://blueprints.launchpad.net/monasca/+spec/read-only-api-user (Meeting topic: monasca)"15:19
*** yamamoto has quit IRC15:19
rhochmuthRead only API15:19
bkleithat' me too15:19
bkleiright now -- we basically have two API roles, one can POST only, and one can do everything else15:20
*** kzaitsev_mb has joined #openstack-meeting-315:20
bkleibut -- we'd like to have dashboard/operator users who can see data, but not POST (or DELETE :))15:20
*** yamamoto has joined #openstack-meeting-315:20
bkleigrafana supports read-only, we'd like to map those users to back-end readonly15:20
bkleidoes this seem like a use-case others would benefit from?15:21
*** Swami has quit IRC15:21
bkleior -- do folks object :)15:22
rhochmuthi think it is useful to be able to restrict users to read only access15:22
bkleii don't think it would be a huge change15:22
*** galstrom is now known as galstrom_zzz15:23
rhochmuthi was hoping in the cas of python that we would implement openstack RBAC15:23
bkleifor sure15:23
bkleiif folks agree the idea is OK, i'll work the change, both python/java15:23
rhochmuthunfortunately, the Java code doesnt' have a similar library15:23
bkleiright -- but the functionality is there, i'll just extend it15:24
witeksounds good to me15:24
bkleithx witek15:24
rhochmuthsounds fine to me15:25
bkleianyone else object? otherwise i'll press ahead with a patch15:25
witek:)15:25
rhochmuththere are probably a few details to discuss15:25
bkleilike role name?  i was going to follow suit and make configurable15:25
rhochmuthwhat is your time-frame for implementation15:25
bkleisoon -- probably start in a week or so15:26
*** mtanino has joined #openstack-meeting-315:26
rhochmuthsounds like new topic time15:27
rhochmuth#topic Beaver log agent, status?15:27
*** openstack changes topic to "Beaver log agent, status? (Meeting topic: monasca)"15:27
bkleithx15:27
witekI wanted to ask about the status of the Beaver log agent15:28
witekwould it be possible to contribute to that?15:28
rhochmuthinteresting, i just got an email from tsv this morning15:28
rhochmuthi thought i saw him join the meeting15:28
tsvwitek: I am refactoring the existing pull request and added some unit tests. will push an update today or tomorrow max15:28
witekwhere is the repo?15:28
tsvhttps://github.com/python-beaver/python-beaver/pull/40615:29
witektsv: thanks15:29
rhochmuthwitek: are you interested in the beaver agent?15:29
tsvwitek: will send you the link once my updates are in15:29
witekyes15:29
rhochmuthare you thinking about moving for logstash to beaver?15:30
witekwe have an internal POC where we don't want to install logstash15:30
*** andreas_s has quit IRC15:30
witekmore like an alternative15:30
rhochmuthok15:30
tsvrhochmuth: sorry about the short notice. fell sick over the weekend15:31
rhochmuthnp15:31
witekso, python-beaver sends logs to logstash?15:32
tsvwitek: it is highly configurable. the pull request i am working on adds a monascalog transport - which would send the logs to monasca log api15:33
witeki see15:33
*** salv-orlando has joined #openstack-meeting-315:34
witekwe have added the pull request with our logstash output plugin to logstash-plugins repository15:34
witekhttps://github.com/logstash-plugins/logstash-output-monasca_log_api/pull/115:34
witekbut it does not get much attention :(15:35
tsvwitek: i see, will check it out15:35
rhochmuth9 days no comments15:35
rhochmuthdo we need to vote for it15:36
witekfor choosing the agent?15:36
rhochmuthfor merging your pr15:36
rhochmuthi thought there was a way to thumbsup the pr15:37
witekoh, I think one comment from you or tsv would be enough for now15:37
bkleipr == parole officer?15:37
rhochmuthpull request15:37
rhochmuthbklei: are you planning on a bp for dimensions15:39
tsvwitek: just left a comment15:39
witekthanks a lot!15:39
bkleican if you want rhochmuth15:39
rhochmuthi think that would be good15:39
bkleiwill add it15:40
rhochmuthwhat is the response that you are thinking about providing15:40
rhochmuthalso, we have dimenion names and dimension values15:40
*** bpokorny has joined #openstack-meeting-315:40
rhochmuthjust wondering if you are thinking about two resources15:40
rhochmuthor just one called dimensions15:40
rhochmuthi then to think of this as two resources15:41
rhochmuthdimension-names15:41
rhochmuthdimension-values15:41
bkleithe use-case we're working for grafana is basically dimension-values15:42
bkleifor a given dimension name -- what are the possible values15:42
bkleiexample output15:42
bklei{15:42
bklei   "links":[15:42
bklei      {15:42
bklei         "rel":"self",15:42
bklei         "href":"http://dev02-monasca-001.os.cloud.twc.net:8070/v2.0/metrics/dimensions?name=hostname"15:42
bklei      }15:42
bklei   ],15:42
bklei   "elements":[15:42
bklei      {15:42
bklei         "id":null,15:42
bklei         "name":"hostname",15:42
bklei         "values":[15:42
bklei            "dev02-compute-001",15:42
bklei15:42
bkleinot done, but u get the idea15:43
bkleii wasn't planning an api to get all the dimension names -- is there a need for that?15:43
bkleirbak?15:43
rbakI didn't really see a need for that, at least not in grafana.15:43
rhochmuthi thought it would be seful to get just the dimension names, given a metric name15:44
rbakBut you can already do that using metric-list with a metric name15:44
rhochmuththe problem with returning all the dimension values, is that could be a huge list15:44
rhochmuthmetric-list also returns a huge list15:45
bkleiwill need pagination/limit for sure15:45
bkleieven though potentially huge, still faster and smaller than metric-list15:45
rhochmuthso, let's say the user selects "vm.cpu.user_perc"15:45
rhochmuthas the metric name15:45
bkleithis is for templating -- metric name not part of the request15:46
*** Sukhdev has joined #openstack-meeting-315:46
rhochmuththere are potentially hundreds of thousands if not millions of VMs15:46
rhochmuththere are maybe around 5-50 dimensions for the metric15:47
rhochmuth5-1015:47
rbakSure, but the getting just the dimension values is far better than getting a full metric-list15:47
rhochmuthagree15:48
bkleiour current issue is metric-list kills the browser when trying to build a template15:48
bkleipaginates until it's out of memory15:48
rhochmuthbut, i want to leave a api spot open for just getting dimension names15:48
rbakWhy is that necessary though?15:49
rhochmuthso, you can got from name, to dimension name to dimension value15:49
*** sambetts is now known as sambetts|afk15:49
rhochmuthi think it is more of a question around optimizing the result set15:49
bkleiwe pretty much have that?  you can --name with metric list15:50
rbakYou can already accomplish that with a metric-list though.  We already do this in grafana and it's pretty instant.15:50
rhochmuthbut, you are going to get all the unique metrics for a specific metric name15:50
rbrndtmetric-list gives a set of dimension sets, lots of duplicates. The dimensions-name would give just a list of the unique dimension names15:50
rhochmuththx rbrndt15:51
*** asettle has quit IRC15:51
rbakI suppose.  That's just never been a problem for us.15:51
bkleiok -- maybe there's a middle ground, maybe i implement dimension-values for now, can add dimension-names later?15:51
*** abalutoiu has joined #openstack-meeting-315:51
bkleiand for dimension-values, i can add an optional metric name?15:52
bkleibut templating in grafana wouldn't use it15:52
rbrndtThe problem the dimension names resource is more useful for is the case of a single metric names with millions of dimensions sets associated15:52
rhochmuththat was the case i was thinking of15:53
rbrndtwhich occurs with lots of vas and a high churn rate15:53
rbrndts/vas/vms15:53
rhochmuthfor the operator/admin account15:53
rhochmuthi don't think this would be required for maas customers/tenants15:53
rhochmuthbut in the case of the operator/tenant account where every vm in the system is accessible, it would be useful15:53
bkleidon't disagree, we just haven't run across the use-case asking for that yet15:54
rhochmuthwe've been hitting it15:55
rhochmuthsince we've been more focused on the operational monitoring problem15:55
rhochmuthand not maas as much yet15:55
bkleiunderstood15:55
bkleii'll add a BP and we can hash this out there?15:56
rhochmuththx15:56
bkleihopefully i can press fwd with dimension-valuse15:56
bkleivalues15:56
*** jplopezgu_ has left #openstack-meeting-315:56
rhochmuthyes, please proceed15:56
bkleigracias15:57
rhochmuthso, any other quick topics in closing15:57
rhochmuthjust a few minutes left15:57
*** cbouch has joined #openstack-meeting-315:57
rbakrhochmuth: Did you ever get that new monasca-grafana-datasource repo we talked about a couple weeks ago?15:57
*** Rockyg has joined #openstack-meeting-315:57
rhochmuththanks for reminding me15:58
rhochmuthi'll get it submitted15:58
rhochmuthsorry15:58
rbaknp.  thanks for doing that.15:58
*** catherineD|2 has joined #openstack-meeting-315:58
rhochmuthhow are your disucssions going with grafana btw15:58
Rockygo/15:58
*** gema has joined #openstack-meeting-315:59
*** vhoward has quit IRC15:59
rbakNot a lot of progress.  We'll keep you updated as we hear more.15:59
rhochmuthok, thx15:59
rhochmuthlooks like ending the meeting15:59
*** seldenr has joined #openstack-meeting-315:59
*** ddieterly is now known as ddieterly[away]15:59
rhochmuththanks everyone15:59
witekthank you16:00
*** cjvolzka has joined #openstack-meeting-316:00
*** cbellucci has quit IRC16:00
*** iyamahat has quit IRC16:00
*** Kamil has quit IRC16:00
*** hosanai has quit IRC16:00
*** koji has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to " (Meeting topic: ops_guide)"16:00
openstackMeeting ended Wed Jul  6 16:00:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-06-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-06-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-07-06-15.00.log.html16:00
hogepodge#startmeeting defcore16:01
openstackMeeting started Wed Jul  6 16:01:04 2016 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
hogepodge#chair markvoelker eglute16:01
openstackWarning: Nick not in channel: markvoelker16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
*** Fdaisuke_ has left #openstack-meeting-316:01
egluteo/16:01
Rockygo/16:01
*** rbrndt has left #openstack-meeting-316:01
*** bklei has quit IRC16:01
VanLo/16:01
gemao/16:02
catherineD|2o/16:02
hogepodge#link agenda https://etherpad.openstack.org/p/DefCoreLunar.1016:02
*** yamahata has quit IRC16:02
hogepodge#topic Sessions for Barcelona16:02
*** openstack changes topic to "Sessions for Barcelona (Meeting topic: defcore)"16:02
*** witek has left #openstack-meeting-316:03
hogepodgeThe call for proposals closes this week for the OpenStack Summit in Barcelona. If you've submitted a talk or are planning to, can you add a link or description to the etherpad?16:03
gemahogepodge: a talk about defcore or about anything?16:04
hogepodgeGenerally about defcore or refstack or interop, but if you have any other talks you've submitted I'd like to hear about them too. :-D16:04
gemaalright16:05
hogepodgeHas anyone submitted anything yet?16:05
egluteno.. have you?16:05
hogepodgeNo, not yet.16:05
hogepodgeOk, moving on.16:05
gemaI have submitted two about running clouds on AArch64 and by ODS I will have notes also on how interoperable they are16:05
*** eliqiao has quit IRC16:05
*** ddieterly[away] is now known as ddieterly16:05
eglutei think having defcore 101 session would be good, what do ohters think16:06
gemaeglute: +116:06
hogepodgegema: great! can you put a link or abstract into the etherpad?16:06
Rockyg++16:06
gemahogepodge: yeah, no prob16:06
*** yamamoto has quit IRC16:06
hogepodgeeglute: I think a 101 would be good, I really want to make sure it captures the process practically from testing to flagging to evaluating16:06
hogepodgeI can start to put something together for it16:07
eglutehogepodge sounds good!16:07
gemaif we do a 101 talk, we should include a bit about the test spec16:07
*** eliqiao has joined #openstack-meeting-316:07
gemaso developers are aware16:07
eglutegema +116:07
hogepodgegema: +116:07
Rockygi think it's good to have the 101 talk and a soon to be/nw capabilities requirement/what's changing talk16:07
egluteRockyg +1 on changes16:07
RockygI think that should be every summit16:08
eglutewe should have working group session(s) again as well16:08
eglutewhere we will be covering changes16:08
hogepodge#link call for speakers page https://www.openstack.org/summit-login/login?BackURL=%2Fsummit%2Fbarcelona-2016%2Fcall-for-presentations%2F16:08
eglutebut if we have a general session, we can cover changes as well16:08
hogepodgeWorking group sessions will be sorted out later this summer, and I'll have more information about how we can get one or two once the process opens16:09
Rockygthanks, hogepodge16:10
hogepodgeok, anything else?16:10
hogepodge#topic flag os-network extension tests16:11
*** openstack changes topic to "flag os-network extension tests (Meeting topic: defcore)"16:11
hogepodge#link https://review.openstack.org/#/c/329220/16:11
*** seldenr has left #openstack-meeting-316:11
hogepodgeVanL: eglute: it doesn't like like dwalleck is here today? Do you have any updates on the status of this?16:11
*** ddieterly is now known as ddieterly[away]16:12
egluteI do not...16:12
VanLThis is a pretty straightforward flag request16:12
VanLThere is an additional functionality being pulled in - os-networks16:12
hogepodgeWe were hoping for more updates on the progress in Tempest. As part of flag requests we want to encourage engagement with upstream so we can make sure the underlying issue is resolved16:12
VanLWe can try to do that, but time is short due to some other factors16:13
eglute+1 on more involvement, but we shouldnt hold back the PR. I had +1 only for more discussion, will change it to +216:14
VanLThere was one -1, looks like due to formatting that is now fixed16:14
VanLotherwise its +616:14
VanLeglute +1 - this shouldn't be controversial16:15
*** alex_xu has quit IRC16:15
VanL:)16:15
hogepodgeVanL: based on the comments from markvoelker it appears part of the holdup is following up with a bug16:15
hogepodgeIt's not controversial, but we'd like to track the progress and create an environment where we can come back to these problems and try to fix them at the source16:16
VanLI can chase down Daryl. I just know that he has a bunch of other things on his plate that have been put higher than this16:16
hogepodgeUnderstand16:16
VanLHe is, unsurprisingly, following the orders of his direct manager - who is telling him to work on other things, not upstream tempest right now.16:17
VanLHe's out of round tuits for a while due to some of the other issues that have been bubbling here over the past months16:17
Rockyghogepodge, perhaps we wan get a defcore impact tag in tempest?  It might raise the visibility of our bugs16:18
hogepodgeok16:18
VanLCan we +2 the PR?16:18
*** mrmartin has quit IRC16:18
eglutei am ready to move it forward, unless there are other comments16:18
hogepodgeIf your cloud isn't running upstream code it's difficult to reproduce and make sure the problem is fixed. I can +2, but I don't feel ok merging until markvoelker +2s it also.16:19
egluteMark had it at +1,16:20
VanLThe issue is an atomic test issue - it pulls in a non-defcore function16:20
egluteI changed mine to +2.16:20
VanL(Turns out we have this function, but we have it on a different URL path due to... reasons..., but fixing that will take too long for right now.)16:21
hogepodgeLet me look at the test and see how deep it funs. I'll review post meeting today.16:21
eglutethank you hogepodge16:21
hogepodges/funs/runs/16:21
hogepodge#topic Move network router tests16:22
VanL(We plan on fixing the URL path, but right now this should be flagged)16:22
*** openstack changes topic to "Move network router tests (Meeting topic: defcore)"16:22
hogepodge#link https://review.openstack.org/#/c/326755/16:22
*** iyamahat has joined #openstack-meeting-316:23
*** bryan_att has quit IRC16:23
hogepodgecatherineD|2: do you have an input on this review?16:23
hogepodgeIs Charles around?16:23
cjvolzkaI am16:23
*** yamahata has joined #openstack-meeting-316:25
cjvolzkaI only noticed this because we don't yet support routers causing us to fail these tests. Since all the other routers tests were put under L3 it made sense to me that these should as well.16:25
hogepodgecjvolzka: ok, makes sense16:26
eglute+216:26
hogepodgeI'll give it a review after the meeting, any other comments on this?16:26
cjvolzkaOnce L3 moves out of advisory then these would all become required again. As they are now we're indirectly requiring router functionality even though routers aren't yet required.16:26
*** markvoelker has joined #openstack-meeting-316:27
hogepodgecjvolzka: yeah, do you think at L3 is something that is reasonably required for defcore given the multitude of networking models?16:27
cjvolzkaThere was some debate on this in the past when routers was first proposed. We don't currently support it, but that's only ancedotal. We're more private cloud focused but it is on our roadmap.16:29
hogepodgecjvolzka: understand. will you make the mid-cycle? I think this could be a useful topic for discussion during one of our sessions there16:30
catherineD|2hogepodge: in general, required capability (L2)  should not include non-require capability (L3) for 2016.08 ...16:30
*** david-lyle_ has joined #openstack-meeting-316:30
cjvolzkahogepodge: Sadly no :(16:30
hogepodgecjvolzka: ok, could you send me or the mailing list an e-mail so I can get some background for discussion?16:31
cjvolzkahogepodge: sure, np16:31
hogepodgenetworks is going to be a really big addition, and I want to make sure we get as much of it right early as we can16:32
*** david-lyle_ is now known as david-lyle16:32
hogepodgecjvolzka: thank you16:32
hogepodgeanything else on this topic?16:32
hogepodge#action hogepodge to add networks agenda item to midcycle16:33
hogepodge#topic Maintenance and flag patches16:33
*** openstack changes topic to "Maintenance and flag patches (Meeting topic: defcore)"16:33
hogepodge#link Flags not carried forward https://review.openstack.org/#/c/310582/16:33
hogepodgeThat patch reconciles the flags on 2015.07 and 2016.0116:34
eglutelooks good to me!16:34
hogepodgecatherineD|2: had a policy question about it that I need to answer16:34
hogepodge#link Gate on active guidelines https://review.openstack.org/#/c/335251/16:34
catherineD|2hogepodge: yea just a question about : Should flags identified in a latest guideline be carried backward to previous guidelines? if so, how many previous guidelines needed to be updated.16:34
hogepodgecatherineD|2: I would think just to active guidelines16:34
catherineD|2ok make senses .. Adding flags will not affect results ... removing flags will16:35
*** ddieterly[away] is now known as ddieterly16:35
hogepodgecatherineD|2: yeah, and it changes the optics of previous guidelines if we change them16:35
eglutelooks like Mark just gave it +2, so if no objections, i will merge it16:36
markvoelkerAnd they only need to be carried forward if the rationale for the flag is still valid.16:36
hogepodgemarkvoelker: +116:36
hogepodgemarkvoelker: yeah, that should be one of the last things we do before presenting next to the board, pulling flags forward or dropping them as needed16:36
catherineD|2hogepodge: ++16:36
Rockyg++16:36
*** kzaitsev_mb has quit IRC16:37
* markvoelker is on a slow mobile link from somewhere in the Appalachians so please pardon me being quiet today16:37
hogepodge#link Add test aliases https://review.openstack.org/#/c/329577/316:37
catherineD|2hogepodge: I reviewed this one16:37
*** yamamoto has joined #openstack-meeting-316:37
hogepodgeMore tempest tests moved, I helped write that patch up and the submitter is very anxious about landing it.16:37
hogepodgecatherineD|2: ty16:37
catherineD|2Adding alias to these tests does not help or hurt anything ...16:38
egluteready to merge then?16:38
catherineD|2first of all these were flagge tessts since Dec 2015 and subject to remove and indeed were removed16:38
catherineD|2and the test does not exist any more ...16:39
*** david-lyle has quit IRC16:39
hogepodgecatherineD|2: I see16:39
catherineD|2I don't mind either way but how do we prevent users from spending time on non-necessary debug?16:39
eglutecatherineD|2 good question... topic for midcycle?16:40
hogepodgecatherineD|2: eglute: +1 on midcycle topic16:40
catherineD|2perhaps educate users that if the flagged message state to be removed ... then users should not pay attention to them?16:40
catherineD|2yea let's add it the midcycle ..16:41
hogepodgecatherineD|2: and that they don't need to pass them. I had a very difficult time communicating this.16:41
catherineD|2meanwhile we can merge the patch for the effort ... but it is really useless16:41
eglutemerged already, thanks markvoelker16:41
hogepodgeAnything else on these?16:42
hogepodge#topic Regroup capabilities16:42
*** openstack changes topic to "Regroup capabilities (Meeting topic: defcore)"16:42
hogepodge#link https://bugs.launchpad.net/defcore/+bug/157916216:42
openstackLaunchpad bug 1579162 in defcore "Group capabilities consistently" [Low,New]16:42
*** Swami__ has quit IRC16:42
hogepodgeVanL: and I were going to work on this, but I think we were sidetracked with other issues.16:43
*** Swami_ has quit IRC16:43
hogepodgeI was going through the bug tracker this morning and was reminded of it.16:43
VanLI had totally forgotten16:43
*** ezpz has left #openstack-meeting-316:43
hogepodgeBasically, the issue is the grouping if networks capabilities is inconsistent with other capabilities, and looking at reconciling it.16:43
hogepodgeI brought it up just to remind ourselves about it.16:44
hogepodgeAnyone have comments on it?16:44
eglutehogepodge and VanL if you have a proposal for midcycle, we could review it then?16:44
VanLThat would work16:45
hogepodgeeglute: sure, just have to write it up16:45
*** alaski has joined #openstack-meeting-316:45
eglutethank you :)16:45
hogepodgemidcycle is filling up rather rapidly, which brings us to the next topic16:45
hogepodge#topic DefCore Mid-cycle/Sprint16:45
*** kzaitsev_mb has joined #openstack-meeting-316:45
*** openstack changes topic to "DefCore Mid-cycle/Sprint (Meeting topic: defcore)"16:45
hogepodgeThank you VanL and eglute for arranging space for us at RAX San Antonio16:45
gema+1, thanks!16:46
egluteit was all VanL!16:46
hogepodgemarkvoelker has put together an initial agenda16:46
hogepodge#link https://etherpad.openstack.org/p/DefCoreSummer2016Sprint16:46
hogepodgeWe should be looking at the topics and making comments so we can nail down the final agenda.16:46
VanLFYI, this was from our internal team: "we were able to reserve 1479 for the original dates provided below.  This meeting room is off the main lobby and has the below necessary room requirements.  Reminder that all visitor names will need to be provided to the Front Desk at least a day prior to arrival."16:47
eglute#action everyone: add your name/company if attending midcycle in person16:47
hogepodgeVanL: thanks, I added that note to the etherpad agenda16:48
*** yamamoto has quit IRC16:48
hogepodge#action everyone review agenda and propose additions/changes16:49
VanLThere will be food trucks around on Tuesday, and there are a number of close restaurants Wed/Thurs. I'll make sure we have snacks.16:49
*** yamahata has quit IRC16:49
hogepodgeAnything else on this?16:50
VanLDrinks will also be available16:50
VanLand provided16:50
eglutei will send out calendar invite for midcycle days16:50
hogepodge#action eglute to send out calendar invitation for midcycle16:50
RockygI hope you have some good bourbon...16:51
eglutenot officially :D16:51
*** yamahata has joined #openstack-meeting-316:51
VanLRockyg: LOL. Not *those* kind of drinks.16:51
hogepodge#topic Waiver for additional responses on Nova API calls16:51
*** openstack changes topic to "Waiver for additional responses on Nova API calls (Meeting topic: defcore)"16:51
hogepodge#link https://review.openstack.org/#/c/333067/16:51
*** mickeys has joined #openstack-meeting-316:52
VanLMy only issue is that I want strict API checking to go through the normal defcore process16:52
*** padkrish has joined #openstack-meeting-316:52
VanLIt doesn't just get "turned on" at some point - changes in the API that are required for TM compliance must be scored, weighed, etc.16:53
hogepodgeI'm not sure what more I can say this week. Administratively I'd like to see the Foundation have a way to work this out, so just a reminder that it's there.16:53
egluteVanL can you create a launchpad issue for strict API checking?16:54
hogepodgeIt's related to this, which gives a formal path for additional properties https://review.openstack.org/#/c/335247/16:54
egluteI would like to move forward with this waiver16:55
hogepodgeeglute: VanL: I can create that too if you'd like16:55
eglutehogepodge that would be great16:55
VanL+1 hogepodge16:55
eglutemarkvoelker are you ok with the waiver?16:55
hogepodgeeglute: don't want to speak for markvoelker, but I think he's waiting on WG and board consensus? I don't want to +2 my own proposal.16:56
*** mriedem has joined #openstack-meeting-316:56
hogepodgeso to that end reviews are helpful16:56
eglutei think the board agreed that we need a waiver16:56
eglutei am ok with going forward with this. we can amend the waiver later as things come up16:57
markvoelkerGenerally yes, I'm ok with it.  From the BoD meeting I got the general impression they were ok with the idea too16:57
*** Swami has joined #openstack-meeting-316:57
hogepodgewith two minutes left, I'm going to post the last few agenda items16:57
hogepodge#topic wrap up16:57
*** openstack changes topic to "wrap up (Meeting topic: defcore)"16:57
hogepodge#link Test Spec https://review.openstack.org/#/c/317531/16:58
hogepodgeI'm sure this will get lots of attention at the sprint16:58
hogepodge#link blueprint for test result ownership https://blueprints.launchpad.net/refstack/+spec/test-results-ownership16:58
*** dasanind has joined #openstack-meeting-316:58
hogepodge#link blueprint for marking results as used in certification https://blueprints.launchpad.net/refstack/+spec/certification-test-record16:58
eglutethanks gema and catherineD|2 for working on them16:58
catherineD|2Please help to review the RefStack blueprint and spec16:59
hogepodge#link review for associating test results to products https://review.openstack.org/#/c/332260/16:59
catherineD|2I hope to have these land and review in the midcycle ..16:59
hogepodgeRefStack is an important companion project to defcore, reviews and comments are greatly valued.16:59
gemawill do16:59
hogepodgeThanks everyone!16:59
gemathank you guys!16:59
catherineD|2Thank you!17:00
hogepodge#endmeeting17:00
*** openstack changes topic to " (Meeting topic: ops_guide)"17:00
openstackMeeting ended Wed Jul  6 17:00:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-06-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-06-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-07-06-16.01.log.html17:00
*** doffm_ has joined #openstack-meeting-317:00
alaski#startmeeting nova_cells17:00
*** markvoelker has quit IRC17:00
openstackMeeting started Wed Jul  6 17:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** cjvolzka has left #openstack-meeting-317:00
alaskianyone awake?17:00
doffm_o\17:00
*** gema has left #openstack-meeting-317:00
mriedemo/17:00
*** doffm_ is now known as doffm17:00
alaskishould be a quick meeting today17:01
melwitto/17:01
*** piet has joined #openstack-meeting-317:01
alaski#topic Testing17:01
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"17:01
alaskiauggy doesn't appear to be here, but she updated me last week17:01
woodster_o/17:01
*** catherineD|2 has left #openstack-meeting-317:01
alaskishe was inches away from having a working testing job with a multi-node setup, but not cells specific yet17:01
*** Sukhdev has quit IRC17:01
mriedemhuh?17:01
alaskiher next step was to incorporate the simple cells setup command and see what happens17:02
mriedemwe already have a non-cells multinode job17:02
alaskishe was mostly copying that as I understand it17:02
dansmitho/17:02
alaskiI don't know what issues she was hitting, but she said -infra was being helpful in getting it working17:03
mriedemseem like you could just run the script from devstack17:03
mriedemin a test patch17:03
mriedemanywho17:03
alaskiright, I have a patch up for that17:03
alaskibut we want on ongoing job17:03
mriedemso she's doing the project-config stuff17:04
alaskiyeah17:04
mriedemok17:05
alaskihopefully she can fill us in next week, or at the midcycle17:05
*** neiljerram has quit IRC17:05
mriedemi usually find it easier to get it working in devstack-gate as a POC17:05
*** dasanind has quit IRC17:05
mriedemthen create the job in project-config17:05
mriedemsince devstack-gate has a multinode flag i think17:05
mriedemso if multinode, tell devstack to do cells setup17:06
mriedemalthough won't we do the cells setup by default for a cell of one?17:06
alaskiyes17:06
mriedemi guess we have to pick the api and cells 0 cells17:06
mriedembut yeah17:06
alaskiI'll point her at these logs, and try to find her patch at some point17:06
*** neiljerram has joined #openstack-meeting-317:06
alaski#topic Reviews17:07
*** openstack changes topic to "Reviews (Meeting topic: nova_cells)"17:07
alaskihttps://etherpad.openstack.org/p/newton-nova-priorities-tracking17:07
alaskiwith FF over there will hopefully be more eyeballs for this stuff17:07
doffmI guess https://review.openstack.org/#/c/274885/ is stuckish.17:07
doffmI modified a while ago to fanout over all cells for the sync.17:07
doffmBut that seems to be unpopular.17:08
dansmithI need to circle back on that, I just wasn't getting it17:08
doffmOk, will put the options in a comment on the review.17:08
alaskiI17:09
dansmithI should probably remove my -117:09
alaskiI'm not reading the comments as against fanout17:09
doffmJust a change in the option name?17:09
dansmithno, I'm just trying to figure it out17:09
alaskimostly seemed to be about which behavior is the default, and name changing17:09
dansmithbut I don't remember what all I wasconfused about17:09
doffmOk.17:09
alaskidansmith: the basic idea is just fanout. it just happens that all we can fan out to right now is cell017:10
dansmithlet me just revisit and then ping you all to unconfuse me once I become reconfused17:10
alaskisounds good17:10
dansmithalso, what's the status on getting that 25th hour added to the day?17:10
doffmI'll try and make the 'fanout' implications more clear in the code.17:11
alaskiI think mriedem has figured it out and is keeping the secret to himself17:11
dansmithheh17:11
doffmI hope the 25th hour task is progressing.17:11
dansmithI expect mriedem's secret is "be divorced soon"17:11
doffmLOL. Blunt.17:11
alaskiheh, that would be one way to do it17:11
dansmithor "regret missing my child's childhood ... later"17:11
alaskiso mostly I just wanted to remind everyon that reviews on cells stuff should pick up with FF over17:12
*** ajmiller has joined #openstack-meeting-317:12
mriedemlaura works nights17:12
mriedemremember17:12
mriedemmarry a nurse17:12
mriedemis the secret17:12
dansmithah17:13
* dansmith is much less impressed now17:13
alaskiwell there you go17:13
*** ddieterly is now known as ddieterly[away]17:13
alaskiwrite a book on that and become rich17:13
alaski#topic Open discussion17:13
*** openstack changes topic to "Open discussion (Meeting topic: nova_cells)"17:13
alaskiI will be in Cali next week so I don't know if I can run the meeting17:14
alaskiwe can decide to skip now, or make a last minute call17:14
mriedemgoing going back back to cali?17:14
alaskior someone else can chair17:14
dansmithalaski: not sure you can pull off calling it "Cali"17:14
alaskidansmith: yep, had to give it a shot though17:15
mriedemalaski is the most thuggish guy i know17:15
dansmithheh17:15
mriedembroken arm from arm wrestling17:15
dansmithlol17:15
dansmithtrue I guess17:15
alaskihah17:15
dansmithwhat a badass17:15
dansmithhe also has that hat17:15
dansmithwhich if worn tilted to the side could be pretty thug-like17:15
mriedemi expect most of my review time through the next week to be on FFE stuff17:15
mriedemwe should probably checkpoint before the midcycle though17:16
alaskidansmith: doing that just exposes how not thuggish I am17:16
dansmithheh17:16
alaskiI don't know what's planned for next week, but I'll do my best to be around for the meeting17:16
mriedemok we can cancel if there isn't anything going on17:17
alaskithat's all I have for today17:17
alaskianyone else?17:17
dansmithnot me17:17
*** ddieterly[away] is now known as ddieterly17:17
alaskimriedem: I'll do a check on Tuesday and make a decision17:18
mriedemsounds good17:18
*** mickeys has quit IRC17:18
alaskithanks all!17:18
alaski#endmeeting17:18
*** openstack changes topic to " (Meeting topic: ops_guide)"17:18
openstackMeeting ended Wed Jul  6 17:18:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:18
*** mriedem has left #openstack-meeting-317:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-07-06-17.00.html17:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-07-06-17.00.txt17:18
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-07-06-17.00.log.html17:18
*** sarob has joined #openstack-meeting-317:19
*** kzaitsev_mb has quit IRC17:22
*** uxdanielle has quit IRC17:22
*** mickeys has joined #openstack-meeting-317:23
*** VW has quit IRC17:29
*** lpetrut has quit IRC17:32
*** Rockyg has quit IRC17:36
*** dasanind has joined #openstack-meeting-317:37
*** dasanind has quit IRC17:40
*** ivar-lazzaro has joined #openstack-meeting-317:44
*** TravT has joined #openstack-meeting-317:45
*** TravT has left #openstack-meeting-317:45
*** cbouch has quit IRC17:45
*** sarob has quit IRC17:46
*** ddieterly is now known as ddieterly[away]17:49
*** sarob has joined #openstack-meeting-317:50
*** rossella_s has quit IRC17:54
*** sdake has quit IRC17:55
*** dasanind has joined #openstack-meeting-317:56
*** sdake has joined #openstack-meeting-317:56
*** ivar-laz_ has joined #openstack-meeting-317:57
*** pvaneck has joined #openstack-meeting-317:59
*** VW has joined #openstack-meeting-318:00
*** ivar-lazzaro has quit IRC18:00
*** VW has quit IRC18:02
*** sdake has quit IRC18:02
*** paul-carlton2 has quit IRC18:05
*** VW has joined #openstack-meeting-318:05
*** sdake has joined #openstack-meeting-318:08
*** sdake has quit IRC18:08
*** sdake has joined #openstack-meeting-318:08
*** geo__ has left #openstack-meeting-318:09
*** salv-orlando has quit IRC18:12
*** pgadiya has joined #openstack-meeting-318:19
*** pgadiya has quit IRC18:19
*** _sarob has joined #openstack-meeting-318:20
*** padkrish has quit IRC18:22
*** sarob has quit IRC18:23
*** chandanc_ has quit IRC18:25
*** jed56 has quit IRC18:25
*** piet has quit IRC18:26
*** padkrish has joined #openstack-meeting-318:27
*** ddieterly[away] is now known as ddieterly18:34
*** ociuhandu has quit IRC18:34
*** ivar-laz_ has quit IRC18:37
*** ivar-lazzaro has joined #openstack-meeting-318:37
*** dasanind has quit IRC18:42
*** dasanind has joined #openstack-meeting-318:45
*** banix has quit IRC18:45
*** padkrish has quit IRC18:48
*** revon has joined #openstack-meeting-318:50
*** vhoward has joined #openstack-meeting-318:52
*** piet has joined #openstack-meeting-318:53
*** ddieterly is now known as ddieterly[away]18:57
*** rhochmuth has quit IRC18:57
*** Sukhdev has joined #openstack-meeting-318:59
*** DevonBoatwright has joined #openstack-meeting-318:59
*** DevonBoatwright has left #openstack-meeting-318:59
*** asettle has joined #openstack-meeting-319:00
*** ddieterly[away] is now known as ddieterly19:02
*** VW has quit IRC19:05
*** VW has joined #openstack-meeting-319:05
*** MeganR has joined #openstack-meeting-319:06
*** padkrish has joined #openstack-meeting-319:07
*** ociuhandu has joined #openstack-meeting-319:09
*** MeganR has quit IRC19:09
*** MeganR has joined #openstack-meeting-319:09
*** MeganR has quit IRC19:10
*** rockyg has joined #openstack-meeting-319:10
*** dtardivel has quit IRC19:17
*** uxdanielle has joined #openstack-meeting-319:18
*** lpetrut has joined #openstack-meeting-319:19
*** asettle has quit IRC19:20
*** vishwanathj has quit IRC19:21
*** vishwanathj has joined #openstack-meeting-319:22
*** asettle has joined #openstack-meeting-319:29
*** ying_zuo has joined #openstack-meeting-319:31
*** padkrish has quit IRC19:32
*** asettle has quit IRC19:36
*** iyamahat has quit IRC19:39
*** lpetrut has quit IRC19:41
*** iyamahat has joined #openstack-meeting-319:43
*** padkrish has joined #openstack-meeting-319:44
*** ddieterly is now known as ddieterly[away]19:44
*** rdopiera has joined #openstack-meeting-319:53
*** flwang1 has quit IRC19:55
*** lpetrut has joined #openstack-meeting-319:55
*** ivar-lazzaro has quit IRC19:56
*** galstrom_zzz is now known as galstrom19:58
*** tsufiev has joined #openstack-meeting-319:58
*** alex_xu has joined #openstack-meeting-319:58
*** asettle has joined #openstack-meeting-319:59
*** robcresswell has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Jul  6 20:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
bpokornyo/20:00
robcresswellHello! Anyone around for Horizon meeting?20:00
asettleo/20:00
*** piet has quit IRC20:01
*** ankur-gupta-f has joined #openstack-meeting-320:01
robcresswellQuiet day!20:01
tsufievha, where is everybody?20:01
*** julim has quit IRC20:01
*** hurgleburgler has joined #openstack-meeting-320:01
ankur-gupta-f\o/20:01
robcresswellA lot of people take this week off in 'murica20:01
robcresswellCelebrate american-brexit20:02
bpokornyHaha20:02
asettleI love that that is now a term20:02
hurgleburglerha20:02
ankur-gupta-fIn Texas we are looking forward to Texit20:02
robcresswelllol20:02
hurgleburglerbeing a native New Mexican, we also look forward to Texit20:03
robcresswellSorry, slow typing over dinner today20:03
robcresswell#topic Agenda20:03
*** openstack changes topic to "Agenda (Meeting topic: horizon)"20:03
robcresswell#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-07-06_2000_UTC20:03
robcresswellThere's a few things on here, so lets get started20:03
robcresswell#topic Glance V2 Update20:04
*** ducttape_ has joined #openstack-meeting-320:04
*** openstack changes topic to "Glance V2 Update (Meeting topic: horizon)"20:04
robcresswellbpokorny: o/20:04
robcresswellCare to elaborate?20:04
bpokornyWe've run into an issue with the Glance v2 patch..20:04
*** dasanind has quit IRC20:04
*** julim has joined #openstack-meeting-320:05
tsufievglance folks don't want to set show_multiple_locations = true, because it would break rackspace public cloud20:05
*** TravT has joined #openstack-meeting-320:05
bpokornyWithout getting into too many specifics, specifying a location for a glance image has been removed.20:05
*** dasanind has joined #openstack-meeting-320:05
tsufievwhich tells me enough about so called 'openstack diversity' :D20:05
bpokorny:)20:05
*** piet has joined #openstack-meeting-320:05
bpokornyI went to the glance meeting last week to ask about it.20:05
bpokornyThey said nova is running into the same issue when using v2.20:06
pieto/20:06
tsufievbpokorny, so what we need here is glexit :)20:06
bpokornySo they're aware of the problem, and Brian R and mfedosin are going to discuss on the ML.20:07
robcresswellWhats the reason it breaks rackspace?20:07
*** TravT_ has joined #openstack-meeting-320:07
bpokornytsufiev :)20:07
bpokornyI haven't heard of the rackspace issue before.20:07
tsufievrobcresswell, that's waht mfedosin told me about that security issue with show_multiple_locations20:08
bpokornyWhat I've heard is that there are security concerns with it.  ^20:08
*** ddieterly[away] is now known as ddieterly20:08
robcresswellI assume the concern is letting a user specify an arbritrary place to download something from (and boot it)20:09
robcresswell?20:09
*** ezpz has joined #openstack-meeting-320:09
bpokornyYeah, I think that's correct.20:09
tsufievafair, yes20:09
*** padkrish has quit IRC20:09
TravT_well, if glance won't support it, then neither can we. maybe it isn't a problem we should concern ourselves with and just move to the direct upload via CORS (timur's patch)20:09
robcresswellRight... I'd rather we just dont worry about it, and when ops complain, I'll happily refer them to glance to shout at instead...20:10
robcresswellIsn't this similar/ the same as the issue we discussed before?20:10
bpokornyGlance currently allows it for v1, which we do in Horizon.20:10
tsufievTravT, have you seen dstanek reply on the ML about CORS & security implications?20:10
TravT_well Glance is also deprecating v120:10
TravT_tsufiev i read it the other day20:11
tsufievin 2 words, he thinks we're fine to go on with keystone tokens in js20:11
tsufievokay20:11
TravT_was there another response?20:11
tsufievnope20:11
bpokornyIf Horizon doesn't support it for v2, should we remove it for v1 also?20:11
robcresswellIsnt V1 supposed to be gone this cycle?20:11
bpokornyOr put logic in to not allow it just if v2 is being used?20:11
TravT_my vote is to move forward with the new angular cors upload.20:11
*** sdake has quit IRC20:12
tsufievTravT_, I think we can support both CORS and the legacy upload for Angular20:12
robcresswellbpokorny: I would say the latter. If the API won't support something, Horizon shouldn't go miles out of its way to maintain logic to work around it20:12
robcresswellSo just disable it in V220:12
TravT_+120:12
bpokornyrobcresswell: TravT_: Sounds good to me.20:12
TravT_if there is big enough demand, then people can lobby to get it into glance as robcresswell said20:12
tsufievor switch to glance v3, hehe20:13
*** pvaneck has quit IRC20:13
robcresswellyup, absolutely agree TravT_20:13
*** pvaneck has joined #openstack-meeting-320:13
robcresswelltsufiev: What was said about CORS?20:14
robcresswellI have a feeling I read this, about security issues preventing it, but wanted to be sure20:14
tsufievrobcresswell, david stanek said there is no catastrophe with passing ks tokens to js20:14
TravT_tsufiev: i spend about 3 hours doing follow up reading about it online after that thread.20:15
tsufievon the other hand, he also said that he would be happy to see some security folks feedback20:15
*** bryan_att has joined #openstack-meeting-320:15
TravT_tried to see if i could break the django csrf token (it already goes to client side), but ran out of time.20:15
tsufievTravT_, maybe you just didn't try hard enough ;)20:15
TravT_that's pretty much a given.20:16
TravT_:)20:16
robcresswellAh, so thats a green light to go ahead for the most part then20:16
tsufievyay!20:16
tsufievTravT_, please see my latest comment in Angular Create Image patch20:17
TravT_ok20:17
tsufievor we can discuss it here briefly20:17
TravT_lemme read real quick20:17
tsufievk20:17
TravT_for others: https://review.openstack.org/#/c/317456/20:17
robcresswell#info Decided not to work around missing Glance support for show_multiple_locations = true and thus image location20:17
*** kzaitsev_mb has joined #openstack-meeting-320:17
robcresswellNot sure if thats entirely accurate, just wanted it logged with keywords.20:18
TravT_feel like we could #success - an actual decision was made20:18
TravT_:D20:18
robcresswellSo that when someone tantrums I can find the meeting :)20:18
*** sdake has joined #openstack-meeting-320:19
robcresswellReady to move on?20:19
* TravT_ still reading tufiev's comments on patch20:19
robcresswellAh wait, I missed that while I was typing the info.20:20
robcresswelltsufiev: Might create some confusion, repurposing a setting no?20:21
TravT_tsufiev, that is interesting... but it is a setting the could slip through the covers.20:21
tsufievrobcresswell, yes, that may be a concern...20:21
*** galstrom is now known as galstrom_zzz20:21
tsufievI'm trying to do as the common sense suggests here20:22
robcresswellMay be safer to deprecate the old one and just use something like IMAGE_UPLOAD = 'CORS' || 'LEGACY' || False20:22
tsufievI like it, robcresswell!20:22
TravT_yeah, i was thinking the same thing.20:23
tsufievbut how it the new setting should behave if HORIZON_IMAGES_ALLOW_UPLOAD = False?20:23
robcresswellThat way the old one can just throw a warning referring to the new one. Makes it a little bloated for a cycle perhaps, but easier for operators to manage20:23
tsufievshould the upload be forbidden completely in that case20:23
tsufievthat definitely needs some thinking20:23
*** ivar-lazzaro has joined #openstack-meeting-320:24
robcresswellYes20:24
tsufievanyways feel free to leave your opinions in the above patch, I'm sure that we'll figure out something reasonable20:24
*** Marcellin_ has joined #openstack-meeting-320:24
robcresswellThats the current expected behaviour. I would think most people won't pay too close attention to the Python to JS shift, so if Image Upload suddenly appears (in JS) they would be surprised20:25
TravT_would it need to actually be a list of supported upload types?20:25
robcresswellso I would stick with False just hiding it20:25
robcresswellIs there really a case where you have CORS available and configured and dont want to use it/20:25
robcresswell?*20:25
robcresswellI wouldnt imagine so.20:25
TravT_no, i'm just thinking that if glance comes up with some new way20:25
TravT_we don't have to invent another settings alltogether to also support it20:26
tsufievI can hardly imagine it as well, but we don't have a way to query if CORS is enabled in Glance, robcresswell20:26
robcresswelltsufiev: No, but the operator setting that variable in Horizon would :)20:26
*** galstrom_zzz is now known as galstrom20:27
robcresswellI meant if you supplied a list and let the user choose, that seems unneccessary20:27
robcresswellI guess it may be an issue if they decide to add other options that might coexist20:27
tsufievyes, no need to expose the choice to user, it should be a deployer's decision20:28
robcresswellYeah20:28
TravT_tsufiev, do we really need both the django and ng patches?20:28
robcresswellI think a variable that takes a string should be fine; if falsy, we just disable. Deprecate the previous setting at the same time, but maintain its behaviour for a cycle.20:28
tsufievI'd prefer to hear what others think, TravT_20:28
tsufievbut I would like to have Django version as well, because it's easier to backport20:29
TravT_okay, i see20:29
robcresswellIf the patch is ready, I think we should accept it, and stop accepting patch on in during O20:29
TravT_was just wondering if the ng could be used on django panel for now20:29
robcresswellon it*20:29
TravT_ng create20:29
tsufievI recall mrunge was interested some time ago in Django version of that patch20:29
mrungehuh?20:30
TravT_uh-oh, now you woke the poor guy up20:30
mrunge:P20:30
tsufievmrunge, the context is: Create Image CORS file upload20:30
tsufievdo you need it ;)?20:30
mrungedoesn't ring any bell20:30
tsufievlol )20:30
mrungebut yes, great!20:31
mrungego for it20:31
robcresswellTravT_: Any other concerns, or does the current path sound reasonable? As resident Glance-expert.20:31
tsufievI realized one thing recently: if something doesn't work for a substantial time, people just forget about it20:31
robcresswellSwift20:31
robcresswellfor example20:31
tsufievmust have some explanation in psycology, I suppose )20:31
robcresswell(The panel, not the project)20:31
TravT_robcresswell, the glance team has been trying hard to deprecate v1 for a long time.20:32
TravT_i think we support v1 with the legacy code20:32
TravT_but for new code and v2 / we don't need to be the banner carriers demanding the same features20:32
robcresswellIt sounds like we should've shifted to v2 last cycle ideally20:33
TravT_i'd like to see us start reducing code paths20:33
TravT_there wasn't a big push to go to v220:33
TravT_because nova hadn't stopped using it20:33
robcresswellDoes NG Images support both? Or just V2?20:33
*** ddieterly is now known as ddieterly[away]20:33
TravT_ng images goes through all the same API layers20:33
TravT_there is some property translation here and there20:33
TravT_it will need to be looked over20:33
tsufievrobcresswell, the funny thing is that right now Horizon uses both v1 and v2 :)20:34
TravT_yes, that is true20:34
*** hurgleburgler has left #openstack-meeting-320:34
robcresswellEither way, we need to finalise V2 support without a bunch of hacks to workaround missing APIs.20:34
tsufievour goal with that v2 patch is to stop relying on v1 being accessible20:35
TravT_maybe all the angular work should be moved to v2 only and the code paths it uses should be v2.20:35
robcresswellTravT_: That's what I was wondering20:35
*** anilvenkata has quit IRC20:35
tsufievTravT_, I thought that it was meant to be done transparently20:35
robcresswellI know people have mentioned having v1 endpoints just so Horizon doesnt fall over.20:35
tsufievI mean, the choice between v1/v2 happening on API layer even before REST API layer20:35
TravT_so, the angular work as all generally tried to rely on the api layers in python20:36
*** ediardo has joined #openstack-meeting-320:36
*** ddieterly[away] is now known as ddieterly20:36
tsufievso Angular code wouldn't even know which Glance version it's dealing with20:36
TravT_it was supposedly one of the advantages to using horizon instead of moving to richard's angboard20:36
TravT_tsufiev: problem is that this isn't always entirely true.20:36
TravT_will need to go back through it.20:37
TravT_in the rest layers, there is some conversion that happens20:37
TravT_because in v1 glance20:37
TravT_all fields just go straight on the base object20:37
*** piet has quit IRC20:37
TravT_^ nix that last statement20:37
TravT_in *v2* glance20:38
*** piet has joined #openstack-meeting-320:38
TravT_in v1 , they separated out "core image properties" from custom properties20:38
tsufievyep, complete isolation is difficult :/20:38
*** _sarob is now known as sarob20:39
TravT_https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/rest/glance.py#L28620:39
TravT_anyway, we've tried to deal with in on angular side20:39
TravT_but we will need to actually test it out20:39
TravT_i think there might be a problem area or two20:40
*** ivar-lazzaro has quit IRC20:41
tsufievokay, so I'll update both Django and NG Create Image patches to use a saner new setting and deprecate the old setting20:41
TravT_sounds good20:41
robcresswellIndeed. We're aiming to swap to angular with Images this cycle, but will have to carry the python for another cycle or two, depending on how long we wish to carry deprecated panels20:42
*** dasanind has quit IRC20:43
robcresswellAnyway, lets move on :)20:43
robcresswell#topic UI Guidelines Spec20:43
*** openstack changes topic to "UI Guidelines Spec (Meeting topic: horizon)"20:43
asettleo/20:43
robcresswell#link https://review.openstack.org/#/c/337202/20:44
pieto/20:44
robcresswellasettle: Want to talk about it?20:44
asettleCheers robcresswell20:44
asettleHey guys, pretty much the subject says it all. Rob mentioned last meeting that we required some volunteers to help out creating this.20:45
asettleI have a spec up in the docs-specs repo that should give a fairly basic overview of what we're planning.20:45
asettleThere's always room for improvement and always keen for people to step forward with new (better) ideas.20:45
*** dasanind has joined #openstack-meeting-320:45
asettlePlease take the time to take a look, especially considering horizon is the official dashboard20:46
asettleWe'll be working on it to hopefully get something out half decent by Newton, so if you don't speak now, forever hold your peace :P20:46
asettleAny questions, feel free to direct them my way, to Piet or even to robcresswell20:46
robcresswellWe've been reaching out to PTLs of projects with horizon plugins too20:46
asettleWe've had a few responses, and reviews. Which is great :) we're aiming to have inclusion from every project that has a GUI20:47
asettleOr at least, we're opening up the opportunity to everyone for input20:47
pietWe also need to reach outside of Horizon20:47
* tsufiev still trying to get some feedback about standard NG wizard workflow in Horizon and murano-dashboard :)20:47
robcresswellBasically, I want people from Horizon to remain involved, even if its just a 2 minute glance at it every now and then. No desire for other projects to dictate to us how to write a UI, so we have plenty of opportunity to get involved here.20:47
asettlePiet - the list of PTL's I emailed included Ironic etc. It was fairly extensive.20:47
ankur-gupta-fThere were long discussions about it. What is the summary of the effort? Intent?20:47
pietasettle Kk20:48
robcresswellankur-gupta-f: All in the spec :)20:48
asettle^^ as above20:48
piettsufiev How different is Murano that the rest of HOrizon?20:48
asettleBut as a TL;DR - create patterns and library, intent? to create consistency between projects20:48
robcresswellBut basically; make guidelines to help people write a consistent UI.20:48
asettleWhich is something piet is really striving for which is excellent :)20:48
ankur-gupta-fThanks :)20:48
tsufievit's about those mockups, piet - mostly about first uploading some stuff to the server, then continuing to fill the forms20:49
asettleNo worries :)20:49
robcresswellReduces load on reviewers and IRC. Helps plugin ecosystem. End product is a consistent UI. Everyone wins.20:49
TravT_The subjects suggested in the spec make sense to me.20:49
*** dasanind has quit IRC20:49
asettle*thumbs up*20:49
robcresswellThanks TravT_20:49
asettleTravT_: great :) cheers. Appreciate it20:49
asettleThat's pretty much all from me. Anything I missed piet?20:49
*** mtanin___ has joined #openstack-meeting-320:50
pietAnd operators have been complaining about inconsistency across projects20:50
pietNewp20:50
pietJust get in there and review.20:50
asettleYeah good point.20:50
*** david-lyle has joined #openstack-meeting-320:50
TravT_so, would we be targeting removing anything from horizon docs?20:50
robcresswellPotentially, if it clashes.20:51
robcresswellWe'd definitely need to reference this doc in the contributing guides20:51
asettleTravT_: not just yet. I think that's something we should focus on afterwards. At the moment we're working on identify patterns, figuring out where the gaps are, and tehn coming up with a collaborative piece you can all use.20:51
*** mtanino has quit IRC20:51
*** padkrish has joined #openstack-meeting-320:51
robcresswellSounds good20:51
pietIt would be good to get feedback on the focus of the doc.  Is it a patterns library?  High level principles?20:52
asettle+120:52
TravT_yeah, are these like mockups?20:52
TravT_and will they point to reference implementation?20:52
*** wangbo has quit IRC20:53
robcresswellMore like an extension of http://docs.openstack.org/contributor-guide/ui-text-guidelines.html in my mind20:53
*** sdake has quit IRC20:53
*** wangbo has joined #openstack-meeting-320:53
asettleThat's how I understand it too, piet ?20:53
*** lblanchard has quit IRC20:53
*** dasanind has joined #openstack-meeting-320:53
robcresswellSo, things like, use an "Info" alert if we don't know the final outcome of an action, a "Success" alert if we do, etc.20:53
pietasettle which part?20:53
pietExtension of the UI Text20:53
pietWith personas thrown in there20:54
asettleYes20:54
*** mtanin___ has quit IRC20:54
robcresswellJust general rules that people may not realise, or have thought about, or reviewers might miss, but overall detract from it being a professional product.20:54
asettleA point of reference, if you will.20:54
pietIn some ways, stuff that devs don't really want to think about...like the location of a cancel button20:54
*** banix has joined #openstack-meeting-320:55
*** padkrish has quit IRC20:55
*** galstrom is now known as galstrom_zzz20:55
pietThe some higher level principles like "Design to scale"20:55
* kzaitsev_mb lurking in case I can answer anything murano-dashboard %)20:55
pietOr "minimum number of steps in workflows"20:55
tsufievspeaking of scale...20:55
asettlekzaitsev_mb: if you wanna check out the spec too, feel free to go ahead :) all reviews are appreciated20:55
*** padkrish has joined #openstack-meeting-320:56
robcresswellLets move on, because I need to mention the last item20:56
pietkzaitsev_mb How much does Murano UI deviate from vanilla horizon20:56
robcresswellBut please read the spec, leave brief comments etc.20:56
asettleThanks robcresswell :) appreciate the plug20:56
robcresswell#topic Cancellation of 800UTC meeting20:56
*** openstack changes topic to "Cancellation of 800UTC meeting (Meeting topic: horizon)"20:56
*** alaski has left #openstack-meeting-320:56
pietThanks robcresswell20:56
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-July/098854.html20:56
robcresswellSo I sent out an email and mentioned it in meetings, and nobody seems to have replied. The patch merged earlier, so the 800UTC meeting is officially no more.20:57
tsufiev\o/20:57
kzaitsev_mbpiet: not much, it's basically a horizon dashboard, that reuses most of the concepts. It's mostly pythonic now, but we're looking into rethinking it as a js/angular based thingy20:57
tsufievmore things to do in the morning20:57
robcresswellIf we have more demand for it, I'm more than happy to hold the meeting, but no desire to waste peoples time by dragging them into an empty meeting room each week.20:58
robcresswellJust want to be clear that its not intended to be exclusive or anything :)20:58
TravT_robcresswell as a non-attendee of the now cancelled meeting, i offer no dissent.20:58
robcresswellTravT_: haha20:58
tsufievsince we've exhausted the agenda, I'd like to advertise an RFE bug in Neutron: https://bugs.launchpad.net/neutron/+bug/159948820:58
openstackLaunchpad bug 1599488 in neutron "[RFE] Enhance Quota API calls to return resource usage per tenant" [Wishlist,New] - Assigned to Sergey Belous (sbelous)20:58
pietkzaitsev_mb Best answer is "wouldn't know because there's no UI spec to follow!!" ;^)20:58
robcresswell#info 800UTC meeting cancelled20:58
robcresswell#topic Open Discussion for 60 seconds20:59
*** openstack changes topic to "Open Discussion for 60 seconds (Meeting topic: horizon)"20:59
tsufievif you know some magic way to make Neutron folks implement it faster, please do it20:59
tsufievit should help us with Neutron quota usages20:59
tsufievbecause now they are terrible in Horiozn20:59
TravT_robcresswell: is next weeks IRC cancelled due to mid-cycle?20:59
* rdopiera looks for his cattle prod20:59
robcresswellTravT_: Thanks for hte reminder!21:00
robcresswellYes, next weeks meeting will be cancelled due to midcycle. I'll send a reminder on the mailer.21:00
robcresswellWe're at time.21:00
robcresswellThanks everyone!21:00
TravT_thanks21:00
ducttape_#brexit21:00
TravT_see some of you next week21:00
tsufievsee you on the midcycle!21:00
robcresswell#endmeeting21:00
bpokornyThanks!21:00
*** openstack changes topic to " (Meeting topic: ops_guide)"21:00
openstackMeeting ended Wed Jul  6 21:00:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-06-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-06-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-07-06-20.00.log.html21:00
*** ducttape_ has left #openstack-meeting-321:00
*** robcresswell has left #openstack-meeting-321:00
*** tsufiev has left #openstack-meeting-321:01
*** TravT has quit IRC21:01
*** TravT_ has left #openstack-meeting-321:01
*** rockyg has quit IRC21:01
*** rdopiera has left #openstack-meeting-321:01
*** ezpz has left #openstack-meeting-321:02
*** sdake has joined #openstack-meeting-321:03
*** dasanind has quit IRC21:03
*** ajmiller_ has joined #openstack-meeting-321:03
*** david-lyle has left #openstack-meeting-321:05
*** ajmiller has quit IRC21:07
*** julim has quit IRC21:07
*** raj_singh has joined #openstack-meeting-321:10
*** raj_singh has left #openstack-meeting-321:10
*** asettle has quit IRC21:13
*** vhoward has quit IRC21:14
*** dasanind has joined #openstack-meeting-321:19
*** flwang1 has joined #openstack-meeting-321:20
*** ivar-lazzaro has joined #openstack-meeting-321:21
*** cleong has quit IRC21:22
*** padkrish has quit IRC21:27
*** padkrish has joined #openstack-meeting-321:31
*** bpokorny has quit IRC21:32
*** neiljerram has quit IRC21:37
*** bpokorny has joined #openstack-meeting-321:38
*** dasanind has quit IRC21:40
*** ddieterly is now known as ddieterly[away]21:40
*** yamahata has quit IRC21:44
*** dasanind has joined #openstack-meeting-321:45
*** piet has quit IRC21:45
*** yamahata has joined #openstack-meeting-321:45
*** ajmiller_ has quit IRC21:46
*** banix has quit IRC21:46
*** ajmiller_ has joined #openstack-meeting-321:46
*** banix has joined #openstack-meeting-321:47
*** sigmavirus is now known as sigmavirus_away21:52
*** salv-orlando has joined #openstack-meeting-321:57
*** dasanind has quit IRC21:58
*** spzala has joined #openstack-meeting-322:00
*** ddieterly[away] is now known as ddieterly22:03
*** rhochmuth has joined #openstack-meeting-322:08
*** banix has quit IRC22:08
*** vishwanathj has quit IRC22:09
*** dasanind has joined #openstack-meeting-322:11
*** padkrish has quit IRC22:14
*** padkrish has joined #openstack-meeting-322:17
*** kzaitsev_mb has quit IRC22:19
*** kzaitsev_mb has joined #openstack-meeting-322:20
*** david-lyle_ has joined #openstack-meeting-322:21
*** lpetrut has quit IRC22:21
*** dkehn__ has joined #openstack-meeting-322:21
*** dkehn_ has quit IRC22:24
*** david-lyle__ has joined #openstack-meeting-322:26
*** bpokorny has quit IRC22:26
*** ivar-lazzaro has quit IRC22:26
*** kzaitsev_mb has quit IRC22:28
*** marst has quit IRC22:29
*** kzaitsev_mb has joined #openstack-meeting-322:30
*** david-lyle_ is now known as david-lyle22:35
*** bpokorny has joined #openstack-meeting-322:35
*** lblanchard has joined #openstack-meeting-322:35
*** padkrish has quit IRC22:36
*** david-lyle__ has quit IRC22:36
*** spzala has quit IRC22:38
*** spzala has joined #openstack-meeting-322:39
*** VW has quit IRC22:42
*** VW has joined #openstack-meeting-322:43
*** salv-orl_ has joined #openstack-meeting-322:43
*** dimtruck is now known as zz_dimtruck22:43
*** spzala has quit IRC22:45
*** salv-orlando has quit IRC22:46
*** uxdanielle has quit IRC22:48
*** padkrish has joined #openstack-meeting-322:48
*** rbak has quit IRC22:51
*** ddieterly is now known as ddieterly[away]22:52
*** ddieterly[away] is now known as ddieterly22:52
*** ddieterly has quit IRC22:52
*** Sukhdev has quit IRC22:53
*** padkrish has quit IRC22:53
*** padkrish has joined #openstack-meeting-322:54
*** uxdanielle has joined #openstack-meeting-322:57
*** mickeys has quit IRC22:57
*** uxdanielle has quit IRC22:58
*** padkrish has quit IRC23:03
*** ociuhandu has quit IRC23:03
*** spzala has joined #openstack-meeting-323:06
*** spzala has quit IRC23:10
*** padkrish has joined #openstack-meeting-323:11
*** rhochmuth has quit IRC23:14
*** padkrish has quit IRC23:19
*** yuikotakadamori has joined #openstack-meeting-323:21
*** VW has quit IRC23:32
*** yuikotakadamori has quit IRC23:33
*** dasanind has quit IRC23:33
*** pt_15 has quit IRC23:36
*** padkrish has joined #openstack-meeting-323:41
*** padkrish has quit IRC23:42
*** sdake has quit IRC23:43
*** padkrish has joined #openstack-meeting-323:46
*** padkrish has quit IRC23:50
*** padkrish has joined #openstack-meeting-323:53
*** padkrish has quit IRC23:58

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