Wednesday, 2017-05-17

*** yamahata has quit IRC00:00
*** jogo has quit IRC00:00
*** cdub has joined #openstack-dev00:01
*** markvoelker has quit IRC00:01
xarses_mordred: wow, that was quick. I'll give it a whirl. tyvm00:01
*** jcoufal has joined #openstack-dev00:02
*** markvoelker has joined #openstack-dev00:02
*** jcoufal_ has quit IRC00:02
*** markvoelker has quit IRC00:04
*** jrist has joined #openstack-dev00:04
*** markvoelker has joined #openstack-dev00:04
*** piyushks has quit IRC00:05
*** baoli has quit IRC00:07
*** akscram has quit IRC00:09
*** jamesmca_ has joined #openstack-dev00:10
*** akscram has joined #openstack-dev00:10
*** jcoufal_ has joined #openstack-dev00:13
*** jcoufal has quit IRC00:13
*** jamesmca_ has quit IRC00:14
*** yamahata has joined #openstack-dev00:15
*** jamesmca_ has joined #openstack-dev00:15
*** d0ugal has quit IRC00:17
*** jamesmca_ has quit IRC00:20
*** jcoufal_ has quit IRC00:22
*** jcoufal has joined #openstack-dev00:23
*** thorst has joined #openstack-dev00:25
*** thorst has quit IRC00:27
*** jcoufal_ has joined #openstack-dev00:32
*** jcoufal has quit IRC00:32
*** ansmith has joined #openstack-dev00:32
*** ijw has quit IRC00:36
*** ijw has joined #openstack-dev00:36
*** limao has joined #openstack-dev00:37
*** hongbin has quit IRC00:37
*** fragatin_ has joined #openstack-dev00:38
*** jamesmca_ has joined #openstack-dev00:39
*** fragatin_ has quit IRC00:39
*** fragatin_ has joined #openstack-dev00:39
*** dimtruck is now known as zz_dimtruck00:40
*** ram5391 has quit IRC00:40
*** gianpietro has quit IRC00:41
*** fragatina has quit IRC00:41
*** jamesmca_ has quit IRC00:41
*** zz_dimtruck is now known as dimtruck00:42
*** charcol-v2 has joined #openstack-dev00:44
*** fragatin_ has quit IRC00:44
*** jcoufal has joined #openstack-dev00:46
*** charcol has quit IRC00:46
*** jcoufal_ has quit IRC00:47
*** dixiaoli has joined #openstack-dev00:51
*** ijw has quit IRC00:54
*** jcoufal_ has joined #openstack-dev00:56
*** charcol-v2 has quit IRC00:57
*** thorst has joined #openstack-dev00:57
*** cfh has quit IRC00:58
*** xlark has joined #openstack-dev00:58
*** charcol has joined #openstack-dev00:58
*** jcoufal has quit IRC00:59
*** diablo_rojo has joined #openstack-dev01:01
*** jamesmca_ has joined #openstack-dev01:07
*** harlowja has quit IRC01:08
*** ansmith has quit IRC01:09
*** d0ugal has joined #openstack-dev01:13
*** thorst has quit IRC01:16
*** bobh has joined #openstack-dev01:17
*** gyee has quit IRC01:22
*** piyushks has joined #openstack-dev01:24
*** gianpietro has joined #openstack-dev01:24
*** salv-orlando has quit IRC01:25
*** gyee has joined #openstack-dev01:26
*** tovin07_ has joined #openstack-dev01:26
*** jcoufal_ has quit IRC01:28
*** jcoufal has joined #openstack-dev01:28
*** gianpietro has quit IRC01:29
*** dixiaoli has quit IRC01:30
*** thorst has joined #openstack-dev01:31
*** jcoufal_ has joined #openstack-dev01:31
*** thorst has quit IRC01:33
*** jcoufal has quit IRC01:34
Anticimexmordred: re trolling (pg depr comments earlier) - it wasn't really trolling, as much as a reading of apparent sentiment from the outside (biases etc apply)01:35
Anticimexmordred: i assume you agree that catching a race error in neutron, such as https://bugs.launchpad.net/neutron/+bug/1691176 , is valuable?01:36
openstackLaunchpad bug 1691176 in neutron "test_verify_duplicate_network_nics[id-1678d144-ed74-43f8-8e57-ab10dbf9b3c2] race fails during port deletion on postgresql job" [High,Fix released] - Assigned to Kevin Benton (kevinbenton)01:36
*** piyushks has quit IRC01:36
*** gianpietro has joined #openstack-dev01:37
*** jamesmca_ has quit IRC01:38
Anticimexi'm not versed enough in the CI/gate to know the required steps in order to fly around and pick up on "postgres" errors (have yet to ever see one that is caused by something which is pg's fault), but it could be an interesting hobby, that perhaps some operators could care about01:38
*** jcoufal_ has quit IRC01:43
*** jcoufal has joined #openstack-dev01:44
*** gianpietro has quit IRC01:45
*** gongysh has joined #openstack-dev01:47
*** bobh has quit IRC01:49
*** donghao has joined #openstack-dev01:52
*** achampion has joined #openstack-dev01:54
*** bobh has joined #openstack-dev01:56
*** donghao has quit IRC01:57
*** rawl has joined #openstack-dev01:58
*** bobmel has quit IRC02:05
*** rawl has quit IRC02:07
*** slaweq has joined #openstack-dev02:10
*** xingchao has joined #openstack-dev02:12
*** slaweq has quit IRC02:15
*** xingchao has quit IRC02:16
*** yamahata has quit IRC02:16
*** thorst has joined #openstack-dev02:18
*** thorst has quit IRC02:19
*** bobh has quit IRC02:19
*** iyamahat has quit IRC02:21
*** gianpietro has joined #openstack-dev02:21
*** ihrachys has joined #openstack-dev02:21
*** cdub has quit IRC02:24
*** cdub has joined #openstack-dev02:25
*** gianpietro has quit IRC02:25
*** cdub has quit IRC02:27
*** jaypipes has joined #openstack-dev02:27
*** jcoufal has quit IRC02:28
*** jcoufal has joined #openstack-dev02:29
*** thorst has joined #openstack-dev02:29
*** thorst has quit IRC02:29
*** xingchao has joined #openstack-dev02:30
*** gyee has quit IRC02:35
*** jaypipes has quit IRC02:40
*** fragatina has joined #openstack-dev02:41
*** jcoufal has quit IRC02:45
*** fragatina has quit IRC02:45
*** cdub has joined #openstack-dev02:47
*** sree has joined #openstack-dev02:49
*** jamesmca_ has joined #openstack-dev02:50
*** nicolasbock has quit IRC02:51
*** sree has quit IRC02:53
*** fragatina has joined #openstack-dev02:56
*** fragatina has quit IRC02:57
*** fragatina has joined #openstack-dev02:58
*** diablo_rojo has quit IRC02:59
*** cdub has quit IRC03:00
*** thorst has joined #openstack-dev03:00
*** cdub has joined #openstack-dev03:00
*** kjw3 has quit IRC03:04
*** ociuhandu has joined #openstack-dev03:08
*** cdub has quit IRC03:09
*** ociuhandu has quit IRC03:10
*** qlixed has quit IRC03:13
*** ociuhandu has joined #openstack-dev03:15
*** thorst has quit IRC03:18
*** limao_ has joined #openstack-dev03:19
*** limao has quit IRC03:20
*** gkadam has joined #openstack-dev03:24
*** rawl has joined #openstack-dev03:24
*** fragatina has quit IRC03:24
*** gkadam has quit IRC03:24
*** gkadam has joined #openstack-dev03:24
*** ram5391 has joined #openstack-dev03:28
*** Poornima has joined #openstack-dev03:28
*** piyushks has joined #openstack-dev03:32
*** jamesmca_ has quit IRC03:36
*** slaweq has joined #openstack-dev03:38
*** slaweq has quit IRC03:43
*** piyushks has quit IRC03:43
*** stanzgy has joined #openstack-dev03:43
*** ihrachys has quit IRC03:44
*** ihrachys has joined #openstack-dev03:44
*** donghao has joined #openstack-dev03:54
*** gouthamr has quit IRC03:57
*** donghao has quit IRC03:59
*** piyushks has joined #openstack-dev04:00
*** zackf has joined #openstack-dev04:00
*** stanzgy has quit IRC04:01
*** zackf has quit IRC04:05
*** stanzgy has joined #openstack-dev04:13
*** gomarivera_ has joined #openstack-dev04:13
*** thorst has joined #openstack-dev04:15
*** gongysh has quit IRC04:15
*** thorst has quit IRC04:20
*** ram5391 has quit IRC04:28
*** Poornima has quit IRC04:33
*** harlowja has joined #openstack-dev04:33
*** cdub has joined #openstack-dev04:33
*** ayogi has joined #openstack-dev04:37
*** anilvenkata has joined #openstack-dev04:44
*** lihi has quit IRC04:46
*** lihi has joined #openstack-dev04:47
*** piyushks has quit IRC04:50
*** akscram has quit IRC04:50
*** akscram has joined #openstack-dev04:51
*** gongysh has joined #openstack-dev04:53
*** rawl has quit IRC04:57
*** piyushks has joined #openstack-dev04:58
*** ociuhandu has quit IRC05:00
*** iyamahat has joined #openstack-dev05:08
*** achampion has quit IRC05:09
*** AnilV4 has joined #openstack-dev05:10
*** thorst has joined #openstack-dev05:16
*** thorst has quit IRC05:21
*** yamahata has joined #openstack-dev05:28
*** sree has joined #openstack-dev05:29
*** salv-orlando has joined #openstack-dev05:32
*** jtomasek has quit IRC05:33
*** achampion has joined #openstack-dev05:35
*** jamesmca_ has joined #openstack-dev05:36
*** achampion has quit IRC05:39
*** armax has quit IRC05:40
*** jamesmca_ has quit IRC05:40
*** skazi has quit IRC05:41
*** iyamahat has quit IRC05:44
*** LuigiOpenstack has joined #openstack-dev05:48
LuigiOpenstackHi team,05:48
*** pcaruana has joined #openstack-dev05:48
LuigiOpenstackI need some help with my code05:48
LuigiOpenstackWhere can I put the code?05:48
*** Bhootrk_ has quit IRC05:49
*** sridharg has joined #openstack-dev05:53
*** harlowja has quit IRC05:54
*** tobberydberg has joined #openstack-dev05:56
*** dsariel has joined #openstack-dev05:57
*** fragatina has joined #openstack-dev05:58
*** armaan has quit IRC06:01
*** armaan has joined #openstack-dev06:01
*** kobis has joined #openstack-dev06:04
*** achampion has joined #openstack-dev06:05
*** piyushks has quit IRC06:07
*** skazi has joined #openstack-dev06:12
*** itzikb has joined #openstack-dev06:15
*** fragatina has quit IRC06:15
*** thorst has joined #openstack-dev06:17
*** rcernin has joined #openstack-dev06:18
*** jprovazn has joined #openstack-dev06:19
*** achampion has quit IRC06:21
*** limao_ has quit IRC06:21
*** thorst has quit IRC06:22
*** takamatsu has joined #openstack-dev06:24
*** limao has joined #openstack-dev06:27
*** paramite has quit IRC06:31
*** gongysh has quit IRC06:31
*** limao has quit IRC06:32
*** dimak_ has joined #openstack-dev06:33
*** athomas has joined #openstack-dev06:35
*** limao has joined #openstack-dev06:39
*** charcol has quit IRC06:41
*** gongysh has joined #openstack-dev06:43
*** matrohon has joined #openstack-dev06:47
*** makowals has joined #openstack-dev06:47
*** limao has quit IRC06:48
*** limao has joined #openstack-dev06:52
*** limao has quit IRC06:52
*** limao has joined #openstack-dev06:53
*** mgagne has quit IRC06:53
*** mgagne has joined #openstack-dev06:56
*** mgagne is now known as Guest2410306:56
*** limao has quit IRC06:57
*** rcernin has quit IRC06:57
*** limao has joined #openstack-dev06:59
*** e0ne has joined #openstack-dev07:02
*** gamado has joined #openstack-dev07:02
*** limao_ has joined #openstack-dev07:02
*** limao has quit IRC07:02
*** limao_ has quit IRC07:02
*** shardy has joined #openstack-dev07:06
*** limao has joined #openstack-dev07:08
*** salv-orlando has quit IRC07:09
*** ltomasbo|away is now known as ltomasbo07:10
*** rcernin has joined #openstack-dev07:13
*** achampion has joined #openstack-dev07:17
*** thorst has joined #openstack-dev07:18
*** thorst has quit IRC07:22
*** epopt has quit IRC07:23
*** sridharg has quit IRC07:23
*** treiz has quit IRC07:26
*** mriedem has quit IRC07:27
*** rcernin has quit IRC07:29
*** sridharg has joined #openstack-dev07:30
*** dtantsur|afk is now known as dtantsur07:33
*** rcernin has joined #openstack-dev07:35
*** rcernin has quit IRC07:35
*** rcernin has joined #openstack-dev07:35
*** akscram has quit IRC07:36
*** akscram has joined #openstack-dev07:37
*** paramite has joined #openstack-dev07:39
*** ioggstream has joined #openstack-dev07:43
*** gfidente has joined #openstack-dev07:47
*** achampion has quit IRC07:50
*** georgelorch has quit IRC07:51
*** gkadam is now known as gkadam-afk07:52
*** georgelorch has joined #openstack-dev07:52
*** jpich has joined #openstack-dev07:53
*** lpetrut has joined #openstack-dev07:54
LuigiOpenstackCan anyone help me with the code at http://paste.openstack.org/show/609741/07:56
LuigiOpenstackI am not able to list images07:56
*** gongysh has quit IRC07:56
*** tobberyd_ has joined #openstack-dev07:56
*** xingchao has quit IRC07:58
*** snica_away is now known as snica07:58
*** xingchao has joined #openstack-dev07:58
*** xingchao has quit IRC07:59
*** tobberydberg has quit IRC07:59
*** zzzeek has quit IRC08:00
*** xingchao has joined #openstack-dev08:00
*** iyamahat has joined #openstack-dev08:03
*** sridharg has quit IRC08:03
*** zzzeek has joined #openstack-dev08:04
*** djohnsto has joined #openstack-dev08:04
*** chigang_ has joined #openstack-dev08:07
*** iyamahat has quit IRC08:07
*** dimtruck is now known as zz_dimtruck08:08
*** salv-orlando has joined #openstack-dev08:10
johnthetubaguylbragstad: I will try, not 100% sure at this point08:12
*** gszasz has joined #openstack-dev08:12
*** lucas-afk is now known as lucasagomes08:13
*** salv-orlando has quit IRC08:14
*** achampion has joined #openstack-dev08:17
*** mhickey has joined #openstack-dev08:17
*** thorst has joined #openstack-dev08:18
*** yamahata has quit IRC08:20
*** xingchao has quit IRC08:20
*** makowals_ has joined #openstack-dev08:20
*** xingchao has joined #openstack-dev08:21
*** achampion has quit IRC08:21
*** makowals has quit IRC08:22
*** thorst has quit IRC08:23
*** dhajare has joined #openstack-dev08:25
*** xingchao has quit IRC08:25
*** radez has quit IRC08:26
*** gszasz has quit IRC08:27
*** jtomasek has joined #openstack-dev08:31
*** akscram has quit IRC08:34
*** gongysh has joined #openstack-dev08:34
*** akscram has joined #openstack-dev08:34
*** vnogin has joined #openstack-dev08:45
*** vnogin has quit IRC08:49
*** aarefiev_afk is now known as aarefiev08:51
*** dimak_ has quit IRC08:52
*** electrofelix has joined #openstack-dev08:52
*** shardy has quit IRC08:53
*** xingchao has joined #openstack-dev08:53
*** egallen has joined #openstack-dev08:54
*** xingchao has quit IRC08:55
*** xingchao has joined #openstack-dev08:55
*** shardy has joined #openstack-dev08:56
*** cablekev1n has joined #openstack-dev08:58
*** xingchao_ has joined #openstack-dev08:59
*** xingchao has quit IRC08:59
*** xingchao_ has quit IRC08:59
*** xingchao has joined #openstack-dev09:00
*** salv-orlando has joined #openstack-dev09:00
ttxjohnthetubaguy: do you remember who signed up (if anyone) to distill the vision feedback into actionable points ?09:01
*** armaan has quit IRC09:02
*** gszasz has joined #openstack-dev09:03
*** xingchao has quit IRC09:04
*** dsariel_ has joined #openstack-dev09:06
*** salv-orlando has quit IRC09:06
*** xingchao has joined #openstack-dev09:08
*** xingchao has quit IRC09:09
*** xingchao has joined #openstack-dev09:09
*** xingchao has quit IRC09:09
*** xingchao has joined #openstack-dev09:10
*** djohnsto has quit IRC09:11
*** tobberyd_ has quit IRC09:12
*** tobberydberg has joined #openstack-dev09:13
*** gongysh has quit IRC09:14
*** gongysh has joined #openstack-dev09:15
*** achampion has joined #openstack-dev09:17
*** thorst has joined #openstack-dev09:19
*** armaan has joined #openstack-dev09:22
*** limao has quit IRC09:26
*** dalgaaf has quit IRC09:33
*** dsariel_ has quit IRC09:33
*** dsariel has quit IRC09:33
*** dalgaaf has joined #openstack-dev09:33
*** asettle has joined #openstack-dev09:37
*** thorst has quit IRC09:39
*** vnogin has joined #openstack-dev09:40
*** vnogin has quit IRC09:44
*** feisky has joined #openstack-dev09:45
dimsHi feisky09:46
johnthetubaguyttx: I don't think anyone did, although I was keen to help with that09:46
ttxjohnthetubaguy: yesterday we had cdent and dtroyer volunteering to help, too09:47
ttxmaybe you 3 can reach out to gothicmindfood and get it started09:47
ttxjohnthetubaguy: see the email I just sent to openstack-tc about the new status tracker @ https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee09:47
johnthetubaguyttx: cool, sounds like a plan, I am not employed right now though, so online off and on right now, I will try get to that09:48
johnthetubaguyttx: nice :)09:48
* dims waves to ttx and johnthetubaguy 09:48
* johnthetubaguy waves back09:49
dimsfeisky : i don't see your groups setup in gerrit https://review.openstack.org/#/admin/groups/09:49
dimsfeisky : i was expecting a stackube-core and stackube-release there09:49
feiskyI'm not sure how to do this.  Could you offer a help?09:49
ttxdims: if you want to help Stackube through the submission process, I can add you as sponsor/driver on that proposal in the tracker :)09:49
dimsttx : sure09:50
* ttx adds09:50
dimsfeisky : we'll need to request help from the infra folks...yet another channel feisky (#openstack-infra)09:50
*** achampion has quit IRC09:51
*** vnogin has joined #openstack-dev09:51
feiskydims: joined the channel.09:51
*** snica has quit IRC09:52
dimsthanks feisky09:53
*** snica has joined #openstack-dev09:53
*** e0ne has quit IRC09:55
*** tovin07_ has quit IRC09:56
*** slaweq has joined #openstack-dev09:56
*** yamamoto has quit IRC09:56
*** itzikb_ has joined #openstack-dev09:59
jamespageicey: https://review.openstack.org/#/q/topic:bug/1691428 fairly simple resolution to that one10:00
*** itzikb has quit IRC10:00
iceyjamespage: had my eye on those, waiting on jenkins :)10:00
*** snica is now known as snica_away10:01
jamespageicey: ta10:01
*** donghao has joined #openstack-dev10:01
*** slaweq has quit IRC10:01
*** xingchao has quit IRC10:04
*** dizquierdo has joined #openstack-dev10:05
*** treiz has joined #openstack-dev10:05
*** donghao has quit IRC10:05
*** johnthetubaguy has left #openstack-dev10:05
*** salv-orlando has joined #openstack-dev10:10
dimsfeisky : can you join #openstack-kuryr, #openstack-containers, #openstack-helm, #openstack-kolla, #openstack-golang and lurk there, i will make introductions as and when folks show up10:11
feiskyok10:12
*** faizy has joined #openstack-dev10:14
*** salv-orlando has quit IRC10:15
*** Daviey_ is now known as Daviey10:15
*** achampion has joined #openstack-dev10:16
dimsoh, and #openstack-zun as well feisky10:17
ttxwow, lotsa channels I'm not on10:19
dimsttx :)10:26
flaper87ttx: rofl10:29
*** sdague has joined #openstack-dev10:29
*** slaweq has joined #openstack-dev10:32
*** thorst has joined #openstack-dev10:35
*** snica_away is now known as snica10:36
*** slaweq has quit IRC10:37
*** jamesmca_ has joined #openstack-dev10:37
*** jkilpatr has quit IRC10:38
*** thorst has quit IRC10:40
*** dimak_ has joined #openstack-dev10:41
*** jamesmca_ has quit IRC10:42
*** yamamoto has joined #openstack-dev10:45
*** ayogi has quit IRC10:52
-openstackstatus- NOTICE: gerrit is being restarted to help stuck git replication issues10:53
*** nicolasbock has joined #openstack-dev10:54
*** aspiers_ has quit IRC10:56
*** feisky has quit IRC10:57
*** feisky has joined #openstack-dev10:58
*** bobmel has joined #openstack-dev10:59
*** jkilpatr has joined #openstack-dev11:00
*** ansmith has joined #openstack-dev11:00
*** gszasz has quit IRC11:05
*** gomarivera_ has quit IRC11:05
*** ansmith has quit IRC11:06
*** feisky has quit IRC11:06
*** salv-orlando has joined #openstack-dev11:11
*** paramite has quit IRC11:14
*** sshnaidm is now known as sshnaidm|lnch11:15
*** feisky has joined #openstack-dev11:15
*** achampion has quit IRC11:15
*** itzikb_ has quit IRC11:15
*** itzikb_ has joined #openstack-dev11:16
*** salv-orlando has quit IRC11:16
*** gongysh has quit IRC11:18
*** gongysh has joined #openstack-dev11:18
*** dsariel has joined #openstack-dev11:18
*** dsariel_ has joined #openstack-dev11:18
*** rfolco has joined #openstack-dev11:19
*** gongysh has quit IRC11:19
*** cdent has joined #openstack-dev11:19
*** gongysh has joined #openstack-dev11:19
*** gongysh has quit IRC11:19
*** gongysh has joined #openstack-dev11:20
*** gongysh has quit IRC11:20
*** dizquierdo has quit IRC11:20
*** gianpietro has joined #openstack-dev11:22
*** gianpietro has quit IRC11:27
*** iogg has joined #openstack-dev11:32
*** ioggstream has quit IRC11:32
*** dizquierdo has joined #openstack-dev11:33
*** alexismonville has joined #openstack-dev11:34
*** vnogin has quit IRC11:37
*** vnogin has joined #openstack-dev11:38
*** alexismonville has quit IRC11:38
*** zul has quit IRC11:39
*** zul has joined #openstack-dev11:41
*** vnogin has quit IRC11:42
*** vnogin has joined #openstack-dev11:46
*** thorst has joined #openstack-dev11:46
*** achampion has joined #openstack-dev11:47
*** e0ne has joined #openstack-dev11:48
*** sshnaidm|lnch is now known as sshnaidm11:48
*** dizquierdo has quit IRC11:49
*** gongysh has joined #openstack-dev11:49
*** paramite has joined #openstack-dev11:50
*** gianpietro has joined #openstack-dev11:50
*** dizquierdo has joined #openstack-dev11:51
*** donghao has joined #openstack-dev11:52
*** gianpietro has quit IRC11:56
*** vnogin has quit IRC11:57
*** claudiub has joined #openstack-dev11:57
*** donghao has quit IRC11:57
*** gongysh has quit IRC11:58
*** lucasagomes is now known as lucas-hungry11:59
*** radez has joined #openstack-dev12:00
*** gordc has joined #openstack-dev12:00
*** skazi has quit IRC12:00
*** cdub has quit IRC12:02
*** skazi has joined #openstack-dev12:03
*** dizquierdo has quit IRC12:04
*** kobis has quit IRC12:04
*** dizquierdo has joined #openstack-dev12:04
*** gianpietro has joined #openstack-dev12:10
*** noslzzp has joined #openstack-dev12:10
*** ericyoung has quit IRC12:11
*** snica is now known as snica_away12:13
*** snica_away is now known as snica12:13
*** claudiub has quit IRC12:15
*** jwcroppe has quit IRC12:16
*** jwcroppe has joined #openstack-dev12:16
*** mriedem has joined #openstack-dev12:17
*** mriedem has quit IRC12:18
*** mriedem has joined #openstack-dev12:18
*** jwcroppe has quit IRC12:20
*** skazi has quit IRC12:20
*** gszasz has joined #openstack-dev12:21
*** skazi has joined #openstack-dev12:21
*** achampion has quit IRC12:22
*** treiz has quit IRC12:22
*** mhickey has quit IRC12:23
*** rpittau has joined #openstack-dev12:26
*** vnogin has joined #openstack-dev12:29
*** skazi has quit IRC12:30
*** gianpietro has quit IRC12:31
*** gianpietro has joined #openstack-dev12:32
*** treiz has joined #openstack-dev12:33
*** ayogi has joined #openstack-dev12:33
*** dizquierdo has quit IRC12:34
*** dizquierdo has joined #openstack-dev12:34
*** zz_dimtruck is now known as dimtruck12:34
*** gkadam-afk is now known as gkadam12:35
*** gianpietro has quit IRC12:36
*** jprovazn has quit IRC12:37
*** salv-orlando has joined #openstack-dev12:39
*** gouthamr has joined #openstack-dev12:40
*** salv-orlando has quit IRC12:40
*** ansmith has joined #openstack-dev12:41
*** edmondsw has joined #openstack-dev12:41
*** salv-orlando has joined #openstack-dev12:41
*** dimak_ has quit IRC12:41
*** cioran89 has joined #openstack-dev12:42
*** kylek3h has quit IRC12:46
*** cdub has joined #openstack-dev12:46
*** jrist has quit IRC12:47
efriedlbragstad Sphinx 1.6.1 has been blocked in g-r for many projects, but looks like keystone-specs isn't in the bot's list.12:48
efriedAppropriate to propose manually?12:48
efried(ref: https://review.openstack.org/#/c/460344/)12:48
*** sree has quit IRC12:48
*** sree has joined #openstack-dev12:49
*** dimak_ has joined #openstack-dev12:49
*** jamesmca_ has joined #openstack-dev12:52
*** jamesmca_ has quit IRC12:52
*** jamesmca_ has joined #openstack-dev12:53
efriedlbragstad https://review.openstack.org/#/c/465543/12:53
*** sree has quit IRC12:54
*** sree has joined #openstack-dev12:54
efriedlbragstad Rebased https://review.openstack.org/#/c/460344/ on it.12:54
efriedFeel free to unwind & slap wrist if that ain't the right thing ;-)12:54
*** bobmel has quit IRC12:56
*** dimak_ has quit IRC12:56
*** bobmel has joined #openstack-dev12:57
*** lucas-hungry is now known as lucasagomes12:57
*** xyang1 has joined #openstack-dev12:58
mordredAnticimex: catching a race error in neutron is valuable - but that can be done with mysql as well, should anyone care to. setting SQL_MODE=TRADITIONAL will throw the same error. if we want the db layer to throw more errors and help catch more bugs lke that, we shoud set that flag in our mysql. highlighting that you think people are biased against pg doesn't really help anything. also, the pg12:59
mordreddeprecation discussion is not based on anti-pg sentiment. I've said multiple times I'd be just as happy scrapping mysql and picking pg - the point is picking ONE thing so we can do a good job with it12:59
*** ayogi has quit IRC13:00
*** gmoro_ has joined #openstack-dev13:00
*** gmoro has quit IRC13:01
cdentI'm still not fully convinced that "picking ONE thing" is a good thing13:01
*** bobmel has quit IRC13:02
*** dtantsur is now known as dtantsur|brb13:02
*** gomarivera_ has joined #openstack-dev13:02
*** eharney has joined #openstack-dev13:03
*** salv-orlando has quit IRC13:03
fungiwe're not really good at distinguishing between "picking two things" and "picking all things" though13:03
*** salv-orlando has joined #openstack-dev13:04
*** dsariel_ has quit IRC13:04
*** dsariel has quit IRC13:04
*** johnthetubaguy has joined #openstack-dev13:04
*** dizquierdo has quit IRC13:05
*** itzikb has joined #openstack-dev13:05
*** haleyb has joined #openstack-dev13:05
*** itzikb_ has quit IRC13:05
*** tuan_luong has joined #openstack-dev13:06
*** dsariel has joined #openstack-dev13:06
*** gomarivera_ has quit IRC13:07
*** salv-orlando has quit IRC13:08
*** stanzgy has quit IRC13:08
openstackgerritdane-fichter proposed openstack/governance master: Add Queens goal split out tempest plugins  https://review.openstack.org/36974913:10
sdagueso, if someone that cared a lot about pg did the following: 1) made consistent utf8 4 byte naming across core infrastructure 2) fixed server list by ip to use the db (not filter in python which falls down if more than 1000 servers got to that filter) 3) made it so new developers didn't need pg driver to run unit tests on all the projects13:10
sdagueI would have less objections13:11
sdagueif we deprecate pg, all of those become easier problems to solve13:11
sdaguemaking them accessable to more people13:11
*** athomas has quit IRC13:12
*** kriskend_ has joined #openstack-dev13:12
sdaguethe bar to address a whole set of problems right now is so high because you have a leaky abstraction in sqla, so the abstraction only helps the easy stuff, not the hard stuff, and the hard stuff gets harder13:13
*** athomas has joined #openstack-dev13:13
*** gianpietro has joined #openstack-dev13:14
*** jrist has joined #openstack-dev13:14
*** dimak_ has joined #openstack-dev13:16
*** jathan has joined #openstack-dev13:17
*** mkoderer has joined #openstack-dev13:17
*** marst has quit IRC13:18
*** marst has joined #openstack-dev13:18
*** kylek3h has joined #openstack-dev13:19
cdentsdague: the fact that sqla can be leaky seems like a big reason why we _should_ test with both mysql and pg, not a reason why we shouldn't13:20
cdentI'm trying hard not to become too overly engaged with this issue, because there are only so many issues a single brain can think usefully about, but it is hard because I keep getting drawn for some reason.13:21
sdaguecdent: it's odd to me that you are arguing the perspective you are, because most of the time you are on the "move fast and break things so it's better for users in the future"13:22
*** vladikr has joined #openstack-dev13:22
sdaguethis isn't just a test issue13:22
cdentI know, I'm surprised too13:23
sdaguethis is a whole lot of things that have now become too hard to do because of supporting multiple backends13:23
cdentbut the thing "associated tooling" issue that came up in boston was extremely compelling (for me)13:23
*** baoli has joined #openstack-dev13:23
cdentit's seems inconsistent to be concerned about api-scripts, but not about database-scripts13:24
sdagueour database is not a public api13:24
cdentbut also, I just find it really weird to _not_ support multiple databases. that's just how things are done13:24
*** jcoufal has joined #openstack-dev13:24
*** kbringard has joined #openstack-dev13:24
sdaguecdent: that's how things are done in trivial applications that don't need advance features13:24
cdentopenstack's use of the database is trivial!13:25
sdagueexcept when it isn't13:25
* cdent shrugs13:25
mordredwell - at the very least, we shoujld probably set sql_mode=traditional in our sqla engine creation and get _that_ item taken care of13:26
cdentmordred++13:26
sdaguemordred: I was pretty sure that's already a thing13:26
*** ram5391 has joined #openstack-dev13:26
sdaguecdent: so in the open source software I use, multiple database support isn't granted13:27
mordredsdague: if https://review.openstack.org/#/c/427667/ happened, then it's not13:27
sdaguewordpress / drupal those both have a supported back end (mysql) and some folks of on the side that do other backends. But definitely not upstream supported.13:27
mordredcdent: multi-database support is also not a thing for any of the large-scale systems out there - facebook runs on one database, not on an optional set13:28
sdaguemordred: I thought that group_by was special13:28
fungihttps://codex.wordpress.org/Using_Alternative_Databases is a nice reference example13:28
sdaguezzzeek said something to that affect in his email response13:28
cdentyou guys are talking about applications, which is fine, but out of another mouth people will talk about openstack as composable toolkits13:29
mordredsdague: group_by behavior gets covered by TRADITONAL as part of ONLY_FULL_GROUP_BY13:29
sdaguemordred: ok13:29
mordredhttps://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_only_full_group_by13:29
*** ram5391 has quit IRC13:29
cdentin _frameworks_ using multiple dbs is common and accepted, and a reason why sqla gained a lot of traction13:29
sdaguecdent: it's still composable, at the service level.13:29
fungicdent: how about openstack as composable (server-side) applications? ;)13:29
sdaguecdent: for applications that don't need to handle zero downtime mix and match code levels with database schema13:30
* fungi isn't sure what about an api service daemon makes it not an application too13:30
cdentI don't know, I really don't know that I want to care about this, but I'm not sure how easily we can dismiss people with existing pg-based deployments and tooling.13:30
mordredcdent: yes. but I think with the push to interoperable end-user apis, I value openstack-as-thing more than I value openstack-as-cloud-construction-toolkit. but that may just be me13:30
mordredcdent: I agree13:30
sdaguecdent: which is why, step 1 - warn new people13:30
mordredyup13:30
cdentyes, I'm totally pro warning people13:31
sdaguenot doing so is basically lying to our users13:31
mordredand then actually talk in real terms about cost on both sides13:31
*** sree has quit IRC13:31
mordredbecaues there are real costs to both sides of the coin13:31
cdentbut it needs to be a warning couched in "we can fix this" rather than "this is the inevitable trend"13:31
sdaguecdent: ok, but then I don't understand why you -1ed the proposal, because the concrete actions were "warn people", and see what a migration looks like13:31
*** jprovazn has joined #openstack-dev13:32
cdentbecause the beginning of it is all "we really only do mysql and doing mysql is really the only way people should be doing things and gosh isn't doing things with mysql great" rather than a more truthful "we have appeared to supports lots of dbs for a long time" and a more respectful "using different dbs is a common choice that different environments might make"13:33
cdentI think the proposal can and should be a) much shorter, b) more forward looking about ways "out"13:34
cdentthere's no need to shame people for having got it "wrong" because they didn't13:34
mordredsdague: hrm. I verify that oslo.db is defaulting to TRADITIONAL. now I'm curious as to what went further wrong there13:34
sdaguecdent: if you want to write an alternative, feel free.13:34
johnthetubaguycdent: I saw this more as shaming ourselves for not telling people its been ages since we did the work to support anything else13:35
cdentsdague: I was going to ask you about that, but haven't rolled around to that part of my day yet. It crossed my mind that that would probably be a lot easier. At the same time, having this kind of discussion is, I think, pretty important because it helps reveal biases and attitudes more completely than simply reviewing proposals. I can still write an alternate if that seems like a good idea, but it may be more than 213:36
sdaguebecause I feel like my process of trying to reduce the complexity of a bunch of problems we want solved, that are too complicated for anyone to take on, is getting responded with "but what we really want is a detailed plan for engineering proposal that's the minimum orgs need to fund to keep this complexity"13:36
*** thorst is now known as thorst_afk13:36
*** johnthetubaguy has left #openstack-dev13:37
cdentI didn't say that myself. I just said we should punt this to the board as an example of a shortfall. Not with a detailed engineering plan. We don't need that.13:37
*** blancos has joined #openstack-dev13:37
openstackgerritdane-fichter proposed openstack/governance master: Add Queens goal split out tempest plugins  https://review.openstack.org/36974913:38
cdentI did, however, say that the statement that "this is complex" doesn't seem to be as well understood as it should be.13:38
sdaguecdent: I disagree, that's actually the sticking point. That's been the constant come back "tell us what the problems are in detial"13:38
cdentfrom who13:38
sdaguein the review, in the room13:38
sdagueright now13:38
mordredcdent: everyone who is opposed to the idea of deprecation13:38
sdaguemordred: ++13:38
cdentthat's not at all what I heard13:38
sdague"define complex"13:38
cdentwhat I heard in the room is people saying "we've got postgres already and switching will be hard"13:39
sdaguewhich was step 2, that suse is exploring13:39
*** achampion has joined #openstack-dev13:40
sdaguethat was one bit, the other was "we would not have done what we'd done over the last 12 months if we knew this wasn't supported"13:40
cdentI guess to some extent on the review is "this is being supported by assertions of complexity, show me the evidence" but that seems rather fair when we have existing passing tests using pg13:40
*** johnthetubaguy has joined #openstack-dev13:40
*** johnthetubaguy has left #openstack-dev13:41
sdaguecdent: passing tests has nothing to do with reducing the complexity of a bunch of unsolved problems13:41
*** johnthetubaguy has joined #openstack-dev13:41
*** johnthetubaguy has left #openstack-dev13:41
mordredyah. that13:41
sdagueI litterally am sick to death of "but it's just a gate job"13:41
mordredthe root problem from my POV is that there are no PG humans actively involved upstream13:41
fungibacking up a bit, we're not currently expending effort to "support" postgres so it's already at risk of breaking if people use it. regardless of whether we might entertain offers to help us "support" more than mysql in the future, can we just say that (and correct our documentation where it claims we're supporting something we haven't been)?13:41
cdentI don't dispute that. And as I keep saying: I'm happy to see the docs change13:41
*** kirotawa1 has joined #openstack-dev13:41
sdaguehaving gone through that gate job with a fine toothed comb (and built it in the first plac) the amount of differential testing that it exposes is really really smal13:42
cdentI _want_ to see the docs change13:42
fungiwe're not saying "we're going to take away postgres support" we're saying "we haven't been supporting postgres, our documentation was wrong, and we're really sorry you wound up coosing to use it based on incorrect information"13:42
*** mhickey has joined #openstack-dev13:42
cdentI'll write up an alternative, and try to make it more straightforward.13:42
*** zzzeek has quit IRC13:43
*** diablo_rojo has joined #openstack-dev13:43
mordredfungi, cdent: well, we should be clear that we're _thinking_ about taking away postgres support - we haven't decided to do that, and may not, but it's important that people understand it's a real consideration13:43
sdagueright13:43
sdaguebecause there is this assumed "forever" bit today13:44
fungii think it totally depends on your definition of te word "support"13:44
mordrednot to me it doesn't ... I believe one of the possible outcomes is "make openstack take an active role in the management of your database resources"13:45
sdaguemordred: ++13:45
*** ram5391 has joined #openstack-dev13:46
fungiit doesn't seem to me like we're supporting postgres even now, but perhaps the minimal level of testing we have for it counts as support to some people13:46
mordredwell. that and the fact that the docs say we support postgres explicitly13:46
mordredI think that may be the largest smoking gun on people getting the idea we support it ;)13:47
*** dimtruck is now known as zz_dimtruck13:47
sdaguemordred: right13:47
sdaguechris read the manual section alloud for ocata in the room where it says that13:47
mordredbut there's  basic "SQL statements execute" - which is regression prevention - then there's "orchestrating maint tasks in an online fashion" - which would imply active design13:48
fungii don't think we've had a policy in the past about what the documentation reviewers are allowed to approve as a statement of support for some technology without conferring with the teams who would actually be the ones making support decisions13:48
sdaguefungi: sure, there are lots of ways we got into this13:48
*** vnogin has quit IRC13:48
mordredyup. we can pass the blame around broadly13:48
fungidid nova's core reviewers claim support for postgres, or did someone work out how to set up postgres, propose an addition to the install guide and documentation reviewers approved it?13:48
mordredI'm sure it's my fault in some number of ways13:49
*** zzzeek has joined #openstack-dev13:49
sdaguefungi: I got it working in the gate in devstack, and got it voting, 4 years ago13:49
sdagueand from that, it filtered through to "supported"13:49
sdagueorganically13:49
mordredin fact, I think I was one of the ones who argued in favor of sqla back when the argument was sqla vs. redis13:49
mordredso ... sorry13:49
fungiwell, thank you for not choosing redis ;)13:50
*** bobmel has joined #openstack-dev13:50
*** limao has joined #openstack-dev13:50
sdaguefungi: but regardless of how we got here, we also need to understand what a wind down looks like13:50
mordred++13:50
*** READ10 has joined #openstack-dev13:50
sdaguebecause since the first time deprecating pg came up 2 years ago, we're probably about 4 - 6 person months of effort in discussions and arguments13:51
*** johnthetubaguy has joined #openstack-dev13:51
sdagueif the cost of removing something that is used at a low rate is that high13:51
sdaguethe barriers to bringing new things in are going to be even higher, because no one wants to have to do the remove fight13:51
fungicompletely agree there13:51
sdaguewhich is a giant chilling effect on trying experiments13:51
mordred++13:52
*** lucasagomes is now known as lucas-brb13:52
*** jamesmca_ has quit IRC13:52
mordredI also think we need, not an "engineering plan" - but we need to understand what the pg supporters could do to make us feel honestly warm and fuzzy about keeping the complexity13:53
*** jamesmca_ has joined #openstack-dev13:53
*** limao_ has joined #openstack-dev13:53
*** vnogin has joined #openstack-dev13:53
mordredsdague: made a list above - I donm't think it's a complete list from my end, because it doesn't cover forward-looking design concerns13:53
persiaIs there any means to adjust the definitions of the identities concerned, so that the pg supporters are the pg maintainers, without needing to be part of the "us" used above?13:53
sdaguepersia: it's not about a driver in isolation13:53
fungiso anyway, my point about the documentation is that we probably need more people reviewing docs specifically with the goal of identifying things we wouldn't want to commit to supporting long-term so they can be wrapped in eye-catching "experimental" admonitions13:54
ttxideally you want those resources to be embedded into existing support teams13:54
sdaguepersia: if it was completely hidden behind a full driver abstraction, it would be different13:54
ttxnot just be "the pgsql person"13:54
sdagueright, people need to be all through the code13:54
*** mriedem is now known as mriedem_afk13:54
*** bobmel has quit IRC13:54
*** baoli_ has joined #openstack-dev13:55
persiasdague: No, it's about a huge mass of work: it's just that in most reprititions of the conversation there are statements like mordered's "make us feel honestly warm and fuzzy", and most of the anecdotes I've heard about pg users are that they are downstream-ish.  I just wondered if there was a way to capture them.13:55
*** limao has quit IRC13:55
*** ansmith has quit IRC13:55
mordredpersia: actually, I think the problem is that the pg supporters are not currently part of the 'us' if they _were_ part of the us, we'd collectively feel like we have the resources to do both things13:55
*** donghao has joined #openstack-dev13:55
sdaguemordred: ++13:55
sdagueright, if you are just going to be downstream, then you get what upstream gives you13:55
persiamordred: Right.  Hence my question: can we make the pg supporters part of "us"?13:55
mordredbut right now, 'us' only includes people with the mysql background, so 'our' opinion of our ability to do well by pg folks is low13:55
sdaguethat's kind of the definition of streams13:55
mordredpersia: yes. I agree - that is ultimately the thing that needs to happen for future pg work in openstack to be successful13:56
sdagueI also think about this a lot - https://blogs.gnome.org/markmc/2014/06/06/an-ideal-openstack-developer/13:56
*** baoli has quit IRC13:57
*** snica is now known as snica_away13:57
*** bobmel has joined #openstack-dev13:58
*** dtantsur|brb is now known as dtantsur13:59
*** donghao has quit IRC14:00
*** salv-orlando has joined #openstack-dev14:00
*** iogg has quit IRC14:02
*** iogg has joined #openstack-dev14:03
*** jwcroppe has joined #openstack-dev14:04
*** djohnsto has joined #openstack-dev14:05
sdaguebecause if we continue to ask the world of new developers, our entire onboarding and learning model will be broken14:06
*** jamesmca_ has quit IRC14:07
openstackgerritChris Dent proposed openstack/governance master: Document lack of posgresql support  https://review.openstack.org/46558914:08
*** zz_dimtruck is now known as dimtruck14:08
cdentsdague, mordred, fungi ^: same as sdague's version in action, but shorter14:08
cdentand with a typo in the commit summary orz14:08
openstackgerritChris Dent proposed openstack/governance master: Document lack of postgresql support  https://review.openstack.org/46558914:08
*** dtardivel has joined #openstack-dev14:09
*** ansmith has joined #openstack-dev14:09
sdaguecdent: you forgot the operator community14:10
*** bobh has joined #openstack-dev14:11
*** AnilV4 has quit IRC14:11
*** awaugama has joined #openstack-dev14:12
cdentthat's kind of intentional. we're making a statement about the ATC community. also we already know from forum discussion that we actually don't have a very good view onto the operator community; only the operator community that happens to talk to us14:12
sdaguewe do have many views14:13
sdagueit's not just the survey14:13
sdaguethe posts and answers on openstack-operators are at least 20 to 1 on the mysql side14:14
openstackgerritChris Dent proposed openstack/governance master: Document lack of postgresql support  https://review.openstack.org/46558914:14
sdagueevery operators mid cycle has sessions devoted to mysql best practices, there has never been one on pg14:14
cdentsdague: yeah, I know that, but that's not all that relelvant for this discussion14:14
sdaguecdent: it's completely relevant14:14
cdentwhat matters is that we're not doing things with it (either testing or using) at the atc level14:14
cdentthe rest of the information is extraneous14:15
sdagueI don't understand why the level of share and expertise and getting real answers isn't relevant here14:15
sdagueno, I completely disagree14:15
sdaguethis is about ecosystem14:15
sdaguethe whole thing matters14:15
cdentI know we disagree, that's why I made an alternate :)14:16
cdentFrom my standpoint what matters is that we don't have people who want to care and feed postgres. Not that we do have people that want to care and feed mysql. That's well known.14:17
cdentIn order for the de-documenting situation to change, we need people to care and feed postgres. If we don't get that, then the path continues.14:17
cdentIf we do, we reconsider14:18
*** itzikb has quit IRC14:20
*** paramite has quit IRC14:21
*** gamado has quit IRC14:22
*** marst has quit IRC14:23
cdentsdague: just in case it's not clear, I didn't write the alternate because I want it to be the one to be published, but because hopefully it makes my concerns with the other one more clear14:24
sdaguemaybe, but the thing that seems to be clear is not feeling that operator data is relevant, which boggles my mind :)14:25
Anticimexmordred: the bias i mentioned was my own. i see that i didn't make that very clear though.   i.e. my own biases in the way i from the outside read & interpret from threads, meetings and reviews the situation14:25
*** xarses_ has quit IRC14:26
*** tuan_luong has quit IRC14:26
*** gszasz has quit IRC14:27
*** ihrachys has quit IRC14:27
*** jprovazn is now known as jprovazn_afk14:27
*** cdub has quit IRC14:27
cdentsdague: I'm not dismissing operators as a class. In fact I'd argue that I'm being more concerned about the invisible operators. what I'm trying to state, though, is that there are a smaller number of factors in the decision than your version asserts:14:27
*** jprovazn_afk has quit IRC14:28
cdentit's not about mysql is supported by most people14:28
cdentit's about posgresql is not getting support14:28
*** dimak_ has quit IRC14:28
cdentthe mysql part simply isn't relevant to what we do with posgresql14:28
*** jwcroppe has quit IRC14:28
cdentif we make it about mysql then it is very easy for the document to become a contentious thing in which people want to flame14:29
cdentand that's not useful14:29
*** jwcroppe has joined #openstack-dev14:29
sdaguesupport includes not only upstream developer support, which is all theory, and includes no actual large running systems14:29
cdentthe simple truth is: we're not testing and exploring postgresql sufficiently to currently declare it supported14:29
cdentin fact the whole doc could be just that one phrase14:29
*** marst has joined #openstack-dev14:30
cdentI think we've established there are plenty of running postgres deployments, so I'm not sure what you're trying to say when you say "no actual"?14:31
*** Guest24103 is now known as mgagne14:32
sdagueno running systems on the dev side14:32
*** mgagne has quit IRC14:32
*** mgagne has joined #openstack-dev14:32
sdagueI didn't mean to say there are no pg deploys14:32
*** yamamoto_ has joined #openstack-dev14:32
*** jwcroppe_ has joined #openstack-dev14:32
*** gyee has joined #openstack-dev14:33
*** zackf has joined #openstack-dev14:33
*** MattMan_1 has quit IRC14:33
sdagueI'm saying support in a community is more than just devs, it's also operators cross supporting each other in various scenarios. Some of which is tribal knowledge there, and some gets back propogated to help change data models and optimizations in the platform14:33
*** MattMan_1 has joined #openstack-dev14:33
*** lucas-brb is now known as lucasagomes14:33
*** jwcroppe has quit IRC14:34
cdentyes, I understand that14:34
cdentbut I disagree that the presence or lack thereof of that community is an _actual_ direct factor in this decision14:35
*** iogg has quit IRC14:35
*** jamesmca_ has joined #openstack-dev14:36
*** treiz has quit IRC14:36
*** yamamoto has quit IRC14:36
cdentit's nice information, good to know, but distracting14:36
*** anilvenkata has quit IRC14:36
*** ioggstream has joined #openstack-dev14:36
cdentsometimes that context is extremely useful (and I'm usually very much in favor of it), but in this case, it is sending people off on tangents14:36
*** vnogin has quit IRC14:36
*** treiz has joined #openstack-dev14:37
*** vnogin has joined #openstack-dev14:37
sdagueok, well that least is a clear axis of disagreement.14:37
*** gamado has joined #openstack-dev14:37
cdentIf the goal is to make mysql the one true db, it is very useful info. If the goal is to use the database abstraction layer to the fullest including the story is using the current state of the universe as an explanation for how the universe ought to be, which is bad pool.14:38
Anticimexsdague: there's a selection bias in the mysql vs pg thing.  i believe operators that choose pg does so because they have expertise on it already.  many shops do, obviously.  therefore the ones that choose to use pg are by a bit of selection bias probably more senior than the average mysql user14:38
*** slaweq has joined #openstack-dev14:39
*** kazsh has joined #openstack-dev14:39
Anticimexsince it's an basically active choice to pick postgres since it's so very narrowly mentioned and documented, my gut feeling is that ~95% of everything openstack documentation kind of assumes mysql14:39
sdagueAnticimex: that's definitely possible. And if it's clear that you might need to be doing some picking up on your own, and you are cool with that, so be it14:40
*** armax has joined #openstack-dev14:40
*** kazsh has quit IRC14:40
Anticimexand i don't think this a 'complex' issue, but a multi-dimensional one.  there's the dimension of developers and lack of pg skills in dev community (which probably gets excarbated due to lack of a range of good mysql settings, where pg gets incorrect blame among devs)14:40
*** kazsh has joined #openstack-dev14:41
*** ram5391 has quit IRC14:42
Anticimexthen there's, at least for me, a dimension of intention among test coverage and data correctness (not said as pg fan, but as operator who really would be hurt by database corruption etc).  this dimension obviously does not require postgres14:42
*** ansmith has quit IRC14:42
Anticimexand then i think i saw what could be a third or fourth dimension but those two are the ones i see as major14:42
sdagueduring the in room session when folks in the pg camp spoke up, there was definitely shock that large sites were running on mysql. Like they didn't really believe me when I said it. So I think there is also some tribalism in there which leaks out.14:43
sdagueAnticimex: I definitely agree that data corruption is bad14:43
Anticimexwell, migration paths for existing users (depends on intetion/direction and eventual actual delivery of whatever is missing for "supporting" pg), unclear documentation etc (easily fixable once intention/direction is concluded), are other issues14:44
sdagueI think zzzeek figured out one more flag we need to help there, but we did lock things down14:44
sdagueit's not quite the wild west it once was14:44
*** snica_away is now known as snica14:44
Anticimexsdague: yeah i attended the forum session as well14:46
sdagueAnticimex: ok, cool, my irc to meatspace mapping not all that great :)14:46
Anticimexi have lack of insight into how many gate tests are doing onesided testing etc14:46
Anticimexso i'm blind there14:46
Anticimexsdague: yeah i'm quite a lurker also14:46
sdaguethere are zero gates of base iass on pg14:47
sdaguethat was turned off over 6 months ago14:47
Anticimexbut i react to the allusion that pg tests breaks things for devs because i don't see that actually substantiated14:47
Anticimexso i'd be super happy if we could enumerate the "what's missing" list14:47
Anticimexor "what's painful"14:47
Anticimexthat mordred began on14:47
sdagueAnticimex: sure, I provided 3 examples above14:48
sdagueplus the zero downtime keystone plan14:48
Anticimexi think zero downtime is a red herring but that's another discussion i think14:48
Anticimexor maybe not14:48
sdagueAnticimex: why is it a red herring?14:48
*** slaweq has quit IRC14:48
Anticimexperhaps it's a question of definition of "zero downtime"14:48
Anticimexi may be wrong )14:49
Anticimexgoogle SRE book says 100% uptime usually isn't worth it14:49
sdaguekeystone actually needs to be zero downtime if you are going to have a cloud without service windows14:49
Anticimexyeah but who has cloud without any type of service window?14:49
sdaguepublic clouds14:49
Anticimexaws has service windows14:50
Anticimexfor computes at least whenever xen breaks14:50
*** gkadam has quit IRC14:50
*** ociuhandu has joined #openstack-dev14:50
sdaguethey don't have a change window for their auth system14:50
fungithey don't live migrate instances off computes, upgrade the hypervisors and migrate them back on?14:50
sdaguefungi: well, they now live patch xen14:50
fungihah14:51
Anticimexanyway, the scope of the keystone zero downtime thing implies some dev/test on postgres as well then if it really requires some db-engine specific triggers etc14:51
sdagueso they don't take down time for that any more14:51
fungithat's gotta be _really_ fun ;)14:51
Anticimexfungi: aws is: "hello dear useryour instances are gonna get shut off and hopefully booted again on XXXX"14:51
sdagueAnticimex: right, which basically takes it off the table if we're saying pg is actually supported14:51
Anticimexor "your instance will get wiped because we're decomissioning the hw" :P14:51
*** tobberyd_ has joined #openstack-dev14:52
Anticimexsdague: yeah but i think that's going at the issue of pg deprecation from the wrong angle.14:52
sdagueAnticimex: that is very different from instances failing to build because keystone is in the middle of an upgrade14:52
sdagueand fails token calls14:52
*** tobberydberg has quit IRC14:52
Anticimexan etherpad for enumeration?14:53
sdagueAnticimex: well, if someone of that opinion wants to solve the keystone zero downtime problem, again I'm happy to stop caring14:53
Anticimexyeah, which comes back to communication14:54
sdaguemy issue remains lots of people saying "it's not bad", "well here are some things no one is tackling because of complexity, and this makes it worse"14:54
Anticimexi think most operators that have picked pg assumed it was "supported"14:54
sdagueAnticimex: right, and they were wrong14:54
sdagueand we have to communicate that fact14:54
fungi(because our documentation was wrong, but yes)14:54
Anticimexso i'm all for communicating accurately what the level of support it, but conditioning path forwards based on a set of possible results/outcomes14:54
sdagueand then ponder what to do with previous mistakes14:54
Anticimexultimatum-like i guess14:54
fungis/was/is still, unfortunately/14:55
sdaguefungi: right, we definitely gave them bad info14:55
Anticimexbut i don't think it is wrong of openstack to support pg14:55
Anticimexand i'm not sure a consumer of openstack can be put to blame for what the docs says either14:55
Anticimexthey were allowed to pick pg, they happily did.  *shrug*14:55
sdagueAnticimex: sure, again, if people that cared were solving all the problem that are made complicated by it, I would actually have no cares14:55
*** piyushks has joined #openstack-dev14:55
fungii don't think we blame them, but at the same time it's being asserted that we can't afford to actually make good on what the documentation promised there14:56
*** tobberyd_ has quit IRC14:56
Anticimexfungi: nod and i agree it's high time to communicate this14:56
cdentthis is why I want to be sure the document doesn't talk about mysql a great deal. If it does, we are making a statement that the path forward is to only support mysql, rather than fixing the fundamental problem: getting people who care about stuff that people use.14:56
cdents/fixing/talking about/14:57
Anticimexbut i think communicating "we're killing it!" already is early (yeah, message changed but that was the original premise in the discussion)14:57
fungijust wishing that what the documentation says would become reality is not enough, as much as that might be nice if it worked tat way14:57
sdagueAnticimex: right, the message did change, based on feedback14:57
Anticimexi would be very satisfied if the current communication is among the line sof: we're havign the following clear discrepancies / deficiencies / deltas between mysql and pg support so keep this in mind, and we're considering removing pg support in xx time unless these are being addressed14:58
Anticimexs/current//14:58
Anticimexsomething like that seems fair to me anyway14:58
*** salv-orlando has quit IRC14:59
Anticimexperhaps word the consideration for removal as punted to xx time in the future.  splitting hairs perhaps?  but like, "we'll re-evaluate the situation at XX ATC meeting" or sth14:59
Anticimexsdague: nod15:00
*** salv-orlando has joined #openstack-dev15:00
*** epopt has joined #openstack-dev15:00
sdagueAnticimex: in the current proposal, what are your objections?15:00
sdagueI guess that's where I'm having issues with because I thought the current proposal was that15:00
Anticimexi have to reread. i'll check cdents too15:00
*** ociuhandu has quit IRC15:01
*** gamado has quit IRC15:01
*** rcernin has quit IRC15:04
*** dsariel has quit IRC15:04
*** salv-orlando has quit IRC15:04
Anticimexsdague: the aura of the current wording in 427880 first two paragraphs is "everyone's using mysql so you should too", 3rd paragraph is ~"some projects are really sloppy with sql and pg breaks our devs work", 4th one begins addressing the documentation issue, the warning message is only communicating current state, and doesn't refer to the bucket list of things to do to reconcile the level of suppo15:06
Anticimexrt. the resolution then proceeds to ...15:06
Anticimex... detail that migration investigation controls future decision on killing it (presumably, if it is possible to migrate out it should be killed)15:06
Anticimexin summary the intent of the resolution as it reads to me is "we want to kill pg"15:07
cdentAnticimex: that's how it reads to me too15:08
*** ansmith has joined #openstack-dev15:12
*** kobis has joined #openstack-dev15:13
*** salv-orlando has joined #openstack-dev15:14
*** gamado has joined #openstack-dev15:17
*** tobberydberg has joined #openstack-dev15:19
*** kobis has quit IRC15:19
*** dsariel has joined #openstack-dev15:20
*** hongbin has joined #openstack-dev15:22
*** salv-orlando has quit IRC15:22
*** felipemonteiro has joined #openstack-dev15:22
*** dizquierdo has joined #openstack-dev15:22
*** tobberydberg has quit IRC15:24
*** kobis has joined #openstack-dev15:26
Anticimexcdents text is much more condensed in spelling out why this resolution is happening, and has the same warning test proposal. keeps the same recommendations but adds also a short paragraph about way forward for keeping PG15:27
*** kobis has quit IRC15:27
Anticimexi think that last part is very thin, i'm missing a more specific problem set somewhere15:27
*** qlixed has joined #openstack-dev15:28
*** rpittau has quit IRC15:28
*** armax has quit IRC15:28
cdentyeah, I would have said more there except I'm not entirely sure what needs to (or  can) be said. I think enumerating all the issues has happened in discussion but not on the documents. I'm not sure it is entirely necessary as the required outcome is the same: either people don't care and we kill pg, or they do and we don't.15:29
Anticimexso i'm not sure how these tc resolutions work, clearly i'm not TC or anything, so perhaps TC is within its right to decide what to do with openstack and that is fine. but to me it is quite significant and important that this is done on honest and transparent grounds15:29
openstackgerritSean Dague proposed openstack/governance master: Declare plainly the current state of Posgresql in OpenStack  https://review.openstack.org/42788015:30
sdaguecdent / Anticimex thank you for feedback, hopefully the new draft addresses much of that15:30
Anticimexcdent: right, and as a related feedback on that, i'm missing the communication towards operators/users about the lay of the land15:30
Anticimexthe warning only says "stay away"15:30
Anticimexor well, "be warned" perhaps is more appropriate.15:31
sdagueAnticimex: how would you communicate the current state of the world15:31
Anticimexi don't know yet.  let's see your new 42788015:31
*** donghao has joined #openstack-dev15:33
jd_who else is pbr-core and can merge the latest Sphinx fix?15:36
*** hieulq_ has joined #openstack-dev15:38
*** donghao has quit IRC15:38
Anticimexsdague: quite a rewrite, and one step back in push for kill15:38
*** psachin has joined #openstack-dev15:38
Anticimexbut i wonder if this resolution isn't subordinated to a TC intention of what do with databases, which was biefly mention in this discussion a bit back15:39
*** donghao has joined #openstack-dev15:39
Anticimexi.e. pros/cons on having multi-engine db support, as the first question15:40
Anticimexif yes, then what does that depend on and what are the deltas, if no, well, then the discussion is much simpler15:40
*** gomarivera_ has joined #openstack-dev15:40
*** vhosakot has joined #openstack-dev15:41
*** dsariel has quit IRC15:42
Anticimexthe preoposed resolution(s) seems to walk this a bit backwards, ie is reactive rather than prescriptive15:45
dimsjd_ : done15:45
jd_dims: <315:45
dimsjd_ : at your service :)15:46
dimscdent : we don't want folks to ask folks to show up with postgres skills, patches, ci jobs etc do we?15:46
dimssdague : ^15:46
cdentdims: we don't?15:47
*** arslanq has joined #openstack-dev15:47
dimscdent : i don't see a shout out to the readers of the resolution to come help in upstream hence asking15:48
*** sree has joined #openstack-dev15:48
cdentmy alternate includes a 4th todo statement of "make this the board/foundation's problem"15:49
Anticimexi think it's a bit backward and would be much easier if agreement was made that the pros outweigh the cons on going to single-sql-engine15:49
arslanqhi guys i just deployed openstack devstack (Master)..I am unable to access horizon...when i checked the httpd service it is listening like: https://pastebin.mozilla.org/902199915:49
Anticimexor well, it would also be more clear if it was concluded that multi-engine support is worth its money15:49
arslanqalso i cant do "screen -x"15:49
cdentdims: because we've been asserting all over the place that the people already reading this stuff aren't the ones who have the solution15:49
dimscdent : lines 61-65?15:50
clarkbarslanq: screen is no longer used by default (so screen behavior is expected)15:50
cdentdims: 35-39 on this one https://review.openstack.org/#/c/465589/3/resolutions/20170517-document-lack-of-postgres-support.rst15:50
Anticimexsingle-engine con: risk of engine suddenly disappearing or getting bought and closed down (or similar)15:51
arslanqclarkb: whats about the horizon issue? and also if there is no screen then how can i check/restart services?15:51
clarkbarslanq: services are managed with systemd by default now so you use systemctl and journalctl to manage services15:52
*** galstrom_zzz is now known as galstrom15:52
clarkbI dont know about horizon, currently rebooting home network gear so camt quite check yet15:52
dimsack reading that carefully cdent15:52
*** caboucha has joined #openstack-dev15:53
*** sree_ has joined #openstack-dev15:53
cdentdims: it's meant as a way to think about alternate ways of saying the same stuff, not as a ready-to-use15:53
dimscdent : sorry i was reading the other one15:53
*** lucasagomes is now known as lucas-afk15:53
*** sree_ is now known as Guest3926315:53
*** paramite has joined #openstack-dev15:54
arslanqclarkb: ok....any workaround for now? i need it now15:54
mordredAnticimex: ah - gotcha (re bias statement - working chronologically through scrollback, haven't gotten any further yet)15:55
dimscdent : i like yours better. will drop a note about the warning in review15:55
*** sree has quit IRC15:55
*** gomarivera_ has quit IRC15:55
Anticimexdims: if the objective is to sneak to single-engine usage, i guess it's counterproductive to ask for all those things?  which is why it seems to me more straighforward and simplified to work out multi-vs-single engine goal first15:56
*** iyamahat has joined #openstack-dev15:56
clarkbarslanq: is the horizon service enabled? thats first thing I would check, then from there check if there is a vhost for it15:56
*** sree has joined #openstack-dev15:56
clarkbarslanq: then check the logs for horizon assuming everything else checks out15:56
arslanqclarkb: i don't see any logs for any service except ovs-vswitch in /opt/stack/logs15:57
clarkbarslanq: right you have to use journalctl now15:57
clarkbarslanq: it should be documented let me find the fiel15:58
*** Guest39263 has quit IRC15:58
*** blancos has left #openstack-dev15:58
Anticimexmordred: by the way, based on what sdague is listing, the choice for single-sql-engine openstack is clearly pretty obvious15:58
clarkbarslanq: doc/source/systemd.rst15:58
*** gouthamr_ has joined #openstack-dev15:58
arslanqclarkb: you wanna take a look to this https://pastebin.mozilla.org/902200015:59
mordredAnticimex: so much scrollback - I agree and disagree with too many things all at once!!!15:59
*** gouthamr has quit IRC15:59
Anticimexbut it's not at all as clear that single-engine is the better way forward, i don't know what to think, i would need lots of facts and pros/cons to form a proper opinion :)16:00
clarkbarslanq: cool that implies horizon is running, next step is checking the logs with journalctl as documented in the file I posted16:00
arslanqok let me check that and tell you16:00
dimsAnticimex : right, that's why i was asking that question16:00
Anticimexand multi-engine support could still be conditionalized, so there's no reason that such a discussion would deadlock or leave devs out to dry etc16:00
*** lpetrut has quit IRC16:01
dimscdent : some feedback on the warning16:01
dimsdhellmann : have some time today to chat about the containers / publish thread?16:02
cdentdims: the warning is copied verbatim from sdague's version, but will give it a look see16:02
Anticimexi also think people could be a bit more objective if put to evaluate the pros/cons of multi-vs-single engine16:02
arslanqclarkb: i am not sure what is the key word for horizon like for nova-compute it is n-cpu....never mind my stupid question16:03
mordredAnticimex: I believe there are even some base philosophical intents that are not necessarily agreed on yet. such as - should openstack take an active role in managing and administering the databases it needs, or should it assume that there is a black-box DB url that is being managed16:03
*** sree has quit IRC16:03
mordredone allows for providing more help to the operator at the expense of making things harder for the teams who do have a set of people who want to manage the database tier16:04
*** sree has joined #openstack-dev16:04
mordredand the more openstack is in the business of taking an active role in admin style tasks, the more multi-db becomes a liability rather than a strength16:05
mordredwhereas if the db tier is a blackbox that sql is sent to, the relative cost for multi-db is low, but the amount that each operator is expected to tend to is higher16:05
*** mriedem_afk is now known as mriedem16:05
Anticimexmordred: i think that's a much more fruitful topic area to discuss, rather than driving to there in reverse16:07
arslanqclarkb: these are the service which are enabled : https://pastebin.mozilla.org/902200316:07
Anticimex( sdague has provided two data points that indicates that mysql folks asks twice the amount of questions ;) )16:08
Anticimexmordred: that seems to make up aspects of a multi-vs-single discussion16:08
*** ihrachys has joined #openstack-dev16:08
mordredAnticimex: maybe I'll start a mailing list thread on that topic area16:08
Anticimexare there any projects that have asked for this?16:08
*** hieulq_ has quit IRC16:09
Anticimexsounds like a good start i guess16:09
mordredAnticimex: and also, you made a point earlier that the people who chose postgres tend to do so because of the existence of postgres expertise already - whereas mysql is the default16:09
*** hieulq_ has joined #openstack-dev16:09
mordredso we're more likely to get people in the mysql ecosystem who do not know mysql best practices16:09
Anticimexyeah that's fairly clear i think16:09
mordredAnticimex: I know that I have received complaints from operators that openstack is a bucket of parts that still expects the operators to handle the hard bits16:10
Anticimexmordred: i just gave a comment in the same direction to cdents alternative resolution proposal, https://review.openstack.org/#/c/46558916:10
mordredand that we should provide much clearer and managed integrations with the standard operator needs16:10
*** hieulq_ has quit IRC16:10
*** gyee_ has joined #openstack-dev16:11
mordredthis is at odds with early-on operator desires that we stay out of their way because they already had established operatational patterns16:11
*** pcaruana has quit IRC16:11
mordredI think the shape of the ecosystem has changed since then, but the pattern of engaging has not16:11
Anticimexi think experienced mysql or pg shops would rather do it themselves and have openstack focus on something they don't already have expertise in16:12
mordredyes. I agree16:12
Anticimexbut for the less experienced.. well, openstack is probably "yikes"16:12
mordredbut on the other hand, I think the number of shops with experienced mysql or pg teams is an unfortunately small percentage of the shops deploying openstack16:12
mordredyup16:12
*** hieulq__ has joined #openstack-dev16:13
Anticimexit's not clear that "managed mysql" or "refernece architecture" (are there any well-known success stories of 'reference architectures'? from my personal experience they're usually crap :D)16:13
Anticimexi honestly believe mysqls lack of awesome defaults complicates it a little for deployers.  also the almost dangerous suggestions that you just apt-get install galera and all is fine and dandy16:14
* Anticimex is certainly not going to suggest that openstack drop mysql, so read it correctly :)16:15
mordredyah. this is why I think it's potentially important for openstack to take a stronger hand - because defaults out of the box are not sufficent16:15
Anticimexif you're setting up public cloud you need expertise IMHO16:15
Anticimexi think galera is overkill (it bit me)16:16
mordredyou do - but honestly we have folks running openstack public clouds with 4-person ops teams16:16
Anticimexit seems to skid a bit on ACID etc, at least master/master16:16
*** ociuhandu has joined #openstack-dev16:16
Anticimexmordred: yeah, and i'm not against simplifications that also address their needs, not at all16:16
mordredso the more we say "clearly your db team should handle that" is the more we're making it harder for those teams to be successful - potentially16:16
Anticimexthere's no inherent value in complicating things at all16:17
mordredAnticimex: and yes - galera is an excellent example of where openstack needs to be deployment architecture aware - it turnsout to successfully galera, you need to behave in certain ways16:17
*** matrohon has quit IRC16:17
mordredthe way you write an application for a galera cluster, vs a master-slave async replication setup, vs an active/passive failover are all a bit different16:18
Anticimexyeah16:18
*** gamado has quit IRC16:18
mordredand the answer as a db consultant is often "you need to structure your application in the following way" not "you need to do these things as an admin"16:18
Anticimexto me galera seems a poor fit for openstack typical use case, but a good fit for geo/globally distributed sql16:18
Anticimexyeah16:18
*** hieulq__ has quit IRC16:18
Anticimexseems obvious to me you need dto be aware that galera doesn't really give you strong ACID. you need to beware and take care16:19
Anticimexgotta go, sorry for all the ramblings here :)16:19
Anticimexlooking forward to the ml thread16:20
mordredAnticimex: thanks for the rambling!16:20
*** gyee has quit IRC16:20
*** bobmel has quit IRC16:20
*** bobmel has joined #openstack-dev16:20
*** jpich has quit IRC16:21
*** snica has quit IRC16:22
*** ociuhandu has quit IRC16:25
*** bobmel has quit IRC16:27
*** gouthamr_ has quit IRC16:28
*** marst has quit IRC16:28
*** aarefiev is now known as aarefiev_afk16:31
*** sree_ has joined #openstack-dev16:32
*** sree_ is now known as Guest1642016:32
*** harlowja has joined #openstack-dev16:32
*** Guest16420 has quit IRC16:33
*** sree has quit IRC16:34
*** gamado has joined #openstack-dev16:38
*** galstrom is now known as galstrom_zzz16:38
*** kazsh has quit IRC16:38
arslanqclarkb: any update?16:39
clarkbarslanq: I still think you need to look at logs16:40
*** ltomasbo is now known as ltomasbo|away16:40
clarkbarslanq: horizon isn't in the enabled systemd services so I would check apache and if nothing there then check the devstack log itself16:40
*** gamado has quit IRC16:42
arslanqclarkb: i just checked "/var/log/httpd/horizon_access.log" : https://pastebin.mozilla.org/902200916:43
arslanqthese are few lines from bottom16:43
arslanqclarkb: i successfully launched VMs from CLI16:44
clarkbthat looks like logs from placement api and keystone leaking into horizon16:44
clarkbso can't really tell if anything horizon is running from that16:44
*** eharney has quit IRC16:44
*** armax has joined #openstack-dev16:48
*** eharney has joined #openstack-dev16:48
fungiis horizon maybe disabled by default in devstack now? we stopped enabling it in our default devstack-gate/tempest jobs right?16:49
*** bobmel has joined #openstack-dev16:51
*** dtantsur is now known as dtantsur|afk16:54
*** gianpietro has quit IRC16:55
*** gouthamr has joined #openstack-dev17:01
*** fragatina has joined #openstack-dev17:02
*** fragatina has quit IRC17:02
*** fragatina has joined #openstack-dev17:03
*** ioggstream has quit IRC17:03
dhellmanndims: I'm eating lunch, but maybe in 15-20 min?17:03
*** dimtruck is now known as zz_dimtruck17:03
*** zz_dimtruck is now known as dimtruck17:04
*** donghao has quit IRC17:04
*** donghao has joined #openstack-dev17:04
*** donghao has quit IRC17:12
*** mhickey has quit IRC17:12
sdaguefungi: it's still on by default in devstack17:13
sdaguebut we could turn it off in testing, I'm not sure there are real tests there17:13
*** jwcroppe_ has quit IRC17:13
fungiahh, i was misremembering then17:14
*** fragatina has quit IRC17:16
sdagueI usually turn it off locally to safe time as it's about 60 seconds additional install time17:17
sdaguebut, people like having the interface to poke with, so on by default still makes sense17:18
*** felipemonteiro has quit IRC17:18
*** gianpietro has joined #openstack-dev17:19
*** Guest80969 has joined #openstack-dev17:20
*** gianpietro has quit IRC17:24
*** harlowja has quit IRC17:26
*** vnogin has quit IRC17:27
*** ssbarnea_ has joined #openstack-dev17:27
*** ericyoung has joined #openstack-dev17:28
*** dtardivel has quit IRC17:28
*** egallen has quit IRC17:30
*** Guest80969 has quit IRC17:30
*** shardy has quit IRC17:32
*** jamesmca_ has quit IRC17:32
*** dizquierdo has quit IRC17:34
arslanqclarkb: i just added another compute node but i cant see it in openstack host list17:37
clarkbarslanq: you have to run the discovery command17:38
*** e0ne has quit IRC17:39
*** felipemonteiro has joined #openstack-dev17:39
*** yamamoto_ has quit IRC17:39
arslanqclarkb: and what is it?17:40
*** fragatina has joined #openstack-dev17:40
clarkbarslanq: I don't know off the top of my head, you'll need to look it up17:40
arslanqclarkb: ok i'll do17:41
arslanqclarkb: Thanks17:41
*** ram5391 has joined #openstack-dev17:41
*** yamamoto has joined #openstack-dev17:43
*** jwcroppe has joined #openstack-dev17:43
*** salv-orlando has joined #openstack-dev17:43
*** wootehfoot has joined #openstack-dev17:45
*** salv-orlando has quit IRC17:48
*** galstrom_zzz is now known as galstrom17:48
*** felipemonteiro has quit IRC17:49
*** ram5391 has quit IRC17:51
*** felipemonteiro has joined #openstack-dev17:52
*** wootehfoot has quit IRC17:54
*** felipemonteiro has quit IRC17:56
*** kbringard has quit IRC17:56
*** wootehfoot has joined #openstack-dev17:57
*** gianpietro has joined #openstack-dev17:57
*** jamielennox is now known as jamielennox|away17:59
*** dhajare has quit IRC18:01
*** iyamahat has quit IRC18:03
*** feisky has quit IRC18:05
*** jamielennox|away is now known as jamielennox18:05
*** achampion has quit IRC18:05
*** qlixed has quit IRC18:06
*** el_qlix0 has joined #openstack-dev18:06
*** zul has quit IRC18:06
*** yamahata has joined #openstack-dev18:09
*** yamamoto has quit IRC18:11
*** yamamoto has joined #openstack-dev18:12
*** claudiub has joined #openstack-dev18:13
bretonclarkb: i guess it happens because keystone now runs on port :80 too18:16
*** bmace__ has quit IRC18:17
*** bmace__ has joined #openstack-dev18:17
*** sree has joined #openstack-dev18:20
*** psachin has quit IRC18:23
*** sree has quit IRC18:25
*** vnogin has joined #openstack-dev18:28
*** electrofelix has quit IRC18:29
*** salv-orlando has joined #openstack-dev18:31
*** achampion has joined #openstack-dev18:32
*** jamesmca_ has joined #openstack-dev18:33
*** e0ne has joined #openstack-dev18:33
*** vnogin has quit IRC18:33
*** jwcroppe has quit IRC18:34
*** zul has joined #openstack-dev18:37
*** salv-orlando has quit IRC18:39
*** vnogin has joined #openstack-dev18:44
*** yamamoto has quit IRC18:45
*** salv-orlando has joined #openstack-dev18:48
*** felipemonteiro has joined #openstack-dev18:49
*** jkilpatr has quit IRC18:50
*** gfidente is now known as gfidente|afk18:51
*** jkilpatr has joined #openstack-dev18:54
*** jamesmca_ has quit IRC18:56
*** salv-orlando has quit IRC18:59
*** achampion has quit IRC19:01
*** READ10 has quit IRC19:03
*** lpetrut has joined #openstack-dev19:03
*** Vek has quit IRC19:04
*** ansmith has quit IRC19:05
*** mordred has quit IRC19:05
*** jwcroppe has joined #openstack-dev19:06
*** mordred has joined #openstack-dev19:06
*** achampion has joined #openstack-dev19:06
cdent\o/ on losing authenticating request ids19:09
*** donghao has joined #openstack-dev19:10
*** cioran89 has quit IRC19:10
*** cioran89 has joined #openstack-dev19:10
*** donghao has quit IRC19:15
*** ansmith has joined #openstack-dev19:20
*** jamesmca_ has joined #openstack-dev19:22
*** gomarivera_ has joined #openstack-dev19:22
*** gomarivera_ has quit IRC19:27
*** piyushks has quit IRC19:27
*** mkoderer has quit IRC19:27
*** awaugama has quit IRC19:28
*** tobberydberg has joined #openstack-dev19:31
*** gianpietro has quit IRC19:35
*** bmace__ has quit IRC19:35
*** NostawRm has quit IRC19:36
*** yamahata has quit IRC19:37
*** harlowja has joined #openstack-dev19:39
*** jamesmca_ has quit IRC19:42
*** xyang1 has quit IRC19:43
*** xyang1 has joined #openstack-dev19:45
*** yamamoto has joined #openstack-dev19:45
*** lpetrut has quit IRC19:47
*** kirotawa1 has quit IRC19:47
*** gfidente|afk has quit IRC19:48
*** dsariel has joined #openstack-dev19:50
*** cioran89 has quit IRC19:52
*** harlowja has quit IRC19:53
*** cioran89 has joined #openstack-dev19:53
*** myoung is now known as myoung|biab19:55
*** myoung|biab is now known as myoung19:55
*** harlowja has joined #openstack-dev19:57
*** matrohon has joined #openstack-dev19:57
*** cioran89 has quit IRC19:58
*** cioran89 has joined #openstack-dev20:00
*** harlowja has quit IRC20:00
*** yamamoto has quit IRC20:02
*** jkilpatr has quit IRC20:04
fungias simple as possible, but no simpler20:05
*** cdent has quit IRC20:05
*** ansmith has quit IRC20:08
*** jkilpatr has joined #openstack-dev20:08
*** cioran89 has quit IRC20:16
*** cioran89 has joined #openstack-dev20:16
*** xlark has quit IRC20:16
*** dimtruck is now known as zz_dimtruck20:18
*** gianpietro has joined #openstack-dev20:20
*** marst has joined #openstack-dev20:20
*** vnogin has quit IRC20:24
*** piyushks has joined #openstack-dev20:24
*** vnogin has joined #openstack-dev20:26
*** jcoufal has quit IRC20:26
*** cioran89 has quit IRC20:26
*** cioran89 has joined #openstack-dev20:27
*** cioran89 has quit IRC20:31
*** noslzzp has quit IRC20:31
*** cioran89 has joined #openstack-dev20:32
*** vnogin has quit IRC20:36
*** mhickey has joined #openstack-dev20:37
*** iyamahat has joined #openstack-dev20:38
*** slaweq has joined #openstack-dev20:38
*** slaweq has quit IRC20:38
*** slaweq has joined #openstack-dev20:41
*** zz_dimtruck is now known as dimtruck20:41
*** vnogin has joined #openstack-dev20:41
*** gouthamr has quit IRC20:44
*** zul has quit IRC20:51
*** piyushks has quit IRC20:58
*** Vek has joined #openstack-dev21:00
*** armax has quit IRC21:02
*** piyushks has joined #openstack-dev21:02
*** bmace__ has joined #openstack-dev21:03
*** thorst_afk has quit IRC21:03
*** rfolco has quit IRC21:03
*** haleyb has quit IRC21:03
*** jwcroppe has quit IRC21:03
*** jrist has quit IRC21:04
*** hongbin has quit IRC21:08
*** gordc has quit IRC21:08
efriedmordred yt?21:09
*** gomarivera_ has joined #openstack-dev21:11
*** donghao has joined #openstack-dev21:13
*** gouthamr has joined #openstack-dev21:14
*** ijw has joined #openstack-dev21:15
*** kobis has joined #openstack-dev21:15
*** gomarivera_ has quit IRC21:15
mordredefried: sup?21:16
*** hongbin has joined #openstack-dev21:16
efriedmordred Wanted to bend your ear about the idea of moving get_service_url() entirely out of nova and into ksa21:16
*** kylek3h has quit IRC21:16
efried...so it can be useful to other services.21:16
efriedmordred Ref: https://review.openstack.org/#/c/458257/21:17
*** donghao has quit IRC21:17
efriedspecifically https://review.openstack.org/#/c/458257/8/nova/utils.py21:17
mordredefried: oh - yes. this is definitely a thing I believe we shoudl do - but I believe we need to go a couple of more rounds on the API-WG specs before we do21:17
mordredefried: which I intend to update tomorrow after having chatted with folks last week, then we can start badgering people for agreement21:18
*** ijw has quit IRC21:19
efriedmordred Okay, I don't have a frame of reference there - does that mean "within the life of this change set," "after this change set but before pike feature freeze," "some time after pike," ...?21:20
*** ijw has joined #openstack-dev21:20
*** ijw has quit IRC21:20
*** ijw has joined #openstack-dev21:20
mordredefried: I'm _definitely_ aiming for before feature freeze21:22
mordredlike, within the next couple of weeks21:22
*** sdague has quit IRC21:22
*** kylek3h has joined #openstack-dev21:22
efriedmordred Okay, nice.  Kinda trying to gauge what I should be doing, if anything, with that change set.21:23
*** LuigiOpenstack has quit IRC21:23
*** rcrit has quit IRC21:23
*** matrohon has quit IRC21:24
mordredefried: nod. I'll ping you tomorrow with the spec follow up and see what you think21:24
efriedmordred Sounds good.  Meanwhile... are you my go-to for the service token thing as well?21:25
*** ijw has quit IRC21:25
*** ijw has joined #openstack-dev21:26
*** edmondsw has quit IRC21:27
mordredefried: maybe? I'm probably not the _worst_ one21:27
edleafemordred: btw - heading out to PyCon tomorrow, so I won't be reviewing your voluminous patches for a little while21:28
*** edmondsw has joined #openstack-dev21:28
edleafemordred: didn't want you to think that you scared me off21:28
mordrededleafe: :)21:30
mordrededleafe: I'll think that anyway21:30
*** edmondsw_ has joined #openstack-dev21:31
*** athomas has quit IRC21:31
*** edmondsw has quit IRC21:32
*** e0ne has quit IRC21:33
*** marst has quit IRC21:33
*** kazsh has joined #openstack-dev21:34
*** ijw has quit IRC21:34
*** rfolco has joined #openstack-dev21:34
*** e0ne has joined #openstack-dev21:34
*** kriskend_ has quit IRC21:35
*** ijw has joined #openstack-dev21:35
*** e0ne has quit IRC21:35
*** e0ne has joined #openstack-dev21:35
*** e0ne has quit IRC21:36
*** edmondsw_ has quit IRC21:36
*** e0ne has joined #openstack-dev21:36
*** e0ne has quit IRC21:36
*** e0ne has joined #openstack-dev21:37
*** e0ne has quit IRC21:37
*** e0ne has joined #openstack-dev21:37
*** e0ne has quit IRC21:38
*** piyushks has quit IRC21:38
*** ijw has quit IRC21:39
*** ijw has joined #openstack-dev21:40
*** baoli_ has quit IRC21:41
*** alexismonville has joined #openstack-dev21:42
*** rcrit has joined #openstack-dev21:44
*** ijw has quit IRC21:47
*** ijw has joined #openstack-dev21:48
*** tobberydberg has quit IRC21:49
*** alexismonville has quit IRC21:50
*** alexismonville has joined #openstack-dev21:51
*** ijw has quit IRC21:52
*** ijw has joined #openstack-dev21:52
*** ijw has quit IRC21:54
*** slaweq has quit IRC21:54
*** ijw has joined #openstack-dev21:55
*** wootehfoot has quit IRC21:57
*** xyang1 has quit IRC21:58
*** rfolco has quit IRC21:58
*** takamatsu has quit IRC21:59
*** bobh has quit IRC21:59
*** thorst_afk has joined #openstack-dev22:00
*** harlowja has joined #openstack-dev22:02
*** kobis has quit IRC22:03
*** vnogin has quit IRC22:04
*** cioran89 has quit IRC22:06
*** cioran89 has joined #openstack-dev22:06
*** jkilpatr has quit IRC22:07
*** kylek3h has quit IRC22:12
*** kazsh has quit IRC22:13
*** dimtruck is now known as zz_dimtruck22:14
*** zz_dimtruck is now known as dimtruck22:14
*** rwsu has quit IRC22:17
*** harlowja has quit IRC22:18
*** thorst_afk has quit IRC22:20
*** vhosakot has quit IRC22:22
*** dimtruck is now known as zz_dimtruck22:23
*** benj_ has joined #openstack-dev22:24
*** jkilpatr has joined #openstack-dev22:24
*** achampion has quit IRC22:26
*** ihrachys has quit IRC22:28
*** mhickey has quit IRC22:32
*** galstrom is now known as galstrom_zzz22:32
*** dsariel has quit IRC22:39
*** charcol has joined #openstack-dev22:44
*** baoli has joined #openstack-dev22:48
*** baoli has quit IRC22:48
*** baoli has joined #openstack-dev22:49
*** eharney has quit IRC22:52
*** zz_dimtruck is now known as dimtruck22:54
*** jathan has quit IRC22:54
*** rwsu has joined #openstack-dev23:10
*** lbragstad has quit IRC23:10
*** gouthamr has quit IRC23:12
*** gouthamr has joined #openstack-dev23:20
*** thorst_afk has joined #openstack-dev23:20
*** bmace__ has left #openstack-dev23:21
*** claudiub has quit IRC23:23
*** kazsh has joined #openstack-dev23:23
*** seba has quit IRC23:24
*** jgrassler has quit IRC23:25
*** caboucha has quit IRC23:32
*** ram5391 has joined #openstack-dev23:33
*** karthiks has quit IRC23:35
*** jgrassler has joined #openstack-dev23:36
*** dimtruck is now known as zz_dimtruck23:37
*** ijw has quit IRC23:38
*** ijw has joined #openstack-dev23:39
*** thorst_afk has quit IRC23:41
*** seba has joined #openstack-dev23:41
*** zul has joined #openstack-dev23:47
*** felipemonteiro has quit IRC23:49
*** tobberydberg has joined #openstack-dev23:50
*** kriskend_ has joined #openstack-dev23:52
*** jamesmca_ has joined #openstack-dev23:53
*** armax has joined #openstack-dev23:53
*** tobberydberg has quit IRC23:54
*** hongbin has quit IRC23:56
*** jamesmca_ has quit IRC23:58
*** kriskend_ has quit IRC23:58

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