Thursday, 2014-11-13

*** david-lyle_afk is now known as david-lyle00:10
openstackgerritSamuel Merritt proposed openstack/swift-specs: Spec for at-rest encryption.  https://review.openstack.org/12322000:11
*** exploreshaifali has quit IRC00:12
*** Nadeem has quit IRC00:13
*** Viswanath has joined #openstack-swift00:17
*** Viswanath has quit IRC00:20
*** dmorita has joined #openstack-swift00:25
*** tellesnobrega_ has joined #openstack-swift00:28
*** tellesnobrega_ has quit IRC00:39
*** dmsimard_away is now known as dmsimard00:40
*** tellesnobrega_ has joined #openstack-swift00:40
*** tellesnobrega_ has quit IRC00:48
claygsome core merge this for christs sake - https://review.openstack.org/#/c/129572/00:51
*** sungju has joined #openstack-swift01:03
*** dmsimard is now known as dmsimard_away01:20
*** RockKuo_Office has joined #openstack-swift01:21
*** gyee has quit IRC01:25
*** addnull has joined #openstack-swift01:25
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873601:30
*** shri has quit IRC01:37
*** haomaiwang has joined #openstack-swift01:45
claygtorgomatic: thanks01:46
*** haomai___ has joined #openstack-swift01:51
*** haomaiwang has quit IRC01:51
*** tellesnobrega_ has joined #openstack-swift01:53
*** nosnos has joined #openstack-swift02:06
*** tellesnobrega_ has quit IRC02:07
*** david-lyle is now known as david-lyle_afk02:08
*** tellesnobrega_ has joined #openstack-swift02:17
*** tellesnobrega_ has quit IRC02:25
*** kyles_ne has joined #openstack-swift02:41
*** kyles_ne has quit IRC02:46
*** tellesnobrega_ has joined #openstack-swift02:59
*** addnull has quit IRC03:11
openstackgerritMerged openstack/python-swiftclient: Fix KeyError raised from client Connection  https://review.openstack.org/12892903:12
*** addnull has joined #openstack-swift03:13
*** nosnos has quit IRC03:25
*** mahatic has quit IRC03:26
openstackgerritMerged openstack/python-swiftclient: Make swift post output an error message when failing  https://review.openstack.org/12957203:30
claygelambert: ping, trying to figure out how to read ec headers from a fragment - i really want to know it's index03:40
claygwhere "really" is only slightly greater than there's a pre-existing call that'll let me do it with pyeclib ;)03:41
*** jyoti-ranjan has joined #openstack-swift03:48
*** nosnos has joined #openstack-swift03:57
elambertclayg:  well in theory you shouldn't have to care .. but libec does expose that … let me look at the current pyeclib04:03
claygwell, turns out I have to care in so much as I need to store only one copy of each fragment and I need to know what fragments I have04:04
*** addnull has quit IRC04:05
elambertfair'nuff04:05
claygheh04:05
claygthanks for being up!04:05
elambertyeah .. np04:05
*** jdaggett has quit IRC04:05
*** jdaggett_ has joined #openstack-swift04:06
elambertit looks like ECPyECLibDriver.get_metadata should do the tick04:08
clayg:returns: an opaque buffer04:10
claygindeed I do not know what those bytes mean04:10
claygis there a struct def somewhere in a .h file I could crib a struct unpack from?04:11
elambertthere is in libec04:11
elamberttypedef struct __attribute__((__packed__))04:11
elambertfragment_metadata04:11
elambert{04:11
elambert    uint32_t    idx;                /* 4 */04:11
elambert    uint32_t    size;               /* 4 */04:11
elambert    uint64_t    orig_data_size;     /* 8 */04:11
elambert    uint8_t     chksum_type;        /* 1 */04:11
elambert    uint32_t    chksum[LIBERASURECODE_MAX_CHECKSUM_LEN]; /* 32 */04:11
elambert    uint8_t     chksum_mismatch;    /* 1 */04:11
elambert    uint8_t     backend_id;         /* 1 */04:11
elambert    uint32_t    backend_version;    /* 4 */04:11
elambert} fragment_metadata_t;04:11
*** jd__` has joined #openstack-swift04:11
elambertwhoops .. should have gisted that04:12
*** tristanC_ has joined #openstack-swift04:12
*** RockKuo_ has joined #openstack-swift04:12
*** mordred_ has joined #openstack-swift04:12
*** Tyger_ has joined #openstack-swift04:12
*** zaitcev has quit IRC04:12
*** mhu has quit IRC04:12
*** EmilienM has quit IRC04:12
*** vishy has quit IRC04:12
*** ahale has quit IRC04:12
*** ondergetekende has quit IRC04:12
*** acoles_away has quit IRC04:12
*** sileht has quit IRC04:12
*** RockKuo_Office has quit IRC04:12
*** mitz_ has quit IRC04:12
*** nottrobin has quit IRC04:12
*** mordred has quit IRC04:12
*** IRTermite has quit IRC04:12
*** tristanC has quit IRC04:12
*** Tyger has quit IRC04:12
*** jd__ has quit IRC04:12
*** JelleB has quit IRC04:12
*** mitz has quit IRC04:12
*** dvorkbjel has quit IRC04:12
*** jd__` is now known as jd__04:12
*** IRTermite1 has joined #openstack-swift04:12
*** nottrobin_ has joined #openstack-swift04:12
*** nottrobin_ has joined #openstack-swift04:12
*** mordred_ is now known as mordred04:12
*** mhu1 has joined #openstack-swift04:12
*** mitz has joined #openstack-swift04:12
claygor tell me the file in liberasurecode ;)04:12
*** mhu1 is now known as mhu04:12
elamberterasurecode.h04:12
*** JelleB has joined #openstack-swift04:12
elambertidx is the field you care about04:13
elambertgiven your usecase .. we should probably exposes in pyeclib04:13
*** ondergetekende has joined #openstack-swift04:14
*** ahale has joined #openstack-swift04:14
*** EmilienM has joined #openstack-swift04:14
*** dvorkbjel has joined #openstack-swift04:15
claygis this the right repo -> git@bitbucket.org:elambert/liberasurecode.git04:15
*** kyles_ne has joined #openstack-swift04:16
elambertthis is04:16
elamberthttps://bitbucket.org/tsg-/liberasurecode04:16
*** vishy has joined #openstack-swift04:16
claygi think i found yours from a link in the README on pyeclib04:16
elambertyikes04:16
*** kyles_ne has quit IRC04:17
claygk this is great, just what I needed <hugs>04:18
elambertI'm gonna fix that now (the reference that is) we abandoned that repo a while go04:18
elambertsorry for the confusion04:18
*** acoles_away has joined #openstack-swift04:18
*** acoles_away is now known as acoles04:19
*** ChanServ sets mode: +v acoles04:19
*** zaitcev has joined #openstack-swift04:20
*** ChanServ sets mode: +v zaitcev04:20
*** sileht has joined #openstack-swift04:22
claygno worries, still a bit confused on what get_metadata is returning exactly04:26
elamberteach fragment has a metadata header that contains info needed by libec to decode the fragment .. that's what its returning04:27
elambertI can describe each member of the header if you are interested04:29
claygwell, what I have installed is returning 20 bytes - which doesn't seem big enough for that struct04:29
*** kyles_ne has joined #openstack-swift04:29
elambertthat aint right04:29
elambertlet me look closer at what the method is doing04:32
claygi think i just have an old version of libec installed maybe?04:32
elambertcould be .. libec has gone through a lot of churn04:33
elamberthow did you install it?04:34
claygdon't really recall - I think it got built when I installed pyeclib04:34
elamberthmm .. once upoin a time pyeclib built libec from source .. but we are moving away from that04:36
*** rawat_vedams has joined #openstack-swift04:37
elambertto be honest, i've been focusing mainly on the libec side of stuff … so not really sure what's up with pyeclib side .. let me see if tushar is around somewhere04:37
claygwell, anyway - I guess I need to know what version of libec I've got built and how it's building - and I also need to get a feature against pyeclib to expose the unpacked fragment_metadata_t struct rather than just the raw bytes04:39
*** tsg has joined #openstack-swift04:39
elamberttsg!04:39
*** tsg_ has joined #openstack-swift04:39
*** tsg_ has quit IRC04:39
tsgelambert: what's up04:40
claygthat's probably about all I got for the night - just sort of picking at it I've got something in bytes 4-8 that look a lot like the unsigned int representing the index - so dunno why the first 4 bytes of padding are doing - or why the rest are all zeros :\04:40
elambertso clayg is trying to trouble shoot some issues with pyeclib04:40
elambertlong story short .. what's the latest pyeclib that has been "released"04:41
claygmeh, maybe it's no so bad - like I said I need to know what i've got for libec on this box, and I need to make a feature request against pyeclib - that may be it04:41
elambertand how does it pull in libec04:41
claygPyECLib==0.9.8 installed04:41
elambertah .. i think we have 0.9.10 now?04:42
tsgelambert: I haven't pushed 0.9.10 to PyPi yet04:42
claygyeah there's a tag for that in the repo04:42
tsgclayg: can you try to build off of git?04:42
claygtsg: i do get the feeling at some point I'ma wanna suss that04:43
elamberttsg .. did 9.8 pull libec from kevin's repo?04:43
tsgyes -04:43
elambertah04:43
tsg(clayg: what's the feature request btw?)04:43
tsgclayg: we are close to 1.0 so 0.9.10 wasn't pushed04:43
tsgI think I should push that04:44
claygtsg unpack fragment_metadata_t when you call get_metadata instead of just returning the raw bytes04:44
tsgclayg: good call .. that will certainly be useful04:44
claygtrello or issue on bitbucket?04:45
tsgTrello is good04:45
elambertbugzilla :-P04:45
* elambert was tyring to be funny04:45
tsg:)04:45
tsgclayg: I assume you were trying to inspect individual EC fragments in FAs04:46
tsgand it was a bit tricky to make sense of the metadata ..04:47
*** kota_ has joined #openstack-swift04:50
claygyeah, sorta, the patch I was looking at was just not doing the right thing - it didn't know it - but the fragment archives did04:50
claygso is the correct and current repo -> git@bitbucket.org:tsg-/liberasurecode.git04:51
tsgyep04:51
tsgand master on https://tsg-@bitbucket.org/kmgreen2/pyeclib.git04:52
tsgs/tsg-/git/04:52
*** tellesnobrega_ has quit IRC04:52
tsgclayg: I assume you have Jerasure 2.0 installed already - that repo is down at the moment04:57
clayghrm... yeah not sure05:01
claygi was able to build liberasurecode, and then setup.py install pylibec, but my swift doesn't work because it doesn't like the signature on ECDriver05:02
tsgclayg: pyeclib until 0.9.8 would pull it automatically .. Debian guys made us change that05:02
claygoic05:02
claygyeah it's gunna be a pita to package al this05:03
tsgclayg: in touch with Zigo to figure that out05:03
clayglibrary_import_str ?05:05
*** zaitcev has quit IRC05:06
claygoh you done gone and implemented a python plugin system without using package resources entry points didnt' you05:08
*** addnull has joined #openstack-swift05:09
*** bkopilov has joined #openstack-swift05:09
tsgclayg: wasn't the plan - something seems amiss - give me until the morning to sort it out05:09
tsg:)05:09
claygawww man this is all fucked up - what'd you guys do to me?  "just go build the latest from source, it'll be better, trust us" :P05:09
tsgclayg: one reason why this isn't on pypi yet05:09
claygAttributeError: 'ECDriver' object has no attribute 'min_parity_fragments_needed'05:09
claygheh05:09
claygyeah np, I didn't even mean to be doing this right now - all I wanted was the fa index - got that - then got side tracked trying to figure out all of this - i should just stick up in swift - better for everyone probably05:11
tsgclayg: let's just stick to 0.9.8 for now - I need to look at why the API was reverted to an old version05:12
tsgI will drop you a note05:12
claygkthxbai05:14
*** ppai has joined #openstack-swift05:28
brianclinewell, crap, that answers that question: https://blueprints.launchpad.net/tempest/+spec/swift-test-without-keystone05:38
brianclinethe qa meeting logs from 2014-12 show discussion of it not really going anywhere05:39
brianclineum. 2013-1205:41
brianclineso by way of that requirement, defcore essentially means "you must be using keystone for anything"05:41
brianclinewhat a crock, imho05:53
*** k4n0 has joined #openstack-swift06:09
*** SkyRocknRoll has joined #openstack-swift06:17
*** SkyRocknRoll has joined #openstack-swift06:17
*** mmcardle1 has quit IRC06:23
*** nshaikh has joined #openstack-swift06:36
*** cbaesema has quit IRC06:38
*** cbaesema has joined #openstack-swift06:42
openstackgerritPrashanth Pai proposed openstack/swift: fsync() on directories  https://review.openstack.org/12692306:42
*** kyles_ne has quit IRC06:52
*** ppai has quit IRC06:55
*** ppai has joined #openstack-swift07:15
*** elambert has quit IRC07:17
*** mkollaro has joined #openstack-swift07:19
*** sungju has quit IRC07:27
mattoliverauGreetings from the south of France :)07:27
*** mkollaro has quit IRC07:31
*** tsg has quit IRC07:59
*** nellysmitt has joined #openstack-swift08:01
*** foexle has joined #openstack-swift08:13
*** bkopilov has quit IRC08:21
*** geaaru has joined #openstack-swift08:36
*** bkopilov has joined #openstack-swift08:37
*** foexle_ has joined #openstack-swift08:57
*** foexle has quit IRC08:59
*** bkopilov has quit IRC09:01
*** exploreshaifali has joined #openstack-swift09:05
*** RockKuo_ has quit IRC09:11
*** ppai has quit IRC09:14
*** bkopilov has joined #openstack-swift09:16
*** exploreshaifali has quit IRC09:18
*** jyoti-ranjan has quit IRC09:23
*** RockKuo_ has joined #openstack-swift09:24
*** ppai has joined #openstack-swift09:28
*** jordanP has joined #openstack-swift09:29
*** exploreshaifali has joined #openstack-swift09:29
*** jyoti-ranjan has joined #openstack-swift09:31
*** jistr has joined #openstack-swift09:34
*** addnull has quit IRC09:34
*** joeljwright has joined #openstack-swift09:44
*** kyles_ne has joined #openstack-swift09:52
*** RockKuo_ has quit IRC09:53
*** kyles_ne has quit IRC09:57
*** sluo_laptop has quit IRC09:58
*** RockKuo_ has joined #openstack-swift10:06
*** aix has joined #openstack-swift10:07
*** ujjain has quit IRC10:11
*** ujjain has joined #openstack-swift10:11
*** MasterPiece has quit IRC10:15
*** mmcardle has joined #openstack-swift10:20
*** haomai___ has quit IRC10:33
*** haomaiwang has joined #openstack-swift10:34
*** tellesnobrega_ has joined #openstack-swift10:35
*** mmcardle has quit IRC10:39
*** mmcardle has joined #openstack-swift10:41
rawat_vedamshi guys..10:49
*** exploreshaifali has quit IRC10:54
rawat_vedamswhen i am starting storage node services Unable to locate config for object-expirer  is it necessary to add object-expirer.conf file  .10:55
rawat_vedamsif i will not add this configuration file then what effect will happen to my swift storage node...?10:57
*** tellesnobrega_ has quit IRC10:59
*** nellysmitt has quit IRC11:00
*** nellysmi_ has joined #openstack-swift11:01
*** joeljwright has quit IRC11:01
*** mkollaro has joined #openstack-swift11:04
rawat_vedamshi friends11:04
rawat_vedamswhen i am starting storage node services Unable to locate config for object-expirer  is it necessary to add object-expirer.conf file11:05
rawat_vedamsif i will not add this configuration file then what effect will happen to my swift storage node...?11:05
*** aix has quit IRC11:09
*** haomaiwang has quit IRC11:10
*** RockKuo_ has quit IRC11:11
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Make preauth params work  https://review.openstack.org/13071111:12
openstackgerritMerged openstack/swift-specs: Composite Authorization and Service Accounts  https://review.openstack.org/10522811:25
*** aix has joined #openstack-swift11:25
openstackgerritDaniel Wakefield proposed openstack/python-swiftclient: Add unit tests for _encode_meta_headers  https://review.openstack.org/13305211:32
*** nosnos has quit IRC11:34
*** nosnos has joined #openstack-swift11:34
*** nosnos has quit IRC11:39
*** mahatic has joined #openstack-swift11:44
*** mmcardle has quit IRC11:54
*** joeljwright has joined #openstack-swift11:54
*** joeljwright has quit IRC11:56
*** dmsimard_away is now known as dmsimard11:57
*** lpabon has joined #openstack-swift12:07
*** kota_ has quit IRC12:11
*** jyoti-ranjan has quit IRC12:12
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Fix cross account upload using --os-storage-url  https://review.openstack.org/12575912:15
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Capture test output better  https://review.openstack.org/13123812:15
*** tdasilva has quit IRC12:19
*** dmorita has quit IRC12:28
*** erlon has quit IRC12:39
*** rawat_vedams has quit IRC12:42
*** lpabon has quit IRC12:50
*** lpabon has joined #openstack-swift12:51
*** aix has quit IRC13:01
*** joeljwright has joined #openstack-swift13:01
*** mmcardle has joined #openstack-swift13:01
*** aix has joined #openstack-swift13:04
*** SkyRocknRoll has quit IRC13:07
*** nellysmi_ has quit IRC13:19
*** ppai has quit IRC13:29
*** miqui has joined #openstack-swift13:31
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Suppress 'No handlers...' message from keystoneclient logger  https://review.openstack.org/13420713:37
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Suppress 'No handlers...' message from keystoneclient logger  https://review.openstack.org/13420713:38
*** aix has quit IRC13:40
*** bkopilov has quit IRC13:44
*** nshaikh has quit IRC13:44
*** tdasilva has joined #openstack-swift13:44
*** mahatic has quit IRC13:46
*** mahatic has joined #openstack-swift13:46
*** SkyRocknRoll has joined #openstack-swift13:47
openstackgerritDonagh McCabe proposed openstack/swift-specs: Adds Object Storage v1 API specification information  https://review.openstack.org/12938413:50
*** X019 has joined #openstack-swift13:50
*** X019 has quit IRC13:52
tdasilvainteresting...just came accross this link: http://webnumbr.com/open-swift-bugs13:53
*** jistr has quit IRC13:53
*** aix has joined #openstack-swift13:54
*** jistr has joined #openstack-swift13:54
cschwedetdasilva: uh, that one looks awful!14:06
tdasilvacschwede: yeah, it looks quite the steady climb since apr'1314:07
*** haomaiwa_ has joined #openstack-swift14:08
jokke_tdasilva: open-glance-bugs does not look any better ;)14:09
*** k4n0 has quit IRC14:10
tdasilvajokke_: yeah, did you see nova? over 100014:11
tdasilvacschwede, jokke_: the interesting thing is that it seems that there was a trigger event on apr'13 that sent numbers climbing14:14
*** joe__ has quit IRC14:15
cschwedetdasilva: yes, you’re right. and quickly going over https://bugs.launchpad.net/swift it looks a lot of bugs are cross-project, for example tests that failed in tempest14:16
*** tsg has joined #openstack-swift14:16
*** joe__ has joined #openstack-swift14:16
*** mmcardle has quit IRC14:17
tdasilvacschwede: oh, so maybe there was a effort starting in that release ( grizzly or havana I'm assuming) to start cross-project testing?14:17
*** joe__ has quit IRC14:19
*** wolsen has quit IRC14:19
*** wolsen has joined #openstack-swift14:19
cschwedetdasilva: not sure, but sounds reasonable to me. but at that point in time more and more swift tests were also added to tempest, and sometimes there are/were race conditions - thus more bug reports14:21
cschwedetdasilva: iirc, sometime ago the infra team asked to use „reckeck bug #123“ rechecks, so people started to add more bug reports to retrigger tests14:22
*** joe__ has joined #openstack-swift14:23
cschwedeanyways, we should try to lower the number and check which reports are actual „real“ bugs14:23
tdasilvacschwede: so tempest creates bug reports automatically? wasn't aware of that...but yes, I agree we should try to lower the number...14:25
cschwedetdasilva: no, not automatically14:25
cschwedebut more bug reports were added because of the policy to add a bug number in case of a recheck14:26
*** joeljwright has quit IRC14:31
tdasilvacschwede: got it14:31
*** mmcardle has joined #openstack-swift14:36
*** joeljwright has joined #openstack-swift14:37
joe__cschwede: Hi, just continue with the issue of where after a quarantine item is replicated back by another node, so far what I have done is that whatever server syncs back the miss matched path file I would just restart that node, so far I have restarted almost all of them, it does not seem to address the issue, however I will keep restarting so far I haven't seen the same node replicating back, it is random14:43
*** lpabon has quit IRC14:51
*** geaaru has quit IRC14:53
*** jistr has quit IRC15:06
*** jistr has joined #openstack-swift15:07
*** tsg has quit IRC15:16
*** lcurtis has joined #openstack-swift15:21
*** mmcardle has quit IRC15:22
swifterdarrelljoe__: thanks for digging into this further... has any node you've rebooted copied any file back to the wrong place again?15:23
joe__swifterdarrell: no so far15:23
swifterdarrelljoe__: k, so there's some chance that the problem will go away once the last node has been rebooted?15:24
* swifterdarrell has fingers crossed15:24
joe__swifterdarrell: I was wondering if there ia a large number of objects like this and the auditor takes too long to complete is it possible the object-replicator would just copy it back?15:25
swifterdarrelljoe__: I think that unless an object-replicator had the bad swift.conf values loaded (imported) into memory, it wouldn't copy them to incorrect locations15:26
swifterdarrelljoe__: (did I misunderstand your quesiton?)15:26
joe__swifterdarrell: okay I will wait, however I am restarting both nodes, the ones that did and did not have the bad swift.conf values15:27
swifterdarrelljoe__: have you seen any node which never had the bad swift.conf values replicate a file to the wrong place?15:28
joe__swifterdarrell: Yes I have seen it15:29
*** mkollaro has quit IRC15:33
joe__swifterdarrell: that is why I asked maybe because it is a large set of objects it takes too long for the auditor and therefore it doesn't qurantine in all nodes at the same time, and the replicator just replicates it because it was missing, etc...15:33
*** mmcardle has joined #openstack-swift15:35
*** annegent_ has joined #openstack-swift15:35
*** Nadeem has joined #openstack-swift15:49
*** jistr has quit IRC15:53
swifterdarrelljoe__: (cc cschwede) hopefully the replicator doesn't blindly copy an object based on where it was in the fs, but rather based on the hash of its name?  I think that's the sort of thing cschwede checked in the code yesterday?15:55
swifterdarrelljoe__: if the situation doesn't resolve with 100% certainty that no swift daemon has bad swift.conf data in memory (e.g. their swift.conf files have been sanity-checked and the server rebooted), then there may still be some mechanism of bad behavior we haven't thought of which bears investigation15:56
*** lpabon has joined #openstack-swift15:57
*** nshaikh has joined #openstack-swift16:13
*** exploreshaifali has joined #openstack-swift16:15
*** dmsimard is now known as dmsimard_away16:26
*** dmsimard_away is now known as dmsimard16:34
*** annegent_ has quit IRC16:37
*** annegent_ has joined #openstack-swift16:38
*** jistr has joined #openstack-swift16:51
claygman jenkins is on a tear this morning16:51
*** SkyRocknRoll has quit IRC16:55
*** tsg has joined #openstack-swift16:57
*** david-lyle_afk is now known as david-lyle16:58
clayggasp!  we've landed TWO specs now!16:59
*** kyles_ne has joined #openstack-swift17:00
*** kyles_ne has quit IRC17:02
*** kyles_ne has joined #openstack-swift17:03
peluseclayg, did you ever by chance run probetests on your SAIO with 8 devices?17:04
*** miqui has quit IRC17:08
*** miqui has joined #openstack-swift17:11
*** X019 has joined #openstack-swift17:12
*** aix has quit IRC17:16
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925017:16
openstackgerritpaul luse proposed openstack/swift-specs: Quick note about the reconstructor section being WIP so stale information isn't read here over the next few weeks...  https://review.openstack.org/13430617:18
*** mtreinish has quit IRC17:19
*** tellesnobrega_ has joined #openstack-swift17:22
*** foexle has joined #openstack-swift17:31
*** jistr has quit IRC17:32
*** openstackgerrit has quit IRC17:34
*** openstackgerrit has joined #openstack-swift17:34
*** exploreshaifali has quit IRC17:35
*** jordanP has quit IRC17:36
*** nellysmitt has joined #openstack-swift17:38
*** nshaikh has quit IRC17:41
*** exploreshaifali has joined #openstack-swift17:41
*** mmcardle has quit IRC18:01
*** openstackgerrit has quit IRC18:03
*** openstackgerrit has joined #openstack-swift18:04
*** joeljwright has quit IRC18:04
*** annegent_ has quit IRC18:12
*** annegent_ has joined #openstack-swift18:13
*** mahatic has quit IRC18:13
*** nshaikh has joined #openstack-swift18:13
*** lpabon has quit IRC18:14
acolespeluse: ^^ so your spec commit title says it all :)18:18
*** tellesnobrega has quit IRC18:19
*** tellesnobrega_ has quit IRC18:20
*** lpabon has joined #openstack-swift18:20
*** mahatic has joined #openstack-swift18:27
*** foexle has quit IRC18:30
*** zaitcev has joined #openstack-swift18:31
*** ChanServ sets mode: +v zaitcev18:31
*** X019 has quit IRC18:33
*** foexle has joined #openstack-swift18:37
*** nellysmitt has quit IRC18:39
*** X019 has joined #openstack-swift18:46
*** annegent_ has quit IRC18:49
*** openstackgerrit has quit IRC18:49
*** openstackgerrit has joined #openstack-swift18:49
*** tellesnobrega has joined #openstack-swift18:50
*** tellesnobrega_ has joined #openstack-swift18:50
claygpeluse: yeah doesn't work ;)18:53
claygpeluse: one line note saying everything is fucked - now that's a spec update I can get behind!18:56
openstackgerritMerged openstack/swift-specs: Quick note about the reconstructor section being WIP so stale information isn't read here over the next few weeks...  https://review.openstack.org/13430619:06
*** nellysmitt has joined #openstack-swift19:14
*** Poe_ has joined #openstack-swift19:15
peluseclayg, you like that huh?  :)19:17
pelusewill take a look at the probe failures now, really want everyone doing EV dev on the same ring setup and EC scheme now that PUT works19:17
*** openstackgerrit has quit IRC19:18
*** openstackgerrit has joined #openstack-swift19:19
peluseargh... EC of course (not EV, don't know what that is)19:19
*** shri has joined #openstack-swift19:22
*** annegent_ has joined #openstack-swift19:24
*** exploreshaifali has quit IRC19:25
*** acoles is now known as acoles_away19:35
*** mahatic has quit IRC19:47
openstackgerritThiago da Silva proposed openstack/swift: initial version of object version middleware  https://review.openstack.org/13434719:51
*** openstackgerrit has quit IRC20:04
*** openstackgerrit has joined #openstack-swift20:05
*** kyles_ne has quit IRC20:08
claygtdasilva: are you pulling object versioning out to middleware!?20:12
tdasilvatdasilva: yeah, that was the plan...thoughts?20:12
claygthat's awesome!  can't wait to review - why is it the "initial" version and not the "final" version?20:13
tdasilvahehehe...i should have said initial draft20:13
clayg... interesting20:13
tdasilvaI just wanted to get a first impression from you guys to make sure I was on the right path20:13
tdasilvaskipped all the tests, docs and everything else20:14
claygtdasilva: oic, cool - well hopefully we can get some feedback early - nice work20:14
tdasilvathanks, yeah, I did some manual testing and it works ok. The pieces I'm still unclear is on the container side of the code20:15
tdasilvaI think there is some code there to handle the header, but I'm not sure if that should be pulled to the middleware20:16
tdasilvaI'm guessing not20:16
tdasilvaI think there's some code on the object-servers too, but don't think that should be touched either20:16
openstackgerritThiago da Silva proposed openstack/swift: object versioning middleware  https://review.openstack.org/13434720:18
tdasilvaclayg: ^^^ better title20:18
*** tellesnobrega_ has quit IRC20:21
claygtdasilva: how's our functional test coverage of versioned objects?20:21
*** exploreshaifali has joined #openstack-swift20:26
tdasilvaclayg: I did not look too closely yet to be honest. I noticed there was only one test there that gets called multiple times (e.g., UTF8, cross-policy, etc)20:35
*** annegent_ has quit IRC20:36
*** annegent_ has joined #openstack-swift20:37
*** annegent_ has quit IRC20:51
*** nellysmitt has quit IRC20:55
*** annegent_ has joined #openstack-swift21:03
*** abhirc has quit IRC21:03
*** kyles_ne has joined #openstack-swift21:09
*** kyles_ne has quit IRC21:13
*** kyles_ne has joined #openstack-swift21:14
*** openstackgerrit has quit IRC21:19
*** openstackgerrit has joined #openstack-swift21:19
*** nshaikh has left #openstack-swift21:22
*** foexle has quit IRC21:23
*** lpabon has quit IRC21:25
*** tdasilva has quit IRC21:43
openstackgerritAnne Gentle proposed openstack/swift-specs: Adds Object Storage v1 API specification information  https://review.openstack.org/12938421:57
*** annegent_ has quit IRC22:08
*** tellesnobrega_ has joined #openstack-swift22:08
*** annegent_ has joined #openstack-swift22:11
openstackgerritAnne Gentle proposed openstack/swift-specs: Adds Object Storage v1 API specification information  https://review.openstack.org/12938422:26
*** joeljwright has joined #openstack-swift22:31
*** gyee has joined #openstack-swift22:37
peluseclayg, I didn't fully root cause the issue w/probetests and >4 devices on the ring but clearly someone had a guard against it, VALIDATE_RSYNC, that will result in skipping pretty much all the probe tests because of not using 3x repl and/or not using 4 devices22:38
pelusesee get_ring() in common.py of probe tests...22:38
claygpeluse: yes22:39
peluseso for now I'll push the SAIO env w/proper EC settings that we can all use for EC dev work knowing that there's a shitpile of probetest work to do (well we knew that already).  Coming here in just a minute22:39
openstackgerritpaul luse proposed openstack/swift: SAIO updates to support EC development environment.  https://review.openstack.org/12815422:45
peluse^ now configured for 4+2+2 w/8 devices on EC ring and still 4 servers.... (instead of before 5 servers 1 device each for 2+1+2)22:46
*** ahonda has quit IRC22:52
*** hondak has joined #openstack-swift22:52
*** Nadeem has quit IRC22:53
claygpeluse: hey that sounds pretty good, i've been doing 4 servers with 12 drives22:55
openstackgerritAnne Gentle proposed openstack/swift-specs: Adds Object Storage v1 API specification information  https://review.openstack.org/12938422:58
*** joeljwright has quit IRC23:03
*** foexle_ has quit IRC23:09
*** dmsimard is now known as dmsimard_away23:22
*** exploreshaifali has quit IRC23:46
*** annegent_ has quit IRC23:56
*** annegent_ has joined #openstack-swift23:58
*** lcurtis has quit IRC23:59
*** annegent_ has quit IRC23:59

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