Thursday, 2015-02-05

achhabraHow can I run "Swift All In One" setup with a python debugger? I am interested in stepping through the Swift code as a request is processed.00:04
*** dkingshott has quit IRC00:05
*** dmsimard is now known as dmsimard_away00:17
*** ho has joined #openstack-swift00:17
*** annegent_ has quit IRC00:20
*** achhabra has quit IRC00:24
*** annegent_ has joined #openstack-swift00:33
*** gyee has quit IRC00:34
*** dmorita has joined #openstack-swift00:37
*** annegent_ has quit IRC00:38
*** lcurtis has quit IRC00:44
*** rmcall has quit IRC00:51
*** annegent_ has joined #openstack-swift00:52
*** annegent_ has quit IRC00:52
*** omame has quit IRC00:54
*** omame has joined #openstack-swift00:54
*** lcurtis has joined #openstack-swift00:57
*** nellysmitt has joined #openstack-swift00:58
*** oomichi has joined #openstack-swift00:58
*** nellysmitt has quit IRC01:02
*** chlong has joined #openstack-swift01:05
pelusenotmyname, so FYI my attempts at messing with that HUP patch are stalled right now as I'm havving issues getting my kernel up to 3.9... will work on it some more tomorrow.  Its happy hour at my house right now!01:05
*** jrichli has joined #openstack-swift01:10
*** david-lyle is now known as david-lyle_afk01:18
*** jamielennox|away is now known as jamielennox01:19
*** chlong has quit IRC01:22
*** annegent_ has joined #openstack-swift01:23
*** dmsimard_away is now known as dmsimard01:34
*** annegent_ has quit IRC01:35
notmynamepeluse: thanks for liiking01:45
*** EmilienM is now known as EmilienM|afk01:55
*** yuan has quit IRC01:59
*** sluo_wfh has joined #openstack-swift02:03
*** dmsimard is now known as dmsimard_away02:03
*** kajinamit has joined #openstack-swift02:06
*** atan8 has joined #openstack-swift02:14
*** haomaiwang has joined #openstack-swift02:16
*** bill_az_ has quit IRC02:19
*** ho has quit IRC02:20
*** chlong has joined #openstack-swift02:26
*** tellesnobrega_ has quit IRC02:31
*** ho has joined #openstack-swift02:37
hohello! i'm back from an two days event, Openstack days tokyo.02:39
*** chlong has quit IRC02:40
mattoliverauho: welcome back :)02:41
homattoliverau: thanks!02:42
*** tellesnobrega_ has joined #openstack-swift02:53
*** nellysmitt has joined #openstack-swift02:58
*** tellesnobrega_ has quit IRC02:59
*** nellysmitt has quit IRC03:04
*** tellesnobrega_ has joined #openstack-swift03:12
*** rmcall has joined #openstack-swift03:13
*** rmcall has quit IRC03:14
*** rmcall has joined #openstack-swift03:15
*** rmcall_ has joined #openstack-swift03:19
*** rmcall has quit IRC03:21
*** rmcall_ has quit IRC03:23
*** rmcall has joined #openstack-swift03:25
*** echevemaster has quit IRC03:26
*** kei_yama has joined #openstack-swift03:27
*** rmcall has quit IRC03:29
*** chlong has joined #openstack-swift03:30
*** rmcall has joined #openstack-swift03:30
*** bkopilov has quit IRC03:34
*** chlong has quit IRC03:37
*** achhabra has joined #openstack-swift03:45
*** rmcall has quit IRC03:46
*** rmcall has joined #openstack-swift03:47
*** rmcall_ has joined #openstack-swift03:56
*** rmcall has quit IRC03:57
*** rmcall_ is now known as rmcall03:57
*** rmcall has quit IRC04:00
*** rmcall has joined #openstack-swift04:03
*** rmcall has quit IRC04:08
*** achhabra has quit IRC04:16
*** jrichli has quit IRC04:24
*** chlong has joined #openstack-swift04:35
*** miqui has joined #openstack-swift04:53
*** chlong has quit IRC04:54
*** nellysmitt has joined #openstack-swift04:59
*** bkopilov has joined #openstack-swift05:01
*** haomaiwang has quit IRC05:02
*** chlong has joined #openstack-swift05:03
*** atan8 has quit IRC05:03
*** nellysmitt has quit IRC05:04
*** silor has joined #openstack-swift05:09
*** silor has quit IRC05:16
*** nshaikh has joined #openstack-swift05:19
*** madhuri has joined #openstack-swift05:30
*** lcurtis has quit IRC05:33
*** abhirc has quit IRC05:40
openstackgerritHisashi Osanai proposed openstack/swift: Enable Object Replicator's failure count in recon  https://review.openstack.org/13834205:42
*** tellesnobrega_ has quit IRC05:58
*** yuan has joined #openstack-swift05:59
*** rmcall has joined #openstack-swift06:06
*** zaitcev has quit IRC06:17
*** rmcall has quit IRC06:26
*** madhuri has quit IRC06:48
*** nellysmitt has joined #openstack-swift07:00
*** nellysmitt has quit IRC07:05
*** chlong has quit IRC07:39
*** kajinamit has quit IRC07:40
*** nellysmitt has joined #openstack-swift08:17
*** rledisez has joined #openstack-swift08:22
*** acoles_away is now known as acoles08:24
*** silor has joined #openstack-swift08:31
*** ppai has joined #openstack-swift08:51
*** donagh has joined #openstack-swift09:03
*** jordanP has joined #openstack-swift09:05
*** jistr has joined #openstack-swift09:07
*** donagh has left #openstack-swift09:10
*** donagh_ has joined #openstack-swift09:10
*** donagh_ has left #openstack-swift09:10
*** donagh has joined #openstack-swift09:19
openstackgerritMadhuri Kumari proposed openstack/swift: Let GET/HEAD on object fail in deleted account.  https://review.openstack.org/14514109:28
openstackgerritMadhuri Kumari proposed openstack/swift: Let GET/HEAD on object fail in deleted account.  https://review.openstack.org/14514109:37
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Add tests for uploads deleting DLO segments  https://review.openstack.org/15317710:06
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Add tests for uploads deleting DLO segments  https://review.openstack.org/15317710:13
*** dmorita has quit IRC10:14
*** cinderella has joined #openstack-swift10:20
cinderellagood morning to everyone10:20
*** anticw_ has quit IRC10:24
*** anticw has joined #openstack-swift10:25
*** tellesnobrega_ has joined #openstack-swift10:28
*** geaaru has joined #openstack-swift10:29
hocinderella: morning!10:36
hoping acoles10:37
cinderellahi ho  can you confirm that juju wants swift as a prerequisite?10:37
acolesho: ping10:42
*** tellesnobrega_ has quit IRC10:43
hociderella: sorry, I'm not familier with juju. but I don't think juju needs to have swift as a prerequisite.10:43
*** tellesnobrega_ has joined #openstack-swift10:45
cinderellaho: any suggestion in adding swift to an openstack installation (all in one) ?10:47
*** silor has quit IRC10:49
*** chlong has joined #openstack-swift10:50
hocinderella: Do you want to install all compo in Openstack at one time? if so , how about packstack?10:52
cinderellaho: I installed all the components one-after-one: glance, cinder, nova, neutron, etc.10:52
cinderellanow I need swift to do some tests with juju, and was finding the best way to do this10:53
hociderella: https://micknelson.wordpress.com/2014/01/09/deploying-swift-with-juju-for-development/ like this?10:54
*** ppai has quit IRC11:02
openstackgerritMerged openstack/swift: Add `swift-scality-backend` to associated projects  https://review.openstack.org/15296011:03
openstackgerritHisashi Osanai proposed openstack/swift: Enable Role-based access control using oslo.policy in Swift  https://review.openstack.org/14993011:03
cinderellaho: not exactly. When I try to run juju quickstart, it tells me that needs swift deployed on the openstack11:04
*** aix has joined #openstack-swift11:04
hoacoles: thanks for the review. the patch above has two problem. one is a problem with oslo.conf. (after this patch it is necesarry to support both conf style: a dictionary and oslo.config). another one is I missed to upload json file.11:07
hoacoles: sorry, i uploaded a dictionary style string in the default-policy.json-sample. I failed to convert it.11:08
*** tellesnobrega_ has quit IRC11:10
hoacoles: sorry for this.11:15
*** ppai has joined #openstack-swift11:16
cinderellaI installed swift, but having problems in contacting it...11:16
cinderellado this endpoint look "right" ? -> http://10.0.0.230:8080/v1/AUTH_914cd4d8565e4fb8beee37f46a50aa4f11:16
hociderella: it looks good. you got it from keystone right?11:17
cinderellaexactly, but it seems to be ded11:17
cinderelladead*11:17
cinderellais the 8080 port good?11:18
hocinderella: it's a default port of proxy-server. so it's good11:18
cinderellamaybe I have some port problems on my net11:19
cinderellahow can I diagnose if swift is running?11:19
hociderella: execute "swift-init all status" or ps -ef | grep swift11:20
cinderellaNo container-sync running No account-replicator running No object-updater running object-server running (18731 - /etc/swift/object-server.conf)11:21
acolesho: ok, i just wondered if i had done something stupid :)11:23
acolesho: maybe we can discuss the policy patch some more next week in SFO?11:23
cinderellaI can't figure why the endpoint isn't responding, ho11:23
acolescinderella: swift-init status shoudl show you 'proxy-server running' in the list of services11:25
hoacoles: yes. I'm looking forward to meeting you there. Is it possible to discuss about 137086? i may mis-understand something...11:25
acolesho: i have a few mins then i have to go11:26
hoacoles: no problem. I would like to discuss it at SFO.11:27
acolesho: ok , sure, see you there!11:28
hoacoles: thanks!11:28
hocinderella: do you have the line like this? proxy-server running (2675 - /etc/swift/proxy-server.conf)11:28
cinderellaho - rebooting right now for other stuff, will tell you soon :)11:31
openstackgerritDonagh McCabe proposed openstack/swift: Let GET/HEAD on object fail in deleted account.  https://review.openstack.org/14514111:42
hocinderella: I have to leave office soon. how about the situation?11:57
cinderellaho: I'm dumb and realized I had installed half of the stuff, I'm proceeding in installing the reamining components11:58
hocinderella: good findings. good luck!11:59
cinderellaho: thanks :)12:00
*** ho has quit IRC12:00
*** EmilienM|afk is now known as EmilienM12:02
*** reed has joined #openstack-swift12:06
*** kei_yama has quit IRC12:19
*** cinderella is now known as cinderella_away12:28
*** silor has joined #openstack-swift12:30
*** cinderella_away has quit IRC12:31
*** chlong has quit IRC12:38
*** oomichi has quit IRC12:39
*** oomichi has joined #openstack-swift12:42
*** oomichi has quit IRC12:44
*** silor has quit IRC12:58
*** silor has joined #openstack-swift13:03
*** oomichi has joined #openstack-swift13:04
*** oomichi has quit IRC13:08
*** bill_az_ has joined #openstack-swift13:23
*** abhirc has joined #openstack-swift13:36
*** bkopilov has quit IRC13:37
*** abhirc has quit IRC13:41
*** achhabra has joined #openstack-swift13:47
*** mahatic has joined #openstack-swift13:56
*** abhirc has joined #openstack-swift14:03
*** nshaikh has quit IRC14:14
*** abhirc_ has joined #openstack-swift14:38
*** abhirc has quit IRC14:40
*** swifty has joined #openstack-swift14:42
swiftygood morning to everyone14:42
swiftyI'm having a problem with my swift14:42
swiftyanyone has some free time ho help me?14:42
swiftyI think I'm quite "near" to a solution14:43
swiftyI've all of my services running, but when I try to "swift stat" I get a "401 Unauthorized"14:44
*** ppai has quit IRC14:45
*** jwalcik has joined #openstack-swift14:47
*** achhabra has quit IRC14:55
*** ppai has joined #openstack-swift15:00
*** ppai has quit IRC15:03
*** rmcall has joined #openstack-swift15:06
*** donagh has left #openstack-swift15:12
*** rmcall has quit IRC15:17
*** david-lyle_afk is now known as david-lyle15:23
*** rdaly2 has joined #openstack-swift15:23
swiftyresolved, thanks anyway15:26
openstackgerritMerged openstack/swift: Update auth_token section in documentation  https://review.openstack.org/15248715:30
*** rmcall has joined #openstack-swift15:39
*** rmcall has quit IRC15:44
notmynamegood morning16:03
*** TobiasE has joined #openstack-swift16:04
TobiasEHi, I found two link about the swift api with different content, does anybody know why there are differences inside? http://docs.openstack.org/api/openstack-object-storage/1.0/os-objectstorage-devguide-1.0.pdf and16:08
TobiasEhttp://developer.openstack.org/api-ref-guides/bk-api-ref-objectstorage-v1.pdf16:08
notmynameTobiasE: just from the table of contents, the first one looks more comprehensive16:10
notmynamewhere did you find those? are they linked somewhere?16:10
TobiasEgoogle gave it to me16:10
*** vishy has quit IRC16:11
*** vishy has joined #openstack-swift16:11
TobiasEThe first one has more features described in chapter one.16:12
TobiasEAre these features still supported? Even they are not mentioned in the second document (the newer one)?16:13
notmynameyes!16:14
TobiasEyes means still supported?16:15
TobiasEAnd when still supported, where documented?16:15
notmynameyes, definitely supported features16:18
notmyname(also we're not in the habit of removing things that would break existing clients)16:19
notmynameas to where documented... is that doc not sufficient? it looks like an official openstack doc16:20
notmynamethere is more documentation (the docs generated from the source code) at http://docs.openstack.org/developer/swift/16:20
ahaleeww the detailed doc is dated last year while the one that says "supported" is dated today, looks pretty confusing16:21
notmynameya16:21
notmynameannegentle: hello. I have docs questions. TobiasE linked 2 pdfs above. where do they come from? I haveven't seen them linked from docs.o.o before. but thye look like good docs16:22
*** kallebe has joined #openstack-swift16:23
notmynameI'm guessing since one is dated feb 5 (ie today) it's autogenerated based on patches landing16:25
*** nellysmitt has quit IRC16:27
TobiasEthe newer one from the 5.th of february is a link from the official openstack api reference page16:28
pelusenotmyname, FYI I finally got my 3.9 working and did post some comments on the patch you mentioned yesterday...16:31
notmynamethanks16:31
pelusenp16:31
notmynameTobiasE: where? the only pdf link I see is for the api complete reference16:31
notmynameTobiasE: well, actually before we get too distracted, did you get your initial question answered? both docs are probably fine. looks like they minimally overlap. all features are supported16:32
notmynamepeluse: I just got to your review in my email :-)16:35
*** bkopilov has joined #openstack-swift16:36
notmynamethanks for being a stickler for test coverage16:36
TobiasEwhen you are here http://developer.openstack.org/api-ref-objectstorage-v1.html and press on the API Supported link, you get the newest one16:36
TobiasEThe older one I found when I googled for swift API doc16:37
notmynameTobiasE: ah ok16:37
TobiasESo, I wonder why there thinks in the older document that are not documented in the newer are still valid or NOT SUPPORTED?16:38
openstackgerritMerged openstack/swift: Tests for the base class of storage nodes  https://review.openstack.org/15175516:39
*** lcurtis has joined #openstack-swift16:40
openstackgerritMerged openstack/swift: Remove the X-Newest pre-flight request on X-Timestamp  https://review.openstack.org/10377816:40
notmynameTobiasE: I asked the docs team what the difference is16:49
notmynameTobiasE: but know that all the features listed in each are supported and available16:49
acolespeluse: notmyname : yes, +1 for insisting on tests16:52
*** jwalcik has quit IRC16:54
*** swifty has quit IRC16:54
TobiasEnotmyname: thanks16:54
*** lcurtis has quit IRC16:59
*** lcurtis has joined #openstack-swift17:01
*** abhirc_ has quit IRC17:02
*** jrichli has joined #openstack-swift17:02
*** jwalcik has joined #openstack-swift17:10
*** imkarrer has joined #openstack-swift17:11
imkarrerGood morning!  I am curious about the formpost middleware.  Formpost returns 401 unauthorized error.  I am following the documentation here http://docs.openstack.org/havana/config-reference/content/object-storage-form-post.html.  It is also worth noting that the tempest test is failing.  I am trying to verify the formpost middleware placement in the pipeline.  Does it go before the auth middleware?17:11
notmynameyup. from the sample config: "# Note: Put formpost just before your auth filter(s) in the pipeline"17:12
imkarrernotmyname: Just a sanity check, it is in the correct place.  Does anything come to mind about where else we could be failing?17:14
notmynameimkarrer: generating the signature is generally the trickiest part (ie the HMAC)17:14
*** aix has quit IRC17:14
notmynamewell, the part most easily fat-fingered17:14
*** rledisez has quit IRC17:15
notmynameimkarrer: are you using the `swift-form-signature` CLI tool to generate it?17:15
imkarrertempest should not fat finger it, and I am using the /bin/swift-form-signature script to make my key17:15
notmynamehmmm17:16
notmynameimkarrer: got any more context to share? do you have an example you can pastebin?17:18
*** Nadeem has joined #openstack-swift17:18
*** Nadeem has quit IRC17:19
imkarrernotmyname: one moment17:20
*** rmcall has joined #openstack-swift17:21
mahaticnotmyname, hello. I was looking into the recon middleware and there is a check in __call__ method that says if the url starts with "/recon/" then do a GET. Should I be changing the url for OPTIONS?17:21
notmynamemahatic: no. I don't think you need to mess with the middleware at all. You only need to change the swift-recon utility to make an OPTIONS call instead of the GET to /recon/*17:22
*** mariusleu has quit IRC17:25
mahaticnotmyname, okay, that's what I wanted to know, OPTIONS will be called with a /recon/* ? (I'm unsure on that being a valid url)17:25
notmynamemahatic: no. OPTIONS will be called with *.17:25
*** abhirc has joined #openstack-swift17:26
mahaticnotmyname, hmm, http://127.0.0.1:6000/* -> that will be an OPTIONS call?17:27
notmynamemahatic: yes. but even just / would probably be fine for now17:28
hurricanerix_So who all is interested in a board game night, during the hackathon?17:29
hurricanerix_torgomatic: ^^^17:29
mahaticnotmyname, oh okay. thanks17:29
*** abhirc has quit IRC17:33
notmynamehurricanerix_: definitely bring games. it's likely you'll find people to play17:33
*** jordanP has quit IRC17:33
*** lcurtis has quit IRC17:35
*** lcurtis has joined #openstack-swift17:35
*** abhirc has joined #openstack-swift17:36
*** abhirc has quit IRC17:36
*** rdaly2_ has joined #openstack-swift17:37
*** rdaly2 has quit IRC17:38
*** mariusleu has joined #openstack-swift17:39
*** acoles is now known as acoles_away17:41
*** panbalag has joined #openstack-swift18:01
*** jwalcik has quit IRC18:05
*** geaaru has quit IRC18:08
*** jistr has quit IRC18:09
*** jistr has joined #openstack-swift18:10
*** kallebe has left #openstack-swift18:15
*** abhirc has joined #openstack-swift18:19
*** jistr has quit IRC18:22
*** abhirc has quit IRC18:23
*** rdaly2_ has quit IRC18:26
*** annegent_ has joined #openstack-swift18:26
*** nellysmitt has joined #openstack-swift18:28
*** abhirc has joined #openstack-swift18:32
*** abhirc has quit IRC18:32
*** nellysmitt has quit IRC18:33
imkarrernotmyname:  I figured it out.  In the keystone middleware section I needed the parameter 'delay_auth_decision = true'.  I was able to infer this from the staticweb middleware documentation.  We are not using static middleware but the auth needs to be delayed so that the authkey can verify the form.  Keystone was throwing out the request since there was no auth metadata.  Only the exipry token.18:35
imkarrernotmyname: Thanks for letting me bounce some ideas off you!18:35
notmynameimkarrer: ah! great to know. glad you figured it out18:36
* notmyname doesn't know of any situations where that keystone middleware should ever be false18:36
imkarrernotmyname: It was not specified in our configuration.  Apparently it does not default to true if not specified.18:38
notmynameya18:38
notmynamebut setting it to false will break formpost, staticweb, tempurls, maybe public read/writes (? not sure on that one)18:39
*** fandi has joined #openstack-swift18:40
torgomaticthere's got to be some way to warn about that18:40
torgomaticevery single person who uses keystone for auth tries a tempurl at some point and then wastes hours of their life until they find that setting and turn it on18:41
torgomaticI cannot think of a reason to ever turn that off in a Swift cluster18:41
notmynametorgomatic: initially should we just change the default?18:42
torgomaticnotmyname: "we", Swift, cannot, as it's keystonemiddleware's code18:42
notmynameah, yeah. just found that. it's in authtoken, not keystoneauth18:42
torgomaticmaybe that default makes sense for Nova?18:43
torgomaticyeah, if it were keystoneauth, this would have been fixed years ago18:43
notmynamewell, I'm feeling a little cranky today. let me go ask...18:43
notmynamehmm...our sample configs say the default is "1"18:44
torgomaticthen they lie18:46
torgomaticcfg.BoolOpt('delay_auth_decision', default=False,18:46
notmynameyup. we need to change our sample config. you want to do that or me?18:47
torgomatic^^ from keystonemiddleware.auth_token.py:23918:47
torgomaticnotmyname: can you? my local tree is all kinds of wonky at the moment18:47
notmynamekk18:47
torgomatic(untracked files, otherwise a simple "git stash" would work)18:47
*** jwalcik has joined #openstack-swift18:49
notmynametorgomatic: do you remember if it prevents basic ACL functionality from working. specifically public content?18:50
torgomaticnotmyname: I think it does; no token --> 40118:50
* notmyname is writing comments in the config18:50
notmynameright18:50
torgomaticso public ACLs break, as do other auth systems in the pipeline (tempurl, $proprietary_auth, whatever)18:51
torgomaticprobably other things too, but I can't think of any18:52
notmynameauthenticated access to /info breaks without it18:54
*** btorch_ is now known as btorch18:59
*** Nadeem has joined #openstack-swift19:00
openstackgerritJohn Dickinson proposed openstack/swift: Correct the config default for delay_auth_decision  https://review.openstack.org/15334019:02
notmynametorgomatic: ^^19:02
panbalagnotmyname, hello19:14
notmynamehello19:15
panbalagnotmyname, I'm working on a test plan for openstack-swift (including storage-policies). I also want to automate the test cases. So I thought Tempest would be the right place to put these tests. Based on the discussion with David Kranz, I understand that swift related tests are spread across Tempest and Swift (functional). He advised that you may be able to direct me to the right place. Can you help?19:16
*** lcurtis has quit IRC19:17
*** jwalcik has quit IRC19:17
*** lcurtis has joined #openstack-swift19:17
notmynamepanbalag: my understanding is that most of the tempest tests are moving to the individual projects19:21
notmynamepanbalag: but that aside, what are you trying to test that's not currently tested today?19:21
notmyname(more tests == more better!)19:21
*** silor1 has joined #openstack-swift19:22
panbalagnotmyname, I don't see any storage policy related tests in Tempest. So I'm focusing on that right now19:22
*** silor has quit IRC19:24
notmynamepanbalag: I need to step away for a little bit (pick up my kid from preschool). but you'll definitely be able to get answers from other people in here19:24
panbalagnotmyname, ok.19:24
*** abhirc has joined #openstack-swift19:25
panbalagpeluse, clayg Could you help me here? If I wanted to contribute new test cases and its automation upstream, Where should I do it?19:26
*** nellysmitt has joined #openstack-swift19:26
mahaticnotmyname, this might be silly. I'm implementing OPTIONS in middleware/recon.py (for cli/recon.py to use). Now, am I wrong in doing device.OPTIONS? (I get the devices from hosts that you pointed early)19:34
mahaticnotmyname, oh I just saw your other message (about you being away) nevermind19:35
*** jwalcik has joined #openstack-swift19:38
*** abhirc has quit IRC19:48
openstackgerritJohn Dickinson proposed openstack/swift: Correct the config default for delay_auth_decision  https://review.openstack.org/15334019:52
*** abhirc has joined #openstack-swift20:00
*** zaitcev has joined #openstack-swift20:05
*** ChanServ sets mode: +v zaitcev20:05
notmynamemahatic: no, I don't think you have to update middleware/recon.py20:17
pelusepanbalag, are you looking for ideas for new tests cases or have you written some test cases down and are unclear where/how to best implement them?20:17
notmynamemahatic: I think you need to add support in cli/recon.py:Scout() to make an OPTIONS call20:17
panbalagpeluse,  I already have test cases. So I want to know the where and how.20:18
notmynamepanbalag: what kind of tests are you writing? functional tests? unit tests? other?20:18
peluseheh, yeah I was about to ask.  maybe if you can share the test cases that would help us figure out the best place for them to land20:19
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873620:19
notmynamemy initial response is that all tests need to be in the swift source tree. and we'll be happy to point you in the right direction for that20:20
panbalagnotmyname, peluse, The tests include things like  creating, deprecating storage policies, replicating contents between containers with different storage policies, etc.20:21
pelusepanbalag, so the functional test suite sounds like a great place to start looking and there are some tests there already but I'm sure you can find some gaps worth closing20:22
panbalagnotmyname, I would consider them mostly functional.20:22
notmynamesounds like functional tests. those should be in test/functional20:22
notmynameand yeah. check out what's there, as peluse said, and see where there are gaps20:22
panbalagnotmyname, peluse, ok..let me check ..I suppose they are in https://github.com/openstack/swift/tree/master/test/functional ?20:23
pelusepanbalag, and if you need some help navigating/identifying things there let us know here in the channel.  yes, those are them20:23
claygso you guys went for the remove x-newest pre-flight instead in favor of capturing 409's - i hope that was a good idea... did anyone try it with container-sync besides me?20:24
*** silor1 has quit IRC20:24
pelusepanbalag, and use of SAIO and steps to verify they work for you are at http://docs.openstack.org/developer/swift/development_saio.html20:24
panbalagpeluse, Will the existing swift related tempest tests be moved here in future?20:25
panbalagpeluse, Sure20:25
peluseclayg, I didn't try with container-sync, i focused my last review on changes since my first review.  If it it turns out to be a bad idea well, hell, your name is all over it so I'm good with it20:26
notmynamepanbalag: maybe (to tempest tests moving). mostly it depends on someone willing to take the time to do that. my understanding, though, is that almost all of the functionality in tempest is already tested in swift's functional tests20:26
claygare these L names really the final cut?  Lizard? Love?  i'm not even into Liberty that much - more of an anarchist20:27
notmynameclayg: ya. and there's a big stink about it (in the TC meetings and on the dev mailing list)20:27
claygheh, ok, but there will be no Hood or Grizzly names added in the final ballet - I should pick now before I forget?20:28
peluselove??? OMG20:28
notmynameya, I wish s/Havana/Hood/20:29
claygok, well i'm going to go ahead and vote, I think London would be ok20:29
pelusewe should be able to do a write in.... like Liquor or something :)20:30
notmynameHavana release in portland. london release in vancouver.20:30
claygI could probably get used to Lizard, I used to call the G release Giraffe, I think i'd been calling L "lollipop"20:30
notmynamelemming was the marketing-disallowed L option20:31
claygawww are lemmings from canada?20:31
notmynameprobably end up with the miami release in tokyo20:31
peluseor we could combine the two and call it lizard-licker :)20:31
notmynamesounds like an ubuntu release20:31
panbalagpeluse, ok. I can verify that. In case, there are any gaps between Tempest and Functional, I'll work on addressing the gaps. In case you hear about anyone already working on it, let me know so that I do not duplicate efforts.20:32
notmynamepanbalag: it's all you! thanks!20:32
claygok, i'm done - I think lemming would have been good - marketing could have had fun with that - it's like the vw bug lemon adds20:32
pelusepanbalag, yup, awesome.  if you want to post your test plan somewhere I'm sure you would get some good feedback as well20:32
claygswift - scalable, dependable, boring - follow the crowd20:33
panbalagpeluse, I was going to ask that next...is there any place where I can post it?20:33
panbalagpeluse, do you use any kind of review board ?20:33
peluseanywhere you like then post a link here in the channel20:34
peluseor, I dunno, notmyname what about posting it as a spec or something?20:34
notmynameya, a spec has the distinct advantage of being seen on gerrit20:34
notmynameI think that would be best20:34
peluseyup20:34
pelusepanbalag, do you know what we mean?  the swift-specs repo?20:35
notmynamethis is cool20:36
notmynamethis is cool http://kmike.ru/python-data-structures/20:36
panbalagpeluse, nope. Can you point me how to.20:36
notmynamemattoliverau: ^^ there's some trie data structures there20:36
pelusepanbalag, here's an example. https://review.openstack.org/#/c/142146/20:36
pelusenotmyname, are there directions anywhere for doing a spec?  I can't remember20:36
notmynameya, looking now20:37
notmynamepanbalag: the high-level flow is documented at http://specs.openstack.org/openstack/swift-specs/readme_link.html20:37
notmynamehere's a mirror to the repo https://github.com/openstack/swift-specs20:37
notmynameand you'll have to do submissions and reviews like any other openstack project (git-review is a helpful tool) http://docs.openstack.org/infra/manual/developers.html20:38
mattoliveraunotmyname: cool, I'll take a look and see if any are a better fit then mine :)20:38
panbalagnotmyname, Thanks. I'll check it. I'll message here if any questions.20:39
notmynamepanbalag: great20:40
mattoliverauNone are distributed in any way or items aren't time stamped (for merging) but maybe more efficient (and hackable).. I'll look into this some more :)20:42
*** silor has joined #openstack-swift20:44
*** abhirc has quit IRC20:54
*** annegent_ has quit IRC20:55
*** annegent_ has joined #openstack-swift21:02
torgomaticLemming would have been an apt name21:06
*** zul has quit IRC21:12
zaitcevMeh, now I need to read kernel again. I thought I was free.21:35
*** silor has quit IRC21:41
openstackgerritMerged openstack/swift: Correct the config default for delay_auth_decision  https://review.openstack.org/15334021:43
*** nellysmitt has quit IRC21:54
*** mahatic has quit IRC21:59
*** abhirc has joined #openstack-swift22:00
*** mariusleu has quit IRC22:21
openstackgerritThiago da Silva proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434722:22
*** abhirc has quit IRC22:25
*** abhirc has joined #openstack-swift22:27
*** mariusleu has joined #openstack-swift22:34
*** jwalcik has quit IRC22:49
*** yuanz has joined #openstack-swift22:53
*** annegent_ has quit IRC22:55
*** yuan has quit IRC22:56
*** abhirc has quit IRC23:07
*** zul has joined #openstack-swift23:12
*** abhirc has joined #openstack-swift23:15
*** jrichli has quit IRC23:18
*** echevemaster has joined #openstack-swift23:19
*** chlong has joined #openstack-swift23:23
*** zul has quit IRC23:24
*** abhirc has quit IRC23:24
*** EmilienM is now known as EmilienM|afk23:33
*** annegent_ has joined #openstack-swift23:35
*** zul has joined #openstack-swift23:37
*** zul has quit IRC23:37
*** esmute has quit IRC23:39
*** annegent_ has quit IRC23:41
*** esmute has joined #openstack-swift23:41
*** david-lyle is now known as david-lyle_afk23:41
*** zul has joined #openstack-swift23:47
*** IRTermite has quit IRC23:48
*** nellysmitt has joined #openstack-swift23:55
*** openstack has joined #openstack-swift23:57

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