Wednesday, 2016-12-07

*** zz_dimtruck is now known as dimtruck00:04
*** donghao has quit IRC00:04
*** aweeks has quit IRC00:06
*** baoli has quit IRC00:07
*** Patifa has quit IRC00:12
*** MeganR has joined #openstack-meeting-300:13
*** haleyb_ has joined #openstack-meeting-300:29
*** haleyb_ has quit IRC00:34
*** kenji-i_ has joined #openstack-meeting-300:34
*** kenji-i has quit IRC00:34
*** mtanino has quit IRC00:39
*** MeganR has quit IRC00:43
*** sdake has joined #openstack-meeting-300:45
*** mariannelm has joined #openstack-meeting-300:48
*** mariannelm has quit IRC00:50
*** mariannelm has joined #openstack-meeting-300:51
*** tuanluong has joined #openstack-meeting-300:51
*** tovin07 has joined #openstack-meeting-300:52
*** bpokorny has quit IRC00:59
*** bpokorny has joined #openstack-meeting-301:00
*** VW has joined #openstack-meeting-301:03
*** bpokorny_ has joined #openstack-meeting-301:04
*** bpokorny has quit IRC01:06
*** julim has joined #openstack-meeting-301:06
*** huanxuan has joined #openstack-meeting-301:13
*** sdake has quit IRC01:14
*** zhurong has joined #openstack-meeting-301:14
*** revon has quit IRC01:22
*** lblanchard has joined #openstack-meeting-301:24
*** zhurong has quit IRC01:25
*** zhurong has joined #openstack-meeting-301:26
*** haleyb_ has joined #openstack-meeting-301:29
*** david-lyle has joined #openstack-meeting-301:33
*** VW has quit IRC01:33
*** zhurong has quit IRC01:34
*** julim has quit IRC01:34
*** zhurong has joined #openstack-meeting-301:35
*** haleyb_ has quit IRC01:35
*** stanzgy has joined #openstack-meeting-301:41
*** pvaneck has quit IRC01:42
*** yamamot__ has joined #openstack-meeting-301:54
*** Sukhdev has quit IRC01:54
*** bpokorny has joined #openstack-meeting-301:56
*** stanzgy has quit IRC01:56
*** stanzgy has joined #openstack-meeting-301:58
*** bpokorny_ has quit IRC01:59
*** bpokorny has quit IRC02:01
*** shu-mutou-AWAY is now known as shu-mutou02:01
*** sdake has joined #openstack-meeting-302:01
*** baoli has joined #openstack-meeting-302:12
*** reedip has quit IRC02:13
*** baoli has quit IRC02:17
*** reedip has joined #openstack-meeting-302:24
*** hogepodge has quit IRC02:38
*** sdake has quit IRC02:47
*** sankarshan_away is now known as sankarshan02:54
*** s3wong has quit IRC03:01
*** yamamot__ has quit IRC03:17
*** yamamot__ has joined #openstack-meeting-303:18
*** prateek has joined #openstack-meeting-303:22
*** lblanchard has quit IRC03:25
*** mariannelm has quit IRC03:30
*** prateek has quit IRC03:32
*** VW has joined #openstack-meeting-303:33
*** VW has quit IRC03:35
*** VW has joined #openstack-meeting-303:35
*** julim has joined #openstack-meeting-303:39
*** galyna has quit IRC03:40
*** julim has quit IRC03:40
*** spzala has quit IRC03:42
*** spzala has joined #openstack-meeting-303:42
*** julim has joined #openstack-meeting-303:44
*** rajinir has quit IRC03:46
*** spzala has quit IRC03:47
*** julim_ has joined #openstack-meeting-303:51
*** julim has quit IRC03:53
*** yamamot__ has quit IRC03:55
*** tqtran has quit IRC03:58
*** spzala has joined #openstack-meeting-304:00
*** spzala has quit IRC04:00
*** reedip has quit IRC04:01
*** VW has quit IRC04:11
*** psachin has joined #openstack-meeting-304:12
*** baoli has joined #openstack-meeting-304:12
*** reedip has joined #openstack-meeting-304:14
*** armax has quit IRC04:21
*** watanabe_isao has joined #openstack-meeting-304:22
*** zhurong has quit IRC04:27
*** numans has quit IRC04:31
*** psachin has quit IRC04:32
*** yamamot__ has joined #openstack-meeting-304:39
*** huanxuan_ has joined #openstack-meeting-304:43
*** Rocky_g has quit IRC04:45
*** huanxuan_ has quit IRC04:49
*** psachin has joined #openstack-meeting-304:49
*** tqtran has joined #openstack-meeting-304:59
*** tqtran has quit IRC05:00
*** sdake has joined #openstack-meeting-305:01
*** sdake has quit IRC05:01
*** sdake has joined #openstack-meeting-305:01
*** baoli has quit IRC05:02
*** baoli has joined #openstack-meeting-305:03
*** numans has joined #openstack-meeting-305:04
*** sdake_ has joined #openstack-meeting-305:04
*** iyamahat_ has quit IRC05:07
*** baoli has quit IRC05:07
*** sdake has quit IRC05:07
*** yamahata has quit IRC05:08
*** leifz has quit IRC05:14
*** ameade_ has joined #openstack-meeting-305:14
*** zhenguo_ has joined #openstack-meeting-305:14
*** ameade has quit IRC05:14
*** natorious has quit IRC05:14
*** sindhu_ has joined #openstack-meeting-305:14
*** mgagne has quit IRC05:15
*** sballe_ has quit IRC05:15
*** spotz_zzz has quit IRC05:15
*** dimtruck has quit IRC05:15
*** zhenguo has quit IRC05:15
*** sindhu has quit IRC05:15
*** macsz_ has joined #openstack-meeting-305:15
*** xgerman_ has joined #openstack-meeting-305:15
*** zhenguo_ is now known as zhenguo05:15
*** sindhu_ is now known as sindhu05:15
*** skath has quit IRC05:15
*** SWDevAngel_ has quit IRC05:15
*** ildikov has quit IRC05:15
*** DuncanT has quit IRC05:15
*** DuncanT_ has joined #openstack-meeting-305:15
*** ildikov has joined #openstack-meeting-305:16
*** DuncanT_ is now known as DuncanT05:16
*** krtaylor has quit IRC05:16
*** betherly has quit IRC05:16
*** xgerman has quit IRC05:16
*** macsz has quit IRC05:16
*** sankarshan has quit IRC05:16
*** ameade_ is now known as ameade05:16
*** xgerman_ is now known as xgerman05:17
*** macsz_ is now known as macsz05:17
*** SWDevAngel_ has joined #openstack-meeting-305:18
*** coolsvap has joined #openstack-meeting-305:19
*** betherly has joined #openstack-meeting-305:19
*** prateek has joined #openstack-meeting-305:20
*** sankarshan has joined #openstack-meeting-305:21
*** sballe_ has joined #openstack-meeting-305:22
*** skath has joined #openstack-meeting-305:23
*** zhurong has joined #openstack-meeting-305:27
*** soichi has joined #openstack-meeting-305:27
*** krtaylor has joined #openstack-meeting-305:28
soichihi05:30
reedipgm05:30
yamamot__hi05:30
soichi#startmeeting taas05:30
openstackMeeting started Wed Dec  7 05:30:56 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:30
*** zhurong has quit IRC05:30
*** openstack changes topic to " (Meeting topic: taas)"05:30
openstackThe meeting name has been set to 'taas'05:31
*** Sukhdev has joined #openstack-meeting-305:31
*** anilvenkata has joined #openstack-meeting-305:31
reedipI just republished the OSC patch ...05:31
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:31
reedipJFYI05:31
*** zhurong has joined #openstack-meeting-305:31
*** kaz has joined #openstack-meeting-305:31
soichireedip: yes05:31
soichi#topic spec05:32
*** openstack changes topic to "spec (Meeting topic: taas)"05:32
soichi1) we should finialize the current spec05:33
yamamot__it's a reminder of spec review + some questions from dragonflow folk05:33
soichi+105:33
*** vnyyad has joined #openstack-meeting-305:33
reedipok05:34
reedipJust going through the points05:34
yamamot__first, please review the spec.05:34
yamamot__#link https://review.openstack.org/#/c/256210/05:34
yamamot__and assuming the spec is ok, now we have a possible extension to the spec05:34
yamamot__ie. "position" parameter05:35
reedipyamamot__ : the spec looks fine by me , but we need some neutron cores as well to review it05:35
yamamot__and we need some clarification about tap on tap05:35
yamamot__reedip: i don't see why. we are not neutron.05:35
reedipyamamot__ then whats stopping us from merging it :)05:36
yamamot__i don't know.05:36
yamamot__it just needs another +2 i guess05:36
reedipyou can give it +2 , right ?05:37
vnyyadi am reviewing it will push it thru today by my evening05:37
reedipunless you are the author ( I forgot )05:37
yamamot__vnyyad: thank you05:37
reedipvnyyad : great to see you here :)05:37
soichivnyyad: +105:37
vnyyadthanks :)05:37
vnyyadgreat to see you all too05:38
yamamot__vnyyad and i are authors of the spec, anil's +2 would be ideal.05:38
yamamot__is he busy these days?05:38
vnyyadyes he was05:38
vnyyadi will mail him regarding this now and see what he has to ay05:39
vnyyad*say05:39
yamamot__thank you05:40
yamamot__any of you need explanation about "position" parameter?05:40
soichiyamamot__: yes, could you explain a little bit about "position" parameter?05:41
yamamot__it was in an earlier version of the spec but reverted when we decided to concentrate to the basic functionality05:41
yamamot__and now dragonflow folks want it.05:41
yamamot__midonet wants it too.05:42
yamamot__it's an attribute for tap-flow05:42
yamamot__it controls traffic is tapped before or after SG processing05:42
soichii see05:42
vnyyadok i remember05:43
yamamot__i guess the alternative position is almost impossible to implement for the current reference implementation, where SG is implemented as a separate bridge.05:43
yamamot__so it's at this point for the benefit for vendors.05:44
soichii understood05:45
yamamot__i guess i (or probably dragonflow folk) can submit an extension spec once the current spec is merged.05:45
vnyyadok... does this need to a runtime thing so something that can be configured while setting up tas05:45
vnyyadif runtime we need the field05:46
yamamot__i'm not sure what you mean05:46
vnyyadi mean if we want to choose position differently for each tap flow setup then its more on the run time and need a parameterr05:47
vnyyadbut if we say as a config all tap tapping is done either before the sc or after the sc then it can be defined in the configuration file05:48
yamamot__which configuration file?05:48
*** hurgleburgler has quit IRC05:48
*** absubram has joined #openstack-meeting-305:49
vnyyadtaas config05:49
*** armax has joined #openstack-meeting-305:49
yamamot__you mean plugin config?05:49
yamamot__ie. neutron server config05:49
vnyyadyeah plugin config ... would that be possible or even meaning full05:50
yamamot__it's possible but i don't see any benefit.  the plugin still need to tell agents which position should be used.05:51
reedipinteresting , and considering that most users would want all their taps to be placed in a single location ( before or after SG ) but the choice of position would vary between the users05:51
*** prateek has quit IRC05:51
yamamot__and it's inconsistent among deployment from POV of api users05:51
soichii guess it depends on the position is configured or specifed by OpenStack operator or user (tenant)05:52
vnyyadyeah... ok05:52
vnyyadi agree05:52
yamamot__next topic is "tap on tap"05:53
yamamot__it's also raised by dragonflow folks05:53
yamamot__#link https://review.openstack.org/#/c/396307/  dragonflow taas spec05:53
*** oanson has joined #openstack-meeting-305:54
yamamot__a question is, what should happen if we configure mirroring from port-A to port-B, and another mirroring from port-B to port-C05:55
yamamot__port-C should see which traffic?05:55
yamamot__i listed a few choices on the wiki05:56
soichii think b) mirror all traffic on the port, including mirrored traffic05:56
soichiin case "ingree" or "both" is specied on port-B05:56
yamamot__i thought b) too, it's the reason why i implemented it in midonet that way.05:56
kazi think so, traffic on the port-A and port-B will be seen.05:57
yamamot__but i guess for some implementations it's difficult to avoid loop05:57
*** absubram has quit IRC05:57
yamamot__eg. A and B tap each other05:57
kazi see05:58
yamamot__so "a) prevent it at plugin level?" might be the safest bet05:58
oansonMaybe loop avoidance in the northbound? Throw an error when the last edge in the loop is added?05:58
yamamot__oanson: good point05:59
yamamot__for those who don't know: oanson is a dragonflow folk.05:59
*** pgadiya has joined #openstack-meeting-305:59
vnyyadoanson: +106:00
soichi+106:00
yamamot__oanson: you mean at plugin level right?06:00
oansonYes. We're working on implementing the API in Dragonflow, and this is a corner-case we were wondering how to solve06:00
oansonyamamot__, yes06:00
yamamot__i wonder how complex a loop detection will be.06:02
yamamot__if we can use CTEs it's easy, but i guess we can't.06:03
oansonWhat about cycle detection algorithms in graphs?06:03
oansonIt's O(V+E), where V is services, and E is flows (vertices and edges in the original)06:04
yamamot__yes. my concern is how to apply it to our implementation in a race-free manner.06:05
*** markvoelker has quit IRC06:05
*** markvoelker has joined #openstack-meeting-306:05
yamamot__any volunteer to design/implement the loop detection?06:06
*** prateek has joined #openstack-meeting-306:06
yamamot__and if we go the route, we need to do something for the reference implementation i guess.06:07
reedipI am still not clear , its new for me :)06:07
yamamot__which part is not clear?06:08
*** markvoelker has quit IRC06:10
*** VW has joined #openstack-meeting-306:11
yamamot__as it's merely a safety rope anyway, i guess the detection doesn't need to be strict.  eg. we can terminate if the chain is longer than X.06:12
yamamot__is this the last topic for today?06:13
soichii think the loop detection is an interesting topic, but we need more time to think it deeply.06:13
yamamot__soichi: +1 let's make it a homework for this week06:13
vnyyadsoichi: +106:14
soichiokay06:14
yamamot__#action all think about loop detection06:14
*** VW has quit IRC06:16
soichiKaz requested for Motoki-san to review TaaS GUI06:16
yamamot__can you change the topic?06:16
soichi#topic TaaS GUI06:16
*** openstack changes topic to "TaaS GUI (Meeting topic: taas)"06:16
soichiKaz requested for Motoki-san to review TaaS GUI06:16
soichiJFYI06:16
kazi sent a mail to Motoki-san and  i asked him to be a reviewer of my TaaS dashboard patch.06:16
yamamot__thank you06:17
soichi#topic Open Discusstion06:17
*** openstack changes topic to "Open Discusstion (Meeting topic: taas)"06:17
yamamot__i created newton branch06:17
soichi+1, thank you06:18
vnyyadyamamot__: thanks06:18
kaz+106:18
*** armax has quit IRC06:18
reedip+106:18
yamamot__a lesson here is the fact taas is actually used by other projects. :-)06:19
soichigreat!!06:19
vnyyadawesome!!!06:19
reedipWe need to get the Spec approved and move this to governance :D ( just my thoughts )06:19
yamamot__a reminder for reviewers: there are a few patches for the branch already.06:20
yamamot__#link https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:stable/newton newton reviews06:20
soichireedip: sure06:20
soichiyamamot__: i will check them06:21
reedipI have a question06:21
reedipthats related to deployment and packaging of TaaS06:22
reedipis there a document which highlights how TaaS should be deployed in a test env ?06:22
reedipAnd is there any current plan for packaging it ( as an RPM ) for test clouds?06:22
yamamot__i thought there is ubuntu package06:23
yamamot__i don't know which version is it though06:23
reedipreally ????06:23
reedipI didnt know that06:24
vnyyadhmmm did not know either06:24
yamamot__#link https://launchpad.net/ubuntu/yakkety/+package/python-neutron-taas06:24
reedipSo we can use it to deploy taas ??06:24
yamamot__i guess so. you can try. :-)06:25
vnyyadoh yeah it does exist :)06:25
reedipOk, let me try it then :D06:25
yamamot__they are keen to package every software i guess :-)06:26
reedipIt seems so :)06:26
yamamot__#action reedip try ubuntu package06:26
reedipGood that they are, atleast we can make something with it06:26
reedipyamamot__ I am trying to create a document which highlights TaaS06:26
reedipI mean how to use it, deploy it , et al06:27
soichireedip* +106:27
reedipI think it can be used as a reference document for everyone ( new developers/users etc ) so that they can test it out06:27
reedipand we can keep this doc in (1) Repo or in (2) Wiki06:27
vnyyadreedip: +106:28
soichiboth (1) and (2)  :)06:28
reedipsoichi : hehe . Ok I will :)06:29
kaz+106:29
yamamot__i prefer (1) as i prefer doc and code live together.06:29
yamamot__1 min left06:29
reedipwe can link the doc with the wiki06:29
reedipi am done with this point , thanks guys06:30
yamamot__thank you06:30
soichiit looks we run out of time06:30
reedip#action reedip to create a doc06:30
soichisee you next week06:30
yamamot__bye06:30
soichi#endmeeting06:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:30
openstackMeeting ended Wed Dec  7 06:30:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-07-05.30.html06:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-07-05.30.txt06:30
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-07-05.30.log.html06:30
soichibye06:30
kazbye06:30
vnyyadbye06:30
*** soichi has left #openstack-meeting-306:31
*** vnyyad has quit IRC06:31
*** kaz has quit IRC06:31
*** emagana has joined #openstack-meeting-306:32
*** sdake_ has quit IRC06:36
*** sdake has joined #openstack-meeting-306:36
*** emagana has quit IRC06:37
*** spotz_zzz has joined #openstack-meeting-306:47
*** sdake_ has joined #openstack-meeting-306:47
*** matjazp has joined #openstack-meeting-306:48
*** sdake has quit IRC06:50
*** lpetrut has joined #openstack-meeting-306:50
*** Sukhdev has quit IRC07:01
*** zhurong has quit IRC07:01
*** zhurong has joined #openstack-meeting-307:02
*** markvoelker has joined #openstack-meeting-307:06
*** sdake_ has quit IRC07:08
*** markvoelker has quit IRC07:10
*** andreas_s has joined #openstack-meeting-307:10
*** tovin07_ has joined #openstack-meeting-307:25
*** nkrinner_afk is now known as nkrinner07:30
*** kzaitsev_mb has joined #openstack-meeting-307:30
*** julim_ has quit IRC07:35
*** pcaruana has joined #openstack-meeting-307:41
*** yamahata has joined #openstack-meeting-307:41
*** sdake has joined #openstack-meeting-307:55
*** zhurong has quit IRC08:00
*** dasanind has quit IRC08:01
*** zhurong has joined #openstack-meeting-308:01
*** matjazp has quit IRC08:03
*** matjazp has joined #openstack-meeting-308:03
*** irenab has quit IRC08:04
*** irenab has joined #openstack-meeting-308:05
*** dasanind has joined #openstack-meeting-308:05
*** markvoelker has joined #openstack-meeting-308:07
*** markvoelker has quit IRC08:11
*** lpetrut has quit IRC08:17
*** irenab has quit IRC08:18
*** irenab has joined #openstack-meeting-308:18
*** jed56 has joined #openstack-meeting-308:21
*** iyamahat has joined #openstack-meeting-308:25
*** lpetrut has joined #openstack-meeting-308:27
*** julim has joined #openstack-meeting-308:35
*** Rocky_g has joined #openstack-meeting-308:36
*** kzaitsev_mb has quit IRC08:36
*** Rocky_g has quit IRC08:38
*** Rocky_g has joined #openstack-meeting-308:38
*** iyamahat has quit IRC08:39
*** Rocky__ has joined #openstack-meeting-308:39
*** Rocky__ has quit IRC08:39
*** eliqiao_ has quit IRC08:41
*** Rocky_g has quit IRC08:42
*** Rocky_g has joined #openstack-meeting-308:42
*** lpetrut has quit IRC08:46
*** Rocky_g has quit IRC08:46
*** Rocky_g has joined #openstack-meeting-308:47
*** qwebirc10966 has joined #openstack-meeting-308:47
*** stevejims has joined #openstack-meeting-308:48
*** Rocky_g has quit IRC08:48
*** mickeys has quit IRC08:49
*** Rockyg has quit IRC08:49
*** Rockyg has joined #openstack-meeting-308:50
*** qwebirc37627 has joined #openstack-meeting-308:53
*** ralonsoh has joined #openstack-meeting-308:53
*** qwebirc55394 has joined #openstack-meeting-308:53
*** MarkBaker has quit IRC08:56
*** MarkBaker has joined #openstack-meeting-308:59
*** emagana has joined #openstack-meeting-308:59
*** eliqiao has joined #openstack-meeting-309:01
*** sdake has quit IRC09:03
*** emagana has quit IRC09:04
*** markvoelker has joined #openstack-meeting-309:07
*** anilvenkata has quit IRC09:09
*** eliqiao has quit IRC09:11
*** lpetrut has joined #openstack-meeting-309:11
*** markvoelker has quit IRC09:12
*** qwebirc55394 has quit IRC09:13
*** eliqiao has joined #openstack-meeting-309:20
*** anilvenkata has joined #openstack-meeting-309:22
*** ibmko has joined #openstack-meeting-309:25
*** paul-carlton has joined #openstack-meeting-309:26
*** tobberydberg has joined #openstack-meeting-309:26
*** lpetrut has quit IRC09:28
*** lpetrut has joined #openstack-meeting-309:28
*** tobberydberg has quit IRC09:28
*** tobberydberg has joined #openstack-meeting-309:30
*** tobberydberg has quit IRC09:30
*** tobberydberg has joined #openstack-meeting-309:31
*** jtomasek has joined #openstack-meeting-309:31
*** cartik has joined #openstack-meeting-309:33
*** egallen has joined #openstack-meeting-309:33
*** matrohon has joined #openstack-meeting-309:33
*** oanson has left #openstack-meeting-309:36
*** egallen has quit IRC09:43
*** egallen has joined #openstack-meeting-309:44
*** egallen has quit IRC09:49
*** eliqiao has quit IRC09:49
*** mickeys has joined #openstack-meeting-309:50
*** egallen has joined #openstack-meeting-309:51
*** matjazp has quit IRC09:51
*** mickeys has quit IRC09:54
*** kzaitsev_mb has joined #openstack-meeting-309:55
*** eliqiao has joined #openstack-meeting-310:00
*** kzaitsev_mb has quit IRC10:00
*** tqtran has joined #openstack-meeting-310:01
*** tovin07_ has quit IRC10:02
*** kzaitsev_mb has joined #openstack-meeting-310:02
*** zhurong has quit IRC10:03
*** tqtran has quit IRC10:05
*** markvoelker has joined #openstack-meeting-310:08
*** irenab has quit IRC10:09
*** irenab has joined #openstack-meeting-310:09
*** markvoelker has quit IRC10:13
*** tuanluong has quit IRC10:17
*** matjazp has joined #openstack-meeting-310:23
*** DuncanT has quit IRC10:33
*** DuncanT has joined #openstack-meeting-310:33
*** david-lyle_ has joined #openstack-meeting-310:35
*** anilvenkata has quit IRC10:37
*** david-lyle has quit IRC10:37
*** egallen_ has joined #openstack-meeting-310:39
*** egallen has quit IRC10:40
*** egallen_ is now known as egallen10:40
*** egallen has quit IRC10:41
*** egallen has joined #openstack-meeting-310:42
*** cartik has quit IRC10:43
*** paul-carlton has quit IRC10:44
*** yamahata has quit IRC10:45
*** paul-carlton has joined #openstack-meeting-310:47
*** mgagne has joined #openstack-meeting-310:47
*** mgagne is now known as Guest261510:47
*** leifz has joined #openstack-meeting-310:48
*** zz_dimtruck has joined #openstack-meeting-310:50
*** stanzgy has quit IRC10:50
*** zz_dimtruck is now known as dimtruck10:50
*** natorious has joined #openstack-meeting-310:50
*** mickeys has joined #openstack-meeting-310:51
*** julim has quit IRC10:53
*** sdake has joined #openstack-meeting-310:55
*** egallen has quit IRC10:56
*** mickeys has quit IRC10:56
*** kzaitsev_mb has quit IRC10:57
*** ildikov has quit IRC11:00
*** ildikov has joined #openstack-meeting-311:00
*** sambetts|afk is now known as sambetts11:00
*** qwebirc10966 has quit IRC11:01
*** matjazp has quit IRC11:02
*** kzaitsev_mb has joined #openstack-meeting-311:06
*** sdague has joined #openstack-meeting-311:08
*** egallen has joined #openstack-meeting-311:09
*** egallen has quit IRC11:12
*** igormarnat_ has quit IRC11:22
*** igormarnat_ has joined #openstack-meeting-311:22
*** ociuhandu has joined #openstack-meeting-311:23
*** ociuhandu has quit IRC11:28
*** anilvenkata has joined #openstack-meeting-311:29
*** ociuhandu has joined #openstack-meeting-311:29
*** yamamot__ has quit IRC11:36
*** shu-mutou is now known as shu-mutou-AWAY11:47
*** emagana has joined #openstack-meeting-311:52
*** mickeys has joined #openstack-meeting-311:53
*** anilvenkata has quit IRC11:54
*** tobberydberg has quit IRC11:56
*** mickeys has quit IRC11:57
*** ociuhandu has quit IRC11:58
*** matjazp has joined #openstack-meeting-311:58
*** egallen has joined #openstack-meeting-311:58
*** cgoncalves has quit IRC12:00
*** paul-carlton1 has joined #openstack-meeting-312:01
*** tqtran has joined #openstack-meeting-312:02
*** paul-carlton has quit IRC12:03
*** huanxuan has quit IRC12:03
*** tqtran has quit IRC12:07
*** anilvenkata has joined #openstack-meeting-312:08
*** tellesnobrega has joined #openstack-meeting-312:08
*** paul-carlton1 has quit IRC12:09
*** markvoelker has joined #openstack-meeting-312:09
*** markvoelker has quit IRC12:15
*** yamamoto has joined #openstack-meeting-312:16
*** irenab has quit IRC12:18
*** irenab has joined #openstack-meeting-312:18
*** nkrinner has quit IRC12:18
*** prateek has quit IRC12:19
*** rtheis has joined #openstack-meeting-312:19
*** nkrinner has joined #openstack-meeting-312:21
*** baoli has joined #openstack-meeting-312:26
*** baoli has quit IRC12:26
*** julim has joined #openstack-meeting-312:26
*** baoli has joined #openstack-meeting-312:26
*** nkrinner has quit IRC12:28
*** julim has quit IRC12:31
*** ociuhandu has joined #openstack-meeting-312:34
*** alexismonville has joined #openstack-meeting-312:36
*** nkrinner has joined #openstack-meeting-312:42
*** qwebirc25678 has joined #openstack-meeting-312:48
*** baoli has quit IRC12:51
*** Miouge has joined #openstack-meeting-312:51
*** mickeys has joined #openstack-meeting-312:53
*** qwebirc25678 has quit IRC12:56
*** qwebirc70038 has joined #openstack-meeting-312:56
*** mickeys has quit IRC12:58
*** julim has joined #openstack-meeting-313:08
*** VW has joined #openstack-meeting-313:12
*** markvoelker has joined #openstack-meeting-313:12
*** julim has quit IRC13:13
*** VW has quit IRC13:16
*** markvoelker has quit IRC13:16
*** jed56 has quit IRC13:17
*** srobert has joined #openstack-meeting-313:18
*** markvoelker has joined #openstack-meeting-313:19
*** matrohon has quit IRC13:21
*** watanabe_isao has quit IRC13:28
*** akijak has joined #openstack-meeting-313:29
*** mcunietti has joined #openstack-meeting-313:31
*** tuan_luong has joined #openstack-meeting-313:36
*** haleyb_ has joined #openstack-meeting-313:42
*** rmart04 has joined #openstack-meeting-313:44
*** tobberyd_ has joined #openstack-meeting-313:51
*** tobberyd_ is now known as tobberydberg13:52
*** qwebirc37627 has quit IRC13:54
*** Guest2615 is now known as mgagne13:54
*** mgagne has quit IRC13:54
*** mgagne has joined #openstack-meeting-313:54
*** mickeys has joined #openstack-meeting-313:54
*** donghao has joined #openstack-meeting-313:58
*** mickeys has quit IRC13:59
*** s3an2 has joined #openstack-meeting-313:59
*** bloatyfloat has joined #openstack-meeting-313:59
*** zhipengh has joined #openstack-meeting-314:01
*** Reedip_ has joined #openstack-meeting-314:02
*** prateek has joined #openstack-meeting-314:03
*** pgadiya has quit IRC14:03
*** tqtran has joined #openstack-meeting-314:04
rmart04Morning! Was expecting Public Cloud WG meet, is this still on?14:05
*** sdake_ has joined #openstack-meeting-314:05
bloatyfloatrmart04: Not seen any notification on operators list suggesting otherwise14:05
*** rpr__ has joined #openstack-meeting-314:06
rmart04Thanks, Ill hang on then :)14:06
MiougeThere was one this morning though14:06
*** prateek_ has joined #openstack-meeting-314:06
*** jenk_s_ has joined #openstack-meeting-314:07
tobberydbergI'm here for that meeting as well. Is it now or in one hour?14:07
*** andymaier has joined #openstack-meeting-314:07
jenk_s_Hi All, i'm here.14:07
*** andymaier_ has joined #openstack-meeting-314:07
*** yamamoto has quit IRC14:08
*** andymaier_ has quit IRC14:08
*** mattjarvis has joined #openstack-meeting-314:08
mattjarvissorry folks, got a bit held up14:08
*** prateek has quit IRC14:08
mattjarviswho's here for the public cloud WG ?14:08
*** tqtran has quit IRC14:09
mgagne<--14:09
tobberydbergI'm here!14:09
MiougeMe as well :)14:09
mattjarvishello mgagne14:09
mattjarvishello all14:09
*** sdake has quit IRC14:09
rmart04NP, I’m In14:09
jenk_s_Hi Matt, I'm here for the public cloud WG (Michael Jenkins)14:09
mattjarvisok, let me just pull up the etherpad14:09
jenk_s_Congrats, Matt on the new job!14:10
mcuniettihi matt and congrats again14:10
mattjarvisthanks jenk_s_14:10
mattjarvisthanks mcunietti14:10
mattjarvisso first things first - could you all add your names to the attendee list if you haven't done already14:10
mattjarvisarray:3 [â–¼14:11
mattjarvis  "token" => {#438 â–¶}14:11
mattjarvis  "user" => User {#450 â–¶}14:11
mattjarvis  "roles" => []14:11
mattjarvishttps://etherpad.openstack.org/p/publiccloud-wg14:11
mcuniettiI'm here for the public cloud WG14:11
mattjarviswhoops14:11
rmart04Could have been worse!14:11
mattjarvisjust need to remember the IRC fu to start the meeting14:12
mattjarvis#startmeeting Public Cloud WG14:12
openstackMeeting started Wed Dec  7 14:12:23 2016 UTC and is due to finish in 60 minutes.  The chair is mattjarvis. Information about MeetBot at http://wiki.debian.org/MeetBot.14:12
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:12
*** openstack changes topic to " (Meeting topic: Public Cloud WG)"14:12
openstackThe meeting name has been set to 'public_cloud_wg'14:12
*** yamamoto has joined #openstack-meeting-314:12
mattjarvisso we seem to have some names as attendees who aren't here - is anyone else lurking ?14:12
s3an2o/14:13
mattjarvisah hello s3an214:13
mattjarvisso firstly thank you all for attending14:13
mattjarvisthis will be a bit of a work in progress for the first few meetings14:14
mcuniettithank you for gathering us all14:14
mattjarvisthe most important things are to define goals and milestones14:14
mattjarvisah, one other thing - if you haven't done this already could you also add which organisation you are representing14:14
mattjarvisin the etherpad14:14
mattjarvisit's important that we have a representative quorum14:14
mcunietti+114:14
mattjarvisand this helps us track14:14
mattjarvisis VW here ?14:15
mattjarvishe said he would try to join14:15
mcuniettiI suggest also to add URL and links to service14:15
mattjarvisgood idea mcunietti14:15
*** baoli has joined #openstack-meeting-314:15
mcuniettiI see Memset also is here! good14:16
rmart04Indeedy!14:16
mattjarvis#topic Meeting cadence and communication methods14:17
*** parora has joined #openstack-meeting-314:17
*** openstack changes topic to "Meeting cadence and communication methods (Meeting topic: Public Cloud WG)"14:17
mattjarvisso on to our first topic14:17
mattjarvisfor some of the WG's IRC hasn't been a favourite choice, particularly when there are non-technical folks involved too14:17
mattjarvisI hope this group will cover both technical and non-technical issues, so is IRC an issue for anyone right now14:18
mcuniettiin order to get an answer, let's add the job description to one's line on etherpad14:18
mattjarvisI've also booked these meetings bi-weekly to begin with as I think there are some fundamental things we need to work out, which will probably involve collaboration around documents to begin with14:19
*** prateek_ has quit IRC14:19
s3an2If IRC was an issue for someone we may not get an answer here14:19
mgagneI prefer IRC tbh as it helps overcoming the language barrier (for me) although I agree that video conference would help us get much higher communication bandwidth14:19
*** prateek has joined #openstack-meeting-314:19
mattjarviss3an2,  that is true14:19
mattjarvismgagne, I suspect initially we will collaborate around documents until we work out some milestones, so that will be less of an issue14:20
mattjarvisbut I would also like to do face to face meetings at the midcycles and summits14:20
* mgagne nods14:20
s3an2mattjarvis, +1 for FTF14:21
mattjarviswhat are the groups thoughts on the assumptions I put in the ether pad for how this group might work ?14:21
rmart04I’m easy IRC/FTF/VC14:21
mattjarvisthis was mainly stolen from the scientific WG, but I know the user committee is keen to see WG's have clearly defined goals and milestones rather than be talking shops14:21
*** mtanino has joined #openstack-meeting-314:22
*** parora has quit IRC14:22
mattjarvisI see others have joined - welcome all14:22
mattjarvisgreat turnout :)14:22
tobberydbergAgreed mattjarvis14:22
mattjarvisso in the absence of any disagreement, we will stick to bi-weekly and IRC for the minute, with the caveat that this may change, add etc.14:23
mcuniettito answer to your question, i suggest we may start addressing competition with AWS. The last Re:invent almost killed me :-)14:23
mattjarvislol14:23
mgagneI'm fine with the assumptions. They are high level enough that there is nothing to say so far about them.14:23
mattjarvisok, I think we need to take this step by step - we will get to setting goals :)14:23
*** yamamoto has quit IRC14:24
mattjarvisdoes anyone else have anything to add to this topic ?14:24
*** hurgleburgler has joined #openstack-meeting-314:24
mattjarvisin that case ...14:24
mattjarvis#topic Who is our constituency - how do we ensure that we are representative14:24
*** openstack changes topic to "Who is our constituency - how do we ensure that we are representative (Meeting topic: Public Cloud WG)"14:24
jenk_s_+1 on competition. Let's think about how to increase PC adoption and usability.14:25
*** numans has quit IRC14:25
mattjarvisso I think this topic is important before we really do anything in this WG14:25
*** yamamoto has joined #openstack-meeting-314:25
*** tonytan4ever has joined #openstack-meeting-314:25
*** anilvenkata has quit IRC14:26
mattjarvisIMO we need to define clearly who our constituency are - ie. what defines a public cloud. If we are going to attempt to represent a community, then we need to define what that community consists of14:26
mcuniettistick to the good old NIST definition? ;-)14:26
mattjarvisI have added a section to the ether pad entitled Who is our constituency. Perhaps the easiest way to do this might be if we take 5 minutes to add our thoughts to the etherpad under that section14:26
*** coolsvap has quit IRC14:27
*** yamamoto has quit IRC14:27
mattjarvisthe output of this I would like to be an agreed definition that goes onto our wiki page14:27
*** yamamoto has joined #openstack-meeting-314:27
mattjarvisso if I could ask you all to add your thoughts to that section14:27
mcunietti"Public cloud. The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider."14:27
mattjarvisgreat mcunietti - could you add that ? Is that the NIST definition ?14:27
mcuniettiyep14:28
*** logan- has joined #openstack-meeting-314:28
*** krtaylor has quit IRC14:28
*** Reedip_ has quit IRC14:28
mattjarvisthere has been some discussion on the lists about whether restricted community clouds also fall under the definition eg. some of the science clouds14:28
mgagneyes, found the same14:28
mcuniettialso, I think we should limit to IaaS, shouldn't we?14:29
*** prateek_ has joined #openstack-meeting-314:29
*** krtaylor has joined #openstack-meeting-314:29
zhipenghand of course, based upon OpenStack14:29
mgagneI think the definition is broad enough to encompass most use cases of what should be a public cloud.14:29
*** prateek has quit IRC14:30
jenk_s_How should we factor into our WG other projects such as Tacker for NFV -- also very important to the providers.14:31
*** matrohon has joined #openstack-meeting-314:31
mattjarvisjenk_s_, the way I would like that to happen is for this WG to be the focal point for interaction with the public cloud provider community14:31
mattjarvisbut TBC14:32
zhipenghjenk_s_ I think NFV might be out of scope here14:32
*** reedip_ has joined #openstack-meeting-314:32
mcuniettiI agree mattjarvis, this could be a "front-end" for the Openstack community when maybe involved in the market disputes or egulation auditions14:32
zhipenghif we consider the classic public cloud definition14:32
mgagneyea, looks more related to telco or enterprise wg14:32
*** lblanchard has joined #openstack-meeting-314:33
mattjarvisso my second question in this area - again part of the idea of being representative14:33
mattjarvisdo we represent public cloud operators as per the marketplace - ie. sponsors of the Foundation ?14:34
mattjarvisor is our community wider than that14:34
mcuniettiI would split the representation concept in two: internal (towards the OS community) and external (the market, the customers, the other non-OS players)14:34
mcuniettithe press also, in the latter14:34
mattjarvisok, could you articulate that idea in the ether pad ?14:35
mcuniettiright away14:35
mattjarvisty14:35
mcuniettidone14:37
*** yankcrime has joined #openstack-meeting-314:37
*** gouthamr has joined #openstack-meeting-314:37
mgagneso this is a way to represent our group to others? (internal: the community itself, external: the market/press)14:37
*** tuan_luong has quit IRC14:38
*** sankarshan is now known as sankarshan_away14:38
rmart04We (Memset) are not currently listed on the OSFMP, making this a requirement could restrict smaller or newer public cloud operators from representing.14:38
logan-^ ++14:38
mattjarvisrmart04, that is a valid point, could you add to the ether pad please14:39
rmart04sure14:39
*** rbak has joined #openstack-meeting-314:39
*** parora has joined #openstack-meeting-314:39
mattjarvisalthough I would say that there is a low barrier of entry for start ups in terms of cost14:39
*** VW has joined #openstack-meeting-314:40
*** VW has quit IRC14:40
mattjarvisIIRC you also can't use the OpenStack logos14:40
mgagneAs long as the cloud is offered publicly, I think it's fine. Counter example, we have a huge private cloud for dev and I wouldn't represent its interests in this group.14:40
*** VW has joined #openstack-meeting-314:41
mattjarvishello VW14:41
*** rhochmuth has joined #openstack-meeting-314:41
*** matrohon has quit IRC14:41
mattjarvissome very good points raised there, looking at time I'd like to keep moving this time - but feel free to continue adding to the ether pad14:42
rmart04Logos > Not for commercial use, I believe.14:42
mattjarvisrmart04, I believe that is true14:42
mcuniettiVW= Vogels Werner, happy you finally joined the rebellion :-)14:42
mattjarvisunless you have an agreement in place14:42
*** haleyb_ has quit IRC14:42
*** prateek_ has quit IRC14:42
mattjarvisso finally on the idea of being representative, I added a section about membership of the WG14:43
mattjarvissuggestions again please14:43
*** prateek_ has joined #openstack-meeting-314:43
mattjarvisI know their are folks not on the lists who should be represented14:43
mattjarvisI have reached out to a few I know14:43
mattjarvisbut it would be good to have the most representative consituency14:43
mattjarvisif anyone has any other ideas, or has contacts with other providers who aren't here14:44
mattjarvisit would be great to get as many people as possible14:44
*** reedip_ has quit IRC14:44
mattjarvisagain this was something that came out of the scientific WG, and I know they found it useful14:44
mcuniettiwould it be good to list all the publi cloud providers we know, and have direct emails to our contacts? I think we can cover pretty much all of them14:45
mattjarvismcunietti, can you take an action to add that list to the ether pad ?14:45
mcuniettiok14:45
mattjarvisI assume you mean from the marketplace14:45
tobberydbergSounds good14:45
mattjarvis#action mcunietti to add list of public cloud providers to the etherpad14:45
mcuniettiI mean the ones where each of us has direct contacts and emails14:46
mattjarvisboth might be good information to have in one place14:46
mgagnelike word of mouth with people/cloud you know14:47
*** parora has quit IRC14:47
mcuniettiexactly14:48
mcuniettiI don't think that going through official contact points would work14:48
mattjarvisso we have 10 minutes left for this meeting, does anyone else have anything to add to this topic for the minute ?14:49
mattjarvisI'd suggest that we can regularly cycle back to the representation aspect as we move this WG forward14:49
*** qwebirc70038 has quit IRC14:49
*** reedip_ has joined #openstack-meeting-314:50
*** hosanai has joined #openstack-meeting-314:50
mattjarvisand please do add any further thoughts to the ether pad. At some point I will then collate, we can vote on the content and then add to our wiki page14:50
mattjarvisgiven where we are with time, I would like to bump up topic 5 which will then leave us all the remaining time to add thoughts on purpose and goals14:51
mattjarvisis that OK with everyone else ?14:51
mgagne+114:51
tobberydberggo14:51
rmart04+114:51
mattjarvis#topic Co-chair proposals <-- nominations and vote.14:52
mattjarvis#topic co-chair nominations14:52
*** openstack changes topic to "Co-chair proposals <-- nominations and vote. (Meeting topic: Public Cloud WG)"14:52
*** openstack changes topic to "co-chair nominations (Meeting topic: Public Cloud WG)"14:52
mattjarvisso as with all WG's it is appropriate to have more than one chair14:52
mattjarvisare there any volunteers to act as co-chairs ?14:52
mattjarvisagain this comes down to being representative, and also means that everything in terms of organisation isn't resting on one individual14:53
*** tongli has joined #openstack-meeting-314:53
mattjarvislol14:54
mattjarvisno-one ?14:54
mcuniettiok matt, I step forward14:54
zhipenghi could volunteer myself14:54
mattjarvisexcellent :)14:54
VWsorry - I'm late - got tied up with things this morning14:55
mattjarvisI actually see nothing wrong with 3 co-chairs, does anyone have any thoughts or issues ?14:55
*** mickeys has joined #openstack-meeting-314:55
mattjarvisno worries VW - progress is on the etherpad14:55
tobberydbergI can do it as well!14:56
*** irenab has quit IRC14:56
mgagneFYI, less than 3 minutes left.14:56
mattjarvisok, we should probably put this to a vote, but no time today, lets return to this next week and decide what to do14:57
*** jenk_s_ has left #openstack-meeting-314:57
mattjarvisso before we have to leave, the last topics were to discuss purpose, goals and scope - all kind of linked together14:57
mattjarvisI'd actually suggest the best way to do this would be to add ideas to the ether pad over the next two weeks and discuss once we've all added content14:58
mattjarvis#topic Discuss purpose and goals14:58
*** openstack changes topic to "Discuss purpose and goals (Meeting topic: Public Cloud WG)"14:58
*** irenab has joined #openstack-meeting-314:59
mattjarvisif you check out the bottom of the ether pad I have added sections on in scope, out of scope, and purpose14:59
mattjarviscould everyone please add their thoughts in those sections for discussion at the next meeting ?14:59
zhipenghsure14:59
VWaye, captain14:59
*** mickeys has quit IRC14:59
tobberydbergyes14:59
mattjarvisthis has been a great turnout, thank you all for participating14:59
mgagnethanks!15:00
mattjarvisnext meeting will be in 2 weeks time15:00
mcuniettithank you all15:00
tobberydbergThank you!15:00
rmart04Sure, thanks for sorting this out!15:00
*** kamil has joined #openstack-meeting-315:00
*** koji has joined #openstack-meeting-315:00
mattjarvislook forward to great work with this WG !15:00
mcuniettiok noted down15:00
*** bobmel has quit IRC15:00
*** witek_ has joined #openstack-meeting-315:00
mattjarvis#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Dec  7 15:00:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/public_cloud_wg/2016/public_cloud_wg.2016-12-07-14.12.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/public_cloud_wg/2016/public_cloud_wg.2016-12-07-14.12.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/public_cloud_wg/2016/public_cloud_wg.2016-12-07-14.12.log.html15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Dec  7 15:00:57 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmutho/15:01
kamilo/15:01
*** logan- has left #openstack-meeting-315:01
kojio/15:01
rbako/15:01
witek_hello15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** Miouge has left #openstack-meeting-315:01
rhochmuthAgenda for Wednesday December 7 2016 (15:00 UTC)15:01
rhochmuth1.Grafana branch - merge upstream?15:01
rhochmuth2.Reviews:15:01
rhochmuth1.https://review.openstack.org/#/c/395246/15:01
rhochmuth2.https://review.openstack.org/#/c/349097 - SAP team would like to contribute 15:01
rhochmuth3.https://review.openstack.org/406936, https://review.openstack.org/40737115:01
rhochmuth4.https://review.openstack.org/40737915:01
rhochmuth5.https://review.openstack.org/#/c/395897/15:01
*** mattjarvis has left #openstack-meeting-315:01
*** qwebirc30600 has joined #openstack-meeting-315:01
rhochmuthhi everyone15:01
hosanaio/15:01
rhochmuthit is really cold and snowing here15:01
qwebirc306000/15:02
*** dirk has joined #openstack-meeting-315:02
qwebirc30600where?15:02
witek_nice15:02
*** zhipengh has left #openstack-meeting-315:02
kamilfridge opened?15:02
rhochmuthFort Collins, CO15:02
qwebirc30600o15:02
rhochmuthlet's get started with the agenda first15:02
*** haleyb_ has joined #openstack-meeting-315:03
rhochmuth#topic Grafana branch - merge upstream?15:03
*** openstack changes topic to "Grafana branch - merge upstream? (Meeting topic: monasca)"15:03
rbakThat's me15:03
rhochmuthplease proceed15:03
rbakRaintank, the owner's of Grafana have been fairly silent lately15:03
*** jobrs has joined #openstack-meeting-315:03
rhochmuthuhh, ohhh15:03
rbakWe're not sure that our original plan of brining them on as vendors for Charter is going to work15:04
rbakAnd our fork of Grafana is slowing getting more complex and harder to merge in.15:04
rhochmuthdo you think that they are having financial problems15:04
rhochmuthor just not interested in what we are doing15:05
rhochmuthor other priorities15:05
rbakJust not interested15:05
rbakThat's probably more accurate15:05
rbakSo we either need to make a push as a community to get the keystone changes moved into upstream, or we need to resign ourselves to maintaining a permanent fork again.15:05
rhochmuthi thought you guys were going to put a support agreement or licensing in-place15:05
rhochmuththat would have incenticized them enough15:06
rbakWe're still trying, but they stopped replying.15:06
rbakThe difficulties with the merger may have scared them off15:06
*** irenab has quit IRC15:06
rhochmuthi see15:06
rbakSo it's a question of whether we can rally enough support15:07
rbakI can put up a new pull request15:07
rhochmuthok15:07
*** tobberydberg has quit IRC15:07
*** yankcrime has left #openstack-meeting-315:07
rhochmuthare we just supposed to thumbs up it at that point15:07
*** haleyb_ has quit IRC15:07
rhochmuthwhat does support mean from your viewpoint?15:08
rbakThumbs up would be good15:08
rbakI also plan on emailing them directly.15:08
rhochmuthok, we can do that15:08
rhochmuthok15:08
rbakIf anyone wants to be included on that let me know15:08
rhochmuthi can contact them also15:08
rhochmuthplease include me15:08
rbakwill do15:08
rhochmuthare you talking to raj dutt15:08
rhochmuthi think that is the name15:08
*** akijak has left #openstack-meeting-315:08
rhochmuthit has been a while15:08
rbakYeah, him and Torkel if I can dig out his email.15:09
rhochmuthwith more and more folks using monasca, i'm hoping they would be interested15:09
rhochmuththere are potential support/service agreements they could get as a result15:09
rbakThat and the fact that the changes we want are actually keystone specific, so in theory it could be used with any openstack projects, or just Grafana as a service.15:10
*** yingjun has joined #openstack-meeting-315:10
rhochmuthbut, there is a lot of momentum around some other tools, like promethues and influxdb, that is probably distractign them15:10
rbakWell, they just released Grafana 4, so hopefully this is a good time, while they're still planning for the next version.15:11
rhochmuthyes, i agree, i would expect some interest on their part15:11
rhochmuthso, now that 4 is out, are you going to look at adding alerts?15:11
rhochmuth:-)15:11
rbakWe're going to look into it, yes15:11
rhochmuththanks15:11
rhochmuthwe've been using grafana a lot internally lately, and it is working great15:12
rbakGood to hear15:12
rhochmuthwe had some very impressive demos this week with kubernetes15:12
rhochmuthand monasca15:12
rbakThat's all I had on this subject.  I'll put up a new pull request and bring that up at the meeting next week.15:12
rhochmuthi'm wondering if we should get a higher level business call together with raintank between allthe interested companies15:13
*** mhoppal has joined #openstack-meeting-315:13
rhochmuthcharter, hpe, fujitsu, …,15:13
*** davidsha has joined #openstack-meeting-315:13
rbakI would be up for that.15:13
*** davidsha has left #openstack-meeting-315:13
rbakI'll suggest that in my email15:13
witek_you have our support too15:13
rhochmuthyes, please do15:13
rhochmuthi think they should understand the momentum and business opportunity better15:14
*** irenab has joined #openstack-meeting-315:14
rhochmuthmaybe we should get and email out to openstack-dev list as well15:14
rhochmuththere are other companies involved in deploying monasca these days that we could also lobby15:14
*** armax has joined #openstack-meeting-315:14
rhochmuthinvariably, it is going to be about the money i guess15:15
rhochmuthor the perceived opportunity15:15
rbakProbably, but they are open source, and did tell us they were interested even without a contract when we talk initially.15:15
rhochmuthok, let's see what happens with the email15:16
rbakSounds good.  I'll include you on that.15:16
rhochmuthand then maybe we can rally the troops15:16
rhochmuththanks rbak15:16
rhochmuthgood update15:16
rhochmuth#topic https://review.openstack.org/#/c/395246/15:16
*** bklei has joined #openstack-meeting-315:16
*** openstack changes topic to "https://review.openstack.org/#/c/395246/ (Meeting topic: monasca)"15:17
rbakThat one is also mine15:17
*** dhague has joined #openstack-meeting-315:17
rbakJust wondering if it can be merged15:17
rbakIt's been around a couple weeks with some +1s15:17
rhochmuthi +1'd again this morning, but yes i think it is ready15:17
rhochmuthyou should probably ping craig15:18
rhochmuthas he spotted a couple of issues15:18
rbakAlright, I can get him to look at it15:18
rhochmuthbut he hasn't looked at it again since your latest fixes/reviews15:18
rhochmuthassuming he is ok, then it could be merged15:19
rbakSounds good.  I'll ping him15:19
rhochmuththx15:19
rhochmuth#topic https://review.openstack.org/#/c/34909715:19
*** openstack changes topic to "https://review.openstack.org/#/c/349097 (Meeting topic: monasca)"15:19
rhochmuthsap, jbors u there?15:19
jobrsyep15:20
jobrswe are willing to help.15:20
rhochmuththanks15:20
jobrsand we are working on some complementary stuff15:20
rhochmuthso, do you want to take on this review15:20
rhochmuthi don't think haneef is working on it anymore15:20
*** yamamoto has quit IRC15:20
rhochmuthand was just waiting to merge it15:20
rhochmuthi had signed off on it15:20
jobrssure15:21
rhochmuththanks15:21
dhaguesorry, late to the topic and just catching up on the discussion so far - all sounds good to me. We need to get some kind of response from raintank, even if it's jsut to get an answer one way or the other15:21
jobrswe want to add notification templates for slack and mail since this is what we are using15:21
*** irenab has quit IRC15:21
rhochmuthdhague: yes, i agree15:21
dhague... and I just noticed the topic change. sorry 'bout that15:21
rhochmuthrbak: please add dhague and jbors to email list, i'm assuming15:22
rbakwill do15:22
rhochmuthemail list to raintank that is15:22
jobrsthanks15:22
dhague+115:22
rhochmuthok, np on topic change15:22
rhochmuthso, i'm assuming dhague will take over the custom formatting for the hipchat plugin15:23
rhochmuthyou had also fixed the slack plugin recently too15:23
dhagueon the new topic, I am looking at that - in fact, having some kind of per-channel templating15:23
dhaguethe idea is this:15:24
dhaguealarm definition "description" field will be a jinja template, so we can generate some kind of human-readable alert message15:24
*** seanhandley has joined #openstack-meeting-315:24
bkleiquestion on the hipchat plugin formatting15:24
dhaguethen at the channel level that can be fed into another template - pretty raw for hipchat & slack, but email would allow HTML headers etc15:25
bkleiwill this patch let us change msg color based on alarm severity?15:25
seanhandleyOh, the public cloud meeting's over15:25
seanhandley:(15:25
jobrsthat will be possible15:25
*** seanhandley has left #openstack-meeting-315:25
jobrsjinja2 has primitives like if and for etc.15:26
bkleiexcellent -- it's goofy that everything is green today15:26
*** yamamoto has joined #openstack-meeting-315:26
jobrsthe redesign has two parts15:26
dhaguejobrs and I had a brainstorming on this yesterday, the above is the brief summary of what we discussed - is it OK with everyone?15:27
dhagueI will let jobrs continue...15:27
jobrsjust wanted to add what I discovered today15:27
jobrsso part one is just in notification: templates for formatting notification messages15:27
*** mcunietti has quit IRC15:27
*** irenab has joined #openstack-meeting-315:28
jobrspart two is more tricky: have the monasca-api pass the alarm-definition's description alongside the alarm (not just the name)15:28
*** sdake_ has quit IRC15:29
bkleithat's not there already?15:29
jobrsso we would need some support in reviewing the API changes and someone who would do the Java side of it15:29
*** jgrassler has joined #openstack-meeting-315:29
rhochmuthwhy do you need the description in the alarm?15:29
*** yamamoto has quit IRC15:29
rhochmuthcan't you get that by querying the db?15:30
rhochmuthnot sure i understand the proposal15:30
bkleihaving the alarm definition description in the alarm is useful -- we use it for runbook links for oncall15:30
jobrsthe description is what matters most to the user (imho)15:31
bkleibut i believe it's already there -- this is from the current hipchat plugin:15:31
bklei   "old_state": "UNDETERMINED",15:31
bklei   "alarm_description": "The http response time is greater than 3s on avg",15:31
bklei   "message": "Thresholds were exceeded for the sub-alarms: avg(soapuiv2MonascaTesterMetric{hostname=dnvrco02-keystone-001}) > 3.0 with the values: [4.6218046456454775]",15:31
*** seanhandley has joined #openstack-meeting-315:31
jobrsit is in the notifications, but not the alarms. when you display the alarm in a UI it would be good to have the description of it15:31
*** baoli has quit IRC15:32
*** sdake has joined #openstack-meeting-315:32
bkleiaah.  i see.15:32
*** absubram has joined #openstack-meeting-315:32
rhochmuthbut, that could be done with mutiple queries15:32
rhochmuthget alarm, then get alarm definition15:33
jobrsif you have a templated alarm description and you can render it using the alarm attributes, then you can have quite instructive alarms15:33
rhochmuththen merge the two15:33
*** qwebirc9811 has joined #openstack-meeting-315:33
jobrsslow15:33
*** seanhandley has left #openstack-meeting-315:33
jobrsyou did the job already for the alarm-description-name15:33
rhochmuthok15:34
rhochmuthinteresting, that we didn't see that through15:34
rhochmuthso, when you query an alarm, you would also return the description in the json body?15:34
*** koji has quit IRC15:34
*** irenab has quit IRC15:35
jobrsyes, and I would do the template rendering in the monasca-client15:35
rhochmuthso, how would the monasca-client know how to render it?15:36
rhochmuththe custom formatting is for the notifications15:36
jobrsthat is what I mean with two parts. One thing is to have descriptions with variables. the other is to have proper presentation for your notification channel15:37
jobrswe believe you need both to have actionable alarms15:37
rhochmuthok15:38
rhochmuthnot sure i'm grokking the full extent of the changes15:39
jobrsit should be non-breaking15:39
rhochmuthgood enough for me15:39
rhochmuth:-)15:39
*** rbrndt has joined #openstack-meeting-315:39
*** irenab has joined #openstack-meeting-315:39
dhagueWe can discuss the fine details in the code review :-)15:40
rhochmuthsounds good15:40
jobrslet's do so15:40
rhochmuthso, at this point i please proceed, and we can discuss more in the code review15:41
jobrslast question - can we use the change for further developments or created a separate one?15:41
rhochmuthsure, you can use that review15:42
rhochmuthi think that is the best option15:42
jobrsgreat, I hope we can deliver the first proposal next week15:42
*** irenab has quit IRC15:42
rhochmuththanks15:42
rhochmuth#topic https://review.openstack.org/406936, https://review.openstack.org/40737115:43
*** openstack changes topic to "https://review.openstack.org/406936, https://review.openstack.org/407371 (Meeting topic: monasca)"15:43
rhochmuthyingjun: you there?15:44
yingjunyep15:45
rhochmuthyou are up15:45
rhochmuthFix UnicodeEncodeError for alarm definition15:45
*** spzala has joined #openstack-meeting-315:46
yingjunso as the bug reported, when i input Chinese in description, it will raise the UnicodeEncodeError15:46
rhochmuthi thought we could encode/decode utf815:47
*** yamamoto has joined #openstack-meeting-315:47
rhochmuthso, i'm a bit confused by the fix and why it was necessary15:48
witek_yingjun: could you add that case to the tests?15:48
*** matjazp_ has joined #openstack-meeting-315:48
yingjunwitek_, sure15:48
rhochmuthshouldn't decode(('utf8') work for both chineese and other strings15:49
*** irenab has joined #openstack-meeting-315:49
rhochmuthwhat you are doing now is not decoding the string if it is six.text_type15:50
*** hogepodge has joined #openstack-meeting-315:50
yingjunyes15:50
*** Sukhdev_ has joined #openstack-meeting-315:51
*** matjazp has quit IRC15:51
yingjuni’m not sure if there’s case it wasn’t text_type15:51
rhochmuthyes, i'm wondering why the data isnn't stored as text_type15:52
rhochmuthi'm wondering if bad data got in the db15:53
rhochmuthshould we have converted it when storing the description15:53
rhochmuthit sounds to me that it wasn't converted when we stored it15:53
yingjunthe case https://github.com/openstack/monasca-api/blob/master/monasca_api/tests/test_alarms.py#L504 do15:53
yingjunbut it mocks the db return value15:54
rhochmuthok, i'll look at it more15:55
rhochmuthi obviousely am missing some bit of understanding15:55
rhochmuthill add comments to the review15:55
*** reedip_ has quit IRC15:55
yingjunok15:55
witek_have you checked that your db has utf8 encoding?15:55
*** mickeys has joined #openstack-meeting-315:56
yingjunwitek_, not yet15:56
yingjunwitek_, i will check that tomorrow, it pretty late here in China...15:56
*** emagana_ has joined #openstack-meeting-315:56
yingjunwitek_, and the test env not in my laptop15:57
rhochmuth#topic https://review.openstack.org/#/c/407379/15:57
*** openstack changes topic to "https://review.openstack.org/#/c/407379/ (Meeting topic: monasca)"15:57
*** emagana has quit IRC15:57
rhochmuthlooks like joe merged that one this morning15:57
*** irenab has quit IRC15:57
rhochmuth#topic https://review.openstack.org/#/c/395897/15:58
*** openstack changes topic to "https://review.openstack.org/#/c/395897/ (Meeting topic: monasca)"15:58
rhochmuthi think we are going to run out of time to discuss this one15:58
yingjun;(15:58
rhochmuthi'll try and look at it more15:58
yingjunrhochmuth, thanks15:59
rhochmuthtomasz seems to think it was the right direction too15:59
*** kamil has quit IRC15:59
rhochmuthhe should probably be pinged again on this one15:59
rhochmuthso, i need to close out the meeting again15:59
rhochmuthone hour just isn't enough some days15:59
*** parora has joined #openstack-meeting-315:59
rhochmuththanks everyone16:00
dhaguethanks16:00
qwebirc30600thanks16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Dec  7 16:00:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-07-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-07-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-07-15.00.log.html16:00
*** mickeys has quit IRC16:00
*** emagana_ has quit IRC16:00
*** hosanai has quit IRC16:00
*** prateek_ has quit IRC16:01
markvoelker#startmeeting defcore16:01
openstackMeeting started Wed Dec  7 16:01:09 2016 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
*** yingjun has quit IRC16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
*** catherineD has joined #openstack-meeting-316:01
openstackThe meeting name has been set to 'defcore'16:01
*** dhague has quit IRC16:01
*** rhochmuth has quit IRC16:01
egluteo/16:01
*** yingjun has joined #openstack-meeting-316:01
markvoelker#chair eglute hogepodge16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
catherineDo/16:01
*** prateek_ has joined #openstack-meeting-316:01
hogepodgeo/16:01
markvoelker#link Today's agenda https://etherpad.openstack.org/p/DefCoreRoble.516:01
Rockygo/16:01
*** galstrom_zzz is now known as galstrom16:01
*** shamail has joined #openstack-meeting-316:02
*** cgoncalves has joined #openstack-meeting-316:02
shamailhi16:02
markvoelkerhi folks.  Let's jump right in...16:02
markvoelker#topic PTG16:02
*** openstack changes topic to "PTG (Meeting topic: defcore)"16:02
markvoelkerhogepodge: any updates on meeting space?16:03
hogepodgemarkvoelker: yes, catherineD through refstack has secured two days of meeting space for us16:03
*** tongli has quit IRC16:03
markvoelkerexcellent, thanks catherineD16:04
*** bklei has quit IRC16:04
markvoelker#info meeting at PTG is on16:04
hogepodgeIt is officially ok for us to use that space along with the refstack project16:04
*** parora has quit IRC16:04
eglutedo we know which days?16:04
hogepodgeI think the first two days, but catherineD can confirm.16:05
egluteyes, i see it on the website16:05
eglutehttps://www.openstack.org/ptg/16:05
*** yingjun has quit IRC16:05
hogepodgeWe're even on the schedule. :-D16:05
catherineDMonday and Tuesday16:06
eglutethank you catherineD!16:06
eglutedo we know how the space will work?16:06
hogepodge#info PTG Monday and Tuesday February 20-2116:06
egluteare we going to have one room for us and refstack, or?16:06
hogepodge#link https://www.openstack.org/ptg/16:06
shamailThe first two days are focused on cross project needs16:06
catherineDyes one room for both days16:06
*** matjazp_ has quit IRC16:07
eglutethanks catherineD16:07
markvoelkercatherineD: ok, so sounds like we'll need to work out some kind of agenda so we're not stepping all over each other. =)16:07
*** irenab has joined #openstack-meeting-316:08
*** matjazp has joined #openstack-meeting-316:08
markvoelkerIs there a tentative schedule for refstack yet?16:08
catherineDyea, but mostly willl be Interop WG meeting  just like the meet term we had before16:08
*** mariannelm has joined #openstack-meeting-316:09
*** witek_ has left #openstack-meeting-316:09
*** rbrndt has left #openstack-meeting-316:09
markvoelkerok, so I guess eglute and you and I should circle up and hash out a tentative agenda then.  Shall we start an etherpad for topics?16:10
egluteyes, lets do that16:10
* shamail cant't make it since kids are off that week16:10
markvoelkerOk, eglute would you mind setting one up and sending it to the ML's16:10
markvoelkershamail: bummer =/16:10
shamailI know :(16:10
eglute#action eglute start etherpad with agenda for PTG and send it out to ML16:11
catherineDbecause most  of the cores  from the RefStack team won't be at PTG16:11
*** rmart04 has quit IRC16:11
*** matjazp_ has joined #openstack-meeting-316:11
markvoelker#action eglute to start PTG agenda etherpad and post to ML16:11
markvoelkerAnythign else on PTG before we move on?16:12
*** irenab has quit IRC16:12
*** reedip_ has joined #openstack-meeting-316:12
*** matjazp has quit IRC16:12
*** lpetrut has quit IRC16:12
markvoelkerhearing none....16:12
markvoelker#topic 2017.0116:12
*** openstack changes topic to "2017.01 (Meeting topic: defcore)"16:12
*** armax has quit IRC16:12
*** yingjun has joined #openstack-meeting-316:12
markvoelkerFirst up: cinder16:12
*** lpetrut has joined #openstack-meeting-316:12
shamailI looked at the etherpad last night to start working on cinder but got a little stuck16:13
shamailI think we want to add all V3 as advisory but reference the V2 tests (which are the same ones referenced by the approved capabilities)?16:13
markvoelkershamail: ?16:14
shamailIs that correct?16:14
*** emagana has joined #openstack-meeting-316:14
*** armax has joined #openstack-meeting-316:14
shamailThe other dilemma is that cinder does have a list API versions call but there is no test for it16:14
hogepodgeThat sounds correct to me, since v3 is the equivalent of nova v2.1 in microversion intent16:15
markvoelkerShamail: Yeah, I think the general idea is to put v3 into advisory as long as the same tests work.16:15
shamailSo we're okay with referencing the same ID idempotent ID?16:15
markvoelkeryup16:15
hogepodgeshamail: sounds like we should write a test for it in the next month. My suggestion is to add the capability section as a placeholder until the test is written16:15
shamailOkay, thanks.16:15
markvoelkerFor the version list thing: I've written a couple of those tests now, seems like something I can add to my plate.16:16
markvoelkerLikely not in time for this round of scoring, but...16:16
shamailSo my actions are create cinder V3 as advisory and add list apis as advisory but no test definition yet?16:16
*** armax has quit IRC16:17
markvoelkerI'd go ahead and add version-list to the scoring sheet and note that no test currently exists for it.16:17
shamailV3 will also probably not pass scoring since most/all SDKs are still using V216:17
markvoelkerIf me or someone else can create one in time we can consider adding it.16:17
shamailBut I'll score it as well16:17
shamailOkay, sounds good16:17
markvoelkerIf not, it'll be a note in the scoring sheet for next time so we can re-eval then16:17
shamailI'll knock that one out tonight16:18
*** yingjun has quit IRC16:18
markvoelkerOk, on to Swift then?  Anything else on cinder?16:18
*** pcaruana has quit IRC16:18
*** yingjun has joined #openstack-meeting-316:18
shamailThat's all for cinder until next week16:18
*** spzala has quit IRC16:19
*** emagana has quit IRC16:19
egluteThanks for reviewing Swift Mark! I will update it today16:19
markvoelkerOk, eglute?  Swift updates?16:19
*** armax has joined #openstack-meeting-316:19
markvoelkerSure.  Sorry that took so long.16:19
eglutethank you for reviewing!16:19
eglutei think i need to do another PR for just updated tests16:20
eglutebut i wonder if that is better for the next cycle16:20
*** spzala has joined #openstack-meeting-316:20
eglutesince that would be a lot of tests to review16:20
*** bobmel has joined #openstack-meeting-316:20
markvoelkerok.  I'll just note that we're running really low on time since January is right aroudn the corner, so the sooner the better (esp. for stuff that may take a while).16:21
markvoelkeranything else on swift?16:22
eglutenot at the moment16:23
*** irenab has joined #openstack-meeting-316:23
hogepodgeOn the time note, for scheduling16:23
hogepodge#info Next is Board meeting January 28, 12:00pm-2:00pm Pacific Conference Call16:23
markvoelkerok, moving on to Nova.  Shamail has a patch up for this16:23
hogepodgeAck, wrong date, that's last year16:23
hogepodgeignore that16:23
markvoelker#link Nova patch https://review.openstack.org/#/c/385781/616:23
shamailYes, I moved the new capabilities to advisory.16:23
*** spzala has quit IRC16:23
markvoelkerCool, thanks.  There was something with the suspend/resume tests I wanted to check into, but I think this getting close16:24
*** bobmel_ has joined #openstack-meeting-316:24
shamailOkay, please let me know if I need to follow-up on anything.16:25
egluteJanuary Board meeting will most likely be on January 31st.16:25
shamailI also rebased the changer16:25
markvoelkerThis could use some more eyeballs from other folks, so please take a look16:25
*** armax has quit IRC16:25
Rockyglink?16:26
*** bobmel has quit IRC16:26
hogepodgeeglute: yes, late january is the proposed date16:26
markvoelkerRockyg: see above. =)16:26
hogepodge#info Jan 31, 1 -3pm pacific16:26
*** psachin has quit IRC16:26
markvoelkerhttps://review.openstack.org/#/c/385781/616:26
Rockygoh.  oops.  Thanks.16:26
markvoelkerOk, anything further on nova?16:27
markvoelkerKeystone and Glance patches are landed, so we're good there.16:27
markvoelkerWhile we're discussing reviews, I'll just note that there are a couple of patches out for aliasing and flagging existing stuff16:28
*** spotz_zzz is now known as spotz16:28
markvoelkereglute: I think you Workflow+1'd one of them but it hasn't merged yet?16:28
eglutehm, let me see16:28
markvoelkereglute: https://review.openstack.org/#/c/405048/16:28
markvoelkermay need a recheck (and a +2 from you while you're at it =)16:29
markvoelkerThe other one is:16:29
markvoelker#link Alias patch https://review.openstack.org/#/c/405039/16:29
markvoelkerWhich LGTM but needs another review or two16:29
eglutelooks good to me, I can move it later after others have a chance to look16:30
*** nkrinner is now known as nkrinner_afk16:30
*** irenab has quit IRC16:30
shamailWill review today16:30
eglutethanks luzC and shamail!16:30
markvoelkerIt's a pretty simple change so should be quick.16:31
markvoelkerOk, monving on to the name change16:31
*** yamahata has joined #openstack-meeting-316:31
*** spzala has joined #openstack-meeting-316:31
markvoelkerShamail: I see you got the wiki moved over16:31
shamailYes sir16:31
markvoelkerI think it's time to pull the trigger on deleting the old #openstack-defcore channel.  What do folks think?  We've been warning about it for weeks...16:31
*** andymaier has quit IRC16:32
*** qwebirc30600 has quit IRC16:32
shamailAll the links I checked worked, but if we notice any issues please let me know16:32
markvoelker(months?)16:32
Rockyg++ good job!16:32
eglutei think closing the other channel is fine!16:32
Rockygany idea how much traffic it's getting?16:32
egluteWe also need to send out official announcement telling people to move16:32
shamailNow that we have the wiki moved, is it okay if we change the eavesdrop listing?16:32
egluteIRC channel? about zero traffic16:32
egluteshamail yes please16:33
shamailWe can stay with the same meeting ID for now to keep the same logs or change it to 'interop' and add a pointer to the old DefCore logs in the wiki.  Thoughts?16:33
RockygYeah. just checked the channel.  Mostly the veterans who are just there in case16:34
markvoelkerShamail: I'd be inclined to go ahead and make the change.16:34
markvoelker(and add pointer in wiki)16:34
RockygAgree.16:34
hogepodgeI'm waiting on infra to approve the new mailing list. I pinged them on it this morning.16:34
shamailmarkvoelker: +1, we'll have to do it sooner orblater16:34
shamailCan you please assign the action to update eavesdrop so I remember?16:35
hogepodge#link New Mailing List review https://review.openstack.org/#/c/404921/16:35
markvoelkershamail: oh, actually I thnk I wrote the eavesdrop change before remembering you had that AI. =)16:35
markvoelkerI'll go ahead and push it this afternoon if that makes life easier on you. =)16:35
*** spzala has quit IRC16:35
shamailPerfect16:35
markvoelker#action markvoelker push eavesdrop patch to update meeting name16:36
eglutehogepodge once the mailing list is created, we can send out official announcment16:36
shamailMake sure you update the wiki location in eavesdrop16:36
hogepodgeshamail: yeah, the openstack bot it out of there16:36
markvoelkershamail: will do16:36
markvoelker#action markvoelker update meeting info in wiki once patch lands16:36
eglutelets not shut down current ML until official announcement goes out16:36
*** armax has joined #openstack-meeting-316:37
*** spzala has joined #openstack-meeting-316:37
hogepodgeonce the new ML is up I'll send the announcement alerting people to move over, then shut down the list so no new messages can reach it.16:37
hogepodgejust waiting on infra now16:37
*** iyamahat has joined #openstack-meeting-316:37
markvoelkersounds like a plan.16:37
*** bpokorny has joined #openstack-meeting-316:37
markvoelkerThe other action related to this on my plate is updting https://review.openstack.org/#/c/327086/ which I'm about 50% done with.16:37
shamailAwesome16:37
*** bpokorny has quit IRC16:38
*** paul-carlton2 has joined #openstack-meeting-316:38
*** irenab has joined #openstack-meeting-316:38
*** bpokorny has joined #openstack-meeting-316:38
*** yingjun has left #openstack-meeting-316:38
markvoelkerWe also wanted to get repo names updates, but I sorta felt like it would be best to land that patch first16:39
Rockyg++16:40
egluteagree16:40
markvoelkerok, anything else we need to talk about on this topic today?16:40
markvoelkerOk, moving on16:41
markvoelker#topic documenting how projects can become part of Guidelines16:41
*** openstack changes topic to "documenting how projects can become part of Guidelines (Meeting topic: defcore)"16:41
markvoelkereglute: I just realized I had an AI to send you some notes I'd started drafting on that, which I totally forgot to do16:41
*** spzala has quit IRC16:41
markvoelkerI'll get those over to you after linch16:41
markvoelker*lunch16:41
eglutemarkvoelker it is ok! i was swamped last week16:42
eglutethank you markvoelker !16:42
markvoelkerAnd with that we're at open discussion...16:42
markvoelker#topic open floor16:42
*** openstack changes topic to "open floor (Meeting topic: defcore)"16:42
egluteI created etherpad for PTG: https://etherpad.openstack.org/p/InteropWGAtlantaPTG16:42
markvoelkereglute: thanks16:42
egluteplease let us know if you are planning to attend16:42
egluteand propose topics for PTG.16:43
*** kzaitsev_mb has quit IRC16:43
shamailDo we see DefCore playing a role in the strategic OpenStack futures discussion?16:43
eglutewe will plan our agenda around it16:43
egluteshamail good question16:43
shamailDo things like scenario tests, discoverability, etc. need to be noted in that convo16:43
eglutei think so16:43
markvoelkershamail: not sure if everyone is even quite aware of that discussion at the past couple of Board meetings...if not, a good primer: https://etherpad.openstack.org/p/ocata-strategic-review-board16:44
shamailDiscoverability should be there and strategically we should ask better collaboration on interoperability in general to achieve a "one global Cloud" feel as described in "one platform"16:45
eglutealso blog post by Mark McLoughlin: https://crustyblaa.com/december-6-openstack-foundation-board-meeting.html16:45
egluteshamail good points16:45
*** mickeys has joined #openstack-meeting-316:45
*** dtp has joined #openstack-meeting-316:45
markvoelkershamail: I think some of those things will be reflected in some of the responses to the "12 questions" exercise too.16:46
markvoelkerOr at least I know they will for at least one response. =p16:46
shamailI defer to y'all to determine the right time since the conversation is still high-level for now... we would just want to raise interoperability as a concern before it becomes too low-level based on next steps16:46
shamailLOL, make that TWO responses :)16:47
egluteshamail i agree16:47
markvoelkerNote also that DefCore was called out specifically in the etherpad there a couple of times, so folks are thinking about how we fit into that picture16:47
eglutethe full discussion on this will be during the next in person board meeting16:47
shamailmarkvoelker: +116:47
markvoelkereglute: remind me, did they decide to try to do that in person at the PTG with the TC?16:47
eglutetentatively, it is scheduled for February 24th in Atlanta16:47
markvoelkerOr was that still just a proposal?16:47
markvoelkerok16:47
shamailThey will be following up to see if it works for them/when16:48
shamailAh nice16:48
shamailThat was fast16:48
*** spzala has joined #openstack-meeting-316:48
RockygThe tc just let everyone know the board might wwant to meet with them at PYG16:49
*** irenab has quit IRC16:49
RockygThe response was "not during the normal days of ptg16:50
eglutewell, normal ptg is monday-thursday i think16:50
egluteand the board meeting on Friday16:50
RockygThough maybe part of Friday.16:50
egluteRockyg where are you seeing this?16:50
Rockygthe TC meeting yesterday.16:51
egluteRockyg thanks!16:51
Rockygcheck the meeting logs.  very near the end.16:51
egluteRockyg will do!16:51
*** armax has quit IRC16:51
RockygYeah.  We need to tag team here to cover all angles ;-)16:52
*** egallen has quit IRC16:52
*** andreas_s has quit IRC16:52
eglute:)16:52
markvoelkerok, anything else today folks?16:53
*** spzala has quit IRC16:53
eglutewe can finish early!16:53
markvoelkerhearing nothing, I think we can close up for the day16:53
eglute:D16:53
eglutethank you markvoelker!16:54
markvoelkerThanks everyone!16:54
markvoelker#endmeeting16:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:54
openstackMeeting ended Wed Dec  7 16:54:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-07-16.01.html16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-07-16.01.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-07-16.01.log.html16:54
Rockygthanks!16:54
shamailBye!16:54
*** shamail has quit IRC16:54
*** spzala has joined #openstack-meeting-316:54
catherineDbye16:54
*** catherineD has left #openstack-meeting-316:56
*** stevejims has quit IRC16:58
*** VW_ has joined #openstack-meeting-316:59
*** spzala has quit IRC16:59
dansmith#startmeeting nova_cells17:00
openstackMeeting started Wed Dec  7 17:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
dansmithlettuce do this, and do it quick17:00
melwitto/17:00
dtpo/17:00
dansmith#topic reviewage17:00
*** openstack changes topic to "reviewage (Meeting topic: nova_cells)"17:00
dansmithmy set is starting to come together and a few things have landed17:01
dansmithso that's good for me17:01
dansmithmelwitt: are there any quota patches up that people need to look at?17:01
*** kzaitsev_mb has joined #openstack-meeting-317:01
melwittnot yet, no17:01
*** bpokorny has quit IRC17:02
dansmithokay17:02
dansmithany other review things we should be looking at?17:02
*** VW has quit IRC17:02
*** lpetrut has quit IRC17:02
*** bpokorny has joined #openstack-meeting-317:02
melwittnot that I know of17:02
dansmithme either17:02
dansmithI guess I skipped over:17:02
dansmith#topic testing/bugs17:03
*** openstack changes topic to "testing/bugs (Meeting topic: nova_cells)"17:03
dansmithnothing here that I know of either17:03
melwittme neither17:03
dansmith#topic open discusheyohn17:03
*** openstack changes topic to "open discusheyohn (Meeting topic: nova_cells)"17:03
dansmithmelwitt: you had a todo for the console stuff17:03
melwittnice spelling17:03
melwittthat's right, I did my consoleauth homework17:04
melwittI put the notes here https://etherpad.openstack.org/p/nova-multiple-cells17:04
melwittbasically I think we will have to just change the deploy assumption to run consoleauth per cell instead of at the top17:04
melwittand then add message queue switching calls to the consoleauth rpcapi, which I can do17:05
*** haleyb_ has joined #openstack-meeting-317:05
dansmithokay that sounds ideal and very cells-ish17:05
dansmithcellsv2-ish I mean17:05
dansmith#link https://etherpad.openstack.org/p/nova-multiple-cells17:05
melwittthis is what we need to do until the tokens in db thing, so when we have that later on we revisit17:05
dansmith#info consoleauth will be per-cell and require just a little wiring to make sure api calls the right one17:06
dansmithyeah, cool17:06
melwittthat is, some day we won't need the consoleauth service at all, IIUC17:06
*** spzala has joined #openstack-meeting-317:06
*** kzaitsev_mb has quit IRC17:06
dansmithyeah17:06
dansmithokay sweet17:06
dansmithanything else for open discussion?17:07
*** bpokorny has quit IRC17:07
dtphi, im' dan17:07
dtpif there's something small i can help with, i'd like to17:07
*** notmars has joined #openstack-meeting-317:07
dansmithdtp: I thought you were an op type person, but you mean help with code yes?17:08
dtpi have basically no experience, except i did write an internal patch in cells v1 to allow a sync of a single instance from compute to api cell17:08
dtpyes17:08
dtpcode17:08
dansmithcool17:08
dansmithmaybe the consoleauth wiring through rpcapi? melwitt that should be pretty simple and following the pattern for compute right?17:08
melwittyeah, that should be a small change17:09
dansmithdtp: do you have access to test hardware? because RSN the bigger deal is going to be trying things with two cells and seeing what breaks17:09
*** dconde has joined #openstack-meeting-317:09
*** dconde has quit IRC17:09
*** mariannelm has quit IRC17:09
dtpi will have to ask about that17:09
*** haleyb_ has quit IRC17:10
*** mariannelm has joined #openstack-meeting-317:10
dansmithdtp: okay -- are you interested in doing that consoleauth change? I mean, if melwitt is willing to let it go..17:10
*** bpokorny has joined #openstack-meeting-317:10
*** Sukhdev_ has quit IRC17:10
melwittyes, if you'd like to do that one, feel free17:10
*** spzala has quit IRC17:11
dtpsure17:11
dansmithdtp: this: https://github.com/openstack/nova/blob/master/nova/consoleauth/rpcapi.py#L7417:11
dansmithdtp: needs to do cell switching like you see in compute/rpcapi.py17:11
dtpcool, thanks17:12
*** spzala has joined #openstack-meeting-317:12
melwittyeah, the ClientRouter and by_instance17:12
*** Patifa has joined #openstack-meeting-317:12
dansmithdtp: the future of nova now depends on you. don't let us down.17:12
dtpoh lordy17:13
dtp:D17:13
dansmithheh17:13
dansmithokay anything else?17:13
melwitthaha17:13
*** bpokorny_ has joined #openstack-meeting-317:14
dansmithokay then17:14
dansmiththanks17:14
dansmith#endmeeting17:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:14
openstackMeeting ended Wed Dec  7 17:14:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-07-17.00.html17:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-07-17.00.txt17:14
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-07-17.00.log.html17:14
*** jtomasek has quit IRC17:14
*** lpetrut has joined #openstack-meeting-317:14
*** dtp has left #openstack-meeting-317:15
*** notmars has quit IRC17:16
*** spzala has quit IRC17:16
*** bpokorny has quit IRC17:17
*** yamamoto has quit IRC17:18
*** kzaitsev_mb has joined #openstack-meeting-317:21
*** spzala has joined #openstack-meeting-317:22
*** iyamahat has quit IRC17:25
*** kzaitsev_mb has quit IRC17:25
*** spzala has quit IRC17:27
*** spzala has joined #openstack-meeting-317:28
*** baoli has joined #openstack-meeting-317:28
*** paul-carlton2 has quit IRC17:30
*** yamamoto has joined #openstack-meeting-317:32
*** reed has quit IRC17:32
*** spzala has quit IRC17:33
*** dhellmann has quit IRC17:33
*** bobmel_ has quit IRC17:37
*** bobmel has joined #openstack-meeting-317:37
*** gouthamr has quit IRC17:37
*** gouthamr has joined #openstack-meeting-317:39
*** rajinir has joined #openstack-meeting-317:39
*** spzala has joined #openstack-meeting-317:40
*** mariannelm has quit IRC17:43
*** julim has joined #openstack-meeting-317:43
*** spzala has quit IRC17:44
*** spzala has joined #openstack-meeting-317:46
*** paul-carlton2 has joined #openstack-meeting-317:48
*** spzala has quit IRC17:50
*** bobmel has quit IRC17:52
*** iyamahat has joined #openstack-meeting-317:58
*** alaski has quit IRC17:58
*** reedip_ has quit IRC17:58
*** bpokorny_ has quit IRC17:59
*** bpokorny has joined #openstack-meeting-317:59
*** dhellmann has joined #openstack-meeting-318:00
*** reed has joined #openstack-meeting-318:00
*** iyamahat has quit IRC18:01
*** yamahata has quit IRC18:01
*** bobmel_ has joined #openstack-meeting-318:02
*** david-lyle_ is now known as david-lyle18:02
*** jobrs has quit IRC18:03
*** numans has joined #openstack-meeting-318:03
*** bpokorny has quit IRC18:04
*** ralonsoh has quit IRC18:04
*** emagana has joined #openstack-meeting-318:05
*** haleyb_ has joined #openstack-meeting-318:06
*** krtaylor has quit IRC18:06
*** cleong has joined #openstack-meeting-318:06
*** alaski has joined #openstack-meeting-318:06
*** spzala has joined #openstack-meeting-318:06
*** parora has joined #openstack-meeting-318:10
*** mhoppal has quit IRC18:11
*** spzala has quit IRC18:12
*** haleyb_ has quit IRC18:12
*** ibmko has quit IRC18:12
*** spzala has joined #openstack-meeting-318:12
*** VW_ has quit IRC18:13
*** yamamoto has quit IRC18:13
*** prateek_ has quit IRC18:13
*** reed has quit IRC18:14
*** VW has joined #openstack-meeting-318:14
*** dhellmann has quit IRC18:15
*** spzala has quit IRC18:17
*** VW_ has joined #openstack-meeting-318:17
*** spotz is now known as spotz_zzz18:18
*** VW has quit IRC18:19
*** VW_ has quit IRC18:21
*** prateek has joined #openstack-meeting-318:21
*** iyamahat has joined #openstack-meeting-318:22
*** spzala has joined #openstack-meeting-318:23
*** matjazp_ has quit IRC18:24
*** parora has quit IRC18:24
*** lpetrut has quit IRC18:24
*** rickflare has quit IRC18:26
*** spzala has quit IRC18:27
*** rickflare has joined #openstack-meeting-318:31
*** paul-carlton2 has quit IRC18:39
*** s3wong has joined #openstack-meeting-318:40
*** sambetts is now known as sambetts|afk18:40
*** prateek has quit IRC18:43
*** spzala has joined #openstack-meeting-318:43
*** ocartier has joined #openstack-meeting-318:44
*** irenab has joined #openstack-meeting-318:45
*** spzala_ has joined #openstack-meeting-318:45
*** armax has joined #openstack-meeting-318:46
*** spzala_ has quit IRC18:47
*** spzala_ has joined #openstack-meeting-318:47
*** spzala has quit IRC18:48
*** ocartier has quit IRC18:57
*** armax has quit IRC19:03
*** armax has joined #openstack-meeting-319:06
*** haleyb_ has joined #openstack-meeting-319:07
*** VW has joined #openstack-meeting-319:09
*** VW has quit IRC19:09
*** VW has joined #openstack-meeting-319:09
*** VW has quit IRC19:09
*** VW has joined #openstack-meeting-319:10
*** bpokorny has joined #openstack-meeting-319:10
*** bpokorny has quit IRC19:10
*** bpokorny has joined #openstack-meeting-319:11
*** haleyb_ has quit IRC19:16
*** haleyb_ has joined #openstack-meeting-319:16
*** krtaylor has joined #openstack-meeting-319:17
*** julim has quit IRC19:18
*** kzaitsev_mb has joined #openstack-meeting-319:22
*** ociuhandu has quit IRC19:24
*** Sukhdev has joined #openstack-meeting-319:25
*** tqtran has joined #openstack-meeting-319:26
*** irenab has quit IRC19:28
*** irenab has joined #openstack-meeting-319:30
*** ianychoi has quit IRC19:30
*** gouthamr has quit IRC19:30
*** qwebirc32268 has joined #openstack-meeting-319:31
*** qwebirc32268 has quit IRC19:32
*** gouthamr has joined #openstack-meeting-319:33
*** armax has quit IRC19:37
*** piet has joined #openstack-meeting-319:39
*** bpokorny has quit IRC19:41
*** bpokorny has joined #openstack-meeting-319:41
*** irenab has quit IRC19:44
*** bpokorny has quit IRC19:45
*** bpokorny has joined #openstack-meeting-319:49
*** irenab has joined #openstack-meeting-319:51
*** dhellmann_ has joined #openstack-meeting-319:52
*** VW_ has joined #openstack-meeting-319:53
*** r1chardj0n3s has joined #openstack-meeting-319:54
*** VW has quit IRC19:56
*** clu_ has joined #openstack-meeting-319:56
*** rdopiera has joined #openstack-meeting-319:57
*** VW_ has quit IRC19:57
*** ducttape_ has joined #openstack-meeting-319:58
*** VW has joined #openstack-meeting-319:59
*** dhellmann_ is now known as dhellmann19:59
r1chardj0n3s#startmeeting horizon20:00
openstackMeeting started Wed Dec  7 20:00:23 2016 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
*** irenab has quit IRC20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
ediardoo/20:00
r1chardj0n3so/20:00
*** VW has quit IRC20:00
*** VW_ has joined #openstack-meeting-320:00
lcastello/20:00
rhagarty_0/20:01
*** robcresswell has joined #openstack-meeting-320:01
ducttape_o/20:01
r1chardj0n3sso, Ocata-2 is next week (ohmygosh)20:01
r1chardj0n3s#topic Priority patches for review20:02
*** openstack changes topic to "Priority patches for review (Meeting topic: horizon)"20:02
r1chardj0n3s#link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open now has some angularjs panels listed, will add more20:02
david-lyleo/20:02
*** VW_ has quit IRC20:02
*** VW has joined #openstack-meeting-320:02
r1chardj0n3sI've started adding the priority angularjs panels to that list, and will add some more. Trying to limit it to just the ones that are most likely to be completed in this release.20:02
r1chardj0n3sie. the ones that have table, create, delete and edit actions at least partially implemented20:03
ediardoCheck this https://review.openstack.org/#/c/366957/20:03
clu_o/20:03
*** reed has joined #openstack-meeting-320:03
robcresswellr1chardj0n3s: Nothing on Users?20:03
ducttape_ediardo - would like to follow up on that link later20:04
r1chardj0n3srobcresswell: which user patches?20:04
robcresswellhttps://review.openstack.org/#/c/336394/20:04
robcresswellJust that I would imagine there is more demand for Users to be functional than Roles, no?20:05
rdopierao/20:05
ducttape_I'd agree that users and projects are more heavily used than roles robcresswell20:05
r1chardj0n3srobcresswell: yep, absolutely. I just somehow didn't see that patch when I skimmed ... will add to the priorities etherpad :/20:05
robcresswellCool20:06
r1chardj0n3sstarred!20:06
robcresswellThere's also a whole instances implementation sat in searchlight ui if someone wants to look at porting that20:06
robcresswellWould also be a good panel to improve *hint hint*20:06
robcresswell:)20:06
r1chardj0n3sagreed20:06
r1chardj0n3sany other users patches i've omitted from the priority list?20:07
robcresswellNot sure atm, I threw a tantrum at everyone using identity-tables blueprint and -1'd them all20:07
robcresswellIt had like 100 patches so I've no idea what was relevant20:07
r1chardj0n3shttps://review.openstack.org/#/c/342170/ perhaps20:08
*** irenab has joined #openstack-meeting-320:08
ducttape_I have a cinder patch that is old as dirt, around quotas20:08
r1chardj0n3sand https://review.openstack.org/#/c/361529/20:08
robcresswellyeah, looks like there are a few on there. Either way, it would be great to focus on getting Users in a good position especially while we have the Keystone meeting each week20:09
ducttape_but the quota rework is probably the thing to focus on20:09
*** haleyb_ has quit IRC20:09
robcresswellducttape_: Yeah, has quota reworks gone stale? Or is that still a thing?20:09
r1chardj0n3swe still need a solution for search-first to replace the user listings in other parts of our UI20:09
r1chardj0n3sI think I was throwing ediardo or lcastell at that problem tho20:09
robcresswell\o/20:10
ediardo\o/20:10
ducttape_quota rework is a thing, just can't get enough time to work on it.   welcome any all help20:10
clu_(https://blueprints.launchpad.net/horizon/+spec/ng-users exists, so we can link to that instead)20:10
r1chardj0n3sducttape_: got links?20:10
ducttape_https://review.openstack.org/#/c/309204/   is the old one20:10
ducttape_it is ready for review, could be merged20:10
ducttape_well, except jenkins, but it is close to done / ready20:11
robcresswellducttape_: I'm pretty swamped right now, freed myself up and immediately got a ton of work. Plus internally I've got Kubernetes work. My career plan has just become "follow david-lyle"20:11
robcresswellCan review though20:11
ducttape_k20:11
robcresswellclu_: Thanks for that!20:11
ducttape_quota rework needs to be rebased and redo all the tests still https://review.openstack.org/#/c/356605/20:11
r1chardj0n3sif anyone feels like a patch should be priority please let me know even outside of this meeting :-)20:12
r1chardj0n3sducttape_: ack20:12
r1chardj0n3s#topic Integration tests are broken, getting no attention at all, and should be removed altogether20:12
*** openstack changes topic to "Integration tests are broken, getting no attention at all, and should be removed altogether (Meeting topic: horizon)"20:12
r1chardj0n3s... discuss20:12
ducttape_I think the out right broken things have been corrected pretty quickly (in the last few weeks), we have master - 5 days in our lab right now20:13
rdopieraeven the simple tests we have are still useful20:13
rdopieraI found a bug with one yesterday20:13
rdopierathe problem is, nobody knows how they work or how to run them locally20:14
r1chardj0n3swe don't have a plan for stability in the gate20:14
r1chardj0n3swe don't have anyone in the community who has fixing them as a priority20:14
robcresswellrdopiera: They've been failing and non-voting for months20:14
rdopierarobcresswell: one is voting20:14
r1chardj0n3srdopiera: do you mean tempest?20:14
lcastellif they can pass along the knowledge to us, we have some hands available20:14
rdopierar1chardj0n3s: yes20:14
r1chardj0n3srdopiera: that's not really a test ;-) it just checks the login screen appears20:15
rdopierar1chardj0n3s: well, it's a test if it finds bugs, and it found one yesterday20:15
david-lyler1chardj0n3s: it does a bit more20:15
r1chardj0n3sit's still worth having, sure20:15
david-lyleit tests that login work20:15
rdopieradavid-lyle: by the way, I will ask you for some help with that later20:15
rdopieradavid-lyle: if you don't mind20:16
*** spzala_ has quit IRC20:16
robcresswellYeah, it also runs through static collecting and compressing as part of the setup, so settings issues will be caught too.20:16
david-lylewhatever help I can provide20:16
r1chardj0n3slcastell: perhaps, if we can get you and timur talking20:16
rdopierar1chardj0n3s: I'd like to try and get that to work20:16
lcastellyep20:16
rdopierar1chardj0n3s: the non-voting tests, I mean20:16
rdopierar1chardj0n3s: if I fail, we can revisit the issue20:16
r1chardj0n3sthe basic issue though isn't with any specific tests, it's with the fragility of the whole setup20:16
ediardoYes, let me know , I can help too20:17
r1chardj0n3swe are constantly being broken by some new release of firefox or selenium20:17
*** spzala has joined #openstack-meeting-320:17
david-lyleor some timeout20:17
r1chardj0n3sor some timeout20:17
rdopierawell, that's modern software development :)20:17
*** stevejims has joined #openstack-meeting-320:17
rdopieraor leftpad.js20:17
*** stevejims has left #openstack-meeting-320:17
r1chardj0n3snode.js programming language issues don't tend to be the cause of breaking our selenium tests20:18
david-lylebut the noise to signal ratio is much too high for anyone to actually think their new code may have broken something20:18
robcresswellNo, this was next level stuff20:18
*** rbak has quit IRC20:18
robcresswellWe had like a 25% pass rate on functioning code before we disabled them20:18
robcresswelland thats when they were "working"20:18
*** rbak has joined #openstack-meeting-320:18
david-lyleI'd prefer we focused on getting unit tests passing on xenial first20:18
r1chardj0n3sediardo / lcastell I will put you in touch with timur to discuss a way forward20:19
lcastellsounds good20:19
robcresswellIt's pretty cryptic syntax too, which doesnt help a great deal.20:19
robcresswelldavid-lyle: UTs fail on Xenial?20:19
ediardook, ty20:19
r1chardj0n3sdavid-lyle: our tests don't pass on xenial??20:19
lcastellwe already talk about it las mid cycle so...20:19
tqtran0/ sorry im late, just caught up with the script20:19
david-lyler1chardj0n3s: nope20:20
r1chardj0n3sdavid-lyle: I'm confused, becuase I see tests passing20:20
*** irenab has quit IRC20:20
david-lyletwo failing non-voting runs at the bottom of every patch20:20
*** stanchan has joined #openstack-meeting-320:20
r1chardj0n3sdavid-lyle: but that's the selenium tests we've been talking about20:21
robcresswellthats the integration tests20:21
david-lyleselenium and integration tests are two very different things20:21
*** VW has quit IRC20:21
david-lylethe selenium tests pass generally20:21
*** spzala has quit IRC20:21
david-lylenot in xenial because the xvfb lib is not installed by default20:22
*** VW has joined #openstack-meeting-320:22
david-lyleany more20:22
r1chardj0n3sdavid-lyle: that's part of the whole mess of issues around ubuntu breaking selenium with firefox/selenium (And now xvfb) releases that break us, yes20:22
david-lyleoh nevermind20:23
robcresswellYeah, the xenial issue might be new, but those integration test runs were set to non-voting before that point20:23
david-lylethe tests are different but I didn't see the xenial was integration20:23
r1chardj0n3ssure, the selenium and integration suites are two separate things, but they both *use* selenium and that's the fragility we have20:23
robcresswellright20:23
r1chardj0n3sok, I'm gonna see if we can get ediardo and lcastell to fix it, working with timur to extract all his knowledge :-)20:24
rdopierathe alternative is to go blind, which is even more fragility20:24
r1chardj0n3smoving on?20:24
r1chardj0n3s(to something much simpler)20:24
r1chardj0n3s#topic Microversion support20:24
lcastell:)20:24
*** openstack changes topic to "Microversion support (Meeting topic: horizon)"20:24
david-lylepersonally I think that test suite is a waste of time20:24
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-microversion-support is where we’ve been discussing the approach20:24
david-lyleonce it's patched it will break and it's limited in time duration20:24
david-lyleit's half sleep calls20:25
robcresswellrdopiera: Well, they are non-voting, so we are already blind20:25
robcresswellso nothing would change20:25
david-lyleok done20:25
rdopierarobcresswell: I agree that setting anything to non-voting doesn't make any sense -- just disable it20:25
robcresswellr1chardj0n3s: On microversions, I realised we've gone full circle with the approach now20:25
r1chardj0n3srobcresswell: \o/20:25
tqtranso... do we have a replacement in mind? or will horizon not be doing tests at all?20:26
rdopiera3rd system syndrome?20:26
david-lyletqtran: it's only integration tests20:26
r1chardj0n3sok, putting microversions discussion on hold20:26
robcresswelltqtran: Well, we need someone to work on it, and noone is20:26
r1chardj0n3sno, no-one has proposed an alternative to selenium tests20:26
robcresswellSo... thats kinda all there is to it20:26
tqtranok thats fair enough, i cant get those to run locally, so testing them was a PITA to begin with20:26
r1chardj0n3swe have to have that level of testing to have confidence, but only if we can make it work20:26
david-lyleselenium works, integration tests use of selenium does not20:27
*** irenab has joined #openstack-meeting-320:27
robcresswellRight20:27
robcresswellperhaps we should consider more tempest scenarios?20:27
david-lyleI'd prefer that to integration test suite20:28
rdopierasounds reasonable20:28
david-lylewithout massive rework I just don't see the integration tests being useful20:28
david-lylethey've been flaking for 4+ releases20:29
r1chardj0n3sdavid-lyle: what is it in our integration / selenium test suite use of selenium that differs from the tempest use of it?20:29
david-lylethat's not going to change with a few days of love20:29
david-lyler1chardj0n3s: good question20:29
david-lyle:)20:29
david-lyleThe selenium tests are launched the same as any unit test but happen to use selenium20:30
r1chardj0n3sdavid-lyle: 'cos if we don't know that then it's pointless moving everything to tempest if it's just going to be as unstable without fixing the root cause20:30
david-lylewell the login test never fails20:30
david-lyleunless it really should :)20:30
david-lylewhich is rare20:30
robcresswellr1chardj0n3s: Either way, I think there would be more value in having new people look into other options at this stage. The learning curve with the current setup is quite high20:30
robcresswellAlso, I rarely see the tempest test randomly fail :p20:31
tqtranthats because we have like one test in tempest20:31
david-lylebest test ever20:31
r1chardj0n3swe have precisely one test in tempest ;-)20:31
david-lylea scenario test yes20:31
robcresswellMy point was that the setup doesnt collapse20:31
r1chardj0n3sok, we have a couple of folks who are willing to get up to speed on our setup to try to fix it, can we agree to leave the disucssion until they've had a look at it?20:32
david-lylepeople maintain tempest, rolling our own demon spawn testing suite is silly20:32
*** gouthamr has quit IRC20:32
david-lyleno20:32
robcresswellAnd there's likely to be more support on adding tempest tests, that hz integration tests, which has precisely one support person right now20:32
david-lyleyou're wasting their time20:32
robcresswellAgree with Dave here20:33
david-lyleI previously was a huge advocate of the integration tests, but the reality has proven it's a lost cause20:33
r1chardj0n3sok, so delete our current integration and selenium tests and start from scratch20:33
robcresswellMirantis had half a dozen people on them at the start of last(?) cycle20:33
tqtran+120:33
david-lylethat work started before either of you even started on horizon and they have never been stable for any duration20:33
david-lyleselenium is different20:34
tqtranscrap it and start new, i like that plan20:34
david-lyledon't conflate the two20:34
robcresswelltqtran: >.<20:34
r1chardj0n3sdavid-lyle: aren't we the only consumers of selenium in tempest?20:34
r1chardj0n3sdavid-lyle: the integration tests and selenium tests in our code use the same testing framework20:34
david-lylebut one is stable and one is not20:35
r1chardj0n3sbecase?20:35
david-lyleplus we have unit tests that run in selenium and those don't fail either20:35
r1chardj0n3syep20:35
david-lyleremoving integration tests will effect sahara20:35
david-lyleI think they have one or two20:35
*** matjazp has joined #openstack-meeting-320:36
david-lyleunless they have removed them already20:36
david-lyleso our Selenium tests in the unit tests will hit mocked API calls20:37
david-lylethe tempest one should hit a devstack instance20:37
r1chardj0n3syes20:37
david-lyletempest and integration are the closest parallel20:37
r1chardj0n3sok, so it sounds like there's general enthusiasm for deleting that set of deck chairs and creating some new tempest ones :-)20:38
robcresswellAt the very least, have a look at tempest before throwing bodies at the current build.20:38
tqtranquestion, so if we go down the tempest route, are we going to bring selenium with us? or will tempest provide all the things we need?20:38
david-lylesince we have the plugin now, we can add tests without worrying about breaking the world20:38
*** irenab has quit IRC20:38
david-lyleselenium is present in tempest I believe20:39
r1chardj0n3sdavid-lyle: are you able to get ediardo and lcastell up to speed on tempesting?20:39
tqtranoh neato20:39
david-lyleyes my knowledge runs very deep :P20:39
r1chardj0n3serm, you've been asserting that sleenium is in tempest...20:39
david-lyleI think so20:39
*** matjazp has quit IRC20:40
david-lyleI created the plugin and maintain the test, so yes I'm the closest thing we have to an expert20:40
robcresswell\o/20:40
tqtranbtw, is the horizon tempest repo own by horizon drivers?20:41
lcastellbring the knowledge20:41
david-lyleyes20:41
david-lyletqtran:  ^^20:41
*** harlowja has quit IRC20:41
r1chardj0n3sdavid-lyle: do you have a quick linky to that repos pls?20:41
david-lylebut I just +2+A stuff I put in there20:41
david-lylecause20:41
tqtranhm ok, im not seeing it on launchpad (but i trust you)20:41
david-lylehttps://github.com/openstack/tempest-horizon20:42
r1chardj0n3sthanks david-lyle20:42
r1chardj0n3sso, microversions?20:43
robcresswellRight20:43
robcresswellI can't really read the word microversion without getting angry any more20:43
david-lyletqtran: https://review.openstack.org/#/admin/projects/openstack/tempest-horizon,access20:43
david-lylehaha20:43
david-lyleyou're welcome robcresswell20:43
*** kbyrne has quit IRC20:43
robcresswellI'm personally still voting for fixed versions in a list in Horizon20:44
r1chardj0n3sone of the big issues is that we were considering allowing version exclusions in our local specification of versions that work20:44
tqtrani also think a fixed version is going to make life easier for us down the stretch20:44
robcresswellBecause microversions are designed for users to know what version they want, and just hit that version20:44
* ducttape_ is looking forward to tempest having microversions20:45
robcresswellso range may break randomly, and range/exclude is troublesome for the reasons you outlined in the etherpad r1chardj0n3s20:45
robcresswellSo, I think we should just stick to a list of known functional versions20:45
robcresswelllike [3.11, 3.18]20:45
*** irenab has joined #openstack-meeting-320:45
*** kbyrne has joined #openstack-meeting-320:45
r1chardj0n3sbut you were arguing against that because maintenance?20:45
robcresswellIndeed20:46
robcresswellI've transcended arguing to the point where I can just  argue myself into a corner alone now20:46
r1chardj0n3swhereas we can just get the version range from the target service's source code20:46
robcresswellBut I think that list of fixed versions is least shit situation20:46
robcressweller20:47
* robcresswell thinks20:47
rhagarty_version each resource?20:47
r1chardj0n3srhagarty_: sorry, expand on that idea please?20:47
robcresswellrhagarty_: It goes way beyond that, we need to version every feature.20:47
rhagarty_most resources will always continue to work, with latest20:47
david-lyleI think we should be naive and let it fail20:47
david-lyleunless we find something breaking then put some logic in20:48
*** rtheis has quit IRC20:48
ducttape_+120:48
david-lylewe don't keep up with the APIs now20:48
r1chardj0n3sdavid-lyle: could you be more explicit? how should we be naive?20:48
ducttape_this is not all that different from policy20:48
david-lyleand now we're going to validate every nuance of microversion role?20:48
david-lyleassume API calls will work :)20:49
ducttape_write / ship code with little to no checks on micro versions20:49
david-lylethere will be a min version for some20:49
david-lylebut latest should work in almost all cases20:49
david-lyleducttape_: ++20:49
rhagarty_but we need to handle new features introduced in microversions... or we just don't suport?20:50
david-lylethe glaring exception will require code changes via bug fixes20:50
ducttape_the only problem, is that this will build up over time, on the min versions etc20:50
robcresswellrhagarty_: Well, that would be accounted for by a minimum20:50
david-lylemost now don't have a min20:50
ducttape_david-lyle - what if someone is adding a new horizon thing, and they place a min check, on something that is not in a released service yet ?20:50
robcresswellAs in, if service.latest is > minimum, show it, and pray it still works20:51
david-lylejust the newest additions (in our code base)20:51
*** spzala has joined #openstack-meeting-320:51
robcresswellducttape_: Well, it just wouldnt show up20:51
ducttape_I think the reviewers might want to have a rule on that tho20:51
david-lylethe result wouldn't show20:51
david-lylelog it20:51
robcresswellThe problem with this is that Horizon could break in fun and unnoticed ways20:51
ducttape_like don't merge code unless this feature is in a release somewhere20:51
rhagarty_resullt would show... with errors20:51
david-lyleducttape_: ++20:51
r1chardj0n3sa problem with ignoring microversions is that it means we could probably never implement something https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/migrate_server.py#L6520:51
ducttape_nah we can add new things, and have them use a min ---   this is fine / ok I think20:52
david-lylethat looks like a disaster20:52
r1chardj0n3snot that I dream of implementing against an API that mutates every few versions...20:52
robcresswellARGH WHO THOUGHT THIS WAS SMART20:52
robcresswellfuck sake.20:52
rdopieranova...20:53
ducttape_holy shit that link is hurrible20:53
r1chardj0n3s"someone else's problem"20:53
ducttape_r1chardj0n3s we now feel very bad about ourselves   ;)20:53
robcresswellstability is hard, lets push this on to the users and consumers.20:53
r1chardj0n3sso, the point is, that for *some* API calls, we will need mivroversion support20:54
ducttape_agree20:54
david-lyleor say this is too stupid20:54
*** irenab has quit IRC20:54
david-lylewe abstain20:54
robcresswellhahaha20:54
r1chardj0n3sI have proposed that we pull the version ranges directly from the service itself (we can grep to find most of the information)20:54
tqtranlol20:54
rhagarty_cinder likes it... it forces user to specify version in CLI calls, which they can live with. They didn't think through/care about Horizon20:54
ducttape_I think david-lyle and I are saying - avoid the micro version stuff unless you are really painted in a corner20:54
r1chardj0n3sducttape_: and I'm agreeing20:54
rhagarty_I am painted in a corner20:55
r1chardj0n3swe already have one patch up that needs microversion support20:55
robcresswellrhagarty_: Or about anyone not using a CLI20:55
*** spzala has quit IRC20:55
r1chardj0n3sso we need to make sure our approach is sensible (or at least starts out with something that we think is sensible)20:55
robcresswellr1chardj0n3s: So, minimum and *optional* maximum?20:55
ducttape_we are not starting from a sensible place  ;)20:55
r1chardj0n3srobcresswell: yes20:55
david-lylewe still have the vague concept of an integrated release20:56
rhagarty_I added cinder consistency groups, which goes away in 4.0. It is being replaced by generic groups, added in 3.13, 3.14 and generic group snapshots added in 3.1520:56
david-lyleas long as we support the latest MV in those releases, I think that handles most of  it20:56
r1chardj0n3swe have four minutes to go20:56
r1chardj0n3s#topic Mascot20:56
*** openstack changes topic to "Mascot (Meeting topic: horizon)"20:56
r1chardj0n3sjust quickly20:56
*** ociuhandu has joined #openstack-meeting-320:56
robcresswellRight, I'll update the bp to specify minimum and optional maximum20:56
ediardoVery Mascot20:56
david-lylethe legacy of backward compatibility may be lost to microversion purgatory20:56
ducttape_did robcresswell get images ?20:56
david-lyleducttape_: on the MML20:57
robcresswelldid I what now20:57
r1chardj0n3sI really like rdopiera's reworking of the mascot, and weill be feeding that back to them20:57
david-lyle*ML20:57
david-lyler1chardj0n3s: ++20:57
robcresswellYeah, it should be orange and white20:57
* ducttape_ avoids the ml, heads there now20:57
robcresswellnot a husky20:57
r1chardj0n3syep20:57
david-lylerdopiera: did you provide that as feedback on the link?20:57
robcresswellits basically identical to the release one I think20:57
david-lyleducttape_: sorry20:57
*** Sukhdev has quit IRC20:57
rdopieradavid-lyle: what link?20:58
robcresswellOh, I threw another tantrum on twitter at the foundation and the updated me on the logo's to say it'll still be another few weeks to make an svg -.- so I'll probably do it myself20:58
david-lylefeedback link for the mascot20:58
r1chardj0n3srobcresswell: \o/20:58
rdopieradavid-lyle: I saw no feedback link, just the image as an attachment20:58
r1chardj0n3sI didn't include the feedback link in my message because I actually don't know what it is ;-)20:59
david-lyleoh r1chardj0n3s didn't include that part of the email20:59
*** tqtran is now known as tqtran-afk20:59
david-lyleI bet he will now20:59
rdopieraso in short, no20:59
david-lyle:)20:59
r1chardj0n3swww.tinyurl.com/OSmascot20:59
*** bpokorny has quit IRC20:59
r1chardj0n3sis the feedback link20:59
r1chardj0n3sthanks everyone! time's up20:59
r1chardj0n3s#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Dec  7 21:00:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-07-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-07-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-07-20.00.log.html21:00
*** ducttape_ has left #openstack-meeting-321:00
*** dimtruck is now known as zz_dimtruck21:00
*** bpokorny has joined #openstack-meeting-321:00
*** tqtran-afk has left #openstack-meeting-321:00
*** irenab has joined #openstack-meeting-321:01
*** ociuhandu has quit IRC21:01
*** TravT has joined #openstack-meeting-321:01
*** spzala has joined #openstack-meeting-321:01
*** TravT has left #openstack-meeting-321:01
*** rdopiera has left #openstack-meeting-321:02
*** spzala has quit IRC21:03
*** alexismonville has quit IRC21:03
*** spzala has joined #openstack-meeting-321:03
*** bpokorny has quit IRC21:04
*** haleyb_ has joined #openstack-meeting-321:05
*** Sukhdev has joined #openstack-meeting-321:06
*** spzala has quit IRC21:07
*** haleyb_ has quit IRC21:10
*** irenab has quit IRC21:10
*** ociuhandu has joined #openstack-meeting-321:13
*** ociuhandu has quit IRC21:17
*** cleong has quit IRC21:19
*** VW has quit IRC21:20
*** irenab has joined #openstack-meeting-321:21
*** ttrifonov_ has quit IRC21:28
*** ociuhandu has joined #openstack-meeting-321:28
*** kzaitsev_mb has quit IRC21:29
*** irenab has quit IRC21:31
*** ttrifonov has joined #openstack-meeting-321:31
*** ociuhandu has quit IRC21:32
*** srobert has quit IRC21:33
*** yamahata has joined #openstack-meeting-321:33
*** irenab has joined #openstack-meeting-321:38
*** harlowja has joined #openstack-meeting-321:41
*** irenab has quit IRC21:48
*** Patifa has quit IRC21:48
*** bpokorny has joined #openstack-meeting-321:52
*** singlethink has joined #openstack-meeting-321:53
*** ibmko has joined #openstack-meeting-321:54
*** reedip has quit IRC21:55
*** krtaylor has quit IRC21:58
*** irenab has joined #openstack-meeting-321:59
*** Patifa has joined #openstack-meeting-322:06
*** bpokorny has quit IRC22:06
*** lblanchard has quit IRC22:07
*** bpokorny has joined #openstack-meeting-322:07
*** irenab has quit IRC22:07
*** reedip has joined #openstack-meeting-322:08
*** revon has joined #openstack-meeting-322:08
*** alexismonville has joined #openstack-meeting-322:09
*** emagana has quit IRC22:09
*** bpokorny has quit IRC22:11
*** baoli has quit IRC22:12
*** baoli has joined #openstack-meeting-322:13
*** clu_ has quit IRC22:13
*** irenab has joined #openstack-meeting-322:14
*** clu_ has joined #openstack-meeting-322:15
*** baoli has quit IRC22:18
*** irenab has quit IRC22:19
*** emagana has joined #openstack-meeting-322:23
*** emagana_ has joined #openstack-meeting-322:25
*** emagana has quit IRC22:28
*** spzala has joined #openstack-meeting-322:29
*** piet has quit IRC22:29
*** emagana_ has quit IRC22:29
*** armax has joined #openstack-meeting-322:33
*** spzala has quit IRC22:36
*** sdake has quit IRC22:37
*** Patifa has quit IRC22:38
*** ianychoi has joined #openstack-meeting-322:40
*** alexismonville has quit IRC22:42
*** krtaylor has joined #openstack-meeting-322:42
*** absubram has quit IRC22:43
*** Patifa has joined #openstack-meeting-322:45
*** bpokorny has joined #openstack-meeting-322:49
*** tonytan4ever has quit IRC22:49
*** Patifa has quit IRC22:54
*** egallen has joined #openstack-meeting-322:54
*** egallen has quit IRC22:56
*** armax has quit IRC23:03
*** haleyb_ has joined #openstack-meeting-323:06
*** piet has joined #openstack-meeting-323:11
*** haleyb_ has quit IRC23:11
*** armax has joined #openstack-meeting-323:12
*** Patifa has joined #openstack-meeting-323:15
*** harlowja has quit IRC23:16
*** bpokorny has quit IRC23:16
*** bpokorny has joined #openstack-meeting-323:16
*** sdake has joined #openstack-meeting-323:17
*** david-lyle_ has joined #openstack-meeting-323:20
*** bpokorny has quit IRC23:20
*** david-lyle_ has quit IRC23:20
*** bpokorny has joined #openstack-meeting-323:20
*** sdake has quit IRC23:20
*** zz_dimtruck is now known as dimtruck23:26
*** armax has quit IRC23:34
*** piet has quit IRC23:41
*** kenji-i_ has quit IRC23:43
*** sdake has joined #openstack-meeting-323:50
*** kenji-i has joined #openstack-meeting-323:54
*** sdake has quit IRC23:57
*** sdake has joined #openstack-meeting-323:57

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