Saturday, 2016-02-20

*** asettle has joined #openstack-swift00:04
*** asettle has quit IRC00:09
openstackgerritJanie Richling proposed openstack/swift: WIP: Set backend content length for fallocate - EC Policy  https://review.openstack.org/28257800:11
*** chsc has quit IRC00:16
notmynamemattoliverau: cool. so it's ready to land?00:27
*** sgundur has left #openstack-swift00:32
*** logan- has quit IRC00:35
*** garthb__ has quit IRC00:35
*** logan- has joined #openstack-swift00:41
*** loth has joined #openstack-swift00:44
lothHey all, how generally is the recommended way to do geo-relication for swift? storage policies?00:45
*** diogogmt has quit IRC00:46
notmynameloth: depends on your goal00:49
notmynameloth: one way (and the most common way I see it) is setting up a storage policy that spans multiple regions00:49
notmynamethen at that point, if you add an object to a container with the global storage policy, you end up with the data geo-replicated00:51
lothI did see this https://www.mirantis.com/blog/configuring-multi-region-cluster-openstack-swift/ which is called proxy affinity i guess?00:52
notmynamehttps://swiftstack.com/wp-content/uploads/2015/06/SwiftStackGlobalClusterDeploymentGuide.pdf is a swiftstack version of how to do that. it has config UI stuff particular to swiftstack's product, but all the settings are configurable by hand in the config files00:53
notmynameloth: and https://swiftstack.com/docs/admin/cluster_management/regions.html00:54
lothah okay, this is a more recent version of the one i found from 2012 :)00:54
lothI'll check them out, thanks!00:55
notmynameloth: the reason I point you there is that setting up a global cluster is tricky. well, more tricky to do right than perhaps a casual IRC conversation allow for. it's good to have thorough docs to peruse00:55
*** gyee has quit IRC00:56
*** trifon has quit IRC01:01
lothIs Swift a good storage location for CDN services, or should that be handled with something else? I can see objects can be made accessible via HTTP01:01
notmynameIMO, swift is fantastic as a CDN origin server. and I think swift is likely overkill for CDN PoPs01:04
lothFound this as an origin server middleware: https://github.com/dpgoetz/sos01:05
notmynameright. that's one that's been used at both RAX and HP for CDN services01:06
notmynameat very large scale in public clouds01:06
lothnotmyname: Thanks for the info! Do you know of any documentation regarding the recommended number of proxies vs storage boxes? Would that depend on the kind of usage that is expected? I can see that the recommended zone number is 5+, and those are largely flexible depending on cluster size.01:09
notmynameoh wow. 5+ zones is a *very* old recommendation01:10
notmynamethe recommended number of proxies is very much dependent on your usage patterns01:10
notmynameand, again with the swiftstack docs, https://swiftstack.com/docs/admin/hardware.html01:11
notmyname(BTW, I work at swiftstack, so that's why I'm familiar with the docs there)01:11
lothWas working with these, which are linked in the openstack doc pages http://docs.openstack.org/developer/swift/deployment_guide.html01:11
notmynameloth: as a very very general rule of thumb, you could likely do 1 proxy per 1000 requests per second that you need. with at least 2 because HA01:12
lothAnd those numbers are per zone?01:12
notmynameno. per cluster01:12
notmynameloth: bah! yes, the 5+ zone requirement was true back in 2012. since then it hasn't been true01:13
lothsuppose openstack doc team is a bit behind :)01:13
notmynamethat's not on the docs team. that's on us01:15
*** _JZ_ has quit IRC01:15
notmynameI filed a bug for it01:15
lothThats interesting, so in these examples there is one zone per rack?01:20
notmynameone zone per rack is generally what people do. that's a reasonable recommendation01:22
lothWhat was the reasoning for the 5 zone minimum in the past?01:22
notmynamebasically, a zone is a physical failure domain in your deployment. and a rack normally has a single ToR switch that is the failure domain01:22
notmynameoriginally, swift would only place 1 replica per zone. so for 3 replicas, you wanted a couple of handoff locations, and that gives you 5 or more01:23
notmynamehowever, these days, the only requirement is that you have at least as many drives as your replica count01:23
lothAh, makes sense01:25
notmynameinterestingly, there's been several generations of ring placement algorithms in swift. the first was the replica-per-zone model. next was the unique-as-possible. lately, we've updated that to be a "distributed-as-balanceable"01:27
lothHow does that work for clusters on the older algorithms, is there some sort of migration needed?01:27
notmynamethe first lasted about a year. the unique as possible lasted about 3 or 4 years. distributed as balanceable has been the new hotness for about 6 months now01:28
notmynamenope. each one can understand the older formats and just makes things better as you adjust capacity and rebalance01:28
notmynamenote that I've grossly trivialized some of the really hard and really interesting work that's gone in to all of that :-)01:29
lothHehe it sounds awesome :)01:29
lothCurrently I've got seperate keystone deployments in every region (which I relize now is probably a mistake). Is it best to have a centralized keystone deployment serving many regions for Swift?01:31
notmynameyou can read a lot of stuff abotu it at http://docs.openstack.org/developer/swift/overview_ring.html01:31
notmynameyeah, a centralized identity system normally makes sense. otherwise you get into "interesting" coordination issues01:32
lothMy other concern is applications already built around Swift wouldnt work without a centralized keystone server01:33
notmynameshouldn't matter01:34
notmynameapps that work with swift need to have some endpoint from which to get an auth token01:35
notmynamedoesn't really matter where, as long as the auth token they get can be validated with the swift cluster they connect to01:35
lothI thought apps that specify a single server (keystone) while giving a region would be expecting endpoint to change for each region, i guess thats incorrect01:38
*** arch-nemesis has quit IRC01:46
lothThanks again for the assistance!01:54
*** lyrrad has quit IRC01:55
*** lpabon has joined #openstack-swift02:05
*** klrmn has quit IRC02:06
*** asettle has joined #openstack-swift02:10
*** asettle has quit IRC02:15
*** rickyrem has joined #openstack-swift02:50
*** lpabon has quit IRC03:01
*** mingdang1 has joined #openstack-swift03:03
*** trifon has joined #openstack-swift03:05
*** rickyrem has quit IRC03:17
*** trifon has quit IRC03:19
*** asettle has joined #openstack-swift03:20
*** asettle has quit IRC03:25
*** trifon has joined #openstack-swift03:38
*** asettle has joined #openstack-swift03:43
*** mingdang1 has quit IRC03:46
*** asettle has quit IRC03:48
*** klrmn has joined #openstack-swift03:49
*** nadeem has joined #openstack-swift03:51
*** asettle has joined #openstack-swift04:06
*** asettle has quit IRC04:11
*** trifon has quit IRC04:15
*** esker has quit IRC04:33
*** esker has joined #openstack-swift04:43
*** mingdang1 has joined #openstack-swift04:47
*** chlong_ has joined #openstack-swift05:21
*** trifon has joined #openstack-swift05:25
*** haomaiwang has joined #openstack-swift05:39
*** zaitcev has quit IRC05:50
*** diazjf1 has quit IRC05:56
*** diazjf has joined #openstack-swift05:56
*** diazjf has quit IRC05:57
*** mingyu has joined #openstack-swift05:59
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-swift06:01
*** asettle has joined #openstack-swift06:09
*** asettle has quit IRC06:14
*** resker has joined #openstack-swift06:18
*** esker has quit IRC06:18
*** mingyu has quit IRC06:20
*** mwheckmann has quit IRC06:38
*** nadeem has quit IRC06:47
*** arch-nemesis has joined #openstack-swift06:51
*** trifon has quit IRC06:52
*** nadeem has joined #openstack-swift06:54
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** mingdang1 has quit IRC07:37
*** forcebanana has joined #openstack-swift07:38
*** haomaiwang has quit IRC08:01
*** haomaiwa_ has joined #openstack-swift08:01
*** haomaiwa_ has quit IRC08:03
openstackgerritTim Burke proposed openstack/swift: By default, disallow inbound X-Timestamp headers  https://review.openstack.org/27925608:05
*** klrmn has quit IRC08:16
*** haomaiwang has joined #openstack-swift08:18
*** haomaiwang has quit IRC08:23
*** asettle has joined #openstack-swift08:31
*** resker has quit IRC08:32
*** asettle has quit IRC08:36
*** mingdang1 has joined #openstack-swift08:37
*** esker has joined #openstack-swift08:40
*** mingdang1 has quit IRC08:41
*** haomaiwang has joined #openstack-swift08:50
*** haomaiwang has quit IRC08:54
*** SkyRocknRoll has joined #openstack-swift08:59
*** haomaiwang has joined #openstack-swift09:05
*** haomaiwang has quit IRC09:10
*** haomaiwang has joined #openstack-swift09:34
*** haomaiwang has quit IRC09:47
*** haomaiwa_ has joined #openstack-swift09:50
*** trifon has joined #openstack-swift09:57
*** SkyRocknRoll has quit IRC10:00
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** haomaiwang has quit IRC10:02
*** stantonnet has quit IRC10:04
*** stantonnet has joined #openstack-swift10:05
*** mingdang1 has joined #openstack-swift10:25
*** esker has quit IRC10:32
*** SkyRocknRoll has joined #openstack-swift10:33
*** esker has joined #openstack-swift10:38
*** openstackgerrit_ has quit IRC10:40
*** openstackgerrit_ has joined #openstack-swift10:41
*** haomaiwa_ has joined #openstack-swift10:45
*** openstackgerrit_ has quit IRC10:48
*** haomaiwa_ has quit IRC10:49
*** haomaiwang has joined #openstack-swift11:00
*** asettle has joined #openstack-swift11:00
*** haomaiwang has quit IRC11:01
*** asettle has quit IRC11:06
*** Jeffrey4l has joined #openstack-swift11:17
*** biyiklioglu has joined #openstack-swift11:24
*** biyiklioglu has quit IRC11:29
*** biyiklioglu has joined #openstack-swift11:29
*** nadeem has quit IRC11:44
*** biyiklioglu has quit IRC11:54
*** ChubYann_ has quit IRC12:10
*** ChubYann_ has joined #openstack-swift12:23
*** Jeffrey4l has quit IRC12:41
*** asettle has joined #openstack-swift12:53
*** Jeffrey4l has joined #openstack-swift12:54
*** asettle has quit IRC12:58
*** haomaiwa_ has joined #openstack-swift13:09
*** urth has quit IRC13:31
*** urth has joined #openstack-swift13:34
*** haomaiwa_ has quit IRC14:01
*** haomaiwang has joined #openstack-swift14:01
*** asettle has joined #openstack-swift14:12
*** asettle has quit IRC14:18
*** baojg has joined #openstack-swift14:18
*** forcebanana has quit IRC14:25
*** mingdang1 has quit IRC14:34
*** haomaiwang has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
*** sgundur has joined #openstack-swift15:41
*** sgundur has left #openstack-swift15:41
*** haomaiwang has quit IRC16:01
*** haomaiwang has joined #openstack-swift16:01
openstackgerritTim Burke proposed openstack/swift: By default, disallow inbound X-Timestamp headers  https://review.openstack.org/27925616:24
*** arch-nemesis has quit IRC16:25
*** Jeffrey4l has quit IRC16:32
*** arch-nemesis has joined #openstack-swift16:41
*** klrmn has joined #openstack-swift16:42
*** asettle has joined #openstack-swift16:52
*** asettle has quit IRC16:57
*** rcernin has joined #openstack-swift16:59
*** arch-nemesis has quit IRC17:00
*** haomaiwang has quit IRC17:01
*** haomaiwa_ has joined #openstack-swift17:01
*** asettle has joined #openstack-swift17:07
natarejso i'm in a situation where i can repurpose some hardware for swift storage nodes for some excellent value capacity17:09
natarej32 bays available with 12 core xeons17:09
natarejhowever it's limited to 1gbe which would be outward facing and 1x10gbe cluster facing17:10
*** asettle has quit IRC17:12
*** arch-nemesis has joined #openstack-swift17:12
natarejwhat would be the most storage you'd be comfortable running with such network limitations? could run up to 256TB for $7000USD but it would take over 2 days to rebalance with the single 10gbe17:14
*** arch-nemesis has quit IRC17:22
openstackgerritJoel Wright proposed openstack/python-swiftclient: Do not reveal auth token in swiftclient log messages by default  https://review.openstack.org/28236317:46
*** ChubYann_ has quit IRC17:54
*** rcernin has quit IRC17:55
*** rcernin has joined #openstack-swift17:59
*** haomaiwa_ has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:01
*** ChubYann_ has joined #openstack-swift18:07
*** baojg has quit IRC18:27
*** asettle has joined #openstack-swift18:50
*** mwheckmann has joined #openstack-swift18:55
*** asettle has quit IRC18:55
*** mwheckmann has quit IRC18:59
*** haomaiwang has quit IRC19:01
*** haomaiwa_ has joined #openstack-swift19:01
*** mwheckmann has joined #openstack-swift19:02
*** SkyRocknRoll has quit IRC19:06
*** mwheckmann has quit IRC19:08
*** haomaiwa_ has quit IRC20:01
*** haomaiwa_ has joined #openstack-swift20:01
*** jmccarthy has quit IRC20:11
*** jmccarthy has joined #openstack-swift20:12
*** Gordoni has joined #openstack-swift20:32
*** proteusguy__ has quit IRC20:49
*** asettle has joined #openstack-swift20:51
*** rcernin has quit IRC20:56
*** asettle has quit IRC20:56
*** haomaiwa_ has quit IRC21:01
*** haomaiwang has joined #openstack-swift21:01
*** proteusguy__ has joined #openstack-swift21:02
*** forcebanana has joined #openstack-swift21:12
*** sgundur has joined #openstack-swift21:25
*** rcernin has joined #openstack-swift21:30
*** trifon has quit IRC21:30
*** klrmn has quit IRC21:46
*** klrmn has joined #openstack-swift21:47
*** haomaiwang has quit IRC22:01
*** haomaiwang has joined #openstack-swift22:01
*** sgundur has left #openstack-swift22:07
*** haomaiwang has quit IRC23:01
*** haomaiwang has joined #openstack-swift23:01

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