Thursday, 2017-03-02

*** ZZelle has quit IRC00:04
*** jkilpatr has joined #openstack-dev00:08
*** krtaylor has quit IRC00:08
*** rfolco has joined #openstack-dev00:13
*** jmckind has quit IRC00:13
*** xarses has quit IRC00:13
*** claudiub|2 has quit IRC00:14
*** sc has quit IRC00:17
*** sc has joined #openstack-dev00:19
*** sc is now known as Guest4454300:19
*** rfolco has quit IRC00:20
*** cdub has quit IRC00:20
*** _cjones_ has quit IRC00:21
*** _cjones_ has joined #openstack-dev00:22
*** _cjones_ has quit IRC00:26
*** limao has joined #openstack-dev00:27
*** mriedem has joined #openstack-dev00:27
*** cdub has joined #openstack-dev00:28
*** jwcroppe has joined #openstack-dev00:28
*** gfidente|afk has quit IRC00:30
*** thorst has joined #openstack-dev00:31
*** ansmith has joined #openstack-dev00:31
*** cdub has quit IRC00:32
*** haukebruno has quit IRC00:33
*** dimtruck is now known as zz_dimtruck00:33
*** cdub has joined #openstack-dev00:34
*** rfolco has joined #openstack-dev00:35
*** rfolco has quit IRC00:35
*** hongbin has quit IRC00:35
*** thorst has quit IRC00:36
*** sdake has quit IRC00:36
*** adu has joined #openstack-dev00:36
*** tovin07 has joined #openstack-dev00:38
*** dtardivel has quit IRC00:40
*** thorst has joined #openstack-dev00:41
*** sdake has joined #openstack-dev00:42
*** cdub has quit IRC00:42
*** gongysh has joined #openstack-dev00:45
*** jathan has quit IRC00:45
*** gongysh has quit IRC00:49
*** owalsh-afk has quit IRC00:52
*** owalsh-afk has joined #openstack-dev00:52
*** krtaylor has joined #openstack-dev00:53
*** zz_dimtruck is now known as dimtruck00:53
*** haukebruno has joined #openstack-dev00:54
*** Jinxing has joined #openstack-dev00:55
*** Jinxing has quit IRC00:56
*** owalsh has joined #openstack-dev00:57
*** jmckind has joined #openstack-dev00:57
*** owalsh-afk has quit IRC00:57
*** ansmith has quit IRC00:59
*** thorst has quit IRC01:01
*** armax has joined #openstack-dev01:06
*** Swami has quit IRC01:06
*** cloudtrainme has joined #openstack-dev01:09
*** jmckind is now known as jmckind_01:13
*** dimtruck is now known as zz_dimtruck01:13
*** jmckind_ is now known as jmckind01:14
*** jamielennox is now known as jamielennox|away01:16
*** saibarspeis has quit IRC01:18
*** saibarspeis has joined #openstack-dev01:20
*** zz_dimtruck is now known as dimtruck01:22
*** jmckind is now known as jmckind_01:32
*** jmckind_ is now known as jmckind01:34
*** jmckind is now known as jmckind_01:34
*** jmckind_ is now known as jmckind01:34
*** yanyanhu has joined #openstack-dev01:50
*** adu has quit IRC01:52
*** chigang has joined #openstack-dev01:57
*** ijw has quit IRC01:58
*** jmckind has quit IRC02:00
*** dimtruck is now known as zz_dimtruck02:06
*** achampion has joined #openstack-dev02:09
*** yuntongjin has joined #openstack-dev02:09
*** sdake_ has joined #openstack-dev02:10
*** gyee has quit IRC02:12
*** gyee has joined #openstack-dev02:12
*** sdake has quit IRC02:13
*** radhikam has quit IRC02:15
*** raunak has quit IRC02:16
*** sdake_ is now known as sdake02:28
*** diablo_rojo has quit IRC02:38
*** yee379 has quit IRC02:49
*** xarses_ has quit IRC02:50
*** yee379 has joined #openstack-dev02:50
*** xarses has joined #openstack-dev02:51
*** cloudtrainme has quit IRC02:53
*** gyee has quit IRC02:58
*** gyee has joined #openstack-dev02:59
*** raunak has joined #openstack-dev03:01
*** rpittau_ has joined #openstack-dev03:02
*** rpittau has quit IRC03:04
*** gongysh has joined #openstack-dev03:04
*** nplanel has joined #openstack-dev03:09
*** john-davidge has joined #openstack-dev03:15
*** gongysh has quit IRC03:16
*** john-davidge has quit IRC03:20
*** mriedem is now known as mriedem_afk03:26
*** erlon has quit IRC03:35
*** halprin has quit IRC03:42
*** yamahata has quit IRC03:45
*** iyamahat has quit IRC03:45
*** tuanluong has joined #openstack-dev03:50
*** thorst has joined #openstack-dev03:50
*** thorst has quit IRC03:50
*** rcernin has quit IRC03:50
*** raunak has quit IRC03:54
*** kgiusti has left #openstack-dev03:54
*** nmathew has joined #openstack-dev03:58
*** yuntongjin has quit IRC04:03
*** nicolasbock has quit IRC04:06
*** fragatina has quit IRC04:13
*** achampion has quit IRC04:13
*** achampion has joined #openstack-dev04:13
*** halprin has joined #openstack-dev04:25
*** psachin has joined #openstack-dev04:26
openstackgerritKirill Zaitsev proposed openstack/governance master: Add yaql under murano team to allow yaql use releases  https://review.openstack.org/43998304:26
*** fragatina has joined #openstack-dev04:28
*** thorst has joined #openstack-dev04:32
*** thorst has quit IRC04:32
*** fragatina has quit IRC04:32
*** sree has joined #openstack-dev04:43
*** ShaneDavidson has quit IRC05:02
*** thorst has joined #openstack-dev05:03
*** sdake has quit IRC05:08
*** qlixed has joined #openstack-dev05:11
*** thorst has quit IRC05:16
*** adriant_ has quit IRC05:20
*** rderose has quit IRC05:21
*** fragatina has joined #openstack-dev05:22
*** ayogi has joined #openstack-dev05:23
*** fragatina has quit IRC05:26
*** k4n0 has joined #openstack-dev05:31
*** radhikam has joined #openstack-dev05:32
*** jcoufal has joined #openstack-dev05:35
*** yolanda has quit IRC05:35
*** john-davidge has joined #openstack-dev05:42
*** radhikam has quit IRC05:45
*** john-davidge has quit IRC05:47
*** halprin has quit IRC05:52
*** Poornima has joined #openstack-dev05:56
*** jcoufal_ has joined #openstack-dev05:59
*** jcoufal has quit IRC06:00
*** dhajare has joined #openstack-dev06:04
*** sridharg has joined #openstack-dev06:07
*** claudiub|2 has joined #openstack-dev06:08
*** chigang has quit IRC06:09
*** qlixed has quit IRC06:12
*** jcoufal has joined #openstack-dev06:12
*** armax has quit IRC06:14
*** jcoufal_ has quit IRC06:15
*** AnilV4 has joined #openstack-dev06:18
*** psachin_ has joined #openstack-dev06:18
*** psachin_ has quit IRC06:19
*** jcoufal_ has joined #openstack-dev06:29
*** achampion has quit IRC06:30
*** sreenath has joined #openstack-dev06:30
*** jcoufal has quit IRC06:31
sreenathHi Guys, does anyone know - how we can enable Swift service in an existing Devstack environment?06:31
*** e0ne has joined #openstack-dev06:31
*** svinota has joined #openstack-dev06:38
*** k4n0 has quit IRC06:40
*** ekuris has joined #openstack-dev06:42
*** jcoufal has joined #openstack-dev06:43
*** salv-orlando has joined #openstack-dev06:45
*** ShaneDavidson has joined #openstack-dev06:46
*** jcoufal_ has quit IRC06:46
*** gamado has joined #openstack-dev06:46
*** salv-orl_ has joined #openstack-dev06:52
*** k4n0 has joined #openstack-dev06:52
*** gyee has quit IRC06:54
*** vnogin has joined #openstack-dev06:54
*** salv-orlando has quit IRC06:55
*** itzikb has joined #openstack-dev06:56
*** jcoufal has quit IRC06:59
*** k4n0 has quit IRC06:59
*** kobis has joined #openstack-dev07:00
*** yamahata has joined #openstack-dev07:08
*** vnogin has quit IRC07:08
*** rcernin has joined #openstack-dev07:18
*** kobis has quit IRC07:18
*** tesseract has joined #openstack-dev07:18
*** lpetrut has joined #openstack-dev07:20
*** ShaneDavidson has quit IRC07:21
*** rarcea has joined #openstack-dev07:24
*** lpetrut has quit IRC07:24
*** hwoarang has quit IRC07:28
*** hwoarang has joined #openstack-dev07:29
*** vladikr has quit IRC07:30
*** charcol has quit IRC07:30
*** ansmith has joined #openstack-dev07:30
*** raunak has joined #openstack-dev07:32
*** zhugaoxiao has joined #openstack-dev07:34
*** yamamoto has quit IRC07:38
*** gongysh has joined #openstack-dev07:41
*** limao has quit IRC07:43
*** hseipp has joined #openstack-dev07:43
*** limao has joined #openstack-dev07:45
*** e0ne has quit IRC07:47
*** ansmith has quit IRC07:47
*** rarcea has quit IRC07:53
*** pkoniszewski has joined #openstack-dev07:53
*** shardy has joined #openstack-dev08:04
*** matrohon has joined #openstack-dev08:04
*** yuntongjin has joined #openstack-dev08:05
*** rarcea has joined #openstack-dev08:05
*** athomas has joined #openstack-dev08:07
*** k4n0 has joined #openstack-dev08:12
*** pcaruana has joined #openstack-dev08:13
*** chigang has joined #openstack-dev08:14
*** treiz has joined #openstack-dev08:15
*** ltomasbo|away is now known as ltomasbo08:16
*** yamamoto has joined #openstack-dev08:17
*** yamamoto_ has joined #openstack-dev08:17
*** tremble has joined #openstack-dev08:19
*** yamamoto_ has quit IRC08:20
*** kobis has joined #openstack-dev08:20
*** yamamoto has quit IRC08:21
*** raunak has quit IRC08:26
*** lpetrut has joined #openstack-dev08:29
*** dtardivel has joined #openstack-dev08:31
*** lpetrut has quit IRC08:33
*** matrohon has quit IRC08:34
*** jpich has joined #openstack-dev08:37
*** DFFlanders has joined #openstack-dev08:40
*** nmathew has quit IRC08:41
*** nmathew- has joined #openstack-dev08:41
*** dnikisho1 has quit IRC08:41
*** dnikishov has joined #openstack-dev08:42
*** dnikishov is now known as Guest6638508:42
*** tlaxkit has joined #openstack-dev08:42
*** jordanP has joined #openstack-dev08:46
*** sshnaidm|off is now known as sshnaidm08:46
*** gszasz has joined #openstack-dev08:47
*** rraja has joined #openstack-dev08:48
*** zackf has quit IRC08:50
*** saibarspeis has quit IRC08:50
*** takamatsu has joined #openstack-dev08:51
*** sdake_ has joined #openstack-dev08:52
*** hseipp has quit IRC08:52
*** dhajare has quit IRC08:53
*** ioggstream has joined #openstack-dev08:59
*** zzzeek has quit IRC09:00
*** zzzeek has joined #openstack-dev09:00
*** priteau has joined #openstack-dev09:01
*** mhickey has joined #openstack-dev09:03
*** shardy has quit IRC09:04
*** shardy has joined #openstack-dev09:04
*** rraja has quit IRC09:09
*** eglynn has joined #openstack-dev09:11
*** thorst has joined #openstack-dev09:13
*** yamamoto has joined #openstack-dev09:17
*** thorst has quit IRC09:18
*** ioggstream has quit IRC09:18
*** gmoro has joined #openstack-dev09:18
*** yamamoto has quit IRC09:22
*** ygbo has joined #openstack-dev09:24
*** eezhova has joined #openstack-dev09:24
*** dsariel has joined #openstack-dev09:25
*** Guest79770 has quit IRC09:27
*** ZZelle has joined #openstack-dev09:27
*** ZZelle is now known as Guest2041809:28
*** Guest20418 is now known as ZZelle_09:28
*** nmathew- has quit IRC09:34
*** lucas-afk is now known as lucasagomes09:35
*** noslzzp_ has joined #openstack-dev09:36
*** noslzzp has quit IRC09:36
*** electrofelix has joined #openstack-dev09:37
*** yuntongjin has quit IRC09:39
*** aarefiev_afk is now known as aarefiev09:39
*** snica has joined #openstack-dev09:40
*** sdake_ is now known as sdake09:41
*** gamado has quit IRC09:44
*** akrivoka has joined #openstack-dev09:46
*** felixsch_ has quit IRC09:49
*** jordanP has quit IRC09:57
*** felixsch_ has joined #openstack-dev09:58
*** MattMan has quit IRC10:00
*** MattMan has joined #openstack-dev10:00
*** aasthad has quit IRC10:02
*** gszasz has quit IRC10:06
*** gszasz has joined #openstack-dev10:08
*** bks has joined #openstack-dev10:10
*** gszasz has quit IRC10:10
*** limao has quit IRC10:11
*** gszasz has joined #openstack-dev10:12
*** tovin07 has quit IRC10:12
*** gmoro has quit IRC10:13
*** gmoro has joined #openstack-dev10:14
*** nmathew has joined #openstack-dev10:16
*** sdake has quit IRC10:18
*** lpetrut has joined #openstack-dev10:18
*** dtantsur|afk is now known as dtantsur10:19
*** yamamoto has joined #openstack-dev10:19
*** yamamoto has quit IRC10:22
*** sdake has joined #openstack-dev10:22
*** gongysh has quit IRC10:27
*** mhickey has quit IRC10:28
*** yanyanhu has quit IRC10:31
*** cdent has joined #openstack-dev10:33
*** sree has quit IRC10:35
*** john-davidge has joined #openstack-dev10:36
odyssey4meshardy flaper87 EmilienM andymccr inc0 v1k0d3n I've moved content from https://etherpad.openstack.org/p/ptg-pike-deployment-projects-collab into https://etherpad.openstack.org/p/deployment-pike and added some meat to it10:40
*** ociuhandu has joined #openstack-dev10:41
shardyodyssey4me: Hey, thanks!10:41
shardyodyssey4me: sorry I wasn't aware there was an existing etherpad10:41
flaper87odyssey4me: that's awesome, thanks10:41
*** sdake has quit IRC10:41
*** john-davidge has quit IRC10:41
odyssey4meshardy that was more of a scratch pad from the initial discussion that OSA and O-H had10:41
odyssey4meit's good that we're moving stuff over into this one as it's more inclusive and purpose specific10:42
*** eezhova has quit IRC10:42
shardyodyssey4me: ah, yeah I think I actuall did see that but forgot, thanks for adding the content :)10:42
shardymaybe we could add a list of the projects interested in collaborating to the wiki along with irc nicks for those prepared to act as a point of contact10:43
* shardy will look at doing that later10:44
*** Poornima has quit IRC10:45
*** ociuhandu has quit IRC10:47
*** dalgaaf has quit IRC10:48
*** dalgaaf has joined #openstack-dev10:48
*** claudiub|2 is now known as claudiub10:49
*** DFFlanders has quit IRC10:51
*** dhajare has joined #openstack-dev10:51
*** yamamoto has joined #openstack-dev10:53
*** yamamoto has quit IRC10:53
*** Guest44543 is now known as sc10:54
*** eezhova has joined #openstack-dev10:54
*** bogdando has joined #openstack-dev10:55
*** mvk has quit IRC10:57
*** ociuhandu has joined #openstack-dev10:59
*** shardy has quit IRC11:00
*** shardy has joined #openstack-dev11:01
*** nicolasbock has joined #openstack-dev11:01
*** ioggstream has joined #openstack-dev11:04
*** yamamoto has joined #openstack-dev11:04
*** paramite has joined #openstack-dev11:07
*** gfidente has joined #openstack-dev11:08
*** nmathew has quit IRC11:08
*** halves has joined #openstack-dev11:08
*** sdake has joined #openstack-dev11:12
*** ioggstream has quit IRC11:13
*** thorst has joined #openstack-dev11:14
*** halves has quit IRC11:16
*** eezhova has quit IRC11:17
*** ociuhandu has quit IRC11:18
*** ociuhandu has joined #openstack-dev11:18
*** ociuhandu has quit IRC11:18
*** ociuhandu has joined #openstack-dev11:19
*** thorst has quit IRC11:19
*** Poornima has joined #openstack-dev11:26
*** mvk has joined #openstack-dev11:28
*** john-davidge has joined #openstack-dev11:29
*** john-dav_ has joined #openstack-dev11:34
*** john-davidge has quit IRC11:34
*** jkilpatr has quit IRC11:34
*** ociuhandu has quit IRC11:37
*** ociuhandu has joined #openstack-dev11:39
*** watersoul has quit IRC11:41
*** eglynn has quit IRC11:43
*** snica is now known as snica_away11:43
*** ociuhandu has quit IRC11:43
*** Poornima has quit IRC11:44
*** paramite has quit IRC11:45
*** sdague has joined #openstack-dev11:46
*** watersoul has joined #openstack-dev11:48
*** sdake has quit IRC11:49
*** sdake has joined #openstack-dev11:49
*** halves has joined #openstack-dev11:50
*** jkilpatr has joined #openstack-dev11:51
*** darvon has quit IRC11:51
*** darvon has joined #openstack-dev11:52
*** yassine has quit IRC11:52
*** lucasagomes is now known as lucas-brb11:52
*** sdake_ has joined #openstack-dev11:55
*** darvon has quit IRC11:55
*** sdake has quit IRC11:56
*** darvon has joined #openstack-dev11:56
*** darvon has quit IRC11:57
*** darvon has joined #openstack-dev11:58
*** yassine has joined #openstack-dev11:58
*** jkilpatr has quit IRC11:58
*** yamamoto has quit IRC11:58
*** chigang has quit IRC11:59
*** e0ne has joined #openstack-dev12:06
*** sreenath has quit IRC12:07
*** yamahata has quit IRC12:08
*** sdake_ is now known as sdake12:09
EmilienModyssey4me: excellent12:10
*** aysyd has joined #openstack-dev12:12
*** jkilpatr has joined #openstack-dev12:12
EmilienModyssey4me: also, ack for mailing list12:13
EmilienMworks for me now12:13
EmilienModyssey4me: creating the WG is on my todo, I was waiting for feedback this week after shardy's email and it seems we're ready now12:13
*** steveg_afk has quit IRC12:14
*** snica_away is now known as snica12:15
EmilienModyssey4me: I'm confused about why not using IRC channel12:15
EmilienMbecause that's how the community works, IRC + ML12:15
odyssey4meEmilienM I don't see what the point is of creating another exclusive space for discussions12:15
odyssey4methat makes sense for projects, but I don't think it's appropriate for working groups12:16
odyssey4methis channel is open, just like the ML and many people would be interested in the discussions we have12:16
*** annegentle has quit IRC12:16
odyssey4mealso, this channel is not all that busy - but everyone is in it, so using this channel increases our discussion exposure, therefore giving us broader input12:17
*** athomas has quit IRC12:18
odyssey4meif our discussion traffic increases such that we're intruding on others, then I'd be happy to support moving to another channel - but having another channel to be mostly idle is a waste of screen real-estate :p12:18
odyssey4meEmilienM if you feel that it's the right thing to do, then I will follow your lead12:19
EmilienMto be honest, I don't know :-) we're starting things now, I think we'll learn on the go how we like to work12:20
odyssey4meIt would have been great to discuss it as a community, instead of a person making a unilateral decision12:20
EmilienMI think for now, discussions should happen on ML when possible (and that's what I would do)12:21
odyssey4meyep, agreed12:21
*** dtantsur is now known as dtantsur|bbl12:21
*** shardy is now known as shardy_lunch12:21
andymccryeah tbh that is the reason i havnt really commented on that side of things at all, its early doors - and its hard to know. perhaps meetings/IRC dont work and the etherpad/ML is all we need, but its all conjecture12:21
*** steveg_afk has joined #openstack-dev12:26
*** alexismonville has joined #openstack-dev12:26
*** athomas has joined #openstack-dev12:29
*** sdake_ has joined #openstack-dev12:29
*** sdake has quit IRC12:30
*** alexismonville has quit IRC12:30
*** cloudtrainme has joined #openstack-dev12:35
*** steveg_afk has quit IRC12:35
*** wznoinsk has quit IRC12:39
*** tuanluong has quit IRC12:40
*** wznoinsk has joined #openstack-dev12:42
*** rraja has joined #openstack-dev12:42
*** gszasz has quit IRC12:43
*** cloudtrainme has quit IRC12:45
*** thorst has joined #openstack-dev12:45
*** nplanel has quit IRC12:45
*** gszasz has joined #openstack-dev12:48
*** gszasz has quit IRC12:48
*** steveg_afk has joined #openstack-dev12:49
*** gszasz has joined #openstack-dev12:51
*** limao has joined #openstack-dev12:51
*** salv-orlando has joined #openstack-dev12:52
*** owalsh is now known as owalsh-afk12:53
*** dsariel has quit IRC12:53
*** ayogi has quit IRC12:54
*** salv-orl_ has quit IRC12:55
*** AnilV4 has quit IRC12:56
*** bogdando has quit IRC12:57
*** rfolco has joined #openstack-dev12:57
*** shardy_lunch is now known as shardy12:58
*** yamamoto has joined #openstack-dev12:59
*** sdake has joined #openstack-dev12:59
*** sdake_ has quit IRC13:01
*** mriedem_afk is now known as mriedem13:02
*** matrohon has joined #openstack-dev13:02
*** jwcroppe has quit IRC13:08
*** yamamoto has quit IRC13:09
*** saggi has quit IRC13:11
*** jlwhite has quit IRC13:15
*** jlwhite has joined #openstack-dev13:15
*** steveg_afk has quit IRC13:15
*** rderose has joined #openstack-dev13:15
*** sdake_ has joined #openstack-dev13:16
*** saggi has joined #openstack-dev13:17
*** ioggstream has joined #openstack-dev13:18
*** sdake has quit IRC13:19
*** READ10 has joined #openstack-dev13:21
*** jwcroppe has joined #openstack-dev13:23
*** nplanel has joined #openstack-dev13:23
*** Poornima has joined #openstack-dev13:25
*** rpittau_ is now known as rpittau13:26
*** snica is now known as snica_away13:28
*** snica_away is now known as snica13:29
*** cdent has quit IRC13:31
*** gordc has joined #openstack-dev13:33
*** dizquierdo has joined #openstack-dev13:34
johnthetubaguySpamapS: dstanek: mriedem: notmorgan: noticed the debate around quota from lbragstad ML post, curious if this helps answer questions: https://review.openstack.org/#/c/42967813:35
*** ansmith has joined #openstack-dev13:35
johnthetubaguyFWIW, I think placement API, once split out of nova, could eventually handle quotas, but the current proposals seems like a good step in that direction13:35
*** ioggstream has quit IRC13:39
*** v1k0d3n has joined #openstack-dev13:43
*** dsariel has joined #openstack-dev13:44
*** lucas-brb is now known as lucasagomes13:44
*** noslzzp_ has quit IRC13:44
*** noslzzp has joined #openstack-dev13:45
*** kgiusti has joined #openstack-dev13:47
*** cloudtrainme has joined #openstack-dev13:48
*** radhikam has joined #openstack-dev13:48
SpamapSjohnthetubaguy: that's an interesting way to go with that. Close to the resource tracker seems like the right place to put usage information.13:49
*** aolwas has quit IRC13:51
*** nplanel has quit IRC13:52
*** eharney has joined #openstack-dev13:52
*** mvk has quit IRC13:52
sdagueSpamapS: were you in the room when the quotas discussion was happening?13:53
*** luizbag has joined #openstack-dev13:54
sdaguebecause, part of the reason for putting limit definitions in keystone is the fact that whenever you update a limit in a hierarchy there is going to have to be a ton of checking and calculating the hierarchy. So it seems really weird and terribly inefficient to do it someplace where you don't have a lock on the hierachy. But that's just for the limits write.13:55
sdaguecalculations on usage stay down in the services13:55
sdaguelimits fetched from the hierarchy13:55
SpamapSsdague: Indeed, I was, but the usage is going to be changing far more often than the limits.13:56
sdagueSpamapS: sure, so I don't see why limits in keystone is an issue13:57
SpamapSAnd usage calc will have to fetch the hierarchy anyway.13:57
sdagueSpamapS: some times13:57
*** eezhova has joined #openstack-dev13:57
sdagueif you run non overbooking, it only needs children13:57
*** eharney has quit IRC13:57
SpamapSRight but overbooking was stated as a hard requirement. Perhaps it's not?13:58
sdagueSpamapS: no, it was stated as a mode that people may want13:58
*** alexismonville has joined #openstack-dev13:59
*** cloudtrainme has quit IRC13:59
SpamapSOk well that is different than hard req :)13:59
sdagueSo I think that a path where limits move to keystone is a very concrete evolution, that gives a real path to making progress. It's actually the first time I've seen any part of this conversation move in a direction that I can imagine it getting implemented.14:00
SpamapSsdague: I see both sides, I do. But the main reason to have them in keystone was that the hierarchy exists there and not in usage-info-holders. But it does exist in usage-info-holders, even if it's just children.14:01
sdagueSpamapS: it doesn't14:01
sdagueit's totally invalidated garbage data14:01
*** salv-orlando has quit IRC14:01
SpamapSThis gets really weird with accounting actually.14:01
SpamapSunless hierarchies are immutable14:01
SpamapSbut that's a bit corner casey14:02
sdaguethere are lots of hard problems here for sure14:02
*** radhikam has quit IRC14:02
sdaguebut we have a very big first order problem right now, in all deployments, that service don't know if projects/users exist when you set limits on them14:02
sdagueand that leads to tons of real bugs14:02
SpamapSsdague: I am not sure I understand how usage can be calculated without the hierarchy being known.14:03
*** cdent has joined #openstack-dev14:03
*** Guest66385 has quit IRC14:03
SpamapSIf it's just  A->B .. and you have a resource in A, and a resource in B...  what's usage for A? What's usage for B?14:03
sdagueand moving that to keystone eliminates a giant class of real bugs today14:03
*** vnogin has joined #openstack-dev14:03
sdagueSpamapS: ok, so I think you are saying hierarchical computations are going to be tricky, regardless14:04
sdagueand I agree14:04
SpamapSWell no, I'm saying hierarchycal computations are going to need to be able to find the root of the tree.14:04
sdaguebut it skips past the limits definitions even being vaguely real14:04
sdagueSpamapS: sure14:04
*** vladikr has joined #openstack-dev14:05
SpamapSAnd it seems to me that there will be usage numbers at every branch of the tree.14:05
sdagueSpamapS: yes, that's true regardless14:05
sdaguewhat isn't true regardless is how much effort is it to ensure that the limits hierarchy is real14:05
SpamapSRight14:06
SpamapSI see your point there.14:06
sdagueeven in flatland today, the limits defintions are often fiction14:06
SpamapSSo even though it would be far more efficient to have the limits local...14:06
sdaguenope14:06
SpamapSit's hard to know if the hierarchy that was set during limits def is still valid.14:06
sdaguethere is one project that knows if a project_id/user_id is real in your system14:07
SpamapSwell it would be pretty darn efficient if there are just rows in a 'limits' table and rows in a 'usages' table and you can just left join to the limits table while you're walking usage.14:07
*** breton has quit IRC14:07
sdaguethat's a real, current issue14:07
*** Poornima has quit IRC14:07
SpamapSBut we could probably do that as a cache14:07
sdagueSpamapS: that statement makes no sense to me?14:07
*** john-dav_ is now known as john-davidge14:08
SpamapSsorry we're a bit out of sync14:08
SpamapSI'm agreeing :)14:08
SpamapSSo if we had the limits in keystone as source of truth...14:08
sdagueYou are going to replicate 300K users/projects from and ldap on every service?14:08
*** jaypipes has quit IRC14:08
SpamapSsdague: just the ones that have usage?14:09
*** jcoufal has joined #openstack-dev14:09
*** eharney has joined #openstack-dev14:09
*** martines has quit IRC14:09
SpamapSwhich I have to do anyway to record said usage.14:09
sdagueright, so consider, getting non fictional limit means you are talking about (project, user (maybe), endpoint, limitedthing, amount)14:09
sdagueSpamapS: you need a limit before you can have usage14:09
SpamapSThat's a very good point.14:10
sdagueand I am quite concerned that (project, user (maybe), endpoint, limitedthing, amount) is valid14:10
sdaguebecause if it is not, there are a million bugs falling out of14:10
sdaguekeystone knows project, user, endpoint. If the endpoint then registers valid limitted things in it, and amount is always a int, you can at least ensure that data is not corrupt14:11
sdaguethat gives you a starting point of limits data will not be corrupt, which is not a thing we can ensure right now14:12
SpamapSSo I like all of that. Let's get into how usage is calculated, because maybe I misunderstood.14:12
johnthetubaguyI tried to draw that out in the spec, if its useful?14:12
*** adu has joined #openstack-dev14:13
johnthetubaguyline 134 in here: https://review.openstack.org/#/c/429678/4/specs/backlog/approved/quota-future.rst14:14
johnthetubaguyI am curious if what I had in my head is what others were thinking14:14
sdagueso, honestly, I think that calculating usage is going to be approximately as hard in any scenario14:14
SpamapSGiven ProjectParent->ProjectChild , if I'm trying to calc usage(ProjectChild) the first step is to find out parents of ProjectChild right?14:14
sdaguebut this gives us a thing we could do in pike, that at least ensures a real source of truth14:14
johnthetubaguyso I think keystone just lists the scope and the limit, the project has to work out how to "count the scope"14:14
SpamapSI'm reading again (I read this a while back.. thought I had it in my head)14:15
johnthetubaguysdague: +1 for making steps forward that help operators a lot now14:15
sdagueI also think this is complicated enough, that until you get some of the birds to land, you can keep going around in circles14:15
johnthetubaguysdague: +114:15
SpamapSOk, if you guys don't want to walk through how usage is calc'd with me, we're all busy. :) Happy to back away faster. ;)14:17
*** kbringard has joined #openstack-dev14:17
sdagueSpamapS: I think it's at best a stretch goal for pike, but really it's queens14:17
SpamapSthe spec says the word 'usage' once. :-P14:18
SpamapSSo it's not at all clear how it's expected to be calculated.14:18
SpamapSPerhaps it's somewhere else.14:18
sdagueand one of the reasons big hard things don't get done is we jump to step 3 or 4 or 27, when if we moved the ball forward here lots of people would be in code and the next problem would be more clear14:19
*** jdandrea has joined #openstack-dev14:19
SpamapSsdague: I can see that you'd rather I just stop commenting, and honestly, you have _a bazillion_ times more context. I was asked to look at it from outside either project, which is what I'm trying to do... but I can't really understand it and I'm probably just a speed bump at this point.14:21
*** owalsh-afk is now known as owalsh14:21
sdagueSpamapS: well mostly I want look at the concrete thing of limits in keystone14:21
SpamapShttp://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/cells-count-resources-to-check-quota-in-api.html <-- says "counting the resources", but again, does not say how they'd be counted14:21
sdaguedoes that paint us into a corner we can't get out of14:21
sdagueand does it solve any real problems immediately (like this garbage limits problem that all projects have right now)14:22
*** dtantsur|bbl is now known as dtantsur14:22
sdagueand I don't think it puts us anywhere terrible, it moves things forward, it solves some real problems, and it's doable in a cycle14:22
SpamapSNo I don't think it does. But it may waste Keystone's time if everyone ends up solving most of the same problems in their resource usage counting anyway, and the caches of limits end up being 1:1 mirrors of keystone's data.14:23
SpamapSWhich is why I'm asking for somebody to point to a clear description of how resources are counted to calc usage(project)14:24
*** baoli has joined #openstack-dev14:24
*** johndperkins has quit IRC14:24
*** martines has joined #openstack-dev14:25
SpamapSIf that has to fetch the project hierarchy from keystone every time anyway, then I reverse my position, and suggest that Keystone be the source of truth for limits since you're going there anyway.14:25
SpamapSI was led to believe that's not the case, and that usage rollups were to be found inside each resource tracker.14:25
sdagueSpamapS: I think the point is, there are a few different models that one might use to this kind of quota calculation14:25
sdagueon the usage side14:25
sdagueand right now, I don't think which model has been decided on, or if there is only going to be one14:26
SpamapSWell _that_ is the most useful piece of information yet. :)14:26
sdagueso we can do the exercise about the various ways to account for usage. But I don't think that changes the storage on limits story, and ensuring that's solid14:26
*** steveg_afk has joined #openstack-dev14:26
SpamapSI agree then. Have a solid source of hierarchy truth and build the usage calcs around that.14:27
SpamapSThis has been very useful in expanding my understanding of the actual current state of things vs. future state in peoples head which I was led to believe was current state.14:27
*** xemdetia has joined #openstack-dev14:28
*** raalee has joined #openstack-dev14:28
sdagueah, ok :)14:28
SpamapSCommon mistake. People speak with authority about the way they think it should work as if that's how it works.14:29
SpamapSAnd I don't check that it actually works that way.14:29
sdagueyeh, so, honestly, I've got a todo to try to help paint the picture, but this week has had some unexpected interuptions, so my brain has not yet had the space for it14:29
sdaguegot to run to breakfast now14:29
SpamapSI think you've got it far clearer than I ever did.14:29
*** dsariel has quit IRC14:30
SpamapSAnd keystone owning the limits for the hierarchy and calculating the rollups makes sense. Now.. I need to drive to Pasadena before it grows from 28 minutes to 58. ;)14:30
*** mriedem has quit IRC14:30
*** steveg_afk has quit IRC14:30
*** breton has joined #openstack-dev14:32
openstackgerritJohn Garbutt proposed openstack/governance master: WIP: Describe what upstream support means  https://review.openstack.org/44060114:32
*** e0ne has quit IRC14:33
dstanekSpamapS: sdague: i've very interested in this as well14:34
*** dnikishov has joined #openstack-dev14:35
dstaneki'll have to read up though since i haven't been paying attention :-(14:35
*** dnikishov is now known as Guest2599114:35
* lbragstad just finished reading scrollback14:35
*** mhickey has joined #openstack-dev14:36
*** e0ne has joined #openstack-dev14:36
*** jaypipes has joined #openstack-dev14:38
*** pabelanger has joined #openstack-dev14:40
*** john-dav_ has joined #openstack-dev14:41
*** john-davidge has quit IRC14:41
*** john-dav_ is now known as john-davidge14:42
*** johndperkins has joined #openstack-dev14:45
*** jaypipes has quit IRC14:48
dstaneki just want to make sure not only are we marching in the right direction, but that we're not marching for marching sake14:49
*** limao_ has joined #openstack-dev14:49
*** limao has quit IRC14:50
dstanekmy understanding thus far is that keystone will hold limit definitions14:50
dstaneknova defined the things that can be limited memory, cpu, whatever and registers them in keystone14:50
dstanekoperators can then use an api in keystone to set hard limits14:50
*** k4n0 has quit IRC14:51
dstanekthen when an VM request comes into nova it will ask keystone for the hieirachy of limits (the parent and all siblings)14:51
*** luizbag has quit IRC14:51
*** hongbin has joined #openstack-dev14:51
*** ihrachys has joined #openstack-dev14:52
dstaneknova would then using its own logic look at the limits the current usage and determine what to do next14:52
dstanekis that a correct characterization?14:52
sdaguedstanek: yep14:52
*** halves has quit IRC14:53
dstaneksdague: perfect14:54
*** jaypipes has joined #openstack-dev14:54
dstanekthat's what SpamapS and I were discussing the other day14:54
sdagueand, some asterixes. The over usage calculations for hierarchy case can/will probably by built into a library because some of it is tricky to get right14:54
dstanekin that model keystone is a glorified kv store]14:54
sdaguedstanek: yep14:54
sdaguedstanek: with some logic to not let you set limits that aren't possible in your model. Like A -> B, A cpus =100, B cpus=20014:55
sdagueso we get clean data on set into keystone14:55
sdaguethen we can trust that the hierarchy is consistent when we use that as source of truth in projects14:55
dstaneksdague: so it sounds easy on the surface14:56
sdagueinstead of having to code around crazy bugs like projects that don't exist14:56
dstaneknew apis that are locked down to service users14:56
dstanekwhat do we do for users? will they need to see their limits?14:56
*** bks has quit IRC14:56
sdagueyeh, they can today in services14:56
*** mvk has joined #openstack-dev14:56
dstanekok, so the user asks nova for limits -> nova gets limits from keystone and the adjusts based on usage14:57
sdaguedstanek: the way it was talked about in the room14:57
*** trikky_one has joined #openstack-dev14:58
sdagueyou can query keystone for limits14:58
dstaneksdague: will services need to get limits for other services? like nova needing to know limits for glance?14:58
dstaneksdague: the user can query keystone?14:58
sdagueyou can query services for usages, which will include limits as well (having fetched it on demand from keystone)14:58
sdaguedstanek: yes, that was the desire14:58
*** baoli has quit IRC14:59
sdagueso I can GET /limits, it opperates in my current project context (and probably returns children in hierarchy mode)14:59
sdaguethen I can see all the limits enacted on me in the system14:59
*** mriedem has joined #openstack-dev14:59
*** mriedem has quit IRC14:59
sdaguebecause booting a server requires not only cpu limits, but network, possibly volumes, etc14:59
*** raalee has quit IRC15:00
dstaneksdague: the only problem there is now to deal with over promising15:00
*** mriedem has joined #openstack-dev15:00
*** TxGirlGeek has joined #openstack-dev15:00
sdaguedstanek: so your connect is, I have limit 100, but so do all the other depts, any my division has 200, and I try to allocate and fail overquota?15:01
*** TxGirlGeek has quit IRC15:02
sdagueI think that's just going to be a matter of being clear in the error message that your parent project has exceeded quota, and ask your administrator to adjust15:02
*** halprin has joined #openstack-dev15:02
dstaneksdague: fair enough. i just wanted to get all my assumptions straightened out15:02
*** kbringard has quit IRC15:02
*** johndperkins has quit IRC15:03
sdaguebut, again, that's kind of all hard regardless, and I don't think we're getting to any of that in pike, just trying to lay the groundwork for a validated clean data set in keystone15:03
*** zz_dimtruck is now known as dimtruck15:03
*** TxGirlGeek has joined #openstack-dev15:03
*** kbringard has joined #openstack-dev15:04
dstaneksdague: my biggest concern would be to make sure the API is somewhat isolated within keystone so that it *could* be split off in the future15:04
*** johndperkins has joined #openstack-dev15:04
sdaguedstanek: I guess... I honestly feel like this has to be deeply tied to the project structure, and unless you are talking about spinning out that, it seems kind of pointless15:05
*** TxGirlGeek has quit IRC15:06
dstaneksdague: i can actually see it in a few different ways, but the thing i was specificaly pushing back on what putting limits in the token response15:06
*** zackf has joined #openstack-dev15:07
*** limao has joined #openstack-dev15:07
sdagueah, yeh, I guess that bit didn't come up there, but I wouldn't assume that things would go in the token. Honestly, I'm in the camp that we should get the catalog out of the token as well, and that the token should really only be project, user, roles.15:08
lbragstadsdague thats an interesting idea15:09
*** limao_ has quit IRC15:10
*** baoli has joined #openstack-dev15:10
*** saibarspeis has joined #openstack-dev15:10
*** itzikb has quit IRC15:10
lbragstadI was talking to notmorgan about versionless auth because we've had a spec in keystone's backlog for *ages* to decouple auth from a version, and that might provide a way to move catalogs out of the token15:10
*** valw has joined #openstack-dev15:10
*** valw has quit IRC15:11
*** rderose has quit IRC15:11
*** valw has joined #openstack-dev15:11
dstaneksdague: you just won my heart :-)15:11
lbragstadit might also provide a way for us to build more sensible catalog (based on the service)15:11
sdaguelbragstad: the thing is, outside of code our community has written, I'm not really convinced that folks use the token embedded catalog15:13
sdagueI have seen a ton of hard coding of urls15:13
lbragstadsdague hmmm I don't know if that's a good thing or a bad thing15:14
lbragstad:)15:14
sdagueit's a neat idea that's too complicated by half, and unless/until there is an equivalent of keystoneauth1 / occ in go, javascript, php, and ruby... it's just not going to all that used15:14
*** TxGirlGeek has joined #openstack-dev15:15
lbragstadsdague you're still referencing the catalog *within* the token response15:15
lbragstad?15:15
*** Guest76598 has joined #openstack-dev15:16
sdaguelbragstad: yes15:16
*** limao has quit IRC15:16
sdagueI feel like the catalog should be user fetchable from keystone, but it being in the token isn't really that useful15:16
*** saibarsp_ has joined #openstack-dev15:16
*** TxGirlGeek has quit IRC15:16
*** TxGirlGeek has joined #openstack-dev15:17
lbragstadsdague yeah - it reminds me of getting access to a building via a badge and being handed a map of all rooms in the building i have access to15:17
lbragstadinstead of finding the map when i need it15:17
lbragstador just trying the door with my badge and seeing what happens15:17
*** sridharg has quit IRC15:18
sdagueyeh, and because we move that token around on the wire inside of services, there is a non negligible cost to that15:18
sdaguethere was a real performance win in nova to delete most of it15:18
*** saibarspeis has quit IRC15:18
*** jdandrea has quit IRC15:18
*** baoli has quit IRC15:18
lbragstadsdague yeah - i'd believe that15:19
dstaneksdague: not PKI tokens being dead we don't really move the catalog around do we?15:19
sdaguedstanek: honestly, I don't know15:19
dstaneks/not/with/15:19
sdagueI thought it was still in the context15:19
sdagueeither it's all still there, or keystoneauth is doing a thing for us15:20
lbragstadwell - we give it to you unless to explicitly say "give me just a token without the service catalog"15:20
lbragstadsdague aha - right15:20
sdaguebecause we get an API request, have to shuffle it off to nova-compute over RPC, and call cinder by catalog with that token15:20
dstaneklbragstad: on token validation or creation, but that no longer flows between services (i don't think)15:20
*** sree has joined #openstack-dev15:21
*** TxGirlGeek has quit IRC15:21
sdaguedstanek: so I think you are talking about the piece we send back to keystone for validation15:22
sdagueand I think I agree that got smaller here15:22
sdaguebut that doesn't change the part that moves across rabbit between services in the context to the best of my knowledge15:23
sdagueit's not the REST cost, it's the RPC carrying cost15:23
lbragstadthat makes sense15:23
*** TxGirlGeek has joined #openstack-dev15:23
lbragstadso the question is whether or not the entire catalog is being transferred over rpc15:23
sdagueespecially given that rabbit is typically the first scaling challenge sites hit15:24
dstaneksdague: sorta. i was talking about the old PKI way where the catalog was embeded in the token and transfered between services15:24
*** kbringard1 has joined #openstack-dev15:24
sdaguedstanek: between REST services, right?15:24
*** radhikam has joined #openstack-dev15:24
*** kbringard has quit IRC15:24
sdagueI mean intra-service calls over RPC, because you will eventually make another call to another service on behalf of the user you accepted the request from15:24
sdaguen-api -> n-cpu -> n-cond etc15:25
*** achampion has joined #openstack-dev15:25
lbragstadsdague ideally wouldn't it be better to only transmit the token (sans catalog) over RPC and then re-inflate it on the other side if needed?15:25
sdaguehttps://github.com/openstack/nova/blob/37cd9a961b065a07352b49ee72394cb210d8838b/nova/context.py#L102-L10615:25
lbragstadaha15:26
*** hseipp has joined #openstack-dev15:26
sdaguelbragstad: right, which requires a user accessible call to fetch their catalog15:26
dstaneksdague: yep, when pushing around PKI tokens you'd be pushing around the catalog :-( sad!15:26
*** sree has quit IRC15:26
sdaguelbragstad: the fact that volumev3 had to go in that list, means I'm pretty sure it's still an issue15:26
lbragstadright15:26
lbragstadso when nova-compute gets a token via RPC, can it validate the user token for that catalog though?15:27
*** jdandrea has joined #openstack-dev15:27
sdaguenova-compute doesn't validate it15:27
sdagueit uses it15:27
*** cdent has quit IRC15:27
lbragstadsdague so it's only validated on entry into nova (at nova-api?)15:28
sdagueyes15:28
lbragstadok - that makes sense15:28
lbragstadfrom there, nova slims the catalog down into only what it assumes it needs before throwing it on the message bus15:28
sdaguelbragstad: yes15:28
* lbragstad nods15:28
sdaguethose are services we know we look up by catalog point to make calls, so any time you want to add another one in there, you have to put that in the list15:29
lbragstadsure15:29
lbragstadit also means you have to do a bunch of extra process just because in order to slim the catalog down to only what the service needs15:30
lbragstadprocessing*15:30
*** spzala has joined #openstack-dev15:30
sdaguewell, the trim is cheap15:30
sdagueit's just surprising to people15:30
lbragstadit'd be cool if there was a way to provide a nova-only catalog based on the service token used to to validate the user token15:31
smcginnisLooks like we have the same on the Cinder side: https://github.com/openstack/cinder/blob/master/cinder/context.py#L8515:31
sdaguelbragstad: it would also be totally fine if there was a GET /catalog that returned my personalized catalog15:31
*** lucasxu has joined #openstack-dev15:32
sdagueand either hit that explicitly15:32
lbragstadsdague on behalf of the user or the service?15:32
sdagueor bake it into the keystoneauth1.get(service="volume")15:32
lbragstadsdague sorry - i guess my question would be, does nova-compute use that endpoint?15:33
sdaguelbragstad: nova-compute needs to talk to cinder some times15:33
sdagueand it needs to know where cinder is15:33
sdagueon behalf of the user15:33
sdaguethis is user token operations15:33
*** bswartz has quit IRC15:34
sdaguelike provision me a volume15:34
sdagueso I can attach it15:34
lbragstadso, in the new way of doing it, nova-compute would ask for the catalog on behalf of the user via their token15:34
lbragstadfrom keystone15:34
sdagueright15:34
lbragstad++15:34
lbragstadsweet - same page15:34
sdagueand, with our existing programming set you could even embed that in keystoneauth115:34
sdagueso that when the endpoint_filter was applied15:35
*** awaugama has joined #openstack-dev15:35
lbragstadso then you'd really only need to put the token on the message bus, versus any bits of the catalog15:35
sdagueit looks at token... oh hey, no service catalog, fine make the keystone call now to know what to do15:35
sdaguethen you could just turn off getting service catalog in your tokens at a service level and it would all work15:35
sdagueRPC all of the sudden gets much lighter15:36
sdaguefor the cost of an extra keystone call in a few places15:36
*** TxGirlGeek has quit IRC15:37
*** TxGirlGeek has joined #openstack-dev15:38
lbragstadaha15:38
johnthetubaguysdague: I am assuming lots of those extra calls could also get removed via some kind of caching (if tenant_id isn't there, etc)?15:38
sdagueI'm now actually curious if neutron does this trimming as well, because they use the rpc bus even more than just about anyone15:38
* SpamapS catches back up15:39
sdaguejohnthetubaguy: sure, but that's all optimizations15:39
*** baoli has joined #openstack-dev15:39
johnthetubaguysdague: totally15:39
*** xarses has quit IRC15:39
sdagueand keystone already has catching mechanisms on their side, I wouldn't overcomplicate this stuff15:39
SpamapSsdague: FWIW, I'm with you that this is deeply tied to project structure in keystone.15:39
*** marst has joined #openstack-dev15:40
johnthetubaguysdague: you may have just found a way to speed up neutron there?15:40
SpamapSthis isn't something I expect to be split out ever15:40
lbragstadsdague ok - so real quick, we could do the majority of this in keystoneauth, but there would be a couple bits that have to change in nova-compute, too?15:40
lbragstadalong with nova context to not prune the catalog at all?15:41
*** awaugama has quit IRC15:42
SpamapSAnd also I'm 100% on the "get the catalog out of the token" train. :)15:42
sdaguejohnthetubaguy: I don't know, I'm going to throw out a test15:42
SpamapSI could see stuffing a "catalog key" in there. So that you can cache the catalogs and not have to re-fetch when you need it.15:43
sdaguelbragstad: yeh, I think the nova changes for something like this would be minimal15:43
sdagueSpamapS: meh, I think that over complicates things. Catalogs don't change that often15:43
SpamapSSo "when I made this token, the catalog was {uuid}" and then validators can just keep that uuid around.15:44
*** baoli has quit IRC15:44
*** ativelkov has quit IRC15:44
*** dteselkin_ has quit IRC15:44
SpamapSsdague: it's quite useful for users too.15:44
sdaguehave services always go to keystone, keystone cache a reasonably long time, keystone dump cache on any endpoint write call15:44
sdaguekeystone knows if you did something that invalidates the cache15:44
lbragstadwe support that today with all catalog related entries fwiw15:45
SpamapSRight, I want to let the users cache, not just keystone.15:45
SpamapSYou can also just give back an ETag and an Expires and use regular HTTP freshness semantics.15:45
sdagueSpamapS: that's fine, but I think that's an over optimization at this point, with an actual cache busting problem15:46
*** adu has quit IRC15:46
*** ativelkov has joined #openstack-dev15:46
sdagueespecially when there is like 2 cycles of work just to get the flow changed in services, for some potentially great wins15:46
*** adu has joined #openstack-dev15:46
SpamapSYeah, just having catalog out is good.15:46
sdagueSpamapS: yeh, you could definitely ETag it15:46
sdaguethat would be fine15:46
sdagueyou'd still be calling keystone, and it would just 304 you15:47
SpamapSYou can also get lots of users pointed at a single caching HTTP proxy that can manage the freshness.15:47
sdaguesure15:48
SpamapSit's a problem people know how to handle.15:48
SpamapSvs. putting it in the token where it could get weird. :)15:48
sdagueright, absolutely15:48
*** dteselkin has joined #openstack-dev15:48
SpamapSsdague: glad we could go around the horn a bit on the hierarchy limits.. hopefully I haven't slowed the train down too much to get it back up to full speed :-P15:49
lbragstadso - what about the usage of endpoint filters?15:49
sdaguelbragstad: what's the question there?15:49
SpamapSlbragstad: I believe in catalog-next there was some desire to deprecate that particular bit of complexity?15:49
SpamapSLet people filter client side would be my preference.15:49
lbragstadI assume that wouldn't be cachable since it's something that could change depending on the user of the token15:49
SpamapSJust cache the whole durn thing.15:49
*** adu has quit IRC15:50
*** ygbo has quit IRC15:50
lbragstadI think the need there was that some deployments only wanted to expose certain endpoints in a catalog based on if a user had a role assignment on a particular project15:50
sdaguelbragstad: the request just needs to be made in a way that all the relevant parts are exposed at the HTTP level to optimize caching15:50
sdaguelbragstad: right, but sure GET /catalog is personalized15:51
*** ygbo has joined #openstack-dev15:51
sdaguemaybe there is an anon version with some common subset, maybe not, I gave up on anonymous catalog because people wanted this other thing for beta services15:51
*** rajinir_ has joined #openstack-dev15:52
lbragstadso would /v3/auth/catalog work?15:52
lbragstadhttps://developer.openstack.org/api-ref/identity/v3/index.html?expanded=get-service-catalog-detail#authentication-and-token-management15:52
sdagueit could just as well be GET /catalog/{project}/{id} - even though project / id are in the token15:52
*** galstrom_zzz is now known as galstrom15:53
sdaguelbragstad: I think probably15:53
SpamapSyeah I'd say /catalog is "the catalog of things this token will give you some form of access to" is a user-friendly API orientation.15:53
*** athomas has quit IRC15:53
*** TxGirlGeek has quit IRC15:54
*** TxGirlGeek has joined #openstack-dev15:54
SpamapSwhether the services are actually configured that way is unfortunately entirely up to the deployer until we start letting service users set role<->endpoint mappings automatically.15:54
*** ksobkowiak has joined #openstack-dev15:54
*** awaugama has joined #openstack-dev15:55
SpamapSfwiw, on the quota side, I do think either inside placement as a user-oriented API, or something like Boson, is where quota _usages_ will eventually need to be. But I'm now fully convinced that the limits are basically an attribute of projects and users.15:56
SpamapSdstanek: how about you?15:56
*** valw has quit IRC15:57
sdaguelbragstad: right, so with that api existing, I think the bit of code that could be thrown together is have keystoneauth hit that transparently if the endpoint_filter passed isn't found in the token15:57
*** diablo_rojo has joined #openstack-dev15:57
sdaguehonestly, that sounds like a thing a keystoneauth person could do in an afternoon :)15:57
lbragstadright15:57
sdagueand make the magic happen15:57
lbragstadthe keystone bits should be there15:57
*** cdent has joined #openstack-dev15:57
* SpamapS would like to take this moment to remind everyone that keystoneauth is not the way we access keystone. Keystone's REST API is.15:58
SpamapSkeystoneauth is a convenience python library.15:58
sdagueSpamapS: yes15:58
*** TxGirlGeek has quit IRC15:59
sdaguebut, from a service shuttle perspective, we could immediately drop rabbit traffic substantially this release doing something like this15:59
*** rcernin has quit IRC15:59
*** diablo_rojo has quit IRC15:59
lbragstadthis should be something that we can do today in keystone via it's REST API, the keystoneauth bits are convenience for the services (i think?)15:59
sdagueand I 100% this changes the way we describe the common flow to users15:59
sdaguebut, honestly, I think they mostly don't get the current common flow :)16:00
*** Leo_ has joined #openstack-dev16:00
*** athomas has joined #openstack-dev16:00
*** diablo_rojo has joined #openstack-dev16:01
*** baoli has joined #openstack-dev16:01
clarkbcan confirm, am user, do not understand keystone16:01
*** xarses has joined #openstack-dev16:02
sdagueclarkb: ♥16:02
*** armax has joined #openstack-dev16:02
* lbragstad pulls chair up next to clarkb 16:02
lbragstadHello, my name is Lance. I've been working on keystone for 4 years and I still don't understand it.16:02
clarkblbragstad: thats what notmorgan said the other day too :)16:03
*** owalsh is now known as owalsh-afk16:03
*** xarses_ has joined #openstack-dev16:03
lbragstadclarkb sounds like we're all on step 1 ;)16:03
*** TxGirlGeek has joined #openstack-dev16:03
*** halves has joined #openstack-dev16:03
notmorganhello my name is notmorgan and keystone is too insane to understand.16:03
*** achampion has quit IRC16:04
*** galstrom is now known as galstrom_zzz16:04
*** andreww has joined #openstack-dev16:05
*** jmckind has joined #openstack-dev16:05
*** yolanda has joined #openstack-dev16:05
*** jathan has joined #openstack-dev16:05
SpamapSHello, My name is Clint, I've been using OpenStack for 4 years and Keystone    400 Bad Request16:05
*** baoli has quit IRC16:05
*** xarses has quit IRC16:06
*** galstrom_zzz is now known as galstrom16:06
*** xarses has joined #openstack-dev16:07
*** paramite has joined #openstack-dev16:07
*** markvoelker has quit IRC16:07
*** tremble has quit IRC16:07
*** xarses_ has quit IRC16:07
notmorganSpamapS: 500 internal server error16:08
*** andreww has quit IRC16:08
*** Guest76598 has quit IRC16:09
lbragstadsdague SpamapS so - this was good and I want to write it down, mailing list seem appropriate?16:09
notmorgankeystoneauth is a library to ease auth transit. it only alleviates auth interactions and nothing else about Keystone's API.16:10
sdaguelbragstad: wfm16:10
briancurtinlarsks: FYI i’m working on some tweaks to that image download stream change—going to just propose some changes on the patch-set myself, was becoming easier to just write the code out than do it in review comments16:10
*** xarses_ has joined #openstack-dev16:11
*** markvoelker has joined #openstack-dev16:12
*** psachin has quit IRC16:12
*** xarses has quit IRC16:14
*** galstrom is now known as galstrom_zzz16:14
*** galstrom_zzz is now known as galstrom16:15
SpamapSlbragstad: +116:17
*** baoli has joined #openstack-dev16:18
SpamapSnotmorgan: But my point is, like shade, keystoneauth should shine light on the painful APIs we have built, and the community should strive for it to be an empty shell.16:18
SpamapSin 3 years if keystoneauth and shade aren't a thin wrapper on requests I'll be sad.16:19
*** cloudtrainme has joined #openstack-dev16:19
notmorganSpamapS: KSA will always be heavier than shade, for some reasons, but in 3 years if I'm still battling these parts of OpenStack I'll be a lot crankier and unhappy16:20
*** ioggstream has joined #openstack-dev16:20
notmorganso, here is hoping :)16:20
*** ksobkowiak has quit IRC16:20
*** raunak has joined #openstack-dev16:23
*** TxGirlGeek has quit IRC16:23
*** karthiks has quit IRC16:25
*** baoli has quit IRC16:26
*** annegentle has joined #openstack-dev16:26
*** baoli has joined #openstack-dev16:26
sdagueSpamapS: right, I think at some point during the API WG conversations I said... "a key point of this is to delete shade"16:27
*** baoli has quit IRC16:27
sdagueshade is a good example of expressing the real work arounds that are needed for real things16:27
sdagueand those should all move back into the servers and not be a client responsibility16:27
*** baoli has joined #openstack-dev16:28
*** salv-orlando has joined #openstack-dev16:29
*** eharney has quit IRC16:29
*** achampion has joined #openstack-dev16:30
*** tlaxkit has quit IRC16:31
*** baoli has quit IRC16:33
*** kobis has quit IRC16:33
*** ksobkowiak has joined #openstack-dev16:35
*** luizbag has joined #openstack-dev16:36
*** raunak has quit IRC16:36
*** makowals has quit IRC16:36
*** TxGirlGeek has joined #openstack-dev16:36
*** eezhova has quit IRC16:39
*** dtardivel has quit IRC16:40
*** cloudtrainme has quit IRC16:41
*** pcaruana has quit IRC16:42
*** makowals has joined #openstack-dev16:43
*** baoli has joined #openstack-dev16:44
*** rraja has quit IRC16:45
*** baoli has quit IRC16:47
*** _cjones_ has joined #openstack-dev16:49
*** _cjones_ has quit IRC16:49
*** _cjones_ has joined #openstack-dev16:50
*** jmckind_ has joined #openstack-dev16:52
*** trikky_one has quit IRC16:52
*** jmckind has quit IRC16:54
*** svinota has quit IRC16:55
*** saibarsp_ has quit IRC16:55
*** baoli has joined #openstack-dev16:58
*** saibarspeis has joined #openstack-dev16:59
*** e0ne has quit IRC17:00
*** ayogi has joined #openstack-dev17:02
*** sdake has joined #openstack-dev17:02
*** kbringard1 has quit IRC17:05
*** sdake_ has quit IRC17:06
*** eezhova has joined #openstack-dev17:07
*** lucasagomes is now known as lucas-afk17:07
*** cloudtrainme has joined #openstack-dev17:08
*** matrohon has quit IRC17:08
*** lpetrut has quit IRC17:12
*** kbringard1 has joined #openstack-dev17:13
*** rajinir_ is now known as rajinir17:13
*** BLZbubba has joined #openstack-dev17:14
*** TxGirlGeek has quit IRC17:16
*** TxGirlGeek has joined #openstack-dev17:16
*** aasthad has joined #openstack-dev17:19
*** raunak has joined #openstack-dev17:21
*** jpich has quit IRC17:21
*** makowals has quit IRC17:22
*** aolwas has joined #openstack-dev17:23
*** svinota has joined #openstack-dev17:25
*** ioggstream has quit IRC17:29
*** dizquierdo has quit IRC17:29
*** lucasxu has quit IRC17:36
*** rfolco has quit IRC17:37
*** makowals has joined #openstack-dev17:38
*** lucasxu has joined #openstack-dev17:38
*** ayogi has quit IRC17:39
*** ygbo has quit IRC17:40
*** ltomasbo is now known as ltomasbo|away17:41
*** Santhosh_ has joined #openstack-dev17:44
Santhosh__> I am running into an issue while installing openstack through pip inside a docker container. I exported all the openstack variables in shell script and checked the openstack version which is good "openstack 3.8.1". In same script after installing openstack, I am running openstack cli command to create a stack. _> The error I am getting is "openstack: 'stack create' is not an openstack command. See 'openstack --help'."17:44
*** gmoro has quit IRC17:45
*** gmoro has joined #openstack-dev17:45
*** zackf has quit IRC17:46
*** dtantsur is now known as dtantsur|afk17:46
*** krtaylor has quit IRC17:46
*** Shafin has joined #openstack-dev17:48
*** Shafin has left #openstack-dev17:48
*** vnogin has quit IRC17:49
*** fragatina has joined #openstack-dev17:49
*** vnogin has joined #openstack-dev17:49
*** gmoro has quit IRC17:50
*** fragatina has quit IRC17:50
Santhosh_Is the chat room active?17:50
*** jdandrea has quit IRC17:52
*** tesseract has quit IRC17:52
*** jdandrea has joined #openstack-dev17:53
*** vnogin has quit IRC17:54
*** lucasxu has quit IRC17:54
*** hseipp has quit IRC17:54
*** fragatina has joined #openstack-dev17:55
*** mriedem1 has joined #openstack-dev17:56
odyssey4meEmilienM inc0 andymccr v1k0d3n not sure if this affects you but FYI we can expect to see infra mirrors for mariadb 10.0 and 10.1 within the next day as https://review.openstack.org/354203 has merged17:56
EmilienModyssey4me: oh nice17:57
*** akrivoka has quit IRC17:57
EmilienMmwhahaha: ^ I don't think we use it in puppet CI17:57
*** mriedem has quit IRC17:57
EmilienMI think we rely on what distro provide17:57
*** fragatina has quit IRC17:57
*** fragatina has joined #openstack-dev17:58
mwhahaharight that's also just ubuntu17:58
*** fragatina has quit IRC17:58
odyssey4meah, good point - but now it'll be easy enough to extend to centos, which we'd actually like17:58
odyssey4meany volunteers to adjust it for that?17:58
*** gfidente is now known as gfidente|afk17:59
clarkbodyssey4me: I don't see centos packages on the mariadb mirror17:59
*** fragatina has joined #openstack-dev17:59
*** fragatina has quit IRC17:59
clarkbI wonder if they do that because centos/fedora already package mariadb whereas debian/ubuntu have stuck with mysql17:59
EmilienModyssey4me: we use the packages in RDO, already mirrored in centos I think17:59
odyssey4meclarkb yes, originally we only wanted ubuntu - I'll have to push a patch to add centos17:59
clarkbodyssey4me: right, there is no mariadb centos package to mirror though17:59
odyssey4meoh really?18:00
odyssey4mehang a sec18:00
clarkbnot at http://ftp.osuosl.org/pub/mariadb/repo/18:00
odyssey4mehttp://yum.mariadb.org/10.1/centos/7/x86_6418:00
odyssey4meya, different source18:00
*** SumitNaiksatam has joined #openstack-dev18:03
*** paramite has quit IRC18:04
*** ptrlv has joined #openstack-dev18:04
*** spzala has quit IRC18:06
*** iyamahat has joined #openstack-dev18:06
*** erlon has joined #openstack-dev18:08
Santhosh_I am running into an issue while installing openstack through pip inside a docker container. I exported all the openstack variables in shell script and checked the openstack version which is good "openstack 3.8.1". In same script after installing openstack, I am running openstack cli command to create a stack. _> The error I am getting is "openstack: 'stack create' is not an openstack command. See 'openstack --help'."18:09
*** jdandrea has quit IRC18:09
clarkbSanthosh_: I think that the stack subcommand is a plugin to the openstackclient so you need to install additional tools to get that plugin18:10
*** breitz has joined #openstack-dev18:11
Santhosh_you mean the heat I have to install?18:11
clarkbSanthosh_: yes you have to installt the heatclient, as an alternative I think that if you install openstackclient instead of python-openstackclient it installs all of the possible deps/plugins18:11
*** mhickey has quit IRC18:11
*** jaypipes has quit IRC18:12
Santhosh_Thanks @clarkb I am going to try now18:12
*** yamahata has joined #openstack-dev18:12
*** vnogin has joined #openstack-dev18:13
*** TxGirlGeek has quit IRC18:15
*** TxGirlGeek has joined #openstack-dev18:16
*** cloudtrainme has quit IRC18:19
*** TxGirlGeek has quit IRC18:20
*** fragatina has joined #openstack-dev18:21
*** shardy has quit IRC18:21
*** TxGirlGeek has joined #openstack-dev18:22
*** wootehfoot has joined #openstack-dev18:23
*** snica is now known as snica_away18:23
*** Leo_ has quit IRC18:24
*** saibarspeis has quit IRC18:24
*** saibarspeis has joined #openstack-dev18:26
*** mugsie has quit IRC18:26
dimssdague : around for a quick project-config review? (just need to mark a stable compat job non-voting)18:27
dimssdague : https://review.openstack.org/#/c/440737/18:27
*** slaweq_ has quit IRC18:29
dimsclarkb : fungi : one of you, pretty please? ^18:30
dtroyerSanthosh_, clarkb: yup, python-heatclient needs to be installed for OSC to see the 'stack' commands.  The openstackclient package has not been released yet (next week hopefully!) which will install _all_ known plugins to OSC, so simpler for users, many more dependencies...18:30
clarkbdtroyer: thanks for confirming18:31
clarkbdims: isn't the idea that master shouldb't break old branches though?18:32
*** slaweq_ has joined #openstack-dev18:32
*** lucasxu has joined #openstack-dev18:32
dimsclarkb : y, still digging out from under pbr/hacking, need this to dig out of the hole18:35
*** rderose has joined #openstack-dev18:35
clarkbgotcha18:35
*** TxGirlGeek has quit IRC18:35
dimsthanks clarkb !18:36
*** TxGirlGeek has joined #openstack-dev18:37
*** slaweq_ has quit IRC18:38
*** SumitNaiksatam has quit IRC18:39
Santhosh_@Clarkb that worked.. Thanks a lot18:40
*** slaweq_ has joined #openstack-dev18:40
*** spzala has joined #openstack-dev18:43
*** kbringard1 has quit IRC18:45
*** rfolco has joined #openstack-dev18:46
*** kbringard has joined #openstack-dev18:46
*** fragatina has quit IRC18:48
*** fragatina has joined #openstack-dev18:49
*** xemdetia has quit IRC18:51
*** spzala has quit IRC18:51
*** xemdetia has joined #openstack-dev18:52
*** salv-orl_ has joined #openstack-dev18:52
*** eharney has joined #openstack-dev18:53
*** sdake_ has joined #openstack-dev18:54
*** kornica has joined #openstack-dev18:54
*** salv-orlando has quit IRC18:55
*** dhajare has quit IRC18:55
*** sdake has quit IRC18:55
kornicahi guys, does anyone know if it possible to link configuration files to be visible in gate's logs ? Like next to screen outputs ?18:55
jrollkornica: they're in the gate logs in etc/18:55
kornicajroll: for instance here (http://logs.openstack.org/04/436804/2/check/gate-tempest-dsvm-monasca-python-mysql-full-ubuntu-xenial/b2d0a03/logs/etc/) I can see core components' configuration18:56
*** jdandrea has joined #openstack-dev18:56
jrollkornica: oh! I see what you mean18:57
kornicajroll: what I would like to add is configuration of monasca components18:57
jrollthere is a thing, let me poke around18:57
kornicathx18:57
clarkbits an explicit whitelist of things for raisins18:59
clarkbmy ideal world would be we have /etc/openstack and you put everything in there like /etc/openstack/nova/ and /etc/openstack/neutron19:00
clarkbthen we can just grab that entire dir, but not all services allow for different config file locations19:00
jroll+119:00
*** e0ne has joined #openstack-dev19:00
jrollclarkb: my grep foo is failing, do you know where this is offhand?19:01
kornicaclarkb: I see why I couldn't ask in monasca if they would be interested in such migration, devstack is anyway dev environment so that shouldn't matter IMHO. But I cannot speak for the rest of monasca :)19:01
*** _cjones_ has quit IRC19:01
*** _cjones_ has joined #openstack-dev19:01
clarkbjroll: its in d-g somewhere, but my grep foo is also failing19:02
clarkbkornica: its a larger openstack problem. Last I checked (admittedly forever ago) swift expects its config in one hardcoded location19:02
clarkband there were other services that did that too iirc19:02
clarkbjroll: I think its in devstack-gate/functions.sh:cleanup_host somewhere19:02
clarkbya found it19:03
jrollah yeah19:03
jrollso just add to $PROJECTS it seems19:03
clarkbhttps://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n704 yup19:03
*** dizquierdo has joined #openstack-dev19:04
*** krtaylor has joined #openstack-dev19:04
kornicaclarkb: yeah...you're right, actually I stubmled upon this while write specs for rpm-packaging project :/19:06
*** _cjones_ has quit IRC19:06
*** ddyer2 has quit IRC19:06
*** vnogin has quit IRC19:06
kornicawell, if that's about adding to $PROJECTS..seems like it might be more, because I have all components used in gate in PROJECTS list because of git_clone usage19:06
*** mriedem1 is now known as mriedem19:07
kornicaoh...I see how this function works...19:07
kornicawell monasca puts everything into /etc/monasca in devstack19:07
kornicaso more like for service in $SERVICES19:08
kornicaanyway, thx that answers my question, guess ball is on my side19:08
kornicacheers19:08
*** e0ne has quit IRC19:08
clarkbkornica: note that devstack-gate will grab /etc/openstack if its there19:08
*** e0ne has joined #openstack-dev19:09
clarkbkornica: that was put in place so that we could migrate to using /etc/openstack as we are able, maybe you could take advantage of that19:09
kornicaclarkb: yep, I noticed, thx :)19:09
*** thorst has quit IRC19:09
*** dharinic is now known as dharinic|lunch19:09
*** thorst has joined #openstack-dev19:10
*** gszasz has quit IRC19:10
*** vnogin has joined #openstack-dev19:10
*** e0ne has quit IRC19:11
*** valw has joined #openstack-dev19:11
*** ddyer has joined #openstack-dev19:11
*** SumitNaiksatam has joined #openstack-dev19:11
*** claudiub has quit IRC19:12
*** e0ne has joined #openstack-dev19:13
*** valw_ has joined #openstack-dev19:14
*** jdandrea has quit IRC19:14
*** Leo_ has joined #openstack-dev19:14
*** thorst has quit IRC19:14
*** valw has quit IRC19:15
*** sshnaidm is now known as sshnaidm|off19:16
*** lucasxu has quit IRC19:18
*** john-davidge has quit IRC19:19
*** kbringard has quit IRC19:19
*** lucasxu has joined #openstack-dev19:19
*** kbringard has joined #openstack-dev19:19
*** armax has quit IRC19:20
*** valw_ has quit IRC19:23
*** eezhova has quit IRC19:24
*** sdake_ has quit IRC19:24
*** dsariel has joined #openstack-dev19:27
*** jdandrea has joined #openstack-dev19:29
*** electrofelix has quit IRC19:31
*** rarcea has quit IRC19:31
*** armax has joined #openstack-dev19:31
*** mriedem1 has joined #openstack-dev19:31
*** eroux has joined #openstack-dev19:32
*** Rockyg has joined #openstack-dev19:34
*** kobis has joined #openstack-dev19:34
*** ijw has joined #openstack-dev19:34
*** jkilpatr has quit IRC19:35
*** mugsie has joined #openstack-dev19:35
*** jkilpatr has joined #openstack-dev19:35
*** mriedem has quit IRC19:35
*** cdent has quit IRC19:36
*** jcoufal has quit IRC19:37
*** sree has joined #openstack-dev19:37
*** jcoufal has joined #openstack-dev19:38
*** e0ne has quit IRC19:38
*** sree has quit IRC19:42
*** steveg_afk has joined #openstack-dev19:44
*** mriedem1 is now known as mriedem19:44
*** tdasilva has quit IRC19:46
*** dharinic|lunch is now known as dharinic19:50
*** ShaneDavidson has joined #openstack-dev19:50
sdaguestevemar: could you un -2 - https://review.openstack.org/#/c/363765/ ?19:50
stevemarsdague: ack19:50
sdagueso, I guess the follow up question to lbragstad ... that spec is definitely not what we seem to have been building concensus around (there are some bits in there that are a bit off base), would you like to see something else in parallel from a clean slate? or try to iterate on that?19:52
*** jcoufal has quit IRC19:53
lbragstadsdague i'd be fine with either, but if i had to pick a preference I'd say we can do something in parallel.19:53
sdagueok, got a call shortly, I can start on a sketch there shortly19:54
sdaguesee where it heads19:54
lbragstadthen if we decide to go with one proposal over the other we have it clearly defined why and we can abandon the other with a clear reason (versus diffing patch sets)19:54
lbragstadsdague thanks!19:55
sdagueyeh19:55
sdaguehonestly, I'm going to try to keep this a little more high level so we can nail agreement and figure out the exact ways to work out details as we go19:55
*** tdasilva has joined #openstack-dev19:56
*** armax has quit IRC19:58
lbragstadsdague ++ totally agree, i think painting the overall picture will help a lot here19:58
*** cloudtrainme has joined #openstack-dev20:01
*** jamielennox|away is now known as jamielennox20:02
*** yassine has quit IRC20:06
*** bobmel has quit IRC20:10
*** luizbag has quit IRC20:13
*** dizquierdo has quit IRC20:15
*** bobmel has joined #openstack-dev20:18
*** athomas has quit IRC20:24
*** vnogin has quit IRC20:25
*** vnogin has joined #openstack-dev20:25
*** saibarspeis has quit IRC20:27
*** halves has quit IRC20:28
*** claudiub has joined #openstack-dev20:33
*** TxGirlGeek has quit IRC20:33
*** thorst has joined #openstack-dev20:35
*** cloudtrainme has quit IRC20:36
*** vnogin has quit IRC20:37
*** trikky_one has joined #openstack-dev20:37
*** rocky_g has joined #openstack-dev20:38
openstackgerritEmilien Macchi proposed openstack/governance master: [goals/pike] Update Artifacts for WSGI goal in Puppet OpenStack  https://review.openstack.org/44080020:41
EmilienMmwhahaha: ^ fyi20:41
mwhahahak20:41
openstackgerritEmilien Macchi proposed openstack/governance master: [goals/pike] Update Artifacts for Python 3.5 goal in Puppet OpenStack  https://review.openstack.org/44080120:43
EmilienMmwhahaha: and another one ^20:43
openstackgerritEmilien Macchi proposed openstack/governance master: [goals/pike] Update Artifacts for Python 3.5 goal in Puppet OpenStack  https://review.openstack.org/44080120:44
mtreinishEmilienM: you don't want to run puppet's ci jobs with openstack running under py35?20:44
*** jkilpatr has quit IRC20:45
mwhahahamtreinish: we don't run python ci jobs except for docs20:45
EmilienMmtreinish: we strongly rely on what distros provide to us20:45
*** jkilpatr has joined #openstack-dev20:45
mtreinishmwhahaha: you deploy a cloud and hit it with tempest right?20:45
mtreinishyou can run those bits under py3520:45
mwhahahamtreinish: not from source20:46
EmilienMhow?20:46
EmilienMwe install packages from distros (RDO + UCA)20:46
*** DFFlanders has joined #openstack-dev20:47
mtreinishEmilienM: I guess if no one packages it with py3 it makes it more difficult. You could still do it but it would involve a lot of annoying games trying to force a specific version (and you'd be hard time with any c libs with python interfaces used)20:48
mwhahahabut that's not what people are deploying20:49
EmilienMmtreinish: we're not going into this :D20:49
mwhahahai'm all for switching to py3 but for our project it makes no sense to wedge it in if that's not what the end user will actually consume20:49
*** rfolco has quit IRC20:51
*** yassine has joined #openstack-dev20:54
*** READ10 has quit IRC20:54
*** salv-orl_ has quit IRC20:54
jrollwhat would puppet CI with py3 really test?20:55
*** awaugama has quit IRC20:55
jrollpuppet isn't python, there's almost nothing in the puppet codebase that changes based on py 2 vs 320:55
jrollmaybe a couple bizarro configs20:55
jrollbut blame that on the service, not the automation :)20:55
mtreinishjroll: nothing really, I was just thinking it through out loud20:56
mwhahahano he was saying to run our tempest runs in py3, but we run them on the the os provided python20:56
mwhahahawe try and do very little source installs for anything besides the puppet modules themselves20:56
mtreinishbecause it also made me think about when anyone is actually going to be using python 3 for running stuff20:56
mwhahahatempest is a specific case because we do check that out, but we then run it under the distro python20:57
jrollmtreinish: yeah I'm mostly just thinking out loud too :)20:57
*** jaypipes has joined #openstack-dev20:57
*** eezhova has joined #openstack-dev20:57
*** aysyd has quit IRC20:57
*** yassine has quit IRC20:58
*** adriant has joined #openstack-dev20:59
openstackgerritEmilien Macchi proposed openstack/governance master: [goals/pike] Update Artifacts for WSGI goal in TripleO  https://review.openstack.org/44080921:01
amrithsmcginnis, ping. would you please forward the invite to another email address I provided.21:01
smcginnisamrith: Will do21:04
EmilienMjroll: o/ while you're here, here's the main blocker for us to switch into WSGI with apache for ironic api: https://bugs.launchpad.net/ironic/+bug/160825221:04
openstackLaunchpad bug 1608252 in Ironic "Ironic API deployed with Apache: Exception registering nodes: Timed out waiting for a reply to message ID" [High,In progress] - Assigned to Yuriy Zveryanskyy (yzveryanskyy)21:04
jrolluh oh21:04
* jroll runs away21:04
EmilienMjroll: also see https://review.openstack.org/#/c/430851/21:04
EmilienMI'll try again when your gate will deploy ironic api in wsgi21:05
*** gordc has quit IRC21:05
jrollEmilienM: yeah, I'm aware of the second :)21:05
jrollthanks for the bug reference, that feels done but hard to tell21:05
EmilienMcool :D21:06
*** vnogin has joined #openstack-dev21:06
lbragstadSpamapS around?21:08
*** gordc has joined #openstack-dev21:09
*** gordc has quit IRC21:09
*** kriskend has joined #openstack-dev21:10
*** trikky_one has quit IRC21:17
*** TxGirlGeek has joined #openstack-dev21:18
*** kjw3 has joined #openstack-dev21:19
*** spartacloud has joined #openstack-dev21:20
*** cdub has joined #openstack-dev21:21
*** yassine has joined #openstack-dev21:21
*** lpetrut has joined #openstack-dev21:24
*** kgiusti has left #openstack-dev21:26
sdaguelbragstad: ok... so as best that I can english good this afternoon, this is a starting point, I hope - https://review.openstack.org/#/c/440815/1/specs/keystone/backlog/unified-limits.rst21:27
sdagueI really tried to err heavily on concepts, and lets on the details, so we don't lose the forest for the trees.21:27
*** salv-orlando has joined #openstack-dev21:28
*** yassine has quit IRC21:28
sdaguelbragstad: probably worth making sure we've all got similar thing in our head before moving forward21:28
*** bobmel has quit IRC21:28
lbragstadsdague ++ reading through it now21:29
lbragstadsdague should we update the ML thread?21:29
*** bobmel has joined #openstack-dev21:30
*** TxGirlGeek has quit IRC21:32
*** jkilpatr has quit IRC21:34
*** eharney has quit IRC21:34
*** bobmel has quit IRC21:35
*** eroux has quit IRC21:40
*** ansmith has quit IRC21:41
sdaguelbragstad: probably, though the fact that it is a hot off the presses brain dump means I'd like to at least get soft feedback first21:42
sdaguealso, at a minimum it should probably have a references section to the rest of the specs in the space21:42
*** yassine has joined #openstack-dev21:43
*** yassine has quit IRC21:44
*** gordc has joined #openstack-dev21:46
*** jdandrea has quit IRC21:48
*** jdandrea has joined #openstack-dev21:48
dstaneksdague: nice work on the limit spec - it's a good start for sure21:52
*** jkilpatr has joined #openstack-dev21:53
*** kuromagi has quit IRC21:53
*** kuromagi^ has joined #openstack-dev21:53
*** xemdetia has quit IRC21:54
*** anteaya has quit IRC21:54
*** cburgess has quit IRC21:54
*** lpetrut has quit IRC21:55
*** pingveno has quit IRC21:58
*** pingveno has joined #openstack-dev21:59
*** dimtruck is now known as zz_dimtruck21:59
*** cburgess has joined #openstack-dev22:00
*** rderose has quit IRC22:03
*** jdandrea has quit IRC22:04
*** cburgess has quit IRC22:04
*** anteaya has joined #openstack-dev22:06
*** thorst has quit IRC22:08
*** kobis has quit IRC22:09
lbragstaddstanek ++22:09
openstackgerritMatt Riedemann proposed openstack/governance master: Update py35 goal status for Nova  https://review.openstack.org/44083222:09
*** cburgess has joined #openstack-dev22:10
*** kobis has joined #openstack-dev22:11
*** cburgess has quit IRC22:16
*** krtaylor has quit IRC22:17
*** slaweq_ has quit IRC22:17
*** TxGirlGeek has joined #openstack-dev22:17
lbragstadEmilienM ping22:19
mmedvedesdague: do you think it would be ok for a third-party CI to report results on devstack-gate changes (never voting). There is value there, e.g. it would have helped to catch some edge cases with recent transition to local.conf22:19
lbragstadEmilienM just got your note about updating pike goal for each project22:19
*** slaweq_ has joined #openstack-dev22:20
*** alexismonville has quit IRC22:20
EmilienMI'm on my phone22:20
clarkbmmedvede: I think jeblair has resisted that in the past22:20
lbragstadEmilienM oh - no worries, ping when you're available :)22:20
EmilienMlbragstad : I'll ping you back22:21
mmedvedeclarkb: yeah, I recall something like that. jeblair - are you still opposed to third-party CI reporting on d-g?22:21
*** cburgess has joined #openstack-dev22:22
mmedvedeclarkb: thanks, I'll ask him later. Can not find anything in my irc logs22:23
*** jdandrea has joined #openstack-dev22:25
jeblairmmedvede, clarkb: i think it's fundamentally different than the server projects.  i know that we want devstack-gate to be useful to third parties, but i don't think we have defined a concrete api surface and made promises about it.  in that respect, d-g changes are far more likely to affect third-party ci systems, and there is generally little that an author of such a change can do about it.  moreover, we know that it is going to ...22:28
jeblair... radically change in the near future.  i think what i'd rather do is focus on refactoring it into reusable pieces, especially ansible roles, with their own testing and defined api surface.22:28
*** jmckind_ has quit IRC22:31
*** bobmel has joined #openstack-dev22:32
*** zz_dimtruck is now known as dimtruck22:32
openstackgerritLance Bragstad proposed openstack/governance master: Update keystone goals for running in apache  https://review.openstack.org/44084022:32
*** rderose has joined #openstack-dev22:33
*** mriedem1 has joined #openstack-dev22:33
*** mriedem has quit IRC22:34
*** thorst has joined #openstack-dev22:36
*** bobmel has quit IRC22:36
*** thorst has quit IRC22:41
mmedvedejeblair: right. There is no stable interface yet and people use it in various unsupported ways. So third-party CIs would break in any case. My thinking is that allowing reporting on d-g would at least make it easier to third-party operators to debug it22:41
jeblairmmedvede: maybe a third-party ci running on it but not reporting upstream (only reporting locally) would help address the situation?  i feel really awkward saying i support a ci system reporting on a repo when we don't expect people to pay attention to it.22:44
*** takamatsu has quit IRC22:47
mmedvedejeblair: so the CI I support already running on d-g patches, and not reporting. It is harder to see when the change is actually breaking our CI without writing some custom jenkins poller and introducing complexity. While if it was reporting, we could use existing tools, such as ci-watch22:47
*** mriedem1 is now known as mriedem22:48
*** achampion has quit IRC22:50
*** salv-orlando has quit IRC22:51
*** salv-orlando has joined #openstack-dev22:51
*** mriedem has quit IRC22:55
*** breitz has quit IRC23:01
*** breitz has joined #openstack-dev23:02
*** kbringard has quit IRC23:02
mmedvedejeblair: would explicitly specifying in the third-party CI comment that it can be ignored, and for third-party operator benefit only, make it less awkward? Trying to think if there is some way to still report without confusing / distracting devs.23:03
*** ihrachys has quit IRC23:04
*** krtaylor has joined #openstack-dev23:04
*** baoli has quit IRC23:04
*** rocky_g has quit IRC23:05
*** tdasilva has quit IRC23:05
jeblairmmedvede: i'd still prefer to avoid making any changes until after we're running zuulv3.  i think enough is going to change to make a lot of this quickly moot.23:06
jeblairmmedvede: if you're running zuul, there are email or sql reporters you can use to get local reports23:06
*** kriskend_ has joined #openstack-dev23:07
*** priteau has quit IRC23:08
*** sdake has joined #openstack-dev23:09
*** priteau has joined #openstack-dev23:09
*** kriskend has quit IRC23:11
*** ShaneDavidson_ has joined #openstack-dev23:11
*** gordc has quit IRC23:11
*** svinota has quit IRC23:12
*** eezhova has quit IRC23:12
mmedvedeok, not sure exactly how zuul v3 would solve it, other than making it easier to write a custom tool for correlating Infra tests vs third-party test resuts. I'll wait, thanks23:13
*** priteau has quit IRC23:14
*** ShaneDavidson has quit IRC23:15
*** jaypipes has quit IRC23:16
*** thorst has joined #openstack-dev23:17
*** sdake has quit IRC23:18
*** sdake has joined #openstack-dev23:19
*** thorst has quit IRC23:19
*** ShaneDavidson_ has quit IRC23:21
*** ShaneDavidson has joined #openstack-dev23:22
*** lucasxu has quit IRC23:22
*** wootehfoot has quit IRC23:22
*** Leo_ has quit IRC23:23
*** tdasilva has joined #openstack-dev23:23
*** mriedem has joined #openstack-dev23:24
*** erlon has quit IRC23:25
*** kriskend_ has quit IRC23:25
*** svinota has joined #openstack-dev23:27
*** vladikr has quit IRC23:29
*** bobmel has joined #openstack-dev23:31
*** marst has quit IRC23:31
*** baoli has joined #openstack-dev23:33
*** charcol has joined #openstack-dev23:35
*** annegentle has quit IRC23:35
*** bobmel has quit IRC23:37
*** jamielennox is now known as jamielennox|away23:37
*** sdake_ has joined #openstack-dev23:40
*** sdake has quit IRC23:40
*** svinota has quit IRC23:40
*** yassine has joined #openstack-dev23:40
*** TxGirlGeek has quit IRC23:41
*** galstrom is now known as galstrom_zzz23:41
*** marst has joined #openstack-dev23:42
*** bobmel has joined #openstack-dev23:52
*** jmckind has joined #openstack-dev23:52
*** sdake_ has quit IRC23:53
*** cdub has quit IRC23:53
openstackgerritTony Breeds proposed openstack/governance master: [goals/pike] Responses for the WSGI goals for requiremenst and stable  https://review.openstack.org/44086923:54
*** _cjones_ has joined #openstack-dev23:55
*** _cjones_ has quit IRC23:55
*** _cjones_ has joined #openstack-dev23:55
*** bobmel has quit IRC23:56
openstackgerritTony Breeds proposed openstack/governance master: [goals/pike] Responses for the WSGI goals for stable  https://review.openstack.org/44087423:57
openstackgerritTony Breeds proposed openstack/governance master: [goals/pike] Responses for the WSGI goals for requirements and stable  https://review.openstack.org/44086923:57
*** jwcroppe has quit IRC23:59
*** jwcroppe has joined #openstack-dev23:59
*** yassine has quit IRC23:59

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