| *** hrou has joined #swift3 | 00:04 | |
| *** matt___ has joined #swift3 | 04:55 | |
| *** hrou has quit IRC | 04:57 | |
| *** notmyname has quit IRC | 05:00 | |
| *** mattoliverau has quit IRC | 05:00 | |
| *** bill_az has quit IRC | 05:02 | |
| *** notmyname has joined #swift3 | 05:03 | |
| *** bill_az has joined #swift3 | 05:28 | |
| *** matt___ is now known as mattoliverau | 05:59 | |
| *** bill_az has quit IRC | 06:47 | |
| *** openstackgerrit has quit IRC | 09:31 | |
| *** openstackgerrit has joined #swift3 | 09:32 | |
| *** openstackgerrit has quit IRC | 10:31 | |
| *** openstackgerrit has joined #swift3 | 10:32 | |
| openstackgerrit | Kota Tsuyuzaki proposed openstack/swift3: Change HomePage from stackforge to openstack https://review.openstack.org/246357 | 12:23 |
|---|---|---|
| *** bill_az has joined #swift3 | 13:52 | |
| *** hrou has joined #swift3 | 14:33 | |
| *** chsc has joined #swift3 | 15:01 | |
| *** bill_az has quit IRC | 15:44 | |
| gmmaha | i had quick question with S3 and keystone. If i have an existing keystone service running on my machine, all my functional tests start failing | 16:43 |
| gmmaha | the setup_keystone script doesnt seem to check if there is an existing keystone service. Is this intentional to get a kosher environment? | 16:44 |
| timburke | gmmaha: i'd expect it's because when the func tests go to start keystone, the port is already in use. i've run into similar issues when i've left swift running | 16:50 |
| gmmaha | timburke: right. and setup_keystone also tries to modify mysql dbs using a password of its own :( | 16:51 |
| gmmaha | should we put a check and if there is existing keystone read the creds off some conf file for our testing? | 16:51 |
| gmmaha | or even ignore the setup process completely? | 16:51 |
| timburke | gmmaha: i think i'd have to defer to kota_ on that; i'm not necessarily opposed, but at least for me, shutting down the offending service is low-enough overhead that i haven't felt the need to make the func tests smarter | 16:55 |
| gmmaha | aah but the offending service here is keystone itself.. Just setup by me | 16:56 |
| gmmaha | :) | 16:56 |
| gmmaha | so its keystone trumping keystone | 16:56 |
| gmmaha | if you ask why i was running keystone already, that was just to test keystone with swift.. so given an existing setup, i didnt want to bring it down. but i see your point. Shutting down that keystone does make it wokr | 16:57 |
| gmmaha | thanks | 16:57 |
| timburke | i could certainly see it being useful, though, to be able to run func tests against an already-running swift(+keystone)(+whatever) instance; it would probably make some development easier. (i'm thinking of the signature v4 work in particular, which will require changes not just to swift3, but to swift and keystonemiddleware as well) | 17:02 |
| gmmaha | timburke: i am very new to swift3, so not very sure what signature v4 work involves. | 17:08 |
| gmmaha | but more of the ease of dev (setup a system and dont touch it again) was what i was shooting for | 17:08 |
| gmmaha | timburke: is there someway i can get to read about the signature v4 effort | 17:55 |
| timburke | gmmaha: i think it's just a set of patches currently: patch 211933, patch 215481 | 17:57 |
| patchbot | timburke: https://review.openstack.org/#/c/211933/ - support AWS signature v4 | 17:57 |
| patchbot | timburke: https://review.openstack.org/#/c/215481/ - Add S3 signature v4 checking | 17:57 |
| gmmaha | timburke: thanks a lot.. will check it out | 17:57 |
| timburke | thanks! i've been meaning to do a thorough review of the swift3 part, but haven't gotten around to it | 17:59 |
| gmmaha | i will try and review it with my limited knowledge of almost everything in there. :) | 18:15 |
| openstackgerrit | Tim Burke proposed openstack/swift3: Accept URL-encoded x-amz-copy-source headers https://review.openstack.org/246018 | 21:38 |
| *** hrou has quit IRC | 21:59 | |
| *** chsc has quit IRC | 23:50 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!