Wednesday, 2016-05-04

*** btully has joined #openstack-glance00:04
*** rena9067 has quit IRC00:17
*** mtanino has quit IRC00:28
*** btully has quit IRC00:38
*** btully has joined #openstack-glance00:39
*** sdake has quit IRC01:13
*** btully has quit IRC01:31
*** btully has joined #openstack-glance01:32
*** wxy has joined #openstack-glance01:33
*** ozialien10 has joined #openstack-glance01:46
*** ozialien10 has quit IRC01:46
*** ozialien10 has joined #openstack-glance01:47
*** cdelatte has quit IRC02:15
*** buzztroll has quit IRC02:23
*** buzztroll has joined #openstack-glance02:26
*** ducttape_ has joined #openstack-glance02:30
*** buzztroll has quit IRC02:38
*** jaypipes has quit IRC02:40
*** ducttape_ has quit IRC02:45
*** ozialien10 has quit IRC02:52
*** ozialien10 has joined #openstack-glance02:52
*** ducttape_ has joined #openstack-glance02:54
*** ducttape_ has quit IRC03:00
*** ducttape_ has joined #openstack-glance03:03
*** mingdang1 has joined #openstack-glance03:23
*** jamielennox is now known as jamielennox|away03:28
*** jamielennox|away is now known as jamielennox03:37
*** ducttape_ has quit IRC03:46
*** e0ne has joined #openstack-glance03:59
*** e0ne has quit IRC04:01
*** e0ne has joined #openstack-glance04:02
*** e0ne has quit IRC04:05
*** pt_15 has quit IRC04:06
*** itisha has quit IRC04:09
*** links has joined #openstack-glance04:25
*** sgotliv has quit IRC04:28
*** pdeore has joined #openstack-glance04:58
jamielennoxhow do i just run glance unit tests05:18
jamielennoxif i do tox -e py27 in most places it works05:18
jamielennoxbut in glance i get a whole bunch of functional failures first that i can't seem to skip05:18
*** buzztroll has joined #openstack-glance05:23
*** ayoung has quit IRC05:31
*** jamielennox is now known as jamielennox|away05:40
*** mnaser has quit IRC05:41
*** sudipto has joined #openstack-glance05:43
*** mnaser has joined #openstack-glance05:48
*** groen692 has joined #openstack-glance06:02
*** david-lyle has quit IRC06:05
*** openstackgerrit has quit IRC06:17
*** openstackgerrit has joined #openstack-glance06:17
*** tshefi has joined #openstack-glance06:22
*** sudipto has quit IRC06:29
*** mingdang1 has quit IRC06:36
*** e0ne has joined #openstack-glance06:41
*** sudipto has joined #openstack-glance06:45
*** sudipto has quit IRC06:58
*** tesseract has joined #openstack-glance07:01
*** tesseract is now known as Guest2331907:01
*** khushbu has joined #openstack-glance07:02
*** pdeore has quit IRC07:08
*** pdeore has joined #openstack-glance07:09
*** sudipto has joined #openstack-glance07:13
*** jamielennox|away is now known as jamielennox07:22
openstackgerritPankaj Mishra proposed openstack/python-glanceclient: python-glanceclient doesn't support $HOME while uploading image  https://review.openstack.org/31039707:27
*** ayoung has joined #openstack-glance07:49
*** dmk0202 has joined #openstack-glance07:54
*** mvk_ has joined #openstack-glance08:23
*** jistr has joined #openstack-glance08:24
*** mvk has quit IRC08:26
*** ozialien10 has quit IRC08:28
*** ozialien10 has joined #openstack-glance08:29
*** markus_z has joined #openstack-glance08:33
*** mosulica has joined #openstack-glance08:36
*** khushbu has quit IRC08:44
*** sgotliv has joined #openstack-glance08:50
*** sgotliv has quit IRC09:19
*** khushbu has joined #openstack-glance09:19
*** sgotliv has joined #openstack-glance09:20
*** buzztroll has quit IRC09:22
*** khushbu has quit IRC09:46
*** dshakhray has joined #openstack-glance09:48
*** flwang has quit IRC09:54
*** dmk0202 has quit IRC09:59
*** mosulica has quit IRC10:03
*** khushbu has joined #openstack-glance10:04
*** e0ne has quit IRC10:06
*** e0ne has joined #openstack-glance10:06
*** flwang has joined #openstack-glance10:08
*** ozialien10 has quit IRC10:18
*** ozialien10 has joined #openstack-glance10:18
*** mingdang1 has joined #openstack-glance10:37
*** MattMan has quit IRC10:39
*** MattMan has joined #openstack-glance10:39
*** links has quit IRC10:45
*** mvk_ has quit IRC10:46
*** smatzek has joined #openstack-glance10:51
*** smatzek has quit IRC10:56
*** smatzek has joined #openstack-glance10:56
*** david-lyle has joined #openstack-glance10:58
*** buzztroll has joined #openstack-glance11:07
*** buzztroll has quit IRC11:12
*** belmoreira has joined #openstack-glance11:15
*** khushbu has quit IRC11:18
*** sudipto has quit IRC11:41
*** ducttape_ has joined #openstack-glance11:46
*** ducttape_ has quit IRC11:50
*** mvk_ has joined #openstack-glance11:54
*** pdeore has quit IRC11:56
*** links has joined #openstack-glance11:59
*** cdelatte has joined #openstack-glance12:02
*** e0ne has quit IRC12:05
*** jaypipes has joined #openstack-glance12:11
*** burgerk has joined #openstack-glance12:19
*** e0ne has joined #openstack-glance12:22
*** ozialien10 has quit IRC12:24
*** ozialien10 has joined #openstack-glance12:25
*** burgerk has quit IRC12:27
rosmaitaflaper87: put a patch up yesterday, stuart commented, put up PS 2: https://review.openstack.org/#/c/311871/12:39
*** links has quit IRC12:46
hemanthmjokke_: why do you think it's unnecessary?12:47
*** julim has joined #openstack-glance12:47
hemanthmjokke_: we are doing this so that it's easier to maintain our config opts.12:52
hemanthmspecifically it is easier to do the other steps of the categorized config options work.12:55
*** buzztroll has joined #openstack-glance12:55
hemanthmbesides that, if one can see all config opts in one central place, one may re-evaluate the need for adding a new config opt12:56
hemanthmand when adding a new config opt, one would be forced to stick to the help text template and add other required flags because all the opts are doing it12:57
hemanthmand it's going to be easier for reviewers as well12:58
*** buzztroll has quit IRC13:00
*** pt_15 has joined #openstack-glance13:03
kragnizfwiw, I think we have a slightly crazy number of config files13:06
*** krotscheck_dcm is now known as krotscheck13:10
*** burgerk has joined #openstack-glance13:10
*** smatzek has quit IRC13:23
*** sudipto has joined #openstack-glance13:24
*** sudipto has quit IRC13:36
*** d0ugal has quit IRC13:46
*** d0ugal has joined #openstack-glance13:47
*** smatzek has joined #openstack-glance13:47
*** sdake has joined #openstack-glance13:48
*** sdake has quit IRC13:48
*** mingdang1 has quit IRC13:49
*** khushbu has joined #openstack-glance13:50
*** ametts has joined #openstack-glance13:55
*** sigmavirus24_awa is now known as sigmavirus2413:56
flaper87rosmaita: awesome14:02
*** itisha has joined #openstack-glance14:02
*** sdake has joined #openstack-glance14:06
*** dmk0202 has joined #openstack-glance14:14
*** mtanino has joined #openstack-glance14:28
*** ozialien10 has quit IRC14:31
*** julim has quit IRC14:32
*** sgotliv has quit IRC14:32
*** dmk0202 has quit IRC14:33
*** julim has joined #openstack-glance14:34
*** buzztroll has joined #openstack-glance14:44
*** m1r4nt15_b0y is now known as d34dh0r5314:44
*** buzztroll has quit IRC14:48
*** e0ne has quit IRC14:50
johnthetubaguyhemanthm: just thinking about centralise configuration, hows that discussion going?14:53
hemanthmjohnthetubaguy: we are still trying to convince jokke_ who believes it could break things in ways that our tests may not necessarily catch14:56
hemanthmjohnthetubaguy: did you notice config centralization breaking anything in nova so far?14:57
jokke_johnthetubaguy: yet to see any value for it compared to the effort and risk, no14:59
hemanthmjokke_: what is the risk you are referring to here?15:01
hemanthmjokke_: and centralization is not a huge effort by itself but it makes things easier later15:02
jokke_hemanthm: as said yesterday the refactoring has it's risks of breaking things we might not catch and all the rest of youyr points are nicely collected per service on the example config files15:06
hemanthmjokke_: are you concerned that tests won't catch it?15:07
hemanthmjokke_: the example config files are not updated frequently enough for developers' use15:10
*** gb21 has joined #openstack-glance15:10
johnthetubaguyjokke_: so granted the problem is worse in nova than glance, but the why is so its easier to shame config options into getting good option descriptions, and to make it harder to create two different configurations for the same setting, just used in two different bits in the code.15:10
johnthetubaguyjokke_: totally getting the grouping in the sample file, and the better option descriptions is the more important part though15:10
* nikhil scrolls back15:11
johnthetubaguynova builds the configuration sample file and pops that into our developer docs, if that helps with making sure that doesn't break15:11
johnthetubaguythats proved very handy a couple of times15:11
johnthetubaguywe regressed a whole heap of stuff in the transition, but now its more central, its going to be way easier for us to keep that looking good15:11
johnthetubaguyas I say, getting a good experience for the operators is key here, the centralise is just to make it easier for reviews and developers to no regress that work15:12
jokke_hemanthm: now when the example configs does not roll fully around and become 6000 line changes we should be regenaring them with any change that touches the config options15:14
jokke_there is no excuse not to15:14
*** pushkaru has joined #openstack-glance15:14
nikhilI am still fuzzy on what exactly being discussed here15:16
jokke_nikhil: nothing new15:16
hemanthmnikhil: config centralization15:16
nikhilit seems like we are proposing refactor of glance/common/config and the likes of it15:17
nikhilcorrect15:17
nikhil?15:17
nikhil(trying to break down the problem)15:17
hemanthmyes15:17
hemanthmand wherever the config opts are defined15:17
nikhilok, so let's start evaluating this objectively15:17
nikhil1. where will the configs move? (to-from) (some diverse examples)15:18
hemanthmto a new package glance.conf15:18
nikhil2. what is currently being used by operators? glance-api.conf.sample etc.?15:18
nikhil3. where is the breakage expected? code, sample, config builds, reorder of configs?15:19
nikhil4. whom & how is the nova developer documentation helping with currently ?15:20
johnthetubaguycan I do 4.15:20
nikhil5. johnthetubaguy mentioned about something being regressed -- can we define in glance what would be expected & the likelihood?15:20
johnthetubaguyit means every change generates a sample config you can review in the jenkins output, to see what the current output of the sample file is15:21
*** rena9067 has joined #openstack-glance15:21
jokke_So the main question I have been asking without answer is "What this would provide that we do not have available yet?"15:21
nikhilok, I am done with questions. feel free to continue with responses..15:21
johnthetubaguy4 also means you ensure the sample generation doesn't error out at any time (we hit that, for another thing)15:21
johnthetubaguyjokke_: being in one place, its easier to add new configs in a consistent way with existing configurations15:22
johnthetubaguynow thats a big deal for nova, the code base is huge, and most people don't know most of the code base15:22
hemanthm3. the centralization itself should not change the contents of the sample file15:23
hemanthm3. centralization should not result in any content-/structure-related changes in the config files15:24
nikhiljohnthetubaguy: I see, so centralization will help with getting a sense of ~800 config options easily for developers and avoid duplication? the debate seems to be on the value addition for this change to glance15:25
jokke_johnthetubaguy: and that's fair. Fos us, we have the example configs in tree for reference and the code base is not that huge (while still not all bits extra familiar for everyone, like myself). But that centralization also looses the perspective and possible causes those issue the x-proj spec tries to solve where changing one option affects many places. Just because it's easier to not think the consequences and go with "That's similar15:26
nikhilthanks for elaborating #3 hemanthm15:26
johnthetubaguyjokke_: not sure what you mean about the changing one option that affects many places? thats not a problem I have been thinking about at least15:27
nikhilhemanthm: do we have a idea of the reuse of config options for api, registry, scrubber etc?15:27
hemanthmnikhil: yes, we do that now and that would continue to be the case15:28
rosmaitals15:28
hemanthmno change there15:28
jokke_johnthetubaguy: that was one pointer in the x-proj spec or the comments where issues were raised of changing config option causing unexpected behavior somewhere else15:28
rosmaita(sorry)15:28
nikhilrosmaita: :)15:28
johnthetubaguyjokke_: hmm, OK, I don't remember that, its more focused on the deployer issues with using our current config15:29
nikhiljokke_: I see15:29
nikhiljokke_: I am skeptical though, do we check that even today?15:29
nikhiljokke_: if not, we should something about it :)15:30
johnthetubaguywhat we need is deployers not having to read the code to understand how to use a CONF setting15:30
johnthetubaguyso thats kinda included in that, I guess15:30
johnthetubaguyyou need to know what it does15:30
johnthetubaguypart of the exercise is, when its super hard to use, we need to change15:31
jokke_nikhil: we do not have tests for that, if that's what you mean.15:31
nikhilhemanthm: I dunno if that's the case what jokke_ is thinking about as well. where the same config is used by different place in the code base and centralizing may loose some hold on the right changes for the config in future.15:31
nikhiljokke_: yeah15:31
jokke_and I see that as problem if that config is not defined close by.15:32
hemanthmjokke_: we have configs defined in arbitrary places even now. Our configs are not necessarily defined near their usage points15:32
jokke_johnthetubaguy: I totally agree that deployers should not need to read the code. But I don't see how bringing all the config code would help on that. Quite opposite "Why should we do example configs? It's all there in the config module, easy to check there."15:33
hemanthmsome of our configs are in glance/common/config.py and others are scattered all over the place and imported15:34
jokke_hemanthm: great, let's start by fixing that ;)15:34
hemanthmjokke_: I don't think we can.15:34
*** belmoreira has quit IRC15:34
jokke_Bringing it all together even15:35
hemanthmwe can't always have option definitions close to usages15:35
hemanthmit's at least consistent15:35
jokke_hemanthm: that's the reality, but that does not justify taking it all as far as we can either15:35
nikhilhemanthm: yes I agree on that fact, and that's never a possibility15:35
*** dshakhray has quit IRC15:36
hemanthmhere is an example: https://github.com/openstack/glance/blob/master/glance/scrubber.py#L36-L3815:36
hemanthmthat option is not used by scrubber at all15:36
hemanthmit's only used by the API15:37
*** jistr has quit IRC15:37
jokke_but anyways as there doesn't seem to be anything new still around the topic, I'll get back to work. No offence meant to anyone.15:37
johnthetubaguyjokke_: I am more thinking about the docs that describe the config, rather than the sample file, getting good descriptions into the config def15:38
johnthetubaguyso the best approach is probably do whats needed for operators, and see how it works15:38
johnthetubaguynova has found it easer to centralize first, but thats more the case of the scale of the problem15:38
nikhilyeah, I think this will help and may hurt glance. it's a good and bad experience for sure.15:39
jokke_johnthetubaguy: and that I'm really supportive. My point is that we have all the config options and their helptexts grouped in the sample configs. There is no better place to reference them for improvements that the example configs that are directly meant for deployers15:39
*** groen692 has quit IRC15:40
*** tshefi has quit IRC15:40
nikhiljohnthetubaguy: I think this will help in the long term though, at least the session during the summit convinced me.15:40
*** sdake_ has joined #openstack-glance15:41
nikhiljokke_: yeah, I think the problem being solved is for developers as I understood from the session. hemanthm please feel free to correct me if I'm wrong15:42
hemanthmnikhil: it is for the developers15:42
nikhilI think I gave a similar summary in the email as well (hoping that memory served right)15:42
hemanthmthat's mentioned on the spec as well15:42
nikhilit's meant to put guilt feeling in dev mind when they introduce new ones15:42
*** sdake has quit IRC15:43
nikhiland it's meant for helping ops and tech writes to improve configs15:43
nikhilmore of providing a platform for that case15:43
hemanthmwell,  we are not seeking any help from them at this point15:43
nikhilok, good!15:44
hemanthmbut it's to help the developers get a consolidated view of the configs15:44
hemanthmwhich helps in maintaining the config opts15:44
nikhiland I think we need a strong example for it hemanthm15:44
hemanthmthere is a patchset nikhil15:45
nikhilbecause that argument is subjective and resulting in differeing opinions15:45
nikhilthe one you linked in the etherpad?15:45
hemanthmyes15:45
nikhilk, thanks15:45
*** khushbu has quit IRC15:45
hemanthmhttps://review.openstack.org/#/c/303552/15:46
*** davideagnello has joined #openstack-glance15:46
*** sdake_ has quit IRC15:46
*** Guest23319 has quit IRC15:46
hemanthmthere are options that are defined in different modules but depend on each other15:46
hemanthmit'll be easier to discover such dependencies too if we have them all centralized at one place15:47
*** khushbu has joined #openstack-glance15:47
jokke_how? If those dependencies are not documented they won't pop up from anywhere else than the actual code15:47
jokke_and if they are documented, they are also documented in the example configs15:48
hemanthmjokke_: populating the dependencies is a part of the x-proj spec15:48
nikhilyeah, I think this can be elaborated a bit. what was happening before and how it's helping now?15:49
hemanthmlike the config option I mentioned above delayed_delete15:49
*** e0ne has joined #openstack-glance15:49
hemanthmdelayed_delete is an API option but that determines whether or not scrubber options should be set15:50
nikhilhemanthm: is that going to be part of help text?15:50
hemanthmyes15:50
nikhilok, then that's a BIG win!15:50
hemanthmthe help text format has related options section15:51
nikhilbecause that's the only way a new developer will bother to look to introduce such weirdness15:51
hemanthmand once we populate the depedencies through oslo.config flags, it'll be generated via oslo config generator as well15:51
nikhilhemanthm: but that happens today as well right?15:52
hemanthmgenerating dependencies through oslo config generator?15:52
nikhilhemanthm: yeas?15:52
nikhiloh wait, no15:53
nikhiltoday it's generating them all unwisely15:53
hemanthmyes15:53
nikhilputting all irrelevant in the unnnecessary files15:53
nikhilTBH, our sample files are terrible!15:53
nikhilI can rant about them for hours15:53
nikhil there have been at least 5 requests on this channel over the last few months asking what configs are to be set for api and for registry15:54
nikhilbecause they are all mixed up!!15:54
johnthetubaguyso... the centralise is not about helping the deployer, its about giving developers the visibility to update the descriptions so docs and sample config are good  for the deployers, if that makes sense15:54
hemanthm++ johnthetubaguy15:55
nikhiljohnthetubaguy: yes, sorry about side tracking the convo..15:55
hemanthmnikhil: yeah, that's where we want to get at with the x-proj sepc15:55
johnthetubaguynikhil: no worries, side tracks are important15:55
hemanthmonce we categorize opts into required, normal, advanced and deprecated, operators would be able to see exactly what's required to run a particular service15:55
jokke_johnthetubaguy: and that why we have glance/etc/* and why I have been so stubborn not to get rid of them ;)15:56
kairatSo we will consider CONF as global variable then15:56
*** sgotliv has joined #openstack-glance15:56
jokke_johnthetubaguy: now I probably really just need to be even more bitch and demand on the reviews those to be updated when ever the options are touched15:57
nikhiljohnthetubaguy: is the documentation going to be somewhere on *.openstack.org/*/*/config-options ?15:57
kairatDo I understand correctly?15:57
jokke_nikhil: iirc those exists already15:57
nikhilkairat: not python global15:57
nikhilkairat: module globals as they are today15:57
nikhilkairat https://review.openstack.org/#/c/303552/15:58
nikhilI'm looking at that and trying to figure out +s and -s15:58
*** jistr has joined #openstack-glance15:58
nikhilI know there's a install guide15:59
*** davideagnello has quit IRC15:59
kairat++ to nikhil15:59
kairatFor me it looks like we are getting everything in one place just because our code is not structured well16:01
kairatBut maybe I am wrong so need to review better16:01
*** davideagnello has joined #openstack-glance16:01
nikhilkairat: nah, I think the idea is to give a holistic perspective on the configs. the specs (xprj and glance ones) tell a bit of the story but we need wider input here.16:03
kairatCan you please point me to x-proj spec?16:04
nikhilkairat: sure, a sec16:04
hemanthmhttps://review.openstack.org/#/c/295543/16:04
kairatI am interested how this would help long-term16:04
nikhilI, myself, need re-reading and some more input from other teams with smaller codebase16:04
kairatnikhil, thanks!16:04
hemanthmnikhil: keystone maybe a good option16:05
hemanthmthey have done centralization too16:05
nikhilhemanthm: oh I see, thanks.16:05
nikhilI will also look for one that has not done it to see why16:05
*** groen692 has joined #openstack-glance16:06
*** buzztroll has joined #openstack-glance16:07
nikhilThanks all for chatting, I gtg. Let's reconvene later.16:08
jokke_nikhil: you might get directed to project called Glance with reason "Because there is one stubborn core" :P16:08
nikhiljokke_: LOL16:08
flaper87jokke_: make that two16:08
nikhiljokke_: with good reason. I just need one more team to say to that they don't want to else glance would be a odd one out.16:09
*** mine0901 has joined #openstack-glance16:13
johnthetubaguynikhil: I think the docs are already there, I should find the link16:19
johnthetubaguynikhil: this one: http://docs.openstack.org/mitaka/config-reference/16:21
johnthetubaguynikhil: there is another one somehwere though... hmm16:21
*** sdake has joined #openstack-glance16:24
johnthetubaguyso the key bit is making the config options are understood without reading code, the how is totally up to each project16:29
johnthetubaguythe x-project spec is really just sharing what has worked in the past16:29
*** ozialien10 has joined #openstack-glance16:29
*** gb21 has quit IRC16:35
*** ninag has joined #openstack-glance16:38
*** flwang has quit IRC16:39
openstackgerritBrian Rosmaita proposed openstack/glance: WIP: WADL to RST migration  https://review.openstack.org/31225916:41
*** e0ne has quit IRC16:46
*** e0ne has joined #openstack-glance16:47
*** gb21 has joined #openstack-glance16:47
*** tsymanczyk has joined #openstack-glance16:49
*** markus_z has quit IRC16:51
*** jistr has quit IRC16:54
*** sdake has quit IRC16:55
nikhiljohnthetubaguy: ack. thanks for the link!16:55
*** flwang has joined #openstack-glance16:59
*** e0ne has quit IRC17:01
*** e0ne has joined #openstack-glance17:02
*** ninag has quit IRC17:02
*** ninag has joined #openstack-glance17:02
*** rena9067 has quit IRC17:04
*** ninag has quit IRC17:07
*** buzztroll has quit IRC17:26
openstackgerritDarja Shakhray proposed openstack/glance: Add transaction layer  https://review.openstack.org/27211817:32
openstackgerritStuart McLaren proposed openstack/glance: [WIP] Image import: prototype /import implementation  https://review.openstack.org/31265317:36
*** tsymanczyk has quit IRC17:47
*** mvk_ has quit IRC17:53
*** khushbu has quit IRC17:55
*** ninag has joined #openstack-glance18:02
*** ninag has quit IRC18:18
*** ninag has joined #openstack-glance18:19
*** ninag_ has joined #openstack-glance18:20
*** sgotliv has quit IRC18:22
*** ninag has quit IRC18:24
*** ninag_ has quit IRC18:25
*** djkonro has joined #openstack-glance18:25
*** ninag has joined #openstack-glance18:34
*** ninag_ has joined #openstack-glance18:35
*** ninag__ has joined #openstack-glance18:36
*** khushbu has joined #openstack-glance18:37
*** ninag has quit IRC18:38
*** ninag_ has quit IRC18:40
*** ninag__ has quit IRC18:40
*** djkonro has quit IRC18:40
*** sdake has joined #openstack-glance18:42
*** sdake has quit IRC18:44
*** sdake has joined #openstack-glance18:46
*** ninag has joined #openstack-glance18:52
*** ninag has quit IRC18:54
*** djkonro has joined #openstack-glance18:54
*** tsymanczyk has joined #openstack-glance18:54
*** djkonro is now known as Guest9099218:54
*** ninag has joined #openstack-glance18:55
*** mvk_ has joined #openstack-glance19:00
*** itisha has quit IRC19:09
*** buzztroll has joined #openstack-glance19:16
*** e0ne has quit IRC19:23
*** sdake has quit IRC19:25
*** sdake has joined #openstack-glance19:26
*** groen692 has quit IRC19:31
*** tsymanczyk has quit IRC19:31
*** smatzek has quit IRC19:35
*** mkrcmari__ has joined #openstack-glance19:40
*** TravT has quit IRC19:42
*** mvk_ has quit IRC19:44
*** TravT has joined #openstack-glance19:45
*** e0ne has joined #openstack-glance19:46
*** openstackgerrit has quit IRC19:48
*** openstackgerrit has joined #openstack-glance19:48
*** e0ne has quit IRC19:48
openstackgerritHemanth Makkapati proposed openstack/glance: Improve help text of scrubber opts  https://review.openstack.org/31272019:49
*** Guest90992 has quit IRC19:50
openstackgerritHemanth Makkapati proposed openstack/glance: Improve help text of scrubber opts  https://review.openstack.org/31272019:57
hemanthmrosmaita ^19:57
* rosmaita looking19:58
*** e0ne has joined #openstack-glance20:02
*** Guest90992 has joined #openstack-glance20:04
*** e0ne has quit IRC20:07
*** Guest90992 is now known as djkonro20:08
*** harlowja has quit IRC20:09
*** e0ne has joined #openstack-glance20:10
*** cdelatte has quit IRC20:12
*** dmk0202 has joined #openstack-glance20:14
*** mvk_ has joined #openstack-glance20:16
*** mvk has joined #openstack-glance20:18
*** mkrcmari__ has quit IRC20:19
*** mvk_ has quit IRC20:21
*** mkrcmari__ has joined #openstack-glance20:21
*** djkonro has quit IRC20:24
*** mvk has quit IRC20:25
*** buzztroll has quit IRC20:27
*** cdelatte has joined #openstack-glance20:31
*** djkonro has joined #openstack-glance20:37
*** djkonro is now known as Guest6938320:37
*** e0ne has quit IRC20:37
*** mvk has joined #openstack-glance20:41
*** buzztroll has joined #openstack-glance20:42
*** mkrcmari__ has quit IRC20:44
*** mvk_ has joined #openstack-glance20:44
*** mkrcmari__ has joined #openstack-glance20:47
*** mvk has quit IRC20:48
*** buzztroll has quit IRC20:48
*** buzztroll has joined #openstack-glance20:49
*** mvk_ has quit IRC20:50
*** mvk has joined #openstack-glance20:51
ntaylor1781So I am interested in contributing, just trying to make sure I have the process down right. First I would create a blueprint, then I would create a glance-spec (that would have the link to the blueprint). At which point we can discuss the need, befor I would start supplying the code?20:51
*** mkrcmari__ has quit IRC20:53
*** mvk_ has joined #openstack-glance20:53
*** Guest69383 has quit IRC20:54
nikhilntaylor1781: heya!20:55
ntaylor1781Howdy!20:55
*** tsymancz1k has joined #openstack-glance20:55
nikhilntaylor1781: thanks for your interest. What are you interested in contributing?20:55
nikhilntaylor1781: I'm working on finalizing the process and we will have a better answer for you next week. But to clarify your question I need the info :)20:56
*** mkrcmari__ has joined #openstack-glance20:56
*** jaypipes has quit IRC20:56
nikhilrosmaita: tsymancz1k : hello20:56
*** mvk has quit IRC20:56
ntaylor1781So while at the Openstack summit I met with a guy who was working on getting glance to support multiple backends, specifically multiple ceph backends. I have started working on that with him, and want to make sure I do everything right.20:56
tsymancz1khello. my connectivity through all of the symantec firewalls is extremely poor.20:56
nikhilrosmaita: tsymancz1k : you guys wanna discuss Community images spec and do a __init__ convo on it tomorrow's meeting https://review.openstack.org/#/c/271019/ ?20:57
rosmaitasure, we could discuss during tomorrow's meeting20:57
tsymancz1ki'll be there. happy to discuss whatever you want.20:57
nikhiltsymancz1k: ah, np at all. just fyi -- I've been having conn issue so trying out irccloud. it's a web thing so works fine for now.20:57
nikhilrosmaita: tsymancz1k thanks!20:57
nikhilntaylor1781: ok. sure, you want to create a full spec for that as what you say involved a bit of location magic that not many are comfortable with in glance atm.20:58
nikhilntaylor1781: the process is20:58
nikhil1) create a BP in lp20:59
nikhil2) create a spec against openstack/glance-specs repo (using template and older specs to fill out the info)20:59
*** julim has quit IRC20:59
*** mvk_ has quit IRC20:59
*** ducttape_ has joined #openstack-glance21:00
nikhil3) highlight me or someone you talked to at the summit to get that going (glance cores need to determine how much of energy and interest people are putting behind their proposals)21:00
*** mvk_ has joined #openstack-glance21:00
nikhil4) you can continue working on your code once you get a first pass from someone that is positive in your approach and you don't have to wait up on spec approval.21:00
nikhil5) world peace :)21:01
*** julim has joined #openstack-glance21:01
ntaylor1781lol21:01
ntaylor1781perfect thanks.21:01
*** btully has quit IRC21:01
nikhil👍21:01
ntaylor1781Yea my company has desperate need for it, and I'm a huge fan of contributing upstream. I don't like to just patch local versions, especially if other people can benefit from it.21:02
ntaylor1781I will start looking at that, and also go over the glance contributing stuff again, just to make sure I have everything right.21:02
ntaylor1781Thanks for your input!21:02
nikhilntaylor1781: ack. yw!21:02
*** mkrcmari__ has quit IRC21:04
*** Guest69383 has joined #openstack-glance21:07
*** harlowja has joined #openstack-glance21:10
*** Guest69383 has quit IRC21:12
*** sgotliv has joined #openstack-glance21:23
*** mingdang1 has joined #openstack-glance21:26
*** sgotliv has quit IRC21:27
*** sgotliv has joined #openstack-glance21:31
*** pushkaru has quit IRC21:31
*** pushkaru has joined #openstack-glance21:32
*** ninag has quit IRC21:35
*** ducttape_ has quit IRC21:42
*** chlong has quit IRC21:45
*** tsymancz1k has quit IRC21:56
*** dmk0202 has quit IRC22:01
*** chlong has joined #openstack-glance22:05
*** julim has quit IRC22:06
*** buzztroll has quit IRC22:07
*** buzztroll has joined #openstack-glance22:08
*** khushbu has quit IRC22:09
*** sigmavirus24 is now known as sigmavirus24_awa22:21
*** ducttape_ has joined #openstack-glance22:24
*** khushbu has joined #openstack-glance22:31
*** burgerk has quit IRC22:37
*** pushkaru has quit IRC22:42
*** bwallis has joined #openstack-glance22:50
*** ametts has quit IRC22:52
*** harlowja has quit IRC22:52
*** harlowja has joined #openstack-glance22:53
*** khushbu has quit IRC22:54
*** ducttape_ has quit IRC23:00
*** mingdang1 has quit IRC23:01
*** rchurch has quit IRC23:09
*** rchurch has joined #openstack-glance23:10
*** ducttape_ has joined #openstack-glance23:29
*** bapalm_ has quit IRC23:30
*** sdake has quit IRC23:37
*** pushkaru has joined #openstack-glance23:38
*** gb21 has quit IRC23:39
*** gb21 has joined #openstack-glance23:40
*** bwallis has quit IRC23:49
*** davideagnello has quit IRC23:51
*** davideagnello has joined #openstack-glance23:52
*** davideagnello has quit IRC23:56

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