Monday, 2014-01-20

*** Nikolay_St has joined #openstack-climate03:44
*** chandankumar_ has joined #openstack-climate05:26
*** DinaBelova_ is now known as DinaBelova05:40
*** SergeyLukjanov_ is now known as SergeyLukjanov05:40
*** YorikSar has quit IRC05:48
*** DinaBelova has quit IRC06:28
*** DinaBelova has joined #openstack-climate06:31
*** SergeyLukjanov is now known as SergeyLukjanov_a06:59
*** SergeyLukjanov_a is now known as SergeyLukjanov_07:00
*** SergeyLukjanov_ is now known as SergeyLukjanov07:08
*** SergeyLukjanov is now known as SergeyLukjanov_07:18
*** YorikSar has joined #openstack-climate07:22
*** SergeyLukjanov_ is now known as SergeyLukjanov07:53
*** bauzas has joined #openstack-climate08:12
bauzashi folks08:14
bauzasDinaBelova, SergeyLukjanov, Nikolay_St ?08:16
DinaBelovabauzas, o/08:16
bauzaswaiting for SergeyLukjanov08:17
SergeyLukjanovo/08:17
bauzasok, lemme explain my thoughts08:17
bauzasand then you'll comment08:17
Nikolay_Sto/08:17
bauzassounds like there was indeed a misunderstanding, but not about what you think08:17
bauzasfirst, lemme briefly explain again how PR usecase works08:18
bauzasadmin provisions hosts08:18
bauzasinto an aggregate08:18
bauzasuser asks for a reservation set08:18
bauzasClimate then creates an aggregate, but *not visible* to the user08:18
bauzas(currently, it is, because for POC, we needed AZes until the filter got merged)08:19
bauzasat the lease start, Climate takes the hosts from the freepool to the user aggregate08:19
bauzasthe user still doesn't know that he's having a dedicated agg08:20
bauzasthe goal of all that crap is that, when the user will *effectively* ask for a VM, the Climate filter will pick the right hosts from the pool08:20
bauzasso, long story short, with PR, we don't need to inpersonate actions on behalf of the user08:21
bauzasthat said08:21
bauzasand that's exactly what I said, I do understand and reckon the need of trusts08:21
bauzasand you're right, trusts are also for inpersonate actions08:22
bauzasbut the thing is : trusts can only be created by API v308:22
bauzasand consequently, it creates a dependency on a Keystone V3 endpoint08:23
SergeyLukjanovbauzas, it was added by default in Havana08:23
SergeyLukjanovbauzas, so, that's not a problem08:23
bauzasSergeyLukjanov: indeed I knew it :)08:23
SergeyLukjanovbauzas, but what's your concern than?08:24
bauzasI'm not against using the trusts,08:24
bauzasI'm just saying this should be optional08:24
SergeyLukjanovwhy?08:24
bauzasbecause for example, DevStack doesn't create a V3 endpoint...08:25
DinaBelovawe don't need it08:25
SergeyLukjanovbauzas, bah08:25
DinaBelovaas it's done in Heat08:25
DinaBelovathey do not use 3rd endpoint08:25
SergeyLukjanovbauzas, take a look on how Heat works08:25
DinaBelovaNick should rewrite trusts, nobody is trying to deny it08:25
DinaBelovain Heat style08:25
DinaBelovabut still I believe that actions that shoulld be done by some user should be done with his name, token, etc.08:26
SergeyLukjanovv2.0 api is still the default keystone api and all projects using v3 on-demand for stuff like trysts08:26
SergeyLukjanovtrusts(08:26
SergeyLukjanov* :008:26
bauzasSergeyLukjanov: that's exactly what I'm saying :)08:27
bauzasv2 is stil the default api08:27
SergeyLukjanovbauzas, but v3 is always enabled since the H release08:27
bauzasso we need to make sure we can run in such what I'm saying a degraded mode08:27
DinaBelovabut that's not OS style to use things that won't be a default way of doing things next release!08:27
SergeyLukjanovbauzas, there are several facts about current code/reviews - service user creds shouldn't be used only for tokens checks and trusts usage, probably for some read-only ops08:29
SergeyLukjanovbauzas, but not for managing aggregates08:29
DinaBelovabauzas because that's not really a good idea08:29
SergeyLukjanovbauzas, admin user creds should be used for it (admin user how creates such hidden aggregates)08:30
DinaBelovadevstack (with climate) will create climate user08:30
bauzasthat's not what Nova thought about pclouds08:30
bauzasI'm looking at how Heat is dealing with that :)08:31
bauzasthe only pointer I have is https://github.com/openstack/heat/blob/master/heat/common/heat_keystoneclient.py08:31
bauzasdo you have others ?08:31
scroisetused here : heat/engine/clients.py08:32
SergeyLukjanovtrusts was created for the projects like climate08:33
SergeyLukjanovservice account usage is totally incorrect for any write ops08:33
SergeyLukjanovif you'd like to have a centralized user to make such ops08:33
SergeyLukjanovyou just need to add special admin user to confs08:34
SergeyLukjanovfor making it08:34
SergeyLukjanovlike in Heat before the trusts were impletemted08:34
DinaBelovabauzas, yes, it is the main one08:34
SergeyLukjanovbut I dont think any objections why trusts shouldn't be used everywhere08:34
DinaBelovabut we have trusts now :)08:34
DinaBelovayep08:34
SergeyLukjanovso, my point is that aggregates should be created by specific admins to keep track on em08:35
SergeyLukjanovdeleted/removed too08:35
SergeyLukjanovso, just by storing trusts ctx in db for aggregates08:35
SergeyLukjanovit'll be much more secure and trackable08:35
SergeyLukjanovI'm ok with using service user for read-only ops08:36
bauzasok, I think I got your ideas08:36
SergeyLukjanovlike hypervisors query08:37
DinaBelovabauzas, that will be just more secure08:38
bauzasthe thing is, we need to document in the README.md that Climate does require the trusts08:38
bauzasso, here is what I propose08:38
bauzasregarding to the 0.1 release dataz08:39
bauzasdate08:39
bauzashold on, I'm running out of battery08:39
bauzas1. OK for creating a trust by default at the lease creation08:39
bauzas2. we should amend our very poor README.md or document somewhere that we need to enable API v308:40
SergeyLukjanovagreed08:40
DinaBelova+108:40
Nikolay_St+108:40
DinaBelovawe should also define new release date08:40
bauzas3. we log a bug for PR asking to use trusts instead of service creds that we target to 0.1.1 or 0.208:41
DinaBelovabecause I'm quite sure we won't be able to do all this in 2 days08:41
bauzasI don't think we need to postpone08:41
bauzasprovided README.md file says 'enable API v3', it still does work with service accounts08:41
Nikolay_Stmay be it's a good thing to postpone for a week, and may be I can help you with places you want to use trusts?08:41
SergeyLukjanov#3 I'm absolutely disagree that service user could be used for write ops08:41
DinaBelova#3 - that's just unappropriate to use smth like climate user for write ops in nova....08:42
DinaBelovathat's quite incorrect imho08:42
bauzasDinaBelova: SergeyLukjanov: we live with High priority bugs08:42
bauzaseven for the 0.1 release08:42
SergeyLukjanovbut it's totally incorrect08:43
DinaBelovathat's not a bug08:43
SergeyLukjanovit's not a bug08:43
SergeyLukjanov:)08:43
DinaBelovathat's incorrect behaviour08:43
DinaBelovathat just should not exist, I believe :D08:43
bauzasfolks, you reviewed it ;)08:43
SergeyLukjanovso, if you prefer to use dedicated user - use it or use trusts instead08:43
bauzasanyway, I can do an emergency patch today for using trusts08:43
DinaBelovayep.And I'm really sorry i missed that. as said in mail08:44
bauzasor I amend the README.md file for saying to create a dedicated account for climate08:44
bauzasI think we can still reach the date08:44
SergeyLukjanovbauzas, due to tha admin-manier of creating aggregates I'm ok now with both dedicated user and trusts for them08:44
bauzasSergeyLukjanov: so that's only a matter of documenting it ?08:45
SergeyLukjanovdedicated but not service08:45
SergeyLukjanovso, small patch for replacing usage of service acc with special one + docs will be ok for me08:45
DinaBelovain conf file we have now smth like climate user08:45
DinaBelovanot admin special created for that08:45
DinaBelovalike it was in heat before trusts08:46
bauzasok, handling it for this morning08:46
SergeyLukjanovheat was used heat_admin or smth like that08:46
bauzascan do that08:46
SergeyLukjanovok, thx08:46
SergeyLukjanovlooks like we'll need to re-iterate on it after the 0.108:46
DinaBelovabauzas, thank you for starting this discussion08:46
bauzaswill discuss with f_rossigneux for making sure its patch does contain the fix08:46
SergeyLukjanovto cleanup that stuff08:46
bauzaswe need to create a bug for asking to use trusts08:46
DinaBelovabauzas, I'm just happy we found this moment now08:47
DinaBelovanot later08:47
DinaBelovabauzas, +108:47
bauzasok, I'm on it08:47
*** SergeyLukjanov is now known as SergeyLukjanov_08:47
*** DinaBelova is now known as DinaBelova_08:48
bauzasDinaBelova_: https://bugs.launchpad.net/climate/+bug/127076509:29
bauzasplease triage it09:29
bauzaswhile I'm writing the patch :)09:29
Nikolay_Stso09:37
Nikolay_StI lost the point09:37
Nikolay_Stwhat's the final decision about trusts patchset?09:37
bauzas1. ok for using trusts09:38
bauzas2. we need to document it somewhere (probably in readme file) that we need keystone api v309:38
bauzas3. I'm fixing the issue with reservation pools and inventory by creating a separate admin user (flagset)09:39
Nikolay_Stfine09:42
bauzasabout 1., we need to make sure that if trusts won't be available, we will gracefully be able to create the lease thou09:42
*** SergeyLukjanov_ is now known as SergeyLukjanov09:43
*** SergeyLukjanov is now known as SergeyLukjanov_09:48
Nikolay_Stbauzas: about vm plugin and 'only logging'09:58
Nikolay_Stwe prefer not to break service if we have some troubles with vms09:59
Nikolay_Stthat's why we use logging and don't raise any exceptions09:59
Nikolay_Stwe've discussed it with Dina previous Wednesdat, I think10:00
Nikolay_StDinaBelova_: ping10:00
Nikolay_Stbauzas: ping10:00
bauzassorry, was on my patch10:00
bauzasI'm about to send it10:00
Nikolay_Stbtw, I prefer log a bug about 'cannot create lease without v3 api'10:01
bauzasYorikSar already gave -1 for some previous identical patterns10:01
Nikolay_Stnot to fix it now10:01
bauzasie. having an except: clause with a log in it10:01
Nikolay_Stbauzas: I can't get about what are your latest words :(10:03
bauzasok10:04
bauzasI'm just saying that I already saw YorikSar giving a -1 for having a try:except: condition with the except: clause catching the exception and only logging it10:04
bauzasas far as I remember, it was for the reservation pool code10:05
bauzasNikolay_St: the main issue you currently have is that the Manager exceptions are not handled by the API10:05
bauzasthis is due to the fact that AMQP is raising a different Exception10:05
bauzashttps://review.openstack.org/#/c/63445/10:06
bauzasthis one is waiting for a second +2/A10:06
bauzasif the Manager raises an Exception, the API will catch it10:06
bauzasand correctly render the exception to the user10:07
bauzasso, related to your patch10:07
bauzasI would prefer having a way to catch the exception, process what it needs to process, and then raise the exception that API will catch and show to the user10:11
bauzasbecause if not, it will fail silently10:11
bauzasNikolay_St: you see my point ?10:13
Nikolay_Stwell10:14
Nikolay_StI try to get it10:14
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780110:16
bauzasNikolay_St: looking at your code10:17
Nikolay_Stbauzas: on which patch?10:17
bauzashttps://review.openstack.org/#/c/49142/10:17
bauzasL10910:19
bauzasoops10:19
bauzasL89 sorrty10:19
bauzasoh10:20
bauzasgotcha10:20
bauzasthis code is executed by Climate, not coming from the API10:21
bauzasit was late in the evening yesterday, so missed it10:21
Nikolay_Styeap10:21
Nikolay_Stso, what's comment are correct, and which not?10:22
bauzasamending it now10:22
Nikolay_StOk, I'll wait for it10:24
Nikolay_Stso10:24
Nikolay_Stfinally what about:10:25
Nikolay_St14:01 < Nikolay_St> btw, I prefer log a bug about 'cannot create lease without v3 api'10:25
Nikolay_Stbauzas: ?10:25
Nikolay_StDinaBelova_: ?10:25
Nikolay_StSergeyLukjanov_: ?10:25
bauzasNikolay_St: could you please be more explicit ?10:26
bauzasI missed your point10:26
Nikolay_Stok10:27
Nikolay_Stso, I prefer not to make some changes in my patches right know, but just test them 'as is'(close to last comment, of courcse). And after that log the bug about10:28
Nikolay_St'lease creatin failed if we don't use keystone api v3'10:28
bauzasok with it10:28
Nikolay_Stfine10:29
bauzasonce your utils patch got merged, I also need to create a bug for PR using your clients and use trusts10:30
Nikolay_Stwell10:35
Nikolay_Stbauzas: we will have code freeze tomorrow?10:36
bauzascode freeze, but that means you can still produce new patchsets10:36
bauzasprovided it's bug fix10:36
bauzasNikolay_St: I have a bug with my venv10:40
Nikolay_Stbauzas: ?10:40
bauzas(climate)bauzas@climate-devstack-ctrl:~$ cd climate && python setup.py install && cd -10:40
bauzasrunning install10:40
bauzasWheel installs require setuptools >= 0.8 for dist-info support.10:40
bauzaspip's wheel support requires setuptools >= 0.8 for dist-info support.10:40
bauzasStoring debug log for failure in /tmp/tmpSdLwux10:40
bauzaserror: ['/opt/climate/bin/python', '-m', 'pip.__init__', 'install', 'pbr>=0.5.21,<1.0', 'Babel>=1.3', 'eventlet>=0.13.0', 'Flask>=0.10,<1.0', 'iso8601>=0.1.8', 'kombu>=2.4.8', 'oslo.config>=1.2.0', 'python-novaclient>=2.15.0', 'netaddr>=0.7.6', 'python-keystoneclient>=0.4.1', 'Routes>=1.12.3', 'SQLAlchemy>=0.7.8,<=0.7.99', 'stevedore>=0.12', 'WebOb>=1.2.3,<1.3'] returned 110:40
Nikolay_Stbauzas: about keystoneclient version?10:40
bauzasyep, upgrading keystoneclient also upgraded pip to 1.510:41
bauzasand consequently it breaks10:41
Nikolay_Stwow10:41
bauzashow did you fix it ?10:41
bauzasbecause I guess you already deployed keystoneclient-0.4.210:42
Nikolay_StI test all my changes on vm with devstack directly10:44
Nikolay_Stbauzas: so, I haven't this problems10:44
Nikolay_Stbauzas: https://review.openstack.org/#/c/52296/33/climate/exceptions.py is comment right? I think no, am I wrong?10:45
bauzasNikolay_St: if these exceptions are raised by the Manager, by methods called by API10:50
bauzasthen if you want them to appear on the API side, you need a rebase to the patch you just approved10:50
bauzasideally, all Manager defined exceptions should reside in a separate Manager exceptions file10:51
bauzasNikolay_St: what's your pip version ?10:53
bauzaspip -V ?10:53
Nikolay_Stpip 1.4.110:53
bauzaswhen I asked to upgrade to keystoneclient==1.4.2, it pulled me a lot of new deps10:54
bauzasincl. pip-1.510:54
bauzasI'll just amend my reqs.txt file, delete and recreate my venv and see what's wront10:55
bauzasbtw, I still don't see requirements.txt updated in the utils patch10:57
bauzaswhile it should10:57
Nikolay_StI'll update in next patchset10:58
bauzascool10:58
bauzasabout ClimateKeystoneClient10:58
Nikolay_Stso, it's ready I think10:58
bauzasI was a fan of try: except:10:58
bauzaswith the ctx stuff10:58
bauzasthe thing you did with Nova10:58
Nikolay_Stwell, I rewrite it like nova client10:58
bauzasok, cool10:59
Nikolay_Stwith one specific hack10:59
Nikolay_StI guess everything will be okay10:59
bauzasyour reply was speaking about trusts10:59
bauzasyep, think so :)10:59
bauzasthe ideal is that for Nova, if we don't specify a context, the client will handle it anyway :)10:59
Nikolay_StI've seen the way (pathetic)11:00
Nikolay_Stwell, I think the good way for me is to upload next patchsets for trust and utils11:01
Nikolay_Stand then begin testing all this stuff + plugin11:01
bauzasyup11:01
bauzasI'm currently installing my venv11:01
bauzasI kept the same reqs.txt file, I only updated python-keystoneclient to 1.4.211:01
bauzaslet's see if it goes with pip-1.511:02
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780111:05
bauzasit goes with pip-1.1 ...11:06
Nikolay_Stbauzas: https://review.openstack.org/#/c/49142/32/climate/plugins/instances/vm_plugin.py about line 8011:08
Nikolay_Stwhy do you think we can get a loop here? and what exit clause are you thinking of?11:09
bauzasit can potentially iterate over and over with _check_active returning False11:10
bauzasand btw., it will return None if it goes into the LOG.exception()11:11
bauzaswhich also reiterates the loop11:11
Nikolay_Stmm...11:27
Nikolay_Stare you sure that nova haven't any exits itself? I mean, if task status will be the same for a long time, isn't it nova-side problem?11:28
bauzaseven if it's a Nova problem, we should not trust that Nova can handle it :)11:30
Nikolay_StI can't see decision for that problem11:32
bauzasat least, provide an exit way11:33
bauzasiterate until a certain number of times for example...11:33
bauzasor, consider that the exception wil return True11:33
bauzasanything but that infinite loop11:34
openstackgerritNikolay Starodubtsev proposed a change to stackforge/climate: Implement keystone trust support  https://review.openstack.org/4800211:39
openstackgerritNikolay Starodubtsev proposed a change to stackforge/climate: Add utils to work with openstack components  https://review.openstack.org/5229611:39
openstackgerritNikolay Starodubtsev proposed a change to stackforge/climate: Implement basic plugin for VM management  https://review.openstack.org/4914211:39
Nikolay_Stbauzas: are you here?12:12
Nikolay_Stbauzas: http://paste.openstack.org/show/0uRPk8OWfXdvIgnSDCTU/ any suggestion about it?12:12
Nikolay_Stbauzas: fix it myself12:17
bauzassorry, was out for lunch12:22
bauzasNikolay_St: you need to create a policy.json file as given in the etc/ directory12:25
bauzasjust copy it12:25
bauzasetc/policy.json -> /etc/climate/policy.json12:26
bauzasNikolay_St: you there ?12:41
Nikolay_Stbauzas:12:41
Nikolay_Stye12:41
bauzasthe utils review is currently on the zuul pipeline12:41
bauzasbut we already have results12:41
bauzasit fails with the requirements check12:42
bauzashttps://jenkins02.openstack.org/job/gate-climate-requirements/26/console12:42
bauzasthis is a big issue :12:42
bauzashttps://jenkins02.openstack.org/job/gate-climate-requirements/26/console12:43
bauzasoops12:43
bauzasRequirement python-keystoneclient>=0.4.2 does not match openstack/requirements value python-keystoneclient>=0.4.112:43
Nikolay_Styeap12:43
Nikolay_StI see it12:43
Nikolay_Stthat's funny, I think :D12:43
bauzasdunno if python-keystoneclient==0.4.2 would match12:44
bauzasI don't think so12:44
Nikolay_StI'll fix it later in the evening12:47
Nikolay_StI need to go unfortunately12:47
bauzasokay,12:47
bauzasthat's bad, I was about giving a +2 to utils :(12:47
bauzasSergeyLukjanov_: all the zuul pipes are currently queued with climate-devstack-dsvm12:48
bauzasSergeyLukjanov_:12:48
bauzasSergeyLukjanov_: http://status.openstack.org/zuul/12:48
bauzasSergeyLukjanov_: :(12:48
openstackgerritA change was merged to stackforge/climate: Fix Manager exceptions rendering for end-users  https://review.openstack.org/6344512:55
*** SergeyLukjanov_ is now known as SergeyLukjanov12:58
*** DinaBelova_ is now known as DinaBelova12:58
DinaBelovabauzas, guys, I'm finally here....13:01
bauzasDinaBelova: hi13:01
DinaBelovaI had to go afk for an hour, and this hour somehow become much more...13:01
DinaBelovaI hate this day :D13:02
SergeyLukjanovbauzas, heh, looks like lack of the devstack nodes13:02
bauzasDinaBelova: no pb13:02
bauzasthat's bad, the utils patch got a -1 for the requirements13:03
bauzasas for the trusts, I'm amending my comments based on what we discussed today13:03
bauzasbut there are still rewrites to do :(13:03
DinaBelovaYes, I.ve read all conversation13:04
SergeyLukjanovbauzas, all the problems are because i2 freeze tomorrow, everyone want to push something before the release13:04
SergeyLukjanovbtw, I think queue time is about 2-2.5h, not more13:04
DinaBelovaluckly, we are not official OS project now :D so we may postpone release on one day if it will be needed and nobody will notice :D13:05
bauzasyup13:05
bauzasfyi, I suddently noticed that f_rossigneux is on vacation this week...13:05
bauzasso scroiset will handle his patches13:06
bauzashe's about committing new patchsets for the PR13:06
DinaBelovabauzas, ok13:07
DinaBelovaalso13:07
DinaBelovagate job for utils is failing because of that 4.2 keystoneclient version.... that has needed change, but is not defined in global reqs13:08
DinaBelovawe need Nick to do that this evening :D13:08
bauzasDinaBelova: yup, I already discussed this with Nick13:08
bauzashe told me he had to go13:08
DinaBelovayes, I'm just sad he missed fact we need exact req like in global ones...13:09
bauzashttps://review.openstack.org/63445 is needed now13:09
bauzasand the gate is around 2h30 mins13:09
bauzasof delay13:09
DinaBelovaI see it's merged already13:09
bauzashow possible ?13:10
DinaBelovadunno13:10
DinaBelova0_013:10
DinaBelovaStatusMerged13:10
DinaBelova:)13:10
bauzasgotcha...13:10
DinaBelovaI may send you screenshot :D13:10
bauzasno no, seeing it13:10
bauzasbut zuul is telling me that the non-voting devstack gate is still queued for this patch13:11
bauzaszuul is lying13:11
bauzas:p13:11
DinaBelovait might not, really...13:11
DinaBelovamerging may be done without non-voting stuff13:11
bauzaslemme check github13:11
DinaBelovasimetimes it happens with such queues13:11
bauzassure, that's possible13:11
bauzasbut that's a terrible waste of resources13:11
DinaBelovaI remember sometimes I see Jenkins comments about devstack job AFTER actual merge13:12
DinaBelovayep, it is..13:12
bauzasabout Manager exceptions, we really need now to put them in manager/exceptioins.py13:13
bauzaseven if it's not API manageable13:14
DinaBelovaAs I see you've get such change now13:14
DinaBelovaI remember giving you +213:14
DinaBelovafor that13:15
DinaBelovabauzas, smaaaal fix needed https://review.openstack.org/#/c/67801/13:15
bauzassure, say it13:16
DinaBelovaI've publishe small comment13:16
bauzasoh dear13:16
DinaBelovayeep13:16
bauzasI'm on it13:16
DinaBelovaok13:16
bauzasdo you know any good WYSIWYG editor for .md files ?13:16
bauzaswe could btw. move it to .rst no ?13:17
bauzaswhat do you think of it ?13:17
bauzasas I need to publish another patchset13:17
DinaBelovaI love more rst, really13:17
DinaBelovaso i think that's ok13:17
bauzasok, doing it now then13:17
DinaBelovafor changing .md -> .rst13:18
*** SergeyLukjanov is now known as SergeyLukjanov_13:26
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780113:40
bauzasfolks, could I please have a quick review for https://review.openstack.org/#/c/67801/ ?13:41
bauzasscroiset is about to create a dependency on this patch13:41
bauzasand as the PR reviews are 4 to be chained... :)13:41
bauzaswe create a 5th level of dep13:42
openstackgerritNikolay Starodubtsev proposed a change to stackforge/climate: Add utils to work with openstack components  https://review.openstack.org/5229614:01
*** SergeyLukjanov_ is now known as SergeyLukjanov14:04
openstackgerritNikolay Starodubtsev proposed a change to stackforge/climate: Add utils to work with openstack components  https://review.openstack.org/5229614:23
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780114:24
bauzassorry, sent a change without testing it14:25
bauzasblame me or flame me :D14:25
bauzasI do have pep8 compliancy, but that's doesn't cover all the cases :)14:25
DinaBelova:D14:27
DinaBelovamissed that too14:27
DinaBelova:D14:27
DinaBelovabauzas, I guess you saw my link about keystoneclient req to Nick's change14:28
DinaBelova:)14:28
bauzasDinaBelova: indeed, gave a +114:28
DinaBelovayeeep...14:29
bauzassorry, I'm not part of the infra gang14:29
DinaBelovaalso we may look on related bug to that req change14:29
DinaBelovabecause we might have the same error14:29
DinaBelovadon't know now, really14:29
DinaBelovawill see how Jenkins will run jobs14:29
DinaBelovaI mean this bug https://bugs.launchpad.net/nova/+bug/126861414:29
bauzasdon't think so14:30
bauzaswe don't have a gate for this14:30
DinaBelovaoh, yep14:31
DinaBelovain my dreams we have :D14:31
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780114:46
bauzasDinaBelova: could you please +2 again ? Swann needed the patch to be rebased14:46
bauzasthanks14:47
DinaBelova:)14:47
bauzasNikolay_St: https://review.openstack.org/#/c/52296/14:48
bauzasyou reverted to keystoneclient-0.4.114:48
bauzasso, I can propose to vote +2 for it14:48
bauzasbut we create a bug14:49
bauzasfor keeping track of the need14:49
bauzasyou OK ?14:49
bauzasDinaBelova: Nikolay_St ?14:49
DinaBelovabauzas, the problem here is14:49
DinaBelovathat we have no real opportunity to merge that unlit that patch to global reqs will be merged14:50
DinaBelovaNick uses 4.2 specific things14:50
DinaBelovaso we NEED to be sure 4.2 will be installed, not 4.114:50
DinaBelovaso we need to write 4.2 in reqs really14:50
DinaBelovabut we won't pass gate until that change to global reqs will be merged14:51
DinaBelovathat's some kind of circle here...14:51
bauzaswell, here are my thoughts14:51
*** SergeyLukjanov is now known as SergeyLukjanov_a14:51
bauzasthe code is almost functional, except that keystoneclient14:52
bauzaswe are blocking a patch because of another14:52
bauzasso, maybe Nick can gracefully handle the miss of keystoneclient.Client() and provides a clear error message14:52
*** SergeyLukjanov_a is now known as SergeyLukjanov_14:52
bauzasso that there is a clear need14:53
bauzasand once the requirements gate got updated, we both upgrade reqs.txt and we remove the try:exception: clause14:53
bauzasI'm particularly concerned about when this requirements gate would be updated14:54
bauzasand I don't want to be stuck because of it14:54
DinaBelovaI suppose you're right here14:54
openstackgerritSwann Croiset proposed a change to stackforge/climate: Physical host reservation plugin  https://review.openstack.org/5428514:54
openstackgerritSwann Croiset proposed a change to stackforge/climate: Physical host reservation (manager and base plugin)  https://review.openstack.org/6470614:54
openstackgerritSwann Croiset proposed a change to stackforge/climate: Physical host reservation (DB related things)  https://review.openstack.org/6470514:54
DinaBelovawill you write Nick comments about that try/except clause for using 4.2 specific moments?14:55
bauzaswill do14:55
DinaBelovaok14:55
DinaBelovahttps://review.openstack.org/#/c/52296/34/climate/utils/openstack/keystone.py, line 76 is that moment14:58
bauzasindeed I know15:01
bauzasfigure out that'me who asked for that line ;)15:01
bauzascomments left15:07
DinaBelovaok, tnx15:10
*** DinaBelova is now known as DinaBelova_15:16
*** SergeyLukjanov_ is now known as SergeyLukjanov15:19
*** DinaBelova_ is now known as DinaBelova15:20
bauzasfolks, I'm currently testing the DB query filter per tenant_id15:22
bauzasthere are chances to have a new patchset now that we have policies in place15:23
bauzasI also need to make sure the patch can be merged with latest patches15:23
*** oblako has joined #openstack-climate15:33
DinaBelovaok15:46
*** oblako has quit IRC15:53
*** SergeyLukjanov is now known as SergeyLukjanov_16:09
*** DinaBelova is now known as DinaBelova_16:17
*** DinaBelova_ is now known as DinaBelova16:39
*** exaggeration has joined #openstack-climate17:03
bauzasDinaBelova: ping ?17:04
DinaBelovabauzas, pong17:04
bauzasI finished up testing filtering out tenants17:04
bauzasthat workds17:04
bauzasworks17:04
bauzasthere is a corollary, still :D17:05
bauzasadmins can only leases from their own tenant17:05
bauzasso, I can propose 2 things :17:05
bauzas1. leave as it is, but add a flag --all-tenants17:05
bauzasthat requires 2 patches, one for the API (will be in the same CR as for the filter), and one for the client17:06
bauzas2. idendifies that's an admin and provide him all results17:06
bauzaswhat are your preference ?17:06
bauzass/are/is17:06
bauzas(sorry, a bit tired)17:06
bauzasDinaBelova: ?17:07
DinaBelovabauzas, sorry, needed to go for 5 mins :)17:09
DinaBelovaI'm here now :)17:09
DinaBelovareading your messages17:09
bauzasno pb, I'm about to leave17:09
bauzaswill work this evening17:09
bauzasI want to finish this patch17:09
bauzasand btw, the way I filter is not the best, IMHO17:10
bauzasbut we're running out of time17:10
DinaBelovaI think second one is now ok17:10
*** exaggeration has quit IRC17:10
bauzasok, will use the policy then17:10
DinaBelovaok17:10
bauzasand check the is_admin policy17:11
DinaBelovabauzas, thank you for your efforts :)17:11
bauzaswe all are on the same boat :)17:11
bauzasand I really *want* Climate to get its 0.1 soon17:12
DinaBelova:D17:12
DinaBelovayou are not alone :)17:13
*** bauzas has quit IRC17:13
*** chandankumar_ has quit IRC17:42
*** SergeyLukjanov_ is now known as SergeyLukjanov17:52
*** chandankumar_ has joined #openstack-climate18:03
*** SergeyLukjanov is now known as SergeyLukjanov_a18:24
*** SergeyLukjanov_a is now known as SergeyLukjanov_18:25
openstackgerritA change was merged to stackforge/climate: Fix service user creating objects  https://review.openstack.org/6780118:39
*** chandankumar_ has quit IRC18:44
*** SergeyLukjanov_ is now known as SergeyLukjanov19:02
*** SergeyLukjanov is now known as SergeyLukjanov_a19:31
*** SergeyLukjanov_a is now known as SergeyLukjanov_19:32
*** SergeyLukjanov_ is now known as SergeyLukjanov19:35
*** malchevsky has joined #openstack-climate19:51
*** callow has joined #openstack-climate20:02
*** callow has quit IRC20:15
*** SergeyLukjanov is now known as SergeyLukjanov_20:22
*** bauzas has joined #openstack-climate20:28
*** germesfinans has joined #openstack-climate20:43
*** germesfinans has quit IRC20:44
*** malchevsky has quit IRC20:57
*** DinaBelova is now known as DinaBelova_21:00
*** sviblovo has joined #openstack-climate21:05
*** sviblovo has quit IRC21:17
*** fnmath has joined #openstack-climate21:23
*** cherok has joined #openstack-climate21:35
*** fnmath has quit IRC21:52
*** cherok has quit IRC22:16
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Filter DB queries per project_id  https://review.openstack.org/5910923:25

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