Tuesday, 2016-04-19

*** mickeys has joined #openstack-meeting00:00
*** asingh has quit IRC00:00
*** kei_ has quit IRC00:01
*** obondarev has joined #openstack-meeting00:01
*** vishwana_ has joined #openstack-meeting00:02
*** kei_ has joined #openstack-meeting00:03
*** vishwana_ has quit IRC00:03
*** vishwanathj has quit IRC00:03
*** vishwanathj has joined #openstack-meeting00:03
*** banix has joined #openstack-meeting00:05
*** banix has quit IRC00:07
*** haomaiwang has joined #openstack-meeting00:11
*** kei_ has quit IRC00:11
*** vishwana_ has joined #openstack-meeting00:12
*** garthb has quit IRC00:14
*** vishwanathj has quit IRC00:15
*** dneary has joined #openstack-meeting00:15
*** Leom has quit IRC00:18
*** spzala has quit IRC00:18
*** Leo_ has joined #openstack-meeting00:19
*** spzala has joined #openstack-meeting00:19
*** obondarev has quit IRC00:20
*** leeantho has quit IRC00:21
*** mickeys has quit IRC00:22
*** toddjohn_ has quit IRC00:23
*** mickeys has joined #openstack-meeting00:23
*** spzala has quit IRC00:24
*** bobh has quit IRC00:27
*** asingh has joined #openstack-meeting00:27
*** mickeys has quit IRC00:27
*** toddjohn_ has joined #openstack-meeting00:27
*** mtanino_ has joined #openstack-meeting00:28
*** mickeys has joined #openstack-meeting00:28
*** mtanino has quit IRC00:29
*** sputnik13 has quit IRC00:31
*** toddjohn_ has quit IRC00:32
*** raildo is now known as raildo-afk00:33
*** Swami has quit IRC00:33
*** dneary has quit IRC00:35
*** Leo_ has quit IRC00:38
*** asingh has quit IRC00:40
*** gyee has quit IRC00:44
*** roxanagh_ has joined #openstack-meeting00:45
*** SridarK has quit IRC00:47
*** Qiming has quit IRC00:47
*** adahms has quit IRC00:48
*** roxanagh_ has quit IRC00:49
*** dmorita has quit IRC00:49
*** Sukhdev has quit IRC00:50
*** dmorita has joined #openstack-meeting00:51
*** bobh has joined #openstack-meeting00:54
*** baoli has joined #openstack-meeting00:57
*** hoangcx has joined #openstack-meeting00:58
*** hoangcx has left #openstack-meeting00:58
*** apoorvad has quit IRC00:58
*** sdague has quit IRC00:59
*** singhj has quit IRC00:59
*** mtanino has joined #openstack-meeting01:03
*** rossella_s has quit IRC01:03
*** rossella_s has joined #openstack-meeting01:04
*** mtanino_ has quit IRC01:04
*** dimtruck is now known as zz_dimtruck01:06
*** lblanchard has quit IRC01:06
*** zhurong has joined #openstack-meeting01:08
*** dmacpher-afk has quit IRC01:10
*** iceyao has joined #openstack-meeting01:11
*** mickeys has quit IRC01:12
*** ayoung has joined #openstack-meeting01:12
*** mickeys has joined #openstack-meeting01:12
*** Leo_ has joined #openstack-meeting01:17
*** mickeys has quit IRC01:17
*** spzala has joined #openstack-meeting01:19
*** Leo_ has quit IRC01:22
*** pvaneck has quit IRC01:24
*** spzala has quit IRC01:25
*** haomaiwang has quit IRC01:26
*** banix has joined #openstack-meeting01:27
*** CaptTofu_ is now known as CaptTofu01:28
*** toddjohn_ has joined #openstack-meeting01:29
*** spzala has joined #openstack-meeting01:33
*** toddjohn_ has quit IRC01:34
*** MarkAtwood has joined #openstack-meeting01:35
*** ebalduf has quit IRC01:38
*** lblanchard has joined #openstack-meeting01:43
*** Qiming has joined #openstack-meeting01:45
*** yanyanhu has joined #openstack-meeting01:45
*** ljxiash_ has joined #openstack-meeting01:48
*** ricolin has joined #openstack-meeting01:49
*** JRobinson__ has quit IRC01:51
*** JRobinson__ has joined #openstack-meeting01:51
*** asettle has quit IRC01:52
*** salv-orlando has joined #openstack-meeting01:56
*** bobh has quit IRC01:58
*** kei has joined #openstack-meeting01:59
*** tfukushima has joined #openstack-meeting02:00
*** edtubill has joined #openstack-meeting02:00
*** salv-orlando has quit IRC02:02
*** eliqiao_ is now known as eliqiao02:02
*** IlyaG has joined #openstack-meeting02:02
*** MaxPC has quit IRC02:06
*** rohit_ has joined #openstack-meeting02:07
*** JRobinson__ has quit IRC02:09
*** keedya has quit IRC02:10
*** rfolco has quit IRC02:12
*** Leo_ has joined #openstack-meeting02:12
*** rfolco has joined #openstack-meeting02:13
*** r-mibu has quit IRC02:14
*** lblanchard has quit IRC02:15
*** Leo_ has quit IRC02:16
*** MarkAtwood has quit IRC02:17
*** rfolco has quit IRC02:17
*** vishwana_ has quit IRC02:19
*** r-mibu has joined #openstack-meeting02:19
*** ninag has quit IRC02:19
*** vishwanathj has joined #openstack-meeting02:21
*** salv-orlando has joined #openstack-meeting02:22
*** iceyao has quit IRC02:24
*** iceyao has joined #openstack-meeting02:24
*** yifei has quit IRC02:25
*** salv-orlando has quit IRC02:26
*** asselin_ has joined #openstack-meeting02:28
*** mtanino has quit IRC02:29
*** asselin__ has quit IRC02:29
*** JRobinson__ has joined #openstack-meeting02:31
*** bobh has joined #openstack-meeting02:31
*** toddjohn_ has joined #openstack-meeting02:31
*** edtubill has quit IRC02:33
*** gongysh has joined #openstack-meeting02:34
*** toddjohn_ has quit IRC02:36
*** edtubill has joined #openstack-meeting02:37
*** sridharg has joined #openstack-meeting02:38
*** iyamahat has quit IRC02:39
*** yamahata has quit IRC02:40
*** MaxPC has joined #openstack-meeting02:40
*** edtubill has quit IRC02:42
*** singhj has joined #openstack-meeting02:42
*** fnaval has quit IRC02:44
*** fnaval has joined #openstack-meeting02:45
*** unicell has quit IRC02:45
*** zz_dimtruck is now known as dimtruck02:50
*** thorst_ has quit IRC02:52
*** ebalduf has joined #openstack-meeting02:53
*** thorst_ has joined #openstack-meeting02:53
*** jckasper has quit IRC02:58
*** jckasper has joined #openstack-meeting02:59
*** zhipeng has joined #openstack-meeting02:59
*** JRobinson__ has quit IRC02:59
*** spzala has quit IRC03:00
*** bobh has quit IRC03:01
*** thorst_ has quit IRC03:01
*** spzala has joined #openstack-meeting03:01
*** sridharg has quit IRC03:02
*** singhj has quit IRC03:02
*** spzala has quit IRC03:05
*** Leo_ has joined #openstack-meeting03:06
*** kei has quit IRC03:06
*** kei has joined #openstack-meeting03:07
*** zhhuabj has quit IRC03:08
*** rogerz has joined #openstack-meeting03:08
*** kei_ has joined #openstack-meeting03:09
*** Leo_ has quit IRC03:10
*** kei has quit IRC03:12
*** ijw has quit IRC03:13
*** mickeys has joined #openstack-meeting03:14
*** unicell has joined #openstack-meeting03:14
*** rogerz has left #openstack-meeting03:15
*** rderose has quit IRC03:16
*** unicell has quit IRC03:19
*** mickeys has quit IRC03:19
*** unicell has joined #openstack-meeting03:19
*** amotoki has quit IRC03:20
*** zhhuabj has joined #openstack-meeting03:20
*** banix has quit IRC03:20
*** mmotiani has quit IRC03:21
*** yamahata has joined #openstack-meeting03:22
*** mmotiani has joined #openstack-meeting03:22
*** epico has joined #openstack-meeting03:22
*** salv-orlando has joined #openstack-meeting03:23
*** tochi has quit IRC03:28
*** neelashah has joined #openstack-meeting03:29
*** salv-orlando has quit IRC03:30
*** armax has quit IRC03:30
*** jdurgin has joined #openstack-meeting03:31
*** baoli has quit IRC03:32
*** ntpttr has quit IRC03:34
*** roxanagh_ has joined #openstack-meeting03:35
*** iceyao_ has joined #openstack-meeting03:36
*** iceyao has quit IRC03:36
*** amandap has quit IRC03:38
*** iceyao has joined #openstack-meeting03:39
*** morgabra has quit IRC03:39
*** hugokuo has quit IRC03:39
*** jdurgin has quit IRC03:39
*** zhipeng has quit IRC03:40
*** persia has quit IRC03:40
*** intr1nsic has quit IRC03:41
*** links has joined #openstack-meeting03:41
*** hugokuo has joined #openstack-meeting03:41
*** amotoki has joined #openstack-meeting03:41
*** morgabra has joined #openstack-meeting03:41
*** iceyao_ has quit IRC03:42
*** saisriki has quit IRC03:42
*** amandap has joined #openstack-meeting03:42
*** ianw has quit IRC03:43
*** iceyao has quit IRC03:44
*** vishwanathj has quit IRC03:45
*** tfukushima has quit IRC03:46
*** liamji has joined #openstack-meeting03:46
*** saisriki has joined #openstack-meeting03:48
*** persia has joined #openstack-meeting03:50
*** irenab_ has joined #openstack-meeting03:51
*** irenab has quit IRC03:54
*** irenab_ is now known as irenab03:54
*** adiantum has joined #openstack-meeting03:55
*** qwebirc40020 has joined #openstack-meeting03:57
*** tochi has joined #openstack-meeting03:57
*** _amrith_ is now known as amrith03:58
*** iyamahat has joined #openstack-meeting03:59
*** thorst_ has joined #openstack-meeting03:59
*** adiantum1 has joined #openstack-meeting04:00
*** neelashah has quit IRC04:01
*** adiantum has quit IRC04:03
*** adiantum1 is now known as adiantum04:03
*** amotoki has quit IRC04:03
*** thorst_ has quit IRC04:06
*** intr1nsic has joined #openstack-meeting04:07
*** gongysh has quit IRC04:08
*** ianw has joined #openstack-meeting04:08
*** sheel has joined #openstack-meeting04:09
*** ayoung has quit IRC04:11
*** tfukushima has joined #openstack-meeting04:12
*** dmorita has quit IRC04:15
*** Kevin_Zheng has quit IRC04:17
*** zhurong has quit IRC04:17
*** rohit_ has quit IRC04:17
*** IlyaG has quit IRC04:18
*** fnaval has quit IRC04:18
*** qwebirc40020 has quit IRC04:20
*** moiz has joined #openstack-meeting04:24
*** intr1nsic has quit IRC04:27
*** haomaiwang has joined #openstack-meeting04:27
*** ianw has quit IRC04:27
*** salv-orlando has joined #openstack-meeting04:27
*** fnaval has joined #openstack-meeting04:29
*** yamamoto has quit IRC04:31
*** toddjohn_ has joined #openstack-meeting04:32
*** amotoki has joined #openstack-meeting04:33
*** ianw has joined #openstack-meeting04:33
*** intr1nsic has joined #openstack-meeting04:33
*** lpetrut has joined #openstack-meeting04:37
*** moiz has quit IRC04:37
*** toddjohn_ has quit IRC04:37
*** amrith is now known as _amrith_04:38
*** asettle has joined #openstack-meeting04:38
*** Poornima has joined #openstack-meeting04:40
*** asingh has joined #openstack-meeting04:40
*** garthb has joined #openstack-meeting04:40
*** asselin_ has quit IRC04:41
*** zqfan has joined #openstack-meeting04:42
*** salv-orlando has quit IRC04:43
*** roxanagh_ has quit IRC04:44
*** ober37_ has joined #openstack-meeting04:45
*** ober37_ has quit IRC04:50
*** Poornima has quit IRC04:52
*** irenab has quit IRC04:52
*** Poornima has joined #openstack-meeting04:52
*** Leo_ has joined #openstack-meeting04:54
*** asettle has quit IRC04:54
*** asettle has joined #openstack-meeting04:55
*** tfukushima has quit IRC04:55
*** tfukushima has joined #openstack-meeting04:56
*** joearnold has quit IRC04:56
*** alpha_ori has quit IRC04:56
*** anderstj has quit IRC04:56
*** ober37_ has joined #openstack-meeting04:56
*** cody-somerville has quit IRC04:57
*** Leo_ has quit IRC04:58
*** ober37_ has quit IRC04:59
*** anderstj has joined #openstack-meeting04:59
*** alpha_ori has joined #openstack-meeting05:00
*** joearnold has joined #openstack-meeting05:00
*** spzala has joined #openstack-meeting05:01
*** cody-somerville has joined #openstack-meeting05:02
*** thorst_ has joined #openstack-meeting05:04
*** spzala has quit IRC05:06
*** rcernin has joined #openstack-meeting05:10
*** zhurong has joined #openstack-meeting05:10
*** moiz has joined #openstack-meeting05:11
*** thorst_ has quit IRC05:12
*** eric_lopez has joined #openstack-meeting05:12
*** elo has quit IRC05:13
*** asettle has quit IRC05:13
*** asettle has joined #openstack-meeting05:13
*** nkrinner has joined #openstack-meeting05:13
*** yamamoto has joined #openstack-meeting05:14
*** tfukushima has quit IRC05:16
*** IlyaG has joined #openstack-meeting05:18
*** IlyaG has quit IRC05:23
*** Sukhdev has joined #openstack-meeting05:30
*** lpetrut has quit IRC05:30
*** lpetrut has joined #openstack-meeting05:30
*** sridharg has joined #openstack-meeting05:31
*** irenab has joined #openstack-meeting05:31
*** toddjohn_ has joined #openstack-meeting05:33
*** garthb has quit IRC05:35
*** asettle has quit IRC05:37
*** toddjohn_ has quit IRC05:38
*** asettle has joined #openstack-meeting05:38
*** salv-orlando has joined #openstack-meeting05:40
*** nadya has joined #openstack-meeting05:41
*** ntpttr has joined #openstack-meeting05:43
*** cody-somerville has quit IRC05:43
*** Poornima has quit IRC05:43
*** Poornima has joined #openstack-meeting05:43
*** lpetrut has quit IRC05:47
*** zhhuabj has quit IRC05:47
*** Leo_ has joined #openstack-meeting05:48
*** moiz has quit IRC05:51
*** asettle has quit IRC05:51
*** salv-orl_ has joined #openstack-meeting05:52
*** Leo_ has quit IRC05:52
*** salv-orl_ has quit IRC05:52
*** salv-orlando has quit IRC05:53
*** tfukushima has joined #openstack-meeting05:53
*** asettle has joined #openstack-meeting05:53
*** salv-orlando has joined #openstack-meeting05:53
*** e0ne has joined #openstack-meeting05:54
*** salv-orlando has quit IRC05:54
*** salv-orlando has joined #openstack-meeting05:55
*** anilvenkata has joined #openstack-meeting05:55
*** cdub has quit IRC05:57
*** spzala has joined #openstack-meeting06:02
*** Poornima has quit IRC06:04
*** zhhuabj has joined #openstack-meeting06:04
*** e0ne has quit IRC06:05
*** lpetrut has joined #openstack-meeting06:05
*** spzala has quit IRC06:07
*** adiantum has quit IRC06:07
*** thorst_ has joined #openstack-meeting06:09
*** e0ne has joined #openstack-meeting06:10
*** lpetrut has quit IRC06:10
*** synegy34 has joined #openstack-meeting06:10
*** gatekeep has quit IRC06:14
*** zhurong has quit IRC06:14
*** dmorita has joined #openstack-meeting06:15
*** zhurong has joined #openstack-meeting06:15
*** asettle has quit IRC06:15
*** asettle has joined #openstack-meeting06:15
*** mickeys has joined #openstack-meeting06:17
*** thorst_ has quit IRC06:17
*** zhurong has quit IRC06:18
*** oomichi has quit IRC06:19
*** dmorita has quit IRC06:19
*** zhurong has joined #openstack-meeting06:20
*** oomichi has joined #openstack-meeting06:20
*** moiz has joined #openstack-meeting06:20
*** Poornima has joined #openstack-meeting06:20
*** Sukhdev has quit IRC06:21
*** rbak has quit IRC06:21
*** mickeys has quit IRC06:22
*** rbak has joined #openstack-meeting06:22
*** dmacpher has joined #openstack-meeting06:23
*** roxanagh_ has joined #openstack-meeting06:24
*** numan_ has joined #openstack-meeting06:24
*** lpetrut has joined #openstack-meeting06:25
*** comay has quit IRC06:25
*** zeih has joined #openstack-meeting06:25
*** yanyanhu has quit IRC06:26
*** zhurong has quit IRC06:27
*** amotoki has quit IRC06:27
*** zhurong has joined #openstack-meeting06:28
*** roxanagh_ has quit IRC06:29
*** Qiming has quit IRC06:29
*** e0ne has quit IRC06:30
*** MaxPC has quit IRC06:30
*** e0ne has joined #openstack-meeting06:32
*** liusheng has quit IRC06:35
*** liusheng has joined #openstack-meeting06:36
*** yuval has joined #openstack-meeting06:38
*** yuval is now known as Guest6063506:38
*** Guest60635 has quit IRC06:38
*** yuval_ has joined #openstack-meeting06:39
*** iyamahat has quit IRC06:39
*** yuval_ is now known as yuval06:40
*** Leo_ has joined #openstack-meeting06:42
*** scheuran has joined #openstack-meeting06:42
*** moiz has quit IRC06:43
*** dmellado_ is now known as dmellado06:44
*** moiz has joined #openstack-meeting06:46
*** Leo_ has quit IRC06:46
*** e0ne has quit IRC06:47
*** sridharg has quit IRC06:47
*** lpetrut has quit IRC06:48
*** fawadkhaliq has joined #openstack-meeting06:49
*** pots1 has joined #openstack-meeting06:51
*** moizarif has joined #openstack-meeting06:51
*** moiz has quit IRC06:53
*** nmagnezi has joined #openstack-meeting06:55
*** Poornima has quit IRC06:57
*** hoangcx has joined #openstack-meeting06:57
*** hoangcx has left #openstack-meeting06:57
yamamotohi07:00
yamamoto#startmeeting networking_midonet07:00
openstackMeeting started Tue Apr 19 07:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto. Information about MeetBot at http://wiki.debian.org/MeetBot.07:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: networking_midonet)"07:00
openstackThe meeting name has been set to 'networking_midonet'07:00
yamamoto#topic agenda07:00
*** openstack changes topic to "agenda (Meeting topic: networking_midonet)"07:00
yamamoto#link https://wiki.openstack.org/wiki/Meetings/NetworkingMidoNet07:00
yamamoto#topic Announcements07:00
*** openstack changes topic to "Announcements (Meeting topic: networking_midonet)"07:00
yamamotoi moved networking-midonet-coverage from post to check07:01
yamamototo increate visibility of the results07:01
yamamotoaustin summit is next week07:01
yamamotolet's cancel next week's meeting07:02
yamamoto#topic Bugs07:02
*** openstack changes topic to "Bugs (Meeting topic: networking_midonet)"07:02
*** bvandenh has joined #openstack-meeting07:02
*** hichihara has quit IRC07:02
yamamoto#link https://bugs.launchpad.net/networking-midonet/07:02
yamamotoall of our tempest jobs are currently failing07:03
yamamotowith timeout07:03
yamamoto#link https://bugs.launchpad.net/networking-midonet/+bug/157148607:03
openstackLaunchpad bug 1571486 in networking-midonet "tempest jobs timout" [Critical,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)07:03
*** spzala has joined #openstack-meeting07:03
yamamotoi'm looking at it but no success so far.07:03
yamamotoi'll continue bug deputy07:04
yamamoto#topic Open Discussion07:05
*** openstack changes topic to "Open Discussion (Meeting topic: networking_midonet)"07:05
yamamotonothing from me07:05
* yamamoto waiting for a while before closing the meeting07:05
*** amotoki has joined #openstack-meeting07:06
*** spzala has quit IRC07:08
*** Kevin_Zheng has joined #openstack-meeting07:09
*** Poornima has joined #openstack-meeting07:10
*** dimtruck is now known as zz_dimtruck07:10
*** fawadkhaliq has quit IRC07:12
*** nadya_ has joined #openstack-meeting07:12
yamamotosee you in austin, bye07:14
yamamoto#endmeeting07:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:14
openstackMeeting ended Tue Apr 19 07:14:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-04-19-07.00.html07:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-04-19-07.00.txt07:14
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-04-19-07.00.log.html07:14
*** nadya has quit IRC07:14
*** thorst_ has joined #openstack-meeting07:15
*** egallen has joined #openstack-meeting07:16
*** pcaruana has joined #openstack-meeting07:16
*** asingh has quit IRC07:17
*** zeih has quit IRC07:17
*** zeih has joined #openstack-meeting07:18
*** matrohon has joined #openstack-meeting07:18
*** amotoki_ has joined #openstack-meeting07:20
*** egallen has quit IRC07:20
*** eliqiao_ has joined #openstack-meeting07:20
*** ebalduf has quit IRC07:20
*** ricolin has quit IRC07:21
*** thorst_ has quit IRC07:22
*** egallen has joined #openstack-meeting07:22
*** amotoki has quit IRC07:22
*** pcaruana has quit IRC07:23
*** eliqiao has quit IRC07:24
*** dmacpher has quit IRC07:24
*** tesseract has joined #openstack-meeting07:24
*** tesseract is now known as Guest2294507:24
*** zeih has quit IRC07:24
*** Rockyg has quit IRC07:24
*** andymaier has joined #openstack-meeting07:25
*** zeih has joined #openstack-meeting07:25
*** roxanagh_ has joined #openstack-meeting07:26
*** Kevin_Zheng has quit IRC07:26
*** hparekh2 has joined #openstack-meeting07:26
*** Kevin_Zheng has joined #openstack-meeting07:27
*** zz_dimtruck is now known as dimtruck07:29
*** jlanoux has joined #openstack-meeting07:29
*** mpaolino has joined #openstack-meeting07:30
*** roxanagh_ has quit IRC07:31
*** toddjohn_ has joined #openstack-meeting07:34
*** gongysh has joined #openstack-meeting07:35
*** lpetrut has joined #openstack-meeting07:36
*** zeih has quit IRC07:39
*** dimtruck is now known as zz_dimtruck07:39
*** toddjohn_ has quit IRC07:39
*** pnavarro has joined #openstack-meeting07:41
ttxanteaya: it's a piece from a local artist - http://www.ateliersergemeurisse.net/#!images/c1han07:47
*** adiantum has joined #openstack-meeting07:48
*** hoangcx has joined #openstack-meeting07:50
*** hoangcx has left #openstack-meeting07:51
*** Kevin_Zheng has quit IRC07:53
*** Kevin_Zheng has joined #openstack-meeting07:57
*** mbound has joined #openstack-meeting07:58
*** kashyap has joined #openstack-meeting07:58
*** hparekh2 has quit IRC07:59
*** clarkb has quit IRC08:00
*** Qiming has joined #openstack-meeting08:00
*** nadya_ has quit IRC08:00
*** neeti has joined #openstack-meeting08:00
*** epico has quit IRC08:01
anteayattx: thank you08:01
anteaya#startmeeting third-party08:02
openstackMeeting started Tue Apr 19 08:02:03 2016 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: third-party)"08:02
openstackThe meeting name has been set to 'third_party'08:02
anteayahello08:02
*** synegi has joined #openstack-meeting08:02
anteayalennyb: are you about?08:03
lennybyeap08:03
lennybhi08:03
anteaya#info this meeting is skipped next week due to summit, it will resume the following week08:03
anteayalennyb: hi08:03
*** eliqiao_ is now known as eliqiao08:04
*** spzala has joined #openstack-meeting08:04
lennybanteaya: I have nothing to discuss and I know that it's late for you, so I wont keep you here08:04
anteayalennyb: can you point mellanox ci to openstack-dev/ci-sandbox instead of openstack-dev/sandbox, please? https://review.openstack.org/#/c/290505/208:04
anteayalennyb: thanks :)08:05
anteayathe sandbox repo is for developers08:05
*** epico has joined #openstack-meeting08:05
lennybsorry.08:05
anteayathe ci-sandbox is for ci systems08:05
anteayano worries08:05
lennybsandbox will be changed.08:05
anteayathanks I appreciate it08:05
anteayathe sandbox repo will be used during summit to help new devs and pleia2 was just preparing for next week08:06
*** synegy34 has quit IRC08:06
anteayaand thats all I had08:06
*** clarkb has joined #openstack-meeting08:06
*** amotoki_ has quit IRC08:06
*** cwolferh has quit IRC08:07
lennybenjoy the summit.... I am sure it will be interesting08:07
anteayathanks I am looking forward to seeing you in Barcelona08:08
anteaya:)08:08
lennybI will try08:09
anteayait would be great if you could be there08:09
*** spzala has quit IRC08:09
anteayabut only if it works out for you08:09
*** adrianofr has quit IRC08:10
*** adrianofr has joined #openstack-meeting08:10
lennyb:)08:10
anteayaany objection to me closing the meeting today?08:10
*** toscalix has joined #openstack-meeting08:10
lennybnop08:11
anteayathanks08:11
anteayathanks for being here08:11
anteayasee you week after next08:11
anteayaenjoy your day!08:11
anteaya#endmeeting08:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:11
openstackMeeting ended Tue Apr 19 08:11:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-08.02.html08:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-08.02.txt08:11
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-08.02.log.html08:11
*** e0ne has joined #openstack-meeting08:13
*** aleksandr_null has quit IRC08:14
*** iyamahat has joined #openstack-meeting08:14
*** ihrachys has joined #openstack-meeting08:14
*** thorst_ has joined #openstack-meeting08:20
*** mhickey has joined #openstack-meeting08:22
*** iyamahat has quit IRC08:23
*** gongysh has quit IRC08:24
*** mickeys has joined #openstack-meeting08:24
*** adiantum has quit IRC08:26
*** ihrachys has quit IRC08:26
*** ygbo has joined #openstack-meeting08:27
*** thorst_ has quit IRC08:27
*** Leo_ has joined #openstack-meeting08:30
*** zz_dimtruck is now known as dimtruck08:30
*** mickeys has quit IRC08:30
*** mickeys has joined #openstack-meeting08:31
*** salv-orlando has quit IRC08:34
*** Leo_ has quit IRC08:35
*** zhhuabj has quit IRC08:35
*** mickeys has quit IRC08:35
*** dmacpher has joined #openstack-meeting08:37
*** neiljerram has joined #openstack-meeting08:39
*** zeih has joined #openstack-meeting08:39
*** yassou has joined #openstack-meeting08:39
*** yassou has quit IRC08:40
*** dimtruck is now known as zz_dimtruck08:40
*** yassine has joined #openstack-meeting08:41
*** asettle has quit IRC08:41
*** asettle has joined #openstack-meeting08:41
*** yassine is now known as Guest2420008:41
*** aleksandr_null has joined #openstack-meeting08:42
*** neiljerram has quit IRC08:45
*** Adri2000 has quit IRC08:47
*** Adri2000 has joined #openstack-meeting08:47
*** zhhuabj has joined #openstack-meeting08:47
*** haukebruno has joined #openstack-meeting08:51
*** asettle has quit IRC08:51
*** sridharg has joined #openstack-meeting08:52
*** sshnaidm has quit IRC08:52
*** asettle has joined #openstack-meeting08:52
*** sridharg has quit IRC08:53
*** sridharg has joined #openstack-meeting08:53
*** sheel has quit IRC08:55
*** electrofelix has joined #openstack-meeting08:56
*** Poornima has quit IRC08:58
*** salv-orlando has joined #openstack-meeting08:59
*** salv-orlando has quit IRC09:00
*** salv-orlando has joined #openstack-meeting09:01
*** Poornima has joined #openstack-meeting09:03
*** Qiming has quit IRC09:04
*** ociuhandu has joined #openstack-meeting09:05
*** spzala has joined #openstack-meeting09:05
*** joeljwright has joined #openstack-meeting09:09
*** joeljwright has left #openstack-meeting09:09
*** spzala has quit IRC09:10
*** roxanagh_ has joined #openstack-meeting09:13
*** sambetts|afk is now known as sambetts09:17
*** amotoki has joined #openstack-meeting09:17
*** roxanagh_ has quit IRC09:18
*** adrianofr has quit IRC09:22
*** hogepodge has joined #openstack-meeting09:23
*** phil__ has joined #openstack-meeting09:24
*** thorst_ has joined #openstack-meeting09:25
*** zz_dimtruck is now known as dimtruck09:31
*** vgridnev has joined #openstack-meeting09:31
*** thorst_ has quit IRC09:31
*** toddjohn_ has joined #openstack-meeting09:36
*** toddjohn_ has quit IRC09:40
*** dimtruck is now known as zz_dimtruck09:41
*** klkumar has joined #openstack-meeting09:42
*** amotoki has quit IRC09:43
*** nadya has joined #openstack-meeting09:44
*** akamyshnikova_ has joined #openstack-meeting09:46
*** zhurong has quit IRC09:46
*** zhhuabj has quit IRC09:47
*** zhurong has joined #openstack-meeting09:47
*** zhurong has quit IRC09:49
*** JRobinson__ has joined #openstack-meeting09:50
*** JRobinson__ has quit IRC09:50
*** dixiaoli has quit IRC09:52
*** klkumar has quit IRC09:53
*** IlyaG has joined #openstack-meeting09:55
*** asettle has quit IRC09:56
*** asettle has joined #openstack-meeting09:57
*** epico has quit IRC09:59
*** IlyaG has quit IRC09:59
*** amotoki has joined #openstack-meeting10:00
*** Guest24200 has quit IRC10:02
*** sshnaidm has joined #openstack-meeting10:04
*** zhhuabj has joined #openstack-meeting10:05
*** nadya has quit IRC10:06
*** spzala has joined #openstack-meeting10:07
*** liamji has quit IRC10:08
*** sdague has joined #openstack-meeting10:08
*** claudiub has joined #openstack-meeting10:10
*** spzala has quit IRC10:11
*** ndipanov has quit IRC10:14
*** amotoki has quit IRC10:14
*** tfukushima has quit IRC10:15
*** dmorita has joined #openstack-meeting10:16
*** ndipanov has joined #openstack-meeting10:18
*** Leo_ has joined #openstack-meeting10:18
*** yamahata has quit IRC10:20
*** dmorita has quit IRC10:20
*** Leo_ has quit IRC10:23
*** nadya has joined #openstack-meeting10:24
*** electrofelix has quit IRC10:24
*** Qiming has joined #openstack-meeting10:25
*** gcb has joined #openstack-meeting10:28
*** pnavarro is now known as pnavarro|mtg10:28
*** thorst_ has joined #openstack-meeting10:29
*** jlanoux_ has joined #openstack-meeting10:30
*** jlanoux has quit IRC10:31
*** zz_dimtruck is now known as dimtruck10:32
*** ljxiash_ has quit IRC10:32
*** electrofelix has joined #openstack-meeting10:34
*** asselin_ has joined #openstack-meeting10:37
*** Qiming has quit IRC10:37
*** thorst_ has quit IRC10:37
*** markvoelker has joined #openstack-meeting10:37
*** jlanoux_ has quit IRC10:38
*** jlanoux has joined #openstack-meeting10:39
*** dimtruck is now known as zz_dimtruck10:41
*** markvoelker has quit IRC10:42
*** asselin_ has quit IRC10:43
*** akamyshnikova has quit IRC10:50
*** egallen has quit IRC10:54
*** akamyshnikova_ has quit IRC10:58
*** JRobinson__ has joined #openstack-meeting10:59
*** rfolco has joined #openstack-meeting11:00
*** rfolco has quit IRC11:00
*** fzdarsky has joined #openstack-meeting11:01
*** ihrachys has joined #openstack-meeting11:01
*** roxanagh_ has joined #openstack-meeting11:01
*** akamyshnikova has joined #openstack-meeting11:05
*** roxanagh_ has quit IRC11:06
*** JRobinson__ has quit IRC11:06
*** spzala has joined #openstack-meeting11:08
*** rtheis has joined #openstack-meeting11:10
*** gongysh has joined #openstack-meeting11:11
*** JRobinson__ has joined #openstack-meeting11:11
*** julim has joined #openstack-meeting11:12
*** spzala has quit IRC11:13
*** eliqiao_ has joined #openstack-meeting11:15
*** spxnezzar has joined #openstack-meeting11:17
*** eliqiao has quit IRC11:19
*** JRobinson__ has quit IRC11:22
*** fzdarsky has quit IRC11:23
*** mickeys has joined #openstack-meeting11:24
*** gongysh has quit IRC11:28
*** egallen has joined #openstack-meeting11:28
*** weshay has quit IRC11:28
*** fzdarsky has joined #openstack-meeting11:29
*** yamamoto has quit IRC11:30
*** mickeys has quit IRC11:30
*** doug-fish has joined #openstack-meeting11:30
*** zz_dimtruck is now known as dimtruck11:32
*** zqfan has quit IRC11:32
*** salv-orlando has quit IRC11:34
*** thorst_ has joined #openstack-meeting11:37
*** toddjohn_ has joined #openstack-meeting11:37
*** mtanino has joined #openstack-meeting11:38
*** markvoelker has joined #openstack-meeting11:38
*** pnavarro|mtg is now known as pnavarro11:38
*** tochi has quit IRC11:39
*** neiljerram has joined #openstack-meeting11:40
*** adahms has joined #openstack-meeting11:41
*** toddjohn_ has quit IRC11:42
*** dimtruck is now known as zz_dimtruck11:42
*** markvoelker has quit IRC11:42
*** salv-orlando has joined #openstack-meeting11:47
*** egallen_ has joined #openstack-meeting11:50
*** egallen has quit IRC11:51
*** egallen_ is now known as egallen11:51
*** mageshgv has joined #openstack-meeting11:52
*** Guest22945 is now known as tesseract11:54
*** tesseract is now known as Guest7339711:54
*** rodrigods has quit IRC11:54
*** rodrigods has joined #openstack-meeting11:55
*** dprince has joined #openstack-meeting11:55
*** bvandenh_ has joined #openstack-meeting11:55
*** bvandenh has quit IRC11:57
*** raildo-afk is now known as raildo11:58
*** haomaiwang has quit IRC12:00
*** hparekh2 has joined #openstack-meeting12:02
*** MaxPC has joined #openstack-meeting12:02
*** fzdarsky has quit IRC12:03
*** weshay has joined #openstack-meeting12:03
*** Leo_ has joined #openstack-meeting12:06
*** _amrith_ is now known as amrith12:07
*** yamamoto has joined #openstack-meeting12:09
*** spzala has joined #openstack-meeting12:09
*** fzdarsky has joined #openstack-meeting12:09
*** bobh has joined #openstack-meeting12:10
*** Leo_ has quit IRC12:11
*** Qiming has joined #openstack-meeting12:11
*** bobh has quit IRC12:12
*** zhurong has joined #openstack-meeting12:12
*** spzala has quit IRC12:13
*** Qiming_ has joined #openstack-meeting12:14
*** sridharg has quit IRC12:15
*** iceyao has joined #openstack-meeting12:15
*** Qiming has quit IRC12:16
*** baoli has joined #openstack-meeting12:16
*** aysyd has joined #openstack-meeting12:17
*** adiantum has joined #openstack-meeting12:17
*** mtreinish has quit IRC12:18
*** baoli_ has joined #openstack-meeting12:18
*** markvoelker has joined #openstack-meeting12:19
*** spzala has joined #openstack-meeting12:19
*** moizarif has quit IRC12:19
*** mtreinish has joined #openstack-meeting12:21
*** baoli has quit IRC12:21
*** sridharg has joined #openstack-meeting12:21
*** yamamoto has quit IRC12:24
*** pradk_ has joined #openstack-meeting12:24
*** toddjohn_ has joined #openstack-meeting12:26
*** bvandenh_ has quit IRC12:30
*** bvandenh has joined #openstack-meeting12:31
*** lezbar has quit IRC12:31
*** yassine has joined #openstack-meeting12:31
*** yassine is now known as Guest4476112:32
*** lezbar has joined #openstack-meeting12:32
*** zz_dimtruck is now known as dimtruck12:33
*** hparekh2 has quit IRC12:33
*** fwdit has joined #openstack-meeting12:33
*** yamamoto has joined #openstack-meeting12:34
*** yamamoto has quit IRC12:39
*** zeih has quit IRC12:42
*** fwdit has quit IRC12:42
*** bvandenh has quit IRC12:43
*** dimtruck is now known as zz_dimtruck12:43
*** bvandenh has joined #openstack-meeting12:43
*** jdurgin has joined #openstack-meeting12:43
*** yamamoto has joined #openstack-meeting12:44
*** ljxiash has joined #openstack-meeting12:44
*** yamamoto has quit IRC12:45
*** egarbade- has quit IRC12:46
*** zeih has joined #openstack-meeting12:48
*** ljxiash has quit IRC12:49
*** zz_dimtruck is now known as dimtruck12:50
*** haomaiwang has joined #openstack-meeting12:52
*** zeih has quit IRC12:54
*** mjturek1 has quit IRC12:54
*** yamamoto has joined #openstack-meeting12:54
*** haomaiwa_ has joined #openstack-meeting12:55
*** HeOS has quit IRC12:55
*** pfallenop has quit IRC12:55
*** haomaiwa_ has quit IRC12:55
*** haomaiwa_ has joined #openstack-meeting12:56
*** haomaiwang has quit IRC12:59
*** zzxwill__ has joined #openstack-meeting13:00
*** pfallenop has joined #openstack-meeting13:01
*** dimtruck is now known as zz_dimtruck13:01
*** synegi is now known as gatekeep13:03
*** yamamoto has quit IRC13:03
*** adiantum has quit IRC13:03
*** rossella_s has quit IRC13:03
*** aysyd has quit IRC13:04
*** eharney has joined #openstack-meeting13:04
*** rossella_s has joined #openstack-meeting13:04
*** keedya has joined #openstack-meeting13:05
*** irenab has quit IRC13:05
*** yamamoto has joined #openstack-meeting13:05
*** lezbar has quit IRC13:05
*** lezbar has joined #openstack-meeting13:06
*** pfallenop has quit IRC13:07
*** pfallenop has joined #openstack-meeting13:09
*** aysyd has joined #openstack-meeting13:12
*** yamamoto has quit IRC13:14
*** zz_dimtruck is now known as dimtruck13:16
*** bobh has joined #openstack-meeting13:16
*** yamamoto has joined #openstack-meeting13:16
*** unicell has quit IRC13:16
*** unicell has joined #openstack-meeting13:17
*** myoung has quit IRC13:17
*** reedip_ has joined #openstack-meeting13:17
*** pabelanger has left #openstack-meeting13:19
*** moiz has joined #openstack-meeting13:19
*** zhurong has quit IRC13:19
*** yamahata has joined #openstack-meeting13:20
*** zhurong has joined #openstack-meeting13:21
*** jdob has quit IRC13:21
*** jdob has joined #openstack-meeting13:21
*** lblanchard has joined #openstack-meeting13:23
*** myoung has joined #openstack-meeting13:23
*** dneary has joined #openstack-meeting13:23
*** efried has joined #openstack-meeting13:24
*** allen_gao has quit IRC13:25
*** neelashah has joined #openstack-meeting13:25
*** akamyshnikova has quit IRC13:25
*** jprovazn has joined #openstack-meeting13:25
*** mriedem_away is now known as mriedem13:25
*** toddjohn_ has quit IRC13:26
*** pfallenop has quit IRC13:26
*** moiz has quit IRC13:26
*** pfallenop has joined #openstack-meeting13:26
*** pfallenop has quit IRC13:26
*** pfallenop has joined #openstack-meeting13:26
*** xyang1 has joined #openstack-meeting13:30
*** jdob has quit IRC13:30
*** jdob has joined #openstack-meeting13:31
*** mriedem has quit IRC13:33
*** allen_gao has joined #openstack-meeting13:34
*** piet has joined #openstack-meeting13:34
*** mriedem has joined #openstack-meeting13:35
*** adiantum has joined #openstack-meeting13:35
*** mriedem has quit IRC13:36
*** mriedem has joined #openstack-meeting13:36
*** openstackstatus has joined #openstack-meeting13:37
*** ChanServ sets mode: +v openstackstatus13:37
*** yamahata has quit IRC13:37
*** gongysh has joined #openstack-meeting13:37
*** dasm has left #openstack-meeting13:38
*** vhoward has joined #openstack-meeting13:39
-openstackstatus- NOTICE: We have recovered one of our cloud providers, but there is a huge backlog of jobs to process. Please have patience until your jobs are processed13:40
*** tonytan4ever has joined #openstack-meeting13:41
*** yamamoto has quit IRC13:41
*** banix has joined #openstack-meeting13:41
*** ljxiash has joined #openstack-meeting13:42
*** yamamoto has joined #openstack-meeting13:43
*** asettle has quit IRC13:45
*** jckasper has quit IRC13:46
*** jckasper has joined #openstack-meeting13:46
*** fnaval has quit IRC13:48
*** egallen has left #openstack-meeting13:49
*** dell has joined #openstack-meeting13:49
*** adiantum has quit IRC13:49
*** dell is now known as zengchen13:49
*** ayoung has joined #openstack-meeting13:50
*** Poornima has quit IRC13:52
*** Poornima has joined #openstack-meeting13:52
*** amitgandhinz has joined #openstack-meeting13:52
*** piet has quit IRC13:53
*** Leo_ has joined #openstack-meeting13:55
*** chenying_ has joined #openstack-meeting13:55
*** yinweimac has joined #openstack-meeting13:57
*** Poornima has quit IRC13:57
*** saggi has joined #openstack-meeting13:57
*** rfolco has joined #openstack-meeting13:57
*** ober37_ has joined #openstack-meeting13:57
*** ober37_ has quit IRC13:58
*** Hunter has joined #openstack-meeting13:58
*** Hunter is now known as Guest4564513:58
*** xiangxinyong456 has joined #openstack-meeting13:58
Guest45645hi bosses13:59
*** ober37_ has joined #openstack-meeting13:59
Guest45645good evening13:59
Guest45645greetings from a newbie13:59
*** Leo_ has quit IRC13:59
*** zhonghua-lee has joined #openstack-meeting13:59
*** asingh has joined #openstack-meeting14:00
*** mtanino has quit IRC14:00
saggi#startmeeting smaug14:00
openstackMeeting started Tue Apr 19 14:00:25 2016 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: smaug)"14:00
openstackThe meeting name has been set to 'smaug'14:00
saggiHi everyone14:00
xiangxinyong456hi14:00
yinweimachi14:00
Guest45645hi14:00
yuvalhey14:00
chenying_hi14:01
zhonghua-leehi14:01
saggigampel is away on holiday. He's collection energy for the summit14:01
saggi*collecting14:01
*** sigmavirus24_awa is now known as sigmavirus2414:01
yinweimaccool14:01
xiangxinyong456:)14:01
*** baoli_ has quit IRC14:01
Guest45645how much has he collected for now?:)14:02
saggiIs everyone here?14:02
zengchenyes14:03
saggigood14:03
saggi#topic OpenStack Summit14:03
*** openstack changes topic to "OpenStack Summit (Meeting topic: smaug)"14:03
saggiSummit is next week14:03
*** links has quit IRC14:03
*** dneary has quit IRC14:03
saggiI'm working on a presentation for the vbrownbag. We get 15 minutes.14:04
saggiI'll send everyone a copy of it later today so you can comment.14:04
xiangxinyong456good14:04
zengchenhave a good trip! great!14:04
yinweimacsure14:04
chenying_Ok14:04
saggiIt's supposed to just introduce Smaug and point out our main advantages14:04
*** dneary has joined #openstack-meeting14:04
saggiMainly our pluggable design. And the whole project attitude.14:05
saggiThese are the things that set us apart14:05
xiangxinyong456saggi: eran told us you need a video14:05
saggiWe would also like to have some sort of a demo video. xiangxinyong456, did gampel speak with you about it?14:05
yinweimacyes, I used to be asked what's the difference with project freeze14:05
*** fnaval has joined #openstack-meeting14:05
xiangxinyong456yeah14:06
*** toddjohn_ has joined #openstack-meeting14:06
saggiyinweimac: I'm also trying to get a hold of the freezer guys to see how we can work together instead of compete.14:06
saggixiangxinyong456: How is that going?14:06
*** piet has joined #openstack-meeting14:06
xiangxinyong456firstly i will send the video to mailinglist14:06
xiangxinyong456i plan to record the video tomorrow14:07
xiangxinyong456but i have no idea about the operation logs14:08
*** psilvad has joined #openstack-meeting14:08
saggixiangxinyong456: What do you mean?14:08
xiangxinyong456because the operation logs have something undecided14:09
saggixiangxinyong456: Well talk about it offline. In either case we might just skip showing it in the video. It's just a short demonstration anyway.14:10
xiangxinyong456ok.14:10
chenying_Now the operation log do not cover the scene portecting immediately without scheduler.14:10
zhonghua-leeis there another topic about that?14:10
saggizhonghua-lee: About what?14:11
*** merooney has joined #openstack-meeting14:11
xiangxinyong456operation logs14:11
xiangxinyong456i add it into wiki14:11
zhonghua-leesaggi: operation logs14:11
saggino but I'll add one14:12
saggi:)14:12
yuvalchenying_: and do you think they should?14:12
saggiAny other comments about summit?14:12
*** xiangxinyong has joined #openstack-meeting14:12
xiangxinyongsaggi, i will send a video to you tommorrow night14:13
saggixiangxinyong, great!14:13
xiangxinyongby email?14:13
*** jmckind has joined #openstack-meeting14:13
saggiyes14:13
saggiif it fits14:13
xiangxinyongok14:13
xiangxinyongor i can upload it to a website14:14
zhonghua-leeI wish I could attend the summit.:(14:14
chenying_yuval: IMO, we should see the progress and status of all operation type from the operation log API .14:14
saggixiangxinyong, I wouldn't like WIP versions of the video public. So if you upload it anywhere make it private.14:14
xiangxinyongchenying_: i agree with you.14:14
saggi#topic operation logs14:15
yuvalchenying_: I totally agree. Problem is, there might not be an operation engine running, only a protection service14:15
*** openstack changes topic to "operation logs (Meeting topic: smaug)"14:15
xiangxinyongsaggi: ok14:15
chenying_checkpoint14:15
saggiThe problem with having operation logs without an operation is that the information will have to go in the bank if it's checkpoint related.14:16
chenying_all protect action will call create_checkpoint14:16
chenying_ create_checkpoint rest API14:16
saggiThis is problematic as it breaks the CRUD nature of REST14:16
saggiAs it is now, information about checkpoint progress is inside the checkpoint.14:17
saggiWe can add more information to the checkpoint, like logs.14:17
saggiBut this will have different endpoints.14:17
chenying_so we can get the progress and status of all operation from  checkpoint  information?14:18
saggiThe point is we can't mix those up.14:18
*** cloudtrainme has joined #openstack-meeting14:18
*** efried has quit IRC14:18
saggiWe want to support the user case of a user never scheduling operations14:18
*** asettle has joined #openstack-meeting14:18
*** edtubill has joined #openstack-meeting14:18
saggihaving it's own management logic somewhere and only using the simple operations.14:18
xiangxinyongsaggi: but we can not distinguish the direct protect and schedule protect from the checkpoints14:19
saggiThis means that the information needs to be part of the entity being created.14:19
*** aimon has joined #openstack-meeting14:19
saggiIt Shouldn't matter how the checkpoint was created for the restore side14:19
saggiThe main issue is whether having logs for the checkpoint is really necessary.14:20
saggiWe currently provide information about current progress.14:20
xiangxinyongsaggi: we should see the checkpoint info from the checkpoint page14:20
saggiSo there are no logs.14:20
*** piet has quit IRC14:21
saggiMeaning there is no infiltration about *when* things changed. Just what the status is now.14:21
saggiI want to know if knowing when things changed really makes sense in the context of a checkpoint.14:21
saggiHow does cinder\nova do per instance logs14:21
saggido they even?14:21
xiangxinyongsagg: do you mean we only need the restore to show in the operation logs page?14:22
*** efried has joined #openstack-meeting14:22
chenying_From xinyong's opinion, He want a or several API that can show the progress and status of a operation(protect delete restore) in smaug ui.14:22
saggiWe have progress status from the checkpoint already14:22
*** ober37_ has quit IRC14:23
chenying_How does cinder\nova do per instance logs   They will not got to a new page, just show the status of the resoure like volume.14:23
saggiWhen you ask for information about a checkpoint you should get progress information (if it makes sense).14:23
chenying_resource14:23
*** asettle has quit IRC14:23
*** salv-orlando has quit IRC14:23
*** asselin_ has joined #openstack-meeting14:24
xiangxinyonghow could we show the delete workflow when we delete a checkpoint?14:24
saggiWhat do you want to show?14:24
yinweimacwe just show the checkpoint is deleting14:25
*** Leo_ has joined #openstack-meeting14:25
*** ebalduf has joined #openstack-meeting14:26
*** numan_ has quit IRC14:26
xiangxinyongso we could change the name "operation logs" to "Restores"?14:26
xiangxinyong?14:26
xiangxinyong?14:26
chenying_Un cinder the the progress and status of volume is recorded in the resoure(volume) db table, will not create a new api or db table to record the  data log.14:26
chenying_In cinder14:26
*** Leom has joined #openstack-meeting14:26
saggiOperation logs are for the operations. Operation could contain multiple atomic operations.14:27
saggi*atomic actions14:27
saggiSo operation logs "link" to object14:27
*** mickeys has joined #openstack-meeting14:28
xiangxinyongsaggi: i got some confused.14:28
saggiI'll try and do a writeup about how operations relate to other entities and than we'll try and think about how to integrate everything together once we all understand the requirements.14:28
saggiOK?14:28
*** merooney has quit IRC14:29
chenying_sure14:29
xiangxinyongok14:29
*** piet has joined #openstack-meeting14:29
saggi#topic operation workflow14:30
*** openstack changes topic to "operation workflow (Meeting topic: smaug)"14:30
*** galstrom_zzz is now known as galstrom14:30
saggi#topic operation workflow14:30
*** openstack changes topic to "operation workflow (Meeting topic: smaug)"14:30
*** Leo_ has quit IRC14:30
saggiOK14:30
*** mickeys has quit IRC14:30
yuvalAs you might have seen, I sent a mail to the openstack-dev (tagged smaug) with a suggestion for the restore/protect resource workflow14:30
*** mickeys has joined #openstack-meeting14:30
yuvalIt basically answer the need for protection plugins to perform work both independently of child resources and other work which depends on child resources14:31
*** asingh has quit IRC14:32
*** zzxwill__ has quit IRC14:32
saggiDid everyone read it?14:33
chenying_I have seen. I will take some time to read it.14:33
saggiyinweimac?14:33
yinweimacyes14:33
*** zzxwill__ has joined #openstack-meeting14:33
yinweimacactually I have a talk with yuval already14:34
yinweimacI agree to divide sync/paralle tasks14:34
*** bvandenh has quit IRC14:34
yinweimacbut at the same time, I have a bit concern that it looks complicating to protection plugin developers14:35
saggiYuval and I were talking about it this morning and identified that the main issue is that TaskFlow doesn't have any support for async tasks.14:35
yinweimacand I also gave one fs consistency case to yuval, to see how to meet this case in his design14:35
*** spxnezzar has quit IRC14:36
*** jungleboyj has joined #openstack-meeting14:36
yinweimacnot actually14:36
yuvalyinweimac: what is that fs consistency case?14:36
*** sheel has joined #openstack-meeting14:36
yinweimacserver freeze io before volumes to take snapshot14:36
*** zhurong has quit IRC14:37
yuvalyinweimac: let me think about it, although that might be an issue with the current workflow patches as well, right?14:37
yinweimacyes14:37
yinweimacI think we may need take time to think more about the task flow14:38
yuvalok, so let's take it offline after the meeting14:38
yinweimacthere's a trade off between the complexity and the clear semantics14:38
yuvalI suggest that everyone should read the mail and the attached pdf, so we will have more eyes and opinions14:38
saggi#topic open issues14:39
yuval*eyes reading it14:39
*** openstack changes topic to "open issues (Meeting topic: smaug)"14:39
yinweimacbut I'm busy with the integration demo14:39
yinweimacright now14:39
*** mtanino has joined #openstack-meeting14:39
yinweimacone suggestion is, how about have smaug all services integrated and make them work first?14:39
yinweimacthen we start an enhance iteration?14:40
saggiyinweimac: enhance iteration?14:40
saggioh14:40
saggisure14:40
saggiyinweimac: Yes, I understand that the demo is high priority14:41
yuvalOpen issue: I think that we should share on some tasks site (waffle? trello?) the open tasks that people are working on. I finished working on an issue, only to find out that someone already submitted a patch for the same issue.14:41
*** singhj has joined #openstack-meeting14:41
saggiWe could use trello, dragonflow uses it and they recommend it14:41
zengcheni have one patch need to be merged, otherwise the OperationEngine can not run. can everyone take you time to review it. it stays for a long time. thanks. https://review.openstack.org/#/c/28226314:41
yinweimachmm, eran used to have epad to assign tasks14:41
*** asingh has joined #openstack-meeting14:41
saggiYes,but we found it hard to maintain.14:42
yinweimacreport bug or bp is an explicit way14:42
*** MarkAtwood has joined #openstack-meeting14:42
chenying_I agree with yinwei.14:42
saggiI don't mind using bugs.14:42
saggiBut that means that everyone needs to open bugs for the tasks they are working on (if no bug exists)14:43
chenying_Can record the task using bug or bp.14:43
saggiAnd tag them as enhancement if they are not actual bugs.14:43
*** amotoki has joined #openstack-meeting14:43
yinweimacenhancement could be bp?14:43
*** eric_lopez has quit IRC14:43
*** pnavarro has quit IRC14:44
yinweimacbtw, will the bugs on launch pad be closed automatically if the patch associated with it has been merged?14:44
saggibp is it's own kind of headache.14:44
saggiyinweimac: They should14:44
yuvalyinweimac: I think so14:44
yuvalthe launchpad bugs/bp system is ok, but I actually think a proper task site is much more convinient14:44
yinweimacok, let's have a try with trello14:45
yuvalbut I don't mind either, as long as we really use it14:45
yinweimacboth will do for me14:45
saggiDo you guys have access to trello from china?14:46
*** enriquetaso has joined #openstack-meeting14:46
xiangxinyongit is ok14:46
xiangxinyongwe used it in the last year14:46
*** eric_lopez has joined #openstack-meeting14:47
saggiOK14:47
saggiAny other topics?14:47
*** e0ne has quit IRC14:47
yuvalUmm14:48
yuvalThere are some old patches which require some reviews14:48
yuvaland some other which are on -1 validation and require work14:49
*** fnaval has quit IRC14:49
chenying_I have one . When will we start to design and develop the backup and replication  plug-in?14:49
*** fnaval has joined #openstack-meeting14:50
saggiWe are working on backup now14:50
yinweimacbackup plugin have been developed already14:50
chenying_sorry It is snapshot14:50
saggireplication will have to wait after we have regular backup working end-to-end14:50
saggisnapshots as well14:50
saggiI'd very much like to get the simple things done first14:50
chenying_Ok14:51
saggi#action (sagg) Prepare document describing logging issue14:51
saggijust so I don't forget14:51
yuvalI will open the Trello board and send the link in #openstack-smaug14:51
xiangxinyongThanks saggi.14:51
saggi#action (yuval) open trello board14:52
saggiAny other action items I might have forgot?14:52
*** hashar has joined #openstack-meeting14:52
saggiOk, than I think we're done14:53
saggiThanks everybody14:53
yinweimacthans14:53
yinweimacthanks14:53
xiangxinyongThanks14:53
yinweimacbye14:53
chenying_thanks  all14:53
yuvalthanks, bye14:53
xiangxinyongBye14:53
saggi#endmeeting14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:54
openstackMeeting ended Tue Apr 19 14:54:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-04-19-14.00.html14:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-04-19-14.00.txt14:54
openstackLog:            http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-04-19-14.00.log.html14:54
*** yinweimac has quit IRC14:54
*** jlanoux has quit IRC14:54
*** nkrinner has quit IRC14:54
Guest45645#openstack-smaug14:55
*** asingh has quit IRC14:57
*** timcline has joined #openstack-meeting14:58
*** emagana has joined #openstack-meeting14:58
*** armax has joined #openstack-meeting14:58
*** dell_ has joined #openstack-meeting15:01
*** amotoki has quit IRC15:02
*** dell_ is now known as zengchenn15:02
*** asingh has joined #openstack-meeting15:02
*** rderose has joined #openstack-meeting15:02
*** singhj has quit IRC15:03
*** zengchen has quit IRC15:04
*** irenab has joined #openstack-meeting15:05
*** nmagnezi has quit IRC15:05
*** garthb has joined #openstack-meeting15:06
*** cloudtrainme has quit IRC15:06
*** irenab has quit IRC15:07
*** baoli has joined #openstack-meeting15:07
*** irenab has joined #openstack-meeting15:07
*** cloudtrainme has joined #openstack-meeting15:08
*** korzen has joined #openstack-meeting15:08
*** numan_ has joined #openstack-meeting15:08
*** spotz_zzz is now known as spotz15:08
*** chenying_ has quit IRC15:09
*** yuval has quit IRC15:09
*** xiangxinyong456 has quit IRC15:09
*** absubram has joined #openstack-meeting15:10
*** zengchenn has quit IRC15:12
*** xiangxinyong456 has joined #openstack-meeting15:13
*** francois has quit IRC15:14
*** dmorita has joined #openstack-meeting15:15
*** francois1 has joined #openstack-meeting15:15
*** mickeys has quit IRC15:16
*** mickeys has joined #openstack-meeting15:16
*** MarkAtwood has quit IRC15:16
*** ozone has joined #openstack-meeting15:17
*** MarkAtwood has joined #openstack-meeting15:17
*** mageshgv has quit IRC15:18
*** singhj has joined #openstack-meeting15:19
*** dmorita has quit IRC15:20
*** mickeys has quit IRC15:20
*** mickeys has joined #openstack-meeting15:20
*** ayoung has quit IRC15:20
*** xiangxinyong456 has quit IRC15:20
*** korzen has quit IRC15:21
*** tonytan4ever has quit IRC15:22
*** tonytan4ever has joined #openstack-meeting15:23
*** jlanoux has joined #openstack-meeting15:23
*** singhj has quit IRC15:23
*** yuval has joined #openstack-meeting15:25
*** fzdarsky has quit IRC15:26
*** xiaohhui has quit IRC15:26
*** xiaohhui has joined #openstack-meeting15:26
*** armax has quit IRC15:27
*** neeti has quit IRC15:27
*** yuval has quit IRC15:28
*** mageshgv has joined #openstack-meeting15:30
*** iyamahat has joined #openstack-meeting15:33
mriedemoh, btw, no stable meeting next week15:35
mriedemforgot to announce that15:35
*** mickeys has quit IRC15:35
*** weshay has quit IRC15:36
mriedemoops, wrong channel15:36
*** mickeys has joined #openstack-meeting15:36
*** Qiming_ has quit IRC15:38
*** vgridnev has quit IRC15:38
*** iyamahat has quit IRC15:39
*** Guest45645 has quit IRC15:39
*** dprince has quit IRC15:40
*** mickeys has quit IRC15:41
*** apoorvad has joined #openstack-meeting15:42
*** dneary has quit IRC15:42
*** dane_leblanc has joined #openstack-meeting15:43
*** cwolferh has joined #openstack-meeting15:43
*** links has joined #openstack-meeting15:45
*** eil397 has joined #openstack-meeting15:45
*** Guest44761 has quit IRC15:48
*** gongysh has quit IRC15:48
*** gongysh has joined #openstack-meeting15:50
*** comay has joined #openstack-meeting15:52
*** gyee has joined #openstack-meeting15:54
*** timcline has quit IRC15:56
*** jmckind has quit IRC15:56
*** links has quit IRC15:57
*** lblanchard has quit IRC15:57
*** Rockyg has joined #openstack-meeting15:57
*** cdub has joined #openstack-meeting15:58
*** lblanchard has joined #openstack-meeting15:58
*** gokrokve has joined #openstack-meeting15:58
*** mickeys has joined #openstack-meeting15:58
*** doug-fish has quit IRC16:00
*** Guest73397 has quit IRC16:00
*** doug-fish has joined #openstack-meeting16:00
*** iyamahat has joined #openstack-meeting16:01
*** egarbade- has joined #openstack-meeting16:02
*** iceyao has quit IRC16:02
*** nadya has quit IRC16:02
*** sshnaidm has quit IRC16:03
*** phil__ has quit IRC16:04
*** efried has quit IRC16:04
*** andymaier has quit IRC16:04
*** scheuran has quit IRC16:04
*** adahms has quit IRC16:05
*** toddjohn_ has quit IRC16:06
*** matrohon has quit IRC16:06
*** efried has joined #openstack-meeting16:06
*** dneary has joined #openstack-meeting16:07
*** leeantho has joined #openstack-meeting16:07
*** Sukhdev has joined #openstack-meeting16:07
*** jmckind has joined #openstack-meeting16:07
*** asettle has joined #openstack-meeting16:07
*** doug-fish has quit IRC16:09
*** busterswt has joined #openstack-meeting16:10
*** ozone has quit IRC16:11
*** ayoung has joined #openstack-meeting16:11
*** yamahata has joined #openstack-meeting16:11
*** asettle has quit IRC16:12
*** sdake has joined #openstack-meeting16:14
*** numan_ has quit IRC16:16
*** samueldmq has quit IRC16:17
*** neelashah has quit IRC16:17
*** mageshgv has quit IRC16:19
*** yamamoto has quit IRC16:19
*** zaro has quit IRC16:20
*** anteaya has quit IRC16:20
*** ozone has joined #openstack-meeting16:20
*** rderose has quit IRC16:24
*** ygbo has quit IRC16:24
*** mickeys has quit IRC16:25
*** rderose has joined #openstack-meeting16:25
*** mickeys has joined #openstack-meeting16:25
*** sdake_ has joined #openstack-meeting16:25
*** doug-fish has joined #openstack-meeting16:27
*** yamahata has quit IRC16:27
*** yamahata has joined #openstack-meeting16:28
*** unicell has quit IRC16:28
*** piet has quit IRC16:29
*** sdake has quit IRC16:29
*** mickeys has quit IRC16:30
*** neelashah has joined #openstack-meeting16:30
*** neelashah has quit IRC16:30
*** piet has joined #openstack-meeting16:31
*** toscalix has quit IRC16:31
*** neelashah has joined #openstack-meeting16:31
*** gyee has quit IRC16:34
*** mageshgv has joined #openstack-meeting16:35
*** IlyaG has joined #openstack-meeting16:35
*** IlyaG has quit IRC16:35
*** IlyaG has joined #openstack-meeting16:35
*** andymaier has joined #openstack-meeting16:36
*** egallen has joined #openstack-meeting16:37
*** IlyaG has quit IRC16:37
*** mhickey has quit IRC16:37
*** dmorita has joined #openstack-meeting16:37
*** gongysh has quit IRC16:38
*** jlanoux has quit IRC16:40
*** lcastell has quit IRC16:44
*** luzC has quit IRC16:44
*** egallen has quit IRC16:44
*** fawadkhaliq has joined #openstack-meeting16:45
*** sshnaidm has joined #openstack-meeting16:46
*** mageshgv has quit IRC16:46
*** salv-orlando has joined #openstack-meeting16:48
*** sputnik13 has joined #openstack-meeting16:48
*** anilvenkata has quit IRC16:48
*** ozone has quit IRC16:51
*** salv-orlando has quit IRC16:51
*** fzdarsky has joined #openstack-meeting16:52
*** klkumar has joined #openstack-meeting16:53
*** timcline has joined #openstack-meeting16:54
*** egallen has joined #openstack-meeting16:56
*** hashar has quit IRC16:57
*** aranjan has joined #openstack-meeting16:58
*** pots1 has quit IRC16:59
*** mageshgv has joined #openstack-meeting16:59
*** aranjan has quit IRC16:59
*** lcastell has joined #openstack-meeting17:00
*** brucet has joined #openstack-meeting17:00
*** aranjan has joined #openstack-meeting17:00
mmedvede#startmeeting third-party17:00
*** luzC has joined #openstack-meeting17:00
openstackMeeting started Tue Apr 19 17:00:40 2016 UTC and is due to finish in 60 minutes.  The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: third-party)"17:00
openstackThe meeting name has been set to 'third_party'17:00
asselinhi17:01
mmedvedehey asselin17:01
mmedvedeI have no announcements17:02
asselinme neither17:02
*** dprince has joined #openstack-meeting17:02
mmedvede#topic CI Watch17:03
*** openstack changes topic to "CI Watch (Meeting topic: third-party)"17:03
mmedvedethat is me17:03
*** haomaiwa_ has quit IRC17:03
mmedvedeI did put a couple of days into it last week17:03
*** rossella_s has quit IRC17:03
*** haomaiwang has joined #openstack-meeting17:03
*** rcernin has quit IRC17:04
mmedvedethe testcase I want to add still requires more refactoring before it can happen17:04
*** rossella_s has joined #openstack-meeting17:04
mmedvedethe test is to consume simulated or fake gerrit events and check if they are parsed correctly17:05
mmedvedeI hope to push something up this week17:06
*** ja3 has joined #openstack-meeting17:06
mmedvedeasselin: I forgot, are you coming to Austin?17:07
asselinmmedvede, I know I promised reviews. I can do some today b/c despite never ending urgent issues, houston flooding is taking us down, so I have some time finally.17:07
ja3howdy, sorry I'm late, Notes alarm didn't go off (grr)17:07
mmedvedehi ja317:07
asselinmmedvede, no, I won't be there unfortunately17:08
asselinonly 1 person from our team is going17:08
*** mriedem has quit IRC17:08
mmedvedeasselin: if you could review, would help. I know we got greenlight to self-approve, but I'd rather not abuse it too much17:08
*** garthb has quit IRC17:09
asselin+117:10
mmedvedeok, moving on17:10
mmedvede#topic Common-CI Solution17:10
*** annegentle has joined #openstack-meeting17:10
*** openstack changes topic to "Common-CI Solution (Meeting topic: third-party)"17:10
mmedvedeasselin: any updates here?17:10
*** fzdarsky has quit IRC17:11
*** mbound has quit IRC17:11
asselinmmedvede, no updates. Hearing folks are successful with it, which is good news.17:11
*** vgridnev has joined #openstack-meeting17:11
mmedvedeI've heard that too17:11
mmedvede#topic Open Discussion17:12
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:12
mmedvedeanything to discuss?17:13
*** s3wong has joined #openstack-meeting17:13
mmedvedeasselin: have the flooding took down your servers?17:13
asselinfyi: https://review.openstack.org/#/c/305499/17:13
asselinmmedvede, yeah....at least they turned off power17:14
asselinmmedvede, not sure if the labs are flooded or not.17:14
*** garthb has joined #openstack-meeting17:14
*** mriedem has joined #openstack-meeting17:14
*** Sukhdev has quit IRC17:15
asselinmmedvede, you guys ok?17:15
mmedvedewe had our CI down because of internal network problems17:16
mmedvedebut I think it has nothing to do with floods17:16
mmedvedeAustin had some rain17:16
*** egallen has quit IRC17:16
*** eil397 has left #openstack-meeting17:17
mmedvedeasselin: I find it very hard to restart the CI after a site-wide outage17:17
mmedvedeasselin: especially that nodepool requires zuul to be up if you want to delete any nodes17:17
clarkbmmedvede: I don't think that is true17:17
asselinmmedvede, really? i never noticed that17:17
clarkbmmedvede: we test that use case on every nodepool patch and it works fine17:18
mmedvedeclarkb: maybe I have old nodepool?17:18
clarkbmaybe?17:18
mmedvedenot maybe, we do not use latest17:18
clarkbwell it has worked for a while17:18
clarkbanyways nodepool works fine without zuul or jenkins, if you just point it at a cloud it will do its thing17:19
*** garthb_ has joined #openstack-meeting17:19
*** yamamoto has joined #openstack-meeting17:20
*** sambetts is now known as sambetts|afk17:20
mmedvedeclarkb: ok, that is user error then. thanks for popping in here :)17:20
*** annegentle has quit IRC17:20
*** garthb has quit IRC17:21
asselinmmedvede, I've nothing else. Going to do some reviews and other actions I've been holding off for too long.17:21
* mmedvede creates a task to update nodepool again17:21
*** moiz has joined #openstack-meeting17:21
mmedvedeasselin: thanks for joining17:21
*** aranjan_ has joined #openstack-meeting17:21
mmedvedeI have a cloud to restore too :)17:21
mmedvedeanything else to discuss?17:22
*** zzxwill__ has quit IRC17:22
mmedvedeja3: you just listening?17:22
mmedvede:)17:22
ja3yes17:22
ja3as usual, doing 3 things in parallel17:22
mmedvedeI hear you17:23
*** annegentle has joined #openstack-meeting17:23
mmedvedelets wrap it up then17:23
mmedvedethanks for attending17:23
*** aranjan has quit IRC17:23
ja3catch you in... 4 weeks I guess17:23
ja3or are we meeting during the summit?17:23
ja3not that I'll be there in person...17:24
*** salv-orlando has joined #openstack-meeting17:24
mmedvedeja3: I'll be at summit17:24
mmedvedeja3: there next meeting in 2 weeks, I think summit is over by then17:24
ja3ah right there you go.  off by 1 bug.17:25
*** annegentle has quit IRC17:25
mmedvede#endmeeting17:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:26
openstackMeeting ended Tue Apr 19 17:26:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-17.00.html17:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-17.00.txt17:26
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-04-19-17.00.log.html17:26
*** ja3 has quit IRC17:26
*** annegentle has joined #openstack-meeting17:28
*** yamamoto has quit IRC17:28
*** dimtruck is now known as zz_dimtruck17:29
*** aimon has quit IRC17:29
*** jmckind has quit IRC17:31
*** mrmartin has joined #openstack-meeting17:31
*** unicell has joined #openstack-meeting17:31
*** weshay has joined #openstack-meeting17:32
*** egallen has joined #openstack-meeting17:32
*** neelashah has quit IRC17:33
*** neelashah has joined #openstack-meeting17:35
*** gokrokve has quit IRC17:37
*** gokrokve has joined #openstack-meeting17:37
*** dneary has quit IRC17:38
*** annegentle has quit IRC17:38
*** jmckind has joined #openstack-meeting17:38
*** gyee has joined #openstack-meeting17:39
*** dneary has joined #openstack-meeting17:40
*** anteaya has joined #openstack-meeting17:42
*** electrofelix has quit IRC17:44
*** lhcheng has joined #openstack-meeting17:45
*** haukebruno has quit IRC17:46
*** haomaiwang has quit IRC17:48
*** haomaiwang has joined #openstack-meeting17:48
*** ndipanov has quit IRC17:52
*** zz_dimtruck is now known as dimtruck17:54
*** iyamahat_ has joined #openstack-meeting17:55
*** nadya has joined #openstack-meeting17:55
*** iyamahat has quit IRC17:57
*** samueldmq has joined #openstack-meeting17:57
*** mickeys has joined #openstack-meeting17:58
*** dmorita has quit IRC17:59
*** shaleh has joined #openstack-meeting17:59
*** dmorita has joined #openstack-meeting17:59
ayoungKEYSTONERS...drag your carcasses in here18:00
*** Sukhdev has joined #openstack-meeting18:00
shaleh\o18:00
htrutao/18:00
*** henrynash has joined #openstack-meeting18:00
bretono/18:00
ayoungstevemar, we gonna do this?18:00
henrynashhi18:00
*** doug-fis_ has joined #openstack-meeting18:00
roxanagheo/18:00
stevemarayoung: sure :)18:00
bkeroo/18:00
lhchengo/18:00
stevemar#startmeeting keystone18:00
stevemarping ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, jorge_munoz, knikolla, lbragstad, lhcheng, marekd, MaxPC, morganfainberg, nkinder, raildo, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tjcocozz, tsymanczyk, topol, vivekd, wanghong, xek18:00
rodrigodshi18:00
openstackMeeting started Tue Apr 19 18:00:39 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
* stevemar pokes the bot18:00
openstackThe meeting name has been set to 'keystone'18:00
topolo/18:00
gyee\o18:00
amakarovhi18:00
stevemarthere it is18:00
stevemaro/18:00
bknudsonhi18:01
ayoungOyez oyez18:01
*** piet has quit IRC18:01
stevemarhey everyone!18:01
*** lpetrut has quit IRC18:01
crinkleo/18:01
rderoseo/18:01
raildoo/18:01
samueldmqheey18:01
*** BobH_ has joined #openstack-meeting18:01
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Main_Agenda18:01
samueldmqo/18:01
stevemaragenda isn't too heavy today18:01
morgan\o/18:01
*** doug-fi__ has joined #openstack-meeting18:01
* morgan waves at everyone... and goes back under a rock.18:01
henrynash\\\\o////18:01
rodrigodswe have a keystone functional tests job!18:01
morganhenrynash: HEY no upstaging me ;)18:01
henrynash(henry playing the spider))18:01
*** garthb__ has joined #openstack-meeting18:02
*** iyamahat_ has quit IRC18:02
htrutalol18:02
*** iyamahat has joined #openstack-meeting18:02
dstanekearly start it seems :-)18:02
*** ober37_ has joined #openstack-meeting18:02
*** garthb_ has quit IRC18:02
*** knikolla has joined #openstack-meeting18:02
gyeemy atomic clocks says 11:0218:02
stevemarrodrigods: nice!18:02
*** neelashah1 has joined #openstack-meeting18:02
stevemarhenrynash: i like your ascii style18:02
henrynash(my body clock says time for dinner)18:02
*** ober37_ has quit IRC18:02
morgananyone who doesn't know... Rule 1 of the Summit for Keystone: don't give ayoung a microphone ;)18:02
*** egallen has quit IRC18:02
morganayoung: ^_^18:03
raildohaha18:03
bknudsonmy phone sayx 11:0518:03
MaxPCmorgan:  unless you want to go over schedule18:03
htrutamorgan: but he takes it anyway18:03
* ayoung don't need no stinken electronic amplification18:03
morganmy computer says 11:0318:03
*** ober37_ has joined #openstack-meeting18:03
knikollahi18:03
dstanekayoung: right...we need duct tape18:03
*** mtreinish has quit IRC18:03
ayoungdstanek, Duck tape.18:03
*** brucet has quit IRC18:03
ayoungIt really is Duck...waterproofing18:03
morgandstanek: gaffer tape18:03
*** doug-fish has quit IRC18:04
bknudson100 mph tape18:04
henrynash(ayoung is indeed, the gaffer)18:04
morganlol18:04
dstanekayoung: i never say duck unless i mean that brand, but yes agree18:04
ayoungbknudson, ++18:04
morganooooooookay. so.18:04
stevemar#topic summit prep18:04
*** openstack changes topic to "summit prep (Meeting topic: keystone)"18:04
*** ober37_ has quit IRC18:04
stevemarso, not sure if you all know, there's a summit next week18:04
stevemarin austin, no big deal18:04
dolphmwat18:04
*** doug-fis_ has quit IRC18:04
henrynasheverest?18:04
gyeestevemar, I added Federation Enhancements in the new  features etherpad18:04
dolphmi should get my plane tickets sorted18:04
stevemardolphm: you haven't already!?18:05
samueldmqI like the "drinks on topol" subtopic18:05
dolphmstevemar: definitely not18:05
stevemarsamueldmq: :)18:05
morganstevemar: he's probably driving18:05
morganstevemar: hence the no plane tickets.18:05
topolsamueldmq. everybody does18:05
stevemarmorgan: ...18:05
lbragstado/18:05
*** neelashah has quit IRC18:05
samueldmqtopol: o/18:05
stevemarmorgan: do i really need sarcasm tags, with you!18:05
amakarovsamueldmq, iirc it was "hp pays" :)18:05
dstanekdolphm: spending 2 hours in the airport to avoid the 1.5 hour drive seems reasonable!18:05
dolphmmorgan: lbragstad and i are being chauffeured18:05
topoldstanek LOL18:05
morganstevemar: best part is... #trollsuccess18:05
morgan;)18:05
stevemarmorgan: dammit!18:05
gyeedriving with a boat?18:06
morgangyee: not cause then they'd be "on a boat"...18:06
stevemarSchedule for Design sessions: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Keystone%3A18:06
samueldmqamakarov: : x18:06
stevemar#link https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Keystone%3A18:06
stevemarwe have 5 fishbowls18:07
gyeeI heard we may need a boat to get around18:07
stevemarmeaning the ones with lots of chairs and a projector18:07
*** dmorita has quit IRC18:07
*** ijw has joined #openstack-meeting18:07
stevemarI made the generic (thanks for the suggestion ayoung), so topics are stability, integration, testing, clients, new features18:07
*** jaugustine has joined #openstack-meeting18:08
ayoungwhere does moving to Fernet fit in there>18:08
ayoung?18:08
stevemaryou can find etherpads on the actual schedule link, or here: https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Keystone18:08
ayoungstability?18:08
stevemarayoung: yep: https://etherpad.openstack.org/p/newton-keystone-stabilization18:08
ayoungcool18:08
*** jmckind_ has joined #openstack-meeting18:08
*** mtreinish has joined #openstack-meeting18:08
*** timcline has quit IRC18:08
stevemari know some of you have separate etherpads going, if its not too hard, try to copy the content onto the one central (or at least link it)18:09
raildoayoung: https://www.openstack.org/summit/austin-2016/summit-schedule/events/914518:09
stevemarrderose for instance ^18:09
*** timcline has joined #openstack-meeting18:09
*** gagehugo has joined #openstack-meeting18:09
bknudsonwhat's the topic for the work sessions?18:09
morganbknudson: work work </warcraft>18:09
stevemarbknudson: basically, yeah18:09
*** klkumar has quit IRC18:09
morganbknudson: or zug zug18:09
stevemarlast time i tried to have topics for the work sessions that didn't seem to go over well, agree?18:10
bretonyep18:10
rderosestevemar: okay18:10
henrynashstevemar: ++18:10
bretoneveryone worked on different things18:10
stevemari'd rather just give us time to work on some of the things we discuss in the fishbowl18:10
shalehthe discussions at the summit tend to push the work sessions in certain directions18:11
shalehhard to know ahead of time what those are18:11
*** jmckind has quit IRC18:11
stevemaragreed18:11
stevemarwhich is why i left them blank18:11
dolphmstevemar: what's the difference between work sessions and contributors meetup? in one of those, we had parallel work streams going on in small groups for sure18:11
*** mickeys has quit IRC18:11
rderosewhere does rolling upgrades fit?  stabilization?18:11
dolphmrderose: work session?18:11
stevemarrderose: i'd say so18:11
amakarovstevemar, it would be good to focus on owning features by the most number of participants possible18:11
henrynashrederose: I think that is database upgrades under stabalization?18:12
stevemaramakarov: agreed!18:12
*** mickeys has joined #openstack-meeting18:12
stevemaramakarov: owner + dedicated reviewer18:12
stevemarreviewer(s)18:12
rderosehenrynash: cool, thx18:12
stevemardolphm: the work sessions are the ones with parallel work streams in small groups/pairs18:13
amakarovstevemar, it's always simpleir to review things you understand what are they about :)18:13
bknudsonthe code should be written so that everybody understands it18:13
bretonbknudson: ++18:13
rodrigodsamakarov, ++18:13
bknudsonotherwise we couldn't maintain it anyways18:13
stevemarany other summit-y type of questions?18:13
*** mickeys has quit IRC18:14
stevemari'm excited to see everyone again :D18:14
*** mickeys has joined #openstack-meeting18:14
stevemaralso, it's on the agenda, so it's official "drinks on topol"18:14
amakarovstevemar, can we add some final part to worksessions were people brief others what they've done?18:14
raildotopol: yay \o/18:14
rodrigodstopol, again?! heh18:14
stevemaramakarov: hmm, is there something you had in mind?18:14
* topol time to figure out some loop holes18:14
dstanektopol: likes it, really he does18:14
gyeehow do we find topol?18:15
ayounggyee, that is never a problem18:15
rodrigodsgyee, topol finds you18:15
stevemaramakarov: like - "what did i accomplish in this work session?"18:15
gyeehah18:15
amakarovstevemar, yep - do something like a stan-up at the end of every worksession18:15
topolgyee, easy Im gonna head to blacks BBQ sunday night18:15
lbragstadI like that plan18:15
gyee++18:15
stevemaramakarov: we could try that if you'd like18:15
stevemaramakarov: just remind me18:15
*** ijw has quit IRC18:15
rodrigodsworth trying18:15
stevemaramakarov: you think it'll help keep us on track?18:16
amakarovstevemar, I'd be honored, but what others think about it? ;)18:16
amakarovstevemar, hope so18:16
samueldmqtopol: I tried Rudy's BBQ last time, was great18:16
dolphmamakarov: +++18:16
stevemaramakarov: should only take 5 minutes :P18:16
*** cdub has quit IRC18:16
*** asselin_ has quit IRC18:16
amakarovstevemar, for seasoned scrummers - yes ))18:17
topolsamueldmq... Rudys is mediocre at best.   Way better in Austin. Ask the locals18:17
dolphmalso, work sessions should share a single etherpad - so we don't have notes and stuff scattered everywhere18:17
stevemaramakarov: let's do it then18:17
stevemardolphm: good call18:17
amakarovstevemar, 5 minutes per work item otherwise18:17
*** ihrachys has quit IRC18:17
rderosedolphm: ++18:17
topoldolphm Great idea18:17
*** ijw has joined #openstack-meeting18:17
stevemardolphm: i'll create some etherpads18:17
bknudsonHopefully we'll have stronger chairs.18:17
stevemaramakarov: i'll cut people off after 30 seconds :)18:17
henrynash(my connection will drop for 10 mins…back in soon)18:17
*** henrynash has quit IRC18:17
lbragstadbknudson bah - I forgot about that18:17
ayoungAlmost tempted to work up something like a gant chart to track all the things we have in flight.18:18
stevemarayoung: it's a lot!18:18
*** dmacpher is now known as dmacpher-afk18:18
dolphmstevemar: i literally mean 1 etherpad for all topics in all work sessions :) with a section for each topic covered there. a lot of work session items will span multiple timeslots, so there's no point in having an etherpad per timeslot18:18
* topol wondering if amakarov has new cool Russian tshirts18:18
ayoungstevemar, its the dependencies that are starting to get hard to track.18:18
stevemardolphm: thanks for the clarification :)18:18
stevemardolphm: https://etherpad.openstack.org/p/newton-keystone-work-session18:19
*** edtubill has quit IRC18:19
* amakarov adds an action item: "Find cool Russian t-shirt"18:19
*** nadya has quit IRC18:19
*** dmorita has joined #openstack-meeting18:19
stevemarhehe18:19
ayoungamakarov, in Austin, Cool Russian T-Shirt finds YOU!18:19
*** krtaylor has quit IRC18:20
stevemaralright, thats it for summit, any other questions ask me in -keystone18:20
amakarovayoung, I remember - Austin is weird18:20
stevemar#topic Functional testing setup18:20
*** openstack changes topic to "Functional testing setup (Meeting topic: keystone)"18:20
stevemarbreton: ^18:20
bretonthere was a similar spec some time ago that was moved to superseded18:20
bretonso i decided to suggest another one18:20
*** mickeys has quit IRC18:20
bretontldr: a devstack plugin in a separate repository that would set up things.18:20
bretonhttps://review.openstack.org/30737118:20
bretonfirst i proposed to implement a plugin for federation only. I've received some feedback to make it more general and set up all functional testing related things. I have done it.18:21
rodrigodsbreton, one doubt: you mean move keystone/keystone_tempest_plugin to there?18:21
*** mickeys has joined #openstack-meeting18:21
rodrigodsthat was one doubt i had18:21
rodrigodsand forgot to ask in the review18:21
*** pvaneck has joined #openstack-meeting18:21
bretonrodrigods: no18:21
rodrigodsso... what is that?18:21
ayoungso...can I suggest that we use Ipsilon for testing?  K2K will only get us SAML, and we'd like to test OpenIDC as well18:21
bretonrodrigods: the plugin will do only set up. Like installing shibboleth.18:22
rodrigodsayoung, ++18:22
rodrigodsbreton, hmmm18:22
rodrigodsnow everything makes sense18:22
ayoungshib isnot going to do OPENIDC, is it?18:22
rodrigodsstevemar, even the name ^18:22
dstanekbreton: if it doesn't live in keystone do we create another repo for it?18:22
bretondstanek: yes18:22
dstanekbreton: any reason for that/18:22
bknudsonis it just the plugin that's in a repo or also the tests?18:23
amakarovdstanek, what do you think, may implementing SAML in keystone be easier solution?18:23
stevemarayoung: it wouldn't no18:23
bretondstanek: the plugin expects that it has a /devstack directory in the root of the repo18:23
dstanekamakarov: easier than?18:23
bretonthere is an alternative to a plugin in a repo -- create directory /devstack in the Keystone tree.18:23
amakarovdstanek, than devstack plugin in separate repo18:23
*** henrynash has joined #openstack-meeting18:23
henrynash(back)18:23
ayoungits still WIP, but Patrick is still cranking on it.  Is there a comparable tech to Shibboleth for OpenIDC?  Something we'd have the repo set up?18:24
bretonbknudson: just the code that does setup. Installing and configuring shibboleth etc18:24
dstanekamakarov: we'll still need devstack plugins even if you guys like the saml2 stuff i'm working on18:24
stevemaryep18:24
bknudsonI'm fine with the devstack plugin being in keystone18:24
morganbknudson: ++18:24
amakarovbreton, /devstack in keystone tree is cool18:24
bknudsonit would provide useful documentation18:24
dstanekbreton: i'd rather it be in keystone so it's easier to manage18:25
rodrigodsbknudson, ++18:25
topoldstanek ++18:25
dstanekbreton: did you see how i implemented my devstack plugins?18:25
rodrigodsmove the work in /tests/functional to /devstack than?18:25
bknudsonI hope the tests are still in /tests.18:25
bretoni've split it into 2 patches -- https://review.openstack.org/307371 Functional testing setup and https://review.openstack.org/307960 Federation testing setup (which uses the repo in the previous spec)18:25
*** mickeys has quit IRC18:25
bretondstanek: yes, i have18:25
bretonbknudson: the tests are in tempest_plugin_keystone18:26
dstanekbreton: that was modeled after what the gate really does18:26
bretonbknudson: in fact, there is no strong preference, i think we can still have them in /tests18:26
ayoungbreton, nice18:26
rodrigodsbknudson, breton, if we are going to use the tempest plugin18:27
rodrigodsit should remain there18:27
rodrigodsthe setup is different from the tests18:27
bretonyep. Usage of tempest plugin is optional for the spec.18:27
bknudsonif you use the plugin, you can run more tests18:27
* ayoung likes where this is going18:27
bknudsonis it automatic where more tests run, or is it a config option to enable it?18:28
rodrigodsbknudson, btw, did you see the job has been merged?18:28
rodrigodsayoung, ++18:28
bknudsonrodrigods: I did. Waiting to see results. If it works, make it voting.18:28
rodrigodsbknudson, ++18:28
bretonbknudson: what is automatic?18:28
bknudsonbreton: if the plugin is available, will federation tests run?18:28
bretonbknudson: no. The devstack plugin does only set up. Nothing related to tests.18:29
breton(i should probably cut out tempest-related things from the spec)18:29
bknudsonor do the tests have to be configured to run the federation tests?18:29
dstanekbknudson: i think we'd need another job to use the plugin and run the tests18:29
*** krtaylor has joined #openstack-meeting18:29
stevemardstanek: that would make sense18:30
bretondstanek: or modify existing one18:30
stevemari always thought that each test suite would have a different job18:30
dstanekunfortunately the details are superseded http://git.openstack.org/cgit/openstack/keystone-specs/tree/superseded/functional-testing-setup.rst18:30
bretondstanek: (if we use tempest plugin; the modification would be minimal)18:30
dstanekyou wouldn't want to use the same setup for all test runs18:31
bretonwhy not? People have a lot of things running at the same time in production.18:31
bknudsonmight be a problem if there was a conflict where 2 things could run at the same time for some reason18:31
*** anilvenkata has joined #openstack-meeting18:31
stevemardstanek: i did that to clean up the repo, i can move it around18:31
dstanekbknudson: exactly18:32
bknudsonbut there's no conflict with the base tests and federation, right?18:32
dstaneki don't believe there is at this point18:32
bknudsonthere would be a conflict if you had a test for sql and for ldap18:32
bretonbknudson: probably there should be multiple plugins then. A plugin to set up federation, a plugin to set up rabbit etc.18:33
rodrigodsmakes sense18:33
bretonmultiple plugins == multiple repos18:33
rodrigodswhy?18:33
rodrigodsnot subfolders?18:33
bknudsonlets start with one repo and worry about multiple later.18:33
*** mickeys has joined #openstack-meeting18:33
dstanekbreton: we already have too many repos :-)18:33
bretonrodrigods: because devstack plugins are supposed to live in a git repo.18:33
ayoungdo LDAP in DSBE only18:33
*** jprovazn has quit IRC18:34
ayoungcan we deprecate LDAP as the identity backend an only support Domain Specific?18:34
*** prad has joined #openstack-meeting18:34
rodrigodswe can use git submodules than18:34
dstanekrodrigods: no, please, no18:34
rodrigodsdstanek, lol ok18:35
bretonOK, so for now i suggest to have a plugin in Keystone main tree that would do setup of all components. If they break or conflict in the future, decouple them into repositories.18:35
amakarovbreton, ++18:36
*** doug-fi__ has quit IRC18:36
rodrigodsbreton, ++18:36
stevemarsounds okay for now18:36
amakarovone step at a time18:36
knikollabreton: ++18:36
rodrigodsthe approach may change when it happens too18:36
samueldmqyeah, let's start simpler18:36
bretonthis won't break any architecture or whatever.18:36
dstanekbreton: we're talking devstack plugin right? not tempest plugin18:36
bretondstanek: yes18:36
*** singhj has joined #openstack-meeting18:36
*** rohit_ has joined #openstack-meeting18:37
breton#link http://docs.openstack.org/developer/devstack/plugins.html#plugins18:37
dstanekbreton: ok, i modeled the /dsvm/* paths based on what the other projects where doing18:37
bretondstanek: maybe they didn't know about devstack plugins, because they are not so old18:37
*** pradk_ has quit IRC18:38
bknudsonthere's no dsvm paths that I can find?18:38
*** mickeys has quit IRC18:38
dstanekthat very well could be18:38
roxanaghebreton, would this plugin be able to setup ldap backend as well?18:38
*** pradk has quit IRC18:38
bknudsonthere's ./ironic/ironic_tempest_plugin18:38
dstanekbknudson: maybe they've move to plugins?18:38
rodrigodsyeah, ironic uses /devstack18:38
rodrigodsfor example18:38
*** pabelanger has joined #openstack-meeting18:38
*** ociuhandu has quit IRC18:38
rodrigodsdstanek, there is a issue with the tempest plugin naming18:38
bretonroxanaghe: afaik you don't need a plugin to set up LDAP backend, i thought that devstack can do that out of the box18:38
rodrigodswe must have "keystone" in it18:38
ayounglets have a "get LDAP testing a reality hackfest" at the summit18:38
*** haukebruno has joined #openstack-meeting18:39
rodrigodsayoung, ++18:39
ayoungdevstack can do it, and then we need to do the DSBE stuff...not huge18:39
roxanaghebreton, that's what I know as well, we just need to enable that in devstack18:39
bretonroxanaghe: i think you meant in the gates18:39
ayoungone big use case is to transition people that were using LDAP as the Identity backend to SQL with DSBE.  THus, the LDAP backed domain has to be V218:40
roxanaghebreton, right :)18:40
ayoung"Default" domain18:40
dstanekrodrigods: easy fix18:40
rodrigodsdstanek, ?18:40
*** Shrews has joined #openstack-meeting18:40
stevemarayoung: ldap working hackfest, i like it18:40
dstanekrodrigods: fixing the naming18:40
rodrigodsdstanek, ahh, sure18:40
bknudsonif tempest is forcing us to use a name we don't want we should fix tempest18:40
*** sdake_ has quit IRC18:41
rodrigodsbknudson, it is just how the tox plugin does the discovery18:41
rodrigodsit looks for the folder name18:41
rodrigodsinside the repo18:41
bretonI am going to code some things by the summit so that you could discuss18:41
samueldmqbknudson: I don't like having to name "keystone" inside keystone too18:41
stevemarbreton: PoC would be great :)18:42
bretonyep18:42
stevemaralright, time for next topic18:43
*** lpetrut has joined #openstack-meeting18:43
*** prad is now known as pradk18:43
ayoungSo...can we open discussion now?18:43
rodrigodsayoung, should be quick18:43
rodrigodsmy topic18:43
stevemarayoung: quick topic first18:43
stevemar#topic Add protocol to identity provider using nonexistent mapping18:43
*** openstack changes topic to "Add protocol to identity provider using nonexistent mapping (Meeting topic: keystone)"18:43
stevemarrodrigods: ^18:43
gyeejust do it!18:43
stevemargyee: lol18:43
ayoung?18:43
rodrigodsok... so for federation we have 3 entities18:43
stevemarbug 157187818:43
openstackbug 1571878 in OpenStack Identity (keystone) "Add protocol to identity provider using nonexistent mapping" [Undecided,New] https://launchpad.net/bugs/1571878 - Assigned to Ron De Rose (ronald-de-rose)18:43
rodrigodsidp, protocol and mapping18:43
rodrigodswe can create a protocol using a nonexistent mapping18:44
ayoungI thought that mapping was enforced18:44
henrynashrodigods: use case being?18:44
bknudsonwhat happens when it tries to use the mapping and it doesn't exist?18:44
rodrigodsbut i'd suggest to have clear steps here18:44
rodrigodsbknudson, blows up, i guess18:44
rodrigodsdidn't try it18:44
rodrigods1 - create idp18:44
rodrigods2 - create mapping18:44
gyeebknudson, you'll get a nice 500 return code18:44
henrynashrodigods: ah sorry, I thought this was a feature you wanted!18:44
rodrigods3 - create protocol18:44
bknudsonthat doesn't seem very friendly18:44
*** dmorita has quit IRC18:45
rodrigodsso... we'd enforce the mapping_id while creating/updating the protocol18:45
rodrigodsthat's it... we even have someone willing to fix18:45
rodrigodsrderose, ^18:45
gyeewe can't have more than one mapping per protocol anyway18:45
gyeeI would even argue that they shouldn't even be separate resource18:45
*** iyamahat has quit IRC18:45
bknudsonyou can share mappings18:45
rderoserodrigods: ++ :)18:45
rodrigodsi have some tests that exposes this https://review.openstack.org/#/c/307508/2/keystone_tempest_plugin/tests/api/identity/v3/test_identity_providers.py18:46
*** mickeys has joined #openstack-meeting18:46
bknudsonyour tests are going to break!18:46
bknudsonwhat if someone is relying on this broken behavior?18:46
rodrigodsbknudson, nope! they are not waiting for an error18:46
gyeebknudson, sharing mapping?18:46
samueldmqbknudson: yes, someone maybe has built tools around this18:46
ayounggyee, you are probably right18:46
ayoungcould we merge mapping into protocol?18:46
rodrigodssamueldmq, bknudson, V10 driver?18:46
ayounggyee, hmmm, except for testing cycle...would be nice to be able to swap between mappings18:47
gyeewe already allow multiple *rules* per mapping18:47
samueldmqrodrigods: it's not about the driver, but the API behavior being changed18:47
gyeeso in essence, you have multiple maps18:47
*** toddjohn_ has joined #openstack-meeting18:47
ayoungyeah, we torqued that one up big time18:47
rodrigodssamueldmq, hmm right18:47
samueldmqrodrigods: I think bknudson is concerned about people already doing it in other order, that isn't the one you propose18:47
lbragstadso - we essentially need to require this attribute in the jsonschema https://github.com/openstack/keystone/blob/e380a3c005aa1c045bc15ef884edf3d0e20032f7/keystone/federation/schema.py#L11018:47
ayoungso...yeah, lets fix that one.18:48
samueldmqso that tooling would be broken if we "fix" it18:48
*** sdake has joined #openstack-meeting18:48
bknudsonhere's the stability guidelines: http://specs.openstack.org/openstack/api-wg/guidelines/evaluating_api_changes.html#guidance18:48
ayoungfor now, yes, only allow a protocol create/update with a valid mapping id18:48
bknudsonwhich I think argues for continuing to allow this18:48
bknudsonwe could deprecate the old behavior18:48
*** dmorita has joined #openstack-meeting18:49
rderoseayoung: ++18:49
ayoungis there really a problem with it being missing?  Does it 500 or something?18:49
*** pradk_ has joined #openstack-meeting18:49
rodrigodsA change such that a request which was successful before now results in an error response (unless the success reported previously was hiding an existing error condition).18:49
stevemarwhats the harm is having this continue? no user actually reported it (sorry rodrigods) :)18:49
dstanekisn't there a way to make it not 500 and be backward compatible?18:49
samueldmqbknudson: I think you're right: "A change such that a request which was successful before now results in an error response " is NOT acceptable18:49
rodrigodsbknudson, think we fall in the "unless"18:49
stevemari think we just have to live with this18:50
rodrigodsstevemar, i'd vote for deprecate18:50
ayoungWe need to put some thought into Federation mapping anyway...needs to be something managable by the Federaiton admins.  We should be able to lock down an Idp to map only to a subset of domains18:50
*** mickeys has quit IRC18:50
*** dane_leblanc_ has joined #openstack-meeting18:50
rodrigodsthis can just return an error of unauthorized just because the mapping was wrong18:50
rderoseayoung: totally agree18:51
rodrigodsnot sure, need to verify what happens in this case18:51
*** dane_leblanc__ has joined #openstack-meeting18:51
samueldmqayoung: maybe IdP's could be domain-specific configs, 1-1 relationship18:51
gyeeI was asked to implement mapping in Horizon the other day during the meetup talk. :-)18:51
*** anilvenkata has quit IRC18:51
ayoungLet's fix the 500, make it fail with a 420 or something and focus on the debug/develop side of Federation to mitigate.18:51
gyeechanging mapping is like changing policy.json18:51
*** iyamahat has joined #openstack-meeting18:51
ayoungLike the policy tool, someone should be able to say "what would I get IFF I passdin these attributes."18:51
*** dane_leblanc__ has quit IRC18:51
gyeehas all sorts of security implications if we are not careful18:51
ayoungpassed18:51
ayoungsamueldmq, I argued for 1-1 ad lost , but we can't do that now.18:52
gyeeat the minimal, need a mapping validation tool18:52
ayoungWe need to say "IdP P can map domains X,y,z"18:52
samueldmq"Changing an error response code to be more accurate." is acceptable as per the API change guideline18:52
stevemargyee: keystone-manage has one18:52
*** ebalduf has quit IRC18:52
*** cody-somerville has joined #openstack-meeting18:52
ayoungthere is the possibility of conflict, etc.18:52
gyeestevemar, it only validate syntax18:52
ayoungbut with the shadow table, we should be able to work around that18:52
*** aranjan has joined #openstack-meeting18:53
gyeesamueldmq, we got request to create a Keystone runbook as well18:53
ayoungOK...gonna snag the last 5 minutes if I might18:54
samueldmqgyee: relly ?18:54
rodrigodswould be nice to "compile" the mapping upon creation too18:54
stevemar#topic open discussion18:54
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:54
ayoungstevemar, ?18:54
* stevemar hands ayoung the mic18:54
ayoungFernet cannot become default18:54
samueldmqgyee: really? it'd be nice to have it for deferation workflow18:54
ayoungever18:54
gyeesamueldmq, yeah, some need to be automated by monitoring and response system18:54
stevemarayoung: i agree!18:54
ayoungFernet is key based.  We break multi site with Fernet18:54
lbragstadMe sigh18:54
stevemarit needs too much setup18:54
samueldmqgyee: that's very interesting18:54
ayoungHowever, we make Fernet the default in DEVstack18:55
shalehI was wondering when people would realize this18:55
samueldmqgyee: any other workflow than federation?18:55
samueldmqgyee: would be interesting to adopt that idea?18:55
*** dane_leblanc has quit IRC18:55
*** brucet has joined #openstack-meeting18:55
ayoungwe tell the world "Fernet is the expected deployment tool.  UUID is for development"18:55
shalehayoung: does using a replicated DB for the keys help with the multi-site?18:55
ayoungand if people really bug us "is it ok for small deploys" we grudging sigh and say 'sure'18:55
bknudsonthis is what https://review.openstack.org/#/c/195780/ does, it changes devstack so if you don't set the KEYSTONE_TOKEN_FORMAT it uses fernet18:55
gyeesamueldmq, yes, including federation18:55
*** dneary has quit IRC18:56
ayoungshaleh, bknudson ++18:56
*** dane_leblanc_ has quit IRC18:56
*** yolanda has joined #openstack-meeting18:56
*** banix has quit IRC18:56
ayoungshaleh, I think it is not our place to try and solve that18:56
ayoungkeys are funny things.  Lets let the deployers deal with deploying them18:56
shalehayoung: as long as our docs are clear I agree18:56
samueldmqgyee: maybe we could do that in the clients and start improving UX there18:56
ayoungsyncing them, securing them18:56
gyeebknudson, would that work for multi-instance devstack?18:56
samueldmqgyee: like openstackclient18:56
*** maishsk has joined #openstack-meeting18:56
*** aranjan_ has quit IRC18:57
lbragstadgyee no18:57
bknudsongyee: it does fernet setup, so probably not.18:57
ayoungbknudson, why the -1 Workflow on that?18:57
lbragstadgyee there isn't anything to sync the key_repository to the other nodes in the deployment18:57
bknudsonayoung: I was asked to add more info to the commit message.18:57
dstanekso multi-instance devstack has no way to do something on one node (like gen certs) and sync to the other?18:58
samueldmq(2 minutes left)18:58
*** amrith is now known as _amrith_18:58
gyeecan we create a "default" key for devstack as its mean for testing only18:58
lbragstaddstanek i'm not sure - but I'd be interested in using that if it exists to sync the key_repository18:58
stevemarayoung: cause if we have it on by default then it'll be hard to test if keystone's default behaviour :)18:58
*** iyamahat has quit IRC18:58
samueldmqgyee: may be an easy workaround18:58
ayoungbknudson, want me to do that?18:59
ayoungI can drop my patch in favor of this18:59
bknudsonayoung: yes.18:59
stevemarending it.....18:59
bknudsonayoung: I'd do it now but I've got a meeting.18:59
*** tonytan4ever has quit IRC18:59
lbragstado/18:59
samueldmqstevemar: ++18:59
ayoungI'm on it18:59
stevemarbknudson: you're always in meetings18:59
dolphmif it helps, it'd be fine to do fernet_setup on both devstacks, then overwrite A with B18:59
ayoungbknudson, just drop the -118:59
stevemar#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
*** henrynash has quit IRC18:59
openstackMeeting ended Tue Apr 19 18:59:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-04-19-18.00.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-04-19-18.00.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-04-19-18.00.log.html18:59
samueldmqthanks18:59
stevemarevacuate and go to -keystone!18:59
fungiinfra team, assemble!19:00
bkeroo/19:00
Zara\o/19:00
crinkleo/19:00
pleia2o/19:00
*** tonytan4ever has joined #openstack-meeting19:00
yolandao/19:00
* jeblair eats a just-in-time sandwich19:00
* stevemar steals one of jeblair's fries19:00
*** shaleh has left #openstack-meeting19:00
*** samueldmq has left #openstack-meeting19:00
* fungi prefers the precompiled variety19:00
*** Sukhdev has quit IRC19:00
*** fawadkhaliq has quit IRC19:00
mordredo/19:00
*** gagehugo has left #openstack-meeting19:00
* bkero imagines that infra-team form a Voltron where fungi is the head whenever that is said.19:00
clarkbhello19:00
fungi...and i'll form the head!19:00
*** neelashah1 has quit IRC19:00
nibalizero/19:01
fungiahh, good times19:01
* fungi sighs at voltron19:01
ianwo/19:01
SotKo/19:01
fungiwe have a shortish agenda, but i'll get going and add a couple chairperson's choice topics at the end, time willing19:01
docaedoo/19:02
fungithis week's topics brought to you by: crinkle, yolanda, rcarrillocruz, Zara, pleia219:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Apr 19 19:02:50 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
fungi#info Infra team meeting for April 26 (next week's) is hereby cancelled on account of there's a summit some of us might be attending. Join us again on May 3 at 19:00 UTC for our usual IRC meeting shenanigans.19:03
*** rocky_g has joined #openstack-meeting19:03
fungi#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
*** dimtruck is now known as zz_dimtruck19:03
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-04-12-19.02.html19:03
fungi"1. (none)"19:03
fungi#topic Specs approval19:03
*** salv-orlando has quit IRC19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
funginone new this week19:03
*** eil397 has joined #openstack-meeting19:04
fungi#topic Priority Efforts: Infra-cloud (crinkle, yolanda, rcarrillocruz)19:04
*** openstack changes topic to "Priority Efforts: Infra-cloud (crinkle, yolanda, rcarrillocruz) (Meeting topic: infra)"19:04
crinklehi19:04
yolandahi19:04
fungii hear there's some water19:04
eil397hi19:04
*** olaph has joined #openstack-meeting19:04
jeblairhello infra cloud?19:04
pabelangero/19:04
fungidid they relocate our cloud to a lake?19:04
*** jeblair sets mode: -o jeblair19:04
crinkleso we learned this morning that the houston data center was just shut off due to severe flooding in the area19:04
yolandahouston ecopod is shut down19:04
*** doug-fis_ has joined #openstack-meeting19:04
crinklewe don't know the state of the machines19:04
olapho/19:05
mordredwow19:05
pabelangereep19:05
*** sheel has quit IRC19:05
docaedoyikes19:05
crinklebut we can guess that this will likely delay our ability to start working on them19:05
morgankindof scary19:05
yolandahopefully they won't be swimming on a lake now19:05
crinklefor the summit19:05
Zarao.O19:05
crinklealso the hipchat server was in houston so we can't exactly ask19:05
yolandaso last news i had from the servers were from yesterday19:05
fungiunfortunate, though i guess we won't know more until lake houston recedes19:05
yolandathey had nearly completed the setup, pending on dhcp reconfiguration for ILOs19:05
*** sigmavirus24 is now known as sigmavirus24_awa19:06
yolandabut yes, cannot get more info until this passes19:06
*** neelashah has joined #openstack-meeting19:06
*** brucet has quit IRC19:06
* mordred suggests that in the future, putting datacenters in flood prone areas is less than ideal ..19:06
anteayalooks like continued rain for the rest of the week19:06
*** brucet has joined #openstack-meeting19:06
anteayaI didn't know Houston was flood prone19:06
jeblairmordred: in the future, all areas will be flood prone :(19:06
crinkleso just wanted to let everyone know what was going on and that we might plan to work on non-infra-cloud things during the friday workday19:06
fungithanks for the heads up! there's still plenty if infracloudish things we can kick around on summit friday even if we don't have machines to do it on19:06
anteayaany area would be flood prone if they got 45 cm rain in 24 hours19:06
mordredanteaya: it's a frequent target of hurricanes19:07
bkeroNew requirement: datacenters need to be constructed on large pontoons for additional 9s19:07
anteayamordred: ah, thank you19:07
mordredanteaya: well, yeah. any place would. except for places with an elevation compared to their surroundings of greater than 45cm19:07
fungianteaya: unfortunately much of our current landmass in north america was once occupied by an inland sea. perhaps it's returning19:07
anteayamordred: fair enough19:07
anteayafungi: seems to be a possiblity19:07
mordredfungi: ++19:07
fungianything else on this topic for now?19:08
crinklenot from me19:08
anteayaI lost my weechat server so won't be online while my compter is off19:08
fungi#topic Storyboard needs a dev server (Zara, pleia2)19:08
*** openstack changes topic to "Storyboard needs a dev server (Zara, pleia2) (Meeting topic: infra)"19:08
fungi#link https://storyboard.openstack.org/#!/story/2000028 Storyboard needs a dev server19:08
*** doug-fis_ has quit IRC19:09
pleia2I don't really have much more to add to this, we should provide them one19:09
anteayapleia2: ++19:09
Zarahi! :)19:09
pleia2thoughts? concerns, etc?19:09
fungiconcise!19:09
anteayaagreement19:09
nibalizeri thought we had one?19:09
Zarayeah, kind of same from me, detail's in the story (thanks for adding context, fungi)19:09
nibalizerclearly i am mistaken19:09
*** myoung has quit IRC19:09
ZaraI didn't understand the significance of the draft builds at all, so that's interesting19:09
fungiwe were going to have one, krotscheck had started some puppeting for it, those changes may still be kicking around in gerrit somewhere19:09
*** myoung has joined #openstack-meeting19:10
nibalizeris the idea to build it with puppet or ansible?19:10
*** banix has joined #openstack-meeting19:10
nibalizer"we want to update the user docs, so want to deploy a version with Ansible as non-Ansible-experts"19:10
pleia2nibalizer: a lot of the notes in that story are old19:10
Zaranibalizer: actually, that one's new19:10
pleia2we do want puppet, like everything else19:11
Zarawe have developer docs for storyboard, and there was a section for operator docs19:11
Zarabut the operator docs turned out to be completely wrong19:11
clarkbpleia2: especially since we already puppet ansible19:11
nibalizerhaha19:11
persiahttps://galaxy.ansible.com/palvarez89/storyboard/ may or may not be useful if some ansible is desired19:11
fungiyeah, i think the solution here is to proceed in the direction we started originally... dev/prod puppet classes like we have for other stuff, spin up a second machine with the dev class, add a separate trove db with dummy/sample data or something19:11
pleia2sounds good, I'm happy to work with the storyboard folks on this post summit19:12
nibalizerme too19:12
pleia2will pull in help as needed19:12
pleia2thanks nibalizer!19:12
nibalizero719:12
rcarrillocruzheya19:12
Zaraso yeah, at the time, we were thinking 'we should get round to deploying something with ansible, as people who don't know ansible, so we can write docs for setting up wiht that role', and a dev server seemed a way to kill two birds with one stone19:12
rcarrillocruzsorry, raining a bit causing traffic jam back home19:12
*** zz_dimtruck is now known as dimtruck19:12
*** iyamahat has joined #openstack-meeting19:12
nibalizerZara: i think a dev server should look very close to our prod server19:12
clarkbrcarrillocruz: are you in houston?19:12
rcarrillocruz:-)19:13
Zarabut it's not necessarily part of a dev server setup; it seemed the simplest option at the time (where we thought we might be on our own for it)19:13
rcarrillocruzi was driving a car, not rowing a boat19:13
rcarrillocruz:D19:13
SotKfungi: that approach sounds good to me19:13
rcarrillocruzso no, not in houston yet19:13
Zaraso that's the context on that19:13
fungithere's nothing wrong with having multiple dev servers, i just continue to believe that one dev server for it should be hosted where we can point the storyboard-webclient draft jobs19:14
* mordred is supportive of a dev server for Zara19:14
anteayaagreed19:14
mordredif someone wants to get FANCY ...19:14
anteayaand SotK19:14
*** doug-fish has joined #openstack-meeting19:14
fungibut also the goal of having the puppet module be reconsumable is to make it easy for others to set up dev or prod servers of their own19:14
mordredsyncing data from prod sb would be neat19:14
mordredon a periodic basis19:14
odyssey4meo/19:14
nibalizeran ansible role to deploy storyboard is something i think we'd be happy to host and test19:15
mordredbut I do not think anyone should block doing the dev server on that19:15
anteayaodyssey4me: you made it!19:15
*** Sukhdev has joined #openstack-meeting19:15
rcarrillocruzi'm happy to help with that19:15
odyssey4meanteaya thanks goodness for appointment reminders, which are useful if you've got the dates set right :)19:15
fungii'm not opposed to having an ansible role for deploying storyboard, but i think that whatever server we're maintaining still needs to be deployed with puppet similar to teh rest of our servers19:15
rcarrillocruzi'm idle-ish on my puppet/ansible tasks lately19:15
anteayaodyssey4me: yay correct dates19:15
*** esker has joined #openstack-meeting19:16
anteayafungi: agreement19:16
fungidon't want to get into a one-of-these-things-is-not-like-the-other situation with our server management19:16
rcarrillocruzpossibly a puppet module for dev sb, plus an ansible playbook to sync up data and all19:16
rcarrillocruz?19:16
pleia2fungi: yeah19:16
*** dneary has joined #openstack-meeting19:16
Zara:) thanks, everyone, and yeah, if it's on the same infra, I agree to do it the same way19:16
Zaras/to/we should19:16
fungiokay, so seems like general agreement, and the task was already begun at one point, so should be reasonable to just pick it back up and continue running with it19:17
Zara\o/19:17
nibalizerno19:17
nibalizerthe puppet module for storyboard should deploy both serevrs19:17
nibalizerwith slightly different inputs19:17
fungiright, that's what i meant about having two classes (implication was in system-config)19:18
*** Sukhdev has quit IRC19:18
fungiboth using a generalized storyboard puppet module19:18
nibalizerand generally i feel that our pattern of two classes isn't correct19:18
nibalizerwe should really only need one with differen inputs19:19
* fungi handwaves19:19
nibalizerbut i'm not exactly volunteering to do that refactor19:19
fungiyou prefer we abstract our differing inputs out into the global site manifest? (or hiera something something?)19:19
nibalizeranyways i think we have consensus19:19
*** Sukhdev has joined #openstack-meeting19:19
fungiokay, cool19:19
fungino need to beat this to death in-meeting. moving on19:19
*** brucet has quit IRC19:20
rcarrillocruz++19:20
*** cody-somerville has quit IRC19:20
nibalizeryep19:20
rcarrillocruzthe prod/dev classes is horrible19:20
fungi#topic Infra-cloud changes needed with new setup: east/west, network ranges (crinkle, yolanda, rcarrillocruz)19:20
*** openstack changes topic to "Infra-cloud changes needed with new setup: east/west, network ranges (crinkle, yolanda, rcarrillocruz) (Meeting topic: infra)"19:20
yolandahi19:20
yolandaso with the movement,we don't have east/west19:20
yolandaeverything ended into the same network19:20
yolandaso I wanted to raise the topic about the two clouds separation now19:20
*** brucet has joined #openstack-meeting19:21
yolandado we still want to keep them separate? if so, what about the naming, network ranges, etc?19:21
clarkbI think having two clouds is a good idea, then we can do staggered upgrades and have no shared data or services19:21
mordredya++19:21
clarkbwhich fits into our original model of completely tearing it down an drebuilding it as the upgrade path19:21
crinkleyeah i think we still wanted that logical separation for that ^19:21
fungias in should we continue with the plan we discussed in ft. collins to assign hosts to one "cloud" or the other and then assign them separate public network allocations?19:21
*** maishsk has left #openstack-meeting19:21
nibalizerseparation++19:21
mordredsounds right19:21
jeblair++19:22
fungior really we can even stick with the same netblocks/upstream gateways/routes i think and just adjust the assignment ranges in neutron?19:22
*** dmorita has quit IRC19:22
yolandaso in terms of network, with have a /19 public range now, so we split that in two, and have the same numbers of servers in both?19:22
clarkbas far as names we could continue to call them east and west just to be confusing :)19:22
yolandaand east/west, sounds confusing19:22
*** maishsk has joined #openstack-meeting19:22
fungivanilla cloud, chocolate cloud19:22
clarkbor cloud1 cloud219:22
* fungi engages in the bikeshed19:22
mordredcloud1/cloud2++19:22
yolandaalso, the number of servers in east/west was so unequal, this can be a good opportunity to rebalance the servers, and have the same numbers on both19:23
jeblairi like vanilla/chocolate :)19:23
clarkbyolanda: ++19:23
fungiRegionOne and RegionNone!19:23
nibalizeri like vanilla chocolate19:23
morganmordred: ++19:23
yolanda++ for vanilla chocolate19:23
*** maishsk has left #openstack-meeting19:23
nibalizersplitting the server baesd on hardware class makes sense to me19:23
rcarrillocruzyeah, although vanilla could tell people there's a special custom flavor on chocolate :D19:23
clarkbyolanda: for the networking I think we get the most flexibility if we do split it between the clouds19:23
rcarrillocruzas in19:23
nibalizerwe had 3 different models19:23
rcarrillocruzvanilla kernel19:23
rcarrillocruzvanilla cloud19:23
fungiyeah, i was wondering if we should be grouping by model, roughly19:23
rcarrillocruzanyway, bikeshedding...19:23
crinklethere is different hardware in west and east so there might end up being differences, like in the mellanox cards19:23
clarkbyolanda: in theory because we use provider networks we don't need to do that but will let us move away from that in the future19:23
*** maishsk has joined #openstack-meeting19:23
clarkbcrinkle: ya, I have a feeling that it will be best effort due to that19:24
jeblairwould it make sense to do 3 clouds then?19:24
nibalizerya so split clouds, vanilla/chocolate naming scheme, and split on hardware type19:24
*** apoorvad has quit IRC19:24
fungistrawberry, obviously19:24
jeblairya19:24
yolandashiny new hardware on one cloud, crap hardware on the other?19:24
fungiso we can be neopolitan19:24
jeblairis the 3rd model type different enough to warrant that?19:24
crinklecookiedoughcloud19:24
nibalizeri highly doubt anything is 'shiny new'19:24
yolandaold vs oldest?19:25
crinklehaha19:25
nibalizersure19:25
fungireally old, and really really old19:25
nibalizerpoint is if we have to firmware upgrade the mellanox cards or the whatever that would affect only one cloud19:25
nibalizerwhich i think is more our style than trying to run 2 clouds at half capacity19:26
*** nadya has joined #openstack-meeting19:26
fungiyeah, i see the most benefit from roughly splitting by server models, where we can19:26
jeblairwhat are the 3 classes?19:26
crinklei think grouping servers in a rack together makes sense, in case they decide they want to move one or a switch goes down on one19:26
jeblairi only see two in http://docs.openstack.org/infra/system-config/infra-cloud.html19:26
fungicrinkle: any chance the racks are mostly one model or another?19:27
nibalizerunfortunately that lacks model numbers19:27
yolandacrinkle, do you have the rack diagrams handy? not on vpn now19:27
rcarrillocruzcrinkle: that's a  good suggestion19:27
rcarrillocruzlike that19:27
crinklefungi: i think west the west rack is moreorless one model, east may be a couple different models19:27
nibalizercrinkle: i think grouping servers by geolocation is good too19:27
crinkleyolanda: nope i do not19:27
rcarrillocruzcos it's pretty common to lose availability in racks19:27
*** mc_nair has left #openstack-meeting19:27
nibalizerprobably better than grouping by hardware classification19:27
yolandai can get those tomorrow, there are listed on a jira ticket19:27
jeblaircan we update the documentation to reflect reality?19:28
*** dmorita has joined #openstack-meeting19:28
yolandaoh wait, i have a copy on email19:28
*** dmorita has quit IRC19:28
fungisure. it looked like they were doing 802.3ad lag cross-device for uplinks, but still if we're not aggregating at teh host level then a switch outage is still going to impact half a rack19:28
jeblairi feel a little in the dark here.  i agree that in principle having a cloud for each of our major configurations sounds reasonable, but i don't know how many that is, or whether the differences are substantial.19:29
yolandaso we have rack 5, 8, 9, 12, and 1319:29
yolandanice19:29
fungialso, i'm with jeblair here, our docs should ideally grow at least a loose rack diagram with host names, and then we should have some table somewhere mapping up models to host names/ranges19:29
yolandai can take care of that19:29
crinklethanks yolanda19:30
fungimakes it easier to reason about stuff like this19:30
fungithanks!19:30
pabelanger++19:30
yolandayep, we better have all documentation on place, then decide19:30
*** gyee has quit IRC19:31
fungiokay, anything else on this front?19:31
yolandanot from my side19:31
*** dmorita has joined #openstack-meeting19:32
fungi#topic Contact address for donated test resources19:32
*** openstack changes topic to "Contact address for donated test resources (Meeting topic: infra)"19:32
*** eil397 has quit IRC19:32
fungithis is something i'd like to get a little consensus, mostly from the root sysadmin team on19:32
*** mbound has joined #openstack-meeting19:32
*** ociuhandu has joined #openstack-meeting19:32
fungiwe had a service provider donating resources to us try to reach out to let us know our service was expiring19:32
*** brucet has quit IRC19:33
fungithe address we gave to contact us is a dumping ground for backscatter from gerrit and other sources of e-mail19:33
fungiwhich nobody looks at afaik19:33
fungiit's on a webmail service19:33
*** brucet has joined #openstack-meeting19:33
jeblairwe look at it when we know we need to look there19:33
fungiyeah19:33
fungii hopped on there today and it had almost 25k unread messages19:34
fungiwondering whether anyone objects to splitting that up and not pointing service provider accounts at that19:34
mordredwe should probably have a root-spam@ and a root-important@19:34
nibalizerya19:34
nibalizeri would read mail forwarded to me from a root-important@19:34
mordredI think having a place that does not get cron or gerrit emails that we can point account signup things to would be great19:34
fungithis is more or less what i was considering19:35
nibalizeryes19:35
clarkbmordred: +119:35
yolandamordred ++19:35
pabelangeragreed19:35
pleia2and seems likely I'd have less of a bounce problem if I was just getting -important19:35
*** banix has quit IRC19:35
mordredof course, we probalby need the main root-important@ alias, and then probably more than one alias pointing to it - because at some places we need more than one email to sign up for more than one account19:35
pleia2(my gmail usage means we turned it off entirely for me)19:36
fungiwe could i suppose have a "hidden" ml at lists.o.o and subscribe interested infra-root members (since they're the only ones who have access to the logins for those services)19:36
jeblairpleia2: this is not the same thing as that19:36
pleia2jeblair: oh19:36
pabelangerfungi: I would be okay with that too19:36
nibalizermordred: +parts?19:36
*** Sukhdev has quit IRC19:36
jeblairpleia2: that is mail to root from systems19:36
mordrednibalizer: maybe so19:36
jeblairpleia2: this is mail from external services19:36
fungiyeah, this particular address currently does not go directly to any of us19:36
nibalizeri love getting email from humans19:36
pleia2jeblair: ah yes, we do have two email accounts19:36
fungiit goes into a webmail account in rackspace and rots until someone goes spelunking19:36
nibalizeri hate getting email from robots19:36
pleia2er, config things19:36
mordredI don't REALLY like human email19:36
mordredbut I'll deal with it19:36
*** haukebruno has quit IRC19:37
jeblairthis would still pretty much all be from robots19:37
*** pradk has quit IRC19:37
jeblairjust fewer of them19:37
rocky_gmordred, ++19:37
*** pradk_ has quit IRC19:37
fungisome of my best friends are robots, after all19:37
nibalizerwell lets try it19:37
anteayahopefully saying important things19:37
nibalizermove a couple accounts to the new addr and see if it seems like its working, then move the rest19:37
*** banix has joined #openstack-meeting19:37
fungiso the main question was hidden list in mailman vs aliases forwarder somewhere?19:37
jeblairfungi: mlist sounds good; though as mordred mentions, we'll need at least 2.19:38
pabelangermailman+19:38
*** eil397 has joined #openstack-meeting19:38
fungisure, that's really no harder than one ;)19:38
jeblair(but one can obviously just be tied to the other)19:38
*** BobH_ has quit IRC19:38
*** pradk has joined #openstack-meeting19:39
*** fzdarsky has joined #openstack-meeting19:39
fungiand the only reason i say "hidden" is so that the general population doesn't think it's a way to reach us for support19:39
*** mpaolino has quit IRC19:39
anteayawell also I think the archives should be hidden too19:39
jeblairfungi: also, this will be a vector for compromising our cloud accounts19:39
anteayaas the posts may contain credentials or other sensitive information19:39
nibalizerjeblair: ah hrm19:39
*** pradk has quit IRC19:40
jeblairanteaya: so, not archived at all :)19:40
anteayaeven better19:40
fungijeblair: anteaya: correct19:40
*** Swami has joined #openstack-meeting19:40
fungiand a very good point19:40
fungiso now wondering if an ml alias somewhere more secure wouldn't be a better idea19:40
fungier, e-mail alias, non-ml19:41
jeblairif we're worried about a mailman bug opening that up, better to stick with a redirect, though we don't have a great host for that.19:41
*** Sukhdev has joined #openstack-meeting19:41
*** mtreinish has quit IRC19:41
fungia very small vm?19:41
jeblairmight be able to just set up forwarding addresses (without being real accounts) on the foundation mail server, but i'm not positive, and that has limited access for us19:41
bkeroporque no procmail?19:42
nibalizerjeblair: i think that might be the way to do it19:42
nibalizerjust configure it with a rule to forward19:42
*** mbound has quit IRC19:42
*** mtreinish has joined #openstack-meeting19:42
fungithe current keys to the kingdom are on a server which we probably don't want processing inbound e-mail from the internet19:42
mordredno. probably not19:42
fungiso i'm feeling more and more like a separate very tiny vm would be more suitable, as much as i hate to suggest that19:43
*** gordc has joined #openstack-meeting19:43
anteayathe best bad idea going it sounds like19:43
fungialso stopping using @openstack.org for it means that we're reducing at least some of the risk exposure for compromising our accounts19:43
*** pradk has joined #openstack-meeting19:43
jeblairmark my words -- we'll be running a cyrus server in no time.  :)19:44
fungisomealias@somehost.openstack.org instead19:44
clarkbwould a simple forward not work?19:44
fungiclarkb: simple forward where and how from what to what?19:44
dougwigjeblair: *shudder*19:44
jeblairclarkb: i think that is the idea under discussion.19:44
clarkbor require all infra root to imap the existing account19:44
clarkbfungi: from current account to each of our personal accounts19:44
clarkbor invert it and pull via map19:44
*** dimtruck is now known as zz_dimtruck19:44
*** baoli has quit IRC19:44
fungithat's an option i hadn't considered, though the existing account is a wasteland of terrible. best to cut our losses there19:44
jeblairclarkb: oh, well the current account gets all of the backscatter from everything.19:45
fungioption being imap the current account19:45
clarkbok filter on to infra-root or wheatever19:45
clarkbthat isn't unsolvable aiui19:45
jeblairto be clear, the current account is exactly what we already want -- it's just too much of what we want :)19:45
fungii don't know about setting up a forward from the current account. we *might* have that ability in the mailbox configuration19:45
jeblairfungi: we do19:45
dougwigi'd also suggest using plus addressing on the recipient, to make your personal filters trivial.19:45
nibalizerthe problem with that is not everything takes it19:45
jeblairfungi: that's how my account was set up before it was deleted.19:46
fungiokay, so that doesn't need someone at the foundation to fix for us then? just adding another alias would need assistance?19:46
nibalizerwhich can be super frustrating19:46
jeblairfungi: i'm not clear what's actually being proposed though19:46
fungijeblair: however, i still very much like the idea of an account on a server which someone who isn't us is less likely to delete19:46
jeblairtell me what i'm missing from "forward all 1k messages/day to all of us"19:46
clarkbjeblair: filter out the stuff that isn't to infra-root19:46
clarkbaiui infra-root is just an alias for another thing that has been in use for forever?19:47
fungiassuming we're not already using infra-root@o.o for other stuff19:47
jeblairinfra-root is the account; there are several aliases that point *to* it19:47
clarkbjeblair: ah ok19:47
clarkbis there not one alias that is significantly less noise than the others?19:47
jeblairwe generally have not signed up with infra-root19:47
jeblairmost of the mail goes to the other aliases19:47
nibalizerso create root-important@o.o and fwd it to infra-root@o.o and configure the infra-root account to spray things that came in to root-important out to each of us19:47
jeblairlike 'gerrit@' and 'jenkins@' and 'openstackinfrastructurebot@' or whatever19:47
clarkbjeblair: ya19:48
fungithough that mail service does have some manipulation rules which could possibly be used to forward based on recipient address19:48
clarkbso as long as we have one that isn't the spam addr, it should mostly work?19:48
fungii haven't looked closely at that feature19:48
mordredhonestly, I think even if the mail service does not have selective forwarding19:48
mordredit' snot a problem19:48
mordredwe all have the ability to filter email locally19:48
jeblair(the reason we have multiple aliases pointing to the account is that the foundation pays per-account, but not per-address, and they wanted to keep costs down, so we collapsed them that way)19:48
mordredand most of us pretty trivially19:48
nibalizeryah19:48
fungithat's still a lot of messages for all of us to bitbucket continually19:48
mordredtotally19:49
clarkbfungi: mordred if we did it server side int oa folder then imap only that it wouldn't be19:49
mordredjust saying - if we can't forward per recip - we can filter locally19:49
*** mtreinish has quit IRC19:49
clarkbput all mail addressed to important user foo in folder important, then everyone imap that19:49
clarkbor forward just that folder, eithe rway we should be able to make something work19:49
mordredsure. it's email, one of the most robust systems on the planet. there are at least 1-billion ways to solve this. I support all of them19:49
fungii'm open to adding another imap box in my mutt config as long as someone is volunteering to fiddle with the filtering mechanism there19:50
jeblairi can do so, but not this week19:50
fungi("there" meaning in the rackspace mail app stuff)19:50
fungiyeah, i don't think this is crazy-urgent, but it is something i need to make sure we don't forget we're not doing19:50
jeblairif you want to action me to investigate that, i can19:51
*** iyamahat has quit IRC19:51
dougwigif it's imap, then you should definitely plus address, as that lets you pick the subfolder on the host, and not use filters at all.19:51
*** iyamahat has joined #openstack-meeting19:51
jeblairand since we're not meeting next week, that gives me some time :)19:51
clarkbdougwig: as nibalizer said yo ucannot rely on that19:51
clarkbdougwig: its great when it works, terrible when it doesn't19:51
fungion a related note, we ought to get contact addresses for things like the providers' incident trackers coifigured to go into whatever solution we're coming up with19:51
jeblairwe should not sign up for anything that does not accept a plus address :)19:51
fungier, configured19:51
*** iyamahat has quit IRC19:51
dougwigeh, you control the destination MTA, so you absolutely can.19:51
clarkbjeblair: I suppose that is also a valid stance19:52
clarkbdougwig: its the side sending you email that often rejects valid email addresses19:52
fungibecause right now i think one of them sends updates to monty, one sends them to someone in foundation executive management, et cetera. it's all over the place19:52
anteayafungi: is this the last topic you wanted to get to today?19:52
jeblairwhere we went wrong was ever signing up something that *didn't* go to monty19:53
dougwigclarkb: *blinks* -- the sending mta has nothing to do with it; it's fully compliant.19:53
*** dbecker has joined #openstack-meeting19:53
fungi#action jeblair investigate mail filtering by recipient options for infra-root@o.o inbox19:53
jeblairmordred is an excellent email filter/responder thing19:53
clarkbdougwig: many services will reject email addresses with + in them19:53
fungianteaya: had one more quick one19:53
*** Sukhdev has quit IRC19:53
anteayafungi: k19:53
fungi#topic Summit session planning19:53
*** openstack changes topic to "Summit session planning (Meeting topic: infra)"19:53
fungijust some quick updates/links here for convenience19:53
fungias teh summit draws ever closer19:53
jeblairdougwig: we also don't control the receiving mta if we continue to use the foundation's mta (but if we spin up a server, we will, and could use + addressing with any character)19:54
*** adiantum has joined #openstack-meeting19:54
fungipleia2 has already started a list of "infra-relevant sessions not in our track" at the bottom of the planning etherpad, so that might be a good place for people to add others and try to coordinate and make sure we get good coverage when there are conflicts19:54
*** lhcheng has left #openstack-meeting19:55
fungi#link https://etherpad.openstack.org/p/infra-newton-summit-planning add infra-relevant sessions at the bottom for coordination purposes19:55
fungiin my e-mail announcement to the list with our finalized schedule, i also included a shorthand for some of the conflicts i spotted19:55
mordredthank you!19:55
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-April/004162.html finalized session schedule with conflicts noted19:56
Zara:) thank you19:56
eil397thank you19:56
fungi#link also pleia2 started our etherpads for the various sessions and i've linked them from the usual wiki page19:56
*** iyamahat has joined #openstack-meeting19:56
fungi#link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Infrastructure summit sessions wiki links19:56
clarkbthey are also linked fro mthe session schedule19:56
nibalizerthanks pleia219:56
anteayathank you pleia2 and fungi19:57
SotKthanks pleia2, fungi19:57
pabelangerlooking forward to the collaboration19:57
fungii included utc time translations there for the benefit of people trying to follow along remotely in etherpads during/after sessions (or who, like me, keep personal time in utc when travelling)19:57
anteayathank you19:57
eil397thanks pleia219:58
fungiclarkb: ahh, yep, i did also put the etherpads in the official schedule as you noted19:58
* anteaya also uses utc time19:58
mordredfungi: you should include a key that tells us what time drinking starts in UTC in the area19:58
fungi#link https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Infrastructure%3A official summit schedule19:58
jeblairif/when we split the developer summit from the marketing summit, we should have the developer summit schedule be in utc19:58
fungimordred: starts?19:58
mordredfungi: good point19:58
anteayajeblair: agreed19:58
pleia2ah, good idea re: utc19:58
mordredfungi: for this summit, maybe we should make it a goal to do one-drink-per-session19:58
jeblairas another shibboleth to let people know they're at the wrong event :)19:58
fungii'll try to backlink other appropriate metadata in the etherpad headers before the end of the week too, in preparation19:58
anteayajeblair: ha ha ha19:59
fungiany summit questions in these last few seconds?19:59
fungiwe're at about 30 seconds remaining19:59
*** jckasper has quit IRC19:59
jeblair'hi, you showed up at 3am, you probably meant to attend this *other* event'19:59
docaedocan we postpone for a week or two you think? hold out for better weather?19:59
fungibetter weather19:59
fungiyes, prepare for a lot of wet19:59
*** gouthamr has joined #openstack-meeting19:59
*** gouthamr has left #openstack-meeting20:00
*** elo has joined #openstack-meeting20:00
fungii'm told inner tubes are a good travel accessory20:00
anteayawoooo water20:00
fungiand we're at time. thanks all, hope to see lots of you in austin!!!20:00
Zara\o/20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Apr 19 20:00:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-04-19-19.02.html20:00
*** agentle has joined #openstack-meeting20:00
bkerobye!20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-04-19-19.02.txt20:00
*** yolanda has left #openstack-meeting20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-04-19-19.02.log.html20:00
crinkleo/20:00
fungitake it away, ttx!20:00
ttxo/20:00
*** cdent has joined #openstack-meeting20:00
*** eric_lopez has quit IRC20:00
mesteryo/20:00
docaedoo/20:00
sdagueo/20:00
*** johnthetubaguy-w has joined #openstack-meeting20:01
*** jckasper has joined #openstack-meeting20:01
*** pabelanger has left #openstack-meeting20:01
ttxannegentle, dims, dhellmann, flaper87, johnthetubaguy, mtreinish, thingee, mordred, morgan, russellb: around ?20:01
agentle\o20:01
dimso/20:01
thingeeo/20:01
dhellmanno/20:01
mordredttx: I dunno20:01
*** agentle is now known as annegentle20:02
* edleafe hides in the back20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Apr 19 20:02:06 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
dhellmannttx: flaper87 asked me to say he might not make it today20:02
*** pradk has quit IRC20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
* morgan hides.20:02
* stevemar sneaks in and sits in the back20:02
ttxHi everyone!20:02
ttxOur agenda for today:20:02
*** annegentle is now known as Guest1493020:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** Guest14930 is now known as agentle20:02
* rocky_g snuffles and coughs quietly in in the back but away from edleafe or stevemar 20:02
* edleafe can't see with stevemar sitting in front of him20:02
*** piet has joined #openstack-meeting20:02
ttx#topic Retire release:has-stable-branches tag20:02
*** openstack changes topic to "Retire release:has-stable-branches tag (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/30570220:03
ttxThis one completes the transition to stable:follows-policy by removing the old has-stable-branches tag20:03
morgano/20:03
ttxNow has enough votes to pass, will approve now unless there are questions20:03
johnthetubaguyno questions from me20:03
ttx#action ttx to follow up to project navigator folks so that they use the new tag20:04
ttx#topic Add release:cycle-trailing tag20:04
*** openstack changes topic to "Add release:cycle-trailing tag (Meeting topic: tc)"20:04
ttx#link https://review.openstack.org/30603720:04
ttxThis one fills a gap we currently have: some projects are not formally part of "the OpenStack release" (since they release after the date) but still are pretty attached to the cycle20:04
sdaguethis seems pretty straight forward20:04
*** lpetrut has quit IRC20:04
ttxCurrently we force those to be "independent", but that's not the right answer20:04
*** neelashah has quit IRC20:05
ttxHence the proposal for a specific model for things that are linked to the release cycle while not formally part of the release20:05
sdaguebasically for packaging / config management stuff to follow official release right?20:05
ttxYeah... The only thing I'd like us to be careful with is our usage of the word "release"20:05
*** johnthetubaguy-w has quit IRC20:05
ttxI still think "the Mitaka release" should be done and complete on release day, otherwise it doesn't mean anything20:05
ttxSo cycle-trailing things are not part of "the release", they are published after the release20:05
ttxAnd we'll have to present things on releases.o.o in a way that makes that clear20:05
johnthetubaguyttx: ah, good point, they depend on the the mitaka release20:05
*** salv-orlando has joined #openstack-meeting20:06
ttxStill a better place to be than to consider them cycle-independent20:06
sdagueyeh, I guess, I doesn't seem to me to be that confusing if puppet for mitaka lands the week after the release :)20:06
ttxwhich was just wrong20:06
sdaguebut so be it20:06
*** sigmavirus24_awa is now known as sigmavirus2420:06
*** _amrith_ is now known as amrith20:07
morgansdague: i don't see it that way, but this is a nice clarification20:07
morgansdague: erm.. i see it the same as you20:07
*** mtreinish1 has joined #openstack-meeting20:07
ttxsdague: I don't want people to go to the release page on release day and then back the next week and discover additions... We need to consider it shipped at some point20:07
morgansdague: better to be clear20:07
mordredthing is- I imagine that the puppet to deploy mitaka might continue to be updated as people learn things20:07
morgan"this is following a dev cycle"20:07
ttxbut we need a place for things trailing the release20:07
agentlemordred: yeah same here... hm20:07
dhellmannmordred : so will mitaka, as stable updates are made20:07
odyssey4medhellmann ++20:08
mordreddhellmann: right - but those are not feature things20:08
agentledhellmann: ok, so it is a "point in time"20:08
sdaguemordred: possibly like we update stable/mitaka in projects as we learn things20:08
*** jaugustine has quit IRC20:08
dimsa few folks from fuel, puppet have looked at it and were ok with it. so +1 from me. only question i had was around the 2 week time frame. but that seemed ok to them20:08
johnthetubaguyso sdague you make a good point they will probably call it those the "their" release mitaka as well, anyways20:08
sdaguemordred: sometimes they are20:08
morganit just clearly says "this isn't expected to release at the same day 'mitaka' is GA"20:08
ttxmorgan: yes20:08
mordredfor instance, mitaka added the ability late in the cycle to bootstrap keystone not using an admin token20:08
mordredone could imagine the puppet people adding support to the mitaka puppet 3 months later as a new 'feature' for managing mitaka20:09
mtreinish1o/20:09
* mtreinish1 curses verizon20:09
mordredI think trying to shoehorn things like puppet into the same box as things like nova is going to hurt20:09
ttxhas enough votes to pass, so will approve now unless someone objects20:09
dhellmannmordred : are you anticipating some sort of issue with what has been said?20:09
odyssey4memordred each project has the ability to use the semver minor version to indicate 'feature' changes if they so choose20:09
sdaguemordred: we just backported mtu logic to liberty today, stuff happens20:09
*** olaph has left #openstack-meeting20:09
mordreddhellmann: nope. just being verbose20:10
dhellmannmordred : ok20:10
*** mickeys has joined #openstack-meeting20:10
morganmordred: as an alternative, what would the option be, stay "independant" release?20:10
ttxok, so we seem to violently agree, just making a few verbose points20:10
sdagueI think there will be puppet for mitaka20:10
*** aranjan_ has joined #openstack-meeting20:10
sdagueit will be confusing to people if we tell the puppet team they can't say that20:10
morgannot because i think it *needs* to be independant or cycle-trailing20:10
morganjust curious20:10
*** jckasper has quit IRC20:10
*** amitgandhinz has quit IRC20:10
*** pvaneck_ has joined #openstack-meeting20:10
johnthetubaguysdague, I think you are right, else its just too confusing20:10
dhellmannsdague : we're not saying that. "puppet for mitaka" is ok. "puppet in mitaka" is less clear.20:10
ttxpuppet for mitaka sounds good to me20:10
morgani support a clear line "these things follow the cycle, but are part of the cycle"20:10
mordredmorgan: ya. I do not htink it's important for the puppet modules to have a mitaka release of the modules. although I thin kthey can choose to do so if they'dlike20:10
*** jckasper has joined #openstack-meeting20:11
morganregardless of how it's communicated20:11
morganvia a tag... via... and meail20:11
mordredmorgan: ++20:11
* amrith sneaks into a back row seat20:11
morgana comment.. a branch, etc20:11
*** salv-orlando has quit IRC20:11
ttxmordred: we don't force them to follow cycle, they choose to :)20:11
*** aranjan has quit IRC20:11
dimsttx : ++20:11
*** brucet has quit IRC20:11
morganlets try the tag.20:12
ttxI agree that it might make sense for them to be independent, but they want to follow the cycle and have a styable branch per release20:12
sdagueanyway, this seems extra meta :)20:12
morganif it doesn't work, we remove it20:12
*** henrynash has joined #openstack-meeting20:12
morganwe have that superpower20:12
ttxso we just give them a way to express that20:12
sdagueyeh, it was an ask, I don't think it confuses things20:12
johnthetubaguyyeah, the tag still seems like a sound idea, to better express what they do20:12
morganthe puppet, kolla, etc things want it.20:12
morganor seem to like it20:12
ttxbecause currently none of the models fit that case. Doesn't mean we force all deployment stuff to follow that model20:12
morganlets see how it works.20:12
ttxok, approving then20:13
johnthetubaguyyeah, seems worth trying20:13
*** esker has quit IRC20:13
ttxalright done20:13
*** pvaneck has quit IRC20:13
ttx#topic Grant Cross-Project Spec Team Voting in Specs20:13
*** openstack changes topic to "Grant Cross-Project Spec Team Voting in Specs (Meeting topic: tc)"20:13
ttx#link https://review.openstack.org/30624420:13
ttxthingee: want to introduce ?20:13
thingeesure20:13
*** esker has joined #openstack-meeting20:14
thingeein a previous TC meeting I was bringing up the fact that I would like to abandon openstack-specs that inative once communicated with the owner.20:14
thingeethis is no longer a problem anymore :)20:14
thingeebut20:14
*** fawadkhaliq has joined #openstack-meeting20:14
thingeeregardless I wanted to have the openstack cross-project team recognized to do voting on these specs20:15
thingeethat involve the project team they represent.20:15
thingeejeblair requested a formal resolution to be written to capture this20:15
sdagueis there a list of those folks besides in gerrit? Just for reference20:15
*** jckasper has quit IRC20:15
*** jmckind_ has quit IRC20:15
morganthingee: so kindof like the rollcall vote for the TC goverance repo but for the x-project team?20:15
thingeethis is giving the ability to the cross-project team to say whether a spec is good or not for their team, instead of the TC looking over that consensus by those teams and finalizing it in their own vote.20:16
*** jckasper has joined #openstack-meeting20:16
thingeesdague: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons20:16
thingeemorgan: yes20:16
mtreinish1thingee: these liasions are like the others where it's the ptl or a ptl chosen delegate?20:16
thingeemtreinish1: yes see our project team guide http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons20:17
agentlemtreinish1: yes, although is that table pre-populated with PTLs to start thingee ?20:17
*** bbbzhao has quit IRC20:17
*** neelashah has joined #openstack-meeting20:17
bswartzI don't understand what the purpose of the voting would be -- just to register feedback?20:18
*** bbbzhao has joined #openstack-meeting20:18
thingeeagentle: originally yes. This team was formed late last year, email communications were originally made on list and directly to ptls to either serve themselves or delegate.20:18
dimsthingee is there a gerrit group populated from that wiki?20:18
thingeebswartz: so previous TC meetings, discussions were that the project team members themselves should know better if a spec would work for their project. If there is consensus in the community and these teams, why would the TC need to rubber stamp.20:19
*** matrohon has joined #openstack-meeting20:19
thingeedims: not yet20:19
morgani'd like to see it become a formal managed via code review group rather than "populate from the wiki"20:19
morganif that makes sense20:19
thingeemorgan: sounds fine to me20:19
ttxwhat I like about this is that it removed the TC from the approval process -- doesn't prevent us from commenting, but we don't stand in the critical path20:19
* morgan doesn't trust wiki to be authoritative20:19
bswartzso if a majority of liasons vote yes for a CP spec, it gets merged?20:20
johnthetubaguyttx: +120:20
thingeethis also introduces a chair to the group. so I guess ideally that person would be able to update the gerrit group20:20
dimsmorgan : +120:20
agentlebswartz: yes, though there's discussion of instead a percentage rather than an integer20:20
thingeettx: +120:20
morganbswartz: i think the TC still can comment/weigh in (as we should)20:20
edleafemorgan: +120:20
thingeemorgan: +120:20
morganand should be able to vote (it is our job to do so and look at the benefit/health of the community/projects)20:20
ttxthe TC can still comment and participate. We can also be appealed to20:20
agentlesince not all cross-project specs affect all projects, could we envision a percent?20:20
*** zz_dimtruck is now known as dimtruck20:20
ttxin case people think the cross-project group is not operating correctly20:21
*** mickeys has quit IRC20:21
morganbut i don't see an issue with the cross-project team having more ownership20:21
thingeeagentle: it's only the involved projects. last paragraph should talk about that20:21
ttxok, another violent agreement ?20:21
morganin fact.. i like it.20:21
morganmore ownership20:21
mesteryttx: Violent agreement is the best kind of agreement :)20:21
*** mickeys has joined #openstack-meeting20:21
morganmestery: ++20:21
thingeeone question though ttx, unanimous decision or majority?20:21
thingeethat was a question some people had in the comments20:22
*** fawadkhaliq has quit IRC20:22
ttxthingee: current style is to rubberstamp consensus, so the chair determines if consensus is reached20:22
anteayaunanimous could really hamstring you20:22
agentlethingee: ok20:22
ttxso current process is unanimous20:22
dimsthingee : i see a few comments there...20:22
ttxdoesn't mean we can't change it20:22
*** fawadkhaliq has joined #openstack-meeting20:22
ttxbut20:22
sdagueI think we should error on the side of asking for concensus20:23
* morgan commented on the review.20:23
morgansdague: ++20:23
*** tonytan_brb has joined #openstack-meeting20:23
sdagueand if we feel stuck, well the TC can always decide a thing20:23
*** dimtruck is now known as zz_dimtruck20:23
ttxtwo ways of solving that -- you want agreement on all affected projects. If a project doesn't want that change, you could try to find common ground and worst case scenario apply the change to every other project and require consensus there20:23
gordcdo you need consensus/unanimous? if project 1,2,3 like an idea, and project 4,5,6,7 don't, do you want to/can you block all the projects that said 'yay'?20:24
*** brucet has joined #openstack-meeting20:24
*** tonytan4ever has quit IRC20:24
sdagueor just have it come forward saying "the follow 2 projects object" but we think it's really important. And TC can say, yes, it's important we all do this thing.20:24
morgansdague: ++20:24
johnthetubaguyseems like the cross project team basically owns deciding the best way to build consensus, and the appeal to the TC if no one can decide seems like a good safety valve20:24
dansmiththat should really be a very unlikely case though right?20:25
thingeesdague: seems like as ttx suggested the chair can determine that.20:25
fungialso is is a tacit approval/lazy consensus unanimity?20:25
morgandansmith: i hope it's unlikely20:25
ttxgordc: so imagine a spec that affects ABCD. D disagrees. You should try to fix the disagreement. If that can't get done, you should limit the spec to ABC and require consensus there20:25
sdaguegordc: I think the point is at the CPL level we're staying you all have the authority to come to concensus20:25
sdagueand that's cool20:25
thingeeif the chair is unsure, could ask the tc to weigh in20:25
dansmithwhat sort of situation would need decree from the TC realistically?20:25
morganif it is happening a lot, we have a difunctional team20:25
dansmithttx: +120:25
johnthetubaguythingee: +120:25
sdaguedansmith: right, I'm just trying to say we lazy evaluate the conflict case20:25
mesteryttx: +120:25
*** pradk has joined #openstack-meeting20:25
gordcttx: ack. makes sense.20:25
mordreddansmith: so far we have not forced the issue on any of the times when a project has unilaterally just not done something20:25
sdagueknowing we have a backstop if we need one20:25
*** mickeys has quit IRC20:25
ttxmorgan: right, if a team refuses to play ball all the time it's grounds for removal, not to force them to merge that code20:26
mordredI think the only thing the TC has ever _forced_ over objections was the move to gerrit20:26
morganttx: exactly.20:26
mordredttx: ++20:26
dansmithyeah20:26
mordred(and that as the ppb, not the TC)20:26
*** nadya has quit IRC20:26
bswartzthis sounds like we're back to CP PTL determines if specs merge or not and the voting is irreleveant (or merely a feedback mechanism)20:26
ttxwe can't force a project to accept code it doesn't want. That would not work20:26
agentlemordred: ah, memories20:26
morganbswartz: i expect it to work like the TC tbh. if it isn't and the CP PTL is running wild, the TC can also step in.20:27
thingeeso I guess I'd like to amend to the spec, if there is disagreement, the chair could merge it if he/she feels there are majority agreeing to it.20:27
dimsmorgan : lol20:27
* ttx has a big board with columns for each project team. Marks an X every time someone is being naughty and in the end if they get 10 crosses they don't get a present at Christmas20:27
thingeebut if the chair can't make decision, could ask the tc to weigh in20:27
*** doug-fish has quit IRC20:27
morgandims: ;)20:27
fungibut also cp specs often don't apply to many (or even a majority) of projects, so asking for consensus across projects which don't have a stake in a particular spec could be problematic. but as long as discretion lies with the chair i suppose the definition of consensus can be considered flexible20:27
anteayattx: ha ha ha20:27
* johnthetubaguy thinks ttx might not be kidding20:28
morganfungi: ++20:28
dansmiththingee: I guess my point is.. do we really need to say that?20:28
dimsjohnthetubaguy : haha20:28
ttxjohnthetubaguy: some projects failed to push their session descriptions in time. I added 2 crosses.20:28
mesteryfungi: Right, I assume the definition of consensus is flexible20:28
morganconsensus is "affected projects"20:28
thingeedansmith: probably not20:28
* johnthetubaguy nods at ttx20:28
morganin this context20:28
thingeedansmith: right not it says unanimous decision.20:28
johnthetubaguy"Assuming there is consensus with those that are involved" seems good enough20:29
dansmithjohnthetubaguy: ++20:29
ttxWe have majority votes on the proposal. Any opposition ?20:29
morganjohnthetubaguy: ++20:29
ttxyep agree it's enough20:29
sdaguejohnthetubaguy: agreed20:29
anteayaI'd substitute unanimous with consensus, personally20:29
morgananteaya: so you'd advocate for "unnanimous" vs "consensus"20:30
thingeettx: alright so I'll follow another update with johnthetubaguy's suggestion20:30
ttxI think it captrues the intent20:30
morganit says consensnus now.20:30
ttxthingee: that's the current wording no ?20:30
* morgan types badly today20:30
dansmithconsensus is better, IMHO20:30
johnthetubaguyso I got the lines mixed up20:30
morgandansmith: i agree20:30
dansmithunanimous sounds like a jury convicting someone20:30
johnthetubaguyline41 and 4620:30
morgandansmith: GUILTY!20:30
anteayamorgan: I advocate for consensous20:30
morgandansmith: i mean...20:30
ttxcurrent wording already says "Assuming there is consensus with those that are involved"20:30
mtreinish1dansmith: only if there are 12 people20:30
*** zz_dimtruck is now known as dimtruck20:30
*** brucet has quit IRC20:31
morgananteaya: it already says consensus in one loine, but unanimous in another20:31
thingeettx: "in the cases where unanimous decision cannot be ..."20:31
johnthetubaguyyeah, I cut and paste that, I guess line 46 is the sticking point20:31
morganso.. thingee please make the consensus/unanimous lines agree20:31
anteayamorgan: I'd remove unanimous20:31
ttxthingee yourcall, happy to pass it as is20:31
ttxthingee: if you cal edit that in-meeting, we can revote20:31
* thingee clicks the edit button20:31
cdentI think something we need to be conscious of is the power for some of the larger projects (cough cough nova) to wield an implicit veto in cross project changes.20:31
*** rderose has quit IRC20:32
*** armax has joined #openstack-meeting20:32
cdentThat's bad.20:32
thingeedone20:32
dansmithno, because we'd just be not part of the concerned parties right?20:32
ttxdansmith: exactly20:32
thingeeplease vote again https://review.openstack.org/#/c/306244/20:32
mesteryRight, if nova opts out, they['re note part of the consensus20:32
mesteryAnd ttx can mark them on his list20:32
ttxcheck20:32
dansmithyeah, let's not make this more combative :)20:32
* cdent sighs20:32
cdentWe've already seen this happen.20:32
* anteaya frames dansmith's comment20:33
dansmithanteaya: that one is free20:33
morganthingee: thanks for the fix.20:33
ttxone more20:33
ttxplease reapply votes20:34
sdaguettx: should be good now20:34
ttxindeed20:34
morgancdent: lets see if we have progressed and have less "veto" happening, if it starts being a problem, we should absolutely revisit20:34
ttxapproved20:34
anteayadansmith: thank you20:34
morgancdent: i am well aware it has happened.20:34
rocky_gthanks, thingee20:34
*** delattec has quit IRC20:34
cdentThanks morgan20:34
ttx#topic Joint BoD/TC meeting agenda20:35
morgancdent: but i think what we have now is solid and the right starting place.-20:35
*** openstack changes topic to "Joint BoD/TC meeting agenda (Meeting topic: tc)"20:35
dimsmorgan : cdent : agree20:35
ttxmorgan: agree20:35
ttxI pushed our ideas to Alan and that resulted in the following agenda for our Sunday meeting:20:35
ttx#link https://etherpad.openstack.org/p/6PuSKyUOHk20:35
ttxThere may still be time to sneak another topic if you feel something is urgently missing20:35
ttxOtherwise it's easy to add a subpoint to one of the catch-all topics like "Newton tension points"20:35
*** jungleboyj has quit IRC20:36
*** doug-fish has joined #openstack-meeting20:36
morganseems reasonable20:36
ttxthe board members didn't exactly add much20:36
*** doug-fish has quit IRC20:36
ttxbut then I can do with a simple agenda20:36
morganhm..20:36
mesteryPlenty of sheds to paint in that agenda ttx :)20:36
*** doug-fish has joined #openstack-meeting20:36
ttxmestery: good then20:36
morganthere was something i had someone ask me about... i don't remember what it was.20:36
*** mickeys has joined #openstack-meeting20:36
mesteryttx: exactly :)20:36
*** vhoward has quit IRC20:37
* morgan will try and remember and ping TTX20:37
anteayadid I miss the discussion about why the product work group has 30 minutes in the board/tc slot?20:37
*** unicell has quit IRC20:37
jrollttx: the container/vm thing, should bare metal be included in that?20:37
rocky_ganteaya, roadmap, etc20:37
ttxanteaya: that was an item added by Alan (the only one)20:37
*** unicell has joined #openstack-meeting20:37
anteayattx: okay thank you20:38
morganjroll: i think that was part of the original convo20:38
ttxjroll: the more the merrier20:38
morganjroll: i'd like to see it there.20:38
jrollttx: it's really "does the nova api fit for different types of compute resources", right?20:38
jrollheh20:38
jrollagree20:38
dimsjroll : yep20:38
ttxjroll: added20:38
jrollthank you ttx20:38
mordredjroll: well, I think  "does the nova api fit for different types of compute resources" is a possible outcome discussion for us20:39
ttx#topic Open discussion20:39
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:39
rocky_ganteaya, hmm.  thanks for pointing out the prodwg thing.  I would have missed it20:39
*** dimtruck is now known as zz_dimtruck20:39
anteayattx we often don't get fully through the whole board/tc agenda, can the product work group go last on this agenda?20:39
jrollmordred: fair enough20:39
anteayarocky_g: sure20:39
ttxanteaya: I'll make that suggestion20:39
anteayattx: thank you20:39
ttx* Video with tips for design summit moderators20:39
ttxWe shot & edited the video last week, then sent it to PTLs and session moderators20:40
ttx#link https://youtu.be/M4cDyM2s2bc20:40
dhellmannnice work!20:40
ttxyay 247 views we are YouTube stars20:40
dimsLOL20:40
* dhellmann goes to watch it again20:40
anteayattx: them them about your painting, I thought it was a mythical beast20:40
*** dprince has quit IRC20:40
ttxhalf of those must be me and my sound checks20:40
*** Sukhdev has joined #openstack-meeting20:40
*** armax_ has joined #openstack-meeting20:40
ttx* Update reference list for Neutron projects (https://review.openstack.org/303026)20:41
*** banix has quit IRC20:41
* docaedo loved that video - great work everyone involved :)20:41
ttxI wanted to draw attention to this review, which will be approved soon under our lazy approval rule unless someone objects20:41
ttxlooks like adding it to agenda gave it some attention20:41
ttxIt's a significant policy chnage in Neutron, so making sure everyone is aware of it20:41
ttxyay merge conflict20:41
*** zz_dimtruck is now known as dimtruck20:42
morganwoot merge conflicts!20:42
agentlettx: did he get an understanding of what it means for the release? (What does it mean?)20:42
*** armax has quit IRC20:42
*** armax_ is now known as armax20:42
dhellmannmestery : is the intent for those teams to ask for official status on their own?20:42
*** ober37 has left #openstack-meeting20:42
ttxdhellmann: they would likely not get it as non-testable using open source tools in ci20:42
thingeeI've been moderating summit sessions wrong this whole time...20:43
mesterydhellmann: You'd have to ask armax, it's out of Neutron's hands once that merges20:43
mtreinish1dhellmann: could they be, the list was all proprietary stuff20:43
dhellmannright, that's why I was asking20:43
morganthingee: amazing!20:43
mesteryBut I imagine many of them may try (and likely fail) to apply20:43
mtreinish1*for talking to proprietary stuff20:43
ttxagentle: what it means for the release ?20:43
agentlettx: is this list for a particular release?20:43
*** mickeys has quit IRC20:43
ttxagentle: they become unofficial, so they are not part of "the release"20:43
agentlettx: were they part of mitaka?20:43
mesteryRight, once that merges, they are not openstack projects20:43
mesteryJust projects using the openstack infrastructure20:44
ttxagentle: they were20:44
agentleconsidered part of mitaka, ok20:44
dimswhich means release team is not on the hook to shepherd releases20:44
*** mickeys has joined #openstack-meeting20:44
dhellmannexcept the ones using release:independent20:44
morganhmm.20:44
ttx(which was most of them)20:44
dhellmann(those weren't part of mitaka, even though they were official during the mitaka cycle)20:44
ttxagentle: most of them weren't in mitaka20:44
ttxmost/all20:44
*** salv-orlando has joined #openstack-meeting20:45
morgani think this is just reflecting the reality20:45
mesteryI'd say all20:45
ttxso it actually won't change much20:45
morganbased upon what ttx and mestery just said20:45
mesteryNone of them had a mitaka release20:45
morganso.. procedural mostly20:45
mesteryThey were all release:independent20:45
ttxwell, welcome clarification20:45
ttxneutron core team couldn't vouch for them20:45
agentleok yeah20:45
*** mickeys has quit IRC20:45
*** adahms has joined #openstack-meeting20:45
agentlewe can put info in a blog post20:45
*** mickeys has joined #openstack-meeting20:46
ttxI agree that if they were in mitaka the move would be more... significant20:46
ttxBut we need to get ready for that20:46
ttx(cleanups of the tent)20:46
mesteryConsider this a litmus test of sorts20:46
morganif they had been in mitaka, i would have pushed this convo to the tent cleanup20:46
mesteryAlthough much of the fury over this change has already happened20:46
ttxthere will be things that were released in mitaka and will get thrown out in newton20:46
morganbut since they weren't i am not as concerned.20:46
mesterymorgan: They were not released in mitaka, but their contributors got ATC, so halfway in mitaka?20:46
mesteryttx: ++20:47
morganmestery: leaving the ATC bit off the table.20:47
mesteryyeah20:47
ttxmorgan: thanks :)20:47
amrithttx, is the BOD/TC meeting open to other attendees? I'd like to attend, especially the last line item on the agenda.20:47
ttxamrith: yes20:47
amriththx ttx20:47
ttxamrith: got the location/date ?20:47
amrithno, am looking for it20:48
amrithit is sundday20:48
amrithi'll be there20:48
rocky_gamrith, the whole BOD meeting, not just the joint one with TC20:48
ttxexcept the private session20:48
amrithttx, I don't have location/time20:48
*** baoli has joined #openstack-meeting20:48
rocky_gttx, oops.  Yeah.  Thanks.  Lunch.20:48
* armax scrolls back20:48
ttxamrith: JW Marriott, Level 3, Salons G/H20:48
anteayaamrith: https://wiki.openstack.org/wiki/Governance/Foundation/24Apr2016BoardMeeting#Joint_Board.2FTC.2FUser_Committee_Meeting20:48
ttx2:30pm Joint TC / UC Meeting20:48
ttxon Sunday20:49
amriththanks ttx, will be there.20:49
ttxAnything else, anyone ?20:49
*** brucet has joined #openstack-meeting20:49
dimsthere's remote access too - http://lists.openstack.org/pipermail/foundation/2016-April/002325.html20:49
ttxHappy to see you all next week20:50
morganyay summit!20:50
dhellmann++ we should get together more often than every 6 months20:51
sdagueis there going to be a TC gathering?20:51
amrithsafe travels everyone20:51
morgandhellmann: of course!20:51
sdagueeven like the informalish bar thing last time, it was nice to happen20:51
agentleis there a second TC-only dinner this time 'round?20:51
ttxI'll be at the WOO event we can do something from there20:51
ttxagentle: no TC-dinner20:51
agentlettx: that works20:51
agentlettx: informal is good20:51
agentlewe can all get the meat sweats together20:52
dimssdague : ++ that would be good20:52
ttxI'll be at the Saturday Board/staff/TC dinner too, but I think a few members will miss that20:52
mtreinish1agentle: ++20:52
sdagueyeh, I won't be there20:52
dhellmannyeah, I'm not coming in until sunday morning20:52
* morgan will be around for Sat.20:52
mtreinish1ttx: yeah, I'll be on a plane when that's scheduled20:52
johnthetubaguyyeah, I fly in late ish saturday sadly20:52
*** mrmartin has quit IRC20:53
*** toddjohn_ has quit IRC20:53
mesterySunday morning for me too20:53
*** mickeys has quit IRC20:53
*** toddjohn_ has joined #openstack-meeting20:53
ttxI'll see some of you Saturday evening then, and the others at the Board/TC meeting and at the WOO event and whatever comes next20:53
*** mickeys has joined #openstack-meeting20:53
*** gordc has left #openstack-meeting20:53
*** tristanC_ is now known as tristanC20:54
*** haleyb has joined #openstack-meeting20:54
dimssafe travels everyone20:54
*** andymaier has quit IRC20:54
ttxalright, time to close this I guess20:55
johnthetubaguyyeah, +1 to that, safe travels everyone20:55
ttxsee you in a few days20:55
* edleafe is driving up Sat afternoon20:55
ttx#endmeeting20:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:55
openstackMeeting ended Tue Apr 19 20:55:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-04-19-20.02.html20:55
mesterySee you all next week and safe travels!20:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-04-19-20.02.txt20:55
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-04-19-20.02.log.html20:55
* morgan finishes tuesday meetings.20:55
*** toddjoh__ has joined #openstack-meeting20:55
agentlemorgan: lucky20:55
morganagentle: hey, i'm unemployed atm :)20:56
morganagentle: i have a lot less to do than those of you who are gainfully employed ^_^. very relaxing20:56
agentlemorgan: oh yeah -- then finish with style!20:56
*** brucet has quit IRC20:56
*** brucet has joined #openstack-meeting20:57
*** toddjohn_ has quit IRC20:57
*** delattec has joined #openstack-meeting20:57
*** mickeys has quit IRC20:58
*** haleyb has quit IRC20:59
*** toddjoh__ has quit IRC21:00
bkero"funemployed"21:01
*** sridharg has quit IRC21:01
*** rfolco has quit IRC21:01
*** jmckind has joined #openstack-meeting21:01
*** mbound has joined #openstack-meeting21:01
*** dims_ has joined #openstack-meeting21:02
*** dims has quit IRC21:02
*** xarses has joined #openstack-meeting21:03
*** brucet has quit IRC21:03
*** rossella_s has quit IRC21:03
*** rossella_s has joined #openstack-meeting21:04
*** amrith is now known as _amrith_21:05
*** psilvad has quit IRC21:05
*** aysyd has quit IRC21:05
*** jmckind has quit IRC21:06
*** baoli_ has joined #openstack-meeting21:06
*** lblanchard has quit IRC21:06
*** rtheis has quit IRC21:07
*** gyee has joined #openstack-meeting21:07
*** baoli__ has joined #openstack-meeting21:08
*** dneary has quit IRC21:08
*** cdent has quit IRC21:08
*** thorst_ has quit IRC21:08
*** baoli has quit IRC21:10
*** Sukhdev has quit IRC21:11
*** brucet has joined #openstack-meeting21:11
*** baoli__ has quit IRC21:11
*** rocky_g has quit IRC21:11
*** baoli_ has quit IRC21:11
*** baoli has joined #openstack-meeting21:12
*** singhj has quit IRC21:12
*** neiljerram has quit IRC21:13
*** haomaiwang has quit IRC21:13
*** singhj has joined #openstack-meeting21:14
*** xarses has left #openstack-meeting21:14
*** brucet has quit IRC21:17
*** jdurgin has quit IRC21:17
*** matrohon has quit IRC21:17
*** fawadkhaliq has quit IRC21:23
*** andymaier has joined #openstack-meeting21:24
*** fawadkhaliq has joined #openstack-meeting21:24
*** neelashah has quit IRC21:24
*** cody-somerville has joined #openstack-meeting21:25
*** dmorita has quit IRC21:27
*** thorst_ has joined #openstack-meeting21:28
*** dmorita has joined #openstack-meeting21:28
*** fawadkhaliq has quit IRC21:28
*** brucet has joined #openstack-meeting21:29
*** tonytan_brb is now known as tonytan4ever21:29
*** sdake_ has joined #openstack-meeting21:30
*** dmorita has quit IRC21:31
*** thorst_ has quit IRC21:31
*** thorst_ has joined #openstack-meeting21:31
*** amitgandhinz has joined #openstack-meeting21:32
*** amitgandhinz has quit IRC21:32
*** sdake has quit IRC21:33
*** brucet has quit IRC21:34
*** fzdarsky has quit IRC21:36
*** cdub has joined #openstack-meeting21:41
*** brucet has joined #openstack-meeting21:43
*** agentle has quit IRC21:44
*** dmorita has joined #openstack-meeting21:49
*** brucet has quit IRC21:49
*** toddjohn_ has joined #openstack-meeting21:50
*** _amrith_ is now known as amrith21:50
*** dbecker has quit IRC21:50
*** mickeys has joined #openstack-meeting21:50
*** cloudtrainme has quit IRC21:51
*** eric_lopez has joined #openstack-meeting21:51
*** adahms has quit IRC21:52
*** mriedem has quit IRC21:52
*** busterswt has quit IRC21:52
*** singhj has quit IRC21:53
*** vgridnev has quit IRC21:53
*** elo has quit IRC21:54
*** toddjohn_ has quit IRC21:54
*** thorst_ has quit IRC21:56
*** dbecker has joined #openstack-meeting21:57
*** mtreinish1 has quit IRC21:58
*** Sukhdev has joined #openstack-meeting21:58
*** gokrokve has quit IRC21:59
*** amrith is now known as _amrith_22:00
*** xyang1 has quit IRC22:01
*** mickeys has quit IRC22:01
*** tonytan4ever_1 has joined #openstack-meeting22:02
*** mickeys has joined #openstack-meeting22:02
tonytan4ever_1ls22:02
*** sigmavirus24 is now known as sigmavirus24_awa22:02
*** Sukhdev has quit IRC22:03
*** Sukhdev has joined #openstack-meeting22:04
*** moiz has quit IRC22:04
*** bobh has quit IRC22:05
*** zzxwill__ has joined #openstack-meeting22:05
*** mickeys has quit IRC22:06
*** rderose has joined #openstack-meeting22:06
*** karthikp has joined #openstack-meeting22:06
*** tonytan4ever has quit IRC22:07
*** tonytan4ever has joined #openstack-meeting22:08
*** lblanchard has joined #openstack-meeting22:11
*** singhj has joined #openstack-meeting22:11
*** spotz is now known as spotz_zzz22:12
*** tonytan4ever has quit IRC22:12
*** brucet has joined #openstack-meeting22:12
*** tonytan4ever has joined #openstack-meeting22:12
*** tonytan4ever has quit IRC22:12
*** Adri2000 has quit IRC22:13
*** fawadkhaliq has joined #openstack-meeting22:14
*** singhj has quit IRC22:15
*** mtreinish has joined #openstack-meeting22:16
*** ayoung has quit IRC22:16
*** Sukhdev has quit IRC22:16
*** alex_xu has quit IRC22:16
*** Sukhdev has joined #openstack-meeting22:17
*** mickeys has joined #openstack-meeting22:18
*** timcline has quit IRC22:18
*** brucet has quit IRC22:18
*** alex_xu has joined #openstack-meeting22:18
*** banix has joined #openstack-meeting22:18
*** brucet has joined #openstack-meeting22:18
*** adahms has joined #openstack-meeting22:20
*** mickeys has quit IRC22:20
*** intr1nsic has quit IRC22:20
*** mickeys has joined #openstack-meeting22:20
*** ianw has quit IRC22:22
*** enriquetaso has quit IRC22:22
*** tonytan4ever_1 has quit IRC22:22
*** piet has quit IRC22:23
*** galstrom is now known as galstrom_zzz22:24
*** ianw has joined #openstack-meeting22:24
*** adiantum has quit IRC22:25
*** tonytan4ever has joined #openstack-meeting22:25
*** salv-orlando has quit IRC22:26
*** intr1nsic has joined #openstack-meeting22:26
*** piet has joined #openstack-meeting22:26
*** sdake_ is now known as sake22:26
*** tonytan4ever has quit IRC22:27
*** brucet has quit IRC22:30
*** brucet has joined #openstack-meeting22:30
*** thorst has joined #openstack-meeting22:30
*** jckasper has quit IRC22:32
*** IlyaG has joined #openstack-meeting22:32
*** IlyaG has quit IRC22:32
*** jckasper has joined #openstack-meeting22:32
*** jckasper has quit IRC22:33
*** jckasper has joined #openstack-meeting22:34
*** zzxwill__ has quit IRC22:35
*** rfolco has joined #openstack-meeting22:35
*** pfallenop has quit IRC22:37
*** ianw has quit IRC22:38
*** asettle has joined #openstack-meeting22:39
*** rderose has quit IRC22:40
*** mbound has quit IRC22:43
*** unicell has quit IRC22:43
*** MaxPC has quit IRC22:44
*** Leo_ has joined #openstack-meeting22:45
*** Leom has quit IRC22:45
*** persia has quit IRC22:46
*** mickeys has quit IRC22:50
*** mickeys has joined #openstack-meeting22:51
*** tellesnobrega is now known as tellesnobrega_af22:52
*** rbak has quit IRC22:52
*** mriedem has joined #openstack-meeting22:54
*** mageshgv has quit IRC22:54
*** mickeys has quit IRC22:55
*** unicell has joined #openstack-meeting22:56
*** haleyb has joined #openstack-meeting22:57
*** eil397 has quit IRC22:57
*** thorst has quit IRC22:58
*** rderose has joined #openstack-meeting22:58
*** tellesnobrega_af is now known as tellesnobrega22:59
*** haleyb has quit IRC23:02
*** toddjohn_ has joined #openstack-meeting23:02
*** bobh has joined #openstack-meeting23:02
*** claudiub has quit IRC23:04
*** persia has joined #openstack-meeting23:04
*** alex_xu has quit IRC23:05
*** bobh has quit IRC23:05
*** alex_xu has joined #openstack-meeting23:06
*** andymaier has quit IRC23:07
*** sdague has quit IRC23:07
*** mageshgv has joined #openstack-meeting23:07
*** Leo_ has quit IRC23:08
*** Qiming has joined #openstack-meeting23:10
*** dimtruck is now known as zz_dimtruck23:13
*** absubram has quit IRC23:13
*** ianw_ has joined #openstack-meeting23:13
*** david-lyle_ has joined #openstack-meeting23:14
*** david-lyle has quit IRC23:14
*** toddjohn_ has quit IRC23:17
*** fawadkhaliq has quit IRC23:19
*** Sukhdev has quit IRC23:19
*** fawadkhaliq has joined #openstack-meeting23:19
*** brucet has quit IRC23:20
*** Sukhdev has joined #openstack-meeting23:21
*** asingh has quit IRC23:22
*** sake is now known as sdake23:22
*** Adri2000 has joined #openstack-meeting23:22
*** fawadkhaliq has quit IRC23:24
*** Qiming has quit IRC23:25
*** brucet has joined #openstack-meeting23:25
*** asettle has quit IRC23:26
*** karthikp has quit IRC23:27
*** asettle has joined #openstack-meeting23:28
*** brucet has quit IRC23:29
*** Swami has quit IRC23:33
*** bobh has joined #openstack-meeting23:33
*** elo has joined #openstack-meeting23:39
*** eric_lopez has quit IRC23:39
*** bobh has quit IRC23:40
*** cburgess has quit IRC23:40
*** tochi has joined #openstack-meeting23:41
*** neelashah has joined #openstack-meeting23:42
*** Clint has quit IRC23:42
*** katomo has joined #openstack-meeting23:42
*** pleia2 has quit IRC23:43
*** pleia2 has joined #openstack-meeting23:43
*** Clint has joined #openstack-meeting23:43
*** Clint has quit IRC23:43
*** Clint has joined #openstack-meeting23:43
*** wbhuber_ has quit IRC23:45
*** HenryG has quit IRC23:45
*** cburgess has joined #openstack-meeting23:45
*** niska has quit IRC23:45
*** katomo has left #openstack-meeting23:46
*** trey has quit IRC23:46
*** wbhuber has joined #openstack-meeting23:47
*** niska has joined #openstack-meeting23:48
*** HenryG has joined #openstack-meeting23:48
*** Leo_ has joined #openstack-meeting23:50
*** trey has joined #openstack-meeting23:51
*** Leo_ has quit IRC23:55
*** tellesnobrega is now known as tellesnobrega_af23:56
*** karthikp has joined #openstack-meeting23:56
*** david-lyle_ is now known as david-lyle23:57
*** thorst has joined #openstack-meeting23:59

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