Tuesday, 2018-04-24

*** gyee has quit IRC00:02
*** chyka has quit IRC00:11
*** jcoufal_ has quit IRC00:23
*** rmascena__ has quit IRC00:25
*** tonyb has quit IRC00:33
*** bobmel has joined #openstack-meeting-alt00:33
*** tonyb has joined #openstack-meeting-alt00:35
*** cloudrancher has quit IRC00:36
*** bobmel has quit IRC00:38
*** spzala has joined #openstack-meeting-alt00:49
*** kumarmn has joined #openstack-meeting-alt00:53
*** hiro-kobayashi has joined #openstack-meeting-alt01:09
*** julim has joined #openstack-meeting-alt01:12
*** spzala has quit IRC01:13
*** julim has quit IRC01:14
*** kumarmn has quit IRC01:15
*** kumarmn has joined #openstack-meeting-alt01:20
*** kumarmn has quit IRC01:25
*** yamahata has quit IRC01:26
*** salv-orl_ has joined #openstack-meeting-alt01:28
*** salv-orlando has quit IRC01:31
*** markstur has quit IRC01:31
*** hongbin_ has joined #openstack-meeting-alt01:32
*** dalgaaf has quit IRC01:42
*** dalgaaf has joined #openstack-meeting-alt01:43
*** spzala has joined #openstack-meeting-alt01:52
*** spzala has quit IRC01:57
*** caowei has joined #openstack-meeting-alt02:04
*** fnaval has quit IRC02:22
*** spzala has joined #openstack-meeting-alt02:34
*** bobmel has joined #openstack-meeting-alt02:34
*** julim has joined #openstack-meeting-alt02:35
*** bobmel has quit IRC02:40
*** spzala has quit IRC02:48
*** yamamoto has quit IRC02:53
*** yamamoto has joined #openstack-meeting-alt02:54
*** yamamoto has quit IRC02:59
*** markstur has joined #openstack-meeting-alt03:31
*** hiro-kobayashi has quit IRC03:35
*** lpetrut has joined #openstack-meeting-alt03:39
*** kumarmn has joined #openstack-meeting-alt03:42
*** janki has joined #openstack-meeting-alt03:44
*** sridharg has joined #openstack-meeting-alt03:48
*** kumarmn has quit IRC03:49
*** shu-mutow-AWAY is now known as shu-mutow03:57
*** hongbin_ has quit IRC03:58
*** ianychoi has quit IRC04:02
*** ianychoi has joined #openstack-meeting-alt04:04
*** kumarmn has joined #openstack-meeting-alt04:05
*** kumarmn has quit IRC04:10
*** lpetrut has quit IRC04:11
*** dklyle has joined #openstack-meeting-alt04:17
*** anilvenkata has joined #openstack-meeting-alt04:19
*** markstur has quit IRC04:22
*** anilvenkata has quit IRC04:23
*** markstur has joined #openstack-meeting-alt04:24
*** ianychoi has quit IRC04:28
*** markvoelker has quit IRC04:29
*** ianychoi has joined #openstack-meeting-alt04:31
*** julim has quit IRC04:34
*** bobmel has joined #openstack-meeting-alt04:35
*** dklyle has quit IRC04:37
*** slaweq has joined #openstack-meeting-alt04:39
*** janki has quit IRC04:39
*** bobmel has quit IRC04:40
*** edmondsw has joined #openstack-meeting-alt04:43
*** edmondsw_ has joined #openstack-meeting-alt04:44
*** slaweq has quit IRC04:47
*** edmondsw has quit IRC04:48
*** lpetrut has joined #openstack-meeting-alt04:58
*** edmondsw_ has quit IRC04:59
*** lpetrut has quit IRC05:27
*** bobmel has joined #openstack-meeting-alt05:36
*** marios has joined #openstack-meeting-alt05:39
*** bobmel has quit IRC05:41
*** edmondsw has joined #openstack-meeting-alt05:41
*** edmondsw has quit IRC05:45
*** janki has joined #openstack-meeting-alt05:49
*** shu-mutow is now known as shu-mutow-AWAY05:59
*** edmondsw has joined #openstack-meeting-alt06:02
*** edmondsw has quit IRC06:06
*** MarkBaker has quit IRC06:07
*** julim has joined #openstack-meeting-alt06:08
*** links has joined #openstack-meeting-alt06:16
*** bhavik1 has joined #openstack-meeting-alt06:17
*** bhavik1 has quit IRC06:23
*** armaan has joined #openstack-meeting-alt06:24
*** armaan has quit IRC06:24
*** trinaths has joined #openstack-meeting-alt06:24
*** jtomasek has joined #openstack-meeting-alt06:25
*** lpetrut has joined #openstack-meeting-alt06:29
*** markvoelker has joined #openstack-meeting-alt06:30
*** MarkBaker has joined #openstack-meeting-alt06:31
*** slaweq has joined #openstack-meeting-alt06:32
*** kopecmartin has joined #openstack-meeting-alt06:33
*** trungnv has joined #openstack-meeting-alt06:41
*** slaweq has quit IRC06:42
*** salv-orl_ has quit IRC06:45
*** salv-orlando has joined #openstack-meeting-alt06:46
*** tesseract has joined #openstack-meeting-alt06:49
*** salv-orlando has quit IRC06:50
*** markstur has quit IRC06:55
*** ianychoi has quit IRC07:00
*** salv-orlando has joined #openstack-meeting-alt07:00
*** markvoelker has quit IRC07:04
*** armaan has joined #openstack-meeting-alt07:06
*** ianychoi has joined #openstack-meeting-alt07:11
*** slaweq has joined #openstack-meeting-alt07:16
*** rcernin has quit IRC07:16
*** jchhatbar has joined #openstack-meeting-alt07:21
*** oikiki has joined #openstack-meeting-alt07:23
*** janki has quit IRC07:23
*** edmondsw has joined #openstack-meeting-alt07:24
*** armaan has quit IRC07:28
*** edmondsw has quit IRC07:28
*** rmart04 has joined #openstack-meeting-alt07:31
*** bobmel has joined #openstack-meeting-alt07:37
*** bobmel has quit IRC07:42
*** derekjhyang has quit IRC07:44
*** edmondsw has joined #openstack-meeting-alt07:45
*** ethfci has quit IRC07:45
*** tssurya has joined #openstack-meeting-alt07:45
*** ethfci has joined #openstack-meeting-alt07:45
*** macermak has joined #openstack-meeting-alt07:46
*** ethfci has quit IRC07:47
*** ethfci has joined #openstack-meeting-alt07:47
*** edmondsw has quit IRC07:49
*** dkehn_ has joined #openstack-meeting-alt07:50
*** spzala has joined #openstack-meeting-alt07:53
*** dkehn has quit IRC07:54
*** spzala has quit IRC07:57
*** markvoelker has joined #openstack-meeting-alt08:01
*** oikiki has quit IRC08:03
*** edmondsw has joined #openstack-meeting-alt08:05
*** kumarmn has joined #openstack-meeting-alt08:06
*** armaan has joined #openstack-meeting-alt08:08
*** edmondsw has quit IRC08:09
*** kumarmn has quit IRC08:11
*** vds has quit IRC08:18
*** dsariel has joined #openstack-meeting-alt08:20
*** priteau has joined #openstack-meeting-alt08:25
*** edmondsw has joined #openstack-meeting-alt08:26
*** bfernando has joined #openstack-meeting-alt08:27
*** edmondsw has quit IRC08:30
*** markvoelker has quit IRC08:34
*** derekh has joined #openstack-meeting-alt08:41
*** MarkBaker has quit IRC08:42
*** hiro-kobayashi has joined #openstack-meeting-alt08:42
*** radeks has joined #openstack-meeting-alt08:48
*** ianw is now known as ianw_pto08:54
*** armaan has quit IRC08:58
*** armaan has joined #openstack-meeting-alt08:58
*** masahito has joined #openstack-meeting-alt09:00
masahito#startmeeting blazar09:01
openstackMeeting started Tue Apr 24 09:01:06 2018 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: blazar)"09:01
openstackThe meeting name has been set to 'blazar'09:01
masahitohi all, time to blazar meeting09:01
masahito#topic RollCall09:01
*** openstack changes topic to "RollCall (Meeting topic: blazar)"09:01
hiro-kobayashio/09:02
masahitoTodya's agenda is09:02
masahito1. September PTG09:02
masahito2. PlacementAPI support09:02
masahito3. Reservation re-allocation09:02
masahito4. AOB09:02
masahitoanything else?09:02
priteauo/09:02
masahitohiro-kobayashi, priteau: hi09:02
priteauGood morning masahito and hiro-kobayashi09:02
masahitopriteau: good morning :-)09:02
*** armaan has quit IRC09:03
hiro-kobayashihi priteau09:03
masahitobertys and GeraldK told me they can't join today's meeting.09:03
masahito#topic September PTG survey09:03
*** openstack changes topic to "September PTG survey (Meeting topic: blazar)"09:03
masahitoThe official announced the next PTG for Stein will be held in Denver on 10th-14th Sep.09:05
masahitohttp://lists.openstack.org/pipermail/openstack-dev/2018-April/129564.html09:05
masahitoThey asked me that we plan to have PTG during this week.09:06
masahitoDo you both have a plan to join the PTG?09:07
hiro-kobayashiYes, I plan to join it.09:07
priteauI can't say yet, it will depend if my employer is happy for me to travel there09:07
masahitoThey also requested me replaying whether to have or not to have until 2nd May.09:08
masahitoI plan to join it, too.09:09
priteauIf it's just hiro-kobayashi and you, would you still hold a Blazar meeting there?09:09
-masahito- So looks like few of us will attend the PTG. I'll replay we plan to have meeting.09:10
hiro-kobayashiI hope new people will join it.09:10
priteauThat would be great.09:10
masahitopriteau: If it's just us, we can implement new features there instead of discussion.09:11
priteauA hackathon? :-)09:11
masahitoyes :-)09:11
hiro-kobayashiSounds good :-)09:12
priteauI will try to let you know if I can attend as soon as possible, but I might know only weeks from now09:12
masahitoI plan to join other project meeting. So I'll be there in either case.09:12
masahitopriteau: got it. The early bird ticket will end by 10th May.09:13
priteauI will get a ticket anyway, since refund is possible until end of August09:14
*** sridharg has quit IRC09:14
masahitosounds nice.09:14
masahitoanything else for this topic?09:15
masahito#topic PlacementAPI support09:16
*** openstack changes topic to "PlacementAPI support (Meeting topic: blazar)"09:16
masahitoI heard hiro-kobayashi has something to discuss for the topic.09:17
hiro-kobayashiyes09:17
hiro-kobayashiI created an etherpad for discussing placement support: https://etherpad.openstack.org/p/blazar-placement-design09:17
hiro-kobayashiI wrote requirements and basic approaches down there.09:18
*** sridharg has joined #openstack-meeting-alt09:18
hiro-kobayashiThe approach 1, 3 and 4 were basically copied from the Dublin PTG etherpad.09:18
hiro-kobayashiI don't understand much about approach 4, though.09:19
priteauThank you hiro-kobayashi for creating the document09:19
priteauI think there is also the concept of aggregates in placement API09:20
masahitohiro-kobayashi: Nice works.09:20
hiro-kobayashipriteau: Yes it would be. I appreciate it if you could write your idea down there09:20
hiro-kobayashiAnd, feel free to edit existing ideas09:21
hiro-kobayashiI think it's better to make a consensus on the basic approach in the Blazar team before Vancouver summit.09:21
priteauI will review and add more details as soon as possible, hopefully this week09:23
masahitoI'd like to add some items for each approach. The way of user interaction with Nova will be changed, etc.09:23
hiro-kobayashiThanks priteau!09:23
hiro-kobayashiThanks!09:23
masahitoMe too. I'll add my comments, too.09:23
masahitoAfter one or two weeks later, we should share this to Placement team.09:24
masahitoAs hiro-kobayashi said, that should be done before the Vancouver summit.09:24
hiro-kobayashimasahito: Agree.09:25
*** panda|bbl is now known as panda|ruck09:25
masahitoanything else?09:26
hiro-kobayashiNothing from me.09:27
masahito#topic Reservation re-allocation09:27
*** openstack changes topic to "Reservation re-allocation (Meeting topic: blazar)"09:27
masahitoI'm working on this spec now. https://docs.openstack.org/blazar/latest/specs/queens/flavors-extra-specs.html09:28
masahitoI want talk about the third work items, Add re-allocation logic to ComputeHostExtraCapability management.09:28
masahitoBased on the discussion on gerrit, Blazar needs to re-allocate reservation once the extra_capability is updated, changed or deleted.09:30
masahitoHowever, Host delete API doesn't allow cloud admins to remove hosts if there are reservations to use the hosts.09:31
*** markvoelker has joined #openstack-meeting-alt09:31
masahitoIMHO, if the Update Host API follows the way of the Delete Host API, the Blazar shouldn't accept the update itself.09:32
priteauOne way to resolve the problem would be to prevent extra capability update if the node is reserved09:32
hiro-kobayashipriteau: +109:33
priteauHowever, that is quite a strong requirement. A better way to handle it would be to prevent extra capability update only if the node has reservations that are using resource_properties09:33
masahitomake sense.09:34
priteauBut we could start with the first approach, and then make it smarter09:34
hiro-kobayashiGood approach09:34
masahitoAlternative is disabling the host and resource-monitoring re-allocate the reservations.09:35
priteauWill it re-allocate a running reservation? I don't remember the behavior09:36
masahitoWhen the reservation is active, resource_changed flag becomes true at least.09:37
hiro-kobayashiCurrently It is not allowed to reallocate if it's active.09:37
*** bobmel has joined #openstack-meeting-alt09:38
hiro-kobayashimasahito: I think blazar should not allow reallocate if it's active except a failure recovery situation.09:38
masahitohiro-kobayashi: IIRC, in addition to resource_changed flag, the missing_resource flag becomes true if there is no alternative resource.09:38
hiro-kobayashiyes09:39
masahitohiro-kobayashi: because it raises complexity of Blazar?09:40
hiro-kobayashimasahito: yes.09:41
masahitogot it.09:42
*** bobmel has quit IRC09:42
masahitoThat's from my side. any comment for the topic?09:42
hiro-kobayashiIf blazar allow reallocation of active reservation, blazar has to handle running instances on removed hosts.09:43
priteaumasahito: I would prefer starting with a simple approach first and increasing complexity later09:44
hiro-kobayashiHow about alining with host reservation update?09:45
hiro-kobayashihttps://github.com/openstack/blazar/blob/master/blazar/plugins/oshosts/host_plugin.py#L52709:45
masahitoI agreed priteau's idea.  I plan to start with your suggestion first.09:45
masahitoI'd like to talk the goal of the BP.09:46
masahitoIf the reservation is in pending status, Blazar try to re-allocate. If it's in active, it fails. right?09:48
masahitoEven if the status is in pending, the update is not allowed in case of missing_resource is true.09:48
hiro-kobayashiI think that's right.09:49
masahitoMake sense. Anyway I'll start with the simple way to do this.09:51
masahito#topic AOB09:51
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:51
masahitoDoes someone have something to share/discuss?09:51
masahitolast 10 mins09:51
hiro-kobayashiNothing from me09:52
priteauI have completed the support for Ironic using Jay's unmerged Nova aggregates patch. The changes to Blazar were quite small.09:53
masahitopriteau: Great work!09:53
hiro-kobayashiGood news!09:54
priteauMoving to placement API will probably be a lot more work ;-)09:55
masahitoYes. But that's a really good news. We can move things forward.09:56
masahitopriteau: btw, do you have some specific topics in next meeting now?  The day of next meeting, 1st May., is holiday in Japan.09:58
priteauNothing specific from me.09:58
priteauWould you like to skip the meeting?09:58
masahitoIf nothing and bertys and GeraldK also doesn't have nothing, I want to skip the meeting.09:58
masahitopriteau: yes.09:58
priteauNo problem09:59
masahitoI'll ask them later. If they doesn't have no topics, I announce the skipping in openstack-dev ML.09:59
-masahito- thanks.10:00
*** julim has quit IRC10:00
masahitoRunning out of time. Nice discussion and greate updates!10:01
masahitoThanks all. bye.10:01
priteauBye everyone, thank you!10:01
masahito#endmeeting10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"10:01
openstackMeeting ended Tue Apr 24 10:01:46 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-04-24-09.01.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-04-24-09.01.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-04-24-09.01.log.html10:01
hiro-kobayashiThank you all! bye!10:01
*** hiro-kobayashi has quit IRC10:01
*** armaan has joined #openstack-meeting-alt10:02
*** trungnv has quit IRC10:02
*** rmart04_ has joined #openstack-meeting-alt10:04
*** macermak has quit IRC10:05
*** macermak has joined #openstack-meeting-alt10:05
*** markvoelker has quit IRC10:06
*** rmart04 has quit IRC10:06
*** rmart04_ is now known as rmart0410:06
*** bobmel has joined #openstack-meeting-alt10:07
*** sambetts_ is now known as sambetts10:11
*** priteau has quit IRC10:11
*** priteau has joined #openstack-meeting-alt10:11
*** rmart04 has quit IRC10:17
*** bfernando has quit IRC10:25
*** armaan has quit IRC10:28
*** armaan has joined #openstack-meeting-alt10:29
*** vds has joined #openstack-meeting-alt10:31
*** armaan has quit IRC10:33
*** rmart04 has joined #openstack-meeting-alt10:33
*** armaan has joined #openstack-meeting-alt10:33
*** vds has quit IRC10:38
*** rmart04 has quit IRC10:46
*** macermak has quit IRC10:57
*** markvoelker has joined #openstack-meeting-alt11:02
*** chyka has joined #openstack-meeting-alt11:06
*** jcoufal has joined #openstack-meeting-alt11:07
*** rmart04 has joined #openstack-meeting-alt11:09
*** chyka has quit IRC11:11
*** caowei has quit IRC11:13
*** trinaths has quit IRC11:14
*** masahito has quit IRC11:15
*** pbourke has quit IRC11:18
*** pbourke has joined #openstack-meeting-alt11:18
*** armaan has quit IRC11:26
*** armaan has joined #openstack-meeting-alt11:26
*** macermak has joined #openstack-meeting-alt11:29
*** armaan has quit IRC11:33
*** armaan has joined #openstack-meeting-alt11:33
*** macermak_ has joined #openstack-meeting-alt11:35
*** markvoelker has quit IRC11:36
*** macermak has quit IRC11:38
*** macermak_ has quit IRC11:45
*** spzala has joined #openstack-meeting-alt11:53
*** liuyulong has joined #openstack-meeting-alt11:54
*** spzala has quit IRC11:57
*** bfernando has joined #openstack-meeting-alt12:00
*** dlenrow has quit IRC12:05
*** dlenrow has joined #openstack-meeting-alt12:06
*** raildo has joined #openstack-meeting-alt12:08
*** zhongjun_ has quit IRC12:09
*** zhongjun_ has joined #openstack-meeting-alt12:09
*** matrohon has joined #openstack-meeting-alt12:12
*** yamamoto has joined #openstack-meeting-alt12:14
*** efried has joined #openstack-meeting-alt12:16
*** markvoelker has joined #openstack-meeting-alt12:16
*** edmondsw has joined #openstack-meeting-alt12:28
*** lbragstad has joined #openstack-meeting-alt12:29
*** edmondsw_ has joined #openstack-meeting-alt12:29
*** tpsilva has joined #openstack-meeting-alt12:29
*** edmondsw has quit IRC12:33
*** vgreen has joined #openstack-meeting-alt12:34
*** panda|ruck is now known as panda|ruck|lunch12:37
*** edmondsw_ has quit IRC12:44
*** edmondsw has joined #openstack-meeting-alt12:48
*** felipemonteiro__ has joined #openstack-meeting-alt12:52
*** edmondsw has quit IRC12:52
*** spzala has joined #openstack-meeting-alt12:53
*** macermak has joined #openstack-meeting-alt12:54
*** learnmore has joined #openstack-meeting-alt12:55
*** spzala has quit IRC12:57
*** edmondsw has joined #openstack-meeting-alt12:59
*** fuqiao has joined #openstack-meeting-alt13:00
*** edmondsw has quit IRC13:01
*** alexchadin has joined #openstack-meeting-alt13:02
*** cloudrancher has joined #openstack-meeting-alt13:04
*** learnmore has quit IRC13:08
*** AlanClark has joined #openstack-meeting-alt13:11
*** armaan has quit IRC13:12
*** armaan has joined #openstack-meeting-alt13:13
*** kumarmn has joined #openstack-meeting-alt13:14
*** salv-orlando has quit IRC13:18
*** salv-orlando has joined #openstack-meeting-alt13:19
*** armaan has quit IRC13:20
*** armaan has joined #openstack-meeting-alt13:21
*** dave-mccowan has joined #openstack-meeting-alt13:22
*** salv-orlando has quit IRC13:24
*** spzala has joined #openstack-meeting-alt13:26
*** edmondsw has joined #openstack-meeting-alt13:27
*** liuyulong has quit IRC13:27
*** yamamoto has quit IRC13:28
*** yamamoto has joined #openstack-meeting-alt13:28
*** edmondsw has quit IRC13:31
*** armaan has quit IRC13:32
*** fuqiao has quit IRC13:32
*** armaan has joined #openstack-meeting-alt13:32
*** fuqiao has joined #openstack-meeting-alt13:32
*** vds has joined #openstack-meeting-alt13:36
*** guyr-infinidat has joined #openstack-meeting-alt13:36
*** panda|ruck|lunch is now known as panda|ruck13:43
*** alexchadin has quit IRC13:50
*** armaan has quit IRC13:51
*** armaan has joined #openstack-meeting-alt13:51
*** felipemonteiro__ has quit IRC13:57
*** felipemonteiro__ has joined #openstack-meeting-alt13:57
*** jaypipes has quit IRC13:58
*** jaypipes has joined #openstack-meeting-alt13:58
*** hongbin_ has joined #openstack-meeting-alt13:59
*** edmondsw has joined #openstack-meeting-alt13:59
*** dustins has joined #openstack-meeting-alt14:00
*** amito has quit IRC14:02
*** amito has joined #openstack-meeting-alt14:02
*** edmondsw has quit IRC14:04
*** yamahata has joined #openstack-meeting-alt14:04
*** edmondsw has joined #openstack-meeting-alt14:04
*** edmondsw has quit IRC14:09
*** edmondsw has joined #openstack-meeting-alt14:09
*** matrohon has quit IRC14:11
*** edmondsw has quit IRC14:14
*** iyamahat has joined #openstack-meeting-alt14:19
*** zhongjun_ has quit IRC14:19
*** cloudrancher has quit IRC14:24
*** alexchadin has joined #openstack-meeting-alt14:25
*** iyamahat has quit IRC14:26
*** iyamahat has joined #openstack-meeting-alt14:26
*** edmondsw has joined #openstack-meeting-alt14:35
*** namnh has joined #openstack-meeting-alt14:35
*** edmondsw has quit IRC14:40
*** links has quit IRC14:42
*** rossella_s has quit IRC14:42
*** edmondsw has joined #openstack-meeting-alt14:42
*** gagehugo has joined #openstack-meeting-alt14:46
*** edmondsw has quit IRC14:46
*** alexchadin has quit IRC14:48
*** markstur has joined #openstack-meeting-alt14:57
*** yamamoto has quit IRC14:58
*** rossella_s has joined #openstack-meeting-alt14:59
*** rmart04 has quit IRC15:01
*** wxy| has joined #openstack-meeting-alt15:02
*** markstur has quit IRC15:02
*** tesseract has quit IRC15:06
*** tesseract has joined #openstack-meeting-alt15:06
*** cloudrancher has joined #openstack-meeting-alt15:10
*** macermak has quit IRC15:12
*** felipemonteiro_ has joined #openstack-meeting-alt15:13
*** alexchadin has joined #openstack-meeting-alt15:13
*** armaan has quit IRC15:14
*** armaan has joined #openstack-meeting-alt15:14
*** felipemonteiro__ has quit IRC15:16
*** kumarmn has quit IRC15:25
*** dklyle has joined #openstack-meeting-alt15:29
*** cloudrancher has quit IRC15:31
*** edmondsw has joined #openstack-meeting-alt15:33
*** salv-orl_ has joined #openstack-meeting-alt15:35
*** kumarmn has joined #openstack-meeting-alt15:37
*** gyee has joined #openstack-meeting-alt15:38
*** kumarmn has quit IRC15:40
*** cloudrancher has joined #openstack-meeting-alt15:41
*** cloudrancher has quit IRC15:42
*** kumarmn has joined #openstack-meeting-alt15:43
*** kumarmn has quit IRC15:45
*** alexchadin has quit IRC15:46
*** matrohon has joined #openstack-meeting-alt15:47
*** kopecmartin has quit IRC15:48
*** felipemonteiro_ has quit IRC15:49
*** felipemonteiro_ has joined #openstack-meeting-alt15:49
*** chyka has joined #openstack-meeting-alt15:50
*** trinaths has joined #openstack-meeting-alt15:52
*** chyka_ has joined #openstack-meeting-alt15:53
*** jbadiapa has quit IRC15:55
*** chyka has quit IRC15:56
*** rossella_s has quit IRC15:59
*** yamamoto has joined #openstack-meeting-alt15:59
*** rossella_s has joined #openstack-meeting-alt15:59
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue Apr 24 16:00:10 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
lbragstadping ayoung, breton, cmurphy, dstanek, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, jdennis, ruan_he, wxy, sonuk16:00
*** openstack changes topic to " (Meeting topic: keystone)"16:00
openstackThe meeting name has been set to 'keystone'16:00
gagehugoo/16:00
hrybackio/16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:00
lbragstadagenda ^16:00
cmurphyo/16:00
knikollao/16:00
wxy|o/16:00
kmalloco/16:01
lbragstad#topic specifications16:01
*** openstack changes topic to "specifications (Meeting topic: keystone)"16:01
lbragstadjust a heads up - we're now past the specification proposal deadline16:02
lbragstadwe'll continue to press on with reviews of what's been proposed16:02
*** spilla has joined #openstack-meeting-alt16:02
lbragstadnext important deadline will be specification freeze which is rocky-2, or June 8th16:03
lbragstad#topic consul16:03
*** openstack changes topic to "consul (Meeting topic: keystone)"16:03
lbragstad#link http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-04-18.log.html#t2018-04-18T13:21:2316:03
lbragstad^ consul came up again in the -tc channel16:03
lbragstadwhich has been a topic that comes up every once in a while16:03
hrybacki'discussed but never implemented' -- just always a low prio?16:04
*** armaan has quit IRC16:04
*** pbourke has quit IRC16:04
lbragstadi'm not even sure we made it that far16:04
*** pbourke has joined #openstack-meeting-alt16:04
*** yamamoto has quit IRC16:04
lbragstadhere is a list of every time it's been mentioned in keystone http://paste.openstack.org/raw/719483/ (i think)16:04
*** armaan has joined #openstack-meeting-alt16:05
lbragstadlist of logs*16:05
gagehugohmm16:05
hrybackinice tool lbragstad16:05
lbragstaddoes this seem like something that would be appropriate for the idea log? http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ideas/README.html16:05
*** kumarmn has joined #openstack-meeting-alt16:06
cmurphywhat is the use case?16:06
lbragstadso - consul is service discovery software16:06
lbragstadthe use case would be that we would off load service catalog stuff to consul instead of reinventing the wheel16:06
lbragstadbut kmalloc knows way more about it than i do16:07
kmallocif we want something clever, like services self-registering.16:07
kmallocconsul is great16:07
kmallocotherwise it's not much different than we have now16:07
*** armaan_ has joined #openstack-meeting-alt16:07
cmurphyso rewrite the service catalog in order to avoid writing a new service catalog?16:07
cmurphysorry didn't mean for that to come out so cynical16:08
lbragstadi was under the impression we would implement a driver or work directly with services to leverage consul16:08
lbragstads/driver/catalog driver/16:08
*** armaan has quit IRC16:08
*** kumarmn_ has joined #openstack-meeting-alt16:09
*** armaan_ has quit IRC16:09
*** bfernando has quit IRC16:10
lbragstad(i believe the second option would offload the responsibility of the catalog to a separate service, and users would talk to consul to figure out where to go to interact with services in a deployment)16:10
*** kumarmn has quit IRC16:10
*** iyamahat has quit IRC16:10
*** rossella_s has quit IRC16:10
*** fuqiao has quit IRC16:12
*** armaan has joined #openstack-meeting-alt16:12
kmalloclbragstad: coreect16:13
*** armaan has quit IRC16:13
kmallocif we are doing that16:13
kmallocbut... i am against the speculative "maybe" bit of a driver16:13
kmallocif consul isn't really a dep of openstack, I don't want to add it16:13
cmurphy++16:13
kmallocit's why i pushed for picking zookeeper...or consul...or even etcd16:13
kmallocand we ended up with "well ALL OF THEM/any"16:14
cmurphyetcd is a base service of openstack16:14
lbragstad^ that's a good point that someone brought up in the discussion a couple days ago16:14
kmallocetcd is mostly a base service.16:14
kmallocso, if we are picking one, i'd say hard set on etcd16:14
kmallocnot "add consul"16:14
kmallocand work around etcd's limitations16:14
kmallocif we can16:14
*** rossella_s has joined #openstack-meeting-alt16:15
*** yamahata has quit IRC16:15
lbragstadok - the fact that consul gets brought up every few/six months tells me it's worth investigating, but i don't expect anyone to sign up for this16:15
lbragstadthat said, where should we document this?16:15
kmalloc*shrug*16:16
lbragstadit feels like a PoC of some kind is needed16:16
kmalloci'm going to be very anti-consul for catalog unless we have some serious weight behind it... even with a PoC16:16
cmurphyi'd like to see some evidence or arguments for why this is better than what we have now and worth us putting in the effort, or else see someone with a specific use case step up to do the work16:16
cmurphywe don't have the bandwidth to take on projects just because16:16
kmalloccmurphy: ++16:16
gagehugoyeah..16:16
lbragstadoh - sorry, i meant in more of a general sense and not just consul16:17
wxy|So users want Keystone to support service self-registering One of the driver may be consul.16:17
wxy|right?16:17
kmallocwxy|: sortof...16:17
kmallocself-registering and direct query by endpoints vs. in token16:17
lbragstadcmurphy: i completely agree about bandwidth16:18
lbragstadi don't want to propose more work for the sake of work, but during the tc discussion it was apparent that this particular thing has been brought up consistently since ~201516:21
lbragstadi guess my end goal was to either open a wishlist bug describing the thing that gets brought up or somehow make it discoverable so that if someone did want to do a PoC they wouldn't have to dig through all the context again16:22
*** tssurya has quit IRC16:23
hrybackiI think adding this to the idea list and letting relevant ideas formulate there until a strong ask arises is a good idea16:24
hrybackithen we have some documented history and can make a more educated decision when priorities begin to shift?16:24
lbragstadif people don't have any objections to that, i can take a stab at proposing it to the idea log16:24
cmurphyi think that's fine, as long as the idea is "do some research on this" and not "implement this"16:25
lbragstad++16:25
lbragstadagreed16:25
hrybacki++16:25
lbragstad#action lbragstad to fill out and idea form for consul16:25
*** jessegler has joined #openstack-meeting-alt16:25
*** bhavik1 has joined #openstack-meeting-alt16:25
lbragstad#topic idempotent migrations16:25
*** openstack changes topic to "idempotent migrations (Meeting topic: keystone)"16:26
lbragstadhrybacki: o/16:26
hrybackio/16:26
hrybackiSo stemming from the review posted by Ade16:26
hrybacki#link https://review.openstack.org/#/c/563266/16:26
*** kumarmn_ has quit IRC16:26
hrybackitl;dr -- let's discuss the merits of making migrations idempotent as a requirement/recommendation/requirement under sitautions x, y, but not z16:27
cmurphythis would help with that postgres deadlock situation16:27
hrybackicmurphy: I'm not following that16:27
cmurphylet me pull up the bug16:27
hrybackity!16:27
hrybackikmalloc: made the good point that making a migration idempotent adds a level of complexity16:28
ayoungI'm against16:28
kmalloca lot of complexity16:28
cmurphyhttps://bugs.launchpad.net/keystone/+bug/175590616:28
openstackLaunchpad bug 1755906 in OpenStack Identity (keystone) "Occasional deadlock during db_sync --contract during Newton to Pike live upgrade" [Medium,Incomplete]16:28
lbragstadcmurphy: https://bugs.launchpad.net/keystone/+bug/1755906 ?16:28
lbragstadoh - yep, beat me to it :)16:28
ayoungIts too much work, and the migration mechanism is already designed to be Idempotent16:28
kmallocayoung: this is more for *all* migrations (going forward)16:28
*** rossella_s has quit IRC16:28
kmallocand my guidance/recommendation is we dont16:29
ayounginstead, we need a better process for doing backports16:29
kmallocbut i am willing to humor discussing and open to changing my opinion16:29
ayoungI think the problem is something like this:16:29
kmallocayoung: this came up because a vendor backported16:29
kmallocnot upstream backported16:29
ayoungkmalloc, I know.  I'm the vendor16:29
kmallocso am i :P16:29
*** rossella_s has joined #openstack-meeting-alt16:29
kmallocbut...16:29
kmallocthat said16:29
lbragstadhow complicated is doing a backport with alembic?16:29
ayoungwe're the vendor, as is hrybacki16:29
hrybackiand vendors will backport. So we should think about that :)16:30
ayoungso...say a feature goes into R16:30
ayoungand we decide we want it in Q16:30
kmalloci am against feature backports. full stop16:30
ayoungmigration fills a hole in a prealloc16:30
kmalloci'd argue for microversions if it stopped it16:30
gagehugokmalloc heh16:30
ayoungbut...since the feature is not in Q yet, there is no way to make the migration idempotent16:30
kmallocbackporting features is *bad* and should not be encourages16:30
kmallocencouraged*16:30
ayoungso...if the vender needs that kind of idempotency, the flow should be:16:30
ayoung1. submit the backport to stable.  Does not need to be accepted, but should be submitted16:31
ayoungas a req to 1 ever getting merged...16:31
kmalloclbragstad: alembic is easier, since you can just place a migration at any point (iirc) and can verify it was added/applied side-channel if it hasn't16:31
kmallocbut... that is a limited understanding16:31
ayoung2.  Submit a change to the original migration to make it idempotent16:31
*** marios has quit IRC16:31
*** jchhatbar has quit IRC16:32
kmallocayoung: i'd -2 upstream changes like that in general unless we're striving to make all migrations idempotent16:32
ayoungwe can be lenient on the idempotent patches.  They should have 0 impact16:32
ayoungkmalloc, what?  Are you looking to make more work?16:32
kmallocbecause migration changes could change resulting schema16:32
ayoungSo...no16:32
kmallocso. no. not more work16:32
ayoungthe only thing we accept is a commit to an existing migration that confirms the change has already been made, and then skips16:32
kmallocjust avoiding accidental schema changes that end up with divergent schemas across deployments16:33
ayoungsay we add a column in migration 10116:33
kmallocagain, migrations are so touchy as is.16:33
ayoungthe only thing we would then accept is a change to migration 101 that checks for the columnt and, if it exists, no-ops16:33
kmallocchanging them in the past could really really break things for some folks16:33
ayoungvendor submits both patches16:33
kmalloceven if it looks like all it does is "check"16:33
kmallocmy opinion: vendor carries downstream.16:33
ayoungthere is 0 impact on the postive thread16:33
ayoungkmalloc, this is IFF they submit to stable16:34
kmallocin the case of the bug brought up... it could have been 100% solved with a different index name16:34
kmalloci don't trust them to submit to stable and master and follow through16:34
ayoungand that is also why it should be submitted to stable16:34
ayoungto get that kind of code review16:34
kmallocit has to land in multiple places.16:34
kmallocthis feels like a really bad idea to support16:34
hrybackiI'm genuinely curious what the rest of the cores feel regarding vendors carrying downstream backports for migrations vs planning for that to happen in upstream16:34
ayoungso...we may end up NEVER accepting these, but we should document the process.16:35
* kmalloc quiets up and lets other speak16:35
* ayoung too16:35
* hrybacki leans on others' experience and knowledge 16:35
ayoungand everyone looks at cmurphy!16:35
* kmalloc stares intently at lbragstad too.16:36
* hrybacki rubs gagehugo's shoulders encouragingly 16:36
lbragstadumm16:36
cmurphywe mostly don't carry patches for any major features16:36
cmurphywe don't have any for migrations that i'm aware of16:36
gagehugoI don't think we carry backported features across releases16:36
ayoungwe have, in the past, accepted changes to old migrations, when an issue has been identified that required it.16:37
lbragstadi'm unfamiliar with how we're managing that relationship internally16:37
hrybackicurious16:37
kmallocayoung: the issues were not for "we backported this" it has always been "this migration fails in this way specifically"16:37
lbragstadi will say that after looking into the osp issue, i see that the migration process is pretty tricky to get right16:37
kmallocand those were reproducable bugs... some around things like MySQL's DDL was finacky16:38
lbragstadif you don't propose the original patch properly, you're kinda screwed16:38
kmallocmy view is pretty strongly: we don't support backporting migrations outside of legit bugs for upstream fixes.16:38
kmallocif you're backporting a migration --- be aware it will be run again in upgrade.16:39
kmallocand take proper steps to ensure (e.g. use a different index name) you're not causing failures.16:39
ayoungkmalloc, so this would be the process we would need iff we backported a fix to the stable branch16:39
hrybacki^^ that scenario has to arise, right?16:40
ayoungI say we document it, and ensure that it is labeld "IN CASE OF FIRE BREAK GLASS" or sommat16:40
kmallocwe already have a way to backport migrations16:40
kmallocmake a migration in master (idempotent) and in a placeholder, backport placeholder16:40
*** matrohon has quit IRC16:40
ayoungkmalloc, but that will break if the migration in master is not idempotent.  So Add that step in.16:41
kmallocno it wont16:41
hrybackiso when do we decide to backport to stable or not? The bug raising this question goes way back -- at least to Liberty16:41
kmallocwe never ever ever ever backport a landed migration.16:41
kmallocif we're doing a backport it's a BUG fix specific migration16:41
kmallocand that is written to be idempotent to begin with16:41
lbragstadthat's the step we missed with migration 2216:42
kmallocand we then land it in the placeholders (also idempotent) and then we backport just the placeholder16:42
hrybackiright, that iddn't happen this time -- my point16:42
kmallocwe didn't backport it.16:42
ayoungsay we drop an index in master.  then we realize we need it in stable. As part of that fix, we realize that id we then go from stable to master (or later stable) we are going to break.  So, yeah, accepting the "check before drop" as a modification to the master migration is the only thing we can do.16:42
kmallocayoung: lets table that, you are talking about a different scenario that is not applicable here16:42
ayoung++16:43
kmallocayoung: i'm not arguing about having a mechanism to support smart migration backporting (and we have that in place -- we can better document it)16:43
kmalloc:)16:43
hrybackiright so in summary: We only 'backport' migrations when it's related to a bug that affects  versions older than master?16:43
kmallocthe summary is: if we have a bug that requires fixing a migration there are 2 scenarios16:44
kmalloc1) Bug affects everyone and we create a new migration and placeholders for bakcporting16:44
ayounghrybacki, I think that, when in doubt, submit your patch to stable.  And we can make the discussion public.  Might not get accepted, but at  least you will know why.16:44
kmalloc2) the bug is in a specific migration and in some scenarios that migration is failing, but strictly in an upgrade (not a backported thing done out of tree). This is fixed in master and backported directly16:45
kmalloc2 is a very very rare case16:45
kmallocwe have had maybe 1 of those16:45
kmallocor 216:45
lbragstad~14 minutes remaining16:46
kmalloccase #1 is not common, but an example is: "we need to make sure indexes are consistently named"16:46
kmallocwe write a migration to fix it, and placeholder backports to fix it in older releases so we're not randomly breaking due to bad assumptions16:46
*** armaan has joined #openstack-meeting-alt16:46
kmalloceverything in case #1 is idempotent16:46
ayoungAnything else on the Agenda?16:47
*** kumarmn has joined #openstack-meeting-alt16:47
hrybackiack. I think I have a good understanding. (lbragstad please push us forward if there is another item on the agenda)16:47
lbragstadnope - that was our last topic16:47
lbragstadi didn't mean to cut the discussion short16:47
hrybackiack16:48
lbragstadjust keeping an eye on time is all16:48
ayoungOK...topic I want people to think about.  We'll discuss this at the summit but...16:48
lbragstad#topic open discussion16:48
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:48
*** salv-orl_ has quit IRC16:48
lbragstadayoung: the floor is yours16:48
ayoungDeleting a project today leaves all objects in remote services orphaned.  What should we do about this?16:48
ayoungAnd...I think that the implied task in that is "how would a user figure out everything that they have labeled under a project to delete it"16:49
ayoungand also16:49
ayoung"how would I lock a project so I can delete stuff without letting someone else still create stuff"16:49
ayoungI don't think there are easy answers16:49
ayoungand I don't think that we can just punt on it, either, say it is not a Keystone problem16:50
ayoungit is not exclusively a Keystone problem, obviously16:50
ayoungbut we should be working cross-project to come up with a range of solutions16:50
lbragstadi was under the impression that notifications were supposed to help with this16:50
kmallociirc, i chatted with nova and nova had a mechanism that would already allow this16:50
kmallocdirect API calls16:50
kmallocnotifications could help, but that is possibly wonky16:51
kmallocsince notifications could be missed.16:51
ayoungIssue with notifications is that the services currently have no listeners.16:51
ayoungSo, one solution would be to build a "cleanup service" that got the project delete notification and had sufficient capabilities to delete...everything?16:51
*** kumarmn has quit IRC16:52
wxy|ayoung: ++ that's what we do in downstream.16:52
lbragstadso - that would still be contingent upon the notification getting received by something16:52
ayounglbragstad, right,although you could also kick it off manually.16:53
lbragstadi suppose16:53
lbragstadi assume that service would need a user?16:53
*** jessegler has quit IRC16:53
*** trinaths has quit IRC16:54
ayounglbragstad, I think it would be a service level role to perform, or we would have to "fake out" a project token for the deleted project16:54
lbragstadwould deployments looking to achieve decentralized authorization from NISTs RBAC model be hesitant to adopting that kind of solution?16:54
lbragstadsince a lot of authorization would bubble up to that role?16:54
lbragstador service user?16:55
ayoungIt is a lot of power.16:55
lbragstadyeah... but it's necessary if you go across the API boundaries, isn't it?16:55
ayoungI'd rather have it done with a soft-delete of the project, followed by cleanup, followed by a hard delete16:55
*** sambetts is now known as sambetts|afk16:55
kmallocayoung: hm.16:56
lbragstadwouldn't that require the same amount of authorization?16:56
ayounglbragstad, I think "delete only tokens" might make sense once we have finer grained roles.16:56
kmallocayoung: i could probably spin up some Resource-Option fu for projects that would support "soft" delete16:56
kmallocin a couple hours16:56
kmalloc(different semantically from "delete" or "disable")16:57
ayoungit could be the original role assignment that is used to determine who can delete16:57
lbragstadisn't disable == soft delete?16:57
kmalloclbragstad: sortof.16:57
kmallocnot really.16:57
*** tosky has joined #openstack-meeting-alt16:57
lbragstadand we already implement that16:57
*** Leo_m has joined #openstack-meeting-alt16:57
ayoungwe could say that disable is a pre-req, tho16:57
kmallocit is somewhere between disable and soft-delete16:57
ayoungdisable means you can get delete only tokens...16:57
* ayoung waves hands16:58
kmallocbecause we can't change disable to waht ayoung says16:58
kmallocsince it changes api behavior16:58
kmallocalso, disable is sortof meant to be reversible16:58
ayoungIt also leaves the question of "what do I delete where" up in the air16:58
*** felipemonteiro__ has joined #openstack-meeting-alt16:59
ayoungI mean, you could start by walking the service catalog, and say "ok, Nova...whatcha got?  Delete that"16:59
kmallocayoung: i really hope we can simplify it long term to "nova - cleanup resources for project X"16:59
ayoungone thing to avoid is the race condition16:59
kmallocnot "what do you have, delete 1, delete 2, etc"16:59
kmalloc;)16:59
ayoung"I keep trying to delte things, but kmalloc keeps making new  VMs on me"16:59
lbragstadand with that we're out of time,17:00
ayoungkmalloc, so...yeah, that is exactly what I think we should work towards17:00
hrybackiReminder that we are conducting our M1 retrospective. Call-in: https://bluejeans.com/8559013623 Trello Board: https://trello.com/b/PiJecAs4/keystone-rocky-m1-retrospective -- I have to break. Let's plan to join in 10? Please add cards in respective columns as you may17:00
lbragstadwe can continue this in office hours after the retro though17:00
lbragstadthanks for coming17:00
hrybackio/17:00
lbragstad#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Apr 24 17:00:45 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-04-24-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-04-24-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-04-24-16.00.log.html17:00
*** yamamoto has joined #openstack-meeting-alt17:00
*** felipemonteiro__ has quit IRC17:01
*** derekh has quit IRC17:01
*** felipemonteiro__ has joined #openstack-meeting-alt17:01
*** felipemonteiro_ has quit IRC17:02
*** felipemonteiro has joined #openstack-meeting-alt17:03
*** iyamahat has joined #openstack-meeting-alt17:03
*** edmondsw has quit IRC17:04
*** panda|ruck is now known as panda|ruck|off17:04
*** yamamoto has quit IRC17:06
*** felipemonteiro__ has quit IRC17:06
*** rossella_s has quit IRC17:06
*** dizquierdo has joined #openstack-meeting-alt17:08
*** jtomasek has quit IRC17:10
*** rossella_s has joined #openstack-meeting-alt17:11
*** dsariel has quit IRC17:13
*** felipemonteiro_ has joined #openstack-meeting-alt17:17
*** felipemonteiro has quit IRC17:20
*** namnh has quit IRC17:21
*** namnh has joined #openstack-meeting-alt17:25
*** dkehn_ has quit IRC17:27
*** kumarmn has joined #openstack-meeting-alt17:28
*** namnh has quit IRC17:30
*** rmart04 has joined #openstack-meeting-alt17:31
*** namnh has joined #openstack-meeting-alt17:31
*** Leo_m_ has joined #openstack-meeting-alt17:33
*** kumarmn has quit IRC17:33
*** armaan has quit IRC17:33
*** lpetrut_ has joined #openstack-meeting-alt17:34
*** Leo_m has quit IRC17:36
*** Leo_m_ has quit IRC17:37
*** lpetrut has quit IRC17:38
*** kumarmn has joined #openstack-meeting-alt17:39
*** wxy| has quit IRC17:40
*** gagehugo has left #openstack-meeting-alt17:40
*** wxy| has joined #openstack-meeting-alt17:40
*** jaypipes is now known as jaypipes-lunch17:43
*** namnh has quit IRC17:44
*** rmart04 has quit IRC17:45
*** namnh has joined #openstack-meeting-alt17:45
*** rmart04 has joined #openstack-meeting-alt17:46
*** namnh has quit IRC17:55
*** wxy| has quit IRC17:55
*** bhavik1 has quit IRC17:55
*** vgreen has quit IRC17:55
*** edmondsw has joined #openstack-meeting-alt17:56
*** kumarmn has quit IRC17:59
*** namnh has joined #openstack-meeting-alt18:00
*** dizquierdo has quit IRC18:02
*** yamamoto has joined #openstack-meeting-alt18:03
*** edmondsw_ has joined #openstack-meeting-alt18:03
*** edmonds__ has joined #openstack-meeting-alt18:05
*** edmonds__ is now known as edmondsw__18:06
*** edmondsw__ is now known as edmondsw___18:06
*** edmondsw has quit IRC18:06
*** edmondsw___ is now known as edmondsw18:06
*** yamamoto has quit IRC18:08
*** edmondsw_ has quit IRC18:09
*** namnh has quit IRC18:10
*** cloudrancher has joined #openstack-meeting-alt18:16
*** lpetrut_ has quit IRC18:17
*** kumarmn has joined #openstack-meeting-alt18:20
*** jaypipes-lunch is now known as jaypipes18:23
*** kumarmn has quit IRC18:24
*** ianychoi has quit IRC18:26
*** iyamahat has quit IRC18:26
*** ianychoi has joined #openstack-meeting-alt18:26
*** gyee has quit IRC18:28
*** cloudrancher has quit IRC18:31
*** felipemonteiro__ has joined #openstack-meeting-alt18:39
*** felipemonteiro_ has quit IRC18:39
*** rmart04 has quit IRC18:53
*** fnaval has joined #openstack-meeting-alt18:54
*** sridharg has quit IRC18:59
*** kumarmn has joined #openstack-meeting-alt19:01
*** dims has quit IRC19:02
*** yamahata has joined #openstack-meeting-alt19:04
*** yamamoto has joined #openstack-meeting-alt19:04
*** lpetrut_ has joined #openstack-meeting-alt19:04
*** iyamahat has joined #openstack-meeting-alt19:05
*** dims has joined #openstack-meeting-alt19:09
*** yamamoto has quit IRC19:10
*** radeks has quit IRC19:14
*** matrohon has joined #openstack-meeting-alt19:14
*** salv-orlando has joined #openstack-meeting-alt19:16
*** Leo_m has joined #openstack-meeting-alt19:20
*** Leo_m has quit IRC19:20
*** Leo_m has joined #openstack-meeting-alt19:20
*** Leo_m has quit IRC19:25
*** tesseract has quit IRC19:26
*** Leo_m has joined #openstack-meeting-alt19:32
*** ianychoi has quit IRC19:39
*** ianychoi has joined #openstack-meeting-alt19:41
*** matrohon has quit IRC19:58
*** matrohon has joined #openstack-meeting-alt19:59
*** kumarmn has quit IRC20:01
*** kumarmn has joined #openstack-meeting-alt20:02
*** rasca has quit IRC20:04
*** weshay has quit IRC20:05
*** ianychoi has quit IRC20:05
*** yamamoto has joined #openstack-meeting-alt20:06
*** lpetrut_ has quit IRC20:07
*** weshay has joined #openstack-meeting-alt20:07
*** rasca has joined #openstack-meeting-alt20:07
*** spilla has left #openstack-meeting-alt20:07
*** ianychoi has joined #openstack-meeting-alt20:09
*** yamamoto has quit IRC20:11
*** dklyle has quit IRC20:18
*** cloudrancher has joined #openstack-meeting-alt20:19
*** AlanClark has quit IRC20:24
*** kumarmn has quit IRC20:24
*** slaweq has quit IRC20:25
*** slaweq has joined #openstack-meeting-alt20:26
*** iyamahat has quit IRC20:28
*** cloudrancher has quit IRC20:29
*** yamahata has quit IRC20:29
*** kumarmn has joined #openstack-meeting-alt20:29
*** priteau_ has joined #openstack-meeting-alt20:31
*** spzala has quit IRC20:32
*** spzala has joined #openstack-meeting-alt20:32
*** raildo has quit IRC20:34
*** raildo has joined #openstack-meeting-alt20:34
*** jcoufal_ has joined #openstack-meeting-alt20:34
*** priteau has quit IRC20:34
*** kumarmn has quit IRC20:34
*** spzala has quit IRC20:34
*** stevebaker has quit IRC20:37
*** jcoufal has quit IRC20:37
*** gouthamr has quit IRC20:38
*** alexchadin has joined #openstack-meeting-alt20:38
*** alexchadin has quit IRC20:38
*** ianychoi has quit IRC20:39
*** ianychoi has joined #openstack-meeting-alt20:40
*** stevebaker has joined #openstack-meeting-alt20:42
*** gouthamr has joined #openstack-meeting-alt20:43
*** rmascena has joined #openstack-meeting-alt20:44
*** raildo has quit IRC20:46
*** rmascena has quit IRC20:50
*** iyamahat has joined #openstack-meeting-alt20:50
*** iyamahat_ has joined #openstack-meeting-alt20:50
*** iyamahat has quit IRC20:55
*** dklyle has joined #openstack-meeting-alt20:56
*** kumarmn has joined #openstack-meeting-alt20:58
*** cloudrancher has joined #openstack-meeting-alt21:05
*** cloudrancher has quit IRC21:05
*** yamamoto has joined #openstack-meeting-alt21:08
*** yamahata has joined #openstack-meeting-alt21:09
*** edmondsw_ has joined #openstack-meeting-alt21:11
*** edmondsw has quit IRC21:13
*** yamamoto has quit IRC21:14
*** dklyle has quit IRC21:14
*** slaweq has quit IRC21:14
*** slaweq has joined #openstack-meeting-alt21:15
*** slaweq has quit IRC21:20
*** matrohon has quit IRC21:21
*** fnaval has quit IRC21:21
*** ianychoi has quit IRC21:24
*** ianychoi has joined #openstack-meeting-alt21:25
*** jcoufal_ has quit IRC21:27
*** fnaval has joined #openstack-meeting-alt21:32
*** priteau_ has quit IRC21:32
*** ianychoi has quit IRC21:35
*** ianychoi has joined #openstack-meeting-alt21:36
*** namnh has joined #openstack-meeting-alt21:37
*** jbadiapa has joined #openstack-meeting-alt21:38
*** cloudrancher has joined #openstack-meeting-alt21:41
*** dklyle has joined #openstack-meeting-alt21:44
*** cloudrancher has quit IRC21:46
*** edmondsw_ has quit IRC21:55
*** ianychoi has quit IRC22:02
*** ianychoi has joined #openstack-meeting-alt22:04
*** kumarmn has quit IRC22:04
*** edmondsw has joined #openstack-meeting-alt22:05
*** edmondsw has quit IRC22:05
*** namnh has quit IRC22:07
*** yamamoto has joined #openstack-meeting-alt22:09
*** yamamoto has quit IRC22:14
*** dave-mccowan has quit IRC22:15
*** gyee has joined #openstack-meeting-alt22:23
*** dtrainor has quit IRC22:41
*** efried has quit IRC22:42
*** fnaval has quit IRC22:45
*** dizquierdo has joined #openstack-meeting-alt22:52
*** fnaval has joined #openstack-meeting-alt22:53
*** fnaval has quit IRC22:54
*** fnaval has joined #openstack-meeting-alt22:54
*** dustins has quit IRC22:58
*** dizquierdo has quit IRC23:09
*** yamamoto has joined #openstack-meeting-alt23:10
*** cloudrancher has joined #openstack-meeting-alt23:10
*** cloudrancher has quit IRC23:15
*** felipemonteiro__ has quit IRC23:16
*** yamamoto has quit IRC23:16
*** cloudrancher has joined #openstack-meeting-alt23:18
*** cloudrancher has quit IRC23:22
*** cloudrancher has joined #openstack-meeting-alt23:23
*** dizquierdo has joined #openstack-meeting-alt23:25
*** chyka_ has quit IRC23:29
*** cloudrancher has quit IRC23:32
*** hongbin_ has quit IRC23:33
*** cloudrancher has joined #openstack-meeting-alt23:36
*** tpsilva has quit IRC23:36
*** dizquierdo has quit IRC23:39
*** cloudrancher has quit IRC23:55
*** tosky has quit IRC23:58
*** yamamoto has joined #openstack-meeting-alt23:58

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