Wednesday, 2017-01-11

*** rbak has quit IRC00:08
*** harlowja has quit IRC00:09
*** pasquier-s has quit IRC00:11
*** baoli has quit IRC00:12
*** macsz has quit IRC00:12
*** zerick has quit IRC00:12
*** markvoelker has quit IRC00:12
*** ttrifonov has quit IRC00:12
*** vdrok has quit IRC00:12
*** NikitaKonovalov has quit IRC00:12
*** rpodolyaka has quit IRC00:12
*** macsz has joined #openstack-meeting-300:12
*** HenryG has quit IRC00:12
*** med_ has quit IRC00:12
*** markvoelker has joined #openstack-meeting-300:12
*** stanzgy has quit IRC00:13
*** pkoniszewski has quit IRC00:13
*** zerick has joined #openstack-meeting-300:13
*** ildikov has quit IRC00:13
*** lcastell has quit IRC00:13
*** NikitaKonovalov has joined #openstack-meeting-300:14
*** VW_ has joined #openstack-meeting-300:14
*** jroll has quit IRC00:14
*** bobmel has joined #openstack-meeting-300:14
*** HenryG has joined #openstack-meeting-300:15
*** pkoniszewski has joined #openstack-meeting-300:16
*** kenji-i has quit IRC00:16
*** med_ has joined #openstack-meeting-300:16
*** lcastell has joined #openstack-meeting-300:17
*** VW has quit IRC00:17
*** med_ is now known as Guest4752000:17
*** ttrifonov has joined #openstack-meeting-300:18
*** VW_ has quit IRC00:18
*** Guest47520 is now known as medberry00:19
*** medberry has quit IRC00:19
*** medberry has joined #openstack-meeting-300:19
*** bobmel has quit IRC00:19
*** stevejims has quit IRC00:20
*** stanzgy has joined #openstack-meeting-300:20
*** rpodolyaka has joined #openstack-meeting-300:20
*** ildikov has joined #openstack-meeting-300:21
*** jroll has joined #openstack-meeting-300:21
*** pasquier-s has joined #openstack-meeting-300:22
*** stevejims has joined #openstack-meeting-300:22
*** vdrok has joined #openstack-meeting-300:22
*** pasquier-s has quit IRC00:25
*** pasquier-s has joined #openstack-meeting-300:25
*** vdrok has quit IRC00:25
*** vdrok has joined #openstack-meeting-300:25
*** harlowja has joined #openstack-meeting-300:25
*** chyka has quit IRC00:33
*** alezil is now known as aslezil00:34
*** sdake has quit IRC00:34
*** bobmel has joined #openstack-meeting-300:35
*** woodster_ has quit IRC00:35
*** bobmel has quit IRC00:40
*** wanghao has joined #openstack-meeting-300:43
*** revon has quit IRC00:53
*** tuanluong has joined #openstack-meeting-300:53
*** stanzgy has quit IRC00:54
*** bobmel has joined #openstack-meeting-300:56
*** VW has joined #openstack-meeting-300:58
*** bobmel has quit IRC01:00
*** VW has quit IRC01:03
*** mestery has left #openstack-meeting-301:17
*** bobmel has joined #openstack-meeting-301:17
*** bobmel has quit IRC01:21
*** huanxuan has joined #openstack-meeting-301:22
*** zz_dimtruck is now known as dimtruck01:22
*** aweeks has joined #openstack-meeting-301:32
*** xgerman has joined #openstack-meeting-301:32
*** dirk has joined #openstack-meeting-301:33
*** briancurtin has joined #openstack-meeting-301:35
*** stanzgy has joined #openstack-meeting-301:37
*** bobmel has joined #openstack-meeting-301:38
*** bobmel has quit IRC01:42
*** markvoelker has quit IRC01:43
*** markvoelker has joined #openstack-meeting-301:44
*** yamamoto_ has joined #openstack-meeting-301:47
*** pvaneck has quit IRC01:48
*** markvoelker has quit IRC01:49
*** bobmel has joined #openstack-meeting-301:59
*** bobmel has quit IRC02:03
*** s3wong has quit IRC02:08
*** dimtruck is now known as zz_dimtruck02:15
*** bobmel has joined #openstack-meeting-302:19
*** bobmel has quit IRC02:24
*** VW has joined #openstack-meeting-302:26
*** kzaitsev_mb has quit IRC02:29
*** VW has quit IRC02:30
*** VW has joined #openstack-meeting-302:31
*** spzala has quit IRC02:52
*** bobmel has joined #openstack-meeting-303:01
*** bobmel has quit IRC03:06
*** zz_dimtruck is now known as dimtruck03:11
*** iyamahat has quit IRC03:13
*** yamahata has quit IRC03:14
*** julim has quit IRC03:16
*** absubram has quit IRC03:18
*** gouthamr has quit IRC03:21
*** amotoki has quit IRC03:21
*** absubram has joined #openstack-meeting-303:25
*** amotoki has joined #openstack-meeting-303:29
*** absubram has quit IRC03:31
*** salv-orl_ has quit IRC03:32
*** salv-orlando has joined #openstack-meeting-303:32
*** amotoki has quit IRC03:33
*** markvoelker has joined #openstack-meeting-303:36
*** yamamoto_ has quit IRC03:43
*** bobmel has joined #openstack-meeting-303:43
*** kbyrne has quit IRC03:45
*** spzala has joined #openstack-meeting-303:47
*** bobmel has quit IRC03:47
*** kbyrne has joined #openstack-meeting-303:48
*** iyamahat has joined #openstack-meeting-303:52
*** sdake has joined #openstack-meeting-303:55
*** sdake has quit IRC04:00
*** iyamahat_ has joined #openstack-meeting-304:00
*** iyamahat has quit IRC04:01
*** sdake has joined #openstack-meeting-304:01
*** bobmel has joined #openstack-meeting-304:04
*** bobmel has quit IRC04:08
*** yamahata has joined #openstack-meeting-304:15
*** VW has quit IRC04:17
*** padkrish has joined #openstack-meeting-304:17
*** sdake has quit IRC04:18
*** padkrish has quit IRC04:18
*** padkrish has joined #openstack-meeting-304:18
*** spzala has quit IRC04:19
*** padkrish has quit IRC04:19
*** salv-orl_ has joined #openstack-meeting-304:23
*** bobmel has joined #openstack-meeting-304:25
*** salv-orlando has quit IRC04:26
*** bobmel has quit IRC04:29
*** iyamahat_ has quit IRC04:32
*** VW has joined #openstack-meeting-304:36
*** psachin has joined #openstack-meeting-304:40
*** bobmel has joined #openstack-meeting-304:46
*** yamamoto_ has joined #openstack-meeting-304:46
*** bobmel has quit IRC04:50
*** absubram has joined #openstack-meeting-304:55
*** absubram_ has joined #openstack-meeting-304:59
*** absubram has quit IRC04:59
*** absubram_ is now known as absubram04:59
*** bobmel has joined #openstack-meeting-305:07
*** sdake has joined #openstack-meeting-305:07
*** bobmel has quit IRC05:11
*** soichi has joined #openstack-meeting-305:27
*** bobmel has joined #openstack-meeting-305:28
*** kaz has joined #openstack-meeting-305:28
njohnstonHi, is this the time for the tap-as-a-service meeting?05:31
soichiyes05:31
kazhi05:31
soichi#startmeeting taas05:31
openstackMeeting started Wed Jan 11 05:31:46 2017 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:31
*** openstack changes topic to " (Meeting topic: taas)"05:31
openstackThe meeting name has been set to 'taas'05:31
soichi#link: https://wiki.openstack.org/wiki/Meetings/taas05:32
soichi#topic: Loop detection of tap flows (to prevent creating a loop)05:32
*** openstack changes topic to ": Loop detection of tap flows (to prevent creating a loop) (Meeting topic: taas)"05:32
*** bobmel has quit IRC05:32
soichii think this topic was homework for everyone :)05:33
*** VW has quit IRC05:33
*** vnyyad has joined #openstack-meeting-305:33
soichivnyyad: hi05:34
vnyyadhi05:34
vnyyadhappy new year to all!05:34
soichiHappy New Year!05:35
kazhi, happy new year05:35
soichiwe'd like to discuss "loop detection of tap flows (to prevent creating a loop)"05:35
soichiit is a cycle detection problem on a directed graph05:35
soichieach tap flow has only one destination (tap service)05:36
vnyyadsoichi: was(is) there a usecase for mirroring a tap service port?05:36
soichii'm not sure about actual use case05:36
vnyyadhmmm... because we can simple deny this in the first place to avoid cycles to keep it simple05:37
vnyyadbut yes if there is a use case we need the algo05:37
soichii agree with you05:38
soichithis topic was submitted by yamamoto san05:38
vnyyadok but lets discuss it anyways... he might have a use case05:39
soichisure05:39
soichieach tap flow has only one destination (tap service)05:39
soichiand loop can be created when a tap flow is created from a tap service to another tap service05:39
soichiso i guess we can use a graph G(V, E) where V=tap service, E=tap flow05:39
soichii think we can apply the cycle detection algo by using DFS (depth-first serach)05:40
vnyyadyes. And this has to be run before creation of each tap flow05:41
soichisure05:41
soichireference: https://www.youtube.com/watch?v=rKQaZuoUR4M05:42
vnyyadalso if i remember now there was a discussion we had on limiting the number of flows a tenant can create, just to make sure they are not creating a mess in the network intentionally or by mistake05:42
soichii think so.05:43
vnyyadso the number of Es in the graph will be limited and the the algo should not spend a lot a time finding the loop05:43
soichii agree05:43
soichikaz: do you have any comments?05:45
reediphi05:45
soichireedip: hi05:45
vnyyadhi05:45
soichireedip: happy new year05:45
kazsorry, no i don't.05:46
reediphappy new year soichi san :)05:46
kazreedip: hi05:46
reediphi kaz , vnyyad05:46
reedipsorry for being late05:46
soichireedip: we are discussing abot loop detection of tap flows05:46
soichido you have any idea?05:47
reedipyes, I am reading the logs for the same. No , I forgot it :P05:47
yamamoto_hi05:47
soichiyamamoto: hi05:47
reediphi yamamoto_ , do we have a use case for mirroring a tap port?05:47
*** bobmel has joined #openstack-meeting-305:49
yamamoto_actually i don't know.05:49
vnyyadany one else has a use-case for this?05:51
soichii don't have. So, guard creating a tap flow on tap service is simple, i think05:52
*** s3wong has joined #openstack-meeting-305:52
vnyyad+105:52
kaz+105:53
*** bobmel has quit IRC05:53
reedipsoichi : but when we mirror a port, do we know that the port is a normal port or a tap port ?? :)05:54
soichii think we can chaeck a tap service is already associated to the port05:55
vnyyadwe can always return an error when we detect it05:55
soichichaeck -> check05:55
reedipsoichi : No, my question is : You have a tap -service , and you created a tap flow on Port p105:56
reedipPort p1 is your source port05:56
reedipthe port created by tap-service is port p2 ( during creation of tap-service)05:56
reedipnow if a user tries to use port p2 as a source port for another tap-service, with destination port p305:57
reedipthen would that work ?05:57
soichiit is not work05:57
vnyyadredeep: it wont05:57
soichiwe wonder is there such a use case05:58
vnyyadblock all attempts to make a already existing tap-service port as a source for a tap flow05:58
soichivnyyad: +105:58
soichiexcuse me, but today i have to leave now. i'd like to pass the chair to kaz.06:00
soichi#chair kaz06:00
openstackCurrent chairs: kaz soichi06:00
soichisee you next week06:00
reedipso that means we need to add a check in out code as well06:00
*** soichi has left #openstack-meeting-306:01
*** ddyer has quit IRC06:01
reedipadios vnyyad06:01
vnyyadis the meeting over?06:02
kazno, still open,06:02
vnyyad:)06:02
vnyyadreedip: yes we need to add the check in the code06:02
*** nkrinner_afk is now known as nkrinner06:04
kazreedip?06:05
reediphi ...06:05
reedipsorry , was working on another item :D06:05
*** kaz has quit IRC06:05
*** kaz has joined #openstack-meeting-306:06
reedipvnyyad : okay, should we add a bug for this ? Also we need to open blueprints in Tap-as-a-Service in launchpad06:06
vnyyadreedip: for the blueprint i need to ask anil, as i am not able to do it for some reason06:07
reedipvnyyad : ohk06:07
njohnstonI have a very general TaaS question; let me know when a good time to ask it would be06:08
kaz#topic Open Discussion06:09
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:09
njohnstonHi!  So I am starting to try and use TaaS by trying it out in a devstack.  My problem is that after setting it up using the directions from INSTALL.rst I keep getting the error "ImportError: Plugin 'taas' not found."  This seems like an FAQ; any advice?  Is there a chat channel you all hang out in, talking about TaaS, where I could check in for questions like this?06:09
*** bobmel has joined #openstack-meeting-306:09
vnyyadnjohnston: is this error on the taas agent side (compute nodes) or on the taas plugin side?06:10
*** lpetrut has joined #openstack-meeting-306:10
yamamoto_there's no such a channel.06:11
yamamoto_there was a discussion about a channel but the consensus at that point was to use #openstack-neutron06:12
yamamoto_as there would be little traffic anyway06:12
njohnstonOK, I can definitely ask there06:12
*** dims has quit IRC06:13
yamamoto_at least i'm there when online.06:13
njohnstonThanks, all!06:13
*** bobmel has quit IRC06:14
yamamoto_wrt import error, i'm not sure.  have you followed devstack/README.rst?06:14
njohnstonyes06:14
njohnstonand this is on the taas plugin side, errors coming from neutron server06:14
yamamoto_can you show us your local.conf?06:15
njohnstonyamamoto_: http://paste.openstack.org/show/594499/06:17
yamamoto_i guess you should use stable/newton for taas as well?06:19
yamamoto_otherwise looks ok to me06:19
vnyyad+106:19
kaz+106:19
yamamoto_i'm not sure branch difference is a cause of the import error or not though.06:19
njohnstonthanks06:21
vnyyadyamamoto: a difference in branch can cause this error, happened to me a month ago06:21
vnyyadlooks like the branches needed to match (branch of devstack and taas)06:22
vnyyadbut for me master devstack with master taas worked out well06:22
kazdo you have any other topics?06:25
yamamoto_njohnston: feel free to ask us again if matchin branches doesn't improve the situation.06:25
yamamoto_i want to remind a few changes to review06:25
*** pcaruana has joined #openstack-meeting-306:25
yamamoto_#link https://review.openstack.org/#/c/256210/ spec06:26
yamamoto_#link https://review.openstack.org/#/c/396022/ horizon06:26
yamamoto_#link https://review.openstack.org/#/c/405261/ tox_install06:27
kazyamamoto_: thanks06:27
yamamoto_#link https://review.openstack.org/#/c/413360/ tox_install (alternative)06:27
yamamoto_tox_install thing might be less obvious06:27
yamamoto_it's necessary to use the correct version of deps on gate06:28
*** MarkBaker has joined #openstack-meeting-306:28
yamamoto_it needs to be backported to stable branch06:28
yamamoto_that's all from me06:28
kazthank you06:29
njohnstonthanks all!06:29
reedipAlso the OSC is up06:29
kazwe have no time left06:30
reediphttps://review.openstack.org/39876706:30
reedipkaz : yeah, this is just for you guys to review :D06:30
yamamoto_yea, use the dashboard link on the wiki for full list. :-)06:30
*** bobmel has joined #openstack-meeting-306:30
*** s3wong has quit IRC06:30
kazyes06:31
kazsee you next week.06:31
kaz#endmeeting06:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:31
openstackMeeting ended Wed Jan 11 06:31:37 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-11-05.31.html06:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-11-05.31.txt06:31
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-11-05.31.log.html06:31
kazbye06:31
reedipasta la vista (schwarzenneger voice ) :D06:32
yamamoto_bye06:32
vnyyadbye06:32
*** vnyyad has quit IRC06:32
*** kaz has quit IRC06:34
*** bobmel has quit IRC06:35
*** pgadiya has joined #openstack-meeting-306:37
*** lpetrut has quit IRC06:43
*** sdake has quit IRC06:45
*** stanzgy has quit IRC06:48
*** stanzgy has joined #openstack-meeting-306:48
*** bobmel has joined #openstack-meeting-306:51
*** bobmel has quit IRC06:56
*** lpetrut has joined #openstack-meeting-307:00
*** lpetrut has quit IRC07:08
*** bobmel has joined #openstack-meeting-307:12
*** bobmel has quit IRC07:17
*** lpetrut has joined #openstack-meeting-307:17
*** MarkBaker has quit IRC07:20
*** anilvenkata has joined #openstack-meeting-307:20
*** andreas_s has joined #openstack-meeting-307:21
*** makowals has joined #openstack-meeting-307:21
*** MarkBaker has joined #openstack-meeting-307:23
*** dimtruck is now known as zz_dimtruck07:24
*** amotoki has joined #openstack-meeting-307:28
*** lpetrut has quit IRC07:33
*** bobmel has joined #openstack-meeting-307:33
*** bobmel has quit IRC07:38
*** MarkBaker has quit IRC07:39
*** ralonsoh has joined #openstack-meeting-307:48
*** hogepodge has quit IRC07:56
*** ccamacho has joined #openstack-meeting-307:57
*** iyamahat has joined #openstack-meeting-308:02
*** sheeprine has quit IRC08:05
*** yamahata has quit IRC08:05
*** iyamahat has quit IRC08:09
*** sheeprine has joined #openstack-meeting-308:09
*** amotoki has quit IRC08:16
*** salv-orl_ has quit IRC08:21
*** lpetrut has joined #openstack-meeting-308:24
*** bobmel has joined #openstack-meeting-308:35
*** Ace__ has joined #openstack-meeting-308:38
*** bobmel has quit IRC08:40
*** pgadiya is now known as pgadiya|mtg08:50
*** pgadiya|mtg is now known as pgadiya08:50
*** MarkBaker has joined #openstack-meeting-308:53
*** bobmel has joined #openstack-meeting-308:57
*** cartik has joined #openstack-meeting-308:59
*** rossella_ has joined #openstack-meeting-308:59
*** bobmel has quit IRC09:01
*** stevejims has quit IRC09:02
*** mickeys has quit IRC09:03
*** sambetts|afk is now known as sambetts09:17
*** amotoki has joined #openstack-meeting-309:22
*** matrohon has joined #openstack-meeting-309:25
*** makowals_ has joined #openstack-meeting-309:26
*** MarkBaker has quit IRC09:27
*** wanghao has quit IRC09:28
*** makowals has quit IRC09:28
*** stevejims has joined #openstack-meeting-309:29
*** kzaitsev_mb has joined #openstack-meeting-309:43
*** kzaitsev_mb has quit IRC09:48
*** cartik has quit IRC09:50
*** MarkBaker has joined #openstack-meeting-309:55
*** xiaofandh12 has joined #openstack-meeting-309:55
*** donghao has quit IRC09:57
*** stevejims has left #openstack-meeting-309:58
*** bobmel has joined #openstack-meeting-309:59
*** mickeys has joined #openstack-meeting-310:04
*** bobmel has quit IRC10:04
*** mickeys has quit IRC10:08
*** sambetts is now known as sambetts|afk10:20
*** bobmel has joined #openstack-meeting-310:20
*** bobmel has quit IRC10:25
*** megm has quit IRC10:27
*** alexpilotti has quit IRC10:27
*** alexpilotti has joined #openstack-meeting-310:28
*** megm has joined #openstack-meeting-310:29
*** MarkBaker has quit IRC10:31
*** bobmel has joined #openstack-meeting-310:41
*** rmart04 has joined #openstack-meeting-310:46
*** kzaitsev_mb has joined #openstack-meeting-310:46
*** bobmel has quit IRC10:46
*** zhurong has joined #openstack-meeting-310:46
*** tuanluong has quit IRC10:46
*** aarefiev has joined #openstack-meeting-310:47
*** aarefiev_afk has quit IRC10:50
*** yamamoto_ has quit IRC10:59
*** bobmel has joined #openstack-meeting-311:02
*** bobmel has quit IRC11:06
*** matrohon has quit IRC11:09
*** yamamoto has joined #openstack-meeting-311:12
*** sdague has joined #openstack-meeting-311:15
*** yamamoto has quit IRC11:17
*** kzaitsev_mb has quit IRC11:20
*** bobmel has joined #openstack-meeting-311:23
*** MarkBaker has joined #openstack-meeting-311:29
*** kzaitsev_mb has joined #openstack-meeting-311:33
*** zhurong has quit IRC11:35
*** bobmel_ has joined #openstack-meeting-311:39
*** dims has joined #openstack-meeting-311:39
*** Ace__ has quit IRC11:40
*** bobmel has quit IRC11:41
*** MarkBaker has quit IRC11:47
*** ociuhandu has joined #openstack-meeting-311:52
*** huanxuan has quit IRC11:58
*** sankarshan_away is now known as sankarshan12:05
*** rtheis has joined #openstack-meeting-312:09
*** sambetts|afk is now known as sambetts12:09
*** amotoki has quit IRC12:14
*** stanzgy has quit IRC12:20
*** alexismonville has joined #openstack-meeting-312:20
*** alexismonville has quit IRC12:25
*** amotoki has joined #openstack-meeting-312:26
*** makowals has joined #openstack-meeting-312:26
*** makowals_ has quit IRC12:26
*** ccamacho is now known as ccamacho|lunch12:32
*** pgadiya has quit IRC12:48
*** liuyulong_ has joined #openstack-meeting-312:48
*** amotoki has quit IRC12:50
*** liuyulong has quit IRC12:51
*** MarkBaker has joined #openstack-meeting-312:53
*** ttrifonov has quit IRC12:53
*** claudiub has joined #openstack-meeting-313:00
*** amotoki has joined #openstack-meeting-313:00
*** sagar_nikam has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:01
openstackMeeting started Wed Jan 11 13:01:08 2017 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubhello. :)13:01
claudiubhappy new year. :)13:01
*** ttrifonov has joined #openstack-meeting-313:01
sagar_nikamHi13:01
sagar_nikamHappy new year  !!!!13:01
*** amotoki has quit IRC13:02
claudiubI hope you've had great holidays. :)13:02
claudiubso we can start this new year with fresh ideas. :D13:03
claudiubsagar_nikam: is anyone else joining?13:03
sagar_nikamno13:04
sagar_nikamwe can start13:04
claudiubcool13:04
claudiub#status nova patches status13:04
sagar_nikamyes... had a great holidays... i hope you had too....13:04
claudiubI had as well, but they passed too fast. :D13:04
claudiub#topic nova patches status13:05
*** openstack changes topic to "nova patches status (Meeting topic: hyper-v)"13:05
claudiubsoo, we had one blueprint merge.13:05
*** amotoki has joined #openstack-meeting-313:05
claudiub#link Adds support for setting boot order in Hyper-V: https://review.openstack.org/24802913:05
claudiubthe Hyper-V vNUMA implementation has a +213:06
*** yamamoto has joined #openstack-meeting-313:06
claudiub#link Hyper-V vNUMA implementation: https://review.openstack.org/28240713:06
sagar_nikamgood13:06
sagar_nikamnice to start new year with some good news13:06
claudiuband the Hyper-V OVS vif driver has a +213:07
claudiub#link Hyper-V OVS VIF driver: https://review.openstack.org/14004513:07
claudiubaaand, today is a nova review sprint day13:07
claudiubmeaning that the nova core will spend most of today reviewing patches13:07
sagar_nikamok13:07
claudiuband the vNUMA and the OVS vif driver patches are on the short-list to getting merged.13:08
claudiubhopefully they will today. :D13:08
claudiubany questions on this topic?13:09
*** matrohon has joined #openstack-meeting-313:09
sagar_nikamno13:09
claudiubcool13:10
claudiubmoving on13:10
claudiub#topic new os-win release13:10
*** openstack changes topic to "new os-win release (Meeting topic: hyper-v)"13:10
claudiubsoo, os-win 1.3.0 has been released13:10
sagar_nikamok13:10
sagar_nikamwhat is changed ?13:10
claudiubit includes some bugfixes, as well as support for nested virtualization and trunked VLANs13:10
sagar_nikamwe just cloned os-win in our downstream repo... stable/mitaka13:10
claudiubthe trunked VLANs patch should merge sometime soon on networking-hyperv13:11
*** qwebirc50747 has joined #openstack-meeting-313:11
sagar_nikamstable/mitaka is which version ... 1.3.0 ?13:11
claudiubthe latest os-win mitaka release is 0.4.213:12
claudiuband the latest newton release is 1.2.113:12
sagar_nikamok13:13
sagar_nikamsince we are getting on to mitaka now13:13
sagar_nikami guess we will stick to stable/mitaka13:13
claudiubalso, I suggest subscribing to the os-win and networking-hyperv bugs mailing lists13:13
claudiub#link https://bugs.launchpad.net/os-win13:13
sagar_nikamok13:14
claudiubwhen a release is made, the OpenStack bot will also mark which bugs has been included in which version13:14
claudiuband you'll also receive those updates on email13:14
claudiubsomething like this: [Bug 1539702] Fix included in openstack/os-win 1.3.013:14
openstackbug 1539702 in os-win "Invalid fibre channel HBA issue" [Undecided,Fix released] https://launchpad.net/bugs/1539702 - Assigned to Lucian Petrut (petrutlucian94)13:14
claudiuboh cool, the OpenStack bot is helpful. :D13:15
claudiubany questions on this topic?13:16
sagar_nikamno...13:16
sagar_nikamfrom my side13:16
sagar_nikamwe just completed the cloning part13:16
sagar_nikamthis week13:16
claudiubi see13:16
sagar_nikamof os-win13:16
sagar_nikamin our downstream repo13:16
claudiuball good?13:16
sagar_nikamso the first step to move to mitaka is done13:16
sagar_nikamyes... all good so far13:16
sagar_nikaminfact we did a small nova boot/start/stop test13:17
sagar_nikamin a dev env13:17
sagar_nikamworks fine13:17
claudiubnice :)13:17
claudiubare you planning to run some rally tests?13:17
sagar_nikamneutron yet to start13:17
sagar_nikamwe need networking-hyperv13:17
sagar_nikamin downstream repo for mitaka13:17
sagar_nikamthat needs to be done13:18
*** dbuliga has joined #openstack-meeting-313:18
sagar_nikamnot rally...but hopefully scale tests13:18
sagar_nikamsometime13:18
claudiubwell, isn't rally supposed to help with those scale tests?13:18
sagar_nikami believe our scale test team uses something else13:18
sagar_nikami am not sure13:18
sagar_nikamwe ask them to run scale tests and we fix issues13:19
claudiubi see13:19
sagar_nikamor reach out to your team13:19
claudiubi'm wondering what are they using13:19
sagar_nikamcan check13:19
sagar_nikamand let you know13:19
claudiubcool, thanks! :)13:20
sagar_nikammostly scripts... which will call nova APIs13:20
claudiubhm, i see13:21
claudiub#topic networking-hyperv patches13:21
*** openstack changes topic to "networking-hyperv patches (Meeting topic: hyper-v)"13:21
claudiubso, as I've mentioned, the trunked VLANs implementation on networking-hyperv is ready13:21
claudiubit just needs to be reviewed13:21
claudiubthe QoS implementation needs to be reviewed as well13:22
claudiubit has 2 patches, one on os-win, and one on networking-hyperv13:22
*** MarkBaker has quit IRC13:22
claudiubthere is still a minor bug to be submitted to neutron though13:22
*** qwebirc50747 has quit IRC13:23
sagar_nikamok13:23
claudiubthere are a few restrictions that needs to be taken into account, when creating neutron QoS policies, if they are to be properly used on Hyper-V nodes13:24
claudiubyou can read about them in the blueprint:13:24
claudiub#link https://blueprints.launchpad.net/os-win/+spec/os-win-network-qos13:24
sagar_nikamok13:25
*** MarkBaker has joined #openstack-meeting-313:25
claudiubany questions? :)13:25
sagar_nikamno..13:26
claudiubmoving on13:27
claudiub# topic open discussion13:27
claudiub#topic open discussion13:27
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:27
claudiubso, the feature freeze is coming soon13:27
claudiubit is on 20th jan, if i'm not mistaken13:28
claudiubso, hopefully we'll get as many patches as possible merged in nova until then. :)13:28
*** amotoki has quit IRC13:28
claudiubthen, in feb 20th, there's going to be the PTG - which will replace the OpenStack Design Summit13:29
sagar_nikamok13:29
claudiubi'll be there, if anyone wants to meetup, and / or discuss things there. :)13:29
sagar_nikamany plans of FC support in stable/mitaka .... may be not feasible... just confirming13:29
claudiubafaik, we merged the FC support in mitaka, in compute-hyperv13:30
sagar_nikami meant in upstream13:31
sagar_nikamthis involves changes in nova as well... so it might not be possibe;13:31
claudiubthis is in compute-hyperv: https://github.com/openstack/compute-hyperv/blob/stable/mitaka/hyperv/nova/volumeops.py#L58913:31
claudiubas for upstream... the os-brick patches merged in newton13:31
sagar_nikamok13:32
sagar_nikamno issues13:32
sagar_nikamwhenever we move to newton... we will use it13:32
claudiuband the patch in nova, it merged in 21 nov, which is ocata13:32
claudiubwell, it's still usable in mitaka :)13:34
sagar_nikameasily rebase able ?13:34
claudiubit should be13:35
claudiubthis is the patch that added it in nova: https://review.openstack.org/#/c/273504/2113:36
sagar_nikamok... may be we will check13:36
claudiubit looks pretty straigh-forward, it replaces the ISCSIVolumeDriver and SMBVolumeDriver with the os-brick ones13:36
sagar_nikamyes...but os-brick is in newton...13:37
sagar_nikami mean the corresponding chnages13:37
claudiubtrue, but you should still be able to use it13:37
sagar_nikamok13:38
sagar_nikamif time permits... we will try FC13:38
claudiubit is just a library, after all13:38
sagar_nikamin stable/mitaka13:38
*** amotoki has joined #openstack-meeting-313:39
claudiubwell, that's pretty much it from me13:39
*** sdake has joined #openstack-meeting-313:39
claudiubwe'll probably start building / testing an ocata release after the feature freeze13:39
claudiubsagar_nikam: anything else you want to discuss?13:40
sagar_nikamno... nothing much13:40
sagar_nikamthanks ...13:40
*** ccamacho|lunch is now known as ccamacho13:41
claudiubwell, I think we can end it here then. :)13:41
sagar_nikamyes13:41
claudiubthanks for joining, and let's hope for a very productive year. :D13:41
sagar_nikamsee you next week13:41
claudiubsee you next week!13:41
sagar_nikami hope so too..13:41
claudiub#endmeeting13:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:42
openstackMeeting ended Wed Jan 11 13:42:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-11-13.01.html13:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-11-13.01.txt13:42
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-11-13.01.log.html13:42
*** rbak has joined #openstack-meeting-313:42
*** sdake_ has joined #openstack-meeting-313:44
*** sdake has quit IRC13:46
*** MarkBaker has quit IRC13:48
*** rbak has quit IRC13:48
*** alexismonville has joined #openstack-meeting-313:49
*** seanhandley has joined #openstack-meeting-313:50
*** jjung has joined #openstack-meeting-313:50
*** yankcrime has joined #openstack-meeting-313:52
*** neiljerram has joined #openstack-meeting-313:53
*** julim has joined #openstack-meeting-313:55
*** david-lyle has quit IRC13:56
*** zhipeng has joined #openstack-meeting-313:57
*** lblanchard has joined #openstack-meeting-313:58
*** slaweq__ has joined #openstack-meeting-313:59
*** tongli has joined #openstack-meeting-313:59
*** amotoki has quit IRC13:59
*** david-lyle has joined #openstack-meeting-313:59
*** baoli has joined #openstack-meeting-313:59
*** baoli has quit IRC14:00
ralonsohlet's go14:00
slaweq__hello14:00
ralonsoh#startmeeting neutron_qos14:00
openstackMeeting started Wed Jan 11 14:00:10 2017 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:00
openstackThe meeting name has been set to 'neutron_qos'14:00
ralonsoh#chair ralonsoh14:00
openstackCurrent chairs: ralonsoh14:00
ralonsohHi everyone14:00
ralonsohHappy new Year!14:00
*** baoli has joined #openstack-meeting-314:00
slaweq__happy new Year :)14:00
ralonsohI'll wait 1 min14:00
slaweq__ok14:00
*** zhipeng has left #openstack-meeting-314:01
ralonsoh#topic RFEs14:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163479814:01
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Confirmed]14:01
ralonsohThe same status: no volunteers14:01
*** yamamoto has quit IRC14:01
ralonsohAnyone?14:02
*** yamamoto has joined #openstack-meeting-314:02
*** yankcrime has left #openstack-meeting-314:02
ajohi :)14:02
ralonsohHi14:02
ajo(I'm around while my other meeting starts)14:03
ralonsohNo volunteers for this one...14:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/1505627:14:03
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee)14:03
ajois the RFE clear?14:03
ralonsohNobody replies you14:03
ralonsohto your comment in the bug14:03
ralonsohSo I don't think so14:03
ajo':)14:04
ralonsohI'll reply again in the bug14:04
ralonsohjust to ask for feedback14:04
ralonsohnext one14:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/150562714:04
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee)14:04
ralonsohajo: you sadi to move this to incomplete14:05
ajothat one is also unclear for a long time, let me scan last reedip coments14:05
ajoright14:05
ralonsohnothing since May14:05
ralonsohWhat should we do?14:06
ajoKeep it to incomplete until they provide a clearer use case, I guess14:06
ralonsohok14:06
*** alexismonville has quit IRC14:06
ralonsohno more RFEs14:06
*** bobmel_ has quit IRC14:06
ralonsoh#topic Bugs14:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:06
ralonsohhttps://bugs.launchpad.net/neutron/+bug/165388214:06
openstackLaunchpad bug 1653882 in neutron "Creation of QOS policy name with too long name returns "Request Failed: internal server error while processing your request." instead of "Bad Request" error" [Undecided,Incomplete] - Assigned to Reedip (reedip-banerjee)14:06
ralonsohIn progress14:06
ralonsohI assigned and going on14:07
ajoralonsoh++14:07
slaweq__looks like quite easy bug :)14:07
*** yamamoto has quit IRC14:07
ralonsohI think so14:07
ralonsohnext one14:07
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164972014:07
openstackLaunchpad bug 1649720 in neutron " DSCP packet marking support in Linuxbridge agent" [Undecided,New]14:07
ralonsohslaweq: should be closed??14:08
slaweq__yep14:08
slaweq__it's about docs update14:08
ralonsohok14:08
ralonsohI'll close it14:08
slaweq__but as I wrote in comment there is no docs to update there14:08
slaweq__thx14:08
ralonsohnext one14:08
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164951714:08
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,New]14:08
ralonsohajo: should be closed?14:08
ajolet me re-read14:09
ajoah, I remember14:09
ajoany opinions on this?14:09
ralonsohthe same as you14:10
slaweq__IMHO it could be good idea to display it separately in port info14:10
ajothe alternative is providing a read only field with: (port.qos_policy_id or port.network.qos_policy_id)14:10
slaweq__so port_policy_id14:10
slaweq__and network_policy_id14:10
slaweq__but it's change in API so can be hard :/14:10
ajowell, we couldn't change exiting one for now14:10
ajoadding is easy14:10
ralonsohbut not change14:10
ajoremoving in the future, hard14:10
slaweq__so add field network_policy_id14:11
slaweq__and remain policy_id as "port_policy_id"14:11
ajoyes14:11
ajomy opinion is not strong14:11
ralonsohslaweq: do you want to take this bug?? do you have time?14:11
slaweq__ralonsoh: I can14:12
ralonsohperfect!14:12
ajoif you think it's beneficial, of course, let's go ahead :)14:12
slaweq__great, so I will try to do it14:12
ajoI think it'll be more self explanatory to the users,14:12
ajoslaweq__++14:12
*** claudiub|2 has joined #openstack-meeting-314:12
ralonsohnext one14:13
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164950314:13
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)14:13
ralonsohthere is a patch14:13
ralonsohbut not continued14:13
ralonsohI'll talk to the owner14:13
ralonsohIf the owner doesn't reply, I'll take this bug14:13
ajomy meeting starts, brb14:14
ralonsohbye!14:14
ralonsohok, so I'll follow this bug14:14
slaweq__ok14:14
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164076214:14
openstackLaunchpad bug 1640762 in neutron "when I update a Qos policy, value of shared can not be changed to false from true" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:14
ralonsohno progress14:15
slaweq__yep14:15
ralonsohno feedback14:15
ralonsohI'll ask again14:15
slaweq__and I cannot reproduce it :/14:15
slaweq__as I wrote in comment14:15
ralonsohyes, that's the problem14:15
slaweq__IMHO there is no bug in fact14:15
ralonsohwe need more feddback14:15
ralonsohyes, I know14:15
slaweq__ok, so we will still wait14:15
ralonsohjust if you can ask again14:15
*** claudiub has quit IRC14:16
slaweq__ok, I will try14:16
ralonsohthanks!14:16
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164075714:16
openstackLaunchpad bug 1640757 in neutron "Parameter validation for string type parameters" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:16
slaweq__#action slawek ask about https://bugs.launchpad.net/neutron/+bug/164076214:16
openstackLaunchpad bug 1640762 in neutron "when I update a Qos policy, value of shared can not be changed to false from true" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:16
*** david-lyle has quit IRC14:16
ralonsohtha same problem14:16
ralonsohno feedback14:16
slaweq__exactly14:16
slaweq__and IMHO also no issue here14:16
ralonsohI think the same as you14:17
*** seanhandley has left #openstack-meeting-314:17
ralonsohso, ask again14:17
ralonsohif no reply, we can close it14:17
slaweq__I think so14:17
ralonsohnext one14:17
ralonsohhttps://bugs.launchpad.net/neutron/+bug/163922014:17
openstackLaunchpad bug 1639220 in neutron "[RFE] Default action for RBAC" [Undecided,New]14:17
ralonsohfor ajo14:17
ralonsoh#action ajo reply with status of this bug: https://bugs.launchpad.net/neutron/+bug/163922014:18
slaweq__this is new one14:18
ralonsohyes14:18
ralonsohbut we need ajo's knowledge in this one14:18
ralonsohbecause he has a talk with Kevin14:18
slaweq__yep14:18
ralonsohso action for ajo14:18
slaweq__ok14:18
ralonsohnext one14:19
ralonsohhttps://bugs.launchpad.net/neutron/+bug/163918614:19
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:19
ralonsohI don't know what is happening....14:19
ralonsohthe same problem14:19
slaweq__in comments there is no anything new about it14:19
ralonsohthis bug involves a lot of things14:20
ralonsohtrunks ports14:20
ralonsohand qos14:20
ralonsohRight now, I don't think we can solve this14:20
*** claudiub has joined #openstack-meeting-314:20
*** davidsha has joined #openstack-meeting-314:20
slaweq__I agree14:20
*** sdake has joined #openstack-meeting-314:21
ralonsohBut, I need to talk to ajo, because it's important to have qos on trunks14:21
davidshaHi, sorry I'm late14:21
ralonsohhi David14:21
slaweq__hello davidsha14:21
*** Swami has joined #openstack-meeting-314:21
ralonsohok, last one14:21
ralonsohhttps://bugs.launchpad.net/neutron/+bug/163074814:21
openstackLaunchpad bug 1630748 in neutron "project_id is not present on all resources" [High,In progress] - Assigned to Darek Smigiel (smigiel-dariusz)14:21
ralonsohIt's finished14:21
ralonsohSo I'll close it manually14:21
*** zz_dimtruck is now known as dimtruck14:22
ralonsohthere are patches for newton and master14:22
slaweq__ok14:22
ralonsohno more bugs14:22
ralonsohin the list14:22
ralonsohanyone has another bug?14:22
slaweq__I don't have anything new14:23
ralonsohok14:23
ralonsoh#topic Other Changes14:23
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"14:23
ralonsohnothing in the list14:23
ralonsohanyone??14:23
*** claudiub|2 has quit IRC14:23
*** sdake_ has quit IRC14:23
*** stevejims has joined #openstack-meeting-314:23
slaweq__ralonsoh: I reviewed Your huge patch with ingress limit for linuxbridge :)14:23
ralonsohhehehe14:23
ralonsohthanks!14:24
ralonsohI know14:24
*** VW has joined #openstack-meeting-314:24
ralonsohnow I need a core to take a look14:24
ralonsohuhmmm ajo!14:24
ralonsoh#action ajo review  https://review.openstack.org/#/c/357865/14:24
slaweq__it can be hard to You to find 2 cores who will review it :)14:24
ralonsohI know... I need this one for the RFE strict min bw support14:25
ralonsohok14:25
ralonsoh#topic Open Discussion14:25
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:25
ralonsohI have one14:25
ralonsohThe BW manager for qos in SRIOV14:25
ralonsohhttps://review.openstack.org/#/c/401254/14:25
ralonsohis low priority, but could be fine to have some reviews14:26
ralonsohanyone have any query?14:26
ralonsohneed for reviews??14:26
slaweq__ok, I will try to look on it asap14:26
ralonsohThank you!!14:27
slaweq__but I'm not sriov expert so ...14:27
ralonsohATLANTA PTG planning!14:27
ralonsohWho is going??14:27
slaweq__btw. do You know what is happening with https://review.openstack.org/#/c/396297/3/specs/ocata/strict-minimum-bandwidth-support.rst ?14:27
slaweq__ajo assigned me to one of points14:27
slaweq__but I don't know in fact if/when I can/should start working on it :)14:28
ralonsohYes, it's for the next release14:28
ralonsohThat's the point: we need to talk with ajo during this meetings14:28
ralonsohI'm doing the first part14:28
ralonsohThe previous link: https://review.openstack.org/#/c/401254/14:28
slaweq__yep, I know14:28
slaweq__I was reviewing BW manager patches for ovs and/or linuxbridge14:29
ralonsohWe need also Miguel Lavalle to attend this meeting14:29
slaweq__right?14:29
ralonsohyes14:29
slaweq__:)14:29
ralonsohand thank you!!14:29
slaweq__no prob14:29
ralonsohso, are you going to Atlanta?14:30
slaweq__about Atlanta, I'm not going there14:30
ralonsoh8-(14:30
davidshaD:14:30
ralonsohSorry about that14:30
*** yamamoto has joined #openstack-meeting-314:30
slaweq__are You going?14:30
ralonsohIf I can go, I'll skype you during the meeting14:30
*** VW_ has joined #openstack-meeting-314:31
*** VW has quit IRC14:31
slaweq__would be great14:31
ralonsohis something missing today??14:31
davidshaWe've covered rfe's, bugs and opens?14:32
ralonsohyes14:32
ajosorry guys, I'm back14:32
ajofinished the other meeting14:32
ralonsohalmost finish14:32
slaweq__You are fast :P14:32
ralonsohno problem14:32
*** sagar_nikam has quit IRC14:32
ralonsohTwo questions14:33
ralonsohhttps://bugs.launchpad.net/neutron/+bug/163922014:33
openstackLaunchpad bug 1639220 in neutron "[RFE] Default action for RBAC" [Undecided,New]14:33
ralonsohajo: status?14:33
ajoralonsoh opening the link you posted for review14:33
ajoralonsoh about RBAC default action?14:33
ralonsohyes14:33
*** jgrassler has joined #openstack-meeting-314:34
ajooh, we could do that, but not the way it was proposed14:34
ajoI talked about that with kevinbenton once, and14:34
ajo"a default" doesn't make sense in the role based access14:34
*** yamamoto has quit IRC14:34
ajowe could include it in the QoS API if we wanted14:35
ajolet me answer again to see if it makes sense to Jens14:35
*** yamamoto has joined #openstack-meeting-314:35
ralonsohok14:35
*** MarkBaker has joined #openstack-meeting-314:35
ralonsohIf the spec is redefined, I can take this bug14:35
ajoralonsoh14:36
ajohow would you define the openstack cli command for this?14:36
ajoif we wanted to provide some sort of "default" policy14:36
ralonsohI mean: if you redefine the spec of the bug14:36
ajoyes, something very basic in terms of openstack-cli14:37
ralonsohok, so you will add a new definition in the bug?14:38
ralonsohjust to know how to proceed14:38
ajohmm14:38
ajomay be14:38
ajoopenstack network qos policy default set <qos-policy-id> ?14:38
ajoI'm seeing a similar pattern with:14:39
ajonetwork ip floating list14:39
ajoand14:39
ajonetwork ip floating pool list14:39
ajocommands14:39
ralonsohyes, I see14:39
*** amotoki has joined #openstack-meeting-314:39
ralonsohOk, I'll write this in the bug14:39
ajonetwork qos policy default (create/set/delete)14:39
ajoack14:40
ajoI'll add that14:40
*** yamamoto has quit IRC14:40
ralonsohand I'll submit a patch14:40
ralonsohone more, ajo14:41
ralonsohhttps://review.openstack.org/#/c/357865/14:41
ralonsohLB with min QOS14:41
ralonsohI need a core14:41
ralonsohto review it14:41
slaweq__good luck with this one ajo :)14:41
slaweq__it's big14:41
ralonsohsorry for that...14:41
ajoack ':D14:42
ajoralonsoh sorry?, thank you ;D14:42
slaweq__but IMO it's good14:42
davidshaThere was also an SR-IOV one right?14:42
ralonsohyes, but low priority14:42
ralonsohthe first part of strict bw14:42
davidshakk, link for ref: https://review.openstack.org/#/c/401254/14:42
ralonsohjust to know if i'm going in the right direction14:43
*** yamamoto has joined #openstack-meeting-314:43
ralonsohNothing but me....14:43
ralonsohAnything else?14:43
ajohmm, the meeting time switch,14:44
ralonsohyes!!!14:44
ajoif we call can in any of the timeslots I suggested :)14:44
ajocall can?14:44
ajoall can...14:44
ralonsohyes, all of them14:44
slaweq__for me all of them was fine14:44
ralonsohdavid??14:44
ajolet me look them up again, 1 sec14:44
ralonsohpossible timeslots I found for QoS: Tuesdays @ 16:00 UTC  (after the neutron main meeting),  Mondays @ 15:00 UTC,  Thursdays @ 15:00 UTC14:44
*** makowals has quit IRC14:45
davidshathose are the times proposed on the main neutron channel right? I'm happy with those.14:45
ajothanks ralonsoh14:45
ajoany preference?14:45
ralonsohtuesdays14:46
slaweq__ok for tuesday14:46
davidshaTuesday is good14:46
ralonsohperfect!14:46
ralonsohajo: do you know how to change it?14:47
ralonsohI don't14:47
ajook, I'll propose a patch right away14:47
ajothank you floks14:47
ajofolks14:47
ralonsohthanks14:47
ajoyeah, it's a patch to irc-meetings repo14:47
ralonsohok14:47
ralonsohso anything else?14:47
ralonsohI end the meeting14:48
*** bobmel has joined #openstack-meeting-314:48
ralonsoh#endmeeting14:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:48
openstackMeeting ended Wed Jan 11 14:48:14 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:48
davidshaThanks!14:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-11-14.00.html14:48
ralonsohbye!14:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-11-14.00.txt14:48
slaweq__thanks14:48
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-01-11-14.00.log.html14:48
slaweq__bye14:48
davidshaCya!14:48
ajothank you ralonsoh , slaweq__ , davidsha !!14:48
davidshaajo: Hey, quick question. You're going to the PTG right?14:49
*** dimtruck is now known as zz_dimtruck14:49
*** tongli has quit IRC14:49
*** yamamoto has quit IRC14:49
*** sdake_ has joined #openstack-meeting-314:51
*** cleong has joined #openstack-meeting-314:51
*** gouthamr has joined #openstack-meeting-314:52
*** tomasztrebski has joined #openstack-meeting-314:52
*** VW_ has quit IRC14:52
*** VW has joined #openstack-meeting-314:53
*** bobmel has quit IRC14:54
*** sdake has quit IRC14:54
*** MarkBaker has quit IRC14:54
*** millerthomasj has joined #openstack-meeting-314:54
*** sgrasley has joined #openstack-meeting-314:55
*** makowals has joined #openstack-meeting-314:55
*** sgrasley has left #openstack-meeting-314:55
*** hosanai has joined #openstack-meeting-314:56
*** sgrasley has joined #openstack-meeting-314:56
*** zhipeng has joined #openstack-meeting-314:57
*** witek has joined #openstack-meeting-314:58
*** bobmel has joined #openstack-meeting-314:59
*** jobrs has joined #openstack-meeting-315:00
*** rbak has joined #openstack-meeting-315:00
*** rhochmuth has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Jan 11 15:01:06 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmutho/15:01
rbako/15:01
hosanaio/15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
shinya_kwbto/15:01
rhochmuthhi everyone15:01
tomasztrebskio/15:01
tomasztrebskiyolo ;)15:01
rhochmuthi was running a little late15:01
rhochmuthbut i made it15:02
witekhello15:02
*** galstrom_zzz is now known as galstrom15:02
rhochmuthlooks like a few items on the agenda15:02
rhochmuth1.https://review.openstack.org/#/c/406511/ - See Tomasz's comments and how to proceed ?15:02
rhochmuth2.https://review.openstack.org/#/c/418598/ - Enable Log Management via specific policy15:02
rhochmuth3.Postgresql-based CI -> tempests running ;-)15:02
rhochmuth1.https://review.openstack.org/#/c/356403/15:02
rhochmuth2.https://review.openstack.org/#/c/418271/15:02
millerthomasjo/15:02
rhochmuth#topic https://review.openstack.org/#/c/406511/15:02
*** cbellucci has joined #openstack-meeting-315:02
*** openstack changes topic to "https://review.openstack.org/#/c/406511/ (Meeting topic: monasca)"15:02
*** zhipeng has quit IRC15:03
*** bklei has joined #openstack-meeting-315:03
bkleio\15:04
tomasztrebskiyeah, so this entry is mine but apart from the question to you to read and put your opinion there, nothing in particular that could be added15:04
rhochmuthi think i'm ok with merging this change15:04
rhochmuthi don't want to hold anyone back15:04
rhochmuthand i'm not aware of anyone using the mongo plugin15:04
*** iyamahat has joined #openstack-meeting-315:04
tomasztrebskido you think filling a bug is in order ?15:05
rhochmuthsure a bug would be in order15:05
rhochmuthit wouldn't hurt15:05
rhochmuthand would allow us to track this15:06
*** spzala has joined #openstack-meeting-315:06
*** spzala has quit IRC15:06
tomasztrebskiok, so that would be all about that, if Joe is fine about it too, we can merge that15:06
*** spzala has joined #openstack-meeting-315:06
rhochmuthi'll add a +1, and let whoever wants to merge it take it from there15:06
tomasztrebskikk15:07
rhochmuth#topic https://review.openstack.org/#/c/418598/15:07
*** openstack changes topic to "https://review.openstack.org/#/c/418598/ (Meeting topic: monasca)"15:07
rhochmuthi'm reading the review for the first time15:08
*** bobmel_ has joined #openstack-meeting-315:08
millerthomasjI work with rbak and bklei, I need this change to be able to allow access to log management with or without grafana also being enabled15:08
*** MarkBaker has joined #openstack-meeting-315:08
rhochmuthwho are rbak and bklei15:09
bklei:)15:09
*** nkrinner is now known as nkrinner_afk15:09
tomasztrebskimillerthomasj: you saw my comment about doing exact same thing for grafana ?15:09
millerthomasjyes, the way grafana is enabled already allows us to set a different policy in our policy.json with no issue15:10
rhochmuthi'll defer to tomasz and witek15:10
*** bobmel has quit IRC15:10
witeklgtm15:10
tomasztrebskioh...wonder how this works without this one15:11
tomasztrebskibut since this is possible, i guess lgtm as well15:11
*** JamesGu has joined #openstack-meeting-315:11
rhochmuthdoes devstack continue to work?15:12
millerthomasjmy real problem is the default admin_required for us is already set to a role for monasca-admin...i want to create a new role for logs_admin15:12
*** claudiub|2 has joined #openstack-meeting-315:12
millerthomasjthe change i proposed doesn't change the default behavior since it defaults to admin_required15:12
*** caboucha has joined #openstack-meeting-315:12
tomasztrebskirhochmuth: dont know, did not really had time to install that and see for myself if it works15:12
rhochmuthmillerthomasj: did you run in devstack?15:13
millerthomasji did not, i ran tests in our development environment here at TWC/Charter15:13
millerthomasji can run the devstack tests also15:14
rhochmuthmillerthomasj: thanks15:14
rhochmuthi don't think the tests will be impacted15:14
*** psachin has quit IRC15:14
rhochmuthbut, just wondering if devstack comes up with logging/kibana15:15
rhochmuthi guess i shoudl say works with kibana still15:15
tomasztrebskiit does, through monasca-log-api15:15
tomasztrebskidevstack plugin15:15
witekyou should enable monasca-log-api plugin and test manually15:15
tomasztrebskisee here: https://github.com/openstack/monasca-log-api/blob/master/devstack/Vagrantfile#L10415:16
millerthomasjwill do15:16
*** claudiub has quit IRC15:16
rhochmuththx15:16
witekthanks15:16
rhochmuthafter done, then please add a comment to the review and tomasz, witek and i will get merged15:16
rhochmuthi think15:17
tomasztrebski]:->15:17
tomasztrebskisure thing :)15:17
rhochmuth#topic Postgresql-based CI -> tempests running ;-)15:17
*** openstack changes topic to "Postgresql-based CI -> tempests running ;-) (Meeting topic: monasca)"15:17
*** david-lyle has joined #openstack-meeting-315:17
tomasztrebskiyeah, that's from me15:17
tomasztrebskiI had some surprise when I saw that under postgresql tempest are failing with authorization issues15:18
tomasztrebskibut work on mysql15:18
*** srobert has joined #openstack-meeting-315:18
*** hogepodge has joined #openstack-meeting-315:18
rhochmuththat is a surprise to me too15:18
tomasztrebskiluckily enough this change put me on right track: https://review.openstack.org/#/c/409584/15:18
tomasztrebskiI created a follow up: https://review.openstack.org/#/c/41827115:18
rhochmuthso, we need to merge, https://review.openstack.org/#/c/409584/15:19
rhochmuthit was merged, never mind15:19
tomasztrebskias it turned out there were some other issues with tempest configuration monasca-api plugin has been providing, so after fixing that and putting postgresql on top of that15:19
*** galstrom is now known as galstrom_zzz15:19
tomasztrebskitempests finally kicked off15:19
tomasztrebskithey are failling which is not that unexpected I guess15:19
tomasztrebskibut I think that's a story for another change or changes15:20
tomasztrebskibtw: sorry for lot of noise in mailbox and all those notifications, tried to remove reviewers until I fixed that but couldn't remove them all15:20
*** zz_dimtruck is now known as dimtruck15:21
rhochmuthso, you would like, https://review.openstack.org/#/c/418271/5, merged15:21
rhochmuththen https://review.openstack.org/#/c/356403/15:21
*** david-lyle has quit IRC15:21
rhochmuthis that the sequence15:22
*** sdake_ has quit IRC15:22
tomasztrebskiyes, that's the sequence15:22
*** yamahata has joined #openstack-meeting-315:22
tomasztrebski+ the next step, that would be the best15:22
tomasztrebski*steps actually15:22
*** sdake has joined #openstack-meeting-315:23
*** marst has joined #openstack-meeting-315:23
tomasztrebskinot to mention that python looks fairly good with only 4 failed tests, but java is totally different story15:23
tomasztrebskicheck here: http://logs.openstack.org/03/356403/75/experimental/gate-tempest-dsvm-monasca-java-postgresql-full-ubuntu-xenial-nv/8754d8f/logs/testr_results.html.gz15:23
rhochmuthok, i'm assuming the zuul will come back soon, but i added a +1 to your tempest review15:23
rhochmuthso there is either code or test to resolve15:24
tomasztrebskiok, but what should we do next, should we move gates from experimantal to just NV (but that would kick those 2 gates for all changes that wouldn't actually fixed that) or should we start fixing that and when we have decent (100%) success rate move to NV or even voting stage ?15:25
tomasztrebskiand if there would be any help from the community with it ?15:26
rhochmuthi would prefer the latter15:26
*** raj_singh_ has joined #openstack-meeting-315:26
rhochmuthdo you think this is a test problem or problm in the postgres code15:27
*** spotz_zzz is now known as spotz15:27
*** alexismonville has joined #openstack-meeting-315:27
tomasztrebskino idea at this point15:28
*** donghao has joined #openstack-meeting-315:28
tomasztrebskisorry15:28
*** bobmel has joined #openstack-meeting-315:28
*** markvoelker has quit IRC15:28
*** baoli has quit IRC15:28
rhochmuthis there anymore to discuss on this topic then?15:29
rhochmuthjust wondering if what i said is ok or if you prefer moving to nv status15:29
*** markvoelker has joined #openstack-meeting-315:29
tomasztrebskiI'd certainly like to know Craig's opinion on that topic, not really sure if he's here but he was the one who brought up the idea of CI with Postgres15:30
*** xiaofandh12 has quit IRC15:30
*** bobmel_ has quit IRC15:31
rhochmuthhe doesnt' usually attend the weekly meeting15:31
rhochmuthbut i'll ping him thius morning15:31
tomasztrebskinaughty...naughty....15:31
rhochmuthand get back to you15:32
tomasztrebskithx15:32
tomasztrebskiok, from my side that's all15:32
rhochmuthso, does that cover all the topics from the agenda then15:32
rhochmuth#topic misc15:33
*** openstack changes topic to "misc (Meeting topic: monasca)"15:33
tomasztrebskiany news on storyboard ?15:33
rhochmuthstoryboard didn't go well15:33
tomasztrebski:(15:33
rhochmuthsteve followed up with the infra team15:34
rhochmuthit doesnt' look like it is really ready for prime-time usage by us15:34
rhochmuthso, currently we aren't going to use ut15:34
*** markvoelker has quit IRC15:35
rhochmuthsteve will submit his bp through the normal process15:35
rhochmuthas well as document his plans in the wiki15:35
rhochmuthand we'll start working with him on designs/reviews15:35
rhochmuthi should point out that there are a lot of reveiws to catch-up on15:36
rhochmuthhpe was a bit busy/distracted on other things, but we are going to try and catch-up a bit15:37
rhochmuthit would be great if others could do the same15:37
tomasztrebskiwe do try, but at least fo Fujitsu that's the same story :/15:37
rhochmuthunderstand15:38
*** sankarshan is now known as sankarshan_away15:38
*** diablo_rojo_phon has joined #openstack-meeting-315:38
rhochmuthi think that is all i have, but for reviews that we think need to get addressed, we'll update with some comments15:39
rhochmuthunless anyone has anything else, then i guess i'll close the meeting15:39
tomasztrebskithere is one thing, that was actually the question to monasca coming from this change that I think is worth putting here: https://review.openstack.org/#/c/418308/15:40
tomasztrebskicomment from Tony15:40
*** thingee has joined #openstack-meeting-315:40
rhochmuththatnks for point out15:40
*** galstrom_zzz is now known as galstrom15:41
diablo_rojo_phonhey rhochmuth you mentioned storyboard? If it has all the things Monasca needs you can definitely migrate there.15:41
witekany news about kafka-python?15:41
*** galstrom is now known as galstrom_zzz15:41
rhochmuthdiablo_rojo_phon: interesting15:42
diablo_rojo_phonrhochmuth: or if there are things missing I'd love to hear what they are so I can help get them implemented :)15:42
rhochmuththe impression we got was that migration might be difficult15:42
rhochmuthhere is the summary that i got15:42
rhochmuth- They don't want to duplicate projects across trackers, so Monasca would have to migrate away from Launchpad15:42
rhochmuth- There are scripts to migrate existing issues, but they may have, quote, "be a little bitrotted"15:42
rhochmuth- Requires change to the project Puppet config, #openstack-infra is the place to ask for more details15:43
rhochmuth- For issues shared with other projects, those projects are required to migrate to Storyboard at same time15:43
diablo_rojo_phonrhochmuth: For some projects dependent on others yes, but not for everyone.15:43
diablo_rojo_phonRight, your last point is what is stopping most projects at this point I believe.15:43
rhochmuthi see15:44
*** spzala has quit IRC15:44
diablo_rojo_phonThe scripts to migrate might be a little out of date, but it shouldn't be that hard to get them up to snuff :)15:44
*** spzala has joined #openstack-meeting-315:44
rhochmuthalthough, i don't think we have many issues shared with other projects15:44
fungithe bitrot in the migration scripts is just because nobody has requested a migration in a while. that's certainly solvable15:44
diablo_rojo_phonThanks fungi :)15:44
rhochmuththx fungi15:44
*** spzala has quit IRC15:45
rhochmuthso, what do you suggest then15:45
fungiit's just that storyboard's featureset and data model have changed slightly since the last time we migrated anything, so we'd want to do some tests on storyboard-dev to make sure importing still works15:45
*** spzala has joined #openstack-meeting-315:45
fungiand if monasca wants to migrate from lp to sb, we can up the priority on whipping the migration script back into shape (or it may turn out to still work just fine)15:46
diablo_rojo_phonI can talk to Zara about getting that on the agenda today for the stoeyboard meeting and circle back around to you rhochmuth about getting Monasca moved.15:46
diablo_rojo_phon*storyboard15:46
rhochmuthit sounds good to me15:46
diablo_rojo_phonSweet :)15:46
rhochmuthi think we had a little of the deer in the headlights syndrome15:47
*** Swami_ has joined #openstack-meeting-315:47
rhochmuthbut, if you are willing to go through that work for us, then i think we are game15:47
diablo_rojo_phonrhochmuth: you're not the only ones so no worries15:47
rhochmuthwitek tomasz ???15:47
*** alexismonville has quit IRC15:47
tomasztrebski+115:47
tomasztrebski:P15:47
diablo_rojo_phonExcellent15:47
rhochmuthbklei?15:47
bkleisorry -- got distracted, reading back15:48
rhochmuthlooks like we might be able to migrate to storyboard after all15:48
bkleii'm in full support of that!15:48
rhochmuththx15:48
witekme too15:48
*** alexismonville has joined #openstack-meeting-315:48
rhochmuthi think we've got a quorum then15:48
tomasztrebskiwitek: what about kafka-python ?15:49
rhochmuthdiablo_rojo_phon: thx, looks like we are reay to migrate15:49
rhochmuthif you and fungi can help15:49
*** Swami has quit IRC15:49
rhochmutheveryone want to move15:49
diablo_rojo_phonrhochmuth: Cool, if you wanna join the storyboard meeting I can send you the info, otherwise Ill ping you after.15:49
*** MarkBaker has quit IRC15:50
rhochmuthis that meeting tomorrow?15:50
witekoslo.messaging wants to uncap the version which is problematic for us15:50
*** Sukhdev has joined #openstack-meeting-315:50
*** yamamoto has joined #openstack-meeting-315:50
tomasztrebskiaaah, that would move the client version to the one which supports newer kafka what they likely need15:51
tomasztrebski?15:51
fungirhochmuth: today at 19:00 utc in #openstack-meeting15:51
fungi#link http://eavesdrop.openstack.org/#StoryBoard_Meeting15:52
*** armax has joined #openstack-meeting-315:52
rhochmuththx fungi, i'll try and make it, but might have a conflict today15:52
rhochmuthwill try15:52
*** sgrasley has quit IRC15:53
*** alexismonville has quit IRC15:53
tomasztrebskiwitek: if they do this, we will have to update the devstack to roll on with newer kafka and all that15:53
rhochmuthso, the last i talked to joe keen, he still had concerns15:53
rhochmuthwith the newer kafka client15:53
*** duartea__ has quit IRC15:53
tomasztrebski+ they will several changes from requirements bot15:53
tomasztrebski*will be15:54
rhochmuththe simple consumer/producer that we use is "deprecated" in that library15:54
tomasztrebskiwell both monasca-api and monasca-log-api would be affected15:54
rhochmuthand we can't use the async, unless we change our code15:55
tomasztrebskinot really sure if monasca-notification and monasca-persister uses monasca-common and in result kafka-python15:55
rhochmuthand it is more than just a trivial change if we want to have guaranteed message delivery15:55
rhochmuthhowever, we were also very interested in the confluent library and moving to that15:55
rhochmuthwhich also is only async15:55
tomasztrebskiyeah, about that...I could find any free time to continue checking on it...15:56
tomasztrebskigot some code saved somewhere and that's it15:56
*** diablo_rojo has joined #openstack-meeting-315:56
rhochmuthso, my preference was to switch to the confluent library15:56
rhochmuththen that woiuld remove the dependency15:57
rhochmuthbut in the short-term, i don't have any great ideas15:57
*** markvoelker has joined #openstack-meeting-315:57
*** CatherineD1 has joined #openstack-meeting-315:57
rhochmuthmoving to a deprecated part of a library by bumping to the latest version in the library seems somewhat risky too15:57
rhochmuthalthough that would free up oslo for making progress15:57
rhochmuthon the library that they want to use15:58
rhochmuthi'll have to check-in with joe again15:58
tomasztrebskiin the end, if they would manage to put their functionality into kafka, that would be beneficial for all15:58
rhochmuthnot sure i understand that15:59
*** claudiub has joined #openstack-meeting-315:59
rhochmuthstatement15:59
tomasztrebskimaybe not directly to us, I mean15:59
*** shamail has joined #openstack-meeting-315:59
rhochmuthi'll check in with joe15:59
witekrhochmuth: thanks15:59
rhochmuthand will try and attend storyboard later15:59
rhochmuthhave to close meeting down now15:59
rhochmuththanks everyone16:00
*** cbellucci has quit IRC16:00
tomasztrebskivye16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jan 11 16:00:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-11-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-11-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-11-15.01.log.html16:00
*** bklei has quit IRC16:00
*** hosanai has quit IRC16:00
markvoelker#startmeeting interopwg16:01
openstackMeeting started Wed Jan 11 16:01:22 2017 UTC and is due to finish in 60 minutes.  The chair is markvoelker. 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: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
markvoelker#chair eglute hogepodge16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
egluteo/16:01
CatherineD1O/16:01
markvoelker#link https://etherpad.openstack.org/p/DefCoreRoble.8 Today's agenda16:02
*** claudiub|2 has quit IRC16:02
shamailHi everyone.  I am here I am double-booked today so partially looking at the chat (please use mention if I am needed)16:02
*** bobmel_ has joined #openstack-meeting-316:02
*** yamamoto has quit IRC16:02
*** bobmel has quit IRC16:02
*** witek has left #openstack-meeting-316:02
hogepodgeo/16:02
*** bobmel_ has quit IRC16:03
markvoelker#topic Finishing up 2017.0116:03
*** openstack changes topic to "Finishing up 2017.01 (Meeting topic: interopwg)"16:03
*** bobmel has joined #openstack-meeting-316:03
markvoelkerWe have a handful of patches left that really need to land this week if they're going on.16:03
markvoelker*in16:03
markvoelkerProbably the biggest concern is what to do with the Cinder v2->v3 stuff16:03
markvoelker#link https://review.openstack.org/#/c/408427/ Cinder patch16:04
*** tomasztrebski has quit IRC16:05
hogepodgeDid we reach a consensus last week?16:05
shamailI looked at the change and didn’t see any new comments specifying the agreed upon direction16:05
*** zhipeng has joined #openstack-meeting-316:06
hogepodgemarkvoelker: eglute: do you think we've reached a consensus direction?16:06
*** kukacz has joined #openstack-meeting-316:06
markvoelkerhogepodge: I thought we had last week, but there were still some concerns discussed. =)16:06
luzCo/16:06
* eglute looks back at chat history16:07
markvoelkerMy inclination is to land it as-is since it's advisroy, and potentially work with the existing fields in the schema as a follow-up16:07
markvoelkerIF we feel the need to add to the schema to more explicitly call out the versioning that's fine (it's a bit late in the game though)16:08
*** anilvenkata has quit IRC16:08
eglutei agree with markvoelker. let us know if you disagree16:09
*** gema has joined #openstack-meeting-316:09
*** salv-orlando has joined #openstack-meeting-316:09
*** bobmel has quit IRC16:09
*** bobmel has joined #openstack-meeting-316:10
*** garloff has joined #openstack-meeting-316:10
eglutehogepodge you ok with this?16:10
hogepodgeeglute: markvoelker yes16:11
egluteanyone else have other opinions?16:12
markvoelkerOk then, please register your +/-1/2's in gerrit and we'll put this to bed.16:12
shamailthanks.16:12
markvoelker#link https://review.openstack.org/#/c/385781/ Nova patch16:13
eglutethank you shamail!16:13
*** Rockyg has joined #openstack-meeting-316:13
markvoelkerI think shamail's latest patchset on this took care of the last nits so I think we're ready to roll barring any further discussion16:14
shamailI updated the Nova patch to fix the Foundation bit right before this meeting.16:14
shamailyeah  :)16:14
Rockygo/16:14
hogepodgetypos in the swift patch were updated too, so that looks good to go. thanks eglute16:14
eglutethanks hogepodge no idea how that fatfinger ended up there16:15
eglutegood catch16:15
markvoelkerOk, so hearing no dissent here, let's get those gerrit votes in16:16
markvoelker#link https://review.openstack.org/#/c/398428/ Swift patch16:16
*** matrohon_ has joined #openstack-meeting-316:16
markvoelkerLooks like the last nits have been dealt with here too...any last comments before we land it?16:17
markvoelkerOk then, I think that about finishes off 2017.01. =)16:18
*** JamesGu has quit IRC16:18
markvoelkerOnce these merge I'll put up a patch to create the new document from next16:18
eglutethanks markvoelker16:18
* garloff congratulates us to finalize 2017.01 :-)16:18
*** matrohon has quit IRC16:19
markvoelkereglute: just to confirm, are we on the BoD agenda?16:19
eglutei will confirm! there was no call for agenda items yet16:19
garloffJan24?16:19
markvoelkereglute: thanks16:20
markvoelkergarloff: yes16:20
eglute#link https://wiki.openstack.org/wiki/Governance/Foundation/24Jan2017BoardMeeting16:20
markvoelkerOk, that brings us to....16:20
markvoelker#topic PTG16:20
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:20
markvoelker#link https://etherpad.openstack.org/p/InteropWGAtlantaPTG  Etherpad for PTG Topics16:20
markvoelkerPlease be aware that we're sharing space with RefStack and the interop challenge folks, so we may need to keep things trim16:21
*** neiljerram has quit IRC16:21
markvoelkerI'd like to finalize a list of topics by the end of tomorrow so I can coordinate with catherine and Brad on who has the floor when16:21
*** ddyer has joined #openstack-meeting-316:21
markvoelkerSo:16:22
markvoelker#action Call for PTG agenda items closes tomorrow, please add ideas to https://etherpad.openstack.org/p/InteropWGAtlantaPTG16:22
*** salv-orl_ has joined #openstack-meeting-316:22
markvoelker(if you haven't already...we've had the pad open for a couple of weeks now)16:23
eglutei think New components/add-on programs is a big one16:23
markvoelkerWe definitely have plenty of interesting topics to talk about. =)  Pity we don't have more time/space.16:23
markvoelkerAlso, if you're planning to come to the PTG, please drop your name in the top of the etherpad there just to give us idea of who will be there16:24
hogepodgeYeah, I'm not sure the PTG format is really a great place for us to be meeting. Seems to constrained by TC needs and rules.16:24
hogepodgeBut, we should give it a try and see how it works out this time around.16:25
gema+116:25
*** salv-orlando has quit IRC16:25
markvoelkerAs a reminder, we (Interop WG, RefStack, interop challenge) have the room Monday-Tuesday for those making travel plans16:25
gemawe can always go back to the old 3 day long format16:25
gemait was rather productive16:25
markvoelkerAnything folks want to discuss about the PTG planning right now?16:26
egluteagree.. also we need to see if we want to be recognized as separate official project for PTGs16:26
*** zhipeng has quit IRC16:26
eglutei am interested to see how this PTG will go16:26
eglutedo we need to set up some time with Heat/Ceilometer folks?16:27
egluteor any other project? since they are going to be there16:28
hogepodgeI'll be at the PTG until Friday noon, so I can meet with other groups as needed16:28
egluteif you can think of other todo items for 2017.0816:28
garloffeglute: Do we consider heat to become part of DefCore (or some DefCore+)?16:28
hogepodgeagree on the add ons, which is in part dependent on the 2.0 schema that I haven't put enough work in to16:29
eglutegarloff yes we been talking about it, but heat is not ready because of how their tests are setup16:29
garloffthen let's meet ...16:29
* garloff acknowledges is easy to say -- will most likely not be able to make it to ATL16:30
hogepodgeone of the heat issues is that the api is pretty basic, and is meant to manage the template payloads which is its own language, not covered by tempest api tests16:30
eglutegarloff we met with them in barcelona, and they committed to doing some work to change this, so we need to follow up and see where they are at16:30
*** ocartier_ has joined #openstack-meeting-316:30
garloffhogepodge: the issue being that tempest framework does not match well testing the payloads, jsut API behavior?16:31
*** galstrom_zzz is now known as galstrom16:31
egluteheat team was going to work on new tests and switch to gabi? or something like that.16:31
*** ocartier has quit IRC16:32
hogepodgegarloff: yeah, and heat is dependent on what other projects are installed and what capabilities they have enabled16:32
markvoelkergarloff: weak attempt at summary: For heat, the API isn't the main source of end user interoperability--it's the heat templates and the resources they provide (which in turn depend on what API's from other projects are supported on the cloud)16:32
garloffhogepodge: so any realistic heat testcase actually is testing a dozen things in one test which is not how you want testing to work16:33
garloffmarkvoelker: understood16:33
garlofftough one -- but we will need to somehow find a handle -- I perceive heat as relevant in customer discussions16:34
markvoelkerWe can and should test some of the heat API's if we add them to a guideline or create a program for them...but that alone is likely insufficient to be very useful.16:34
*** mickeys has joined #openstack-meeting-316:35
eglutestarting with discovery apis would be good. if i remember correctly, thats what we discussed with the heat team in barcelona16:35
garloffmarkvoelker: or we push this to the interop challenge WG?16:35
* eglute goes looking for a time machine16:35
markvoelkereglute: if we want to talk to the heat folks at the PTG, I'd suggest we do it in their meeting room (since we're splitting ours 3 ways) or in the hallway/coffee shop track16:35
*** rhochmuth has quit IRC16:35
eglutei agree16:35
markvoelkerThat said, I'm going to have to depart Wednesday evening due to another obligation. =)  But I think we're mostly just checking in here.16:35
*** neiljerram has joined #openstack-meeting-316:36
eglutehere are some short notes on heat: https://etherpad.openstack.org/p/DefCoreBarcelona16:36
egluteyeah, just checking in to see if they made progress on gabbi stuff16:36
eglutegabbi patch is being updated, so they are working on it16:37
*** catherineD has joined #openstack-meeting-316:37
eglutehttps://review.openstack.org/#/c/348076/16:37
markvoelkerOK, anything else on PTG stuff?16:38
* catherineD sorry my internet on the bus is not good ..16:38
eglutesame with ceilometer- need to get a status of where they are at with their apis16:39
* catherineD now in the office16:39
catherineDabout the Heat subject ...16:39
*** andreas_s has quit IRC16:39
catherineDif we think that for Heat it is the resources that is important .. does it make sense to include Heat in DefCore?16:39
*** mickeys has quit IRC16:40
*** reedip_outofmemo has joined #openstack-meeting-316:40
eglutewhat do you mean catherineD? as a capability?16:41
hogepodgeIt would me nice to have a way to indicate a cloud has an interoperable heat16:41
catherineDeglute: yes ..16:41
*** zhipeng has joined #openstack-meeting-316:41
hogepodgeit's becoming a more reliable and important project16:41
garloffcatherineD: If DefCore is about InterOp, then using heat templates from one cloud in another one is a valid expectation, no?16:41
RockygWhat would be great would be a hot validator that all could use  ;)16:42
hogepodges/me/be16:42
catherineDhogepodge:If I remember correctly (we need to confirm again) ... the Heat tean thinks of resources as "content" not API16:42
catherineDI think Heat is a good subject for PTG discussion about must pass tests ... should they be Heat API or resources16:43
hogepodgecatherineD: yeah, you've definitely done most of the work there and have a better understanding of their pov than I do16:43
garloffcatherineD: it's all about the payload (the .yaml) ...16:43
*** kzaitsev_mb has quit IRC16:43
markvoelkerRight, I think the idea here is that (assuming heat meets criteria) we still may want to include it in Guidelines at some point (this might say "if the cloud has a Powered logo, you know it has a heat API and you can push stacks to it").  But API's alone may not be sufficient, and heat's a bit unique in that regard.16:44
hogepodgein some ways, passing other capabilities should help guarantee the minimum available for heat templates16:44
catherineDgarloff: the discussion is about the API that execute the template or the template itself16:44
eglutecatherineD are you going to be in atlanta?16:44
hogepodgeso just having the heat api tested and working along with the other project apis could be sufficient16:44
*** CatherineD1 has quit IRC16:44
*** zhipeng has quit IRC16:44
catherineDeglute: I am waiting for travel approval ... will put my name in as soon as I get it16:44
markvoelkerI don't think it's a question of either we focus on the templates or we focus on the API.  It's an "and".16:44
catherineDhogepodge: yea that is what the Heat team's direction ..16:45
eglutecatherineD ok!16:45
eglutecould someone reach out to heat team and setup a time for us to meet?16:45
garloffcatherineD: the heat API is trivial while the template definition/content is not, yes16:45
catherineDgarloff: absolutely16:46
catherineDI do not think we should and can spec content in general16:46
gemagarloff: isn't the template definition the entry parameter of the API?16:46
*** neiljerram has quit IRC16:47
gemaor the template, rather, once defined16:47
hogepodgeI can schedule a meeting with heat team at ptg16:47
garloffgema: sure, you submit the template via API and then expect the platform to do a lot of complex stuff ;-)16:47
gemagarloff: fair enough, we just need to make sure that for certain template configurations, heat behaves the same in all the different clous16:48
gemaclouds16:48
gemaso the end user can expect the same16:48
*** shamail has quit IRC16:48
*** bobmel_ has joined #openstack-meeting-316:48
* markvoelker glances at the clock and suggests we move on and discuss more in ATL16:48
gemasorry :)16:48
gemayep yep16:49
garloffgema: Challenges I see are that (a) one typical heat template would test many many different things in one test and (b) we need to measure with probably many tests that what we asked heat to do was successful16:49
markvoelkerNono, good discussion, we're just down to 10 minutes. =)16:49
catherineDsorry to bring the Heat subject back .. but agree with markvoelker: that it should be a subject at PTG16:49
markvoelker#topic User survey16:49
*** openstack changes topic to "User survey (Meeting topic: interopwg)"16:49
eglutecatherineD could you please reach out to Heat team and setup a time for us to meet wit hthem?16:49
markvoelker(skipped the name change topic just briefly since I think this is quick)16:50
catherineDeglute:  hogepodge: just indeicates that he will do so ..16:50
markvoelkereglute: would you like to fill folks in on the outcome of the user survey question discussion?16:50
hogepodge#action hogepodge set up meeting with heat team at ptg16:50
egluteoh i missed it thanks!!!16:50
egluteYes, user survey: looks like we are getting TWO questions!16:51
*** bobmel has quit IRC16:51
eglutelet me find the link to questions16:51
eglutecant find the etherpad right now, but this is what we submitted:16:53
eglute1.) (short answer format)  Do you use the OpenStack Powered program or Interoperability Guideline compliance as a factor in your OpenStack procurement process?  Why or why not?16:53
egluteas first question16:53
egluteand second one that will most likely also be included:16:53
hogepodge#link https://etherpad.openstack.org/p/interopwg_user_survey_question16:53
eglute2.) (multiple choice, select all that apply) What do you consider to be the biggest challenges to achieving interoperability between OpenStack clouds?16:53
eglutelet me know if you would like me to paste all the answers to the second question16:54
gemareading on the etherpad16:54
eglutehttps://etherpad.openstack.org/p/interopwg_user_survey_question16:55
egluteoh thanks hogepodge16:55
eglutei was too slow16:55
*** ocartier_ has quit IRC16:56
eglutehopefully answers to these will help us out going forward16:56
gemasounds good indeed16:56
egluteand i am looking at the survey that is being built, and i see both questions there16:57
eglutethere is a refstack question there as well:16:57
eglute"I'm interested in helping our interoperability testing efforts by checking my cloud capabilities with RefStack."16:58
hogepodgetwo minutes, anything else?16:58
catherineDthe question list on https://etherpad.openstack.org/p/interopwg_user_survey_question looks good ..16:58
*** neiljerram has joined #openstack-meeting-316:59
markvoelkerJust FYI, a couple of those last 2017.01 patches will need rebasing16:59
eglutethanks catherineD, we went only with the first 216:59
eglutemarkvoelker ok!16:59
markvoelkerAnd with that, we've run out the clock.  Thanks folks!17:00
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
catherineDeglute: because we can only submit 2 questions?17:00
openstackMeeting ended Wed Jan 11 17:00:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
eglutethey were all clean merges?17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-11-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-11-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-11-16.01.log.html17:00
*** mickeys has joined #openstack-meeting-317:01
*** catherineD has left #openstack-meeting-317:01
*** matrohon_ has quit IRC17:03
*** rhochmuth has joined #openstack-meeting-317:04
*** ricardoas has left #openstack-meeting-317:07
*** Sukhdev has quit IRC17:08
*** briancurtin has quit IRC17:11
*** pcaruana has quit IRC17:12
*** rmart04 has quit IRC17:13
*** wxy has quit IRC17:14
*** Swami_ has quit IRC17:14
*** ocartier has joined #openstack-meeting-317:16
*** stevejims has quit IRC17:17
*** sdake_ has joined #openstack-meeting-317:22
*** bobmel_ has quit IRC17:22
*** bobmel has joined #openstack-meeting-317:24
*** jobrs has quit IRC17:25
*** iyamahat has quit IRC17:25
*** sdake has quit IRC17:25
*** yamahata has quit IRC17:25
*** bobmel has quit IRC17:27
*** bobmel has joined #openstack-meeting-317:27
*** bobmel has quit IRC17:28
*** davidsha has left #openstack-meeting-317:29
*** bobmel has joined #openstack-meeting-317:31
*** baoli has joined #openstack-meeting-317:36
*** lpetrut has quit IRC17:38
*** caboucha has quit IRC17:50
*** rossella_ has quit IRC17:52
*** iyamahat has joined #openstack-meeting-317:53
*** aarefiev is now known as aarefiev_afk17:54
*** yamahata has joined #openstack-meeting-317:54
*** Swami has joined #openstack-meeting-317:54
*** ociuhandu has quit IRC18:01
*** ralonsoh has quit IRC18:03
*** galstrom is now known as galstrom_zzz18:04
*** bobmel_ has joined #openstack-meeting-318:08
*** galstrom_zzz is now known as galstrom18:10
*** reedip_outofmemo has quit IRC18:11
*** bobmel has quit IRC18:12
*** tonytan4ever has joined #openstack-meeting-318:12
*** claudiub|2 has joined #openstack-meeting-318:15
*** david-lyle has joined #openstack-meeting-318:15
*** david-lyle has quit IRC18:16
*** david-lyle has joined #openstack-meeting-318:16
*** claudiub has quit IRC18:19
*** sambetts is now known as sambetts|afk18:19
*** reedip_outofmemo has joined #openstack-meeting-318:27
*** rbak has quit IRC18:29
*** ianychoi has quit IRC18:30
*** lpetrut has joined #openstack-meeting-318:31
*** amotoki has quit IRC18:32
*** absubram has quit IRC18:36
*** rossella_ has joined #openstack-meeting-318:38
*** absubram has joined #openstack-meeting-318:39
*** raj_singh_ has quit IRC18:41
*** s3wong has joined #openstack-meeting-318:42
*** rbak has joined #openstack-meeting-318:43
*** jjung has left #openstack-meeting-318:45
*** ociuhandu has joined #openstack-meeting-318:45
*** Rockyg has quit IRC18:51
*** lpetrut has quit IRC18:55
*** abalutoiu has joined #openstack-meeting-318:58
*** reedip_outofmemo has quit IRC19:02
*** mtanino has joined #openstack-meeting-319:02
*** ocartier_ has joined #openstack-meeting-319:04
*** ocartier_ has quit IRC19:04
*** VW has quit IRC19:04
*** ocartier_ has joined #openstack-meeting-319:05
*** ocartier has quit IRC19:06
*** spzala has quit IRC19:07
*** spzala has joined #openstack-meeting-319:07
*** briancurtin has joined #openstack-meeting-319:09
*** spzala has quit IRC19:12
*** wxy has joined #openstack-meeting-319:12
*** kzaitsev_mb has joined #openstack-meeting-319:15
*** rossella_ has quit IRC19:15
*** rossella_ has joined #openstack-meeting-319:19
*** pvaneck has joined #openstack-meeting-319:30
*** s3wong has quit IRC19:32
*** amotoki has joined #openstack-meeting-319:32
*** krtaylor has quit IRC19:37
*** ocartier_ has quit IRC19:37
*** VW has joined #openstack-meeting-319:37
*** ocartier has joined #openstack-meeting-319:38
*** rdopiera has joined #openstack-meeting-319:41
*** ocartier has quit IRC19:45
*** salv-orl_ has quit IRC19:45
*** revon has joined #openstack-meeting-319:45
*** ankur-gupta-f has joined #openstack-meeting-319:50
*** r1chardj0n3s has joined #openstack-meeting-319:51
*** ocartier has joined #openstack-meeting-319:54
*** viks has joined #openstack-meeting-319:56
*** lucas__ has joined #openstack-meeting-319:57
*** VW has quit IRC19:58
r1chardj0n3shm20:00
vikshi20:00
r1chardj0n3s#startmeeting horizon20:00
openstackMeeting started Wed Jan 11 20:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. 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
r1chardj0n3sgood morning :-)20:00
viksgood morning20:00
*** VW has joined #openstack-meeting-320:01
david-lyleo/20:01
rdopierao/20:01
rhagartyo/20:01
ankur-gupta-f\o/20:01
r1chardj0n3sthanks folks for coming along, I'll get through some procedural stuff first20:02
r1chardj0n3s#topic Ocata Feature Freeze next week20:02
*** openstack changes topic to "Ocata Feature Freeze next week (Meeting topic: horizon)"20:02
*** TravT has joined #openstack-meeting-320:02
r1chardj0n3s#link https://releases.openstack.org/ocata/schedule.html20:02
TravTo/20:02
betherlyo/20:02
r1chardj0n3sAs per the Ocala schedule, we will be going into feature freeze next week. We freeze a week before other projects to give plugin authors a chance to respond to changes in our release.20:02
r1chardj0n3sOnce Ocata-3 has been tagged, we will only be accepting release-critical bug fix patches unless you receive a feature freeze exception (FFE). We will also try to reduce the amount of string changes to give the translation team time to complete translation.20:02
TravTyeah, we just made some adjustments to the searchlight-ui plugin20:03
*** clu_ has joined #openstack-meeting-320:03
betherlyr1chardj0n3s: I'm currently working on the qos panel. Will that be under the feature freeze or under the same leeway as the plugins?20:03
r1chardj0n3sbetherly: plugins still freeze a week later20:03
*** deshipu has joined #openstack-meeting-320:04
betherlyr1chardj0n3s: yep. Just checking when the hard deadline is for it to try and get in. Not sure it will make this release either way though tbh...20:04
*** tsufiev has joined #openstack-meeting-320:05
r1chardj0n3sand the qos panel isn't under the Horizon project, so I have no control over FFE there :-)20:05
tsufievo/20:05
deshipur1chardj0n3s: I thought it's in the horizon repo?20:05
* deshipu <-- rdopiera, sorry, my work server just went down20:07
*** sdake_ is now known as sdake20:07
r1chardj0n3soh, it's a new panel in Horizon? right, sorry for my confusion20:08
r1chardj0n3sso yeah, that freezes with the rest of Horizon20:08
ankur-gupta-fr1chardj0n3s: would the lbaas-dash fall under the restriction?20:08
david-lylebecause it effects plugins?20:08
david-lyle:-D20:09
r1chardj0n3sankur-gupta-f: plugins still go into feature freeze at the time of the rest of OpenStack, a week after Horizon does20:10
ankur-gupta-fokay thanks20:10
betherlyr1chardj0n3s: thanks :)20:11
r1chardj0n3sReview rate is still very low, but if you are reviewing then I'll remind you that the priorities for this release are:20:11
r1chardj0n3s#link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open20:11
r1chardj0n3splease consider focusing your efforts there, thanks :-)20:11
david-lylelet's add K2K support?20:12
r1chardj0n3sdavid-lyle: the DOA patch https://review.openstack.org/#/c/415521/ ?20:12
r1chardj0n3soh, and the rest20:13
david-lylehttps://review.openstack.org/40845020:13
david-lyleis the horizon piece20:13
r1chardj0n3syup, so I see four patches related to that bp20:14
david-lyleI'm about ready to push the refactor, then tackle reviewing the d-o-a side20:14
david-lylewe'll need to release d-o-a20:14
r1chardj0n3ser, three20:14
r1chardj0n3sI can't count20:14
david-lyleand do the requirements dance20:14
r1chardj0n3sthat's gonna end up in FFE land :-)20:14
r1chardj0n3sbut I think it's justifiable with minimal plugin impact20:14
r1chardj0n3sI've added the three patches to the priority list20:15
*** spzala_ has joined #openstack-meeting-320:15
r1chardj0n3swhich shall be known as the list that grows, and never shrinks :-P20:15
david-lyleif that breaks a plugin, someone is doing something wrong :)20:15
r1chardj0n3sIt's a good thing that people never do anything wrong :P20:16
*** jlopezgu has joined #openstack-meeting-320:16
r1chardj0n3sok, moving on20:16
r1chardj0n3s#topic Pike PTG planning20:16
*** clu_ has quit IRC20:16
*** openstack changes topic to "Pike PTG planning (Meeting topic: horizon)"20:16
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-ptg-pike20:16
r1chardj0n3sI've put together a start at an etherpad. If you're going to the PTG, which is just over a month away now, then please add topics of discussion to that etherpad. It'd be handy to know who's actually going too.20:17
r1chardj0n3sI don't have confirmation of attendance at this time.20:17
david-lyler1chardj0n3s: I just added that to https://wiki.openstack.org/wiki/PTG/Pike/Etherpads20:18
r1chardj0n3sthanks david-lyle20:18
*** clu_ has joined #openstack-meeting-320:18
david-lylewhere do you want attendance info?20:19
david-lylehere or etherpad?20:19
r1chardj0n3sthe etherpad would be more convenient I reckon20:19
david-lyleI added the folks I know of20:20
r1chardj0n3scheers20:20
*** spzala_ has quit IRC20:20
r1chardj0n3s#topic BP: Snapshot listing per volume20:20
*** openstack changes topic to "BP: Snapshot listing per volume (Meeting topic: horizon)"20:20
r1chardj0n3s#link https://blueprints.launchpad.net/horizon/+spec/snapshot-listing-per-volume20:20
vikshi20:20
r1chardj0n3shai20:20
viksI have put up the BP20:21
r1chardj0n3sI've added a comment to the BP whiteboard, you might not have seen it yet20:21
viksok20:21
*** spzala has joined #openstack-meeting-320:21
viksI will update the blue print20:22
viksbut in case of systems which have large number of volume snapshts20:22
david-lyleyou could even provide a link from volumes to the filtered view20:22
r1chardj0n3sthat was my thought20:22
viksit becomes very difficult20:22
viksok20:23
viksbut having a page makes it upfront usable20:23
*** mpotdar has joined #openstack-meeting-320:23
david-lyleis this a view off the volume itself?20:23
viksaslo we have scheduled snapshots20:23
david-lylelike in the volume details?20:24
viksso it becomes very difficult to locate snapshots becase names are real long string20:24
viksso volume based page helps20:24
viksyes20:24
viksyes david20:24
david-lyleso a tab on the volume details page20:25
viksit is another tab next to volume details/overview20:25
david-lyleI could see that20:25
r1chardj0n3syeah, that makes sense20:25
*** lucas__ has quit IRC20:25
viksso IMO I can implment it the older way first20:26
viksthen I can try for complete angular way20:26
viksI thin I can do it for Ocata...20:26
r1chardj0n3swe only have 1 week to get Ocata patches in, there's no way it'll get reviewed in time I'm afraid20:27
ediardo:(20:27
viksLet me try non angular way of tabtable in this release20:28
*** lucas__ has joined #openstack-meeting-320:28
r1chardj0n3sok20:28
viksI will put up angular in next release20:28
r1chardj0n3syup20:28
viksI think I can get it in :)20:28
r1chardj0n3sthe non-angular approach should be less work20:28
viksyes richard20:28
viksshould I start the omplentation20:29
r1chardj0n3swith some small changes to the BP for clarity I think it's worth having, so I'll approve it20:29
viksi guess I will need approval for check-in and reviews20:30
viksgr820:30
viks:)20:30
viksI will update the BP20:30
viksand start putting up the code asap20:30
r1chardj0n3s#topic Open Discussion20:31
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:31
r1chardj0n3sdoes anyone have anything else they'd like to bring up?20:31
deshipuI do20:31
r1chardj0n3sgo for it :-)20:31
jlopezgur1chardj0n3s: I'll update the keystone patches this week, sorry I've been busy with another project20:31
*** lucas__ has quit IRC20:31
deshipuI have a patch up that fixes the VersionManager to make it possible to distinguish between version 4.2 and version 4.2020:31
r1chardj0n3sjlopezgu: +120:32
deshipuI just realized that without this patch the simple-tenant-pagination patch will be impossible to use, because the pagination only works with nova api versions above 4.2020:32
r1chardj0n3sI see rdopiera's patch https://review.openstack.org/#/c/410688/ ?20:32
TravTr1chardj0n3s question on the tox usage with plugins.20:32
deshipuand we currently can't configure Horizon to use that version20:33
r1chardj0n3sdeshipu: is that the patch you're referring to?20:33
deshipur1chardj0n3s: thank you, sorry, I'm on my private laptop20:33
deshipur1chardj0n3s: yes20:33
deshiputhe issue is that we are using floats for the versions20:34
david-lyler1chardj0n3s: deshipu = rdoperia20:34
r1chardj0n3sright, I had reviewed that and need to follow up on rdopiera's revision, yep20:34
deshipuand 4.2 and 4.20 are the same floats20:34
r1chardj0n3swhaaaaa???20:34
r1chardj0n3sthat's crazy!!20:34
r1chardj0n3sright, now that rdopiera==deshipu things make more sense :-D20:34
david-lylehaha20:35
deshiputhe way I did it in this patch, I'm making a magical Version object that behaves like floats, but hase semantic_version inside20:35
r1chardj0n3sthe patch itself made sense, I just had that issue with reimplementing semantic_version20:35
deshiputhis way I don't have modify all the code in Horizon20:35
r1chardj0n3snow that's fixed, it should be fine20:35
*** tsufiev has left #openstack-meeting-320:35
r1chardj0n3sI'll review it today20:35
deshipuhowever, I wonder if it would be cleaner in the long term to actually modify all the code in Horizon to use semantic_version directly20:35
deshipubut that is a considerably higher risk change20:35
*** sdake has quit IRC20:35
deshipuwe probably don't want it just before a freeze?20:36
r1chardj0n3syeah20:36
david-lylemicroversions just keep on giving20:36
deshiputhis is not caused by microversions directly20:36
r1chardj0n3sdeshipu: if it turns out to be broken or just plain bad we have enough time to fix/remove it20:37
deshipuwe would hit that as soon as we reach 4.1020:37
*** lucas__ has joined #openstack-meeting-320:37
*** sdake has joined #openstack-meeting-320:37
deshipuwhich is feasible without microversions20:37
* david-lyle has to look closer20:37
*** krtaylor has joined #openstack-meeting-320:38
r1chardj0n3sOK, one last thing: I'm at a conference next week. I'll still be around but won't be able to run the weekly meeting. Rob has said he'll be able to run it though, so yay Rob!!20:39
*** kzaitsev_mb has quit IRC20:40
deshipuenjoy the trip20:40
* david-lyle is jealous20:40
viksone more thing from my side...https://review.openstack.org/#/c/372150/20:40
jlopezguhahaaha20:40
viksi dont know if this is the correct forum20:40
jlopezguwhy jelous david-lyle if you're coming to SA next week?20:40
viksbut we can close this20:40
TravTr1chardj0n3s: where is the conference?20:40
david-lyleTazmania vs San Antonio, I'm not sure jlopezgu20:41
jlopezgujealous*20:41
david-lyle;)20:41
jlopezguhahahahaha20:41
r1chardj0n3sTravT: is in Hobart, which will be 10ºC cooler than Melbourne (we're due for ~40ºC over a couple of days)20:41
*** sdake has quit IRC20:41
deshipuviks: it looks like it's already abandoned?20:41
jlopezguIt should be cool to visit Tazmania20:41
TravTsounds like fun!20:41
clu_O_O20:41
jlopezguyou should also come soon r1chardj0n3s20:42
viksi mean let us close the big...it still shows in progress20:42
viksbug*20:42
r1chardj0n3sviks: I just looked, that patch is superseded by https://review.openstack.org/#/c/335020/ which is merged, yes?20:42
r1chardj0n3sahhhh20:42
r1chardj0n3sI understand, sorry viks20:42
r1chardj0n3sthe replacement patch didn't reference the bug :/20:43
r1chardj0n3ssince the bug was a wishlist item, we can just close it20:43
viksok20:44
viksthanks20:44
r1chardj0n3sthx david-lyle20:44
david-lylenp20:44
r1chardj0n3salso20:45
r1chardj0n3s"Tazmania"20:45
r1chardj0n3sreally, david-lyle? :-P20:45
david-lylewhat can't I spell20:45
david-lyleIn 'merica we like 'z's20:45
r1chardj0n3syou do like your zeees20:45
david-lylejust sprinkle liberally20:46
clu_zavid-zyle20:46
david-lyleexacltly20:46
jlopezguLOL20:46
r1chardj0n3somg a wild clu_ appears!20:46
r1chardj0n3s#endmeeting20:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:46
openstackMeeting ended Wed Jan 11 20:46:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-11-20.00.html20:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-11-20.00.txt20:46
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-11-20.00.log.html20:46
*** viks has left #openstack-meeting-320:47
*** deshipu has left #openstack-meeting-320:48
*** sdake has joined #openstack-meeting-320:49
*** r1chardj0n3s has left #openstack-meeting-320:51
*** TravT has quit IRC20:53
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Jan 11 21:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
dansmithanyone around?21:00
*** tonytan4ever has quit IRC21:00
*** mriedem has joined #openstack-meeting-321:00
mriedemo/////21:01
*** dtp_ has joined #openstack-meeting-321:01
dtp_o/21:01
dansmithcoffee + sudafed = energy21:01
mriedemi am...becoming21:01
*** tonytan4ever has joined #openstack-meeting-321:01
dansmithhehe21:01
dansmith#topic cells testing/bugs21:01
*** openstack changes topic to "cells testing/bugs (Meeting topic: nova_cells)"21:01
dansmithso, this has been unfun for me for a couple weeks,21:02
*** dtp_ is now known as dtp21:02
dansmithgetting the cellsv1 job to be happy with having cellsv2 mappings in place21:02
dansmithI've come to realize that we're just short-circuiting too much cellsv1 replication by allowing the api to go direct to the cells and have the replication going on,21:02
dansmithso I've got a patch up that disables those shortcuts for cellsv1 deploys21:03
dansmithhttps://review.openstack.org/#/c/418141/21:03
dansmithit's about to go green I think21:03
dansmithand I will start getting the patches above it back into happy state so we can hopefully get on with things21:03
dansmithat some point cellsv1 people will do a cutover, which will likely just be larger than I was hoping, but still pretty easy I think21:04
dansmithand at least it will be reversible if they cut, find issues, they can cut back without much fuss21:04
dansmithanything else on cells testing/bugs?21:04
dansmith#topic open reviews21:05
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:05
*** rossella_ has quit IRC21:05
dansmithso I've got open reviews, linked from the above one that has to go first21:05
bauzas\o (late)21:05
dansmithdtp: you've still got yours open I presume, which I haven't gotten back to yet21:05
dansmithdtp: is it ready to go?21:05
dtpready for round two, yep21:05
dansmithcool21:05
dansmithanything else on open reviews?21:06
dansmithI think melwitt is looking for review on her quota patches, but I haven't been over those yet21:06
dansmithanyone looking to help could definitely review those to help keep that moving21:07
melwittoops, yes. I got the first two out of WIP by adding all the tests21:07
*** dimtruck is now known as zz_dimtruck21:07
dansmithcool21:08
*** jlopezgu has left #openstack-meeting-321:08
dtpis there any value in me reviewing things?  i'd be lying if i said i had a total grasp of the system at this point21:08
melwittstill working on tests on the third. but it can still be reviewed for the approach, if anyone has issues let me know asap21:08
dansmithdtp: of course21:08
mriedemmelwitt: the patches to move quotas to the api db right?21:09
mriedemor counting21:09
mriedem?21:09
dansmithboth?21:09
mriedemi haven't looked at either yet21:09
melwittmriedem: the first two move quotas, the third does the counting resources thing. all three are needed together, that is, if we can't get the counting in, we shouldn't move things to the api db yet since we are omitting reservations and usages tables21:09
*** rbak has quit IRC21:10
mriedemok21:10
mriedemhmm, wonder if we should -2 the bottom change then21:10
melwittthat might be safest, as long as people know to still review it21:10
mriedemyeah...even w/o i don't know who is going to review it right now21:11
mriedemi mean the people in this meeting yeah21:11
mriedemdan is out next week though, and i'm out the week after next, which is also the week of FF21:11
mriedemso i'll probably need to start kicking some people21:11
dansmithmaybe we could get sdague to look21:12
mriedemyeah maybe21:12
melwittyeah. it's gotten no action so far and they've been there for awhile, at least as WIP for lacking tests21:12
mriedemor i can just be super passive aggressive midwesterner in the ML and channel21:12
dansmithheh21:12
mriedemmelwitt: maybe it's trying too hard?21:12
melwittyeah, probably21:12
* mriedem is making a joke about getting action21:13
dansmithhah21:13
melwitthaha, I know21:13
mriedemoh ok21:13
bauzasmriedem: which change are we discussing to review ?21:13
dansmithanyway, anything else about open reviews?21:13
bauzasthe quota ones ?21:13
mriedemgod if godaddy were newer than liberty dtp could test this all out in preprod21:13
dansmithbauzas: see the priorities etherpad21:13
mriedembauzas: yes21:13
bauzasokay21:14
melwittI think you're right, quotas patches are trying too hard21:14
dtpspeaking of that21:14
dtpwhat would we need to have something useful re testbed?21:14
dansmithlet's move on to...21:14
dansmith#topic open discussion21:14
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:14
mriedemdtp: i suspect you guys will be the canaries for the cells v1 upgrade21:14
dtpi hope so21:15
dansmithyou might regret tat,21:15
dansmithbut super glad to hear you say it :)21:15
melwittI can't remember what version CERN and Nectar are on21:15
mriedemklindgren and mdorman said it was totally cool...21:15
dtp:) we have cells v1 problems...helping cells v2 will make us feel good21:15
dansmithdtp: and you're a cellsv2 developer now, so if it doesn't do what you want, you have only yourself to blame :)21:16
dtpso true!21:16
* dansmith takes a screenshot ... for later21:17
dansmithokay, so I have one thing for open discussion21:17
dansmithI'm going to be in the wilderness this time next week,21:17
dansmithso someone needs to run this meeting or we need to cancel it21:17
dansmithif nobody volunteers, then we cancel21:18
dansmithsounds like cancel21:18
dansmithlet it be known henceforth21:18
dansmithanything else for open discussion?21:18
dansmithanyone?21:19
dansmithbueller?21:19
dansmithsomeone say "nothing from me"21:19
dtpi'm good21:19
dansmithokay then21:20
dansmith#endmeeting21:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:20
openstackMeeting ended Wed Jan 11 21:20:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-11-21.00.html21:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-11-21.00.txt21:20
bauzas:)21:20
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-11-21.00.log.html21:20
*** diablo_rojo_phon has quit IRC21:20
*** rbak has joined #openstack-meeting-321:20
*** dtp has left #openstack-meeting-321:20
*** lucas__ is now known as lucasxu21:24
*** salv-orlando has joined #openstack-meeting-321:25
*** zz_dimtruck is now known as dimtruck21:27
*** lpetrut has joined #openstack-meeting-321:33
*** rtheis has quit IRC21:38
*** lpetrut has quit IRC21:38
*** abalutoiu has quit IRC21:41
*** srobert_ has joined #openstack-meeting-321:49
*** cleong has quit IRC21:49
*** tonytan4ever has quit IRC21:51
*** srobert has quit IRC21:51
*** lucasxu has quit IRC21:52
*** krtaylor has quit IRC21:54
*** lucas__ has joined #openstack-meeting-321:54
*** MarkBaker has joined #openstack-meeting-321:54
*** VW has quit IRC21:59
*** sdake has quit IRC22:03
*** sdake has joined #openstack-meeting-322:04
*** spzala has quit IRC22:09
*** VW has joined #openstack-meeting-322:11
*** MarkBaker has quit IRC22:12
*** lblanchard has quit IRC22:13
*** spzala has joined #openstack-meeting-322:16
*** sdake has quit IRC22:16
*** lucas__ has quit IRC22:18
*** spzala has quit IRC22:20
*** salv-orl_ has joined #openstack-meeting-322:22
*** s3wong has joined #openstack-meeting-322:24
*** salv-orlando has quit IRC22:26
*** spzala has joined #openstack-meeting-322:28
*** spzala has quit IRC22:28
*** markvoelker has quit IRC22:29
*** baoli has quit IRC22:30
*** srobert_ has quit IRC22:30
*** markvoelker has joined #openstack-meeting-322:32
*** markvoelker has quit IRC22:34
*** markvoelker has joined #openstack-meeting-322:34
*** markvoelker_ has joined #openstack-meeting-322:39
*** markvoelker has quit IRC22:39
*** VW has quit IRC22:39
*** kberger has joined #openstack-meeting-322:41
*** mriedem has left #openstack-meeting-322:41
*** marst has quit IRC22:44
*** VW has joined #openstack-meeting-322:44
*** julim has quit IRC22:49
*** Swami has quit IRC22:56
*** VW has quit IRC22:58
*** spzala has joined #openstack-meeting-323:01
*** krtaylor has joined #openstack-meeting-323:02
*** bobmel_ has quit IRC23:02
*** spzala has quit IRC23:09
*** spzala has joined #openstack-meeting-323:09
*** kzaitsev_mb has joined #openstack-meeting-323:13
*** VW has joined #openstack-meeting-323:16
*** claudiub|2 has quit IRC23:16
*** spzala has quit IRC23:18
*** VW has quit IRC23:20
*** sdake has joined #openstack-meeting-323:21
*** revon has quit IRC23:23
*** tellesnobrega has quit IRC23:23
*** galstrom is now known as galstrom_zzz23:30
*** sdake_ has joined #openstack-meeting-323:30
*** sdake has quit IRC23:31
*** markvoelker_ has quit IRC23:32
*** VW has joined #openstack-meeting-323:35
*** sdake has joined #openstack-meeting-323:37
*** sdake_ has quit IRC23:38
*** VW has quit IRC23:40
*** markvoelker has joined #openstack-meeting-323:40
*** dimtruck is now known as zz_dimtruck23:47
*** salv-orl_ has quit IRC23:52
*** rhochmuth has quit IRC23:54
*** sdake_ has joined #openstack-meeting-323:55
*** sdake has quit IRC23:56
*** pvaneck has quit IRC23:58
*** pvaneck has joined #openstack-meeting-323:58
*** rbak has quit IRC23:59

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