Monday, 2014-09-01

*** DisneyRicky has quit IRC00:07
*** pandemicsyn2 has quit IRC00:07
*** esmute has quit IRC00:07
*** CybergeekDK has quit IRC00:07
*** shakamunyi has quit IRC00:07
*** pberis has joined #openstack-swift00:07
*** nottrobin_ has joined #openstack-swift00:07
*** zhiyan_ has joined #openstack-swift00:07
*** zacksh has joined #openstack-swift00:07
*** jdag___ has joined #openstack-swift00:07
*** openstack has joined #openstack-swift00:09
*** zhiyan_ is now known as zhiyan00:09
*** jdag___ is now known as jdag__00:10
*** nottrobin_ is now known as nottrobin00:10
*** swat30 has quit IRC00:11
*** pberis1 has quit IRC00:11
*** mitz_ has quit IRC00:11
*** swat30_ is now known as swat3000:11
*** dmorita has joined #openstack-swift00:33
*** shakamunyi has joined #openstack-swift00:54
*** early has quit IRC00:57
*** echevemaster has joined #openstack-swift00:58
*** echevemaster has joined #openstack-swift00:58
*** shakamunyi has quit IRC00:59
*** early has joined #openstack-swift01:02
*** addnull has joined #openstack-swift01:04
*** early has quit IRC01:05
*** early has joined #openstack-swift01:07
*** tsg has joined #openstack-swift01:11
*** early has quit IRC01:17
*** early has joined #openstack-swift01:21
*** tsg has quit IRC01:36
*** nosnos has joined #openstack-swift01:42
*** kota_ has joined #openstack-swift01:49
*** shakamunyi has joined #openstack-swift01:55
developerstill don't see any new updates in proxy.log01:58
*** shakamunyi has quit IRC01:59
*** addnull has quit IRC02:12
*** addnull has joined #openstack-swift02:13
*** addnull has quit IRC02:17
*** addnull has joined #openstack-swift02:18
*** sungju has quit IRC02:36
developer<peluse> Here is the error response I get back when I try to do the HEAD request02:53
developer+peluse: https://gist.github.com/anonymous/4ff3fda4c028aac1eb4802:54
*** shakamunyi has joined #openstack-swift02:56
developer+peluse: Also left some other updates while you were away.02:59
developer(scroll above)02:59
developer(to see)02:59
*** shakamunyi has quit IRC03:00
*** addnull has quit IRC03:06
*** addnull has joined #openstack-swift03:06
*** addnull has quit IRC03:10
*** addnull has joined #openstack-swift03:21
*** addnull has quit IRC03:24
*** addnull has joined #openstack-swift03:24
*** tsg has joined #openstack-swift03:50
*** shakamunyi has joined #openstack-swift03:57
*** shakamunyi has quit IRC04:01
*** addnull has quit IRC04:05
*** addnull has joined #openstack-swift04:05
*** fifieldt_ has quit IRC04:08
*** addnull has quit IRC04:10
*** tumf has joined #openstack-swift04:13
*** ppai has joined #openstack-swift04:15
*** chandankumar has joined #openstack-swift04:32
*** chandankumar has quit IRC04:53
*** shakamunyi has joined #openstack-swift04:58
*** tumf has quit IRC04:59
*** tumf has joined #openstack-swift05:00
*** chandankumar has joined #openstack-swift05:01
*** shakamunyi has quit IRC05:02
*** addnull has joined #openstack-swift05:03
*** tumf_ has joined #openstack-swift05:04
*** tumf_ has quit IRC05:05
*** tumf_ has joined #openstack-swift05:06
*** tumf has quit IRC05:07
*** chandankumar has quit IRC05:09
*** kopparam has joined #openstack-swift05:13
*** chandankumar has joined #openstack-swift05:14
*** tumf_ has quit IRC05:38
*** chandankumar has quit IRC05:40
*** tumf has joined #openstack-swift05:44
*** shakamunyi has joined #openstack-swift05:58
*** tumf has quit IRC06:01
*** shakamunyi has quit IRC06:03
*** k4n0 has joined #openstack-swift06:04
*** sungju has joined #openstack-swift06:05
*** echevemaster has quit IRC06:12
*** Anju has joined #openstack-swift06:16
*** joeljwright has joined #openstack-swift06:17
*** chandankumar has joined #openstack-swift06:19
openstackgerritYuan Zhou proposed a change to openstack/swift: Use mkstemp() instead of deprecated mktemp()  https://review.openstack.org/11808406:23
*** slo_ has quit IRC06:26
*** haomai___ has quit IRC06:35
*** chandankumar has quit IRC06:38
*** chandankumar has joined #openstack-swift06:43
*** haomaiwang has joined #openstack-swift06:54
*** chandankumar has quit IRC06:54
*** chandankumar has joined #openstack-swift06:54
*** Trixboxer has joined #openstack-swift06:55
*** shakamunyi has joined #openstack-swift06:59
*** kopparam has quit IRC07:04
*** shakamunyi has quit IRC07:04
*** kopparam has joined #openstack-swift07:04
*** kopparam has quit IRC07:09
*** sungju has quit IRC07:27
*** ksuni has joined #openstack-swift07:27
*** tab___ has joined #openstack-swift07:27
*** ksuni has quit IRC07:28
*** chandankumar has quit IRC07:28
*** kopparam has joined #openstack-swift07:33
*** chandankumar has joined #openstack-swift07:41
*** nshaikh has joined #openstack-swift07:52
*** shakamunyi has joined #openstack-swift08:00
*** geaaru has joined #openstack-swift08:01
*** tsg has quit IRC08:03
*** kota_ has quit IRC08:04
*** shakamunyi has quit IRC08:05
*** sungju has joined #openstack-swift08:18
*** Dafna has joined #openstack-swift08:28
*** sungju has quit IRC08:29
*** kopparam has quit IRC08:30
*** kopparam has joined #openstack-swift08:31
*** Midnightmyth has joined #openstack-swift08:34
*** nshaikh has quit IRC08:47
*** k4n0 has quit IRC08:47
*** aix has joined #openstack-swift08:56
*** shakamunyi has joined #openstack-swift09:01
*** chandankumar has quit IRC09:02
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Merge "Allow empty reseller prefixes in domain_remap"  https://review.openstack.org/11810809:04
*** k4n0 has joined #openstack-swift09:05
*** shakamunyi has quit IRC09:05
*** mkollaro has joined #openstack-swift09:20
*** k4n0 has quit IRC10:00
*** shakamunyi has joined #openstack-swift10:02
*** shakamunyi has quit IRC10:07
*** kopparam_ has joined #openstack-swift10:11
*** kopparam has quit IRC10:13
*** k4n0 has joined #openstack-swift10:13
*** kopparam_ has quit IRC10:17
*** kopparam has joined #openstack-swift10:18
*** kopparam has quit IRC10:23
ctennisdeveloper: the line "Invalid path: /node_for_swift/sdf1/807/AUTH_system" is interesting..do you have the drive mounted at /node_for_swift/sdf1 ?10:33
ctennisthe corresponding log file showing what the swift processes were doing would be more interesting I think..what error they're reporting behind the scenes that causes you to get a 400 back10:33
*** developer has quit IRC10:37
*** dmorita has quit IRC10:57
*** shakamunyi has joined #openstack-swift11:02
*** shakamunyi has quit IRC11:07
*** kopparam has joined #openstack-swift11:14
*** addnull has quit IRC11:23
*** chandankumar has joined #openstack-swift11:26
*** kopparam has quit IRC11:28
*** kopparam has joined #openstack-swift11:29
*** zul has joined #openstack-swift11:36
*** chandankumar has quit IRC11:39
*** addnull has joined #openstack-swift11:45
*** addnull has quit IRC11:55
*** shakamunyi has joined #openstack-swift12:03
*** marcusvrn has joined #openstack-swift12:06
*** shakamunyi has quit IRC12:08
*** Midnightmyth has quit IRC12:10
*** kopparam has quit IRC12:22
*** kopparam has joined #openstack-swift12:23
*** kopparam has quit IRC12:27
*** nosnos has quit IRC12:32
*** nosnos has joined #openstack-swift12:33
*** ppai has quit IRC12:36
*** nosnos has quit IRC12:37
*** addnull has joined #openstack-swift12:38
*** addnull has quit IRC12:46
*** ppai has joined #openstack-swift12:50
*** bkopilov has joined #openstack-swift13:04
*** shakamunyi has joined #openstack-swift13:04
*** shakamunyi has quit IRC13:09
pelusedeveloper:  I'll be on and off today throughout the day, let me know when you're around.  yeah, the invalid path thing looks like it could be what's behind your error13:17
*** silverpuff has quit IRC13:39
pelusedeveloper:  and also I didn't see the path /node_for_swift specified anyone in your .conf files either.   if you deviated from the directions in the link you sent in step 2 of "Configure the Storage nodes" then you could have some problems because the default path for devices is /srv/node if not specified in the .conf files and it looks like you did somthing else13:40
pelusedeveloer:  I would suggest instead of trying to go configure things for the path you chose, just go follow step2 exactly and then restart your services and try again13:41
pelusedeveloper:  note that the devices path is also specified in  /etc/rsyncd.conf:13:42
*** gindating has joined #openstack-swift13:44
*** bvandenh has joined #openstack-swift13:47
ctennispeluse: he's gone from IRC unfortunately13:48
*** openstack has joined #openstack-swift13:57
*** openstackstatus has joined #openstack-swift13:58
*** ChanServ sets mode: +v openstackstatus13:58
*** Anju has quit IRC13:59
pelusectennis:  yeah, I figure maybe he's using a bouner or something and will see it later :)14:00
*** zaitcev has joined #openstack-swift14:03
*** ChanServ sets mode: +v zaitcev14:03
*** shakamunyi has joined #openstack-swift14:05
*** shakamunyi has quit IRC14:09
*** Alex_Gaynor_ is now known as Alex_Gaynor14:18
*** Alex_Gaynor has quit IRC14:18
*** Alex_Gaynor has joined #openstack-swift14:18
*** aix has quit IRC14:36
*** k4n0 has quit IRC14:37
*** HenryG has joined #openstack-swift14:57
*** aix has joined #openstack-swift15:01
*** shakamunyi has joined #openstack-swift15:06
*** shakamunyi has quit IRC15:10
*** ppai has quit IRC15:13
*** ChanServ changes topic to "Swift 2.1.0 https://launchpad.net/swift/+milestone/2.1.0 | Swift Review Dashboard: http://bit.ly/1iVBigF | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews"15:17
*** bvandenh has quit IRC15:29
*** bkopilov has quit IRC15:47
openstackgerritanju Tiwari proposed a change to openstack/swift: Added a check for limit value  https://review.openstack.org/11818615:57
*** shakamunyi has joined #openstack-swift16:06
*** shakamunyi has quit IRC16:11
*** aix has quit IRC16:23
goodespeluse: good morning16:27
*** aix has joined #openstack-swift16:36
*** mkollaro has quit IRC16:41
*** Anju has joined #openstack-swift16:56
Anjuhi notmyname16:57
AnjuI see your comments ..I did not get the metacoment part16:58
*** shakamunyi has joined #openstack-swift17:07
notmynameAnju: ah, just saying that I'm not sure what the end-user/client impact will be17:07
notmynameAnju: that is, the current behavior is to ignore malformed limit queries. your new behavior is to return an error17:07
notmynameAnju: I'd love your comments on that, but I also want to get the feedback of other core reviewers too17:08
Anjunotmyname: at least postive17:08
Anju:)17:08
notmynameAnju: but note that my comment on that in no way reflects the code. just curious about any migration path17:08
notmynameAnju: one thing you could do that would be helpful is to look a swiftclient and see how or if it handles that case.17:09
notmynameand leave a comment about it in your patch17:09
notmynameAnju: what does python-swiftclient do if a non-int is given for the limit parameter17:09
Anjunotmyname: actually I got this error because I want to add a limit options there also17:10
notmyname:-)17:10
AnjuI was getting this error17:10
Anjuso I checked swift code17:10
Anjuthen caught thsi17:10
Anjuthis17:10
Anjufinding a bug in swift is so hard17:11
Anju:)17:11
notmynameheh. don't worry. they are there :-)17:11
Anju:)17:11
notmyname...all my code hasn't been rewritten out of swift yet ;-)17:12
Anju:) :)17:12
*** shakamunyi has quit IRC17:12
AnjuI will change the code part .. If..else..If you want17:12
Anjubut I hope cores accept this17:13
Anjufingures crossed17:13
ahalequick question on proposing change to swift .. does it have to have a bug/bp ? or can i just drop a patch ?17:16
notmynamesure. actually, I like it, in general. I just want to make sure that we don't inadvertently break the ecosystem17:16
notmynameahale: just drop a patch :-)17:16
ahalecool :)17:17
notmynameahale: bugs and blueprints are nice to have. and I'll probably have to go create it after the fact if you don't. but don't consider that a barrier to entry (IMO)17:17
ahalethe contributing to openstack and gerrit workflow pages are a long hard read..17:17
notmynameahale: normally, I'll only ask for bugs/blueprints if it's something more significant, especially something that needs to be tracked external to swift17:17
ahaleahh nah its just a saio config change17:18
ahalenothing significant :)17:18
notmynameahale: oh. well then certainly don't fight with LP to get that in :-)17:18
AnjuAgree notmyname17:18
notmynameAnju: if you would have had the test I would have left it as +0 until more people could weigh in (note that it's a US holiday today, so it will be at least tomorrow before people are likely to look at it)17:19
ahalei figured it makes sense to have bind_ip set, since the ring-builder and curl lines use it anyway so no impact on tests or docs, and it saves putting a public + default password box up if you're doing it somewhere with public ips17:20
ahale*set to localhost17:20
notmynamecool17:20
notmynameahale: one thing we want to do is make the bind_port required (no default, must be set in configs) so that we can later change the default port in configs17:21
notmynameahale: turns out that some people get really upset* that swift's default ports conflict with x.org17:22
ahalehehe, finally get off the port 6000 :)17:22
notmyname*well, annoyed17:22
notmynameahale: I'm assuming you have all the ports explicitly set anyway already :-)17:22
ahalethey're all set in the saio at least, for the crazy ports17:23
Anjuyes notmyname ..I will..No body will giev a single eye with your -1 :-)17:25
notmynameahale: don't forget the sample saio configs in doc/saio if you are changing something there17:25
ahaleyeah thats the ones I am changing! are there others that should be more obvious notmyname  ? :)17:26
*** mahatic has joined #openstack-swift17:26
notmynameahale: no IIRC all the docs directly import those now. maybe there was something in the surrounding text17:26
ahaleahh17:26
ahaleyeah no the docs do import them so its just that - dont think it even needs a mention in the text17:27
*** acoles is now known as acoles_away17:28
Anjunotmyname: sorry I am asking you more,,are you not happy with condition ? you said to change the if ..else part also ?17:33
notmynameAnju: oh. that's less important. I prefer it with the else, but I should have added a "nit" tag to those comments.17:34
notmynameAnju: so yeah I think it would be nice, and I think it's clearer with the else. but you're the one writing it :-)17:35
*** mahatic has quit IRC17:36
notmynamehmm..oops. teh proxy sample config says the default is port 80. the default is actually 808017:36
AnjuI was happy with that...but will see :P17:37
ahaleugh gerrit docs are very confusing - they suggest Change-Id is meant to be added by a post hook, and if its missing directs you to a part of docs that has no mention of it >.<17:42
notmynameahale: did you install git-review?17:42
ahaleyeah, it added a remote fine as well17:42
notmynameahale: yeah, when you do the initial `git review -s` it sets up the post commit hook to add the change-id to the commit message17:43
ahalelemme try again from scratch17:43
*** mahatic has joined #openstack-swift17:49
*** geaaru has quit IRC17:59
*** tsg has joined #openstack-swift18:02
ahaleoh i am an idiot18:03
openstackgerritAndrew Hale proposed a change to openstack/swift: Only bind SAIO daemons to localhost  https://review.openstack.org/11819718:04
ahaleew, can you easily change a commit msg ? like, adding linebreaks18:05
Anjuagain checkout the samwe..and then git commit -a --amend18:07
*** shakamunyi has joined #openstack-swift18:08
notmyname-a is only needed of you're adding new files to the commit18:09
ahaleso just a git commit --amend ?18:10
notmynameahale: yes18:10
notmynameahale: or I can do it in gerrit18:10
notmynameahale: whichever you prefer18:10
ahaleoh if you dont mind that would be awesome18:10
notmynamekk18:10
openstackgerritJohn Dickinson proposed a change to openstack/swift: Only bind SAIO daemons to localhost  https://review.openstack.org/11819718:11
ahalethis kind of git use is terrying to ops like me18:11
ahalethanks!18:11
notmyname:-)18:11
notmynamethere's a little "edit the commit message in the gerrit UI. that's the first time I've used it18:11
ahaleoh nice :)18:12
*** shakamunyi has quit IRC18:13
*** Anju has quit IRC18:14
*** mahatic_ has joined #openstack-swift18:19
*** mahatic has quit IRC18:20
ahalenotmyname: looks like the swiftstack ci thingy is having trouble with pypi18:20
notmynameahale: ya, I just asked charz about it18:20
ahale:)18:21
notmynamebut it's really late/early for him right now :-)18:21
notmyname(taipei)18:22
openstackgerritJohn Dickinson proposed a change to openstack/swift: make the bind_port config setting required  https://review.openstack.org/11820018:25
notmynamethere's a first attempt at making the bind_port required18:25
*** aix has quit IRC18:36
pelusenotmyname: just installed a fresh SAIO on trusty and seeing 5 errors in unittests complaining about 'long int too large to congert to int' and wondering if you've heard of this...18:37
ahalefwiw, I did a fresh one on precise yesterday and it was fine18:39
pelusethanks, no issues w/precise.  wondering if there's thing here with python 2.7.3 (precise) vs 2.7.6 (what you get w/trusty) or if I just shouldn't be working on a holiday18:40
notmynamepeluse: is this one of your old 16 bit machines? ;-)18:40
notmynamepeluse: IOW, no idea :-)18:41
pelusenotmyname, heh.  OK, I'll maybe look at it closer later after a beer or something :)18:41
notmynamepeluse: but the biggest config values I can think of would be the constraints set in swift.conf. check that you didn't add another digit to max_object_size or something18:41
notmynamepeluse: maybe we cast that to int "because sys.maxint is enough for anybody"18:42
notmyname(maxint is 9223372036854775807 on my saio)18:43
notmynameboth 64bit18:43
notmynameboth == mac and saio18:44
pelusewow man, for my trusty is 2147483647 and for my precise its same as yours18:44
peluseWTF happened there!18:44
notmynameif you've got a 32 bit vm, it will be 4294967295 (5gb == 5368709120)18:45
notmynamesinged ints on 32 bit18:45
notmyname2**31-118:45
peluseah hell, I grabbed the wrong ISO.  thanks!18:46
peluse&*(&(*!HKJH&^!!!!18:46
notmynamethat's an interesting failure mode, though. we explicity cast to int() in many places with the general expectation that header values (eg content-length) and constraints will be representable there18:47
notmynamenot exactly 10-year future proof, I guess18:47
peluseyup, the error was not obvious, I took a quick look at the code.  Will reisntall my new insteall, argh18:48
* notmyname would love a network connection that can transfer more than 2**64 bits in one stream18:48
Alex_Gaynorint() will happilly return a long if you send a value too large18:48
Alex_Gaynor>>>> int("3413432480932497823147890214214213")18:48
Alex_Gaynor3413432480932497823147890214214213L18:48
notmynameAlex_Gaynor: hmm...so I wonder where that is getting thrown in swift18:49
pelusemaster: File "/home/peluse/swift/test/unit/__init__.py", line 755,18:49
pelusebut I've already blown it away so don't ask for more details :)18:50
*** Jouva has joined #openstack-swift19:08
JouvaSo I'm fairly new to OpenStack but know just a few basics about it. Have not deployed anything yet. Not going for a huge deployment (like 1-3 TB hosted in 2 or 3 locations). For such a small deployment is it worth it? If so, what sort of hardware could one get away with for CPU/Mem for the storage and proxy machines? We don't expect heavy amounts of traffic. Nothing constant. But we19:11
Jouvawant redundancy (physical storage and network wise) and the ability to grow our storage19:11
zaitcevI pass on suggesting on this. I don't deal with geographic distribution among "2 or 3 locations".19:13
openstackgerritanju Tiwari proposed a change to openstack/swift: Added a check for limit value  https://review.openstack.org/11818619:15
notmynameJouva: general guidelines are about 1GB of ram per spindle and about 1 core for every 2-3 spindles. it varies greatly depending on your use case though19:18
Jouvanotmyname: Is that for the storage itself?19:19
notmynameJouva: 1-3TB is generally really small for swift clusters (normally you'd start with a machine with 12-24 data drives. with 3x replication, that gives you more than your looking for)19:19
JouvaGot ya19:19
notmynameJouva: yeah. large deployments could specialize in as many as 3 different SKUs, but small deployments can easily run everything on one box19:20
notmynameor one SKU. eg have 2 boxes for some HA, but they each run all the swift processes19:20
notmynameJouva: so if you've got one box with 12 drives, a quad core cpu, 16gb ram, and a 10g nic, you'll have a nice all-in-one box19:22
notmynameJouva: and with 12 4t drives, that will give you a total of 4tb usable storage with 3x replication19:23
JouvaThought that'd give me more, but ok!19:24
JouvaI know there's redundancy involved and all that, but I thought 3x replication would cut the storage down by 1/3 not by 1/12th19:25
notmynameah, my math is bad19:25
Jouva12 1TBs would give me 4TB, right?19:25
notmynameyes19:25
JouvaOk19:25
notmynamesorry. I'll blame that on the holiday...yeah..that's it...the holiday19:26
zaitcevIN AMERICA19:26
JouvaThat excuse is Good Enough For Me(tm)19:26
zaitcevSo, what about the 3 locations? Just deploy 3 clusters and have the app select, like Amazon S3 regions?19:27
zaitcevWell, 3 boxes19:27
zaitcevat this size19:27
notmynameJouva: for base 10 (marketing) to base 2 (formatted) space, allowing for 80% full, it's pretty close to taking the total TB on the box and dividing by 4. eg 100 6TB hard drives is about 150TB usable)19:27
JouvaRight right19:27
JouvaI know it's not exact, but the first number you said wasn't right.19:28
JouvaBut with 12 1TBs it's 4TB-ish19:28
notmynamezaitcev: depends on the use case19:28
notmynamefor multiple regions, you can either allow the client to choose, or you can let swift manage the replication between them and expose it as a single endpoint19:28
notmynamebasically, do you need locality of access (lower latency) or do you need some DR story in case one region goes offline19:29
ahaleI always think looking at the max available storage is dangerous, since getting a full swift cluster is such a painful thing to deal with you want to knock 20% off when reporting to people who pay for it19:30
notmynameahale: yes :-)19:31
notmynameahale: something I've learned, though, is that a lot of the traditional storage options that swift replaces tend to start really hurting after 50-60% full (anecdotal)19:32
ahaleoh really19:32
notmynameyeah. not to mention that some need nightly "defrags" that mean you don't want end-user requests to it19:34
ahaleI've seen container dbs that could have benefitted from a scheduled vacuum :)19:35
notmyname:-)19:36
ahaleoh, are there any plans for container/account storage policies ?19:36
ahalesometimes it could be cool to split out some containers onto different hardware, .expiring for example19:37
notmynamenot right now19:37
ahaleare blueprints the way to suggest features ? (not that one, another"it would be cool if"  I just remembered)19:39
ahalethey seem kinda formal19:39
ahalei guess a bug report that you can't do somrthing could work19:40
notmynameahale: the specs documents are supposed to be a better way to do that. clone the repo, add/edit a text file, and submit through gerrit19:49
notmynameI've got a list of small niceties that I'd like to track somewhere.19:49
notmynameI don't know if wiki page, catch-all specs document, or blueprints is the best way19:49
ahaleI'm not really sure19:50
notmynameI'll probably either do a wiki page or blueprints. or a wiki with blueprints linked...19:51
notmynameright now it's all in an evernote doc :-)19:51
ahalenot being a dev, something that doesn't carry a feeling of "heres work I think someone should do" would be nice - or a way to gain concensus something is worth adding before adding it19:51
ahaleupdaing official docs straight out feels a little presumptous :)19:51
notmyname:-)19:51
notmynameI don't think the specs should necessarily be seen that way. in fact, they were first proposed at an ops summit to figure out how ops can have better feedback into the dev community19:53
ahalemaybe it would feel different in a less established project19:54
jokke_notmyname: gratz for another successful release ;)19:56
ahalealso I'm probably in a funny position, anything related to my business would go through my devs normally, things from my daydreaming about features isn't really relevent for that route19:57
*** ChanServ changes topic to "Swift 2.1.0 https://launchpad.net/swift/+milestone/2.1.0 | Swift Review Dashboard: http://bit.ly/1iVBigF | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews | Ideas: https://wiki.openstack.org/wiki/Swift/ideas"20:34
notmynameahale: new link in the /topic20:34
notmynameahale: https://wiki.openstack.org/wiki/Swift/ideas20:34
ahaleaha cool stuff20:34
ahaleoh label mounting in docs is very low hanging fruit20:35
*** swills has quit IRC20:49
*** stenchlarge has joined #openstack-swift21:01
*** joeljwright has quit IRC21:02
*** swills has joined #openstack-swift21:11
*** tdasilva has quit IRC21:16
openstackgerritanju Tiwari proposed a change to openstack/swift: Added a check for limit value  https://review.openstack.org/11818621:28
*** samwebster has quit IRC21:33
*** samwebster has joined #openstack-swift21:34
*** echevemaster has joined #openstack-swift21:45
*** haomaiwang has quit IRC22:11
*** haomaiwa_ has joined #openstack-swift22:30
*** haomaiwa_ has quit IRC23:01
*** haomaiwang has joined #openstack-swift23:02
mattoliverauMorning all23:12
*** HenryG has quit IRC23:13
*** haomaiwang has quit IRC23:22
*** haomaiwa_ has joined #openstack-swift23:25
*** tsg has quit IRC23:26
*** HenryG has joined #openstack-swift23:28
*** fifieldt has joined #openstack-swift23:32
*** haomaiwa_ has quit IRC23:34
*** haomaiwa_ has joined #openstack-swift23:35
*** haomaiwa_ has quit IRC23:56

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