Wednesday, 2017-08-30

*** hongbin has quit IRC00:23
*** Swami has quit IRC00:30
*** wanghao has joined #openstack-meeting-300:39
*** shuyingya has joined #openstack-meeting-300:41
*** skelso has joined #openstack-meeting-300:41
*** sekelso has joined #openstack-meeting-300:42
*** pvaneck has quit IRC00:43
*** shuyingy_ has joined #openstack-meeting-300:44
*** shuyingya has quit IRC00:45
*** zhurong has joined #openstack-meeting-300:45
*** skelso has quit IRC00:46
*** shuyingy_ has quit IRC00:56
*** rama_y has quit IRC01:04
*** annegentle has joined #openstack-meeting-301:12
*** baoli has joined #openstack-meeting-301:13
*** wanghao_ has joined #openstack-meeting-301:17
*** shuyingya has joined #openstack-meeting-301:18
*** wanghao has quit IRC01:21
*** shuyingya has quit IRC01:23
*** shuyingya has joined #openstack-meeting-301:23
*** galstrom_zzz is now known as galstrom01:41
*** diablo_rojo has quit IRC01:45
*** julim has joined #openstack-meeting-301:50
*** gcb has joined #openstack-meeting-301:58
*** kukacz has quit IRC02:00
*** kukacz has joined #openstack-meeting-302:01
*** benj_ has quit IRC02:17
*** benj_ has joined #openstack-meeting-302:21
*** salv-orlando has joined #openstack-meeting-302:26
*** yamamoto has joined #openstack-meeting-302:30
*** gouthamr has quit IRC02:46
*** yamamoto has quit IRC02:48
*** baoli has quit IRC02:54
*** baoli has joined #openstack-meeting-302:55
*** bobh has joined #openstack-meeting-302:56
*** galstrom is now known as galstrom_zzz02:56
*** iyamahat has quit IRC03:18
*** iyamahat has joined #openstack-meeting-303:18
*** iyamahat has quit IRC03:23
*** TuanLA has joined #openstack-meeting-303:23
*** yamahata has quit IRC03:27
*** sekelso has quit IRC03:30
*** wanghao_ has quit IRC03:32
*** armstrong has joined #openstack-meeting-303:32
*** wanghao has joined #openstack-meeting-303:33
*** yamamoto has joined #openstack-meeting-303:33
*** bobh has quit IRC03:37
*** yamamoto has quit IRC03:41
*** trungnv has joined #openstack-meeting-303:43
*** trungnv_ has joined #openstack-meeting-303:43
*** trungnv has quit IRC03:43
*** trungnv_ has quit IRC03:43
*** trungnv has joined #openstack-meeting-303:45
*** baoli has quit IRC03:51
*** annegentle has quit IRC03:52
*** trungnv has quit IRC04:21
*** trungnv has joined #openstack-meeting-304:24
*** kaz has joined #openstack-meeting-304:24
*** diablo_rojo has joined #openstack-meeting-304:28
*** rstarmer has quit IRC04:43
*** diablo_rojo has quit IRC04:43
*** rstarmer has joined #openstack-meeting-304:43
*** yamahata has joined #openstack-meeting-304:45
*** wanghao_ has joined #openstack-meeting-304:57
*** chyka has quit IRC04:58
*** wanghao has quit IRC04:58
*** salv-orlando has quit IRC04:58
*** shuyingy_ has joined #openstack-meeting-305:01
*** rama_y has joined #openstack-meeting-305:03
*** shuyingya has quit IRC05:04
*** vmud213 has joined #openstack-meeting-305:10
*** gcb has quit IRC05:10
*** gcb has joined #openstack-meeting-305:11
*** lpetrut has joined #openstack-meeting-305:22
*** shu-mutou-AWAY is now known as shu-mutou05:22
*** salv-orlando has joined #openstack-meeting-305:23
*** TuanLA has quit IRC05:26
*** TuanLA has joined #openstack-meeting-305:27
*** rama_y has quit IRC05:31
*** armstrong has quit IRC05:42
*** pgadiya has joined #openstack-meeting-305:47
*** marios has joined #openstack-meeting-305:48
*** wanghao has joined #openstack-meeting-305:59
*** yamamoto has joined #openstack-meeting-305:59
*** kaz has quit IRC06:00
*** vishwana_ has quit IRC06:02
*** wanghao_ has quit IRC06:02
*** vishwanathj has joined #openstack-meeting-306:03
*** anilvenkata has joined #openstack-meeting-306:04
*** cgoncalves has quit IRC06:05
*** cgoncalves has joined #openstack-meeting-306:06
*** anilvenkata has quit IRC06:08
*** anilvenkata has joined #openstack-meeting-306:08
*** iyamahat has joined #openstack-meeting-306:19
*** iyamahat has quit IRC06:21
*** iyamahat has joined #openstack-meeting-306:22
*** iyamahat has quit IRC06:23
*** iyamahat has joined #openstack-meeting-306:23
*** iyamahat has quit IRC06:24
*** iyamahat_ has joined #openstack-meeting-306:24
*** iyamahat has joined #openstack-meeting-306:25
*** iyamahat_ has quit IRC06:25
*** rossella_s has quit IRC06:28
*** iyamahat has quit IRC06:29
*** iyamahat has joined #openstack-meeting-306:29
*** iyamahat_ has joined #openstack-meeting-306:30
*** iyamahat has quit IRC06:30
*** iyamahat_ has quit IRC06:35
*** wanghao has quit IRC06:35
*** iyamahat__ has joined #openstack-meeting-306:35
*** wanghao has joined #openstack-meeting-306:36
*** lpetrut has quit IRC06:36
*** iyamahat__ has quit IRC06:38
*** iyamahat__ has joined #openstack-meeting-306:38
*** anilvenkata has quit IRC06:40
*** pcaruana has joined #openstack-meeting-306:43
*** anilvenkata has joined #openstack-meeting-306:49
*** slaweq has joined #openstack-meeting-306:50
*** TuanLA has quit IRC06:54
*** trungnv has quit IRC06:54
*** trungnv has joined #openstack-meeting-306:54
*** TuanLA has joined #openstack-meeting-306:55
*** slaweq has quit IRC06:55
*** lpetrut has joined #openstack-meeting-306:56
*** iyamahat__ has quit IRC06:59
*** iyamahat__ has joined #openstack-meeting-306:59
*** iyamahat_ has joined #openstack-meeting-307:01
*** iyamahat__ has quit IRC07:05
*** lpetrut has quit IRC07:07
*** iyamahat_ has quit IRC07:08
*** david-lyle has quit IRC07:08
*** iyamahat_ has joined #openstack-meeting-307:08
*** david-lyle has joined #openstack-meeting-307:08
*** ralonsoh has joined #openstack-meeting-307:14
*** iyamahat_ has quit IRC07:18
*** iyamahat has joined #openstack-meeting-307:18
*** etingof has quit IRC07:20
*** iyamahat_ has joined #openstack-meeting-307:20
*** MarkBaker has quit IRC07:23
*** iyamahat has quit IRC07:24
*** abalutoiu__ has joined #openstack-meeting-307:38
*** etingof has joined #openstack-meeting-307:40
*** etingof has quit IRC07:47
*** rmart04 has joined #openstack-meeting-307:51
*** yamamoto has quit IRC07:53
*** etingof has joined #openstack-meeting-308:00
*** iyamahat__ has joined #openstack-meeting-308:08
*** lpetrut has joined #openstack-meeting-308:09
*** iyamahat_ has quit IRC08:11
*** wanghao_ has joined #openstack-meeting-308:14
*** wanghao_ has quit IRC08:15
*** wanghao has quit IRC08:15
*** wanghao has joined #openstack-meeting-308:16
*** iyamahat__ has quit IRC08:34
*** baojg has joined #openstack-meeting-308:35
*** MarkBaker has joined #openstack-meeting-308:36
*** yamamoto has joined #openstack-meeting-308:37
*** baojg has quit IRC08:39
*** andreas_s has joined #openstack-meeting-308:44
*** psachin has joined #openstack-meeting-308:44
*** andreas_s has quit IRC08:44
*** andreas_s has joined #openstack-meeting-308:45
*** andreas_s has quit IRC08:46
*** andreas_s has joined #openstack-meeting-308:47
*** andreas_s has quit IRC08:47
*** stendulker has joined #openstack-meeting-308:48
*** TuanLA has quit IRC08:50
*** salv-orlando has quit IRC08:55
*** abalutoiu__ has quit IRC08:56
*** salv-orlando has joined #openstack-meeting-308:57
*** abalutoiu__ has joined #openstack-meeting-308:58
*** MarkBaker has quit IRC09:01
*** TuanLA has joined #openstack-meeting-309:02
*** andreas_s has joined #openstack-meeting-309:10
*** shu-mutou is now known as shu-mutou-AWAY09:10
*** trungnv has quit IRC09:12
*** psachin has quit IRC09:12
*** MarkBaker has joined #openstack-meeting-309:14
*** sambetts|afk is now known as sambetts09:15
*** sergio__ has quit IRC09:22
*** dims has quit IRC09:28
*** trungnv has joined #openstack-meeting-309:30
*** wanghao has quit IRC09:35
*** wanghao has joined #openstack-meeting-309:35
*** wanghao has quit IRC09:36
*** wanghao has joined #openstack-meeting-309:36
*** wanghao has quit IRC09:36
*** baojg has joined #openstack-meeting-309:36
*** wanghao has joined #openstack-meeting-309:37
*** wanghao has quit IRC09:37
*** wanghao has joined #openstack-meeting-309:38
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting-309:38
*** wanghao has quit IRC09:39
*** wanghao has joined #openstack-meeting-309:39
*** wanghao has quit IRC09:40
*** wanghao has joined #openstack-meeting-309:40
*** wanghao has quit IRC09:40
*** baojg has quit IRC09:41
*** wanghao has joined #openstack-meeting-309:41
*** yamamoto has quit IRC09:45
*** yamamoto has joined #openstack-meeting-309:52
*** abalutoiu__ has quit IRC09:56
*** abalutoiu__ has joined #openstack-meeting-309:56
*** sdague has joined #openstack-meeting-309:57
*** dims has joined #openstack-meeting-309:58
*** egallen has joined #openstack-meeting-310:12
*** salv-orlando has quit IRC10:17
*** salv-orlando has joined #openstack-meeting-310:18
*** abalutoiu__ has quit IRC10:23
*** abalutoiu__ has joined #openstack-meeting-310:39
*** egallen has quit IRC10:41
*** egallen has joined #openstack-meeting-310:42
*** egallen has quit IRC10:42
*** egallen has joined #openstack-meeting-310:42
*** egallen has quit IRC10:43
*** egallen has joined #openstack-meeting-310:43
*** egallen has quit IRC10:44
*** admcleod has joined #openstack-meeting-310:44
*** egallen has joined #openstack-meeting-310:44
*** egallen has quit IRC10:44
*** egallen has joined #openstack-meeting-310:45
*** egallen has quit IRC10:45
*** egallen has joined #openstack-meeting-310:46
*** egallen has quit IRC10:46
*** zhurong has quit IRC10:52
*** julim has quit IRC10:58
*** julim has joined #openstack-meeting-310:59
*** MarkBaker has quit IRC11:02
*** abalutoiu_ has joined #openstack-meeting-311:04
*** abalutoiu__ has quit IRC11:06
*** sankarshan has quit IRC11:12
*** sankarshan has joined #openstack-meeting-311:12
*** MarkBaker has joined #openstack-meeting-311:14
*** pbourke has quit IRC11:20
*** iyamahat has joined #openstack-meeting-311:21
*** TuanLA has quit IRC11:22
*** pbourke has joined #openstack-meeting-311:22
*** iyamahat has quit IRC11:22
*** iyamahat has joined #openstack-meeting-311:23
*** abalutoiu_ has quit IRC11:26
*** stendulker has quit IRC11:30
*** ansmith has quit IRC11:36
*** yamahata has quit IRC11:37
*** iyamahat has quit IRC11:38
*** vmud213 has quit IRC11:38
*** shuyingya has joined #openstack-meeting-311:39
*** abalutoiu_ has joined #openstack-meeting-311:40
*** shuyingy_ has quit IRC11:40
*** MarkBaker has quit IRC11:40
*** rstarmer has quit IRC11:41
*** MarkBaker has joined #openstack-meeting-311:41
*** rstarmer has joined #openstack-meeting-311:42
*** coolsvap has joined #openstack-meeting-311:50
*** pgadiya has quit IRC11:54
*** lhx_ has joined #openstack-meeting-311:55
*** egallen has joined #openstack-meeting-311:56
*** psachin has joined #openstack-meeting-311:56
*** prometheanfire has joined #openstack-meeting-311:58
prometheanfiredims: dirk tonyb toabctl11:58
toabctlhi11:59
dimso/11:59
dirko/11:59
* dirk is only lurking11:59
prometheanfire#startmeeting requirements11:59
openstackMeeting started Wed Aug 30 11:59:36 2017 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.11:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:59
*** openstack changes topic to " (Meeting topic: requirements)"11:59
openstackThe meeting name has been set to 'requirements'11:59
prometheanfire#topic rollcall11:59
*** openstack changes topic to "rollcall (Meeting topic: requirements)"11:59
coolsvapo/11:59
prometheanfirecoolsvap: yo12:00
coolsvapprometheanfire: hi12:00
prometheanfiredims: dirk toabctl mind saying hi again :D12:01
dimso/12:01
dimshi12:01
dirkhi12:01
toabctl:)12:01
prometheanfirecool12:01
prometheanfire#topic anything from the queue?12:01
*** openstack changes topic to "anything from the queue? (Meeting topic: requirements)"12:01
*** raildo has joined #openstack-meeting-312:02
prometheanfireno?12:02
prometheanfiregood :D12:02
prometheanfire#topic more ptg planning12:02
*** openstack changes topic to "more ptg planning (Meeting topic: requirements)"12:02
prometheanfiredon't know if others want to do a team photo, but if so we should get a time down12:03
prometheanfire#link https://docs.google.com/spreadsheets/d/18DmI9ydq6dKr4hAcoAN83vYXWn8TV1NEvy09Ll02_Y0/edit#gid=012:03
prometheanfireHere is the current queens requirements itenerary12:04
prometheanfire#link https://etherpad.openstack.org/p/queens-PTG-requirements12:04
prometheanfireanyone have anything related to the ptg they want to say/ask about?12:04
coolsvaphow many sessions do we have ? do you have the link handy?12:06
*** lhx__ has joined #openstack-meeting-312:06
*** raildo has quit IRC12:07
*** egallen has quit IRC12:07
*** lhx_ has quit IRC12:07
*** trungnv has quit IRC12:07
*** ianychoi has quit IRC12:07
*** ruan_he has quit IRC12:07
*** lifeless has quit IRC12:07
*** dasanind has quit IRC12:07
*** calbers has quit IRC12:07
*** kmARC has quit IRC12:07
*** admcleod has quit IRC12:07
*** sergek_ has quit IRC12:07
*** mrhillsman has quit IRC12:07
*** sweston has quit IRC12:07
*** amotoki has quit IRC12:07
*** ianychoi_ has joined #openstack-meeting-312:07
coolsvapgot it12:07
*** admcleod has joined #openstack-meeting-312:07
*** psachin has quit IRC12:07
prometheanfirewe are sharing the infra room but seem to have our own 'track' here https://wiki.openstack.org/wiki/PTG/Queens/Etherpads12:07
prometheanfiremonday/tuesday12:07
*** egallen has joined #openstack-meeting-312:08
prometheanfire#topic freeze status12:09
*** openstack changes topic to "freeze status (Meeting topic: requirements)"12:09
prometheanfirewe unfroze fully, seems to have gone well12:09
prometheanfire#topic open discussion12:09
*** openstack changes topic to "open discussion (Meeting topic: requirements)"12:09
prometheanfireif no one says anything for a min or two I'll close this12:10
*** kei1 has quit IRC12:10
dimsno updates from me prometheanfire12:10
* coolsvap too12:10
*** kbyrne has quit IRC12:10
*** amotoki has joined #openstack-meeting-312:11
prometheanfirewfm12:11
prometheanfire#endmeeting12:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:11
openstackMeeting ended Wed Aug 30 12:11:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-30-11.59.html12:11
*** calbers has joined #openstack-meeting-312:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-30-11.59.txt12:11
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-30-11.59.log.html12:11
* prometheanfire goes back to bed12:11
*** prometheanfire has left #openstack-meeting-312:11
*** kei1 has joined #openstack-meeting-312:11
*** kbyrne has joined #openstack-meeting-312:12
*** shuyingya has left #openstack-meeting-312:15
*** lifeless_ has joined #openstack-meeting-312:22
*** raildo has joined #openstack-meeting-312:22
*** trungnv has joined #openstack-meeting-312:22
*** ruan_he has joined #openstack-meeting-312:22
*** dasanind has joined #openstack-meeting-312:22
*** kmARC has joined #openstack-meeting-312:22
*** sergek_ has joined #openstack-meeting-312:22
*** mrhillsman has joined #openstack-meeting-312:22
*** sweston has joined #openstack-meeting-312:22
*** barjavel.freenode.net changes topic to "more ptg planning (Meeting topic: requirements)"12:22
*** salv-orlando has quit IRC12:25
*** amotoki has quit IRC12:25
*** amotoki has joined #openstack-meeting-312:27
*** egallen has quit IRC12:30
*** egallen has joined #openstack-meeting-312:32
*** ansmith has joined #openstack-meeting-312:41
*** MarkBaker has quit IRC12:42
*** egallen has quit IRC12:42
*** egallen has joined #openstack-meeting-312:44
*** MarkBaker has joined #openstack-meeting-312:54
*** wondra has joined #openstack-meeting-312:59
*** wondra has left #openstack-meeting-313:00
*** shuyingy_ has joined #openstack-meeting-313:01
*** lyan has joined #openstack-meeting-313:04
*** abalutoiu__ has joined #openstack-meeting-313:05
*** gcb has quit IRC13:06
*** skelso has joined #openstack-meeting-313:07
*** abalutoiu_ has quit IRC13:08
*** andreas_s has quit IRC13:11
*** srobert has joined #openstack-meeting-313:15
*** gouthamr has joined #openstack-meeting-313:19
*** annabelleB has joined #openstack-meeting-313:20
*** abalutoiu_ has joined #openstack-meeting-313:24
*** chyka has joined #openstack-meeting-313:25
*** abalutoiu__ has quit IRC13:27
*** chyka has quit IRC13:30
*** abalutoiu__ has joined #openstack-meeting-313:31
*** baoli has joined #openstack-meeting-313:32
*** abalutoiu_ has quit IRC13:34
*** trungnv__ has joined #openstack-meeting-313:36
*** annegentle has joined #openstack-meeting-313:38
*** cleong has joined #openstack-meeting-313:45
*** lucasxu has joined #openstack-meeting-313:48
*** seanhandley has joined #openstack-meeting-313:49
*** zhipeng has joined #openstack-meeting-313:54
seanhandleyhi zhipeng tobberydberg o/13:58
*** zhipeng has quit IRC13:58
tobberydberghi o/13:58
seanhandleyOops - I killed Howard's connection by saying hello :D13:58
seanhandleyI see a few other familiar usernames here too13:58
seanhandleyAre you joining us for the meeting annabelleB ?13:59
annabelleBYup! Just getting settled here13:59
seanhandleyAwesome :-)13:59
seanhandleyOk, time to get started then14:00
seanhandley#startmeeting publiccloud-wg14:00
openstackMeeting started Wed Aug 30 14:00:49 2017 UTC and is due to finish in 60 minutes.  The chair is seanhandley. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: publiccloud-wg)"14:00
openstackThe meeting name has been set to 'publiccloud_wg'14:00
seanhandleyCan folks please add their names to the participants on the Etherpad:14:01
seanhandley#link https://etherpad.openstack.org/p/publiccloud-wg14:01
*** salv-orlando has joined #openstack-meeting-314:01
seanhandleyHopefully Howard will be back shortly14:02
*** marst has joined #openstack-meeting-314:02
seanhandleyAre you joining us adriant ?14:02
tobberydbergIs it vacation time?14:02
seanhandleyYeah, I guess school Summer holidays for most people in August14:03
seanhandley#topic Review Action Points14:03
tobberydbergok ok14:03
*** openstack changes topic to "Review Action Points (Meeting topic: publiccloud-wg)"14:03
seanhandleySo there were no APs last meeting but some from before that still need attention14:04
hogepodgeo/14:04
*** lsell has joined #openstack-meeting-314:04
seanhandleyhi Chris o/14:04
tobberydbergwelcome!14:04
seanhandleyGlad you could join us :)14:04
seanhandleyEtherpad is here: https://etherpad.openstack.org/p/publiccloud-wg14:04
hogepodgeThank you!14:05
lsellSorry I'm late...also joining from the Foundation staff team with Chris and Anne14:05
seanhandleyno worries - happy to have you all here with us :)14:05
*** stendulker has joined #openstack-meeting-314:06
seanhandleyOne previous AP that I need to work on is an initial spec for how the passport tokens might work, but given recent discussion we should probably save that for the time being14:06
seanhandleySo I think we should move straight on to point 214:06
*** pcaruana has quit IRC14:06
seanhandley#topic Passport Scheme14:06
*** openstack changes topic to "Passport Scheme (Meeting topic: publiccloud-wg)"14:06
tobberydbergagree14:06
seanhandleySo, welcome annabelleB hogepodge and lsell14:07
*** rstarmer has quit IRC14:07
seanhandleyI'm going to be proxying Flanders a little here, since it's so late at night in Australia14:07
*** pilgrimstack has joined #openstack-meeting-314:07
seanhandleyI'll dig out the slides he shared via email14:07
pilgrimstacko/14:07
seanhandley#link https://docs.google.com/presentation/d/1Y2_TiSjElnPdNvVtIsco2_PVTtfKdZDMtvL5mmW6E7A/edit#slide=id.g1fc89766ca_0_214:08
tobberydbergnice to have you here pilgrimstack =)14:08
*** zhipeng has joined #openstack-meeting-314:08
seanhandleyhey zhipeng o/14:08
tobberydbergPlease put your name at the etherpad14:08
zhipenghey seanhandley o/14:08
seanhandleyYou too lsell and pilgrimstack ^14:09
seanhandleyHas everyone seen the slides that Flanders put together about the passport scheme ?14:09
*** yankcrime has joined #openstack-meeting-314:09
yankcrimeo/14:09
seanhandleyhey yankcrime o/14:10
tobberydbergyes, have seen that =)14:10
yankcrimehi!14:10
seanhandleySo14:10
seanhandleythe goal is to launch the initial simple version of this scheme at Sydney14:11
seanhandleyThis will take the form of a page at openstack.org/passport14:11
seanhandleywhich will list participating public clouds14:11
seanhandleythe listing will hook up to those cloud's freemium account pages14:11
seanhandleyand we'll have some rough guidelines for the content of those pages themselves to keep it all consistent and sane14:12
zhipengsounds about that14:12
pilgrimstacksounds good to me14:13
lsellI'm definitely on board with this approach, because from Foundation perspective, we want to put a spotlight on OpenStack public clouds, and this gives us a tangible program to promote14:13
*** hongbin has joined #openstack-meeting-314:13
lsellIt will also help us gauge interest to see how we want to carry the program forward14:13
seanhandleyindeed14:14
*** baojg has joined #openstack-meeting-314:14
seanhandleyOne thing I'll add to the etherpad is we want some analytics data from those freemium account pages14:14
seanhandleyand that needs to be fed back to the foundation14:14
seanhandleySo how will that be achieved technically? Does the Foundation have a set of scripts it wants public clouds to drop into their pages?14:14
annabelleBThat’s one why to do it, but that can get a bit messy when we’ve tried that in the past. I might propose that we get the PCs to send us a weekly report? Pros and cons to both approaches, but the later requires them to stay active with us?14:16
hogepodgeIt's not to say the federated billing isn't important or a goal, it just puts the program front in center in a way that encourages early participation.14:16
lsellThat's a good question. I was originally thinking we might track it like we track the outbound links in our commercial marketplace, which would basically give us visibility into how people are going from the o.o/passport landing page out to the providers14:16
annabelleBYes, we can see the exits on our side, we just can’t see any further behavior once they’re on the landing page14:16
*** zhipeng has quit IRC14:16
lsellIt would also be nice to get data back from providers, weekly might be a bit of a high bar, but regularly would be nice :)14:16
*** zhipeng has joined #openstack-meeting-314:17
seanhandleyok, that makes sense14:17
zhipengthe bottom line is that this analytics won't create security holes in participating PCs14:17
zhipengor legal ones14:17
seanhandleyso analytics on openstack.org for the outbound links14:17
lsellI also want to make sure that asking providers to launch a new landing page is feasible if they have existing freemium offerings they want to promote via the program. Asking them to launch a new landing page with tracking in two months might be a hurdle, but y'all would probably know best14:18
tobberydbergWith the way we thought the scheme to work we will get some initial feedback at which cloud the code is registered...14:18
seanhandleythen the expectation is for the public clouds to engage with the foundation re: signups14:18
seanhandleyit'll be easier to track when we introduce a technical solution with codes14:18
pilgrimstackanalytics is too far away from the first goal I think, let's keep that for steps 3 or 4 I think14:19
seanhandleybecause those codes will be redeemed via a service the foundation is in control of14:19
seanhandleybut for now, it has to be more of a manual sharing of info between PCs and the foundation itself14:19
seanhandleyI think the Foundation wants to see interest pilgrimstack14:19
seanhandleyso it's clear if the passport scheme is viable14:19
seanhandleyis that correct folks?14:20
pilgrimstackseanhandley: Yep, The first proposal from lsell should be enought to start14:20
zhipengagree14:20
seanhandleyok14:20
seanhandleylet's move on then14:20
zhipenglet's start with bare minimum and build upon that14:20
tobberydberg+114:20
pilgrimstack+114:20
seanhandleylsell: Regarding making these public clouds create new freemium pages on their domains14:21
rmart04+114:21
pilgrimstackso what this landing page should do ?14:21
seanhandleyGreat question pilgrimstack14:22
tobberydbergRegarding that, last meeting we had a call for PCs to signup to commit to do that before Sydney14:22
lsellAh ok, that's good to know14:22
tobberydbergAlso, what it should consist of14:22
pilgrimstackregister a new account and create a openstack tenant ?14:22
seanhandleyI can see the value in having a specific freemium page that mentions the scheme14:22
pilgrimstack+ Provisionning credit of course14:22
tobberydberglook a little bit further down at the ether..14:22
seanhandleyit reinforces the customer UX14:22
lsellI can definitely see the value...I was just worried because if I went to my web team right now with a new project that needed to be launched before Sydney they might shoot me :)14:22
lsellThat said..this passport program page is in the queue, so no worries :)14:23
seanhandleyhehe, well that's good then :)14:23
seanhandleyRegarding openstack.org/passport - are we willing to launch it without any public clouds on it and a "Coming Soon" sort of message?14:24
zhipengi think for start we could just provide a summary of the participating PC's current promo schems at the moment14:24
zhipengof course those are related to Open Passport14:24
seanhandleyor do we only want it world visible once we have agreed participation from a number of clouds?14:24
zhipengwe could indicate that by Vancouver we want to have a single entrance14:24
zhipengand federate billing14:24
lsellI would suggest we wait and launch it once we have it set up, and not make promises for the future until we start making progress in that direction...14:25
seanhandleyOk14:25
seanhandleySo one thing we should discuss is what the guidelines for the freemium pages should be14:26
lsellJust logistically, we're probably not going to be able to focus on building out a page until we get through the PTG, but I also think it's something we can really "launch" at Sydney if that makes sense...work with all of the participating companies to put together a press release, promote, advertise, etc.14:26
seanhandleyI guess the Freemium page should have consistent branding at least - maybe even an OpenStack-Powered style image somewhere14:27
zhipengyes agree14:27
lsellYes, that would be nice14:27
rmart04sounds good14:28
seanhandley"OpenStack Passport Partner" or something :)14:28
seanhandleyWe're not going to get very far by making stipulations about how their freemium accounts should work at this stage14:29
seanhandleybecause they'll all be slightly different14:29
tobberydberg+114:29
*** VW has joined #openstack-meeting-314:29
pilgrimstack+114:29
seanhandleyso I don't know what other guidelines to enforce for those freemium pages, really.14:30
seanhandleyAny ideas?14:30
lsellWell, I am curious how much you think the sign up process/requirements differ among each provider...our team has signed up for a couple of different trial programs, and some seem super easy while others are a bit more cumbersome.14:30
*** sekelso has joined #openstack-meeting-314:30
pilgrimstackThis should include the quickest steps to register an account and start with a tenant with some creadit14:31
*** skelso has quit IRC14:31
tobberydbergShould we really interfere with how each cloud would like to design the signup process?14:31
zhipengat the first stage the signup should be something like an intent of participation, should be enough14:31
zhipengwhen we work out the federated system, then we could actually enforce freemium setups and so forth14:31
zhipengpilgrimstack yes that makes sense14:31
zhipengso for guideline, at the moment may each PC should have a dedicated promo page for open passport14:31
zhipengand have the logo on the web page14:32
lsellI don't think we can interfere, but I do want to make sure we're promoting good experiences14:32
pilgrimstack@OVH this means creating an OVH account, ordering a public cloud project (the tenant) and inject the credit14:32
zhipengsignup left to each provider at the moment14:32
tobberydbergok lsell agree with that14:32
seanhandleyI guess this page could at least give simple instructions for how to sign up14:33
seanhandleyand then a button to click to begin that process14:33
tobberydbergYes, bare minimum14:33
seanhandleythen longer term we can make expectations for signup flow14:33
pilgrimstackseanhandley: as a very first step I think it's easy for everybody14:33
zhipengor each PC have a button so after clicking it goes to the specific program ?14:33
seanhandleyok - so the freemium page just gives clear instructions - it doesn't change any established UX14:34
lsell+114:34
tobberydberg+114:34
seanhandleySimple enough!14:34
lsellwe can just distribute a logo/graphic and some language to use on each landing page14:34
zhipenglsell +114:34
rmart04+1 (I’d expect providers are already trying to streamline their setup processes as best they can!)14:34
seanhandleyPerfect lsell14:34
seanhandley+114:35
lsellagree about not having requirements for sign up process, but i think this team does need some criteria or grounds to reject a provider if it's just a terrible experience....14:35
annabelleB+114:35
tobberydberg+114:35
seanhandley+114:35
hogepodge+114:35
seanhandleyDo we have a metric for how terrible the UX is?14:36
seanhandleyOr will this be a value judgement?14:36
zhipengno dedicated open passport landing page ?14:36
zhipengif a provider just randomly point it to something14:36
zhipengthen it should get rejected14:36
lsellso as we're reaching out to our public cloud provider database, we can say "here's how you participate, but please note we'll be testing your program to ensure it meets quality..." (something better worded than that)14:36
*** galstrom_zzz is now known as galstrom14:37
seanhandleyOk, that needs defining14:37
annabelleBI don’t think they need to have a dedicated passport page, but they need to have a clear “Sign up for a free trial here” page14:37
seanhandleyand it's clear someone will need to act as a gateway for who we accept and who we don't accept14:37
zhipengi'm thinking David ? :P14:37
hogepodgeI would suggest a Foundation staff member along with one or two members of this working group, to make sure it's community driven.14:38
*** lpetrut has quit IRC14:38
seanhandleyOk. I'm happy to help, as I'm sure are my co-chairs zhipeng and tobberydberg :)14:39
lsellAgree, Foundation can be neutral because you don't want it to turn into a political or competitive thing, but we definitely need this team to weigh in and help make a judgment call14:39
rmart04I’d hope that if PC’s are spending the time to get involved in this process they aren’t going to be sending people in circles once they try to signup but agree that it should be well defined…14:39
tobberydbergSome page that meets the requirements for a good UX, mentioning something like "OpenStack Passport Partner" or logo etc14:39
seanhandleyWe're nearly 40 mins in so let's think of some action items :)14:39
seanhandleylsell hogepodge annabelleB: How were you thinking we'd reach out to people about the scheme?14:40
seanhandleyEmail?14:40
seanhandleywhen I say people, I mean public clouds14:41
tobberydbergI believe that most important is to get some basics up describing what we are saying here, so that it's clear for all whats the latest14:41
zhipeng++14:41
tobberydbergseanhandley: of course happy help out there as well14:41
zhipenga mission statement paragraph on PCWG wiki ?14:42
*** egallen has quit IRC14:42
tobberydberg...and with getting that first version up...14:42
lsellDanny Carreno on Foundation team has a database of all the public cloud providers we have relationships with (as foundation sponsors, in the marketplace, etc.). I think we should basically draft an email in an etherpad that he can send to all of the providers to start recruiting. We just need to figure out the immediate call to action and deadline for them to participate14:43
tobberydberg+114:43
seanhandley+114:43
*** egallen has joined #openstack-meeting-314:43
tobberydbergAnd, a good desciption of what they are supposed to signup for =)14:44
rmart04+114:44
lsellI believe there are about 25 providers, and I would be very happy if we even just had 4-5 on board for launch...but it's a good practice to give everyone a heads up. I have a feeling there are some public cloud folks who don't even know about this working group14:44
*** abalutoiu__ has quit IRC14:44
yankcrimeis the foundation's long-term expectation that customers would continue to buy credit via the passport scheme to use with participating public cloud providers?14:44
hogepodgeWould announcing a cfp on a mailing list be a good way to make sure that everyone has a chance to hear?14:45
lsellNot necessarily, no14:45
pilgrimstackwhen we deal OVH vouchers, we have 2 kind of vouchers. 1. No Credit Card required but we delete the ressource at the end, 2. Credit Card required and the user can keep his ressources after the credit expiration14:45
tobberydbergAP: seanhandley zhipeng and myself to have that description up by next meeting ??14:45
seanhandley#action Draft an email inviting a public cloud to participate in the scheme https://etherpad.openstack.org/p/passport-scheme-email-draft14:45
lsell(my no was for yankcrime)14:45
seanhandley#link https://etherpad.openstack.org/p/passport-scheme-email-draft14:45
lsell+1 mailing list14:45
seanhandleytobberydberg: sounds good :)14:46
yankcrimethanks lsell14:46
pilgrimstackdo you also have this both kind of vouchers?14:46
zhipenglet's draft the email first, then hit ml and individual PCs at the same time14:46
tobberydberg#action seanhandley zhipeng and myself to have description of passport up by next meeting14:46
seanhandley+1 zhipeng14:46
seanhandleyI'd imagine a lot of the public clouds don't follow the mailing lists very closely14:47
seanhandleyor perhaps their tech teams do and their management teams don't14:47
yankcrimefor sure they don't, i can think of at least one that will be unaware of this passport work (but which will want to participate)14:47
tobberydbergThey don't, and hard to do as well... Think the best way is via lsell and the DB of PCs14:48
*** annegentle has quit IRC14:48
lsellShould our goal be to distribute the email early next week? Monday is a holiday in the US, but we could go Tuesday or Wednesday14:48
pilgrimstackto simplify my question, will you take the credit card of the user before opening the tenant ? because that's a big question for us14:48
lsellthat is a good question14:48
seanhandleyI don't think it matters pilgrimstack - not at this stage14:49
hogepodgeI prefer to not require a credit card, because it's a real barrier to entry. I understand the desire to convert users to paying customers.14:49
seanhandleycredit card verification is a reasonable anti fraud measure14:49
seanhandleyparticularly with free accounts14:49
hogepodgeThere's that too.14:49
zhipengi think if we offer promo code, credit card should not be required14:49
tobberydbergThink that will have to be left for each PC14:50
seanhandleyhogepodge: You should see how many of our signups drop off at credit card entry stage :D14:50
yankcrimehogepodge: too many bad actors out there to do otherwise14:50
* yankcrime nods14:50
zhipengand seanhandley do we require SSO with openstack foundation id ?14:50
seanhandleyok back to what you said lsell14:50
seanhandleyI think aiming to mail out next week could work just fine14:50
seanhandleyI think there'll need to be some collaboration on the etherpad link I shared above14:51
seanhandleyand some communication between the foundation and this WG14:51
lsellOK, we'll also try to work on a proposed timeline between now and Sydney in the same etherpad14:51
seanhandleyshould I contact you regarding the mailout next week lsell ?14:51
lsellYes, that would be great. I want to get buy in on the email and timeline from this group before we pull the trigger14:51
seanhandleyif the text is ready then the Foundation can mail out to its list - then the WG can announce to the mailing lists ?14:52
seanhandleyperfect14:52
lsellyes, that sounds great14:52
tobberydbergWe don't need a clear description of the "OpenStack Passport" before sending the email?14:52
seanhandleyI'll get in touch with you Monday via your foundation address :-)14:52
seanhandley#action Sean to contact Lauren re: mailout text14:52
seanhandleytobberydberg: We definitely do :)14:53
yankcrimetobberydberg i think we do, as well as clear goals / aims14:53
seanhandleytobberydberg: And you're on vacation14:53
lselltobberydberg ideally this email will be a forcing function to get these descriptions documented14:53
tobberydbergok....that basically count me out, just so you know, since I'm not back from vacation until Tuesday next week14:53
lsellwe can also push it back a week, i'm just cognizant that it's almost September (yikes!) so we basically have two months14:53
lsellhow about we plan for the following Monday to distribute emails then?14:54
seanhandleyMonday 11th?14:54
seanhandleySound better tobberydberg ?14:54
lsellYes. We'll be at the PTG, but it shouldn't be hard to just hit send if we get the content worked out next week14:54
tobberydbergLike that better yes14:54
seanhandleyOk14:55
seanhandleyOnce again, I've made an etherpad for drafting that: https://etherpad.openstack.org/p/passport-scheme-email-draft14:55
tobberydbergwe can work out the email in parallel14:55
lsellperfect14:55
seanhandleyok14:56
tobberydberg(of topic ... with everything in the going here ... meeting every week until Sydney? )14:56
seanhandleywe're nearly out of time and I feel like we still have lots to talk about14:56
lselli'm fine with that, but next week i will be on a plane at this same time, just as a heads up14:57
seanhandleyno problem lsell14:57
seanhandley#openstack-publiccloud is probably the best place for this14:57
*** abalutoiu__ has joined #openstack-meeting-314:57
tobberydberg+114:57
seanhandleyand +1 to weekly meetings about it, even if it's just a 10 minute catch up14:57
hogepodgeI can make next week (my plane is in the afternoon).14:58
*** VW has quit IRC14:58
seanhandleyWe still need to decide on the agenda for the fishbowl at OpenStack Days UK next month but we can save that for next WG meeting in 2 weeks14:58
lselloh, and i'll be at openstack days UK!14:58
seanhandleyAwesome :D14:58
tobberydberg#action tobberydberg to suggest weekly meetings instead of bi-weekly metings14:58
*** VW has joined #openstack-meeting-314:58
tobberydbergNice to here that lsell =)14:59
seanhandleyOk, we're out of time - there's usually another meeting right after this one14:59
lsellI also just want to say a HUGE thank you to all of you...I really love these ideas, and you've done an amazing job putting it together. I know you have super busy day jobs, and we really appreciate it14:59
tobberydbergGood work seanhandley!14:59
seanhandleyI'll be around for a while in #openstack-publiccloud if anyone wants to talk more about this right away14:59
*** baoli has quit IRC14:59
seanhandleyThanks lsell - I'm really excited about the scheme15:00
tobberydbergI can stay for a couple of minutes15:00
seanhandleyand I'm really pleased that the Foundation is getting behind it15:00
*** baoli has joined #openstack-meeting-315:00
*** baoli has quit IRC15:00
seanhandleythanks again lsell hogepodge and annabelleB for joining us today15:00
tobberydbergAgree with seanhandley!15:00
zhipenglsell we could take this offline, but quick question on our EU meetup series15:00
annabelleBabsolutely! looking forward to working with you all15:00
zhipengcould foundation do a promotion on that ?15:00
seanhandley#endmeeting15:01
*** openstack changes topic to "more ptg planning (Meeting topic: requirements)"15:01
openstackMeeting ended Wed Aug 30 15:01:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-30-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-30-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-30-14.00.log.html15:01
lsellzhipeng: yes, could you shoot an email to anne@o.o and lauren@o.o ?15:01
zhipengsure no problem :)15:01
*** annegentle has joined #openstack-meeting-315:02
*** annabelleB has left #openstack-meeting-315:03
tobberydberggood initiative zhipeng!15:06
*** baoli has joined #openstack-meeting-315:10
*** vmud213 has joined #openstack-meeting-315:13
*** trungnv__ has quit IRC15:14
*** stendulker has quit IRC15:15
*** stendulker has joined #openstack-meeting-315:16
*** alexpilotti has quit IRC15:16
*** chyka has joined #openstack-meeting-315:16
*** chyka has quit IRC15:17
*** chyka has joined #openstack-meeting-315:19
*** gmann has quit IRC15:22
*** gmann has joined #openstack-meeting-315:22
*** baoli has quit IRC15:23
*** baoli has joined #openstack-meeting-315:24
*** baoli has quit IRC15:25
*** baoli has joined #openstack-meeting-315:26
*** seanhandley has left #openstack-meeting-315:27
*** egallen has quit IRC15:30
*** alexpilotti has joined #openstack-meeting-315:31
*** alexpilotti has quit IRC15:38
*** sekelso has quit IRC15:39
*** salv-orlando has quit IRC15:41
*** shuyingy_ has quit IRC15:42
*** sekelso has joined #openstack-meeting-315:42
*** salv-orlando has joined #openstack-meeting-315:42
*** alexpilotti has joined #openstack-meeting-315:43
*** lsell has left #openstack-meeting-315:47
*** egallen has joined #openstack-meeting-315:48
*** iyamahat has joined #openstack-meeting-315:50
*** georgk has joined #openstack-meeting-315:50
*** zhipeng has quit IRC15:50
*** sekelso has quit IRC15:50
*** zhipeng has joined #openstack-meeting-315:51
*** yamahata has joined #openstack-meeting-315:51
*** shuyingya has joined #openstack-meeting-315:52
*** yankcrime has left #openstack-meeting-315:53
*** gouthamr has quit IRC15:53
*** pcaruana has joined #openstack-meeting-315:54
*** egallen has quit IRC15:54
*** rmart04 has quit IRC15:56
*** shuyingy_ has joined #openstack-meeting-315:56
*** shuyingya has quit IRC15:56
*** Rockyg has joined #openstack-meeting-315:56
*** pilgrimstack has quit IRC16:01
*** marios has quit IRC16:02
eglute#startmeeting interopwg16:02
openstackMeeting started Wed Aug 30 16:02:29 2017 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: interopwg)"16:02
openstackThe meeting name has been set to 'interopwg'16:02
Rockygo/16:02
egluteHello everyone!16:02
eglute#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:02
kgarloffHi16:02
eglute#link https://etherpad.openstack.org/p/InteropVertigo.1316:02
hogepodgeo/16:02
eglute#chair hogepodge16:03
openstackCurrent chairs: eglute hogepodge16:03
georgkhi16:03
zhipengo/16:03
eglutemy IRC client is acting up. in case i dont respond for a while, I will have hogepodge take over16:03
mrhillsmano/16:03
egluteEveryone, please take a look at the agenda, and update as needed https://etherpad.openstack.org/p/InteropVertigo.1316:03
eglute#topic PTG16:04
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:04
eglutePTG is just around the corner!16:04
egluteIf you have not updated yet the etherpad that you will be attending, please do so!16:04
hogepodge#link https://etherpad.openstack.org/p/InteropDenver2017PTG16:04
eglute#link https://etherpad.openstack.org/p/InteropVertigo.1316:04
egluteerr yes on hogepodge link16:05
eglutehttps://etherpad.openstack.org/p/InteropDenver2017PTG16:05
eglutealso, please add suggested topics16:05
*** alexpilo_ has joined #openstack-meeting-316:06
egluteany other comments on PTG?16:06
hogepodgeUnfortunately catherine and paul can't make it, but we'll try to include them and Rockyg with zoom conferences.16:06
RockygThanks!16:07
eglutehogepodge do you know if there will be cameras in the PTG rooms?16:07
egluteor just on our laptops?16:07
*** catherineD has joined #openstack-meeting-316:07
hogepodgeeglute: there won't be. Conference calls are diy for teams.16:07
catherineDo/16:07
eglutehogepodge cool16:07
eglutei have a zoom account!16:07
*** alexpilotti has quit IRC16:08
hogepodgeI do too. :-D16:08
egluteI added a section for remote participants16:08
RockygWe've got zoom we can use now, if that helps16:08
*** salv-orlando has quit IRC16:08
eglutelooks like everyone is switching to zoom :D16:08
Rockygdoh! not enough coffee16:09
egluteanything else on PTG?16:09
egluteif you think you will want to attend remote, please update the etherpad16:10
*** alexpilo_ has quit IRC16:10
eglute#topic Flag a test that requires a second set of user credential16:10
*** openstack changes topic to "Flag a test that requires a second set of user credential (Meeting topic: interopwg)"16:10
eglute#link https://review.openstack.org/#/c/491927/16:10
eglutei re-read it yesterday, and noticed that i missed a question from catherineD16:10
egluteshould the test be removed all together from 2017.09?16:11
eglutei think it should be16:11
catherineDeglute: I can update the patch if that is our decision here16:11
eglutethank you catherineD! what does everyone else think?16:11
hogepodgeWe would need a test to keep the capability.16:12
hogepodgeIt's too late for 2018.01. That's the main question. I think listing projects is important.16:12
hogepodgeDo we have a volunteer to write a new test?16:13
kgarloffhogepodge: listing projects is important, yes16:13
hogepodgeMy suggest would be to keep the test flagged for next, just for that reason, so we don't have an empty capability.16:13
eglutehogepodge i think you are right. i didnt notice that it was the only test16:13
eglutehogepodge agree16:13
kgarloff... until we get a new one ...16:14
egluteagree16:14
hogepodgeyes, to be included in 2018.0[8|9]16:14
eglutei will echo hogepodge: any volunteers to write a new test? :)16:14
hogepodgeI can suggest a volunteer (mguiney) :-)16:15
eglute+1 :D16:15
eglute#action mguiney to write new test for https://review.openstack.org/#/c/491927/16:15
*** pilgrimstack has joined #openstack-meeting-316:15
egluteanything else on this?16:16
catherineDeglute: meanwhile we should merge https://review.openstack.org/#/c/491927/16:16
*** alexpilotti has joined #openstack-meeting-316:16
egluteyes i agree!16:16
eglutedone16:16
eglute#topic Extension programs16:17
*** openstack changes topic to "Extension programs (Meeting topic: interopwg)"16:17
*** zhipeng has quit IRC16:17
eglute#topic Extension programs Designate16:17
*** openstack changes topic to "Extension programs Designate (Meeting topic: interopwg)"16:17
eglute#link https://review.openstack.org/#/c/492635/16:17
*** zhipeng has joined #openstack-meeting-316:18
*** iyamahat has quit IRC16:19
egluteMark has left some comments regarding ipv616:19
*** gouthamr has joined #openstack-meeting-316:19
eglutebut i think otherwise it looks good!16:19
egluteanyone else have comments?16:19
*** iyamahat has joined #openstack-meeting-316:19
*** stendulker has quit IRC16:19
hogepodgeI will send up new patches today for finalization based on the comments. I think we'll be good to present to board if we have consensus next week.16:20
*** alexpilotti has quit IRC16:20
*** iyamahat has quit IRC16:21
*** iyamahat has joined #openstack-meeting-316:21
hogepodgeI will incorporate the ipv6 notes into the guideline as a permanent record of that discussion16:21
eglutethank you hogepodge!16:22
*** iyamahat has quit IRC16:23
egluteeveryone, please leave any last comments if you have them on the patch!16:23
*** iyamahat has joined #openstack-meeting-316:23
egluteI would like to have it merged this week!16:23
eglute#Extension programs Heat16:25
eglute#link https://review.openstack.org/#/c/490648/16:25
eglutethere are some new comments too hogepodge did you see?16:25
eglutebut otherwise it is almost ready as well16:25
*** alexpilotti has joined #openstack-meeting-316:26
hogepodgefeedback from everyone on this last patch would be useful, even if just +1 or -1 for details I can fix up16:26
eglutethanks hogepodge looks good to me :)16:28
eglutei will give my +2 later :)16:28
egluteanything else on heat?16:28
eglute#topic Create rough draft of extension programs16:29
*** openstack changes topic to "Create rough draft of extension programs (Meeting topic: interopwg)"16:29
eglute#link https://review.openstack.org/#/c/472785/16:29
egluteMark is attending a conference this week, so he hasnt had a chance to update it16:30
*** alexpilotti has quit IRC16:30
*** shuyingy_ has quit IRC16:30
eglutethank you hogepodge for reviewing16:30
egluteeveryone else also please do some final reviews16:30
hogepodgeIt's well thought out, just missing some aspects we clarified over the last month or so. Thanks to markvoelker for preparing it.16:30
egluteI agree!16:31
egluteanything else?16:32
*** markvoelker has joined #openstack-meeting-316:32
*** egallen has joined #openstack-meeting-316:32
eglute#topic open floor16:32
*** openstack changes topic to "open floor (Meeting topic: interopwg)"16:32
eglutewe are done with all the topics i had on the agenda16:32
egluteanyone have anything they would like to discuss?16:32
*** trungnv__ has joined #openstack-meeting-316:33
*** zhipeng has quit IRC16:33
*** zhipeng has joined #openstack-meeting-316:33
eglutein that case, everyone, please review the patches today16:33
hogepodgeWow, I think this may be our shortest meeting ever. :-D16:33
egluteand we can end early :)16:33
eglutethanks everyone!!!16:33
Rockygkewl16:33
eglute#endmeeting16:34
*** openstack changes topic to "more ptg planning (Meeting topic: requirements)"16:34
openstackMeeting ended Wed Aug 30 16:34:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:34
hogepodgeThanks everyone!16:34
Rockygthanks!16:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-08-30-16.02.html16:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-08-30-16.02.txt16:34
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-08-30-16.02.log.html16:34
*** zhipeng has quit IRC16:35
*** alexpilotti has joined #openstack-meeting-316:38
*** bobh has joined #openstack-meeting-316:41
*** alexpilotti has quit IRC16:42
*** georgk has quit IRC16:46
*** iyamahat has quit IRC16:49
*** egallen has quit IRC16:52
*** alexpilotti has joined #openstack-meeting-316:53
*** alexpilo_ has joined #openstack-meeting-316:55
*** alexpilotti has quit IRC16:58
dansmith#startmeeting nova_cells17:00
openstackMeeting started Wed Aug 30 17:00:00 2017 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
melwitto/17:00
*** mriedem has joined #openstack-meeting-317:00
mriedemo/17:00
dansmithohai17:00
melwittwelcome mriedem17:01
dansmith#topic bugs17:01
*** openstack changes topic to "bugs (Meeting topic: nova_cells)"17:01
dansmithmriedem: you had a couple in the last week or so right?17:01
mriedemthere is a backport proposed for the guest assisted snapshot one17:01
mriedemhttps://review.openstack.org/#/c/498979/17:01
dansmithcool17:01
mriedemi think that's the only cells v2 bug recently, everything else is placement17:01
dansmithokay cool17:02
*** ralonsoh has quit IRC17:02
dansmithanything else on bugs?17:02
mriedemdo'nt think so17:02
dansmith#topic open reviews17:02
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"17:02
dansmithI don't have anything for this at the moment either, since I'm working on some placement things we need to get done ASAP17:02
mriedemi don't think there are any open reviews for cells v2 that i know of17:03
dansmithanyone else?17:03
dansmithack17:03
dansmith#topic open discussion17:03
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"17:03
dansmithmriedem: you wanted to scheme about ptg things right?17:03
mriedemyes17:03
mriedemhttps://etherpad.openstack.org/p/nova-ptg-queens17:03
mriedemthere are some random things17:03
dansmithI've put a few things on there so far for cells17:03
mriedemthe main things i think are17:04
mriedem1. Use GET /usages from the Placement API for counting quotas rather than iterating cells.17:04
mriedem2. Scheduling alternative hosts in the cell for retries17:04
mriedemedleafe has a spec related to ^17:04
mriedemhttps://review.openstack.org/#/c/498830/17:04
dansmithyep, I took a first pass on that spec,17:04
dansmithalthough it's just a piece of the puzzle17:05
mriedemright it's not the full picture17:05
mriedemjust the data format i think between conductor and scheduler right?17:05
*** iyamahat has joined #openstack-meeting-317:05
dansmithyeah17:05
*** iyamahat has quit IRC17:05
mriedem3. all of the upcall stuff https://docs.openstack.org/nova/latest/user/cellsv2_layout.html#operations-requiring-upcalls17:05
mriedem*all of the "other" upcall stuff17:06
dansmithyeah I need to revisit those things and see what is actionable17:06
melwitton the GET /usages thing the missing piece will be counting instances independent of cells. and the need to keep instance mappings around forever because deleted instances. I was wondering if it would be kosher to add a deleted column to instance mappings to know whether to count17:06
dansmiththe affinity stuff just has to wait for the distance placement stuff17:06
dansmithmelwitt: if it's in placement we count it, and if it's not we don't right?17:07
mriedemmelwitt: knee jerk reaction is we don't want a deleted column on instance_mappings17:07
dansmithyeah, do not want17:07
melwittdoes placement have instances count in it?17:07
*** markvoelker has quit IRC17:07
mriedemno,17:07
mriedemi think that means, GET /allocations/{instance_uuid} returns 404 right?17:08
dansmithright17:08
*** bobmel has quit IRC17:08
mriedemand that would also tied into how GET /usages works when filtering on instance.project_id and instance.user_id17:08
mriedemif the instance is deleted, it shouldn't be in the placement allocations table and it's usages won't be affected by the instance consumer17:08
melwittohhh, I see what you're saying17:08
*** yamahata has quit IRC17:09
dansmithwe should be able to list allocations by project too, so you can get a list of all the instances for a given project/user and that will have consumer ids, which are instances17:09
*** alexpilo_ has quit IRC17:09
melwittsweet.17:09
*** salv-orlando has joined #openstack-meeting-317:09
*** bobmel has joined #openstack-meeting-317:09
melwittthat works for me17:09
mriedemthe counting via placement stuff is all a bit busted right now too with how we're accounting for allocations during a move17:09
mriedemwhich is going to be fixed with dan's migration uuid stuff17:09
dansmithyah17:10
melwittoh, right. so we won't get a double count for a move-in-progress17:10
melwitt?17:10
dansmithwell,17:10
dansmithyou won't if you consider only instances17:10
dansmithbut I think you'll want to consider migrations too so your quota covers things you have in resize_confirm state right?17:10
melwittmaybe, now that it could potentially be consuming twice the resources, I wouldn't want that counting against quota17:11
dansmithno?17:11
mriedemwe don't double account quota during a move today17:12
dansmithI thought there was a request to prevent people from having 20 instances, all in resize_confirm state for a month17:12
dansmithright, but that's a bug right?17:12
mriedemwe pike the bigger parts of the flavor and count that for quota17:12
melwittI didn't think so. well, it would be a regression or rather it will change how quota has been counted17:12
mriedem*pick17:12
melwittbecause this double allocating thing is new right?17:12
mriedemthe double accounting is new17:12
dansmithwell, regardless, right now you can't tell the difference between the two halves of a migration,17:12
dansmithand after my change, counting just the instance allocation will give you the target of the migration, which is what you want17:12
*** Rockyg has quit IRC17:13
dansmithwhether or not we work in the source side is something we can discuss17:13
melwittokay17:13
dansmithbut because of the way I have it set up, it'll just do what you're expecting by default17:13
*** krtaylor has quit IRC17:13
dansmithso we can discuss at the ptg maybe and see what others think17:13
melwittk17:14
dansmithpretty sure I was talking to johnthetubaguy about the migration quota limit thing, so if he's there we can get his input17:14
mriedemi think we'd have to account for the source side17:14
mriedemfor an old flavor that has bigger cpu/ram than the new flavor17:14
*** dims has quit IRC17:14
*** salv-orlando has quit IRC17:14
mriedemotherwise if you resize, then do something else to raise quota, and revert, you could go over quota on the revert17:14
mriedembut yeah i suppose details can be hashed out at the ptg17:15
dansmithI think that's confusing and not what _I_ would want, but yeah, we can argue later17:15
melwittyeah. I suspect you're right though. currently we're considering old flavor or new flavor depending on whether it's an upsize or downsize17:15
mriedemfor multi-cell ci testing,17:16
mriedemi think in boston sdague said he wanted to write some new deployment tooling using ansible or something since devstack/devstack-gate/grenade gets too complicated with all the bash and multiple nodes and such17:17
*** alexpilotti has joined #openstack-meeting-317:17
*** trungnv__ has quit IRC17:17
mriedembut, that seems like a herculian task17:17
dansmithyeah I'm not so sure how likely that is to happen at this point17:17
dansmithyeah17:17
mriedembut i think we should definitely try a 2-cell ci job in queens17:18
*** dims has joined #openstack-meeting-317:18
dansmithwell, I'd like to, but there are a lot of things piling up quickly so I don't want to put it too high on the priority list17:18
dansmithso far,17:18
dansmithI haven't found anything that works with our gate but doesn't with two real cells17:18
dansmithI'm sure there are some, but seems like not too major17:19
*** alexpilotti has quit IRC17:19
dansmithanyway, worth discussion at the ptg, which is what we're doing here17:19
mriedemyeah it doesn't need to be top priority, but if we can at least figure out some of the high level what needs to happen, i know enough about d-g to do some damage17:19
*** alexpilotti has joined #openstack-meeting-317:19
dansmithwoot17:19
mriedemthe efficient listing stuff...17:20
mriedemidk17:20
dansmithI need to sync back up with mdbooth on that, but I'm hoping he's still going to do it.. last I heard from him it sounded like he was,17:20
dansmithbut if he's not we have to get a plan for that I think17:20
melwittI'm willing to pick it up if he can't get to it17:21
dansmithmriedem: what else?17:22
mriedemi see melwitt added consoles17:22
melwittI'll be continuing the consoles stuff. there's some review on it that I need to address17:22
mriedemre-propose the spec if you haven't already17:23
melwittyeah, will do that17:24
melwittI probably need a new spec for swapping the quota count with placement calls too17:24
melwittdo you think?17:24
dansmithyeah17:24
mriedemyes17:25
*** annabelleB has joined #openstack-meeting-317:25
melwittokay. what about for the DB magic instance listing?17:25
*** annabelleB has left #openstack-meeting-317:25
mriedemthat's purely poc at this point i think17:26
melwittso finish the patch and then write a spec?17:26
melwittif it works17:26
mriedemnot sure it requires a spec17:26
mriedemit should be transparent to the user17:26
melwittoksy17:26
melwitt*okay17:26
dansmithwhat magic instance thing?17:26
mriedemit's really fixing a bug17:26
melwittmdbooth's thing17:27
dansmithoh listing17:27
* dansmith read that wrong17:27
*** iyamahat has joined #openstack-meeting-317:27
mriedemwell i think that's probably certainly enough crap to worry about17:27
melwittagreed17:28
dansmithcool, so anything else?17:28
*** alexpilotti has quit IRC17:28
mriedemno17:28
melwittnay17:28
dansmithawesome17:28
dansmith#endmeeting17:28
*** openstack changes topic to "more ptg planning (Meeting topic: requirements)"17:28
openstackMeeting ended Wed Aug 30 17:28:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-08-30-17.00.html17:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-08-30-17.00.txt17:28
*** mriedem has left #openstack-meeting-317:28
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-08-30-17.00.log.html17:28
*** lyan has quit IRC17:35
*** annabelleB has joined #openstack-meeting-317:35
*** abalutoiu__ has quit IRC17:40
*** sambetts is now known as sambetts|afk17:40
*** bobh has quit IRC17:41
*** diablo_rojo has joined #openstack-meeting-317:47
*** yamahata has joined #openstack-meeting-317:47
*** lhx__ has quit IRC17:48
*** vmud213 has quit IRC17:48
*** Swami has joined #openstack-meeting-317:53
*** krtaylor has joined #openstack-meeting-317:56
*** anilvenkata is now known as anilvenkata|AFK17:58
*** VW_ has joined #openstack-meeting-318:00
*** VW_ has quit IRC18:02
*** VW_ has joined #openstack-meeting-318:02
*** VW has quit IRC18:03
*** markvoelker has joined #openstack-meeting-318:10
*** salv-orlando has joined #openstack-meeting-318:10
*** s3wong has joined #openstack-meeting-318:11
*** salv-orlando has quit IRC18:15
*** gouthamr has quit IRC18:28
*** etingof has quit IRC18:29
*** alexpilotti has joined #openstack-meeting-318:30
*** VW_ has quit IRC18:31
*** VW has joined #openstack-meeting-318:34
*** VW has quit IRC18:34
*** alexpilotti has quit IRC18:34
*** VW has joined #openstack-meeting-318:36
*** VW has quit IRC18:36
*** VW has joined #openstack-meeting-318:37
*** alexpilotti has joined #openstack-meeting-318:42
*** markvoelker has quit IRC18:43
*** gouthamr has joined #openstack-meeting-318:44
*** rmart04 has joined #openstack-meeting-318:48
*** e0ne has joined #openstack-meeting-318:51
*** markvoelker has joined #openstack-meeting-319:06
*** annabelleB has quit IRC19:11
*** salv-orlando has joined #openstack-meeting-319:11
*** rmart04 has quit IRC19:12
*** annegentle has quit IRC19:16
*** s3wong has quit IRC19:16
*** salv-orlando has quit IRC19:17
*** yamamoto has quit IRC19:22
*** annabelleB has joined #openstack-meeting-319:23
*** dims has quit IRC19:28
*** yamamoto has joined #openstack-meeting-319:28
*** julim has quit IRC19:30
*** julim_ has joined #openstack-meeting-319:30
*** shuyingya has joined #openstack-meeting-319:31
*** dims has joined #openstack-meeting-319:31
*** shuyingya has quit IRC19:35
*** markvoelker has quit IRC19:37
*** markvoelker has joined #openstack-meeting-319:38
*** coolsvap has quit IRC19:39
*** etingof has joined #openstack-meeting-319:42
*** ducttape_ has joined #openstack-meeting-319:50
*** srobert_ has joined #openstack-meeting-319:55
*** markvoelker has quit IRC19:56
*** annabelleB has quit IRC19:57
*** srobert has quit IRC19:59
*** rdopiera has joined #openstack-meeting-319:59
*** srobert_ has quit IRC20:00
ying_zuo#startmeeting horizon20:00
openstackMeeting started Wed Aug 30 20:00:34 2017 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
ying_zuoHi everyone o/20:00
e0nehi20:00
david-lyleo/20:01
robcresswello/20:01
rdopierao/20:01
ying_zuo#topic Announcements20:02
*** openstack changes topic to "Announcements (Meeting topic: horizon)"20:02
ying_zuo#info OpenStack Pike is available now!20:02
ying_zuo#link https://www.openstack.org/software/pike/20:02
ying_zuoThanks everyone for your contribution in making this release successful!20:02
robcresswell#o/20:02
e0nemy congratulations!20:02
robcresswell\o/ *20:03
ying_zuo\o/20:03
ying_zuo#info Schedule for PTG20:03
ying_zuo#link https://etherpad.openstack.org/p/horizon-ptg-queens20:03
ying_zuoFeel free to comment or add more topics in the open discussion time slots.20:03
ying_zuo#info Bug report guidelines20:04
ying_zuo#link https://bugs.launchpad.net/horizon/+filebug20:04
e0neying_zuo: is it final schedule?20:04
ying_zuonot really20:04
ying_zuoare you planning to add changes?20:04
*** annabelleB has joined #openstack-meeting-320:04
ying_zuoyou can add more topics in the open discussion time slots20:05
e0neying_zuo: not yet. I'm trying to manage my schedule to resolve conflicts and participate in pagination discussion20:06
ying_zuothere's a time slot for it each day20:06
ying_zuowhat time will work for you?20:07
*** benj_ has quit IRC20:08
*** alexpilo_ has joined #openstack-meeting-320:08
*** yamamoto has quit IRC20:08
ying_zuocan you let me know in #openstack-horizon?20:08
e0neying_zuo: before the noon on Monday or Tuesday will be great for me20:09
*** cleong has quit IRC20:09
*** benj_ has joined #openstack-meeting-320:09
e0neying_zuo: but I don't really want to change schedule if only me is interested in it20:09
e0neying_zuo: I mean all day Tuesday20:10
ying_zuoI will move it to Tuesday then20:10
ying_zuounless there's other objection...20:10
*** lpetrut has joined #openstack-meeting-320:10
*** alexpilotti has quit IRC20:10
e0neying_zuo: thank you. I apprciate it20:11
ying_zuonp20:11
ying_zuogoing back to the bug report guidelines topic...20:12
ying_zuoYou will notice the report guidelines when you try to open a bug report now. Thanks robcresswell20:12
ying_zuoThis is to make sure the bug report has the important information and it will help both developers and reviewers.20:12
ying_zuo#topic Open Discussion20:12
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:12
*** salv-orlando has joined #openstack-meeting-320:13
e0neI hope, my question will be fast enough20:14
*** catherineD has left #openstack-meeting-320:14
e0nemyself with rdopiera found that some admin pages could be open by non-admin users: http://paste.openstack.org/show/619772/20:14
e0newhat is expected behaviour for /admin/ paged? should render some data for non-admin users or raise NotAuthorized error?20:15
ying_zuodo they show admin information?20:15
e0neying_zuo: no20:16
david-lyleidentity pages are designed to open based on roles and policy, the test is not admin or not20:16
rdopierathey just show messages that they failed to get the information20:16
david-lyleis this via going to the URL directly?20:16
rdopierayeah20:16
david-lyleshrug20:16
david-lyle:)20:16
rdopieraI was trying to test the new "not authorized" page20:16
e0neying_zuo: but sometimes (e.g. hypervisors) it shows almost empty page with error messages like 'can't retrieve data'20:16
rdopieraand stumbled upon that20:16
e0nefor note: it's reproducible on a current master20:17
ying_zuobut that's because the users try to hack the pages20:17
rdopieraying_zuo: or they just changed the user to one that doesn't have the permission20:17
e0neI prefer to show some error and do not try to render such pages20:17
rdopieraying_zuo: which is the reason for working on the not authorized page in the first place20:17
ying_zuordopiera: what do you mean?20:18
e0neying_zuo: we're talking about this patch https://review.openstack.org/49147920:18
ying_zuohow can they change the user?20:18
rdopieraying_zuo: you can switch domains or other things, and suddenly not have the permission to see the page on which you are currently20:18
david-lyleso I'm guessing old policy files20:18
*** salv-orlando has quit IRC20:18
david-lylehttps://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/hypervisors/panel.py#L2420:19
david-lylethat policy rule is relatively new20:19
ying_zuoI see. so they can do actions that they are not supposed to20:19
rdopieradavid-lyle: that seems to work fine, as the page is not displayed in the menu20:19
david-lylerdopiera, ok20:19
david-lylehmm20:19
rdopieraying_zuo: no, because the services will check the permissions on their side and not allow that20:19
rdopieraying_zuo: you just get an empty page with a lot of errors20:20
e0ne^^ and it's not a user-friendly at all20:20
rdopierawhich is not critically bad, in fact could be acceptable20:20
rdopierabut a bit messy20:20
ying_zuoit's cleaner to just disable the panel20:20
e0nerdopiera: +120:20
rdopieraying_zuo: the panel is disabled correctly20:20
rdopieraying_zuo: but if you were on that page while you switched domains or users, you will still visit that page20:21
ying_zuoI meant setting the policy rule to disalbe it as david-lyle mentioned20:21
ying_zuogot it20:21
rdopierawe are working on a patch that displays a "not authorized" page then20:22
rdopieraand it works on most of the pages, which raise the correct exception20:22
rdopierabut those pages for some reason don't20:22
e0neying_zuo: here is a screenshot of hypervisors page: https://cl.ly/3M423D1Z2b3420:23
ying_zuothanks e0ne20:24
rdopieraI think the problem is that they have a catch-all try-except and don't delegate the exception handling to horizon20:24
rdopierabut I didn't verify that20:24
e0neying_zuo: other pages in the list look similar20:24
e0nerdopiera: let's decide what do we want to have first20:24
e0nerdopiera: IMO, we'll be able to fix it really quick if we decide what is excepted behaviour20:25
*** pilgrimstack has left #openstack-meeting-320:25
*** VW_ has joined #openstack-meeting-320:25
* e0ne wants quick meetings at 11pm20:26
*** VW_ has quit IRC20:27
*** VW__ has joined #openstack-meeting-320:27
robcresswellI feel like I missed the "solutions" part of the discussion20:28
ying_zuoI think just raise an exception. doesn't need to show a "not authorized" page.20:28
*** VW has quit IRC20:28
e0nerobcresswell: +1 :(20:28
david-lylewhere is unauthorized escaping in admin.instance ?20:28
robcresswellSo, the Not Authorised page from before is no longer an option?20:28
rdopierarobcresswell: it works on most pages20:29
e0neying_zuo: but we're talking about '/admin/some-page' and non-admin users20:29
david-lylerdopiera, by luck?20:29
rdopieraanother possibility is that those pages raise some other exception that doesn't get caught by our "not authorized page" mechanism20:29
rdopieradavid-lyle: by courage20:30
robcresswellhahaha20:30
e0nedavid-lyle, rdopiera: it depends on policies and who raises NotAuthorized exception20:30
e0nerdopiera: :)20:30
*** gary-smith has joined #openstack-meeting-320:30
david-lyleI'm looking at admin.instance get_data and not seeing any non-blanket "except Exception"20:30
rdopieraI say let's get the page to work on most pages, and then we can start cleaning up the mess20:30
david-lyleso I'm wondering what is working there20:30
david-lylemost likely we're leaking exceptions somehow20:31
robcresswellAlright so... whats the question here, exactly?20:31
*** jeremy_moffitt has joined #openstack-meeting-320:31
robcresswellah my internet skipped there, once sec20:31
e0nethe question is:20:31
robcresswellone*20:31
rdopiera"what should we do" :)20:31
e0newhat is expected result for such cases?20:31
*** VW__ has quit IRC20:31
robcresswelle0ne: Expected result? Isn't this what we discussed before though? A Not Authorised page with a login box or something20:32
*** VW has joined #openstack-meeting-320:32
robcresswellor a "Go to Login" and "Go to home"20:32
e0neif non-admin user somehow opens e.g. /admin/hypersvisors/ page. what should be?20:32
david-lylerobcresswell, so we catch all exceptions other than not authorized?20:32
robcresswelldavid-lyle: Sorry?20:33
e0nerobcresswell: it's a bit different case, but I'm OK to show Not Authorized page20:33
david-lylethe policy before was not let exception bubble up to the user uncaught20:33
robcresswelle0ne: I'm having deja vu, I thought we discussed this a few weeks ago :p20:33
robcresswelldavid-lyle: Ah, I see your train of thought now20:33
e0nerobcresswell: not really this issue, but very similar20:34
david-lylewhich the unauthorized page would cover but at a different level, it seems weird to only bubble that one20:34
e0nerobcresswell: now we have pages that partially work for non-admin20:34
david-lylepartially work is maybe an overstatement :)20:34
robcresswellNot weird, not really. In web stuff I write separately I usually have redirects for specific HTTP codes. (401, 403, off the top of my head)20:35
david-lylethey don't load data20:35
david-lylerobcresswell, sure, ideally we should be explicit about our exceptions20:35
*** apetrich has quit IRC20:35
e0nerobcresswell: e.g.: http://10.13.0.43/dashboard/admin/volume_types/ can be both opened by admin and non-admin users20:35
david-lyleunfortunately things have gotten lax and we attempt to catch all generally20:35
e0nerobcresswell: but non-admins won't see private volume types20:36
robcresswellurgh, this "admin" concept20:36
david-lyleadmin is not a concept20:36
david-lyleit's a legacy20:36
e0neIMO, we should not allow for non-admin to open any of /admin/* pages20:36
robcresswellI meant specifically the Horizon interpretation of admin20:36
david-lylehiding pages from the nav should be sufficient20:36
rdopierae0ne: there are no admins20:37
*** apetrich has joined #openstack-meeting-320:37
rdopierae0ne: permissions defpend on the policies20:37
e0neOK, replace, please, 'admin' to 'users w/o permissions to open this page or view all data on the page'20:37
david-lyleif a user wants to go directly to a page what is the harm of being told you're not authorized to get the data on the page?20:38
robcresswellSo, the issue as described before was something like, if you can see admin/instances on one project, but then you change to one where you can't, Horizon gives you a double login in some circumstances20:38
rdopieradavid-lyle: no harm, but it's messy, it would be nicer to show a nice "not authorized" message and a link to the login page20:38
david-lyleon that login page I've lost all context20:39
david-lyleperhaps I'm just scoped to the wrong project20:39
robcresswelldavid-lyle: Horizon passes through that little "next" link though20:39
*** pcaruana has quit IRC20:40
robcresswellWhich is problematic if you try a different login, and thats not got permissions either, I *think* is the issue20:40
david-lylewith the project you were scoped to visable to the user?20:40
*** s3wong has joined #openstack-meeting-320:40
robcresswellNo, but isn't the idea that you would then login under a different user (magic admin account) to do some action?20:40
david-lylethe user could have been correct20:41
david-lylethe project scope could have been wrong20:41
robcresswellTrue20:41
* robcresswell is thinking20:42
david-lyleI think it's by strange luck that some pages would filter out and other won't at this point. I worry that the behavior will not be reliable20:42
robcresswellWhat's the alternative, show a blank page?20:42
*** annabelleB has quit IRC20:43
david-lylejust show the page with the error message that you don't have proper privilege to view the contents of this page20:43
david-lylethat's what the identity pages do20:43
david-lylebut they're intended for all users to be able to hit20:43
*** annabelleB has joined #openstack-meeting-320:43
robcresswellI wonder if people would complain about losing the redirect functionality20:43
lucasxui will ;(20:44
e0nerobcresswell: we can redirect to login page with a correct '?next=' param20:44
rdopierawe discussed that already20:45
rdopieraand agreed on it20:45
e0nerdopiera: +120:45
robcresswelle0ne: Right, but I'm saying that if we just displayed a blank page with an error, we lose that20:45
rdopierathe problem now is whether all pages should behave consistently or not20:45
*** ansmith has quit IRC20:45
david-lyle+1 to consistency20:45
e0nerobcresswell: page with error and login link20:45
rdopieraand how urgent it is20:45
rdopierapersonally I think it would be nice to be consistent but it's not high priority20:45
e0nerdopiera: +1, I absolutely agree20:45
robcresswelle0ne: Didn't we just say we can't reliably do that?20:46
robcresswellI *think* what david-lyle was suggesting is that if you go to admin/instances without correct permissions you just show a blank page with "You dont have permissions to do X / Y"20:46
e0newhat about page like https://review.openstack.org/#/c/491479/9/horizon/templates/not_authorized.html20:47
e0ne?20:47
robcresswelle0ne: You're not reading my questions. Didn't we say earlie that we could not reliably determine that?20:47
robcresswellearlier*20:47
david-lyleI think with policy that becomes a very gray line20:47
rdopierarobcresswell: we can determine very reliably that we got an exception from the api20:48
e0nerobcresswell: we can catch needed API from APIs20:48
robcresswell"Something went wrong. Would you like to log out?"20:48
e0ne*can catch needed exception20:48
david-lylerdopiera, so are you suggest we rewrite all the excepts in the get_data calls?20:49
robcresswelle0ne: I thought you and rdopiera earlier said we cannot get the exception reliably20:49
e0nerobcresswell: I hope, all APIs can return not authorized. we can handle them correctly20:49
*** lucasxu has quit IRC20:49
e0nerobcresswell: it's only in a *current* implementation of some pages20:49
rdopieradavid-lyle: something like that, perhaps fix it in the handling of the exceptions, less invasive20:50
david-lyleso so except Exception as e, if e is not UnAuthorized?20:50
rdopieradavid-lyle: we have an exception handler function already that handles most of those exceptions20:50
rdopieradavid-lyle: but for some reason not all of them20:50
rdopieradavid-lyle: and it does see those exceptions, because it displays the messages20:51
*** ducttape_ has left #openstack-meeting-320:51
e0ne10mins reminder20:52
*** slaweq has joined #openstack-meeting-320:52
david-lyleso https://github.com/openstack/horizon/blob/master/openstack_dashboard/exceptions.py#L29 isn't broad enough?20:52
rdopieraapparently20:52
david-lylehypervisors doesn't use novaclient.Unauthorized?20:52
rdopieraor some other special case is happening20:53
*** egallen has joined #openstack-meeting-320:53
rdopieraI didn't analyze the code enough to be sure20:53
e0nedavid-lyle: the issue is, sometimes we catch Exception and return error message to user instead of re-raising NonAuthorized20:53
*** gouthamr has quit IRC20:54
* robcresswell reminds everyone we have crippling performance issues on other pages, even if users sometimes have to log in twice when they try and view a page they dont have permissions for.20:54
rdopierae0ne: that coould make sense when the page contains multiple things, and some of them the user has permission to see20:54
e0nerdopiera: good point20:55
rdopieraso maybe let's leave it as it is for now20:55
robcresswelle0ne: If it is possible to correctly identify that a NotAuthorised exception is there in all cases, then we can consider doing something special20:55
david-lylee0ne, I understand. My two points are I think a blanket unauthorized for a page that attempts to make several API calls may not be correct and two, it seems you'll have to reverse engineer all client authorization failures to handle them properly20:55
e0nedavid-lyle: I agree20:55
e0nelooks like we have a decision:20:55
david-lyleto me the unauthorized page is a carry over from the admin/non-admin days when things were binary20:56
rdopierait's better than the redirect20:56
*** annabelleB has quit IRC20:56
e0netry to handle NotAuthorised if we can or leave it as is for now20:56
e0ne2mins reminder20:58
ying_zuocool. I think that's it for today. Thanks everyone for attending.20:58
rdopieratick tock20:58
rdopieragoodnight20:58
e0nesee you next week20:58
ying_zuo#endmeeting20:58
*** openstack changes topic to "more ptg planning (Meeting topic: requirements)"20:58
openstackMeeting ended Wed Aug 30 20:58:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-30-20.00.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-30-20.00.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-30-20.00.log.html20:59
*** rdopiera has left #openstack-meeting-320:59
*** annegentle has joined #openstack-meeting-321:00
*** bobh has joined #openstack-meeting-321:03
*** e0ne has quit IRC21:06
*** alexpilotti has joined #openstack-meeting-321:07
*** alexpilotti has quit IRC21:08
*** alexpilotti has joined #openstack-meeting-321:08
*** alexpilo_ has quit IRC21:10
*** gouthamr has joined #openstack-meeting-321:10
*** salv-orlando has joined #openstack-meeting-321:14
*** georgk has joined #openstack-meeting-321:19
*** salv-orlando has quit IRC21:19
*** krtaylor has quit IRC21:20
*** gary-smith has left #openstack-meeting-321:20
*** baoli has quit IRC21:23
*** georgk1 has joined #openstack-meeting-321:28
*** georgk has quit IRC21:29
*** jeremy_moffitt has left #openstack-meeting-321:35
*** annabelleB has joined #openstack-meeting-321:36
*** lpetrut has quit IRC21:45
*** VW has quit IRC21:57
*** georgk1 has quit IRC21:57
*** VW has joined #openstack-meeting-322:01
*** egallen has quit IRC22:02
*** krtaylor has joined #openstack-meeting-322:05
*** raildo has quit IRC22:08
*** salv-orlando has joined #openstack-meeting-322:15
*** salv-orlando has quit IRC22:20
*** VW has quit IRC22:20
*** marst has quit IRC22:20
*** slaweq has quit IRC22:30
*** rstarmer has joined #openstack-meeting-322:35
*** annabelleB has quit IRC22:37
*** kbyrne has quit IRC22:40
*** VW has joined #openstack-meeting-322:41
*** kbyrne has joined #openstack-meeting-322:41
*** galstrom is now known as galstrom_zzz22:44
*** VW has quit IRC22:45
*** bobh has quit IRC23:09
*** hongbin has quit IRC23:10
*** chyka has quit IRC23:10
*** scottda has quit IRC23:12
*** salv-orlando has joined #openstack-meeting-323:16
*** salv-orlando has quit IRC23:21
*** annegentle has quit IRC23:26
*** rstarmer has quit IRC23:38
*** Fdaisuke has joined #openstack-meeting-323:41
*** markvoelker_ has joined #openstack-meeting-323:45
*** s3wong has quit IRC23:48
*** bobh has joined #openstack-meeting-323:50
*** kbyrne has quit IRC23:51
*** bobh has quit IRC23:51
*** kbyrne has joined #openstack-meeting-323:54

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