Thursday, 2017-12-21

*** lukebrowning has joined #openstack-tc00:49
*** lukebrowning has quit IRC00:54
*** lukebrowning has joined #openstack-tc00:55
*** marst has quit IRC00:56
*** lukebrowning has quit IRC01:00
*** lukebrowning has joined #openstack-tc01:01
*** kumarmn has joined #openstack-tc01:04
*** lukebrowning has quit IRC01:07
*** lukebrowning has joined #openstack-tc01:08
*** kumarmn has quit IRC01:09
*** lukebrowning has quit IRC01:13
*** lukebrowning has joined #openstack-tc01:14
*** lukebrowning has quit IRC01:19
*** openstackgerrit has joined #openstack-tc01:20
openstackgerritDai Dang Van proposed openstack/governance master: Update policy goal for trove  https://review.openstack.org/52944701:20
*** lukebrowning has joined #openstack-tc01:22
*** kumarmn has joined #openstack-tc01:22
*** lukebrowning has quit IRC01:27
*** liujiong has joined #openstack-tc01:28
*** kumarmn has quit IRC01:36
*** kumarmn has joined #openstack-tc01:38
*** lukebrowning has joined #openstack-tc01:57
*** lukebrowning has quit IRC02:02
*** gcb has joined #openstack-tc02:03
*** lukebrowning has joined #openstack-tc02:03
*** harlowja has quit IRC02:07
*** dhellmann has quit IRC02:07
*** dansmith has quit IRC02:07
*** evrardjp has quit IRC02:07
*** kumarmn has quit IRC02:08
*** lukebrowning has quit IRC02:08
*** dansmith has joined #openstack-tc02:08
*** dansmith is now known as Guest9968002:08
*** dhellmann has joined #openstack-tc02:08
*** evrardjp has joined #openstack-tc02:09
*** mriedem has quit IRC02:10
*** lukebrowning has joined #openstack-tc02:34
*** lukebrowning has quit IRC02:38
*** lukebrowning has joined #openstack-tc02:40
*** lukebrowning has quit IRC02:45
*** lukebrowning has joined #openstack-tc02:46
*** lukebrowning has quit IRC02:51
*** lukebrowning has joined #openstack-tc02:57
*** lukebrowning has quit IRC03:02
*** lukebrowning has joined #openstack-tc03:03
*** lukebrowning has quit IRC03:08
*** lukebrowning has joined #openstack-tc03:10
*** lukebrowning has quit IRC03:14
*** lukebrowning has joined #openstack-tc03:16
*** lukebrowning has quit IRC03:21
*** lukebrowning has joined #openstack-tc03:23
*** kumarmn has joined #openstack-tc03:28
*** lukebrowning has quit IRC03:28
*** lukebrowning has joined #openstack-tc03:30
*** lukebrowning has quit IRC03:35
*** liujiong has quit IRC03:35
*** lukebrowning has joined #openstack-tc03:36
*** liujiong has joined #openstack-tc03:36
*** kumarmn has quit IRC03:37
*** kumarmn has joined #openstack-tc03:38
*** liujiong has quit IRC03:41
*** liujiong has joined #openstack-tc03:41
*** lukebrowning has quit IRC03:41
*** lukebrowning has joined #openstack-tc03:42
*** kumarmn has quit IRC03:43
*** lukebrowning has quit IRC03:47
*** lukebrowning has joined #openstack-tc03:49
*** kumarmn has joined #openstack-tc03:50
*** lukebrowning has quit IRC03:53
*** lukebrowning has joined #openstack-tc03:55
*** kumarmn has quit IRC03:58
*** kumarmn has joined #openstack-tc03:58
*** kumarmn has quit IRC03:59
*** lukebrowning has quit IRC04:00
*** lukebrowning has joined #openstack-tc04:01
*** lukebrowning has quit IRC04:06
*** lukebrowning has joined #openstack-tc04:07
*** lukebrowning has quit IRC04:13
*** haken_gra696 has joined #openstack-tc04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEnhlwev: mordred amrith johnthetubaguy alex_xu david-lyle tdasilva dirk zaneb mnaser dmsimard dims evrard04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEnsunzc: mordred notmyname smcginnis dims TheJulia dmsimard evrar04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODElukjreplwn: jungleboyj robcresswell med_ per04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEnhjitrld: thingee lbragstad mordred gcb mgagne openstackstatus tdasilva SamYaple med_ mtreinish fdegir alex_xu ian04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODExxxlmirfx: openstack TheJulia fdegir thingee mtreinish04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEbhmbdv: mgagne ianw_pto tdasilva johnthetubaguy pabelanger robcresswell openstackgerrit persia tonyb amr04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEajlci: dirk mordred dhellmann tonyb med_ TheJulia diablo_rojo smcginnis pa04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEwwyxmub: Dunca04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEzdfht: diablo_rojo johnt04:17
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEvskfgalay: notmyname smc04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEsjqgc: david-lyle dmsimard notmyname robcresswell purplerbot joh04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEuflgvjpx: mordred mnaser persia knikolla tdasilva dims david-lyle robcresswell mgagne openstackgerrit med_ Emilien04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODErwktwox: dhellmann mwhahaha amrith tristanC tdasilva openstackstatus ianw_pto mnaser johnthetubaguy mtreinish evra04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEcsxylf: dmsima04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEokjuva: dims tonyb mordred TheJulia jroll knikolla SamYaple notm04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEpujff: alex_xu openstackstatus dia04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODElgldoxtlct: dirk Emilien04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEzkczhx: med_ alex_xu flwang fungi openstack lbragstad evrardjp smcginnis zaneb david04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEahfjigep: amrith dtantsur|afk jroll zaneb mgagne tristanC med_ TheJulia johnsom evra04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEgqbqq: evrardjp Guest99680 dhellmann david-l04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEimwuq: johnsom lbragstad flwang dtantsur|afk openstackstatus openstackgerrit dirk zaneb fungi mgagne persia med_ m04:18
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEgrhvdelnu: robcresswell TheJulia mtreinish thingee fdegir tristanC gcb jun04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEpwjpmrryja: liujiong jungleboyj fl04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEsfderq: johnthetubaguy fungi kniko04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEgcjmlyooqb: mo04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEtvpti: persia tdasilva openstack DuncanT flwang johnsom diablo_rojo dirk TheJulia fdegir david-lyle med_ knikolla04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODElbcjat: knikolla mgagne flwang johnsom dims mnaser persia dirk EmilienM pu04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEchjoedrah: purplerbot tristanC dav04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEqqicp: alex_xu liujiong jroll jungleboyj thingee notmyname mnaser openstackgerrit ro04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEovwtn: pabelanger dims liujiong gcb tonyb fungi purple04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEvljhwiylu: david-lyle dmsimard med_ jroll tdasilva gcb dirk alex_xu zaneb johnthetubaguy fdegi04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEflait: pabelan04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEbghduwrmp: fungi mordred openstackgerrit jungleboyj jr04:19
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEvizaeafb: evrardjp DuncanT knikolla jroll lbragstad tdasilva dtantsur|afk amrith ope04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEyppwezxkqi: johnthetubaguy TheJulia persia jungleboyj thingee EmilienM pabelanger tdasilva rob04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEirlafzn: SamYaple alex_xu Guest99680 flwang knikolla j04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODElygopzf: Guest99680 ianw_pto thingee evrardjp smcginnis jungleboyj fdegir mwhahaha jroll pabelanger dmsi04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEmjkidhzw: openstackgerrit liujiong ianw_pto gcb mnaser tdasilva dmsimard evrardjp fdegir zaneb flwang dhellmann pe04:20
*** dax has joined #openstack-tc04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODEwbkffsc: mgagn04:20
haken_gra696▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ https://beta.companieshouse.gov.uk/company/10308021/filing-history christel sold freenode to Private Internet Access Andrew Lee WHO ALSO OWNS SNOONET AND IS MOVING FREENODE TO THAT SERVER (NEXT MONTH) AND CLOSING DOWN OPEN SOURCE ROOMS PLEASE COMPLAIN IN CHAN FREENODElkvdfnksqo: fungi robcresswell Gue04:20
*** haken_gra696 has quit IRC04:20
*** dax has left #openstack-tc04:31
*** lukebrowning has joined #openstack-tc04:40
*** lukebrowning has quit IRC04:45
*** lukebrowning has joined #openstack-tc04:46
*** lukebrowning has quit IRC04:51
*** lukebrowning has joined #openstack-tc04:52
*** lukebrowning has quit IRC04:57
*** lukebrowning has joined #openstack-tc04:59
*** lukebrowning has quit IRC05:03
*** lukebrowning has joined #openstack-tc05:13
*** lukebrowning has quit IRC05:16
*** lukebrowning has joined #openstack-tc05:17
*** lukebrowning has quit IRC05:22
*** lukebrowning has joined #openstack-tc05:26
*** lukebrowning has quit IRC05:31
*** lukebrowning has joined #openstack-tc05:32
*** lukebrowning has quit IRC05:41
*** lukebrowning has joined #openstack-tc05:44
*** lukebrowning has quit IRC05:48
*** lukebrowning has joined #openstack-tc05:50
*** lukebrowning has quit IRC05:54
*** tristanC_ has joined #openstack-tc06:21
*** robcresswell has quit IRC06:26
*** fdegir has quit IRC06:26
*** dirk has quit IRC06:26
*** TheJulia has quit IRC06:26
*** jroll has quit IRC06:26
*** persia has quit IRC06:26
*** knikolla has quit IRC06:26
*** tristanC has quit IRC06:26
*** jroll has joined #openstack-tc06:31
*** robcresswell has joined #openstack-tc06:31
*** fdegir has joined #openstack-tc06:31
*** dirk has joined #openstack-tc06:31
*** TheJulia has joined #openstack-tc06:31
*** persia has joined #openstack-tc06:31
*** knikolla has joined #openstack-tc06:31
*** robcresswell has quit IRC06:48
*** fdegir has quit IRC06:48
*** dirk has quit IRC06:48
*** TheJulia has quit IRC06:48
*** jroll has quit IRC06:48
*** persia has quit IRC06:48
*** knikolla has quit IRC06:48
*** lukebrowning has joined #openstack-tc06:49
*** lukebrowning has quit IRC06:54
*** lukebrowning has joined #openstack-tc06:55
*** lukebrowning has quit IRC07:00
*** lukebrowning has joined #openstack-tc07:02
*** lukebrowning has quit IRC07:06
*** lukebrowning has joined #openstack-tc07:08
*** lukebrowning has quit IRC07:12
*** lukebrowning has joined #openstack-tc07:14
*** lukebrowning has quit IRC07:19
*** dirk has joined #openstack-tc07:24
*** TheJulia has joined #openstack-tc07:24
*** robcresswell has joined #openstack-tc07:24
*** persia has joined #openstack-tc07:25
*** knikolla has joined #openstack-tc07:25
*** fdegir has joined #openstack-tc07:25
*** jroll has joined #openstack-tc07:25
*** ianw_pto is now known as ianw07:43
*** ianw is now known as ianw_pto07:43
*** gcb has quit IRC08:16
*** lukebrowning has joined #openstack-tc08:38
*** lukebrowning has quit IRC08:43
*** lukebrowning has joined #openstack-tc08:44
*** kumarmn has joined #openstack-tc08:48
*** lukebrowning has quit IRC08:49
*** lukebrowning has joined #openstack-tc08:51
*** kumarmn has quit IRC08:52
*** tristanC_ is now known as tristanC08:53
*** lukebrowning has quit IRC08:55
*** lukebrowning has joined #openstack-tc08:57
*** lukebrowning has quit IRC09:02
*** gcb has joined #openstack-tc09:03
*** lukebrowning has joined #openstack-tc09:03
*** lukebrowning has quit IRC09:08
*** lukebrowning has joined #openstack-tc09:10
*** lukebrowning has quit IRC09:14
*** lukebrowning has joined #openstack-tc09:16
*** lukebrowning has quit IRC09:20
*** dtantsur|afk is now known as dtantsur09:36
*** lukebrowning has joined #openstack-tc09:37
*** lukebrowning has quit IRC09:42
*** lukebrowning has joined #openstack-tc09:43
*** lukebrowning has quit IRC09:48
*** lukebrowning has joined #openstack-tc09:50
*** lukebrowning has quit IRC09:54
*** lukebrowning has joined #openstack-tc09:56
*** liujiong has quit IRC09:56
*** lukebrowning has quit IRC10:01
*** ianychoi has joined #openstack-tc10:06
*** lukebrowning has joined #openstack-tc10:13
*** lukebrowning has quit IRC10:18
*** lukebrowning has joined #openstack-tc10:20
*** lukebrowning has quit IRC10:24
*** dtantsur is now known as dtantsur|brb10:27
*** lukebrowning has joined #openstack-tc10:47
*** kumarmn has joined #openstack-tc10:50
*** lukebrowning has quit IRC10:52
*** lukebrowning has joined #openstack-tc10:53
*** kumarmn has quit IRC10:54
*** lukebrowning has quit IRC10:58
*** lukebrowning has joined #openstack-tc11:00
*** lukebrowning has quit IRC11:04
*** lukebrowning has joined #openstack-tc11:06
*** lukebrowning has quit IRC11:11
*** lukebrowning has joined #openstack-tc11:12
*** lukebrowning has quit IRC11:17
*** lukebrowning has joined #openstack-tc11:18
*** lukebrowning has quit IRC11:23
*** lukebrowning has joined #openstack-tc11:53
*** lukebrowning has quit IRC11:57
*** lukebrowning has joined #openstack-tc11:59
*** cdent has joined #openstack-tc12:03
*** lukebrowning has quit IRC12:03
*** lukebrowning has joined #openstack-tc12:09
*** dtantsur|brb is now known as dtantsur12:12
*** lukebrowning has quit IRC12:14
*** lukebrowning has joined #openstack-tc12:16
*** lukebrowning has quit IRC12:21
*** lukebrowning has joined #openstack-tc12:22
*** lukebrowning has quit IRC12:27
*** lukebrowning has joined #openstack-tc12:29
*** lukebrowning has quit IRC12:33
*** lukebrowning has joined #openstack-tc12:35
*** lukebrowning has quit IRC12:39
*** lukebrowning has joined #openstack-tc12:41
*** lukebrowning has quit IRC12:46
*** lukebrowning has joined #openstack-tc12:47
*** kumarmn has joined #openstack-tc12:51
*** lukebrowning has quit IRC12:52
*** lukebrowning has joined #openstack-tc12:53
*** kumarmn has quit IRC12:56
*** lukebrowning has quit IRC13:00
dimssomeone really wants to talk to us :)13:01
cdentluke has been doing that for days and days and days and days13:01
*** lukebrowning has joined #openstack-tc13:02
*** lukebrowning has quit IRC13:07
*** lukebrowning has joined #openstack-tc13:08
*** rosmaita has joined #openstack-tc13:10
*** lukebrowning has quit IRC13:13
*** lukebrowning has joined #openstack-tc13:14
cdenthuh, I thought part of the challenge with everyone consuming notifications is that they are not broadcast pub/sub-like, but instead are consume once and gone. I seem to recall from ceilometer days that we had this problem. If ceilo at the notifications, nothing else could have them.13:18
cdentIs that still true, or was it every true?13:18
cdentCan we change it?13:18
*** lukebrowning has quit IRC13:19
*** lukebrowning has joined #openstack-tc13:21
*** lukebrowning has quit IRC13:25
*** lukebrowning has joined #openstack-tc13:30
*** lukebrowning has quit IRC13:35
*** lukebrowning has joined #openstack-tc13:37
*** cdent has quit IRC13:37
*** lukebrowning has quit IRC13:41
*** lukebrowning has joined #openstack-tc13:43
*** cdent has joined #openstack-tc13:43
*** mriedem has joined #openstack-tc13:46
*** lukebrowning has quit IRC13:48
*** lukebrowning has joined #openstack-tc13:49
*** lukebrowning has quit IRC13:54
dmsimardI was asleep when last night's spam wave happened but last time it happened earlier this week I limited the damage by kickbanning bots and turning channel restrictions on13:54
dmsimardfungi and I discussed probably implementing this in accessbot13:55
*** lukebrowning has joined #openstack-tc13:55
*** lukebrowning has quit IRC14:00
*** lukebrowning has joined #openstack-tc14:02
*** lukebrowning has quit IRC14:07
*** lukebrowning has joined #openstack-tc14:08
*** lukebrowning has quit IRC14:13
*** lukebrowning has joined #openstack-tc14:14
dimsdmsimard : thanks!14:15
*** lukebrowning has quit IRC14:19
*** lukebrowning has joined #openstack-tc14:20
*** kumarmn has joined #openstack-tc14:23
*** lukebrowning has quit IRC14:25
*** lukebrowning has joined #openstack-tc14:33
*** lukebrowning has quit IRC14:38
fungiwell, implementing the flag which rejects unregistered nicks from /join'ing channels. it's something we would normally ever enact under persistent spam attacks since lots of people have enough trouble figuring out how to use irc much less figuring out how to register their nick and identify with nickserv14:38
*** lukebrowning has joined #openstack-tc14:39
*** lukebrowning has quit IRC14:44
*** lukebrowning has joined #openstack-tc14:45
*** rosmaita has quit IRC14:48
*** lukebrowning has quit IRC14:50
*** lukebrowning has joined #openstack-tc14:52
smcginnisIt would be unfortunate if we forced casual folks into going through all that.14:53
smcginnisHopefully this doesn't persist.14:53
*** lukebrowning has quit IRC14:56
*** lukebrowning has joined #openstack-tc14:58
fungitc-members: here's hoping for a more active office hour than wednesday ;)15:00
* smcginnis wants to just watch fungi talk to himself15:00
dtroyerHey ho!15:00
* cdent listens to fungi15:00
fungiworst case, i can invite the spambot back for an encore15:00
* dtroyer spoils smcginnis' fun15:00
smcginnis:)15:00
cmurphyhello15:01
cmurphythanks for holding down the fort yesterday fungi15:01
pabelangero/15:02
cdentYeah, I reckon we all owe fungi a great deal for the huge effort at mediation he performed15:02
dimso/15:02
*** lukebrowning has quit IRC15:02
* dtroyer read meditation at first there15:02
* cmurphy did too15:03
fungiit was a little of both15:03
fungialso cartoons15:03
fungiokay, actually it was in fact mostly cartoons15:04
*** lukebrowning has joined #openstack-tc15:04
dtroyercertain cartoons can lead to the same sorts of questions and pondering… well, maybe just "Duck Amuck"15:05
persiaIn the backscroll since the last office hour, there was some discussion of reasons to say negative things about OpenStack: one source I didn't see mentioned, but I sometimes encounter is complaints from people who are used to using traditional VMs, who complain about volume management, difficulties with the OS install process, etc.  These same folk seem delighted with container management tooling, as it does what they want without overloading15:05
persiatheir concept of "VM".  I don't know how prevalent this is, or how many folk don't use pre-installed images, etc., but it may be one of the many sources of distaste.15:05
dtroyernow I'm wondering how that fits with certain recent topics here15:05
fungicontainers amuck15:06
dtroyerpersia: I saw someone also mention a change in how we think about nova in particular as suited to cloud apps vs VM management.15:06
dtroyerfungi: ++15:06
fungipersia: by "pre-installed images" you mean booting instances from default images the service provider makes available vs supplying their own images and booting those?15:07
persiafungi: I mean booting an instance from an image that represents an installed OS, rather than one that represents an OS installer.15:08
fungiahh, gotcha15:08
persiaService providers can make images available, but users may not choose to use them (especially when using them requires them to rethink how they are doing things)15:08
*** lukebrowning has quit IRC15:09
dtroyeralso certain requirements for repeatability discourage the use of images that may go away at operators discretion15:09
fungiwell, i'll admit that at least for infra's use case, which involves attempting to treat systems consistently across multiple service providers, building our own images and uploading them has become essential. no two providers have exactly teh same images in their catalog15:09
persiaOne pattern I've seen that represents this class of thinking is for folk given access to AWS or an OpenStack to install a VMHost, in which they launch VMs for multiple sysroots, or similar.15:09
*** lukebrowning has joined #openstack-tc15:10
*** AJaeger has joined #openstack-tc15:11
fungioh, nesting virtual machines inside the nova-booted or aws instances?15:11
persiaAs one possible example, there are lots of docs about using `docker build` to create an image to use with docker.  There are many fewer for d-i-b.15:12
persiafungi: Yes: I believe this comes from internal semantic mapping for "virtual machine" as being something into which one installs an OS, rather than conceiving of the API resource as being something to which one passes a sysroot directly.15:13
smcginnisIIRC, only very recent versions of libvirt really supported nested virtualization well.15:14
persiasmcginnis: That's just a performance optimisation: low-speed nested virtualisation has been supported for decades.15:15
*** lukebrowning has quit IRC15:15
cdentit's certainly been the case for me when talking to random people that they can instantly grasp why they want to 'docker build' and much slower for why they want to do the nova boot dance15:15
persiacdent: "nova boot dance"?15:16
*** lukebrowning has joined #openstack-tc15:17
fungiyeah, the term "nested virtualization" is often misused to refer to hardware accelerated nested virt15:17
fungibut you can certainly nest virtual machines in other virtual machines without hardware optimizations to make them more performant15:17
cdentpersia: make a virtual machine, which happens to have an os, on which I need to do some stuff, and some other stuff, and yet other stuff, before I can actually do something15:17
persiacdent: Ah, as opposed to just having nova boot a preconfigured environment that happens to have the right things.  Yes, I suppose my point ends up being "the current messaging about nova boot suggests it is complicated, whereas other tooling suggests it can be simple to instantiate a repeatable custom environment."  Thanks for helping me understand that :)15:19
dtroyerin other words, comparing eating an apple salad bought from the deli vs picking apples, cutting them up, etc…15:19
persiadtroyer: Yes, although in practice, the underlying mechanisms aren't actually that different.  We already have tooling that automates the picking, cleaning, cutting, etc. (being d-i-b + glance, IIRC)15:20
cdentpersia: yeah, it's a messaging problem15:21
fungisuccessful uses of nova virtual machine instances tend to involve some sort of orchestration and configuration management engine deploying your applications into the vm for you once you boot it15:21
fungiif you're using generic images that is15:21
*** lukebrowning has quit IRC15:22
fungirather than having it boot up already configured with your application installed15:22
*** marst has joined #openstack-tc15:22
smcginnisWe have default volume types in cinder. Maybe we need a default instance flavor in nova. Then we can do "openstack run xenial" and get a running environment.15:22
smcginnisOr "openstack run my_app_configured_image15:23
*** lukebrowning has joined #openstack-tc15:23
TheJuliasmcginnis: or click in a gui...15:23
smcginnisTheJulia: Gooey? :) Yeah, that too.15:23
* EmilienM waves15:24
* fungi keeps forgetting we have one of those15:24
dtroyersmcginnis: too many opinions!  Even if we had baked in defaults from the start for flavors, etc, we'd still not be able to do that on j-random-cloud without a priori knowledge of the deployment15:24
TheJuliaI wonder how much of it is things like cli preference15:24
TheJuliaor lack their of15:24
smcginnisdtroyer: It would require some admin pre-config ahead of time, but if you know there is a typical default, it could help in some situations.15:24
ttxohai15:24
TheJuliaso what if there was tooling to discover or assist an operator in pre-baking a population for their environment?15:25
smcginnisBut just brainstorming.15:25
ttxbit late due to real life interruptions15:25
pabelangersmcginnis: you've basically described nodepool, does require defining the defaults, but once done, you ask for specific label and comes online. But, how would that be different then say, heat? Assuming cloud was running heat15:25
smcginnispabelanger: I was going to bring up heat but decided against it. :)15:25
dtroyerTheJulia: mordred has a proposal somehwere for the downloadable/cacheable cloud discovery doc that would/should include this15:25
smcginnisJust for the reason we were talking simplicity. But that probably is the better answer.15:26
pabelangersmcginnis: okay (I agree) I just wasn't sure if it was something else15:26
smcginnis;)15:27
* smcginnis steps out for appts15:27
dtroyerWe're dancing around (again) one of the things that will always favor public clouds individually in these discussions, knowing a bunch of default/configuration values ahead of time.15:27
*** lukebrowning has quit IRC15:28
dtroyeras a broup of course they are all different, but the comparison we see is "AWS vs OpenStack" not "AWS vs CityCloud" or whpomever15:28
TheJuliadtroyer: I feel like there are two^Wthree different cases. Structure of the cloud as the user perceives it, Operator preference for what runs in that cloud, and then user preference for $things being in the image that they may need.15:28
mordreddtroyer: yes - I need to rebase and fix that15:28
dtroyerSince OpenStack as a whole does not have that level of control, we will always 'lose' at that level of comparison15:29
dtroyerTheJulia: I think it has those three levels defined IIRC15:30
mordredTheJulia: https://review.openstack.org/#/c/459869/ fwiw15:31
persiaI feel like we're moving from "users complain about X" to "operators should do X for users": is there not something that can be done for users that all the operators end up having without needing them to each individually make changes?15:31
TheJuliadtroyer: I might be thinking way lower level in terms of operator preference, like preferred kernels or preferred versions of particular packages of things because the line between operator and user is semi-blurred15:32
mordredpersia: I agree - if the result is "tons of work for operators" it's not going to happen - however, if there is a way we can empower operators to easily make their users' lives better, and if the operator *doesn't* do it it's still available to the user as a local override ...15:32
dtroyerpersia: my gut reaction is the answer is "not give operators so many knobs to twiddle"15:32
fungipersia: i feel like that's a big point to the interop effort15:32
mordredthat's where I think the biggest win is15:32
fungibut basically if we can take choices away from operators, it reduces the ways in which they will "differentiate" themselves and pass that confution along to users15:33
fungiconfusion15:33
dtroyerTheJulia: gotcha… we were straddling images and contents with API-level comparisons15:33
dtroyerfungi says it in much nore palatable language :)15:34
fungihowever, to a great extent i don't think taking configurability away from deployers and operators works well in practice, since that's part of where our service provider culture of everyone carrying their own forks of openstack stems from15:34
*** lukebrowning has joined #openstack-tc15:34
fungiwe can't every completely take away the ability to customize openstack, since it's free software15:34
fungiwhat we've been able to take away is the ability to use specific trademarks15:35
TheJuliadtroyer: I think it still all kind of goes together, because it does boil down to making life easier in a sense15:35
persiaMy thought was more that things like "allow operators to provide a default with a short name" is an over-optimisation, but yeah, interop and more similarity between deployments both help.15:35
dtroyerwould it be interesting to compare say ESX with OpenStack in terms of the number/kinds of things that deployments can configure?  how many internal forks are there because they can instead of because it was really necessary?15:35
TheJuliadtroyer: or how much internal code is tied up trying to handle things that esx doesn't support well because of an operators opinions with their deployment15:37
fungiwell, also i don't think intentional differentiation is behind _all_ the internal forking. a lot of the blame also rests on how hard upgrades used to be, and the need to manually backport critical fixes to whatever version a deployment was "stuck" running15:37
fungibut once you've already decided you can't get away from running a fork anyway, the temptation to go ahead and add some bells and whistles in your fork may become greater/more palatable15:38
persiaMost of the complaints about "OpenStack" I hear aren't about particular deployments, or even differences between deployments: users I speak with seem happy to move between operators, or between internal/private clouds and various operators.15:39
*** lukebrowning has quit IRC15:39
dtroyersometimes those deployments are stuck because of the customization done too.  my hunch is that a good number of deployments with internal forks would not have done that again (as much) knowing what they know now.  Anyone know if we have a way to confirm or deny that hunch?15:39
fungiwe experienced this years ago running a fork of gerrit. we had one important (to us) feature we were having no luck upstreaming. but once we were committed to having to run a fork to maintain that feature, anything else we could have upstreamed was arguably easier to just put in our fork since we couldn't see the light at the end of the tunnel for when we'd be able to actually use anything we upstreamed15:40
fungianyway15:40
*** lukebrowning has joined #openstack-tc15:40
mriedemmordred: persia: get-me-a-network as an example?15:41
mriedemops just setup the default network i think and the rest is handled automagically by neutron15:42
persiamriedem: For some value of "automagically", depending on the level of tenant customisation required, but yes, that's a good example.15:42
mriedemsimilar idea here https://review.openstack.org/#/c/511965/15:43
mriedemhalf baked at this point, but make boot from volume simpler15:43
mriedemif you want multiple disks in a specific boot order with ephemeral and swap and guest format and disk buses, do that using the full API15:43
mriedembut if you just want your volume-backed instance with the image in the root disk, make it simpler15:44
fungi`openstack server do-what-i-want`15:44
mordredright. and then in shade the idea is to use get-me-a-network if the cloud has it, and fake it for the user is the cloud doensn't have it15:44
fungi`openstack server make-me-a-sandwich`15:44
mriedemdtroyer: "Anyone know if we have a way to confirm or deny that hunch?" yes that's very real15:44
mriedemi don't have a way to confirm it, because a lot of companies don't like to talk about it publicly15:45
mriedembut i know of at least a few that have that problem15:45
*** lukebrowning has quit IRC15:45
dtroyermriedem: thanks, that at least broadens the pool of anecdata there15:45
mriedemsome are pretty public about it15:45
mordredI have been at at least one while it discovered the epic horror of what it had done to itself15:46
mriedempenick and mgagne and klindgren come to mind15:46
mriedemreally anyone running cellsv115:46
mordredand that led to a policy of NEVER landing local patches without them at least being submitted upstream with some sort of upstream buy-on on the idea15:46
mriedemmordred: the smart ones do that15:46
*** lukebrowning has joined #openstack-tc15:47
TheJuliabut what does buy-in mean? does that mean that the submitter is going to continue to work the patch until it lands before applying internally, or does it mean that one +2, and then the patch becomes maintained and never land? Seems like a communication of expectation issue from both sides.15:49
TheJulias/maintained/unmaintained/15:49
mriedembuy-in is generally at a minimum a "this isn't totally bat shit crazy"15:50
mriedemor "-1 this is not the place to do this" from a core reviewer15:50
fungias in "we can probably get that feature implemented in some form, even if it looks nothing like your implementation under the hood?"15:51
mriedemif it's a bug fix that can generally fly, because if people agree it's a bug, hopefully it eventually gets fixed upstream even if not the original way you proposed15:51
mriedemif it's a feature, that's a different story15:51
mriedemIMO15:51
*** lukebrowning has quit IRC15:51
mriedemdepends on the feature, risk tolerance, etc15:51
mriedemif it's like a config option or something, pretty trivial, then it might be fine15:52
TheJuliamaybe projects should build consensus around expectations in terms of contributions if they haven't already?15:52
mriedemif it's a new API microversion, you probably don't want to risk that15:52
mriedemit depends on the company making the contribution too really15:52
mriedemand what their policy and culture are15:52
TheJuliaeach project, is naturally going to be different based on the composition of people, and their commitments.15:52
TheJuliamriedem: exactly15:52
fungii heard a lot of anecdotes out of rackspace that their forks of stuff ended up being self-perpetuating because they implemented features/options differently than what got upstreamed (if they ever got upstreamed in some cases), and had customers depending on those features in production so were contractually obligated to maintain their alternate reality even if support for something basically the same15:53
fungieventually emerged upstream with slightly different characteristics15:53
mriedemi fought for about 4 years at ibm to get us to a sane upstream<>downstream policy that finally got exec backing, but it was a hard slog15:53
*** lukebrowning has joined #openstack-tc15:53
mriedemand then shortly after that they killed the project :/15:53
TheJuliafungi: I wonder how many of those features were driven by short timelines for business requirements to differentiate themselves as a provider.15:55
fungimriedem: i so wanted to be able to nova boot a systemz lpar15:55
TheJuliaheh15:55
mriedemfungi: you still can https://review.openstack.org/#/q/topic:bp/add-zvm-driver-queens+status:open15:56
fungiTheJulia: no idea, but if it was at all like my old service provider job it was probably the sort of thing were sales said "we have this big deal who says they'll sign if only we get feature x they need added"15:56
mtreinishfungi: you're giving me flashbacks to those akward meetings I had with the z/OS hypervisor team years ago on doing that...15:56
mriedemTheJulia: it surely is driven in part by that,15:56
fungimtreinish: just use "facility" every third word and they'll assume you know what you're talking about15:56
mriedemi remember fighing a group consuming our stuff that was getting ready for ibm interconnect, which is the big ibm sales pow wow thing i guess, and getting escalated daily about why i wouldn't backport some features that weren't yet +2 upstream15:57
mriedemlike the whole "don't you know who i am?!" thing15:57
TheJuliaI fought a lot of that at HP[E] when I was split upstream/downstream15:57
*** lukebrowning has quit IRC15:58
TheJuliaThat desire to sell things or be flashy tends to be the focus and the debt of doing so doesn't calculate in.15:59
*** lukebrowning has joined #openstack-tc15:59
TheJuliaI wonder if things would change, at least in that interaction if they were able to scope the amount of effort/debt they would be building up by doing so15:59
* TheJulia is just thinking outloud16:00
mriedemthat's what i started doing about 2 years into the maintenance of mistakes made before i was even really working upstream,16:01
mriedemi started keeping track of every merge conflict we'd have (twice daily rebases with upstream), tag it about which feature it was related to, and how much time i spent working on it16:01
mriedemso i could eventually say, you're paying me x in salary and i'm spending y of my week on maintaining something that is not making you money16:02
mriedemmeanwhile the architects that pushed the early "value add" forks had all moved onto other positions and didn't have to care about the maintenance of said mistakes16:02
*** lukebrowning has quit IRC16:04
*** lukebrowning has joined #openstack-tc16:05
TheJuliaThat is a good post feature feedback loop. At least in Ironic, I feel like we don't arm developers that appear to implement a feature with enough information to set expectations appropriate/realistic expectations with the business. I feel like someone in the community for a while is able to grasp that, and communicate that upwards though.16:06
mriedemwell you're also assuming the developer cares16:07
TheJuliatrue16:07
mriedemor plans on maintaining that thing16:07
TheJuliaYeah16:08
* TheJulia would like to believe that everyone cares16:08
mriedemi tend to get into long co-dependent abusive relationships with the code i write16:08
*** lukebrowning has quit IRC16:10
*** lukebrowning has joined #openstack-tc16:12
fungito some degree, "startup mentality" plays into this too... accruing debt (be it technical or financial) early on is assumed to either be dwarfed by the success you'll drown in later or become irrelevant since you'll go out of business/scrap that business unit and move onto the next big thing16:15
fungiand if you're successful, solving the technical debt can become somebody elses problem16:15
*** lukebrowning has quit IRC16:17
*** lukebrowning has joined #openstack-tc16:18
*** lukebrowning has quit IRC16:23
*** lukebrowning has joined #openstack-tc16:24
*** lukebrowning has quit IRC16:29
*** lukebrowning has joined #openstack-tc16:31
*** lukebrowning has quit IRC16:35
*** lukebrowning has joined #openstack-tc16:37
*** lukebrowning has quit IRC16:42
*** lukebrowning has joined #openstack-tc16:43
*** lukebrowning has quit IRC16:48
*** lukebrowning has joined #openstack-tc16:49
*** lukebrowning has quit IRC16:54
*** lukebrowning has joined #openstack-tc16:56
*** lukebrowning has quit IRC17:01
*** lukebrowning has joined #openstack-tc17:02
*** lukebrowning has quit IRC17:07
*** lukebrowning has joined #openstack-tc17:08
*** lukebrowning has quit IRC17:13
*** kmalloc has joined #openstack-tc17:13
*** lukebrowning has joined #openstack-tc17:15
*** lukebrowning has quit IRC17:19
*** lukebrowning has joined #openstack-tc17:21
*** lukebrowning has quit IRC17:26
*** lukebrowning has joined #openstack-tc17:30
*** lukebrowning has quit IRC17:34
*** lukebrowning has joined #openstack-tc17:36
*** marst has quit IRC17:40
*** marst has joined #openstack-tc17:40
*** lukebrowning has quit IRC17:41
jrollTheJulia: some of those rackspace things were to differentiate (I think), but more were to 1) get a major thing done in months, not years, and 2) to handle the scale they were operating at (see cells v1, the upstream version is really only half done)17:42
*** lukebrowning has joined #openstack-tc17:42
*** lukebrowning has quit IRC17:47
*** dtantsur is now known as dtantsur|afk17:49
*** lukebrowning has joined #openstack-tc17:49
*** lukebrowning has quit IRC17:53
*** lukebrowning has joined #openstack-tc17:55
*** lukebrowning has quit IRC17:59
*** lukebrowning has joined #openstack-tc18:01
*** lukebrowning has quit IRC18:06
*** lukebrowning has joined #openstack-tc18:08
*** lukebrowning has quit IRC18:12
*** harlowja has joined #openstack-tc18:16
*** lukebrowning has joined #openstack-tc18:37
*** lukebrowning has quit IRC18:42
*** lukebrowning has joined #openstack-tc18:44
*** cdent has quit IRC18:44
*** lukebrowning has quit IRC18:48
*** lukebrowning has joined #openstack-tc18:50
*** lukebrowning has quit IRC18:55
*** lukebrowning has joined #openstack-tc18:56
*** lukebrowning has quit IRC19:01
*** lukebrowning has joined #openstack-tc19:03
*** lukebrowning has quit IRC19:07
*** lukebrowning has joined #openstack-tc19:09
*** lukebrowning has quit IRC19:14
*** lukebrowning has joined #openstack-tc19:46
*** diablo_rojo has quit IRC19:51
*** lukebrowning has quit IRC19:51
*** lukebrowning has joined #openstack-tc19:52
*** lukebrowning has quit IRC19:57
*** lukebrowning has joined #openstack-tc19:58
*** lukebrowning has quit IRC20:03
*** lukebrowning has joined #openstack-tc20:07
*** lukebrowning has quit IRC20:11
*** lukebrowning has joined #openstack-tc20:13
*** lukebrowning has quit IRC20:18
*** lukebrowning has joined #openstack-tc20:19
*** lukebrowning has quit IRC20:24
*** lukebrowning has joined #openstack-tc20:26
*** lukebrowning has quit IRC20:30
*** lukebrowning has joined #openstack-tc20:32
*** lukebrowning has quit IRC20:37
*** lukebrowning has joined #openstack-tc20:38
*** lukebrowning has quit IRC20:43
*** lukebrowning has joined #openstack-tc20:45
*** lukebrowning has quit IRC20:49
*** lukebrowning has joined #openstack-tc20:51
*** diablo_rojo has joined #openstack-tc20:51
*** lukebrowning has quit IRC20:56
*** AJaeger has left #openstack-tc20:59
*** lukebrowning has joined #openstack-tc21:02
*** lukebrowning has quit IRC21:07
*** lukebrowning has joined #openstack-tc21:09
*** lukebrowning has quit IRC21:13
*** lukebrowning has joined #openstack-tc21:15
*** lukebrowning has quit IRC21:20
*** lukebrowning has joined #openstack-tc21:21
*** flwang has quit IRC21:23
*** lukebrowning has quit IRC21:26
*** flwang has joined #openstack-tc21:36
*** lukebrowning has joined #openstack-tc21:53
*** andreaf has quit IRC21:55
*** andreaf has joined #openstack-tc21:56
*** lukebrowning has quit IRC21:58
*** diablo_rojo has quit IRC22:07
*** diablo_rojo has joined #openstack-tc22:14
*** lukebrowning has joined #openstack-tc22:33
*** lukebrowning has quit IRC22:38
*** lukebrowning has joined #openstack-tc22:39
*** lukebrowning has quit IRC22:44
*** lukebrowning has joined #openstack-tc22:45
*** diablo_rojo has quit IRC22:49
*** lukebrowning has quit IRC22:50
*** lukebrowning has joined #openstack-tc22:52
*** lukebrowning has quit IRC22:57
*** lukebrowning has joined #openstack-tc22:58
*** lukebrowning has quit IRC23:03
*** lukebrowning has joined #openstack-tc23:04
*** lukebrowning has quit IRC23:09
*** lukebrowning has joined #openstack-tc23:10
*** kumarmn has quit IRC23:13
*** lukebrowning has quit IRC23:15
*** lukebrowning has joined #openstack-tc23:17
*** lukebrowning has quit IRC23:22
*** lukebrowning has joined #openstack-tc23:23
*** kumarmn has joined #openstack-tc23:27
*** lukebrowning has quit IRC23:28

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