Monday, 2014-04-14

*** chandan_kumar has joined #openstack-climate04:52
*** tomek_adamczewsk has quit IRC06:08
*** tomek_adamczewsk has joined #openstack-climate06:48
*** bauzas has joined #openstack-climate07:15
*** tomek_adamczewsk has quit IRC07:39
*** tomek_adamczewsk has joined #openstack-climate07:41
openstackgerritA change was merged to stackforge/python-climateclient: Removing dependencies from test-requirements  https://review.openstack.org/8690608:08
bauzasDinaBelova: hi08:44
bauzasDinaBelova: do you know if Nikolay is around today ?08:44
bauzasDinaBelova: https://review.openstack.org/#/c/78309/08:44
bauzasDinaBelova: seems like he got trouble when testing08:44
bauzasDinaBelova: I want to make sure he properly tuned his devstack08:44
bauzasDinaBelova: oh, maybe I found why08:46
bauzasDinaBelova: probably because I haven't added a devstack conf flag08:46
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Add extensions for API v2 controllers  https://review.openstack.org/7830909:00
*** chandan_kumar has quit IRC10:55
DinaBelovabauzas, he has several meetings today11:01
DinaBelovahe's in the office11:01
DinaBelovaI'll catch him11:01
*** chandan_kumar has joined #openstack-climate11:09
*** chandan_kumar has quit IRC11:16
Nikolay_1tbauzas: hi11:26
Nikolay_1tbauzas: i'm here11:26
Nikolay_1tbauzas: what problem have you found?11:26
*** chandan_kumar has joined #openstack-climate11:30
*** cmart has joined #openstack-climate12:17
bauzashi Nikolay_1t13:04
DinaBelova:D13:14
DinaBelovahe just went from the office :D13:14
openstackgerritSwann Croiset proposed a change to stackforge/climate: Host creation: use auto-generated uuid as id  https://review.openstack.org/8726613:15
scroisethi all13:16
scroiset^^^ a simple patch for postgresql13:16
cmartscroiset, hi! it worked for me, but not for Jenkins.. :(13:30
cmartI think that is failing due to some tests :S13:32
*** pafuent has joined #openstack-climate13:46
*** pafuent has quit IRC13:54
bauzascmart: we just discussed with scroiset about that14:04
bauzascmart: a new change will happen14:04
cmartOK!14:06
scroisethumm .. cmart: see my comments on the LP bug ..14:08
cmartgot it! I'll talk to Pablo then (I think that he had some progress with the 2nd option). Thanks!14:10
*** pafuent has joined #openstack-climate14:21
scroisetok thanks14:25
pafuentHi. DinaBelova, bauzas, scroiset, Could you take a look at https://review.openstack.org/#/c/84158/?14:28
bauzaspafuent: my only concern was about where to store the trust_id14:29
bauzaspafuent: I already reviewed your patch14:29
bauzaspafuent: you're storing it in ComputeHost table14:30
bauzaspafuent: IMHO, ComputeHostAllocation would be the best fit14:30
bauzasbecause that's a reservation info14:30
pafuentbauzas: Ok, I'll check it14:31
bauzaspafuent: will place a note14:31
cmartscroiset, are you there?14:35
scroisetyes14:46
pafuentDo we need to do something for this patch https://review.openstack.org/#/c/86777/?14:47
pafuentFails due to a rebase. The updated lines were deleted in https://review.openstack.org/#/c/86906/14:47
pafuentShould someone put a -2 that patch?14:47
cmartscroiset, I'm finishing the tempest stuff and I remember that you told me to add execution instructions on the README file..14:51
scroisetfor the patch https://review.openstack.org/#/c/86777/? .. seems we should abandonned it indeed14:52
cmartI ran my tests by adding a new  "tox" target on the tempest tox.ini file.. and my idea was to add that instructions on the README.. Is that OK for you?14:53
scroisettempest : yes I asekd to you :)14:53
scroisetok for me ... so it will be smth like : tox tempest ?14:54
scroisetbtw, there is an error in the README ..14:54
cmartyeah.. tox -eclimate-scenario..14:54
scroisetnot ./run_tests.sh14:54
scroisetbut ./run_tempest.sh ..14:55
cmartor maybe I could create one that runs all the climate tests..14:55
cmartincluding both cli and scenario tests14:55
scroisetall the tests sounds good14:55
scroisetfor me14:55
cmartOK..14:55
cmartwill do that..14:55
cmartthanks14:56
cmartone quick question.. what is the effect of the "slow" tag?15:00
scroisetfor tox?15:00
cmartyeah15:01
scroisethumm .. I think all tests are run sequentially15:01
scroisetso it's slow15:01
cmartbecause I'm seeing that the heat guys out different targets for those kind of tests..15:01
scroisetforget what I just said .. it's a testr related '--slowest'15:03
cmartand my idea was to create the new tox target with a regex based on the name of the tests files. For instance:  bash tools/pretty_tox.sh '(?!.*\[.*\bslow\b.*\])(^tempest\.(api|scenario|thirdparty|cli)\.resource_reservation) {posargs}15:03
cmartI'm not sure if I should handle them separately..15:03
scroiset.. depending how long are your scenarios  ?15:06
scroisetheat have some tests for autoscaling veryyy long .. (tests are still skipped last time I took a look)15:06
cmartfrom three to five minutes.. it's only one test..15:07
scroisetI would say .. keep it simple for the begin.15:07
scroisetone target should be fine15:08
cmartOK.. I'll remove the slow restriction from my target15:08
pafuentbauzas: Regarding the table of trust_id, seems that I can't put that column in other table. The trust_id is needed to delete the compute host, and seems that you could do that without any reservation.15:08
pafuentbauzas: I'm clear?15:08
cmartit will look like: bash tools/pretty_tox.sh '(^tempest\.(api|scenario|thirdparty|cli)\.resource_reservation) {posargs}15:08
bauzaspafuent: indeed, I looked at the code15:09
bauzaspafuent: you're adding trust_id in the dict15:09
bauzaspafuent: but imho, this shouldn't be stored in ComputeHost15:09
bauzaspafuent: trusts are useful for operations that are needed to be deferred15:11
bauzaspafuent: creating hosts is not one of these15:11
*** chandan_kumar has quit IRC15:11
bauzaspafuent: when thinking at this review, we shouldn't even store trusts15:11
bauzasfor ComputeHosts I mean15:12
bauzaspafuent: and take use of the one in Leases for operating on PR reservations15:12
pafuentbauzas: So I'll need to modify the delete API in order to have a trust to delete the compute host15:12
pafuentbauzas: Are you OK with that?15:14
bauzaspafuent: well, we're discussing it with scroiset15:14
bauzaspafuent: there is a major concern there15:15
bauzaspafuent: we have 2 API endpoints15:15
bauzas1/ for creating leases15:15
bauzas2/ for creating hosts15:15
bauzasfor creating hosts, it requires to be admin15:15
bauzasbut this operation is immediate, no need to store a trust15:16
pafuentbauzas: I agree15:16
bauzaswe can generate a trust and pass it to Nova15:16
bauzasfor the deletion, we can also create a trust15:16
bauzasin terms of security, that's even better to generate another trust for deleting15:17
bauzasbecause the user could have been compromised15:17
bauzasok with the hosts ?15:17
bauzastrusts should remain in memory for the duration of the request15:18
pafuentbauzas: Yes15:18
bauzasok15:18
bauzasabout leases15:18
bauzasthat's another problem15:18
bauzasleases can be performed on a user basis15:18
bauzasnot requiring to be admin15:18
bauzasbut when manipulating Nova aggregates, it has to be done as admin15:19
bauzasand this action needs to be deferred => trust15:20
bauzasbut if we store the user trust and pass it to Nova, it won't work because of not having enough rights for manipulating aggs15:21
bauzasyou got it?15:21
pafuentbauzas: Yes15:22
bauzasso we need to store trust rights having admin rights15:22
pafuentbauzas: So we need some kind of validation that the user that uses PR plugin is an admin, right?15:23
bauzasno15:23
bauzaswe need to find some way to create an admin trustee with a user trustor15:23
bauzasprovided we are a service with admin rightsd15:23
bauzashttp://docs.openstack.org/api/openstack-identity-service/3/content/trusts.html15:25
pafuentbauzas: To check if I got the idea...15:25
pafuentbauzas: Regular user => regular trust15:25
bauzastrustor is climate15:26
bauzastrustee is the user15:26
pafuentbauzas: Because we are a service with admin powers: regular trust => admin trust15:26
bauzasunless I'm wrong15:26
bauzaspafuent: but I'm not that good at trusts :)15:27
bauzaspafuent: maybe DinaBelova could help :)15:27
* DinaBelova reading the logs15:28
bauzasseems like I misunderstood trustor != trustee15:29
bauzaslet me check code15:29
pafuentOK15:29
bauzaspafuent: indeed I'm wrong15:30
pafuentTrusts are immutable. If the trustee wishes to modify the         attributes of the trust, they should create a new trust and         delete the old trust.15:30
bauzaspafuent: https://github.com/stackforge/climate/blob/9552fce675eb9c48f86f2338b97ba79dba7951bb/climate/utils/trusts.py#L2815:30
DinaBelovasomehow I can15:31
pafuentDinaBelova: Hi15:31
DinaBelovacan't get the point of the argument)15:31
DinaBelovapafuent, o/15:31
DinaBelovaI wanted smth like: admin user created host trusts Climate internal user to commit actions like moving host from freepool to the new user's pool15:33
bauzasDinaBelova: well, within a project, an user can be admin, while in another project, he is not15:34
bauzasDinaBelova: but that's a good option15:35
DinaBelovawell, I'm just trying to get the possible solution15:36
pafuentbauzas: In the PR use case, Which kind of user create PR leases?15:36
bauzaspafuent: simple user15:36
DinaBelovaI mean if this admin is global keystone admin - it'll work15:36
bauzasthen OK15:38
pafuentbauzas: DinaBelova: Ok, so we need to store a trust from the user that creates the host, and use that trust when a regular uses create a lease, right?15:38
bauzaspafuent: only for manipulating aggs IMHO15:38
bauzaspafuent: nevermind15:38
bauzaspafuent: yes15:38
pafuentbauzas: So, we are back at the point of where to store that trust, right?15:39
bauzaspafuent: seems so15:39
bauzaspafuent: but at least we get a clear view :)15:39
pafuentbauzas: Yeah, that's rigth15:39
pafuentpafuent: :-D15:40
pafuentbauzas: The reservations and allocations are created with the lease, right?15:40
bauzaspafuent: yup15:40
pafuentbauzas: So we can store the trust there because don't exists at the moment of the host creation15:41
bauzas:)15:41
pafuentbauzas: Sorry, can't store15:41
bauzaspafuent: yup15:41
bauzaspafuent: let's store it in ComputeHosts15:42
bauzaspafuent: sounds like you were right15:42
pafuentbauzas: OK15:43
DinaBelovaokay, cool15:44
bauzaspafuent: maybe a nicer logic would be to get the trust for the host, and use it for moving from agg to agg15:46
bauzasbut if so, we need to iterate over the hosts15:47
bauzasif 2 hosts for one reservation15:47
pafuentbauzas: I'll check that15:48
*** tomek_adamczewsk has quit IRC15:48
pafuentbauzas: Sorry, but I need to go15:48
bauzaspafuent: ok me too15:51
bauzaspafuent: bye15:51
*** bauzas has quit IRC15:53
*** chandan_kumar has joined #openstack-climate16:33
*** tomek_adamczewsk has joined #openstack-climate17:54
*** tomek_adamczewsk has quit IRC18:13
*** pafuent has left #openstack-climate18:18
*** pafuent has joined #openstack-climate18:22
*** tomek_adamczewsk has joined #openstack-climate18:32
openstackgerritChristian Martinez proposed a change to stackforge/climate: Add scenario testing support  https://review.openstack.org/8735218:40
cmart:S:S:S:S18:40
*** chandan_kumar has quit IRC19:22
*** tomek_adamczewsk has quit IRC20:25
*** cmart has quit IRC20:39
openstackgerritCristian A Sanchez proposed a change to stackforge/climate: Change references of tenant to project  https://review.openstack.org/8219220:47
*** tomek_adamczewsk has joined #openstack-climate20:48
openstackgerritCristian A Sanchez proposed a change to stackforge/climate: Change references of tenant to project  https://review.openstack.org/8219221:01
*** pafuent has left #openstack-climate21:10
*** tomek_adamczewsk has quit IRC22:21

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