Tuesday, 2018-05-08

*** Bonjourm8 has quit IRC00:23
*** julim has quit IRC00:34
*** cloudrancher has joined #openstack-meeting-alt00:35
*** felipemonteiro__ has joined #openstack-meeting-alt00:39
*** hiro-kobayashi has joined #openstack-meeting-alt00:47
*** cloudrancher has quit IRC01:19
*** jesusaur has quit IRC01:22
*** jesusaur has joined #openstack-meeting-alt01:24
*** Bonjourm8 has joined #openstack-meeting-alt01:31
*** junboli has joined #openstack-meeting-alt01:34
*** felipemonteiro__ has quit IRC01:35
*** dalgaaf has quit IRC01:45
*** dalgaaf has joined #openstack-meeting-alt01:46
*** carl_baldwin_ has quit IRC01:55
*** lei-zh has joined #openstack-meeting-alt01:56
*** hongbin has joined #openstack-meeting-alt02:02
*** markstur_ has quit IRC02:09
*** Bonjourm8 has quit IRC02:11
*** yamamoto has joined #openstack-meeting-alt02:17
*** dave-mccowan has quit IRC02:20
*** yamamoto has quit IRC02:22
*** junboli has quit IRC02:29
*** brault has joined #openstack-meeting-alt02:31
*** lei-zh has quit IRC02:33
*** lei-zh has joined #openstack-meeting-alt02:34
*** shu-mutow-AWAY is now known as shu-mutow02:35
*** brault has quit IRC02:36
*** hongbin_ has joined #openstack-meeting-alt02:37
*** felipemonteiro__ has joined #openstack-meeting-alt02:39
*** hongbin has quit IRC02:40
*** felipemonteiro__ has quit IRC02:58
*** yamamoto has joined #openstack-meeting-alt03:04
*** smyers has quit IRC03:08
*** gcb has joined #openstack-meeting-alt03:08
*** yamamoto has quit IRC03:31
*** lpetrut has joined #openstack-meeting-alt03:43
*** sridharg has joined #openstack-meeting-alt03:48
*** gyee has quit IRC03:48
*** janki has joined #openstack-meeting-alt03:50
*** cloudrancher has joined #openstack-meeting-alt03:52
*** markstur has joined #openstack-meeting-alt03:54
*** hongbin_ has quit IRC03:55
*** cloudrancher has quit IRC03:57
*** markstur has quit IRC03:59
*** fnaval has quit IRC04:11
*** lpetrut has quit IRC04:15
*** gyee has joined #openstack-meeting-alt04:17
*** lei-zh has quit IRC04:17
*** gyee has quit IRC04:24
*** anilvenkata has joined #openstack-meeting-alt04:34
*** chhagarw has joined #openstack-meeting-alt04:37
*** links has joined #openstack-meeting-alt04:38
*** chhagarw has quit IRC04:41
*** chhagarw has joined #openstack-meeting-alt04:44
*** Zames_ has joined #openstack-meeting-alt04:59
*** Zames_ has quit IRC05:02
*** yamamoto has joined #openstack-meeting-alt05:06
*** lei-zh has joined #openstack-meeting-alt05:07
*** lpetrut has joined #openstack-meeting-alt05:13
*** jesusaur has quit IRC05:14
*** e0ne has joined #openstack-meeting-alt05:18
*** jesusaur has joined #openstack-meeting-alt05:20
*** jtomasek has joined #openstack-meeting-alt05:23
*** radeks has joined #openstack-meeting-alt05:24
*** lpetrut has quit IRC05:24
*** e0ne has quit IRC05:29
*** trinaths has joined #openstack-meeting-alt05:40
*** markstur has joined #openstack-meeting-alt05:42
*** markstur has quit IRC05:48
*** marios has joined #openstack-meeting-alt05:51
*** kaisers1 has quit IRC05:54
*** mjura has joined #openstack-meeting-alt05:59
*** markvoelker has quit IRC06:01
*** tssurya has joined #openstack-meeting-alt06:03
*** armaan has joined #openstack-meeting-alt06:07
*** lpetrut has joined #openstack-meeting-alt06:10
*** kaisers1 has joined #openstack-meeting-alt06:11
*** armaan has quit IRC06:11
*** armaan has joined #openstack-meeting-alt06:12
*** mjura has quit IRC06:21
*** mjura has joined #openstack-meeting-alt06:24
*** armaan has quit IRC06:24
*** armaan has joined #openstack-meeting-alt06:25
*** brault has joined #openstack-meeting-alt06:32
*** brault has quit IRC06:36
*** alexchadin has joined #openstack-meeting-alt06:39
*** jesusaur has quit IRC06:45
*** kaisers1 has quit IRC06:45
*** jesusaur has joined #openstack-meeting-alt06:46
*** vabada has joined #openstack-meeting-alt06:47
*** rasca has quit IRC06:56
*** radeks_ has joined #openstack-meeting-alt07:01
*** markvoelker has joined #openstack-meeting-alt07:01
*** brault has joined #openstack-meeting-alt07:02
*** rasca has joined #openstack-meeting-alt07:04
*** brault has quit IRC07:04
*** brault has joined #openstack-meeting-alt07:04
*** alexchad_ has joined #openstack-meeting-alt07:08
*** rcernin has quit IRC07:08
*** alexchadin has quit IRC07:10
*** zhuli has quit IRC07:12
*** zhuli_ has joined #openstack-meeting-alt07:13
*** florianf has joined #openstack-meeting-alt07:13
*** armaan has quit IRC07:14
*** trinaths has quit IRC07:15
*** bertys_ has joined #openstack-meeting-alt07:19
*** kaisers1 has joined #openstack-meeting-alt07:22
*** rwsu has quit IRC07:32
*** markvoelker has quit IRC07:36
*** gcb has quit IRC07:41
*** alexchad_ has quit IRC07:48
*** yamamoto has quit IRC07:56
*** rwsu has joined #openstack-meeting-alt08:02
*** yamamoto has joined #openstack-meeting-alt08:03
*** lpetrut has quit IRC08:05
*** hiro-kobayashi has quit IRC08:22
*** markvoelker has joined #openstack-meeting-alt08:33
*** MarkBaker has joined #openstack-meeting-alt08:34
*** arnewiebalck_ has joined #openstack-meeting-alt08:38
*** arnewiebalck has quit IRC08:39
*** arnewiebalck_ is now known as arnewiebalck08:39
*** yamamoto_ has joined #openstack-meeting-alt08:40
*** e0ne has joined #openstack-meeting-alt08:40
*** aspiers has quit IRC08:40
*** zigo_ has quit IRC08:40
*** rasca has quit IRC08:41
*** yamamoto has quit IRC08:41
*** aspiers has joined #openstack-meeting-alt08:41
*** rasca has joined #openstack-meeting-alt08:42
*** alexchadin has joined #openstack-meeting-alt08:44
*** derekh has joined #openstack-meeting-alt08:44
*** zigo has joined #openstack-meeting-alt08:45
*** vabada has quit IRC08:55
*** vabada has joined #openstack-meeting-alt08:55
*** yamamoto_ has quit IRC08:56
*** d0ugal__ has quit IRC08:57
*** Zames_ has joined #openstack-meeting-alt08:58
*** d0ugal has joined #openstack-meeting-alt08:58
*** masahito has joined #openstack-meeting-alt08:59
masahito#startmeeting blazar09:00
openstackMeeting started Tue May  8 09:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: blazar)"09:00
openstackThe meeting name has been set to 'blazar'09:00
masahito#topic RollCall09:00
*** openstack changes topic to "RollCall (Meeting topic: blazar)"09:00
*** panda|off is now known as panda09:01
bertys_o/09:01
bertys_masahito: hi09:01
*** armaan has joined #openstack-meeting-alt09:01
*** hiro-kobayashi has joined #openstack-meeting-alt09:01
bertys_hiro-kobayashi: hi09:02
hiro-kobayashihi all!09:02
*** Zames_ has quit IRC09:02
masahitoToday's agenda is09:02
masahito1. placement support09:02
masahito2. AOB09:02
masahitoless topics09:02
masahitoanything else?09:02
*** lpetrut has joined #openstack-meeting-alt09:03
masahitobertys_, hiro-kobayashi: hello09:03
masahito#topic placement support09:04
*** openstack changes topic to "placement support (Meeting topic: blazar)"09:04
masahitoIn last meeting hiro-kobayashi shared design idea for placement support.09:04
masahitohttps://etherpad.openstack.org/p/blazar-placement-design09:05
masahitoand asked us to comment for the approach.09:05
masahitoI commented this week.09:05
masahitohiro-kobayashi: any update for the design?09:06
hiro-kobayashithanks for comments and adding details!09:06
masahitoAs we discussed before, I'd like to share the idea to openstack-dev ML before the Vancouver summit.09:06
*** markvoelker has quit IRC09:07
*** armaan has quit IRC09:08
hiro-kobayashimasashito: thanks.09:08
masahitoMy main question for the design is will host reservation ask user to choose private flavor instead of scheduler hint?09:08
*** yamamoto has joined #openstack-meeting-alt09:08
hiro-kobayashiIIRC, scheduler filter is not recommended because it affects inter-operability.09:09
hiro-kobayashiSo, I think it's better to use a private flavor.09:10
hiro-kobayashiHowever, it will increase the number of flavors...09:10
masahitoyes.09:12
hiro-kobayashiDoes 4 need a private flavor?09:13
masahitoMy concern is how host reservation create its flavors and count the usage.09:13
hiro-kobayashiHow does the lease owner specify the allocation ID?09:13
masahitoMy understand is yes for instance reservation but no for host reservation.09:14
*** lpetrut has quit IRC09:14
masahitoIIRC, Nova doesn't have the feature now.09:15
masahitoWe need to propose it.09:15
bertys_hiro-kobayashi, masahito: What about focusing first on instance reservation only?09:16
*** fnaval has joined #openstack-meeting-alt09:16
masahitobertys_: yes.09:17
hiro-kobayashibertys_: make sense but it's better to consider both for basic design.09:18
masahitoI also thought we need to handle 3 items with placement, freepool, host reservation and instance reservation, when I read the design.09:18
hiro-kobayashimasahito: Yes. And another item is capacity query. It's an advanced topic, thogh.09:20
*** fnaval has quit IRC09:20
masahitoThere could be another Nova-ish approach. Once we've written down our concern, it's good to share Nova team ASAP.09:20
hiro-kobayashiI mean, using placement for the 'reservation candidates' API09:20
hiro-kobayashimasahito: Agree.09:21
*** sambetts|afk is now known as sambetts09:22
masahitohiro-kobayashi: do you have a planning date to share it to the team?09:22
hiro-kobayashiNo, but before the summit.09:23
masahitoIf possible, I'd like to share it before next meeting because we can discuss the reaction from the team in weekly meeting and Blazar's forum session is on Monday in the summit.09:25
masahitos/in weekly meeting/ in the next weekly meeting/09:25
bertys_From the analysis, it seems right now that we have three options on the table for instance reservation: (#1 and #3) or (#2 and #3) or 4 as REQ3 is mandatory req IMHO09:26
hiro-kobayashiDo you mean Placement weekly meeting?09:26
bertys_with (#1 and #3)= #509:26
bertys_sorry (#1 and #3) would be #6 );09:27
masahitohiro-kobayashi: the blazar weekly meeting09:27
hiro-kobayashibertys_: I thinks #1 can satisfy REQ 1-3. so #1, #4, #509:28
hiro-kobayashiare the possible approach.09:29
hiro-kobayashimasahito: got it09:29
masahito#5 only works for the instance reservation, right?09:30
hiro-kobayashimasahito: I thinks it can be used for both of host and instance. However, host reservation has a problem of the number of flavor.09:31
*** lei-zh has quit IRC09:32
*** Zames_ has joined #openstack-meeting-alt09:33
masahitohiro-kobayashi: Additionally, how does blazar count the max of CUSTOM_RESOURCE in host reservation?09:33
bertys_hiro-kobayashi: Have you already investigated whether 1) is sufficient or a combination of 1) and 3) would be necessary to support REQ3?09:34
hiro-kobayashimasahito: good point! I thinks blazar should not (cannot) count max09:35
*** Zames_ has quit IRC09:35
hiro-kobayashibertys_: Yes. But a patch is needed. https://review.openstack.org/#/c/561842/09:36
hiro-kobayashiThis patch enables update of the usage of nested resources when launching an instance.09:37
bertys_hiro-kobayashi: Okay, thanks for sharing this info09:37
masahitonice.09:38
*** shu-mutow is now known as shu-mutow-AWAY09:39
hiro-kobayashiI added info to the etherpad page09:39
masahitookay, another comment for the design?09:42
masahitoif nothing, let's move on to next.09:42
bertys_hiro-kobayashi: thanks, I need to catch up again with nested RPs ); Things are moving fast now09:42
masahito#topic AOB09:45
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:45
masahitoDoes someone have topics to share/discuss?09:46
*** vabada has quit IRC09:46
*** vabada has joined #openstack-meeting-alt09:46
masahitoI'll share my update.09:47
masahitoI pushed the patches for multi-freepools and flavor-extra-specs.09:47
masahitomulti-freepools: https://review.openstack.org/#/c/564138/09:48
masahitoflavor-extra-specs: https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bp/flavors-extra-specs09:48
masahitoPlease review the patces.09:48
masahitoThat's from my side.09:48
hiro-kobayashiGreat!09:49
hiro-kobayashiMy test env is down now, so I'll review and test them as soon as it goes up.09:49
masahitothanks09:50
bertys_I have reached out to Jean-Philippe (Ansible PTL) yesterday and there are few patches related to Blazar under review now e.g. https://review.openstack.org/#/c/566541/. Looks good so far09:50
bertys_I am also planning to attend OpenStack PTG in Denver. Tentatively from Sep. 11 to 1409:52
masahitoGood to hear.09:52
*** florianf has quit IRC09:53
masahitoanything else? if nothing, let's finish the meeting early.09:54
hiro-kobayashiNothing from my side09:54
*** florianf has joined #openstack-meeting-alt09:54
masahitoOK, thanks everyone!09:56
hiro-kobayashithanks! bye09:56
masahito#endmeeting09:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:56
openstackMeeting ended Tue May  8 09:56:35 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-05-08-09.00.html09:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-05-08-09.00.txt09:56
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-05-08-09.00.log.html09:56
*** Zames_ has joined #openstack-meeting-alt09:56
*** bertys_ has quit IRC09:56
*** hiro-kobayashi has quit IRC09:57
*** Zames_ has quit IRC09:57
*** Zames_ has joined #openstack-meeting-alt10:02
*** armaan has joined #openstack-meeting-alt10:04
*** markvoelker has joined #openstack-meeting-alt10:04
*** Zames_ has quit IRC10:04
*** alexchadin has quit IRC10:09
*** yamamoto has quit IRC10:15
*** caowei has quit IRC10:20
*** yamamoto has joined #openstack-meeting-alt10:20
*** rcernin has joined #openstack-meeting-alt10:35
*** markvoelker has quit IRC10:38
*** masahito has quit IRC10:39
*** yamamoto has quit IRC10:48
*** alexchadin has joined #openstack-meeting-alt10:55
*** panda is now known as panda|lunch11:08
*** markvoelker has joined #openstack-meeting-alt11:34
*** yamamoto has joined #openstack-meeting-alt11:37
*** sridharg has quit IRC11:56
*** sridharg has joined #openstack-meeting-alt11:57
*** raildo has joined #openstack-meeting-alt12:03
*** panda|lunch is now known as panda12:04
*** markvoelker has quit IRC12:08
*** edmondsw has joined #openstack-meeting-alt12:08
*** markvoelker has joined #openstack-meeting-alt12:15
*** dave-mccowan has joined #openstack-meeting-alt12:22
*** dave-mcc_ has joined #openstack-meeting-alt12:24
*** dave-mccowan has quit IRC12:26
*** learnmore has joined #openstack-meeting-alt12:27
*** jokke__ is now known as jokke_12:31
*** alexchadin has quit IRC12:31
*** alexchadin has joined #openstack-meeting-alt12:33
*** vgreen has joined #openstack-meeting-alt12:49
*** arxcruz has quit IRC12:50
*** fuqiao has joined #openstack-meeting-alt12:56
*** arxcruz has joined #openstack-meeting-alt12:57
*** arxcruz has quit IRC13:00
*** arxcruz has joined #openstack-meeting-alt13:01
*** jcoufal has joined #openstack-meeting-alt13:02
*** brault has quit IRC13:04
*** armaan has quit IRC13:05
*** armaan has joined #openstack-meeting-alt13:06
*** yamamoto has quit IRC13:16
*** yamamoto has joined #openstack-meeting-alt13:16
*** dklyle has quit IRC13:19
*** learnmore has quit IRC13:22
*** armaan has quit IRC13:23
*** armaan has joined #openstack-meeting-alt13:23
*** felipemonteiro__ has joined #openstack-meeting-alt13:28
*** dustins has joined #openstack-meeting-alt13:30
*** rmart04 has joined #openstack-meeting-alt13:34
*** felipemonteiro_ has joined #openstack-meeting-alt13:36
*** felipemonteiro__ has quit IRC13:39
*** Bonjourm8 has joined #openstack-meeting-alt13:41
*** Bonjourm8 has quit IRC13:42
*** anilvenkata has quit IRC13:45
*** mjura has quit IRC13:46
*** amotoki has quit IRC13:51
*** hongbin has joined #openstack-meeting-alt13:59
*** rossella_s has quit IRC14:03
*** alexchadin has quit IRC14:03
*** lbragstad has quit IRC14:05
*** rossella_s has joined #openstack-meeting-alt14:05
*** lbragstad has joined #openstack-meeting-alt14:05
*** e0ne_ has joined #openstack-meeting-alt14:05
*** e0ne has quit IRC14:05
*** armaan has quit IRC14:07
*** armaan has joined #openstack-meeting-alt14:07
*** yamamoto has quit IRC14:16
*** yamamoto has joined #openstack-meeting-alt14:19
*** chhavi__ has joined #openstack-meeting-alt14:23
*** cloudrancher has joined #openstack-meeting-alt14:25
*** armaan has quit IRC14:25
*** chhavi__ has quit IRC14:26
*** armaan has joined #openstack-meeting-alt14:26
*** chhagarw has quit IRC14:26
*** chhagarw has joined #openstack-meeting-alt14:27
*** chhagarw has quit IRC14:34
*** fnaval has joined #openstack-meeting-alt14:35
*** smyers has joined #openstack-meeting-alt14:38
*** dklyle has joined #openstack-meeting-alt14:42
*** rcernin has quit IRC14:47
*** wxy| has joined #openstack-meeting-alt15:01
*** rmart04 has quit IRC15:01
*** markstur has joined #openstack-meeting-alt15:06
*** links has quit IRC15:08
*** manjeet has joined #openstack-meeting-alt15:12
*** gagehugo has joined #openstack-meeting-alt15:12
*** zzzeek has joined #openstack-meeting-alt15:13
*** manjeet is now known as manjeets_wfh15:13
*** florianf has quit IRC15:13
*** kumarmn has quit IRC15:14
*** spilla has joined #openstack-meeting-alt15:15
*** spilla has left #openstack-meeting-alt15:16
*** jaosorior has joined #openstack-meeting-alt15:17
*** fuqiao has quit IRC15:25
*** vds has joined #openstack-meeting-alt15:26
*** vds has quit IRC15:26
*** florianf has joined #openstack-meeting-alt15:28
*** manjeets_ has joined #openstack-meeting-alt15:28
*** manjeets_ has quit IRC15:29
*** manjeets_ has joined #openstack-meeting-alt15:29
*** felipemonteiro has joined #openstack-meeting-alt15:30
*** felipemonteiro__ has joined #openstack-meeting-alt15:31
*** manjeets_wfh has quit IRC15:31
*** vds has joined #openstack-meeting-alt15:31
*** pbourke has quit IRC15:32
*** felipemonteiro_ has quit IRC15:32
*** manjeets_ is now known as manjeets_wfh15:33
*** vds has quit IRC15:33
*** pbourke has joined #openstack-meeting-alt15:34
*** felipemonteiro has quit IRC15:35
*** kumarmn has joined #openstack-meeting-alt15:50
*** kumarmn has quit IRC15:54
*** e0ne_ has quit IRC15:58
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue May  8 16:00:24 2018 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: keystone)"16:00
cmurphyo/16:00
openstackThe meeting name has been set to 'keystone'16:00
knikollao/16:00
hrybackio/16:00
lbragstado/16:00
gagehugoo/16:00
*** edmondsw has quit IRC16:00
wxy|o/16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:00
lbragstadagenda ^16:00
*** edmondsw has joined #openstack-meeting-alt16:01
kmallocO/16:01
*** janki has quit IRC16:01
lbragstadwe have a good mix of folks here - so we can go ahead and get started16:02
lbragstad#topic New direction with default roles16:02
*** openstack changes topic to "New direction with default roles (Meeting topic: keystone)"16:02
lbragstadthanks to jroll we got a bunch of good infomraiton on the openstack-specs process last week16:02
lbragstad#link http://lists.openstack.org/pipermail/openstack-dev/2018-May/130207.html16:02
lbragstadsummary ^16:02
lbragstad#link https://review.openstack.org/#/c/566377/16:02
lbragstadnew specification ^16:02
lbragstadthe TL;DR is that openstack-specs isn't really reviewed anymore, and sounds like it has been unofficially superseded by community goals16:03
* hrybacki nods16:03
lbragstaddhellmann: and mnaser had some really good input on the process too, and actually recommended that we propose the default roles thing as a community goal16:04
lbragstad(which i was pretty hesitant about)16:04
lbragstadjust because of the volume of work16:04
lbragstadin the mean time, they suggested building out a solid template using keystone and a couple other services before we formally propose it as a community gaol16:04
*** gyee has joined #openstack-meeting-alt16:04
lbragstadwhich is what hrybacki has done with the new specification16:04
hrybackiWe are hoping for Keystone, Barbican, and Octavia at a minimum16:05
hrybackiRegardless, I'd like to get a jump on the Keystone work sooner rather than later16:05
lbragstadi thought the encouragement for proposing this as a community goal was a good sign16:06
hrybacki+116:06
*** rmascena has joined #openstack-meeting-alt16:06
lbragstadso - i guess what we need to decide here is whether or not to allow the specification proposal post specification proposal freeze16:06
*** marios has quit IRC16:06
*** cloudrancher has quit IRC16:06
kmallocI am ok with this one post freeze (tentatively, based upon cmnty feedback on community goals)16:07
kmallocThis is pretty well defined scope wise.16:07
lbragstadwe also proposed it to openstack-specs a long time ago, so technically it's not a "new" proposal16:08
knikolla++16:08
lbragstadbut.. going to formality16:08
lbragstadcross the i's, dot the t's16:08
*** raildo has quit IRC16:08
dhellmannkeep in mind that before it can be accepted as a goal, we would need to see at least one project adopting it and general support for it across the other projects16:09
cmurphythe formalities are supposed to help us with planning work, moving the spec to a different repo isn't really changing anything for us16:09
lbragstad++ cmurphy16:09
lbragstadwe were planning on doing this work regardless i guess16:09
kmallocExactly.16:09
lbragstadcool - so no objections then, and it sounds like everyone is on the same page16:10
lbragstadi'll link to this discussion in the ml list16:10
lbragstadand we can go through the review process for the specification16:10
hrybacki+1 thanks lbragstad16:11
*** jaosorior has left #openstack-meeting-alt16:11
lbragstaddhellmann: brings up a good point, because we'll have the opportunity to really make the template solid before proposing the community goal16:11
lbragstadso we could work in the system_scope stuff too16:11
lbragstadand hopefully provide a really clear picture of how the two concepts work together16:11
*** manjeets_ has joined #openstack-meeting-alt16:12
*** cloudrancher has joined #openstack-meeting-alt16:12
lbragstad#topic getting patrole in CI16:12
*** openstack changes topic to "getting patrole in CI (Meeting topic: keystone)"16:12
lbragstadhrybacki: was this your topic?16:12
hrybackiaye16:13
hrybackiOkay, so this goes along with the default roles work. tl;dr we need a way to test it and CI is slow, slow, slow to bring in new features16:13
lbragstad#link https://review.openstack.org/#/c/559137/16:13
hrybackiand, now knowing that openstack-specs isn't really monitored, the original review in keystone-specs16:13
hrybacki#link https://review.openstack.org/#/c/464678/16:13
gagehugowould this also be a good fit for a "community goal"?16:14
hrybackigagehugo: yes. I think that these two go hand-in-hand16:14
gagehugohave some role testing in multiple projects16:14
hrybackiand testing it out in Keystone/Barbican would be a great place to start and work out the kinks16:14
gagehugofelipemonteriro__ ^16:14
*** manjeets_wfh has quit IRC16:15
hrybackiI'd like to see the original review picked back up, targetting a non-voting job against keystone changes. No way of knowing how long that will take tbh so getting the ball rolling know is preferential imo16:16
gagehugoadding a playbook to keystone is pretty simple now too16:16
hrybackiI don't see how this would pigeon hole us (I need to do more research on Patrole) but felipemonteiro__ is quite responsive16:16
hrybackigagehugo: +116:16
hrybackiI know that ayoung was opposed to the original keystone-spec when we were targetting RBAC in middleware work. I'm hoping he'd be willing to remove it now however16:17
*** harlowja has joined #openstack-meeting-alt16:17
*** kumarmn has joined #openstack-meeting-alt16:18
hrybackilbragstad: as we are past spec proposal freeze I can see how this might not be ideal for Rocky but is it possible to work on a PoC in the meantime?16:18
ayoungwhich one?16:18
hrybackiayoung: https://review.openstack.org/#/c/464678/16:18
felipemonteiro__hrybacki: hi. i don't recall if i mentioned this in the spec, but i noticed keystone (particularly lbragstad) and others were committing only to openstack-specs, so i followed suit... i can backtrack too as well and update the one in keystone-specs.16:18
hrybackifelipemonteiro__: ack, we thought that was the current standard but it's not. Community Goals are where it's at but require adoption and support across several projects first16:19
gagehugoyeah I don't think openstack-specs is actively reviewed16:19
ayoungMy issue with patrole is that I am afraid they are going to lock us in to the current, broken Bug 968696 stuff16:19
openstackbug 968696 in OpenStack Identity (keystone) ""admin"-ness not properly scoped" [High,In progress] https://launchpad.net/bugs/968696 - Assigned to Adam Young (ayoung)16:19
ayoungI would be fine with it going in afterwards, or if there was a plan to mitigate16:19
hrybackiayoung: how would it do that?16:19
hrybackinon-voting*16:19
lbragstadwe could have a requirement to only add test cases for patrole once an API works in the new default roles and has scope_types set16:19
ayoungI've not gotten a sense from the Patrole team that they take the problem seriously enough16:19
ayoungTBH, if they care about policy, Patrole should be a distant second in effort16:20
ayounggetting the changes in for scope should be full court press16:20
*** arnewiebalck has quit IRC16:21
ayoungfelipemonteiro__, you are the Patrole Point of contact?16:21
hrybackiayoung: folks are working that. I'm wanting to work with the AT&T folks to lay out the legwork for Patrole. I'd like to have a testing strategy ready to go before submitting a Communtiy Goal for the default roles work16:21
*** yamamoto has quit IRC16:21
*** kumarmn has quit IRC16:21
*** cloudrancher has quit IRC16:22
hrybackiI don't presume that goal will be accepted until T release16:23
kmallocPatrole must come after new role work16:23
felipemonteiro__ayoung: yes, as while others are active downstream, i work upstream too16:23
hrybackiI keep hearing that but I don't understand why16:23
ayoungfelipemonteiro__, why do you care?16:23
kmallocWe can't lock in on the broken role setup we have now.16:23
ayoungfelipemonteiro__, why did you build patrole?  What was the impetus?16:23
hrybackikmalloc: I don't get why it would do that16:24
kmallocGating on it locks us/wedges us deeper into where we are today that is seeing a lot of work to undig the hole16:24
lbragstadall the testing would require setup classes and infrastructure to assert scopes and things like that16:24
felipemonteiro__i didn't build it, i helped contribute to it. i care because at&t cares about validating any rbac changes since our rbac customization is rather complex compared to most folks'.16:24
hrybackinon-voting jobs won't lock us in but they will give us a baseline to look back upon16:24
ayoungfelipemonteiro__, that is the problem16:25
gagehugokmalloc I would hope we wouldn't make it voting until the broken roles are fixed16:25
ayoungwe need to change RBAC, radically16:25
ayoungbecause how it exists today is broken16:25
hrybackiI'm not asking us to put in an entire suite of tests -- I just want to ensure that the infrastructure is there for when we are ready to do just that (after role work is in)16:25
kmallochrybacki: try changing something tempest is locked in on. It at least extends the timeframe by 2-3 cycles, and may mean we are even longer pushing out for generalized acceptance/gating of the new way16:25
ayoungand if we test based on how it is today, we will not be able to fix it16:25
ayoungand I am firm on thiws16:25
ayoungthis16:25
ayoungpatrole, without a fix for 968696 is dangerous16:25
*** spilla has joined #openstack-meeting-alt16:25
ayoungand I have been burnt by this pattern before16:26
ayoungwe had tests in tempest that assumed broken behavior16:26
kmallocIn short, it must come (anything that locks/gates/tests with voting) after new role work.16:26
lbragstadis there something preventing us from doing this incrementally?16:26
ayoungand we could not fix in Keystoner because then the tests would fail in tempest, and not pass gate etc16:26
hrybackibut how do we confirm role work is not broken without testing it?16:26
hrybackialso again non-voting**16:26
ayounghrybacki, we know it IS broken today16:27
lbragstadif we add the default roles to an API in keystone, we can add a test to patrole after words to assert the correct behavior along with unit tests, can we not?16:27
kmalloclbragstad: current roles are so narrow, if we test + vote now, we aren't going to be able to move the needle16:27
ayoungonce we fix it, yes, patrole16:27
ayoungnot until16:27
kmallocSo, we should setup patrole to test with the new defaults out the gate.16:27
ayoungfelipemonteiro__, help out on the 968696 work and you will get my full supprt16:27
kmallocJust not on the current broken RBAC setup.16:27
felipemonteiro__ayoung: yeah you're right, we've had to seek out workarounds to said bug internally, including scoping adminness via sub-admin roles and the like, but as a result of which we had to have a means of validation.16:27
ayoungdo we have scope changes for all services?16:27
hrybackikmalloc: that is precisely what I'm shooting to do16:28
*** manjeets_ has quit IRC16:28
ayoungfelipemonteiro__, here is what I would accept16:28
lbragstadi think we've all said the same thing, just different ways16:28
ayounga version of Patrole that fails due to bug 96869616:28
openstackbug 968696 in OpenStack Identity (keystone) ""admin"-ness not properly scoped" [High,In progress] https://launchpad.net/bugs/968696 - Assigned to Adam Young (ayoung)16:28
ayoungand that passes when we show changes go in that fix it16:28
kmallochrybacki: good, what ayoung and I are saying is we absolutely don't want to test current state of the world.16:28
*** radeks_ has quit IRC16:28
kmallocWe're on the same page.16:28
*** erlon has quit IRC16:29
hrybackiokay cool -- so tl;dr ensure the spec clearly indicates the non-voting* gate will be in place and testing against <how we expect success to look after things are resolved>16:29
ayounghrybacki, ++16:29
gagehugohrybacki ++16:29
kmallocAs long as we keep that in mind we are good. Standing patrole up for the new defaults is the confirm we have fixed 9869616:29
kmallocAnd don't regress.16:30
hrybackithis way we have infra in place, that won't interfere with fixes, and doesn't stick us into existing behaviors16:30
kmalloc++16:30
kmallocExactly.16:30
hrybackiexcellent, thanks all :)16:30
hrybackilbragstad: you right16:30
lbragstadit sounds like the patrole spec can be collapsed into the testing section of the default roles one16:30
ayounglbragstad, do we have changes in place for, say cinder, neutron, glance, as well as nova?16:30
lbragstadayoung: i've been working on patches for nova, but i haven't gotten everythign done yet16:30
hrybackilbragstad: I'm not sure I want to tightly couple them but dont' have solid reasons to jusitfy that intuitino yet16:30
lbragstadwaiting on the ksm patch and the oslo.context patch16:31
ayoungkeep them separate, but link them at the related specs section16:31
lbragstadhrybacki: ayoung ok - wfm16:31
hrybackiare we okay to un-abandon https://review.openstack.org/#/c/464678/ in this case?16:31
*** spilla has quit IRC16:31
felipemonteiro__ayoung: i can certainly try to assist in changing things w.r.t to things like system scoping but it's not my full time job, so any change that isn't forthcoming isn't because of a lack of agreement or consensus16:31
hrybackiI can work with felipemonteiro__ to bring it up-to-date given today's discussion16:32
*** kumarmn has joined #openstack-meeting-alt16:32
ayoungIts just a -116:32
ayounghrybacki, TYVM16:32
hrybackithanks for popping in felipemonteiro__ -- lbragstad that is all I have on that topic16:33
lbragstadcool16:34
lbragstad#topic multisite support16:34
*** openstack changes topic to "multisite support (Meeting topic: keystone)"16:34
lbragstadayoung:  i think this one was you?16:34
zzzeekhey this is me16:34
lbragstadhey zzzeek16:34
zzzeeki got alerted to a blueprint that ayoung is working on which is about something ive already been working on for months16:34
ayoung#link https://review.openstack.org/#/c/566448/16:34
zzzeekwhich is being able to have multiple overclouds coordinate against a single keystone database16:34
zzzeekwe've already worked out a deployment plan for this as well as solved a few thorny issues in making it work with very minimal tripleo changes16:35
ayoungthe pattern we are seeing is that multi-site is not necessarily planned up front16:35
ayounginstead, a large organization might have several openstack deployments, and they realize that they need to be run as multiple regions of a single deployment16:35
zzzeekright...so i call it  a "stretch" clsuter, where you take the two overclouds and then you add a glaera database that is "stretched" over the two or more overclouds16:36
lbragstad#link https://github.com/zzzeek/stretch_cluster/tree/standard_tripleo_version16:36
zzzeekso that's a working POC16:36
kmallocSounds like something icky to setup, but a good approach in general.16:36
ayoungFor people not up-to-speed with Tripleo, overcloud is the term for the openstack cluster we care about16:36
zzzeekwhich does what it has to in order to make the two overclouds talk, so the plan is, make it nicer and make it not break with upgrades16:36
ayoungthere is an undercloud using ironic but those are site specific16:36
zzzeekright so here we are assuming: tripleo, pacemaker / HA, docker containers, galera16:37
kmallocThe only sticky point is divergence of keystone data, afaict.16:37
ayoungzzzeek, and for the overcloud, we are supporting Keystone,nova,neutron,glance,swift, cinder, Sahara?16:37
ayoungkmalloc, it is a major stickypoint, yes16:38
*** rossella_s has quit IRC16:38
kmallocBetween the two sites (assuming these are existing clouds)16:38
zzzeekayoung: keystone is the only service that actually communicates over the two overclouds.  the rest of the servcies remain local to their overcloud16:38
kmallocIf it is strictly a new deployment, less icky.16:38
zzzeekso for the merging of data, O16:38
zzzeekI've been assuming that the overclouds are built up indepdendntly but plan to be merged immediately16:38
ayoungupgrades should be able to use the Keystone 0 downtime upgrade mechanism,16:39
zzzeekso the keystone DBs are built up individually using distinct region names16:39
kmallocThat is less problematic to address.16:39
ayoungrole IDs should be synced16:39
zzzeekthen the DBs are merged where all region-specific records are added16:39
*** yamamoto has joined #openstack-meeting-alt16:39
kmallocLong running clouds would be hard (tm)16:39
zzzeekat the moment I just use SQL scripts inside of an ansible playbook to do this16:39
ayounglong running would require db conversion scripts, I would think16:39
ayoungnot to be lightly undertaken, but not impossible16:40
kmallocayoung: yes. And it gets very sticky.16:40
ayoungjust...don't try to do it while running the cloud16:40
*** rossella_s has joined #openstack-meeting-alt16:40
kmalloczzzeek: we could wrap that into a keystone-manage (vs ansible)16:40
kmallocAnd I'd be ok with that.16:40
ayoungi.e.  stop keystone, run script, start keystone16:40
ayoung++16:40
*** manjeet has joined #openstack-meeting-alt16:40
zzzeekkmalloc: yes it woudl be a keystone command16:40
ayoungthe biggest problem I would expect would be the Default domain16:41
kmallocayoung: id is "default"16:41
ayoungeveryone has one, and they have the same ID and Name, but then there are all the projects under16:41
kmallocSo, not a big issue.16:41
ayoungall of the projects under it will conflict, tho16:41
zzzeekkmalloc: but additional work here that is outside of keystone involves deploying the galera cluster across datacenters.    since ayoung's spec is against tripleo, that would be part of it right?16:41
kmallocThis is not long running clouds, so manageable.16:41
ayoungso if you have 2 clouds, and each has a Production proejct, in default domain, they will have same names, different Ids16:42
ayoungright,16:42
kmalloczzzeek: yes, with a spec/something for keystone to track against16:42
*** manjeets_ has joined #openstack-meeting-alt16:42
ayoungfor long running clouds, you would say "get everything off the default domain"16:42
ayoungbefore you could even consider something like this16:42
kmallocBut our side is pretty minimal, if you want to move it out of ansible.. non-existent if ansible is a-ok to continue with.16:43
zzzeekkmalloc: the ansible thing i have right now is not production grade since it is hardcoding SQL in it16:43
ayoungwould that be something we could do in a migration?16:43
ayoungis it a run once type thing?16:43
kmallocayoung: unlikely.16:43
zzzeekayoung: not really, it deosnt chagne the structure of the database, it's about data coming into the DB16:43
kmallocBut we can explore it.16:43
zzzeekayoung: it's like, here's a keystone DB, heres a bunch of new services etc. from a new region16:44
zzzeekthat can happen any number of times16:44
lbragstadand it must be idempotent, right?16:44
kmallocYeah, I would expect it to be idempotent16:44
zzzeeklbragstad: well if it's a keystone-manage command, it's always nice if it is but i dont know it's 100% necessary16:45
*** manjeet has quit IRC16:45
kmallocI think idempotent is a requirement. Risk of breaking things if it isn't is high16:45
*** chandankumar has joined #openstack-meeting-alt16:45
zzzeekkmalloc: sure.  so keystone might need to have some knowledge of this16:45
kmallocAnd up-arrow+enter could ruin a cloud.16:46
zzzeeke.g. the keystone db16:46
zzzeekkmalloc: yes if you're guarding against arrow-enter then yes, you need some kind of record that shows somehting already happened16:46
kmallocYep.16:46
zzzeekso i didn't manage to get "domains" to do this, keystone seemed pretty intent on "domain" being "default"16:46
zzzeekit seemed like "regions" were the correct concept16:46
kmallocAnd keystone-manage commands are mostly safe to run anytime(tm)16:46
zzzeekis that not correct ?16:46
*** jtomasek has quit IRC16:47
ayoungso...from keystone-manage, we would want utilities to rename domains and regions.  Anything else?16:47
kmallocThis sounds like regions to me. Domains are containers.. you'll need to replicate them, but that is fine.16:47
zzzeekkmalloc: here's the code right now: https://github.com/zzzeek/stretch_cluster/blob/standard_tripleo_version/roles/setup-keystone-db/tasks/main.yml#L2916:47
zzzeekkmalloc: which got me a basic nova hello world going16:48
kmallocCool.16:48
zzzeekkmalloc: there's a copy of each keystone DB on the shared cluster, keystone1 and keystone2, and it just copies region and endpoint in and that's it16:48
kmallocYeah that should ultimately be doable via keystone-manage.16:48
ayoungSome of that is Tripleo specific, I think.  If you install Keystone, you don't get any service catalog by default16:48
zzzeekkmalloc: seemed a little too simple16:48
kmallocSo, you're going to run into some issues with roles, projects, etx16:48
*** dklyle has quit IRC16:48
*** EmilienM is now known as EmilienM_PTO16:49
zzzeekkmalloc: so the assumption i made was that, you've just deployed the two overclouds assuming this case so they have the same passwods, the same projects and roles, etc.16:49
ayoungah...rigjht...role IDs should be sync-able, too16:49
kmallocBasically that doesn't solve authn/authz across the clouds consistently16:49
ayoungand that will be an expensive database update16:49
kmallocProject IDs are uuid4 generated16:49
zzzeekkmalloc: for our initial version we were going to keep it simple that the two overclouds can fold into each other16:49
kmallocSo, if any are created, IDs won't be the same.16:49
ayoungprojects should be left alone16:49
ayoungthe problem is if two clusters have the same project name in the same domain.  New install, not an issue16:50
kmallocSame with users, etc. Passwords are bcrypt, so salted ...same but different t hashed strings.16:50
zzzeekkmalloc: yeah i acually deployed the overclouds w/ identical passwords to solve that :)16:50
ayoungcan we sync the salt?16:50
kmallocWe would need to sync the hash.16:50
*** oikiki has joined #openstack-meeting-alt16:51
kmallocWhich covers the salt.16:51
kmallocWe can't force a salt within keystone16:51
zzzeeki would say, pick a winner, the operator has to know the passwords are going to change if they aren't the same already16:52
kmalloczzzeek: so, you will see drift of data between the keystone's if we're only galeraing the regions/catalog.16:52
*** kumarmn has quit IRC16:52
zzzeekkmalloc: right.  initial use case is that you have a brand new keystone DB in both datacenters16:52
kmallocRight, you should setup a "master cloud" that populates the new cloud16:52
kmallocAnd overwrites things as needed.16:53
ayoungso, I think we need a spec for the keystone manage changes we want to support this, right?16:53
kmallocYeah, I think we do16:53
kmallocThis isn't a bad concept, or even anything outlandish16:53
zzzeekOK so from my perspective, I'm looking at the full view, which is, you have two tripleo overclouds, you have deployed such that keystones are talking to a separate galera DB that is local to their environment, the "stretch" operation then pulls those galeras into a single cross-datacenter cluster and the keystone data is merged16:54
kmallocJust need to have it clearly written.16:54
lbragstadwe'll need a proposal exception as well16:54
ayoungI did start a tripleo spec, but I think I want a separate one for the Keystone options16:54
*** kumarmn has joined #openstack-meeting-alt16:54
zzzeekalso since nobody asked, the big trick here is that I modified the pacemaker resource agent to allow multiple pacemakers to coordinate a single galera cluster16:54
kmalloczzzeek: that sounds reasonable. Then pivot the keystone to read/write from.galera16:54
ayoungI'll submit a placeholder16:54
kmallocOnce the new db is in place.16:55
lbragstadjust a heads up, we're at 5 minutes remaining16:55
kmallocayoung: this may need to be a "utility" separate from keystone e-manage16:55
zzzeekwhat also is nice is that the keystone services never change the DB they talk to, it's a galera cluster that just suddenly has new nodes as part of it16:55
kmallocayoung: let's get a spec and go from there. Make sure to add clear use-case descriptions16:56
ayoungkmalloc, if so, we'll get that in the spec16:56
kmallocSo we don't need to refer to the meeting long to remember it all :)16:56
*** derekh has quit IRC16:57
lbragstadi look forward to reading the spec, it'll be more clear to me on paper i think16:58
kmalloc#action ayoung to write up spec for stretch over cloud with zzzeek16:58
*** kumarmn_ has joined #openstack-meeting-alt16:58
*** kumarmn has quit IRC16:58
lbragstadany other comments on this topic?16:59
lbragstadthanks zzzeek17:00
lbragstad#topic open discussion17:00
*** openstack changes topic to "open discussion (Meeting topic: keystone)"17:00
lbragstadlast minute -17:00
lbragstadwxy|: has a new version of the unified limit stuff up17:00
lbragstadand it looks really good17:00
lbragstadeveryone here should go read17:00
lbragstad:)17:00
lbragstad#link https://review.openstack.org/#/c/540803/1017:00
gagehugolemme leave a tab open for it17:00
* hrybacki same17:01
lbragstadthanks for the time everyone!17:01
lbragstad#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:01
openstackMeeting ended Tue May  8 17:01:10 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-05-08-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-05-08-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-05-08-16.00.log.html17:01
*** wxy| has quit IRC17:02
*** sambetts is now known as sambetts|afk17:02
*** kumarmn_ has quit IRC17:02
*** gagehugo has left #openstack-meeting-alt17:03
*** dklyle has joined #openstack-meeting-alt17:04
*** kumarmn has joined #openstack-meeting-alt17:04
*** tosky has joined #openstack-meeting-alt17:05
*** e0ne has joined #openstack-meeting-alt17:10
*** yamamoto has quit IRC17:10
*** kumarmn has quit IRC17:11
*** e0ne has quit IRC17:12
*** panda is now known as panda|off17:16
*** gyee has quit IRC17:17
*** ayoung is now known as ayoung-dentist17:25
*** slaweq has quit IRC17:25
*** slaweq has joined #openstack-meeting-alt17:26
*** harlowja has quit IRC17:31
*** slaweq has quit IRC17:31
*** e0ne has joined #openstack-meeting-alt17:32
*** julim has joined #openstack-meeting-alt17:33
*** kumarmn has joined #openstack-meeting-alt17:33
*** julim has quit IRC17:33
*** dklyle has quit IRC17:37
*** kumarmn has quit IRC17:38
*** slaweq has joined #openstack-meeting-alt17:41
*** kumarmn has joined #openstack-meeting-alt17:41
*** julim has joined #openstack-meeting-alt17:42
*** slaweq has quit IRC17:45
*** tssurya has quit IRC17:50
*** jlvillal is now known as jlvacation17:51
*** jtomasek has joined #openstack-meeting-alt17:54
*** kumarmn_ has joined #openstack-meeting-alt18:04
*** rossella_s has quit IRC18:05
*** kumarmn has quit IRC18:05
*** myoung|ruck is now known as myoung|ruck|biab18:07
*** felipemonteiro__ has quit IRC18:10
*** felipemonteiro__ has joined #openstack-meeting-alt18:10
*** yamamoto has joined #openstack-meeting-alt18:11
*** radeks_ has joined #openstack-meeting-alt18:11
*** kumarmn has joined #openstack-meeting-alt18:11
*** kumarmn_ has quit IRC18:14
*** gyee has joined #openstack-meeting-alt18:19
*** Bonjourm8 has joined #openstack-meeting-alt18:20
*** yamamoto has quit IRC18:21
*** kumarmn has quit IRC18:22
*** erlon has joined #openstack-meeting-alt18:22
*** kumarmn has joined #openstack-meeting-alt18:25
*** harlowja has joined #openstack-meeting-alt18:25
*** vabada2 has joined #openstack-meeting-alt18:26
*** vabada has quit IRC18:27
*** erlon has quit IRC18:28
*** sridharg has quit IRC18:29
*** kumarmn has quit IRC18:29
*** strigazi has quit IRC18:30
*** strigazi has joined #openstack-meeting-alt18:31
*** kumarmn has joined #openstack-meeting-alt18:36
*** rossella_s has joined #openstack-meeting-alt18:37
*** e0ne has quit IRC18:38
*** kumarmn_ has joined #openstack-meeting-alt18:38
*** kumarmn_ has quit IRC18:38
*** kumarmn_ has joined #openstack-meeting-alt18:39
*** Swami has joined #openstack-meeting-alt18:39
*** kumarmn has quit IRC18:41
*** kumarmn_ has quit IRC18:43
*** kumarmn has joined #openstack-meeting-alt18:43
*** Swami has quit IRC18:45
*** kumarmn has quit IRC18:48
*** jtomasek has quit IRC18:48
*** Bonjourm8 has quit IRC18:52
*** e0ne has joined #openstack-meeting-alt19:02
*** julim has quit IRC19:04
*** dklyle has joined #openstack-meeting-alt19:09
*** Swami has joined #openstack-meeting-alt19:10
*** Swami_ has joined #openstack-meeting-alt19:10
*** vgreen has quit IRC19:13
*** dave-mcc_ has quit IRC19:14
*** dave-mccowan has joined #openstack-meeting-alt19:20
*** e0ne has quit IRC19:24
*** david-lyle has joined #openstack-meeting-alt19:27
*** myoung|ruck|biab is now known as myoung|ruck19:29
*** slaweq has joined #openstack-meeting-alt19:41
*** slaweq has quit IRC19:45
*** kumarmn has joined #openstack-meeting-alt19:48
*** kumarmn has quit IRC19:52
*** kumarmn has joined #openstack-meeting-alt19:53
*** florianf has quit IRC19:56
*** kumarmn has quit IRC19:57
*** markstur has quit IRC19:59
*** julim has joined #openstack-meeting-alt20:01
*** radeks__ has joined #openstack-meeting-alt20:04
*** radeks_ has quit IRC20:05
*** radeks has quit IRC20:06
*** tosky has quit IRC20:08
*** tosky has joined #openstack-meeting-alt20:08
*** markstur has joined #openstack-meeting-alt20:11
*** rmascena has quit IRC20:12
*** e0ne has joined #openstack-meeting-alt20:20
*** julim has quit IRC20:24
*** dklyle has quit IRC20:32
*** edmondsw has quit IRC20:33
*** e0ne has quit IRC20:45
*** ttsiouts_ has joined #openstack-meeting-alt20:46
*** slaweq has joined #openstack-meeting-alt20:49
*** radeks__ has quit IRC20:53
*** ayoung-dentist is now known as ayoung20:57
*** kumarmn has joined #openstack-meeting-alt21:05
*** kumarmn has quit IRC21:09
*** dustins has quit IRC21:09
*** felipemonteiro_ has joined #openstack-meeting-alt21:13
*** ianychoi has quit IRC21:15
*** felipemonteiro__ has quit IRC21:17
*** david-lyle has quit IRC21:23
*** felipemonteiro__ has joined #openstack-meeting-alt21:38
*** felipemonteiro_ has quit IRC21:38
*** markvoelker_ has joined #openstack-meeting-alt21:41
*** markvoelker has quit IRC21:42
*** kumarmn has joined #openstack-meeting-alt21:45
*** jcoufal has quit IRC21:47
*** ttsiouts_ has quit IRC21:48
*** kumarmn has quit IRC21:51
*** manjeets_ has quit IRC21:53
*** oikiki has quit IRC21:55
*** clopez has quit IRC22:06
*** kumarmn has joined #openstack-meeting-alt22:09
*** kumarmn has quit IRC22:13
*** rwsu has quit IRC22:13
*** kumarmn has joined #openstack-meeting-alt22:14
*** MarkBaker has quit IRC22:14
*** kumarmn has quit IRC22:17
*** kumarmn has joined #openstack-meeting-alt22:17
*** clopez has joined #openstack-meeting-alt22:20
*** kumarmn has quit IRC22:22
*** myoung|ruck is now known as myoung|ruck|bbl22:23
*** rcernin has joined #openstack-meeting-alt22:25
*** felipemonteiro_ has joined #openstack-meeting-alt22:34
*** felipemonteiro__ has quit IRC22:37
*** julim has joined #openstack-meeting-alt22:38
*** kumarmn has joined #openstack-meeting-alt22:48
*** hongbin has quit IRC22:48
*** kumarmn has quit IRC22:51
*** kumarmn has joined #openstack-meeting-alt22:51
*** julim has quit IRC22:52
*** kumarmn has quit IRC22:52
*** julim has joined #openstack-meeting-alt22:53
*** slaweq has quit IRC22:57
*** tpsilva has quit IRC22:58
*** felipemonteiro__ has joined #openstack-meeting-alt23:04
*** felipemonteiro_ has quit IRC23:04
*** felipemonteiro__ has quit IRC23:14
*** kumarmn has joined #openstack-meeting-alt23:17
*** julim has quit IRC23:18
*** kumarmn has quit IRC23:18
*** kumarmn has joined #openstack-meeting-alt23:19
*** kumarmn has quit IRC23:19
*** kumarmn has joined #openstack-meeting-alt23:20
*** kumarmn_ has joined #openstack-meeting-alt23:23
*** kumarmn has quit IRC23:25
*** kumarmn has joined #openstack-meeting-alt23:26
*** tosky has quit IRC23:27
*** kumarmn_ has quit IRC23:27
*** julim has joined #openstack-meeting-alt23:29
*** kumarmn has quit IRC23:31

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