Tuesday, 2018-02-06

*** arcolife has quit IRC00:03
*** mtreinish has quit IRC00:12
*** edmondsw has joined #openstack-glance00:21
*** edmondsw has quit IRC00:25
*** r-daneel has quit IRC00:29
*** mtreinish has joined #openstack-glance00:37
*** Supun has joined #openstack-glance00:50
*** Dinesh_Bhor has joined #openstack-glance00:54
*** Dinesh_Bhor has quit IRC00:56
*** Dinesh_Bhor has joined #openstack-glance01:07
*** dalgaaf has quit IRC01:15
*** dalgaaf has joined #openstack-glance01:16
*** Dinesh_Bhor has quit IRC01:17
*** Dinesh_Bhor has joined #openstack-glance01:18
*** Dinesh_Bhor has quit IRC01:21
*** Supun has quit IRC01:23
*** Dinesh_Bhor has joined #openstack-glance01:47
*** Dinesh_Bhor has quit IRC01:50
*** sapd__ has quit IRC02:04
*** sapd has joined #openstack-glance02:06
*** edmondsw has joined #openstack-glance02:09
*** Dinesh_Bhor has joined #openstack-glance02:12
*** itlinux has joined #openstack-glance02:13
*** edmondsw has quit IRC02:14
*** Dinesh_Bhor has quit IRC02:15
*** harlowja has quit IRC02:18
*** markvoelker has joined #openstack-glance02:22
*** markvoelker has quit IRC02:24
*** markvoelker has joined #openstack-glance02:31
*** Dinesh_Bhor has joined #openstack-glance02:31
*** itlinux has quit IRC02:43
*** bkopilov has quit IRC02:50
*** markvoelker has quit IRC02:56
*** markvoelker has joined #openstack-glance02:59
*** idlemind has joined #openstack-glance03:08
idlemindhey, running stable/pike from openstack-ansible ... in glance i have show_multiple_locations = False and i have policy.json configured for "" for (delete, get, set)_image_location and i get 403 Forbidden: It's not allowed to add locations if locations are invisible. (HTTP 403) ... if i set show_image_location to True it all works but it get a log message about deprecation ... at point does show_image_location go away03:10
idlemindand defer to rbac?03:10
*** markvoelker has quit IRC03:11
*** markvoelker has joined #openstack-glance03:14
*** d0ugal_ has joined #openstack-glance03:16
*** d0ugal has quit IRC03:19
*** markvoelker has quit IRC03:25
*** gcb has joined #openstack-glance03:26
*** gyee has quit IRC03:29
*** markvoelker has joined #openstack-glance03:30
*** markvoelker has quit IRC03:42
*** pdeore has joined #openstack-glance03:47
*** jdurgin has quit IRC03:50
*** jdurgin has joined #openstack-glance03:52
*** edmondsw has joined #openstack-glance03:58
*** edmondsw has quit IRC04:02
*** bkopilov has joined #openstack-glance04:08
*** pooja_jadhav has joined #openstack-glance04:11
*** udesale has joined #openstack-glance04:13
rosmaitaidlemind show_multiple_locations will not go away for queens, there are some complications making it difficult to remove that setting and use rbac only ... we plan to come up with a solution during the Rocky planning sessions at the PTG in Dublin at the end of february04:19
*** abhishekk has joined #openstack-glance04:21
*** ratailor has joined #openstack-glance04:22
bhagyashrisrosmaita: Thanks for review :) waiting for other's opinion04:40
rosmaitayes, hopefully we'll hear something soon ... otherwise, i will just make a decision!04:41
bhagyashrisrosmaita: ok thank you :)04:43
*** pgadige__ has joined #openstack-glance04:44
*** harlowja has joined #openstack-glance04:46
ShilpaRosmaita: Hi04:47
ShilpaThank you for reviewing.04:47
rosmaitaShilpa no problem, sorry about the delay04:47
Shilpano problem, you are too busy, i know04:48
*** rosmaita has quit IRC04:53
*** zhurong has quit IRC05:07
*** harlowja has quit IRC05:11
*** links has joined #openstack-glance05:12
*** itlinux has joined #openstack-glance05:17
*** edmondsw has joined #openstack-glance05:46
openstackgerritMerged openstack/glance master: Modify glance manage db sync to use EMC  https://review.openstack.org/43393405:47
*** edmondsw has quit IRC05:50
*** itlinux has quit IRC05:55
*** pdeore has quit IRC05:57
*** pdeore has joined #openstack-glance05:57
*** gcb has quit IRC06:00
*** Dinesh_Bhor has quit IRC06:04
*** e0ne has joined #openstack-glance06:04
*** Dinesh_Bhor has joined #openstack-glance06:05
*** Dinesh__Bhor has joined #openstack-glance06:09
*** Dinesh_Bhor has quit IRC06:10
*** d0ugal_ has quit IRC06:14
*** takedakn has joined #openstack-glance06:18
*** takedakn has quit IRC06:19
*** d0ugal_ has joined #openstack-glance06:23
*** ratailor_ has joined #openstack-glance06:36
*** mosulica has joined #openstack-glance06:38
*** ratailor has quit IRC06:38
*** threestrands has quit IRC06:40
*** Dinesh__Bhor has quit IRC06:57
*** mosulica has quit IRC07:06
*** Dinesh__Bhor has joined #openstack-glance07:08
*** zhurong has joined #openstack-glance07:09
*** Dinesh__Bhor has quit IRC07:10
*** gcb has joined #openstack-glance07:13
*** e0ne has quit IRC07:22
*** tshefi has joined #openstack-glance07:23
*** AlexeyAbashkin has joined #openstack-glance07:32
*** rcernin has quit IRC07:37
*** AlexeyAbashkin has quit IRC07:39
*** bhagyashris has quit IRC07:42
*** AlexeyAbashkin has joined #openstack-glance07:48
openstackgerritwangdequn proposed openstack/glance master: correct url in comments  https://review.openstack.org/54116607:51
*** alexchadin has joined #openstack-glance08:02
*** twouters_ has quit IRC08:11
*** twouters_ has joined #openstack-glance08:11
*** twouters_ is now known as twouters08:11
*** pcaruana has joined #openstack-glance08:14
*** abhishekk has quit IRC08:21
*** tesseract has joined #openstack-glance08:22
*** bhagyashris has joined #openstack-glance08:25
*** zhurong has quit IRC08:38
*** Dinesh__Bhor has joined #openstack-glance08:39
*** abhishekk has joined #openstack-glance08:41
*** frti has joined #openstack-glance08:48
*** d0ugal_ has quit IRC08:57
*** alexchadin has quit IRC08:57
*** d0ugal has joined #openstack-glance08:57
*** d0ugal has quit IRC08:57
*** d0ugal has joined #openstack-glance08:57
*** alexchadin has joined #openstack-glance08:58
*** Dinesh__Bhor has quit IRC09:00
*** zhurong has joined #openstack-glance09:03
*** Dinesh__Bhor has joined #openstack-glance09:04
*** e0ne has joined #openstack-glance09:05
*** threestrands has joined #openstack-glance09:06
*** threestrands has quit IRC09:21
*** frti_ has joined #openstack-glance09:21
*** edmondsw has joined #openstack-glance09:22
*** wxy has quit IRC09:22
*** pgadige__ has left #openstack-glance09:23
*** frti_ has quit IRC09:25
*** frti has quit IRC09:25
*** edmondsw has quit IRC09:27
*** hoonetorg has quit IRC09:28
*** pooja_jadhav is now known as neha_alhat09:32
*** hoonetorg has joined #openstack-glance09:41
*** arcolife has joined #openstack-glance09:43
*** takedakn has joined #openstack-glance09:49
*** takedakn has quit IRC09:54
*** Dinesh__Bhor has quit IRC09:57
*** amrith has left #openstack-glance10:04
*** alexchadin has quit IRC10:22
*** dtantsur|afk is now known as dtantsur10:25
*** alexchadin has joined #openstack-glance10:25
*** bkopilov has quit IRC10:27
*** abhishekk has quit IRC10:27
-openstackstatus- NOTICE: Our Zuul infrastructure is currently experiencing some problems and processing jobs very slowly, we're investigating. Please do not approve or recheck changes for now.10:29
*** alexchadin has quit IRC10:30
*** alexchadin has joined #openstack-glance10:30
*** alexchadin has quit IRC10:30
*** alexchadin has joined #openstack-glance10:31
*** alexchadin has quit IRC10:31
*** alexchadin has joined #openstack-glance10:32
*** alexchadin has quit IRC10:32
*** alexchadin has joined #openstack-glance10:33
*** alexchadin has quit IRC10:33
*** aniketh has joined #openstack-glance11:08
*** edmondsw has joined #openstack-glance11:10
*** alexchadin has joined #openstack-glance11:11
*** edmondsw has quit IRC11:15
*** udesale has quit IRC11:22
*** nicolasbock has joined #openstack-glance11:26
*** links has quit IRC11:41
*** links has joined #openstack-glance11:54
*** Supun has joined #openstack-glance11:57
*** mosulica has joined #openstack-glance12:09
*** arcolife has quit IRC12:13
*** pdeore has quit IRC12:14
*** ratailor_ has quit IRC12:33
*** links has quit IRC12:55
*** takamatsu has joined #openstack-glance12:56
*** AlexeyAbashkin has quit IRC12:59
*** zhurong_ has joined #openstack-glance13:01
*** AlexeyAbashkin has joined #openstack-glance13:01
*** udesale has joined #openstack-glance13:02
*** zhurong has quit IRC13:08
*** links has joined #openstack-glance13:08
*** edmondsw has joined #openstack-glance13:13
*** udesale has quit IRC13:21
*** udesale has joined #openstack-glance13:22
*** alexchadin has quit IRC13:22
*** alexchadin has joined #openstack-glance13:23
*** AlexeyAbashkin has quit IRC13:25
*** Supun has quit IRC13:27
*** AlexeyAbashkin has joined #openstack-glance13:27
*** bkopilov has joined #openstack-glance13:27
*** Supun has joined #openstack-glance13:28
*** AlexeyAbashkin has quit IRC13:38
*** zhurong_ has quit IRC13:52
*** tshefi_ has joined #openstack-glance13:53
*** tshefi has quit IRC13:55
idlemindrosmaita thanks for the clarification14:11
*** abhishekk has joined #openstack-glance14:13
*** rosmaita has joined #openstack-glance14:20
rosmaitajokke_ ping me when you have a few minutes14:21
*** pdeore has joined #openstack-glance14:21
abhishekkrosmaita, hi good morning14:22
rosmaitaabhishekk good evening!14:23
rosmaitaabhishekk got a few minutes?14:23
abhishekkrosmaita, yes14:23
jokke_rosmaita: ping14:23
rosmaitagreat, jokke_ is here too14:24
rosmaitaok, got something to run past you14:24
rosmaitai am thinking that we keep 2.6 experimental in Queens14:24
rosmaitait's my fault, i should've organized the effort better14:25
rosmaitabut here is why:14:25
rosmaita(1) the discovery API is going to change, at least with respect to responses and schemas14:25
rosmaita(2) i think we need to harden the plugin interface14:26
rosmaitaor at least provide some docs about how to use it better14:26
*** tshefi_ has quit IRC14:26
rosmaitayou may have seen my comments on the metadata injection patch14:26
rosmaitai'm worried that we are making the image_repo kind of an API14:26
* jokke_ goes and looks14:26
rosmaitanot for end users, but for operators14:26
abhishekkrosmaita, I have checked your those comments, which makes sense14:27
rosmaitastuart had a concern about the "old" tasks interface that opened up all of the glance infrastructure for operators to monkey with14:27
rosmaitanow, it's true that they have all the source code and can patch as they will14:28
rosmaitabut it's probably better if we provide a basic infrastructure for them to use14:28
rosmaitaanyway, i'd look at this as an "extended feedback period" before we finalize the image import API14:28
rosmaitathat sucks for the next PTL, I know, because continued work on image import will make it less likely that other stuff will get done14:29
bhagyashrisrosmaita, Hi good morning, just want to discuss regarding comments given on patch https://review.openstack.org/#/c/455837/ by you and some replies given by abhishekk so i would like to see your opinion on it.14:30
rosmaitabhagyashris sure, let me finish this conversation with jokke_ and abhishekk and then i will read through14:30
bhagyashrisrosmaita, ok14:30
abhishekkrosmaita, it will not be that much work though14:31
rosmaitawell, that would be good14:31
rosmaitain fact, it would be quite excellent14:31
abhishekkright,14:32
rosmaitai think we need to provide a bit more structure around the plugins, get the discovery stuff working, and then we are ready for a "real" API14:32
rosmaitaas part of that, my secret plan is to modernize our json-schema usage14:33
abhishekkI am inclined towards keeping 2.6 experimental in queens14:33
rosmaitait would be great if for R-1 we have 2.6 non-experimental, and by R-2 have v1 ripped out14:34
jokke_rosmaita: (1) the discovery API is going to extend ... we will not have 2.6 current by 2025 if we wait that to finalize (2) not sure what you mean ... are you proposing that we write yet another abstraction layer to the onion just for the plugins?14:34
*** AlexeyAbashkin has joined #openstack-glance14:35
rosmaitafor (2), no, not necessarily, but we do need some docs about what the image_repo is, and we also need to agree ("we" == glance community) that we won't make changes to the image_repo, because it needs to be stable14:36
*** pdeore has quit IRC14:36
*** dtantsur is now known as dtantsur|bbl14:37
rosmaitaas for (1), i may have been looking at the wrong patch, but is the whitelist/blackllist implemented for web-download?14:37
*** links has quit IRC14:38
rosmaitaaddendum to the above: by R-1, we need to have v1 removed from devstack14:39
jokke_rosmaita: no, I might have misunderstood the agreement of having v1 feature par there that will be hardened and how is that affecting the discovery, are we supposed to expose that there?14:40
rosmaitayou're right, its a separate issue14:41
jokke_It might not be a bad idea, I'm just failing to remember seeing such on any of the spec requirements for it14:41
rosmaitabut i mean the way we've been promoting it is that web-download will do copy-from the right way14:41
rosmaitai'm afraid if we release it in a current API, the assumption will be that the protections are there14:42
rosmaitaand they are not14:42
rosmaitathe discovery issue is that if we make 2.6 current now, we'll have to do 2.7 in rocky14:42
rosmaitai'd rather have 2.6 be 2.5 + interoperable image import completed (more or less)14:43
jokke_I see your point and that would be simple to fix by not enabling the web-download by default and documenting it in the reno14:44
jokke_which would enable the people relying still v1 api get same level of functionality without relying experimental API14:45
jokke_which is even more red flag for lots of production environments than running deprecated one14:45
rosmaitai guess the other thing that worries me is no glanceclient support for web-download14:46
*** alexchadin has quit IRC14:48
jokke_it's fairly difficult to implement and release client featuring something that is not in the API ;)14:48
rosmaitathis is completely off-topic, but when does ocata go EOL?14:48
rosmaitasmcginnis ^^14:48
jokke_I don't think it does14:48
smcginnisrosmaita: Ocata will be EOL at the end of February.14:49
smcginnisFeb 26 is the officially published date.14:49
rosmaitasmcginnis asking because i am wasting a lot of time trying to restore the gates14:49
jokke_smcginnis: so we still EOL we just don't remove the branches or how did that stable keeparound went?14:50
rosmaitaand if it's going EOL, maybe it doesn't matter?14:50
smcginnisrosmaita: It would be good to get it working, at least to be able to cut one final official upstream version of Ocata.14:50
smcginnisBut all things being equal, I think there are more pressing issues at the moment.14:51
smcginnisjokke_: We remove the branches, but not the tag.14:51
jokke_smcginnis: I don't also think there has been anything merged into it since last tag14:51
smcginnisOr rather, we add an "ocata-eol" tag at the point where it was branched.14:51
rosmaitaok, i have to rebuild a new environment ... the amount of stuff broken in there is truly distressing14:51
rosmaitai'm starting to wonder if it's because i've got some bad sh*t hanging around14:51
jokke_smcginnis: that was supposed to change based on the decisions made in SYD14:51
smcginnisjokke_: Ah, if there's nothing in there since last time, I would drop it a notch or two on the priority list.14:52
jokke_smcginnis: or is that just from some future release onwards14:52
smcginnisjokke_: I know there was some talk about keeping it, but I didn't see an "official" decision.14:52
rosmaitahttp://git.openstack.org/cgit/openstack/glance?h=stable%2Focata14:52
rosmaitajokke_ is correct, nothing new in there from the glance side14:53
*** shilpa_ has joined #openstack-glance14:53
smcginnisEven if we do end up keeping the stable/ocata branch, we will stop running full gate testing against it.14:53
jokke_smcginnis: yeah, that would be expected14:53
smcginnisrosmaita: Have you been able to narrow down the nature of the failures?14:53
rosmaitai've got about 500 of these atm: oslo_config.cfg.RequiredOptError: value required for option auth-url in group [keystone_authtoken]14:53
rosmaitai had to backport the eventlet stuff14:54
jokke_it's just matter of how much we care if -eol tag has broken tests or if existing branch has broken tests14:54
rosmaitaand the fixtures import that i put into stable/pike14:54
* jokke_ is trying to figure out how long implications it would have to just forget the ocata tests for now14:54
rosmaitaand then went 2 more down to modernize our eventlet usage14:54
smcginnisMaybe worth pinging keystone to see if they've seen that error before?14:54
rosmaitawell, that's why i want to do a rebuild first ... it doesn't make sense becasue i don't think any keystone stuff was updated in u-c for ocata14:55
rosmaitasame with oslo-config14:56
jokke_rosmaita: is that one of those things that broke since moving to zuulv3?14:56
rosmaitajokke_ not sure14:56
smcginnisThat's what I'm wondering, but don't immediately see how.14:56
jokke_Might be just difference how the environment is built and it does not bake that in and we never did either because it was coming from the env14:57
smcginnisThere were a lot of docs jobs failures from the new zuul setup, but I would be surprised if it would cause something like this.14:57
smcginnisMaybe another system package difference?14:57
rosmaitamaybe i should just put the patch up with what i have now and see what happens in the gate14:57
abhishekkrosmaita, anything I can do here?14:58
rosmaitaabhishekk i'll shoot you an email if there's something you can look at in the morning14:59
abhishekkrosmaita, great14:59
rosmaitaright now, you need to convince jokke_ that keeping 2.6 experimental is a good idea14:59
rosmaita:)14:59
abhishekkrosmaita, :D14:59
rosmaitawe should probably all sleep on that idea actually, since i just sprung it on everyone15:00
jokke_it's not a good idea ... it will put me in quite difficult spot in up- and downstreams for next cycle, but ultimately it's not my call to make15:00
abhishekkjokke_, is their a quick way to resolve rosmaita's concerns?15:02
rosmaitawell, if you are ok with having to do a 2.7, then it's not a big deal15:02
jokke_my take is that version numbers are cheap and as we're not microversioning it will not cause huge mess of tech dept for us. The point for having it experimental was to gather feedback if we're going to totally wrong direction on this and need to do some backwards incompatible changes to the process once people are actually able to try it15:05
jokke_I'd be way more in favor if that was the case but so far the feedback has been couraging, not demanding ofr change15:06
rosmaitawell, that's a good point15:06
rosmaitai am worried that the pressure to microversion would be a PITA15:06
rosmaitabut you seem to be able to handle that pressure just fine :D15:06
rosmaitaok, tell you what15:07
rosmaitalet me draft some release notes/documentation for making 2.6 current15:07
rosmaitawe don't have to include them in RC-115:07
rosmaitabut it will give me a better idea of what exactly the state of the API is15:07
jokke_as long as we're confident that we do not need to break that API, as it seems atm. I'd be pro of "CURRENT"ing it15:08
jokke_obviously if that's not the case I might change my mind quite rapidly ;)15:08
rosmaitai am pretty confident that we won't break it, just extend it15:08
*** Supun has quit IRC15:08
jokke_That's how it has been looking to me as well15:08
rosmaitaok, i will think really carefully about this today and have a more detailed analysis tomorrow15:09
jokke_and we have been fine doing that all along the v215:09
rosmaitajokke_ you are back from lunch, right?15:09
jokke_Obviously if we do make it current, that will put presure for me to prioritize to implement the client parts asap so we have released client that is compatible with the Queens and has that functionality available15:10
jokke_rosmaita: it's past 3PM so yeah15:10
rosmaitai need a few min of your time15:11
*** mnaser has quit IRC15:11
jokke_shoot15:11
rosmaitahere's what i am backporting to stable/ocata: http://paste.openstack.org/show/663467/15:12
*** mnaser has joined #openstack-glance15:12
rosmaitamy question is about the one at the bottom15:12
rosmaitathe eventlet we are using in ocata is 0.19.015:13
*** abhishekk is now known as abhishekk|meetin15:13
*** dtantsur|bbl is now known as dtantsur15:14
rosmaitafor stable/pike, those 2 commits at the bottom were already there15:14
jokke_I would not backport that unless it makes the other backports impossible/pain in the bollox15:15
rosmaitaTBH, i don't remember if it helped or not15:16
rosmaitaok, i will do a new branch without that one and see what happens15:16
rosmaitawhen's your end-of-day today?15:17
jokke_hmm-m ... interestingly I do not find that commit ID from master15:17
rosmaitathat15:19
rosmaita's weird , i did a cherry-pick -x15:20
jokke_I found the commit15:20
*** bhagyashris_ has joined #openstack-glance15:20
jokke_yeah, that should not change too much and it's not something we should backport to this support phase anymore as it does not affect only tests nor is super critical15:23
jokke_obviously if you see world breaking without it, it might be easier to do15:24
jokke_ /cleaner15:24
rosmaitaagreed, am setting up a clean vm now to work in15:24
*** shilpa__ has joined #openstack-glance15:32
*** shilpa_ has quit IRC15:33
*** shilpa__ has quit IRC15:35
*** jungleboyj has quit IRC15:36
*** jungleboyj has joined #openstack-glance15:36
*** Supun has joined #openstack-glance15:39
rosmaitajokke_ when you have a minute, please look at https://review.openstack.org/#/c/540490/ (it's the backport to stable/pike) ... i forgot to ask abhishekk why he only gave it a +115:40
abhishekk|meetinrosmaita, I am not a stable maintainer atm15:41
rosmaitaabhishekk|meetin ty, forgot about that15:41
abhishekk|meetinrosmaita, no issues15:41
rosmaitai think the only active stable maintainers are co-authors of that patch!15:42
*** Supun has quit IRC15:44
*** dtantsur is now known as dtantsur|bbl15:49
*** pcaruana has quit IRC15:51
jokke_rosmaita: I think we should ping one of the stable-cores to +2A that15:52
jokke_flaper87 is still on that list15:53
jokke_was it tests/docs only affecting change I'd be ok to ninja it in between the two of us15:55
*** r-daneel has joined #openstack-glance16:01
*** mosulica has quit IRC16:14
*** abhishekk|meetin has quit IRC16:16
*** e0ne has quit IRC16:22
*** itlinux has joined #openstack-glance16:34
*** _alastor__ has joined #openstack-glance16:39
*** bhagyashris_ has quit IRC16:44
*** pbourke has joined #openstack-glance16:51
*** pbourke has quit IRC17:02
*** gyee has joined #openstack-glance17:02
*** pbourke has joined #openstack-glance17:04
*** r-daneel has quit IRC17:22
*** r-daneel has joined #openstack-glance17:22
*** AlexeyAbashkin has quit IRC17:25
*** AlexeyAbashkin has joined #openstack-glance17:25
*** udesale has quit IRC17:25
*** AlexeyAbashkin has quit IRC17:29
pbourkehi, wondering has anyone run 'tox -epy27' from behind a proxy recently?17:34
*** mine0901 has joined #openstack-glance17:37
*** mtreinish has quit IRC17:43
rosmaitapbourke you mean from master? should be ok, those are only unit tests now17:49
rosmaitaprior to about 2 weeks ago they were both unit & functional17:49
pbourkerosmaita: yeah, I'm just seeing an issue I think with this patch from stuart https://review.openstack.org/#/c/316965/17:50
*** mtreinish has joined #openstack-glance17:50
pbourkeit's odd to me that he used 0.0.0.0:1 rather than say 127.0.0.1 which will be in most people's $no_proxy17:50
*** jose-phillips has left #openstack-glance17:50
pbourkeif it set $no_proxy=0.0.0.0:1 the tests run but that kind of sucks...17:50
*** NostawRm has quit IRC17:57
pbourkerosmaita: I'll put up a patch to replace that and see what people think17:57
*** NostawRm has joined #openstack-glance17:57
rosmaitapbourke i have no objection, though unless it's causing gate issues, probably won't be looked at for a while17:58
pbourkekk17:58
rosmaitai don't remember why stuart used the zero ip, but i noticed that ian +2'd it, and he'17:58
rosmaitas really careful about that kind of thing, so there must have been a good reason17:59
rosmaitathat is unfortunately lost to posterity17:59
rosmaitabut we can discuss on the patch, maybe someone will remember17:59
rosmaitathanks!17:59
pbourkethanks also :)18:00
*** tesseract has quit IRC18:00
openstackgerritPaul Bourke (pbourke) proposed openstack/glance master: Fix some api tests when behind http proxy  https://review.openstack.org/54139018:07
*** dtantsur|bbl is now known as dtantsur18:22
*** harlowja has joined #openstack-glance18:35
*** pooja-jadhav has joined #openstack-glance18:50
*** niraj_singh has joined #openstack-glance18:52
*** nsingh has quit IRC18:55
*** neha_alhat has quit IRC18:55
*** AlexeyAbashkin has joined #openstack-glance19:00
*** r-daneel_ has joined #openstack-glance19:08
*** r-daneel has quit IRC19:09
*** r-daneel_ is now known as r-daneel19:09
anikethrosmaita, jokke_: Ping19:11
anikethSorry for asking, again and again, Since I was trying to contribute to Glance and move to GSoC afterwards - I was OpenStack through devstack. Is it better to be followed for contributing to Glance as well or is there something else? I'm asking because, I encountered some errors while setting up devstack and still on building that. Would you assist me in bulding it, please :)19:15
clarkbaniketh: it would probably help if you could share the errors you have encountered with devstack19:15
clarkbyou can paste the devstack log into a paste service and share that here19:16
anikethclarkb: alright! I'm setting up my VM right now, it has some issues related to its sources list I guess. Let me fix that and will get to you :D19:19
rosmaitaaniketh: what clarkb said, also this page may help: https://docs.openstack.org/nova/13.1.2/development.environment.html19:21
rosmaitayou want to make sure you've got all the right packages installed to do development19:22
anikethrosmaita: Okay, thanks :D19:23
anikethSo, is it better to have devstack set up done right?19:24
rosmaitai think so ... make sure you install the "prerequisite packages" listed on that page19:25
rosmaitaalso, make sure you set it up in some kind of virtual machine ... every so often it will get hosed and it's easier to just throw it away and build a new one19:26
anikethAlright!19:27
anikethI am using KVM for that. :)19:27
*** dtantsur is now known as dtantsur|afk20:03
*** r-daneel_ has joined #openstack-glance20:16
*** r-daneel has quit IRC20:17
*** r-daneel_ is now known as r-daneel20:17
anikethI'm facing this kinda error right now: http://dpaste.com/31TX02M20:22
anikethrosmaita: ^20:22
rosmaitalooking20:24
*** e0ne has joined #openstack-glance20:24
aniketh:D20:25
clarkblooking at that I think we need more context to debug. Can you share the entire devstack log? and maybe the localrc too?20:27
anikethclarkb: local.conf?20:29
rosmaitayep20:30
clarkbaniketh: yes sorry20:30
anikethclarkb: debstack log: http://dpaste.com/1T2J3V920:32
anikethclarkb: local.conf: http://dpaste.com/13MNBCZ20:34
clarkbaniketh: the problem appears to start at 2018-02-06 20:30:41.81020:36
clarkbit is trying to clone the openstack/requirements repo into /opt/stack/requirements directory but that directory exists and is not a git repo? or at least isn't a complete git repo20:36
clarkbaniketh: can you see what you have in /opt/stack/requirements?20:36
anikethclarkb: It is empty20:37
clarkbaniketh: ok you might try deleting that directory20:37
clarkband any other directories under /opt/stack/ if they are empty20:37
anikethalright!20:38
anikethnot devstack right?20:38
anikethclarkb: *20:38
clarkbonly if the directory is empty but devstack shouldn't be if it is running from there20:38
clarkbthe problem is devstack seems to assume that if the directory exists it will be a valid git repo20:39
clarkband the requirements repo is not a valid repo it is empty20:39
rosmaitaaniketh : where did you clone devstack to on your machine?20:39
anikethoh, okay!20:39
anikethrosmaita: /opt/stack20:39
rosmaitai never do that20:40
rosmaitaso it may or may not work20:40
rosmaitai usually clone to my home directory as a regular user with sudo powers20:40
rosmaitaand then run stack.sh out of there20:40
anikethrosmaita: oh!20:40
anikeththe reference which I20:40
rosmaitathe installer will create /opt/stack if necessary and put all the repos in there20:41
anikeththe reference which I'm following asks me to do that20:41
rosmaitaoh20:41
rosmaitamy build-devstack process is from around folsom20:42
rosmaita:)20:42
rosmaitathere have probably been a lot of improvements20:42
anikethoh!20:42
anikethSo, what should I do? Continue what I'm doing rn or ?20:43
anikethhttps://nishayadavsite.wordpress.com/2016/06/29/how-to-set-up-work-environment-to-become-an-openstack-developer/20:43
rosmaitawhat reference are you using?20:43
rosmaita:)20:43
anikethThis is what am following btw20:43
anikethIt looks simple that's why :D20:43
rosmaitanothing wrong with that!20:44
rosmaitai guess check the permissions on /opt/stack20:45
rosmaitamake sure your stack user owns it20:45
rosmaitaotherwise that guide looks good20:47
anikethyes it does.20:47
anikethokay, cool. Thanks :D20:47
rosmaitaone thing i do, not sure you need to any more, is sudo apt-get python-pip20:48
rosmaitaactually, i see she does that in section 820:48
rosmaitaand it looks like she has you set /opt/stack as the home directory for the 'stack' user20:50
rosmaitaso the permissions should be ok20:51
rosmaitathat's a good guide20:52
rosmaitai guess, just delete everything in /opt/stack and start over20:53
*** takamatsu has quit IRC21:01
*** e0ne has quit IRC21:01
*** e0ne has joined #openstack-glance21:17
*** AlexeyAbashkin has quit IRC21:21
*** threestrands has joined #openstack-glance21:32
*** threestrands has quit IRC21:32
*** threestrands has joined #openstack-glance21:32
*** itlinux has quit IRC21:50
*** itlinux has joined #openstack-glance21:55
*** e0ne has quit IRC22:15
*** openstackgerrit has quit IRC22:16
*** rcernin has joined #openstack-glance22:28
*** edmondsw has quit IRC22:37
*** edmondsw has joined #openstack-glance22:38
*** edmondsw has quit IRC22:42
*** itlinux has quit IRC22:53
*** r-daneel has quit IRC23:12
*** r-daneel has joined #openstack-glance23:13
*** MattMan has quit IRC23:37
*** MattMan has joined #openstack-glance23:38

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